Recording notes from 5/27/25 to 5/28/25.

Phone call with Bryan to go over some ecommerce questions. He has a client that wants to use multiple locations out in ecommerce land. Normally, we use a setting and then just use that single location/store out in ecommerce land. We talked about what would need to be done to make it all work and how long that may take. We will dig into this tomorrow over a GoToMeeting session.

Working with Russell on the graphical homepages project. Only got about half an hour today. We ran late on an earlier meeting and then I got pulled off because my wife needed me to pick up our daughter. Short meeting today. Working on layout stuff. I got a couple of screenshot graphics from Russell to help with the project. See attached.

Steve and I going over highlights and thoughts from our meeting. Phone call going over plans, vision, and other things that are circling around. We are really trying to educate people that we are working with. It will help them out in the long run.

There were 12 people on the call. 4 from adilas (Steve, Sean, Josh, and I). The rest were from Yogen Fruz. We started out and Sean was giving a demo to their team. He started with clock in/outs. Then he showed some simple carts, checkout options, gift cards and loyalty points, and discounts. Simple POS stuff.

He was able to switch from the demo site out to the live site to show some real values. They, the Yogen Fruz team, got into some questions about the backend and cost of goods. It got into accounting pretty quickly vs just POS stuff. Steve took over and showed some new AI (grok) stuff that he is working on. I took a bunch of other notes. Here they are, no special order:

- They are wanting an offline solution. Adilas is a full web-based solution currently.

- There was a super diverse group, lots of questions from their different sides. Operations, POS, hardware, accounting, managing, etc.

- Steve was talking about adilas and how it is setup as a paperless office. Tons of options to add photos, scans, images, and other media/content or files for documentation. Currently, the YF team is very heavy into tons of spreadsheets and such.

- Talking about backend accounting options. Light show and tell session.

- Ivan - new guy - seemed pretty technical. He has some great questions and tried to keep the meeting on task. It was going all over the place.

- One thing that Steve and Josh were saying was, they could use their phones or any other web connected device, if the Internet went down. They were even talking, say a physical unit goes down (physical failure). They could even use any device until we (they) get them new hardware - different backup options.

- Lots of talk about API socket connections and connecting with delivery options and other possible vendors and 3rd parties. Mixing and blending pieces.

- AI talk... where we are heading - sanitation of data - security and transfer of data.

- Steve was pitching enterprise level mapping for customers and items.

- Aaron (main boss) was saying... we are planning to release these features in stages. Some of the questions were directed to POS, ecommerce, scheduling, payroll, financials, etc. Aaron seems to be catching the vision. I don't know all of the stages, but imagine something like: Stage 1, POS and inventory tracking, stage 2, ecommerce and menu boards, Stage 3, backend accounting, etc.

- Lots of talk about hardware stuff, including menu boards, printers, and POS stuff.

- They wanted someone to fix the Windows settings for multiple displays (2-sided POS station - cashier and customer side). They can do it right now, but they want it to be automated. That is a Windows thing but we will get someone on that.

- Towards the end, there was some talking about pricing and what is included - setup, monthly, ecommerce, support, changes, etc.

- This is just for me... It really seems like they want the moon, but they are trying to talk us down on everything (cost wise). Most of our other clients, we offer something, and they say yes or no. They do a lot on their own and we either train them or setup a plan to get them the help that they need. This one seems like there will be some direct handholding along the way. We just have to make sure that expectations are set before we (or they) commit to something. I have already seen some feature creep for this project (the scope keeps changing). I really hope that we nail down the stages or phases and then stick to that. It could get crazy if that is not followed.

- Good overall meeting. We left it in their court. Steve and Josh will do some follow-up.

Benning golf tournament plan. Meeting with Bryan. Going over deliverables for the golf tournament. He had a document prepped with an outline. We then went through the outline and filled in either questions, assumptions, and/or plans. It went pretty smoothly, as far as a brainstorming process. Bryan has all of the notes.

Phone call with Steve. Touching base on different needs and things that are going on. People are looking for solutions. Talking about some of our new and old connections and contacts. Going over some marketing ideas and who will help us with those marketing efforts. Good catch-up phone call.

Meeting with Steve and Cory. We stared out by doing a recap of our plan and going over a number of scenarios. I got some questions answered. They want us to hyperfocus on the MVP and go from there. Anything extra, needs to sit on the side. We may end up circling back around. We talked about voids and limiting those options (making things go away after other transactions or sub cause and effect processes have taken place). Some of those interconnected processes can get super crazy if too many things start interconnecting and then you void something. We spent some time and went over vendor credits (new project) and how all of that will work out and play through. We had some great conversations, and I got a bunch of questions answered. I'm ready to start building.

Tech support to help Michael with some backend queries. Ran a couple of queries and sent the results to the 3rd party developer for review. Multiple emails and back and forth.