Good phone call with Andrew. After the phone call, he sent me an email with some good stuff in it. I also sent him an email with a couple of links about where we are heading.

These are the links that I sent him...

master plans going forward... https://data0.adilas.biz/lite/

the presentation gallery... https://news.adilas.biz/sales-gallery/adilas-advert-index.html

investment opportunities... https://data0.adilas.biz/lite/adilas_investment_opportunities.cfm

Here are a few of my notes from the phone call.

- Andrew just jumped into it. I got some of his full life story, right off the bat. We even talked about some recovery stuff and some tough spots.

- He has experience working with POS systems, retail, restaurant, hotel, frozen yogurt, franchising, beverages, etc. Pretty diverse.

- He likes to bring value where he can, in any way.

- He has some psychology training and loves people.

- He shared some stories about alcohol, drugs, ADHD, and God given gifts. Fun conversation.

- He was talking about his mission in life and how he wants to help people.

- Seems to be a big thinker. When asked, he said, "I don't live in problems - I figure out solutions and move on."

- He said that he likes to study.

- Create awareness and access - make it affordable.

- Lots of time learning AI - like ridiculous amounts of time...

- Building tools for himself, no code experience, able to verbalize what he sees.

- Trying to match up the right places with the right people - protecting people that he cares about.

- Controlling chaos and not getting stressed out - plans on it being crazy and when it is, he's already there... then just start bringing it back down until it is in control.

- Thinking about how he thinks and learning about himself or learning about yourself.

- He is always talking to vendors and knows how to talk and speak their language.

- Quick at catching the idea and then being able to virtually spitball ideas, based on what he knows.

- Being strategic with the bells and whistles.

- Building websites - a way to get ideas out of his head - almost mini presentations, but clickable, with some light content and concepts. Quick brain dumps using AI to help build the websites.

- There is some magic in seeing things visually. He just talks to ChatGPT and does a lot of copy and pasting things into a site builder app.

- He shared a couple of websites with me. One is called Logics420, another is called GCBuddy (general contractor buddy), and a small adilas demo site. He likes to build things, tinker, and then refine as he goes.

- If he can see it in his head, he tries to verbalize it, and then make it into something.

- Give lots of free feedback.

- Towards the end of the call, we were talking about adilas, AI, bots, and how to get that all put together. Fun conversation. He was saying something that I thought was really cool. Instead of having one bot that knew everything. He was saying, what about a bot per section or even per page, then connecting those bots together. Creative idea and I could see how it could help train the bots, just what was needed and nothing else. This may not be the final idea, but I thought that it was worth recording.

- Target the medium sized industries.

- He highly recommended that we, the adilas team, focus on the Grok AI integration. Steve has been heading that up, so far. I know that he wants help, we just get pulled off on other pieces or to different projects. Lots of moving parts and pieces.

- Anyways, great phone call. I enjoyed it and scribbled down a number of post-it notes, while we were talking and chatting. We'll talk again soon, I imagine.

Adilas Key Contributors:

Steve Berkenkotter - Main owner and business partner - original ideas, concepts, and training - sales, relationships, dreamer, visionary, custom code, coordinator, builder of the first industry specific skin, and the list goes on. Huge player in the adilas story and timeline. One of the original owners in Moring Star Automotive - where the system came from. There are three known Steve's in the system notes. Most of them are this Steve (99 out of 100 times). He won't admit it, but adilas was his brainchild.

David Berkenkotter - Steve's brother and business partner in Morning Star Automotive. David was a system user and helped us create the adilas quick search. He liked using that feature, the quick search, but it only existed on one page originally. He wanted us to put it on every page. That ended up being in the header. He was also one of the original partners in adilas. Power user in the system. Sadly, he passed away due to cancer.

Shari Olin - Commonly known as "Shari O.". She worked in the accounting department back in the Morning Star days. She has been somewhat of a mother hen to help all of us crazy chickens keep going. She helps with customer support, training, payroll, bill collection, and tons of backend office functions. Major power user. Just being silly, but she can have the mouth of a sailor but the heart of an angel. Part of the adilas admin team and a great friend.

Craig Leitner - Also part of the original Morning Star team. Craig was the automotive floorplan and bank guy. He is a power user in the system and does a lot of bank reconciliation and other tasks. He currently works with Steve and asks as the adilas controller (money flow guy).

