Recording notes from 6/10/25 to 6/14/25.

Working with Bryan and going over a comic book ecommerce demo and what they are doing. Brian Mowris from FineTech has a few clients that are in the hobby store arena. They are looking for quick ecommerce, full POS, and all of the other fun stuff that adilas could bring to the table. These are smaller customer but there could be a lot of them. We watched a demo and I took a few notes. We then got Brian Mowris on the phone and chatted with him. We feel like we are 85% of the way there, out of the box. We talked about a few funding options and how best to proceed. Good stuff.

Meeting with Shannon and working on content for the adilas value add-on core model. This is somewhat of the master plan and where we are heading. Today we were working on content for defining the core. Here is some of what we came up with... we may still edit some things but it's a start.

New content... - part of the value add-on core

Before defining the current adilas core, we thought that it would be helpful to show what is common or somewhat industry standard as far as matching software to needs.

The current approach that most businesses use is to look around and try to find the best in class pieces of software. Then they try to marry those software pieces together to get a semi-workable system. This commonly ends up being a solution that includes anywhere from 4-10 (or more) different software packages to run their business. Imagine something like this: Best in class inventory tracking, best in class POS (point of sale), best in class ecommerce package, accounting, payroll, timecards, CRM (customer relationship management), project management, scheduling, etc. You get the idea... Does this sound familiar?

This ends up being what is called a "mashup", or mix, of different software packages all trying to be pulled into one workable solution. The pain comes in as each piece dead ends and doesn't fully fit with the other pieces. You end up in somewhat of a time sink as you have to duplicate data or search for data details in or from one software package to the other. Not to mention that you have different accounts, contracts, logins, and are paying for multiple pieces of software.

Inside of adilas, we are demonstrating that it is possible to do all of these critical business functions in a single integrated system. This is what we do at adilas. Imagine being able to do full inventory tracking, fully configurable POS functionality, CRM functionality, scheduling, accounting, payroll, ecommerce, full financials, reporting, exports, and having a virtual paperless office (CMS - content management system). This is just the surface of what is available with adilas, one system, all working together in an integrated solution.

Some of the benefits of having a fully integrated solution are things like: Having everything in one place and it all interconnects (no dead ends). Being able to search and find underlying details of amounts, sums, and counts. Not having to buy all of the other software packages. You are no longer limited to strictly linear processes. You are able to have a virtual three-dimensional (3D) system that allows you to enter data at any level and it will interconnect. Another huge advantage is that you get to use what features you want and don't have to use other features that you don't need. It's all there, if you need or want it.

To describe the adilas transactional core, what already exists, we will start with the word "transactional". This means - details or individual transactions. If you catch every penny in and every penny out, every invoice, every PO, item usage, expenses, deposits, etc., you start getting transactions and data history. This creates multi-relational data stored over time. All of these underlying details and histories become the transactional core. Everyone who uses adilas will need a transactional core. This is what people will purchase as the base model for how they run their business.

If you want more, here is a 50 slide pitch of what we do... have fun... we call this the presentation gallery.

Working with Bryan and going over new code to be able to switch locations out in ecommerce. He also introduced a quick mode that skips certain steps and limits how much editing of customer and profile type information. He is calling it quick shop mode. Light debugging and looking over new code. We made a few changes and then did some code branch management stuff to get everything all good to go. Fixed a merge conflict and got the new branch all merged into the master code branch.

Working with Russell on the graphical homepages. More work on custom CSS and setting up layers to help guide the users to what is most important. Working on leading the eye from one thing to the next in a hierarchy of visual elements. It sounds cool, but it takes some work and planning to really make it happen. He is more skilled than I am with that kind of stuff.

Meeting with FineTech folks. Bryan Dayton and I were on the meeting on the adilas side. We didn't really know what the subject of the meeting was. The FineTech folks had a number of questions about merchant processing, onboarding, custom quotes, and possible white label stuff.

We explained the integration of Clover devices, emphasizing the use of the Cloud Pay Display app for connectivity. We then discussed the technical aspects of merchant processing, device compatibility, and the need for API credentials. Jennifer inquired about onboarding processes, training, and the potential for customization. I provided contact information for key Adilas team members for support and training. The meeting concluded with a discussion on industry targeting and the importance of clear communication for updates and new features.

Back on the vendor credit project. Passing params to help create new vendor credits. Part manual but part automated (what the new credit is tied to - PO's, expense, and vendor id's). Working on the flow process and what is connected to what.

Phone call with Steve going over some sales strategies and ideas. He was on a meeting with a lady who knows Josh from California. She was proposing that we change our onboarding process. Instead of talking to a company and showing them a small demo, basically telling them that we will do a 3 month free trial and help them along the way. She recommended that we find businesses that have multiple locations (say 2-50 locations). We then jump in and show them vs trying to talk them into saying yes.

She was also telling Steve some basic numbers... For example: If you take our total overall revenue and divide it by the number of clients (regardless of what they have paid), you get a simple client value. So, for us, it came out to an average client value of $11,000. So, even if it takes us a couple of thousands of dollars to get the client, they end up being worth $11K ish (average).

She was also recommending that instead of building out a huge demo site and then trying to show the client, we spend that same amount of time helping the actual client do their stuff and run their business. If we do this, we spend the same amount of time and potentially cut the training time and help a client see what we can do, first hand. Interesting ideas.

Here is the quick summary - just for fun - free trial - figure $2k onboarding - worth $11k average - give it away - go after businesses with multiple locations - reallocation of funds - helping businesses succeed.

From Bryan - Check and push Healthy Bite code

Working with Bryan. Looking at session values and switching locations out in ecommerce land. He is calling it the quick shop settings. We spent some time and reworked a query to only pull items per location that have 1 or more in the total quantity per location. Should be some good stuff. He still needs to work on it a little bit, but making great progress.

Small fixes and checks after a meeting with Steve and Cory. Working on the pay PO page and the display for the payables homepage. Showing vendor credits with other totals at the top of the page.

Small internal tech support things with Cory - time card clean-up and helping with payroll and commissions. Talking with Steve about AI integrations and new settings and filters on the fulfillment pages.

Meeting with Steve and Cory. The whole meeting was a little bit over an hour. The first 45 mins were spent reviewing where we are at on partial PO and vendor credits project. I showed them some of the pages and code. We went through a few different scenarios and what not. I took a few notes on places that still need some loving. Making good progress. We should have this vendor credit portion done by the end of June.

Working on adding vendor credit links to the po line items page. Options for viewing existing credits and creating new ones. This is part of the manual creation process for vendor credits.