I joined the meeting late, but Alan and Steve were going over SG&A costs when I got there. They have a client that is wanting to virtually plug the SG&A numbers. Steve was talking about how that is playing with fire and not good accounting. After that, Alan gave a small demo of his production and advanced recipe/build process for sub inventory. It looked great and had lots of heavy client-side JavaScript stuff going on.

We covered a bunch of topics. Here are some small notes that I picked up from the discussion. No specific order.

- Steve and Alan were discussing settings and adding more settings for production and manufacturing.

- Steve was asking for input on direction, on the sales side of things.

- Alan was proposing some industry specific skins to help with sales.

- Alan was also saying that we should circle back around and build out more reports or even dashboard level pages to show all of quick data, counts, and totals. He was saying, we should stick to our name - Adilas - All data is live and searchable - stay true to that slogan. Along with that, we were talking about some places that still need some help and a little bit of loving. Sub inventory was a big topic along with other histories.

- Steve mentioned that he is working on some job costing options and reports. Tying in expenses, invoices, deposits, PO's, and time cards to elements of time (the job or projects).

- Small observation - both SG&A costs and job costing are dealing with deeper tracking of sub pieces and components that make up a bigger thing or item. Kinda interesting. That's some deep terrain and more than just simple inventory tracking. It's a mix of operations being tied into accounting.

- There have been more requests for more charts, graphs, and eye candy type stuff. At one point, we really wanted to do some graphical homepages to show and highlight some of that data. We have all of the data. It just isn't presented in an eye candy and easy format to see and look at.

- Alan is thinking that people (our clients and users) are going to be looking for more and more efficient ways of doing things and tracking things. There seems to be a draw or trend towards efficiency.

- We spent some time talking about AI stuff (artificial intelligence). That is a big buzz word right now. What if we redid some of our homepages (made them more graphical) and helped to show trends and month over month, year over year tends and patters. That could be really cool!

- We talked about the history homepage and how it shows a great overview of what was done or worked on throughout the day. That is some great information and a great daily summary of what happened in the system. Steve was showing that piece to a perspective client and they were super impressed.

- Back to AI stuff. We may use some verbiage like, we do such and such, similar to how AI works, without actually saying that we are using true AI. We already do a lot of that type of stuff. We feed data in, we then train the system to do certain things with it. As we go along, we can see areas that we could work on and turn our interface into a more AI oriented type product. We're not that far off, even right now.

- More talk about comparing patterns, comparing trends, and showing business intelligence (BI) level stuff.

- Mike, would like us to work more on the backend accounting pieces to help round out the system. Mike is a CPA that Steve has been working with for years.

- We could gain a lot, even on the virtual AI level, if we started to build out reports that show the known issues. We have a whole page that lists places and scenarios where things can get off the tracks or in the ditch (virtually). Date problems, number mismatches, disconnects, cart before the horse stuff, etc. That would be super cool to get those pieces built into the system.

- We circled back to sub inventory and possible ways of fixing things up there. We would love to add part id's, part category id's, and other key attribute id's to help the retrieval be faster and smoother. We can get the data in, it's the getting it back out that makes it a little bit harder (current database relationship structure). Anyways, some talks about ways to sure things up and fix some of the underlying pillars in the system.

- Quite a bit of discussion about Biotrack and Metrc (state compliance systems). We spend a lot of time and money trying to keep these connections up to date and working correctly. It's a moving target. We also want to pass on some of the costs to our clients and users.

- Our clients have some great ideas and tend to tell us what they are wanting and/or needing. That is awesome! We just need to figure out how to charge them for those upgrades. Basically, who is going to pay for the changes? Sometimes that can get tricky - either way, it's still part of the game we play.

- Most of our clients want real-time data going back and forth (live - not batched or staged).

- Alan and Steve were talking about ways to simplify the current API connections.

- Light talks about what some of the other developers were working on.

- We would love to be able to bill for real usage and what features our clients are using.

- We keep seeing costs increase. This is costs to us, costs to our clients, and even costs that 3rd parties are pushing and/or passing on. Everything seems to be in a state of upward flux. Along with this conversation, there were talks about some of the 3rd parties limiting throughput and/or limiting the number of API socket requests without a price increase.

- We talked about changing some of the file names. Some of the pages started out as a cannabis related page. We are now making those things more general so that we can use them (the pages and features) for our other clients.

- Going where the money is (based on client requests).

- Steve wants us to quote/estimate some new code for a client. Alan was recommending that we break things into phases and stages. Good discussion on this topic.

- Steve is doing some high-end business consulting for some of our clients. Helping them make decisions and plan for the future.

- The last topic of the day was thinking and finding ways to harvest the services (service byproducts) that our clients want or need (adilas marketplace stuff). If we help our current clients, that is an avenue of funding that comes from inside vs having to get new clients. Basically, help them get what they want. Steve put it this way - make your choice and then build up that choice (meaning software choice and pushing that software further along).