Cory Warden - Originally an adilas rep and consultant. Cory become part of the team after being a rep for quite some time. She helps with customer care, client support, project management, and keeping the team on track. She also does all of the news and updates and other training material. Cory does tons of oversight type services for our clients. Power user and part of the admin team.

Sean Carlton - Sean was a manager at a Cannabis dispensary in Colorado that used adilas for years and years until they sold. Steve recruited Sean to help with sales, deployment, and training. Sean brings lots of usage experience. Often, he is one of the helpers if we need to send someone onsite to help with a deployment or training session. Power user.

Brandon Moore - I'm one of the guys that writes most of the developer's notebook entries. Originally, I was hired by Morning Star, the automotive dealership, to help with data entry, accounting, and website stuff. I ended up being one of the main adilas developers and architects. I build content, write code, help other developers and team members, and help with training. Helped start the project back in 2001 under the Morning Star name.

Chris Dunsey - One of the first adilas interns (developers). Helped with a number of projects. Ended up being somewhat of a consultant later on.

Shawn Curtis - Kinda a funny story. He was taking a developer's class at Bridgerland. He knew my brother Russell. He asked to join our developer class and became one of the first interns along with Chris Dunsey. Shawn ended up helping with payroll and other projects. Some of the photo galleries in the system came from Shawn's help. He also worked on the media/content (file upload) pieces. Later on, he did more payroll work and acted as a buddy to Brandon and did some consulting work. We worked together for years and years.

Russell Moore - Russell is my younger brother. Originally, he was added to the group because of his graphic skills. He ended up being a great backend developer and project manager. He has also acted as a trainer and mentor for Brandon along the way. Much of the current system came from projects and efforts that Russell was involved with. He has also been Brandon's AI tutor in recent years. Great help to the system. Huge contribution.

Chris Johnnie - He is an entrepreneur who teamed up with Russell to help create a company called "Adilas For Business" or "AFB". Eventually, both Russell and Chris sold their pieces back to adilas. They were honestly the first ones to really try to run as a white label of adilas. This was back in 2015 and 2016. Chris really helped to push the product to the next level along with Russell's help.

Danny Shuford - Longtime friend of Steve's. Danny helped with some website design, sales, and videos for adilas. He even got into creating custom PDF labels for clients. Light development work.

Marisa Shaw - She is Danny's daughter. Danny brought her to an adilas training event in Denver, CO. Marisa was the star student. She ended up helping with some graphics, flyers, marketing material, teaching, instruction, and planning. Power user. Very helpful.

Shannon Scoffield - Shannon is Brandon and Russell's sister. Her maiden name is Shannon Moore. Huge help and virtual assistant to Brandon. She has helped with training, project management, and content creation. Most of the major content sessions were or have been with Brandon and Shannon working together. When they, Brandon and Shannon, were traveling, Shannon was one of the primary adilas instructors. If she was teaching Brandon was taking notes. If Brandon was teaching, Shannon was taking notes. Power user.

Cheryl Moore - Cheryl is my mom. What an asset. She owns a small business and has owed a few different ones. When we were doing training sessions, she came to every one of them. She asked wonderful questions and was a great supporter. Sometime, I would use her as a test subject - can my mom do this? If yes, we are good. If not, we may need to keep tweaking it. Thanks mom!

Wayne Moore - Wayne is my dad. He was my hiking buddy and more than willing to talk about ideas and concepts on our walks and hikes. He helped out with video stuff and was a great coordinator for making other connections. He worked at Bridgerland (technical college) and helped us get setup with classrooms, computer labs, and other great connections. Huge cheerleader! There is another Wayne, Wayne Andersen, he is a backend developer, systems guy, and database guy.

Wayne Andersen - This Wayne lives in Portugal and helps with all of the backend security, server, and code testing. Major skills, writes code, helps push all of us to new technologies, partially retired but loves to play with tech stuff. If you search for Wayne and it deals with concepts and coordination stuff, that's my dad, Wayne Moore. If you search for Wayne and it sounds like a master backend guy, that's Wayne Andersen.

Alan Williams - One of the lead developer's at adilas.biz. Alan joined us in 2015 and quickly came up through the ranks. Trainer, CTO, team lead, master developer, prototyper, and system architect. Alan has helped with many projects and features over the years. He also helped Brandon with some of the prep work for the adilas lite (fracture) plans and project. Sometimes called "Dr. Alan" by the other developers. Example: This might be a project for Dr. Alan.

Bryan Dayton - Bryan has been one of the most versatile guys on our team. Originally, he joined a development class out of curiosity. He and Brandon live in the same town and know each other from church. Bryan has done more custom code or small system projects than almost any other developer. He also joined the team in 2015. He helps with sales, custom projects, pushing on projects that he thinks will yield a return. Lots of work on the adilas lite and fracture project. Very hard working and versatile.

Dustin Siegel - Developer who helped with numerous cannabis and cultivation type projects. He worked directly under Steve to help with that business vertical. Many of the original pages that Steve built were taken over and remade by Dustin.

Eric Tauer - Developer and custom code guy. Originally, Eric knew Steve and lived in Salida, CO. As a note, adilas is Salida spelled backwards. Eric has a background in database work and data warehousing. Eric has done tons of custom systems for clients. Often, Eric would pioneer certain features or logic, as custom code, and then we would bring those features into the main adilas application.

Garrett Kirschbaum - Adilas intern and then full developer back in 2015. Stressful time of building and expansion. He and others helped run the adilas shop with Brandon's help. Garrett was a great developer and helped us standardize a number of tools and features. He was the first developer to work on sub inventory, back in the day. He also did other projects and helped with some developer management stuff.

Charles or "Chuck" Swann - Charles was an instructor at Bridgerland for web development. He builds custom websites, does amazing mock-ups, prototypes, and is a CSS master (styling a website using code). Chuck worked with Russell to help with redesign work, projects, and vision. Chuck worked fulltime for a number of years and now works and coordinates work done by a small hand-picked design and development team. Anything that needs some design loving gets passed over the Chuck and his small team.

Steve McNew - Friend of Steve Berkenkotter's. This Steve helped prep some whitepaper documents to help with getting adilas standardized and some internal audit type stuff. Mostly white papers and putting things down on paper. He ended up getting hired by the local school district and wasn't able to finish the process, but he got it started. He asked some great questions, and we had some good conversations.

Abby Elkins - Abby is Brandon's daughter. Her maiden name was Abby Moore. Abby, when she was little (10-12 years old) helped with some of the original concept artwork for adilas. Later on, she helped with content for the presentation gallery and then the adilas lite plans (fracture). Currently, she is working graphic artwork for different adilas pages. She's now in her mid 20's and has some awesome art and content skills.

Aspen Moore - Aspen is Abby's younger sister and Brandon's daughter. Aspen helped Brandon with some planning and counseling (mental help). Aspen also did some general business consulting with her dad Brandon.

John Maestas - Developer, backend server guys, and designer. John came to us through Dustin. John was uses as a jack of all trades on the backend and frontend. He did numerous projects, documentation, payroll, and page redesign projects. John was also very help to Brandon in working on the notes and comments on the SWOT analysis document. Many other projects as well. Good vision of the future.

Kiva Berkenkotter - Steve's wife. She helped Steve with various projects and planning sessions. At one point, she was in charge of paying commissions and collecting monthly reoccurring payments. Huge supporter to Steve!

Heather Moore - Heather is Brandon's wife. What a trooper. Cheerleader, support, ideas, and consulting. Huge asset to Brandon (me). Thanks Heather!

Jonathan Wells - Designer and mock-up guy. He helped to map out the system and created a number of deep mock-ups for adilas lite (fracture) projects. Great job catching the vision and putting those pieces into a visual representation. We still refer to his work when talking about fracture (future project for adilas).

Jonathan Johnson - Business consultant from Epic Enterprises. Met with Brandon and Steve in end of 2019 into 2020. Really helped us see some needs and opportunities. Later, helped Brandon with some other consulting when trying to define the fracture plan.

Calvin Chipman - Windows software developer. Calvin also did a bunch of web-based work, database stuff, label printing, and API socket stuff. Calvin was the first developer to use the adilas API's to create a native mobile app for a client. He also built a number of special developer tools used by some of our team to speed things up. He's the tool guy!

Cody Apedaile - Bryan Dayton's cousin, Cody helped with a bunch of JavaScript code and changes. He also spent some time working on the UML diagram for the adilas database. We didn't get things finished, but he was working on a new build your own interface (custom to you) for adilas. We ran out of funding. We want to get back to that project at some point.

Dave Forbis - Dave was the official "high tech gofer". He did a bunch of things. Graphics, project management, brainstorming, planning, sales, and helped with managing developers for the adilas shop. He was another great student. He came to a number of training courses and brought so much to the courses. He was also a big support to Brandon during some rough times.

Josh - There are three Josh's. Josh Wheeler, Brandon's friend and developer. Josh Sagert, developer and adilas user (worked tons on the discount engine), and Josh White, Steve's friend from California. Josh White has brought us a number of bigger leads and bigger players, like franchises, and other higher-end clients. Anything recent is Josh White, from California. He helps with networking, sales, and dreaming of new things.

Suzi Distelberg - Sales, training, and deployment. She also worked with some custom projects and doing step-by-step user guides. She has helped with all kinds of projects and even gone onsite for setups and training. Great asset!

Kelly Whyman - Kelly is Dustin's wife. Kelly was single handedly the best independent sales rep that adilas had. She did training, consulting, and sponsored a number of custom projects. Kelly helped Steve and Brandon with reports, functionality, and other things. She got so good at things, state contracts snagged her up to work at state and multi-state level stuff.

Molly Hennessy - Molly was another independent sales rep and consultant. She had numerous clients and got into doing SOP's (standard operating procedures) and other high-end documentation and training. Molly was an entrepreneur and even started creating some of her own product and services. If you search adilas on google, some of the other results are from Molly. Super creative and a great consultant.

Hamid Karbasi - Developer - He has worked with Brandon doing small websites, training, and small tasks. He currently is a manager at a retail store and brings some managerial type skills to the table. Willing to talk about concepts and how they apply to retail and other environments. He is also lightly helping with some planning for fracture.

Gene Spaulding - Friend, entrepreneur, and businessman. Gene is an old college friend. We had a number of friends in common. He has been a small mentor to me over the years. Way back, before adilas, he helped me get my first business loan for a project that I was working on.

Sharik Peck - Friend, entrepreneur, public speaker, physical therapist, and businessman. Good influence and mentor in ways. Sharik and I used to exercise together back in the day. Many of fun walk, run, and weightlifting session. Learning some conference and training skills from him and his wife. They have done really well pushing their product lines and doing some marketing. Trying to get some ideas.

Bridgerland Technical College - Use to be Bridgerland Applied Technology College. Not a person, but a huge help. This is a local technical college in the Logan, UT, area. Brandon's dad, Wayne, worked there. Tons of assets. They provided classrooms, training options, computers, and even an small incubation spot (starter office space) for the adilas shop during the startup phase. Huge asset!

McCorvey's Pro Shop - Also known as Bowling World. Client that had multiple locations. The started out with around 30 and grew up to the 90+ location level, all using adilas. Long time client.

Emerald Fields - They were the first client that wanted their own fully dedicated box and server. They had multiple locations and requested some custom code, reports, and features.

Beaver Mountain Ski School - Client that we helped them track their ski school (snow sport) lessons. Students, instructors, classes, and schedules. Custom interface dealing with elements of time and flex grid.

Bear 100 - This was the first event or annual event client that we did. They used the system for about a week each year. They had 350+ runners and their families that would be on the site for multiple days straight. It was a 100 mile running race with 13 aid stations and a small social portal for the family and friends to watch their runners. This one was special as it had custom input options to upload CSV files to populate the database vs normal HTML form field entries. Records were sent in batches from remote places to adilas for storage and race progress.

High Valley Bike Shuttle - Online ecommerce and scheduling client. They also have a cafe and small retail store. Fun online scheduling and bulk flex grid projects.

Herbo - Mike Roundtree, owner of Herbo, was the first company to do a small white label of adilas. Mike has been a great asset to Steve and the two of them have worked on projects, plans, and dreams. Herbo also has a custom payment solution that they are trying to market and get rolling. Mike has been a great supporter for years. He is also a certified CPA and that credential helps us and him. We would like to get other CPA's on board as well. Thanks Mike!

Nxtlinq AI - AI assistant. These guys really pushed us to get an AI agent inside of adilas. Tons of development took place and lots of prep stuff. We wanted to do a 3-part plan for integrating AI. 1. Teach it how to navigate using the AI quick search (check - done), 2. Teach it all things adilas. and 3. Teach it how to be clear up at the consultant type level. We only got the first phase done. Lots of other plans and such, but we ran out of funding.

Grok AI - Steve loves using Grok. He has built a number of image generation options inside of adilas. He is also working with Grok to feed it data to help with analytics and AI insight. This is not finished yet, but we may end up using Grok as an AI assistant inside of adilas. We have simple and emerging connections available right now but need to really polish things up before going live with the AI assistant options.

ChatGPT AI - We have started using ChatGPT to help with code, explanations, explore resources, planning, and help with training and flow for people and other AI bots. Currently, Brandon, Steve, Bryan, Alan, Josh, Russell, Chuck, and Wayne are using AI in either ChatGPT chat sessions or some other form of AI. We have some using Copilot, Gemini, Claude, etc. AI is actually helping in many ways. ChatGPT is a big one for use. Anyways, they are earning their place in the adilas key contributors list.

There are so many more that I can't list. Developers, users, power users, reps, consultants, trainers, clients, accountants, friends, family, and even critics. They have all helped out the idea farming process and progression. Good stuff! We couldn't have done this alone. It takes a community to do what we are doing.

Meeting with Russell and Abby. We started out and spent most of the time working on some webpage layouts and mock-ups. Working on some of our graphic skills. Russell was showing us how Grok was able to take a simple static image and create a motion animation or small movie from the single graphic. You could prompt it or just let it do its own interpretation. Kinda interesting.

After the main practice session, Abby was showing me some of her progress on some of the graphics that she is working on. Fun stuff. We are starting to break out of the box, literally, in her designs. She is making great progress. We will be meeting tomorrow again, as we ran out of time.

Good meeting with Steve. We went over tons of different things. Here are some of my notes.

- Fixing the Grok AI Agent. It is available but not yet trained. We have it hooked up, but hidden... Just us can play with it right now. It will be an ongoing project. We made it so that we could push it up live but, once again, no one knows about it and we don't want them to know about it yet. Steve wanted it to show some people that there is some potential (seeding the discussion).

- Lots of talk about sales and generating revenue. Steve wants to work with people who are willing to talk to anyone and then when they want a demo, he and Sean can step in. He doesn't want to train them on everything, just a simple salesperson who can generate leads. He wants our team to do the demos.

- Steve was asking about Alan. We jumped in and looked around at both the system (timecards) and bit bucket. I reported that I had met with him and it was a great meeting.

- We talked about adilas and expectations. There are a lot of undefined rules and assumptions. We are planning on refining some of that as we go. It just is what it is right now.

- Steve is doing tons of small mini projects for Cory. He is really busy doing all of the little things. I would say he is getting buried. I have been there so many time. I feel for him.

- We talked about a couple of possible partners and outside businesses that have expressed interest in what we are doing. Currently, there seems to be lots of demands and not much show of support so far. It is just starting out, and we aren't sure where it is going. We want the leads, the customers, and the work, but so far, it hasn't really produced.

- We are trying not to waste time and energy, but we really don't know where to go. We are basically, trying to follow the money. Picking up the pieces.

- Steve and I talked about options in sales and also trimming down our current team. We have to cut some costs. It is rough sometimes.

- We spent some time talking about payment processing and how they do their billing. They, the payment processors, usually do a percentage of the monthly credit card sales. We would like to do something similar but instead of doing just the credit card processing, we would like to do a small percentage of the total sales per month. We are thinking from 1% to 1/2 of a percent. Somewhere in there. Trying to figure that out.

- Steve was talking about robots and even payment processing is becoming more automated and even mobile. He was talking about advancements in robots and other technologies. He reads a lot and likes to keep up on that stuff.

- We would like to get our Grok AI agent up and working. We feel that we may be able to control that better than having an outside party program and control it. That is still a lot of work. Steve really feels like if we don't embrace the full AI wave, we will be left behind.

- Bryan popped in for a minute. I told him that I would text him when we were done. We were spoused to meet but Steve and I got started late.

- Bryan is working with some CPA's and trying to get them to see the vision of what we are doing. Long ago, that was Steve's vision. He wanted to fly around in his plane (he's a pilot) and go see all of the CPA's and show them how adilas works. Funny but cool, old memory. Still a possibility.

- Steve has been around a lot of salespeople. He was sharing some of his experiences. We need people in places where there are a lot of other people (businesses). We don't have anything right now, as far as a salesperson or a sales team.

- Sales is just a game of numbers. You also have to be willing to be told no. Not all personality types can do that. Steve was mentioning that we have started a bunch of people but they haven't worked out. This may not go here, but I'm going to add it in anyways. Steve and I were talking on Monday, 1/12/26. I had a meeting later on Thursday, 1/15/26, with Shannon. She made an interesting observation. We used to have a rep type model, where the rep, an independent, would go pedal and push our product. They would then get a commission and also be able to get monies directly from the client to help with anything that the client needed. That was very successful. They, the reps, would max out and eventually stop, but each one could handle a certain number of clients. We had some reps that were making great money. Because it wasn't super organized, we decided to pull that back internally. Due to budgets, we have not been able to fill that same role that those reps were providing. We have way more control over what is being done, but we don't have anybody out there pushing on things. Interesting observation.

- Back to the meeting with Steve. After we talked about sales for the first little bit, I changed gears and did a mini pitch to Steve about focusing on people and trying to stabilize the team. That conversation always comes back to funding and where do you get the money from? This has been a common theme over the years.

- I was drawing and showing some ideas. We have focused on features and functionality so much. We keep building lists and slowly clicking through things. I really feel like we need to change the focus to people and the team vs the next cool thing. The sad part is, we have done this for years and years and years. We keep thinking, when we get such and such done, it will all get better. We get to that point and then there is always something more. I honestly can't even see the end of what is wanted (feature or functionality wise). It feels like a perpetual or ongoing list of wishes and demands.

- We jumped in the system and were looking at sales, numbers, trends, year over year totals, etc.

- We may want to allow the developers to go back and bid (put out estimates) on custom code projects. That's what they used to do, back in the day. We tried to pull that all under the main adilas roof as well. That was super expensive. We may need to figure out a hybrid and see if we can make that work. We don't want a full wild west again, but we may need to bring some of the independent pieces back in. It just costs too much for us to fully support a full staff of full time developers. We'll figure it out.

- Our costs are around 40% (roughly). So, if you had a system sell for $100. We would use $40 to pay for servers and other small things. The other $60 would be profit that could be split and/or divided to create some sort of incentive. Steve is trying to see if he can get anybody to play that way. We just have to get more clients. He was pitching a 50/50 split of the profit. So, for a $100 deal, that would be $40 overhead (costs), then split $60/2 or $30 per entity that is helping with the sale.

- We were talking about setup, activation, and selling systems. We are seeing a growing demand for enterprise level functionality. They, our clients, just expect us to have it all built. They really want it, but it is only partially done, not all the way yet. We end up getting stuck in the middle, footing the bill, and not being able to just sell what they want. We already have vendors, customers, and items on the enterprise level. We just need so much more. Well, you have to start somewhere.

- Steve was talking about 10 free hours of training and then rolling into $65 per hour after that. We can help with anything that is needed, whether that be training, data entry, bank reconciliation, inventory help, balance sheet and accounting work, etc. We offer a lot of services. Basically, what do you need? We can help.

- Steve wants to find some power users and see if they would like to work for us. We have had great success by hiring people who were once adilas users and then bringing them in and onto our team. They already know and love adilas. They tend to find a good home with us. It just comes down to budgets again.

- As we were talking... I was pitching things and it kept getting met by something like... We've tried that... We need to do something different. I don't feel like that. If we did try things, the timing may have been off, the wrong person, or it wasn't really tried. I don't want to just keep randomly trying things. I think we need to focus on people, talents, skills, and personalities. If we can get the right people in the right places, and get them trained and supported, it will work. I know it!

- We may need to try things again! Lots of things are changing and been changing over the years. We have been doing this since 2001. Adilas became a real entity in 2008. We need to circle back around and focus on people.

- The topic switched to AI. Steve wants us to use AI to build code for us. He thinks that we can reduce our tech needs by 60%. He uses it tons and tons. I use it as well. We want to get our other developers up and going on it. It's not that they aren't... we just need to keep going. We need to look at it as a tool, not the only answer. It does have pros and cons. It definitely has its place. Certain things still need the human touch.

- We ended our meeting by him telling me that I could look around and work on a plan and then bring it back to him. We have to make some changes. That is for sure. I just don't want to randomly do things that may hurt us in the long run. It takes me so long to train new people. I hate to see them just go away. We have a team, but yes, they are kinda tired. We have been running hard for years and years, almost without any breaks. That is rough. We will figure it out. That's the new goal. Figure out how to make this work and stabilize the team.

Spent the first 2.5 hours working on the Grok AI agent and getting things tied in there. We are just starting out there and tiptoeing through that process. We are using Grok as the AI agent, for this new one, and then using ChatGPT to help us know how to code the stuff for Grok. Kinda funny. Anyways, we had a great session. We were in deep rewriting code. We were asking all kinds of questions and testing those changes that we were making. I was happy with the session.

The last half an hour, we were looking at the code from Alan and the new CardPointe stuff. We need some new code and changes but were not sure of the status of that project. We looked at his branch and poked around for a bit. I will give him a call. He and his wife recently had a new little girl. I imagine that he has been completely pulled into that mix (life in general).

Meeting with Steve. He is working with Grok and ChatGPT to help him code some things. One of his projects is working on some ecommerce sales by category specific settings. We flipped over to working on the Grok AI chat bot inside of adilas. We setup a scratch file and were working with it to see what the responses were. We changed some paths and did some light debugging. Our next joint session will be again on Thursday afternoon. He may work on it as he gets time. I pushed up all of the changes to his branch inside of bit bucket.

At the end of the session, we were chatting about other developers and other projects. Light catch-up stuff.

Emails and recording notes from last week. Research on JavaScript fetch commands and looking over code from Steve's Grok AI agent project.

Working with Steve on his Grok AI agent. We had to play around with it and get into the JavaScript stuff. He is going to push his branch up and I'm going to pull it and play around with it. We started getting deep in the weeds. I really need to play with it locally to get it going and connected. He is making great progress. I'm impressed.

Meeting with Steve. We spent some time talking about the mini private AI agent. We logged into the Nxtlinq backend and were looking at their context window. Josh jumped on for a little bit. Steve and I were making plans and talking about things. Where do we want to go and how are we going to get there?

We talked about some global context pieces and what we are hoping for. We would love the AI agent to help us with some videos, running comparisons, drawing (whiteboards what to do).

Steve has a couple of other projects going on right now. We flipped over to them and went through them for a bit. We talked about three other projects and went over some questions that he has. One of the projects is that Steve had questions about using Grok AI as an AI agent. We talked about getting new session variables on the login, logout, change corp, 3rd party solutions, footers, and sdk's files or pages.

Next, we flipped over to a small project that is dealing with ecommerce and part category settings. Currently, we have a setting that allows for a corporation or entity to select a sales mode. These are inventory level controls like show and sell parent inventory, show parents and sell subs, show sub and sell subs, etc. All of these are dealing with parent/child relationships within the inventory itself. Steve is working on a new setting that will allow that bigger master switch to be controlled on the part category level. Some categories tend more toward child or sub inventory than other ones. Anyways, he is working on changing out that master switch and making it more granular at the part/item category level.

The last project that he is working on is saving a custom report from inside the system. The new report has both normal FORM scope params as well as dynamic, on the fly params. We went over some options and did some comparing of the FORM scope values. It goes something like this... We use a normal web-based form to pull the report. At that point, we have all of the FORM scope values or variables. If the user wants to save the report, we send all of the data over to a save report page that putts all of that information into a JSON object for database storage. We then take the new database id number and use it as a URL scope variable. Basically, run report X based on the settings stored by id number Y. It works pretty slick. We have done this for years and years. This particular one has some other random dynamics that are making it a little bit more difficult. We are not sure, but it seems to be a case sensitive problem with what is being created (dynamic FORM values) and what is being saved in JSON format. We didn't quite finish this, but were getting close.

Quick phone call with Steve. He is going to try to use Grok to do an AI agent. We are just experimenting. Working on new global context table inside of adilas to help with AI global context stuff.

Meeting with Steve over the GoToMeeting session. Going over agentic tool calling. He has been doing some research on both Grok and ChatGPT on how to setup or use our own AI agent. Talking about helping it to have its own memory by building in new tools and our own database to help with context and storage. Until we have that new database built, we will use the help file database. Tons of capacity there.

Emails. Paying bills and reading information from Steve working with Grok (AI) about the adilas AI model (Adi). He sent some texts around with some new features that were being highlighted based on AI going over our news and updates section. More emails.

Working with Shannon. I was showing her the expanded AI quick search options. That was kinda fun. So much potential there. Talking about what we can harness..., quickly and efficiently. We then read over the overview of the adilas lite - Fracture project - this was what Steve got back from Grok. Shannon took some notes.

These are notes from Shannon: Brandon reading the AI summary of Adilas Lite:

- Project overview hub - Adilas ecosystem

- Ambitious roadmap for next generation SaaS map

- Clean, modular, teaser, further explanation

- Solid, forward thinking, scaling Adilas from ERP to community

- Flexible, customizable, modularity, user centric - following SaaS trends

- Technical depth and community

- A vibrant hub for

- Teaser heavy - would like to see more visuals, demos, things to make it more engaging

- Grow into a dynamic dashboard overtime

- Jellyfish model and jellyfish analogy - adaptable and fluid, recurring revenue with add-ons - monetize ecosystems, rapid scaling if the core offering hooks users

- Value Add-On Core model - technical meat, starting at transactional data to unlimited, scalable at a level people can understand

- Adilas University - essential for adoption, helping growing community, build loyalty, include gamification/certification it could be even better

- Adilas Marketplace - huge potential for revenue drive and ecosystem builder, success depend on curation to avoid quality issues

- Adilas Cafe & Communities - slack-like portal, one-stop shop, broaden the appeal beyond users, social features - a community first brand

- Adilas Lite - Fracture - the crown jewel, rebuilding with new code, toggle on/off - this screams user empowerment... a lot of other great things!!!! - could separate Adilas from other more rigid Sap and Oracle

- Other Business Plans - lots of other great things that I didn’t get recorded - got caught up in listening to these last two - lite and other plans

- Adilas Videos & Research - transparency, keep community invested, ties things together, road maps could be invaluable for developers eyeing integration

- Vision - building a sustainable interconnected world around it

- Improve - more interactive elements, make it live and searchable,

After doing this, we then switched over to building new content for the adilas cafe page. Working on sub content. Good session.

Working with Steve on a custom ecommerce shopping cart. He is working on selling sub inventory by choosing a sub package to purchase. He had a bunch of code from Grok (AI stuff), and we had to back most of it out. We did it the old fashion way and got it all working. Not that the code was bad from AI but it didn't fit into our page flow. Anyways, we got it all fixed up and good to go. Steve is going to keep tweaking on his code, but we got the main task done and accomplished. Good work session.

Looking into a slow query for sub inventory and sub inventory attributes. Steve sent me an email with some ideas from Grok AI. Looking into what we need to do to make things faster or more usable. Poking around and reading over code. Did a few global searches to see what pages use what. Mostly just trying to figure out what it does and how it is used. Kinda deep logic (loops, sub queries, grouping, queries of queries, dynamic union output from multiple table sources).

Email to Steve about a big AI response for one of his queries and methods. He was asking Grok AI some questions and wanted me to review his decisions, output, and suggestions. The AI response was quite deep and impressive. I sent back an email with a few comments and small changes. I was very impressed with how deep the AI response and suggestions were. Interesting.

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.

Started reading over brainstorming notes from last Friday. Steve joined the meeting, and we were talking about AI and doing AI data analysis. He was showing me some of his new AI stuff that he is playing with. Very interesting. Going over prompts (what AI needs to do its stuff) and even asking it what a better prompt would be. The key in in the prompts... Steve was asking it (Grok), how to do better prompts and what it is looking for. Great ideas. We spent some time looking around and then talking about where and how to use it, meaning AI options.