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.

Recording notes from last week. Tying things together. Read a bio from a guy by the name of Andrew. He seems to be a developer, entrepreneur, and ecosystem level thinker. Sounds cool! I have an email and a text message out to him. This is a contact from Steve.

Phone call with Josh. He wants some help doing developer work for potential clients. They, Josh, Cory, Steve, and Eric have been doing some fun projects. Lots of look and feel, email campaigns, and new ecommerce skins. He has some potential clients lined up, just needs to fix certain things. He was asking me where I'm at with things. I'm off the side of the bus (not with everybody else). He wants me to work with Steve and the crew on development projects that need to be done. I'm trying to do some planning and working with ChatGPT (AI) to help line out the master plan stuff. We have never had that, meaning a master plan. I'm not trying to get it, the master plan, too detailed, but we need it. I feel that it is very important. We will always have more projects and development work. To me, it's just another checkbox and/or request. We have tons of those, meaning checkboxes, done and pushed out. Just for fun, here is a link to a 50-page document, just with features inside of adilas.

It's not just planning, I'm circling back around, finishing things up, reinforcing the foundation, and refining things. I'm trying to simplify things, make it easier to understand, explore new avenues, use AI to help us get rid of the rub and/or friction. Tons of things. In sales we talk about features, advantages, and benefits. We have the feature part down... We need to circle back around and make sure that we can show the advantages and the benefits. Some of that is look and feel and some of that is flow and simplicity. Just as a sample, here is an element of time entry that shows some of what we are doing and how we can harvest these AI conversations to help show the simplicity of what we are really trying to do. See EOT # 12793 in the shop. This entry has four new documents that are super easy to read, yet tell a huge amount of what we do and offer. We are working on graphics, help files, documentation, etc. We tend to go so quickly, that we don't put the finish on it.

One of the biggest things that people complain about is what it looks like (look and feel of the UI). We have great tech and functionality. We need to circle around and put that finish on our product that people are looking for. I love it, and I totally see it. There is nothing wrong with what he, Josh, is asking. I also know that it takes major resources to do all of that. I really want to see if we can get some investors to help us with some gas money, help us along the path. We have put every extra cent into this project that we could and/or can. That is awesome, but it is also taxing.

Josh recommended that I call Steve and see what he needs help with. I just know if I do that, I'm back in the mix of going a million miles an hour without a plan. We joke about it, but there is some reality to the situation, we are hanging on the car or train as it is going down the road and/or train tracks. We are working on it while it is going, making corners, going up/down hills, etc. In real life, the plan is - just follow the money, but then it never ends and you don't know where you are going. It starts getting complicated. Everything has to keep going and connect to tell the story. I really feel like me not being on the train is important right now. I don't know the timing of everything. We'll get it all figured out.

After we got done talking, it took me a couple of hours to get back on level ground. I think that I have some mental anxiety about where things are at right now and where things are going. I've been in this battle (the adilas project) for 20+ years. I've been burned out and reanimated a number of times. It's a repeating cycle. It has been pretty stressful. I really want to see it succeed, but the current demands are saying, jump right back in at full speed. I need to be on the outside right now, if for nothing else, for my mental wellbeing. I'm working on other parts of the system. There will be great ROI (return on investment) of what I am doing, it just may not be super visible right now. I know that it is going to help.

Working with Shannon on help files and defining parts of the interactive map. We put in a whole new intro section and started moving some of the numbered sections around. Overall, a good session. Here are a few notes for me...

- Go back to October 2010. I was planning things out and trying to figure out where things fit together. There are a bunch of brainstorming documents that deal with what are the topics, what is the scope of each topic, how does it play into operations, how does it play into accounting, and who are it's buddies. That brainstorming session, over days and days, was the initial catalysis for the adilas interactive map. Specifically, we were planning and mapping out how the balance sheet fully works. Here is a link to that info: October 2010 in the developer's notebook.

- It feels like we are slowly coming up the chain... This is an analogy with food and baking/cooking, but it has similar things that have happened with how we pitch and promote adilas. We started out talking about the ingredients, then moving up to the functions of things that you can do, and finally getting to the results and/or what you can create. So, in food, ingredients are things like milk, sugar, flour, butter, salt, eggs, etc. Functions are things like baking, cooking, boiling, mixing, frying, roasting, chilling, freezing, thawing, etc. The outcomes and/or results are things like pies, cakes, cookies, brownies, cinnamon rolls, ice cream, smoothies, etc. This is what people really want.

- In the adilas world, the ingredients are things like invoices, quotes, inventory items, customers, vendors, PO's, expense/receipts, banks, deposits, etc. The functions are thing like POS (point of sale) systems, CRM (customer relationship management), CMS (content management systems), ERP (enterprise resource planning), accounting, inventory management, etc. The outcomes and/or results are peace of mind, clarity, trust in your numbers and the story that you are getting, being able to make decisions, gaining visibility, accountability, business intelligence (BI), digital storytelling, confidence, etc. We are wanting to get there... to the outcomes and/or results. We are only now seeing that we have been spending all of our time telling people that we have invoices and customers or we can do POS mixed with CRM stuff. We haven't quite gotten to the part that people really want. That's where we are heading.

- This little analogy about cooking and baking as compared to adilas business platform and system tools (see above) could be a super fun graphic. We are learning and we need to show what is really possible. In Steve's words, we need to sell the sizzle, not the steak.

Phone call with Steve. We had to play a little bit of phone tag, due to connections. Once we got connected, we had a good conversation. The main things that we were talking about were dealing with removing friction and rub on the client side of the equation. Making things easier and easier. We talked briefly spoke about some current projects like Metrc updates, merchant processing, and CardPointe and Clover server issues and threading. Here are some of my other notes:

- One of Steve's biggest goals is to get AI fully integrated into the adilas system. Almost to the point of a simple chat-based system that could handle and process natural language and then be able to help the user do anything inside of the adilas system. Not just navigation, education, training, and consulting, but actual physical tasks. Instead of clicking buttons, navigating, and running reports, you could just talk with the system, and it would be able to help you. That is one of his main goals. It may take some steps to get there, but a cool vision.

- Along with the idea above, of a system that could do anything (AI super system), he was talking about a flow process like this... From left to right... Something comes in, it could be a bill, receiving inventory, doing a sales transaction, whatever... The middle would be the chat window and super simple interface (almost nothing structured). You tell the system what you want to do and it helps you do it. If it needs more information, it would just prompt you and help hold your hand. Then on the right, or the output window, you could get your results and/or confirmation that the task was completed. The results don't even have to be reports that we have programmed. It, the output and/or results, could flex, based on what was asked and/or being worked on.

- I was expressing that I liked the idea, and I could see how it could really help in some situations. This is just me, but I don't think that every person wants that. Yes, it could be an awesome option and could speed certain things up. However, if it was a repeated process, that would be a pain to keep telling it what to do. It might take longer to explain it than it would to click two quick buttons (from a pre-built interface). There are a lot of assumptions being made. One, it (AI) would have to have a super deep knowledge of the system and all of its possibilities. Someone would have to help set things up. We would need to record those instructions in order to repeat those processes. Things change as time goes by, someone would have to be able to edit things, etc. We would also want it to keep learning on the fly. Technically, each person, even across the same business, would have specific needs.

- Without being a "Debbie Downer", I could see something like this being possible as a phase 4 or 5 of working with the AI agents. Phase 1 would be integration and doing simple existing navigation and use of tools. Phase 2 would include education and training on existing pieces. Phase 3 could be where we start letting the AI agent have access to raw data through API's and special AI tooling. Phase 4 we would have to introduce ways of creating some kind of assembly or package for the AI agent to follow (recipe/build type mentality). Then maybe a phase 5 where the system is trained and enabled to help with all kinds of stuff. This could be super deep. Say a person has a picture of something. Do they want to enter it into the system, store info, check something off, etc. It's a little too open right now. This is my take on it... but it would have to be a phase 5 ish type thing.

- As Steve and I were talking, we were talking about AI, bots, robots, agents, etc. Steve was saying that they are all combining into just the AI (artificial intelligence). The words bots, agents, etc. may go away. They are somewhat merging (lines are blurring). There is some mixing going on.

- I loved his ideas on helping our clients get rid of heavy learning curves, manuals, processes, etc. Decrease the friction and the rub. I love that. It just takes time and money and development (and a plan) to get there.

- We talked about the fact that some (most) people don't want to watch a hundred videos or read a huge, big user guide. They want it to be easy.

- Some of what we were talking about might even be the next steps (future) beyond the value add-on core model and/or the fracture UI buildout.

- Trying to listen to what our clients are saying and telling us. That is important. This came from Russell, long ago - Our clients want something that is easy, powerful, and looks nice. If they can get those three things, it will sell.

- I wanted to record these ideas... part of the idea farming stuff that we are doing. We record things, plant them in the ground (sit on them or think about them), and then finally roll around to see if we can make something out of the ideas. Ideally, we get more and more activity on certain things and that helps us know what is being asked for and/or required. Fun process, but it does take time and feedback loops (over and over again).

- For me, when I got home, I scribbled down some notes and drew some funnels, mixing of tools, and even possible stacked or reverse funnels. All of this deals with getting something, mixing it together, using possible tools, and then getting an output (of some sort). Sometimes, once you get an output or result, you have to remix it or send it through another funnel to get what you really want. Break it down, transform it, summarize it, expand it, or whatever... some kind of action to either pull, mix, create, and/or alter something. As a note for me, I have some old graphics that I was working on back when I was doing some developer intern training. These guys had to produce something (desired output or a result), but the starting spot varied. They could use tools and then produce the desired output. I might tie back into that concept.

- Dealing with the concepts for the developers (listed above - inputs, funnels, mixing, blending, and getting outputs). I found some of the old entries. They were in 2/14/2015 and then again on 3/6/2015. If you want, check out these entries and look at the image galleries for expanded visuals. I also added some of the old handwritten notes and scans to this element of time. These entries also include some concepting on the 3D calendar. All playing through around the same time. Kinda fun. Enjoy!

Research on the data assembly line, new school accounting, and 3D levels. Found a bunch of old entries that Shannon and I were working on for the user guide. See section 11, for concepts on financials and accounting. Here are a number of links to show where some of the information is.

General adilas notes from back in 2008. This is when Brandon and Steve were working on the balance sheet. This is when the concept of allowing the data to flex until everything is correct or back to a stable spot. Web link - developer's notebook - balance sheet stuff in 2008

Writing out the progression of what we have learned thus far. These entries go forward from 2008 to the end of 2014. These are some notes from Brandon while helping to train some new interns and developers who were helping on the adilas project. These notes will be shown in two sections. One is the general notes from October of 2014. They will show the general flavor of what is going on at this time in history. The other notes will be specifically 10/14/14 where the actual entries hit the developer's notebook. Here are those links:

Web link - October 2014 - General developer's notebook for the month of October 2014.

Web link - time_web_gallery.cfm?corp=371&id=2894 - Specific date in time when the concepts first hit the notebook as a single entry. Progression of operations and accounting.

The next major time period was in March of 2015. This was a different set of developers that had questions and wanted to see how operations and accounting played together. This will have two sections as well. This will have the month of March 2015 and then a specific time when the process was described in more detail, with a slightly different flow, which helped in presenting the ideas. Here are those links:

Web link - March 2015 - General developer's notebook for March 2015

Web link - time_web_gallery.cfm?corp=371&id=3618 - Specific date when the process was explained using a giant Whiteboard at Bridgerland Technical College.

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.

Phone call with Steve. We were talking about the current load and how much is going on. It's hard to keep up. Steve is feeling pretty overwhelmed. He and the other team members are running the ship while I am off on the side trying to work on plans and investor stuff. It's pretty rough. There is also some underlying tension from a miscommunication and overstep on my part. See EOT # 12731 for some back story.

Here are some of my notes from the meeting with Steve:

- We started out and I read a post-it note full of some things that I think Steve has issues with - my personality traits. See attached, if you want for the post-it note. We are all working hard, but we have different opinions on what will help and where to focus. Similar but also somewhat different directions. Neither one is bad, just different approaches.

- He is busy taking care of business and paying clients. He is trying to only work on funded projects and projects that have ROI (return on investment).

- Trying to fill in the blanks (needs of whatever is needed).

- Steve is shooting for full AI projects - code, planning, fixes, etc. Steve is heavily leaning on AI as the backup or fallback. He is totally going in the AI direction for as much as he can.

- He showed me a small website that a guy built using just AI. Here's the link. I pulled it up. It looks great. It is pretty impressive. It doesn't have any real content, just a shell, but it looks amazing. We talked and chatted about that for a while. There is some fear that some of these guys are going to take over and build what we have built over the last 20+ years. Basically, a question of what is stopping them from taking the next step and building it out on their own? I see it, what we have and offer, as way deeper than that, but there is some worry and unknowns.

- He is seeing or thinking that people don't want any real interface... they just want a simple chat type interface and AI will do everything for them. I was telling him that our full interface and existing pieces need to still be there. There is value there. It is nice to be able to do anything that you want (say an AI chat window), but there are also times and places for a quick and easy button or link. We need both. Our interface is not our real product.

- We talked about how Wayne is working with some AI agents to work on the database and some database updates.

- Steve is feeling a little bit of panic mode. He watches and reads a lot of tech news. Huge changes are happening all around us.

- Only working on funded projects.

- Relying on Craig for all money type decisions (controller level control for funds).

- There is an urgency to what we are doing.

- AI is going so fast, it is scary. He is scared.

- Small talk about IP (intellectual property) and how we can't stop AI. If they want to do something, they can just do it, change it a bit, and run with it.

- He wants me to look into complex binary (tech stuff). He is planning on doing some more research there. Basically, skipping the code and going right to binary level commands.

- Brief talk about how people interact with things. He was saying that people don't want to do any data entry. They just want the AI agent or system to do it. Something like this, I have a document, I upload it, I then have the AI agent enter it into the system. Thanks, all done. AI does it all. As a side note, there may be some automation things that we can do, but don't think that everything will be like that.

- Talking about taking care of the business right in front of us. I don't deny that... and I know that there is a need there. We have been doing that for the past 20+ years. It is also a small trap, in some ways. It keeps us from breaking out of our form or container. We are somewhat maxing out our current model.

- If you read between the lines, he and the team are busy, with paying clients. There is a demand for what we are doing.

- We finished up the meeting, and he was going to go jump into another project that is needed. He is working super hard. He is trying to fill in the gaps as best as he can. I'm super grateful for that.

- After the meeting, I was talking with Heather (my wife). We were talking about an analogy of a malt shop or ice cream shop. Say you have a line out the door, small rush, tables need to be wiped, and dishes need to be done. Everybody is busting their buts, except for one guy in the back who is dreaming of a better way to do it. That doesn't fly very well. Sad to say, I'm that guy. I'm not trying to hurt anybody, and what I am doing is super important, it just gets judged pretty harshly. I fully understand. I have been in there busting my but as well, for years and years. I just know that there is a better way. The story above changes when you say, this small rush has been going on for years and years. We have all been pushing on things. It is not just one night, where things get busy. That longer timeframe makes a big difference.

- Tying this back to adilas (above ice cream shop analogy). We offer custom code. That is awesome and totally part of our model. However, we get so tied up in doing custom code that we can't finish what we really need to. We end up getting stuck in that scenario, kinda like the malt shop. There is a balance. You have to have the money to keep going, and that is super important (work right in front of you). You also need to look to the future as well. I heard a guy say one time, there is a difference between working in your business and working on your business. We need both. It's a fine line and tough balance.

Meeting with Dennis. I told him where we are at as far as readiness and that we should have a decision for him in a week. He wants to help us do some go to market planning and readiness stuff. I really think that it will help. Here are some notes from our quick meeting:

- If I am pitching the idea to Steve, show him the savings and the benefits of what we are planning on doing.

- He was asking, I have to think that something is wrong with the model or the business if you are stuck at a certain revenue amount per year. How can we help you break past that number or value?

- We are a business support service entity - his terminology for what we do.

- At some point, we may really want some outside help and opinions (consulting and ideas).

- Light talks about the contribution margin of each customer, each employee/owner, and each service that we provide. Really looking at the data behind the numbers.

- Sometimes you have to take a step back to see what is really going on.

Talking with Alan about projects and AI use cases. We spent some time talking and going over things. We showed each other some of what we are doing. Alan is working on multi-threaded stuff for merchant processing different gateways. I have been working on some pricing structures for the main adilas website.

Jumped on the meeting with Shannon. Only had time for just a quick hello and how are you doing. I got a phone call from Steve. I told Shannon that we would need to reschedule. Then working with the banks to reverse a draw on the line of credit. Multiple phone calls, emails, etc.

Phone call, texts, emails, and signing up for a line of credit with a company. We already have one (a line of credit), but this was a better deal. Small switch-a-roo on some light funding.

/////
Some new notes added on 3/10/26 - the rest of the story...

Small back story. I got an email from a business funding company (cold email, no prior connection). This was early to mid-February of 2026. I was actively looking for some business funding and investor type deals. I replied that we weren't interested in any loans, but we were looking to do a capital raise. I sent him a link to the investment options for adilas. The guy got back to me, we chatted, he said that he had a supervisor that dealt with investment type stuff. Anyways, the guy ended up giving me a number of leads of either banks and/or investor type people. We went through a number of possible options. Pretty good leads.

At one point, I texted the guy and asked him if he would ever work on commission to help sell adilas or get a commission if he helped with a capital raise. He replied back that he was on salary but thanks for the offer. We aren't buddies, but he was actively pushing on things. Cheers to him. I was impressed.

It's now Friday, 2/27/26. Multiple weeks have gone by, dealing with the guy and some of his leads. I have them all documented in the developer's notebook. There were some loan options, line of credit options, etc.

On Fridays, I am normally up at the local ski resort. I'm a snowboard instructor and have been since 1995 (long time). I go up every Friday. Anyways, I taught a 2-hour private lesson, made a number of runs on my own, and stopped for lunch. I decided that I had a ton to do back home, so I took off early to head back to town. When I got back into cell service, I saw a text from this guy. Super simple, give me a call when you can. I then gave him a call. He had another lead for me. Nothing new, similar to what he had already done. The guy said that he could beat our current line of credit. He then asked if I was interested? I said yes, I was interested in seeing what he could do and how they could beat the current rates. The goal was just to see what he had to offer.

Back a couple of weeks ago, I had to provide them some bank statements to meet with one of the guys. That is pretty common, no big deal. That's how the banks see what you can qualify for. At that point, they were trying to see what we would qualify if we got a loan. I had looked up the company, and it was totally legit. Anyways, I get connected with this other guy, some sort of an admin/supervisor who worked with this other guy. They were calling and texting me and seeing I was interested in using them, instead of our existing line of credit. Our other line of credit had a huge interest rate, so I was interested in checking it out.

All of the sudden, if felt like that, they were offering me a line of credit, and I could get it today (start the draw and funds would hit our bank in a couple of day). I think that they were trying to close some things before the end of the month (fill out some sales goals - last Friday in Feb). I just had to do a pull or a draw on the line in order to set it up. I had enough time, in between other things that I was doing, to look up what else we owed and how we might be able to use this small advance on the line of credit to wipe out other debt (debt consolidation) and even get some to help moving forward (lube the wheel). That was the goal. This could work out slick.

My bad, I did not communicate with Steve or anybody else on the team. I signed on the deal and requested a draw on the line. This whole thing, just sort of fell into my lap. It seemed like a great deal, I was looking for something like this, I had already had numerous interactions with this guy, and it felt good. It was just my name on the line of credit, and I really thought that it could help. So, I did it.

Fast forward to Monday, 3/2/26. I sent a text to both Steve and Craig that a large amount may be showing up in the bank and that I would get them some more information. By end of day on Monday, the amount had showed up in the bank. I then wrote an email to both Steve and Craig Monday night about what it was for and my plans. The email went out late on Monday night. Once again, my fault, and no or minimum communication. By early Tuesday morning, excuse my language, but all hell had broken lose. Emails were sent, texts were sent, and a cussing and screaming phone call had taken place by around 10 am on Tuesday morning.

On the banking and funding side of things, we had to stop things, back things out, and do a lot of phone calling and talking with banks and the financial institution that had given us the line of credit. It turned into a crazy mess. It got really ugly.

It is now just over a week later, and things are kinda calming down. My bad, I overstepped my bounds. It caused a ton of stress, bad feelings, pressure, cause and effect decisions, etc. I did not communicate. I know that. I was honestly trying to help.

Multiple sessions working with ChatGPT on adilas pricing structures and such. Getting help with prices, plans, add-on's, and other options. Shannon and I started the session earlier this morning. I then did multiple other sessions throughout the evening to finish up. We had left out activations, setups, 3rd party solutions, and other industry specific stuff. We also added in some notes to help us account for upcoming changes to the adilas value add-on core model, adilas marketplace, and the adilas cafe. All part of the new future and where we are headed.

Steve challenged me to work with ChatGPT to actually build out small samples and pages. We went through three different versions. Once we finished, I sent an email out to Chuck (designer) with the temp files and instructions. ChatGPT was very helpful. Recording some notes from the day.

Here is the full chat link of our session - 5-6 hours in total - https://chatgpt.com/share/69a0a070-3778-8007-a998-ebf29c864809

Reviewing some how to videos on the TechSmith website. This is for a product called Snagit. We are going to be doing some screen capture stuff. Emails and recording notes. Light review of what Steve has been working on. He is really pushing hard on some dashboards and lots of AI integrations. Good stuff. Fixing some old images on the steps to success pages. Small CSS changes. We haven't touched that section for over 10 years. We just get busy doing other things. I'm going to be circling back around to that part of the site. It will get a major overhaul, but we are heading back to that section.

Spent an hour fixing the developer's notebook. Changed a bunch of navigation links into buttons and added a little bit of JavaScript to show/hide the main search criteria form. Other small changes.

Phone call with Steve and then a phone call with Bryan. The main subjects were dealing with pricing and how to help figure things out. Here are my notes.

- Pricing has always been a crazy battle.

- Steve, Josh, and Bryan have been working on some ideas for pricing.

- Bryan was running things through AI (ChatGPT). Here is a small summary of what it recommended. As a note, Bryan sent me a file with more of the chat messages and prompts.

----

Adilas Pricing Summary

Monthly Software Fee "Unlike flat monthly fees that hit hardest when times are tough, Adilas scales with your business-low when revenue is low, and never punishes success."

- 0.4% of gross revenue

- Minimum: $59 per month

- For multiple businesses or monthly revenue over $150,000: Please contact us for a custom quote

Setup & Training (One-Time Fee)

- $300 - Includes 5 hours of system activation and personalized training

- $500 - Includes 10 hours of system activation and personalized training

- Hours are tailored to your needs. Most clients are fully operational within the included setup hours.

Additional Services

- Ongoing training: $65/hour

- Custom development & integrations: $100/hour

----

- As we use more AI stuff, we and/or our clients, may be charged more for tokens and token usage. Currently free, but that may increase as we go. We will monitor the tokens.

- Steve was saying that Josh has been pitching the enterprise system, for up to 10 entities, at $2,500/month.

- Some of our competition makes money on the credit card processing. We don't really care what merchant processing company they use.

- Steve was talking about a potential client that has a consignment type location. He was talking about a pricing model per booth or per sub section of the consignment store.

- The per location question always comes into play.

- We need to set some minimums.

- It seems like the sweet spot is a business that does between $40K to $100K per month in gross revenue.

- Pricing is confusing and totally depends on the model, the vertical, the complexity of the client, and expectations.

- We like to talk to the person... It helps us read the person and what they are feeling and looking for.

- Steve and I talked a lot about showing them the value of what they are getting. Josh has been pushing on that as well.

- We were talking about some folks wanting to do their own coding using AI.

- We offer all kinds of managed services, including training, setup, deployment, data entry, fractional bookkeeping, etc.

- Most system are just a POS (point of sale) - adilas is so much more. Often people are comparing prices of what we offer to someone else who is just offering the POS part of the puzzle.

- We should probably be compared to ERP pricing, but that sometime puts it completely out of range for the smaller guys, smaller clients, and companies.

- Steve and I were talking about impressions. He kept saying, we are not trying to give them any impression. People will form an impression, either way. In a way, we don't know how to brand or pitch ourselves.

- Maybe come up with some categories of pricing and let the clients see where they fit. In a way, how do you (as a client) want to be priced? Percentage, fixed price, per vertical, per location, etc. - Not sure.

- Being on the street. I was proposing things and Steve was saying, that's all great, but you need to be out on the street and see how that is received. I was pitching for higher prices.

- Walking a mile in someone else's shoes - you'll get the idea and figure out where they are coming from.

- Most software is priced per vertical. There are so many verticals. Maybe we offer dynamic pricing... Let's talk.

- We were talking about Finetech (merchant processing company) selling our software as an add-on. Something like this... it will be such and such for your merchant processing. If you want, we have connections with an awesome software company that we could add-on for x (some small percentage - Steve was thinking about under .5% or 1/2 a percent).

- Steve was talking about how he feels that processing is going to change. Dealing with more mobile type ways of accepting payments and auto tying things into a POS or some sort of system. Robot type stuff.

- At some point, we would love to bill for usage, storage, and processing (called throughput). He was saying that it would help to have some case studies and some examples. We would love to get there, but we are not ready for that yet.

- One of the most common things that we can tie a price to is revenue. It seems to tie things together.

- Most software systems are sold by the seat. With adilas, you get it all.

- We are trying to get a ballpark price (self serve - online). To really get it tight, we would like to talk to the client.

- Get a hold of us. Let's talk.

- We are US based, for our tech support. Steve was saying that was a big question that he has been hearing. Where is your tech support based out of? Am I going to be able to understand the person on the other line? Legit question.

- Switched over to talking about load balancing our servers. If we were to make some changes there, we could cut some costs. Steve is working with Wayne on this. Dealing with server backend coding languages and licenses.

- Databases, datasources, and converting the bus into motorcycles. Maybe create a new database that has corp-specific database tables or some other changes. We have wanted to do this project for quite some time. We have called it the datasource project or the world building project.

- In database land, if we could make things go away (clients and accounts), we could potentially allow for anybody to setup a system. It would either make the grade or get fully removed. Currently, we don't remove anything, we just set it to inactive (virtual delete).

- Drawing the line somewhere. That could be price, company size, business vertical, etc.

- Questions about servicing the account - if it is so small, it makes it hard to service it, there isn't much buffer to cover any tech support costs. Maybe offer a tech support plan or a be able to pre-pay for a certain number of tech support hours. Just some thoughts. This is mostly for the really tiny accounts.

- Talking costs and split commissions. Say something like this... Our costs are 40%. The remaining 60%, we could split 1/2 and 1/2 or 30% with whomever is selling or servicing the account.

Anyways, some good conversation topics and ideas. We will get it all figured out. Making progress.

LTF was a product done by Brandon Moore back in the early 2000's. It was originally a Flash based product that was distributed on an interactive CD-ROM. Most people don't even have an optical drive anymore (what you use to read a CD for your computer). This is a link to the project as a Windows .zip file.

LTF - Learn To Freeride - Volume 1 - Flatland, Rails, and Jibbing (.zip file) - After downloading, for Windows run the LTF_win.exe file. That will start the program. For Mac, download the Adobe Flash player and open the start.swf file (Flash file). There used to be a better Mac version but I'm not sure where it went.

Learn To Freeride was a company that taught snowboarding freestyle skills and moves. Back in the day, one of the only ways to distribute content was via CD. People were still on dial-up modems for Internet connection. The original CD had about 270 video clips, built in video player, music, and three different skins (classic, retro, and punk). This was before apps, but basically, it was an app. Kind of a cool piece of history.

How this ties into adilas.biz - Brandon was working on this project in 2004-2006. This was right about the time that Steve Berkenkotter, founder of adilas.biz - recruited Brandon to help on the adilas.biz project. Brandon had taken out a business loan to pay for and fund the LTF project. Steve offered some database and web work, and Brandon took him up on it to help pay off the loan. If you want more history, here is a small history document covering that time period. Click here for the PDF file - adilas_history_bio.pdf

Meeting with Alan and Steve. He, Steve, is having the AI agents write code and he is managing it. He is working on phone notifications. He is using multiple AI bots to compare notes and check direction stuff. As part of the process, he was getting Wayne, our server guy, to install some different things on the servers. Steve was showing us some things that he is working on, some new reports, and new homepages.

We switched gears and I was showing some stuff from what Shannon and I were working on this morning (eot # 12662). Alan is doing some other research to help with things. We talked about using AI for input data options. Quick, snap a picture, and have the AI do the look-up and prep the input. Having it help with predictions and trending and some sort of analytics.

Steve was showing the different AI models. Looking at pricing per millions of tokens and the context window sizes. Things are changing quickly. We want to keep using natural language processes and asking it for help. Talking about future buildouts and white label options. Steve was talking about robots and what is coming (stuff from the news). Talking about data in and data out. I mentioned that Bryan was working with a potential client that wants a simple POS systems and automating things behind the scenes (eot # 12656). Steve was saying that he sees that kind of thing happening over and over again.

Alan and Steve were saying that our dreams can be realized so much more quickly now. In some ways, you can take the code writing hurtle out of the picture. You still have to know what you know and be willing to mix things together, but things can happen much quicker now. Interesting times.

Working with Shannon. Talks about AI cannibalism and what is happening to the SaaS (software as a service) model. This came from an article on X - twitter (link). Steve sent it over to Alan and I to read. Anyways, I was reading it and Shannon was taking some notes. I was then drawing about how people are using AI and where things are going. I was showing 2 main things... companies need to use AI or be left behind. If they do use AI, especially SaaS companies, they are basically cannibalizing their own products and services.

Notes from Shannon - summary of the article on X:

- Biggest irony in tech history... earnings are up and stock is down

- Huge companies invested tons in AI and ironically it is hurting them

- No AI, you are left behind. Yes AI, and it will start to cannibalize your company

- AI doesn't make software companies stronger, it makes them obsolete

- AI is replacing the software that these companies are selling

- If AI can write code, automate flow, do X, Y, and Z - all for pennies - why would you pay for software?

- One AI agent replaces 10 seats, One prompt replaces months of custom development, One LLM call replaces entire software categories

- Companies that invested most in AI are hurting the most

- Companies enabling AI (hardware) made money

- Hardware up and software down

- The AI world needs GPU's (graphical processing unit)

- Don't need software subscriptions when AI can build it for you

- Investors question - will your business survive the next five years?

- Software earnings were up, but stocks were down. How do you compete with free?

- AI is getting more reliable - you don't have to rely on these older SaaS software packages

- One of the biggest market shifts in history - $500 Billion gone in market value in one day

Shannon and I were talking about what the models are going to look like - drawings... molecule (mash-ups) vs a systemized approach. with AI, it will take the mash-up and really make it even more complicated. Little microservices - more than just a mash-up, it will become soup... just being silly - see attached for a small drawing. In the drawing, I was showing Shannon that we have to use it, meaning AI. Most people and/or companies fall into one of three models. The do it yourselfers (pen, paper, spreadsheets), the mash-ups (molecule type model - trying to mix and blend together), and the systems and platform models. Adilas is a platform model. We would love people to add in AI over the top of what we are already doing. It will just make it richer and better and better. Once again, see the drawing for more info.

Building on a platform that supports AI add-on's - we have the engine to build on top of - the platform - really pushing the platform and how it can service the user needs and requests.

Some of our plans... for helping AI do things... see element of time # 12392 - this entry covers user defined prompts, chaining prompts (multiple prompts in a row or sequence), and how to use AI to help do even more

- Switched to reading over the investment options and opportunities for adilas. Read over some new rules from element of time # 12645

As Shannon and I were talking - I was saying that hyperlinks are my way of gathering things... I can interconnect almost anything using a hyperlink. That is awesome.

We read over the entry on 12645 (see link above) and worked on redefining certain pieces. We aren't trying to get perfect verbiage at this point, more along the general flavor lines. Great session.

Jumped on the GoToMeeting session with Steve. We went over his email that he sent out to all of the guys. Kind of a pivot type email. We talked about different options and where things are going. I then spent some time pitching him on where we are going and what things are looking like. I was doing lots of drawings, talking, and explaining. We went over ideas and options. Towards the end, he was giving me some advice and what not. We talked about capital gains taxes and things to think about on legal stuff (selling percentages of adilas). I am very grateful for his advice and thoughts. Here we go, new chapter.

As part of this new chapter, I will be putting the next two months (hourly wages) on the adilas ship B side (fracture and adilas lite - recorded in the adilas shop) side of the puzzle. Adilas (normal adilas or ship A) owes me some monies. I will be drawing on that as I do a 2 month push to help get some sales and funding. I will not be adding in any new bills (hourly invoices) to the main adilas system during this upcoming 2 months. I'm planning on a 3-way pitch. We will show an introduction (who and what are we), our current offerings (where we are at and what is available right now - sales), and plans for a future buildout (investments). We are going to see where it goes!

I had a few fun ideas over the weekend. These are mostly dealing with a transition to pitch and sell what we have. Often, I keep looking forward to this view of the future where certain things fall into place. I hope that I'm right, but I think that I need to roll with what we have, right now, and then see if that can help us get to that future vision. I tend to prep and prep and prep and maybe even some more prep... Part of my personality. I want it to be nice, awesome, and tight. For now, we may have to roll with it a little bit, vs trying to cross every T and dot every I. Here we go... :)

Here are some of my notes - these are from 1/25/26 and 1/26/26:

- Be honest about what we are doing. Tell it like it is vs just paining the picture of the future. We have come a long way.

- Be our style - emphasis on "our" style

- Think audience - small to medium - for clients, investors, and entrepreneurs

- List out the investment options - show the whole gamut (scope). Think all of the business functions, sub parts of the adilas lite (fracture) plan, and the known areas for investment opportunities. Say someone was interested in education, AI integrations, POS (point of sale) functionality, CRM, CMS, ERP, ecommerce, scheduling, custom code, industry specific skins, marketing, sales, etc. List them all out.

- Point them (interested people) to the web for more details.

- Explain the push window (date range for trying to raise capital).

- Ask them to share with friends, family, and known acquaintances - we are looking for those beginners and lower intermediate investors.

- If they join in, become part of the family, we could give them view only access into the adilas backend. Make sure that they can see what they want to, but also keep and make it safe.

- Big fish vs smaller fish - we want to keep some of our culture.

- Light history about where we came from and what we have been doing.

- Small stats on what we are doing right now... monthly reoccurring revenue, accounts receivable (A/R's), team size, accounts payable (A/P's), etc. Let them see the picture.

- Why the push... explain the why

- What is our culture - explain a little bit about our culture

- What are the goals and vision

- Grassroots and community oriented

- Introduce yourself - this has been my career for the past 20+ years - what do you love and why

- Trying to build a community where others can share and participate

- For me, on the community funded projects - open it up more - clean it up - flag and tag projects to certain key categories - maybe even reopen the actual donation and payment options. We had shut that off due to security and hackers. We could spend some time and tighten that up. That would be fun.

- Reread my church notebook from 1/25/26. I took some good notes and there were some good talks and discussions.

- One of the songs we sang today was hymn 237 - "Do What Is Right". I like that song and it hit a little bit different today. If you aren't sure what to do, do what is right and let the consequences follow. Great message.

- I saw a cool flyer at church today. It was well designed. I was looking at it and trying to get some ideas (layouts and designs). Maybe a fun side with some good whitespace, a nice design, and a simple message. Then the other side could have more information.

- This was huge for me... use existing pieces and artwork - graphics from the teaching gallery, main website, and the presentation gallery - tie it all together.

- If I were holding someone's hand (virtually)... what would I say or tell them? Go in that direction.

- Building a house - analogy - you prep, you plan, you build the outside (earlier versions), and then you work on the inside and do finish work. That is basically what we are doing with the adilas.biz project.

- 3-part pitch deck - introduction, current offerings, and future plans and future buildout

New notes from 1/26/26

- See the text message that I sent to myself. My dad and I were grabbing a breakfast burrito. He was rattling off a bunch of names and possible contacts. That will be a great start.

- Post the BATC interview videos - maybe some other ones as well - just a thought - link to Google Drive adilas videos

- On a call earlier this morning... I mentioned that the adilas part or the software that we were building was the only thing that survived the downturn (recession) in 2008/09 from the old Morning Start Automotive, Inc. business (used car and trailer dealership that Steve owned).

- I reread some notes from yesterday... I liked these ones... people - the plan is people, the purpose is people - and bringing people to Christ and helping people to the next step

- On profitability - we are saying 40% cost, the rest (other 60%) is currently being dumped into development and R&D

Yesterday we met with Steve, see element of time # 12620 for details. Today we were working on where can we go and what can we do. I was showing Shannon some options for outside control of the funding. Lots of drawing and showing flow and possible flow and control. Here are some of our other notes.

- From yesterday's chat, Shannon was talking about Steve not wanting to declare bankruptcy (closing things down) and me not wanting to go back to being alone. Both of us were trying to protect ourselves from super painful past experiences. Very interesting.

- Current ROI vs future ROI. We actually need both.

- Lots of talk about repeating patterns

- Avoiding pain, this seems to be a trend and natural reaction.

- Shannon and I reread over some notes from a business consultant meeting from back in the end of 2019. We called it "our rejecting of things" discussion (EOT # 5295).

- Our people are wanting more structure - see this PDF for an internal adilas survey.

- Helping to frame the pitch to build on top of an existing engine vs building something from the ground up - riding on top of our existing software and team - white labeling a custom skin on top of what we have... fund that... you could get a fully funded and finished system so much quicker - tapping into existing infrastructure.

- Play the game with the massive tools that we have... quick add-ons

- We really enjoyed rereading that full element of time from the business consultant (see link for # 5295).

- What makes a mom-and-pop shop... vs a bigger business? It is mostly about what they choose to do.

- We then flipped over to the element of time # 5296 - this one was a few days later from the previous one. Another business consulting meeting.

- We may need some interplay between the jellyfish model and the value add-on core model (either way - they are tied together)

- Reading over the adilas value add-on core model (see link above) - reading section by section

- Focusing on the industry-specific skins angle - getting investments here at this level.

- We become the underlying engine and let the other companies push and sell things.

Shannon and I were going to jump on and do a work session. Steve was on the meeting. He and I ended up chatting for the whole time. After the meeting, Shannon and I went over some of the topics. I didn't take notes during the actual meeting. Most of these are from Shannon and I talking after the main meeting. Here are some of my notes.

- Steve was saying that he is planning on shutting down adilas or at least start tightening things down. He only wants to work on ROI type projects (return on investment). We tend to get pulled in many directions and don't always get paid by people who we do things for.

- Shannon was listening and showing compassion - I thought that was awesome. I was trying to follow her lead on both the listening and showing compassion. Steve is feeling pretty alone and beat-up by clients, outside parties, and even from internal sources. Software development is and can be a tough gig.

- Only funded products and projects. We have to make a switch.

- There is gold (tons of potential) but we have to remove the overburden (what is covering the gold)

- Cash flow and paying bills - even non people bills - like servers and other tech stuff and loan repayments. Steve hates debt with good reason. Back before the 2008/09 economic crash, they were quite extended for an automotive dealership floorplan. The debt became a crushing reality after sales dropped by well over half. This was back in the Morning Star days.

- Reoccurring monthly fees or revenue is the main thing that investors are looking for. We have some one-off stuff (custom code), and they don't count storage or other reoccurring fees. Especially if they go away or may go away (decreasing) - Investors are looking for monthly reoccurring revenue.

- We took some time and went over some history. We have been doing this for years and we really have been trying to do our best. It's been super tough.

- Repeat patterns - we have seen certain things over and over again. It has to be a different approach forward.

- We talked about options to scale back and then build up

- There is value in what we are doing (but we need to stop)

- The home base (golden goose) is going down... what do we need to do to save that? Steve was saying, it (adilas) is in the ER (emergency room), on life support, how do we tend to that?

- No fun to do what he did (Steve - talking to us and bringing us the bad news)

- Having skin in the game (who is invested)

- Steve said, the gun is pointed in my direction, meaning if things go south, he is the primary percentage holder.

- Staying up late, losing sleep, working weekends, etc. It has been crazy!

- SBA loans and other debt... crushing - long term - we are in a hole

- He really wants things to switch to hourly work and monitoring how much is being paid and who is doing what.

- Supporting each other

- Looking for a future vs saving what is there right now (saving the patient)

- Both Steve and I have had to chat with each other over the years - talking each other off the cliff (wanting to bail out)

- Tons of pressure for paying non-negotiable bills - everything is on auto withdrawal.

- He already went through this... meaning shutting down a company. It hurts.

- Shannon and I were talking about roots and branches and how those need to be graphed in at times to help save the whole.

- I was saying or telling Steve that I make decisions based more on gut feelings, promptings, and impressions vs straight logic. That's who I am.

- We talked about being led - spiritual stuff - getting divine help and trying to listen to what the spirt is saying.

- We want to mix things up. Talking about existing pieces vs following what feels right.

- Fundamentally different ways of looking at the situation (logic vs feelings)

- Compromise and bending but still pushing forward - mixing things together.

All in all, a good but hard meeting. I really want to keep pushing forward, even when pure logic says no. I do feel driven to help, let's see what happens. After Steve left, Shannon and I chatted and will try to mix and blend the different pieces where we can. We have to keep pushing.

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.

There are notes from this morning... 1/12/26 - these notes may seem personal - they are what happened on Sunday 1/11/26 - I recorded them on Monday. They play into the mix as this is the backing for us trying to do what we are doing. It is personal, but still super important (to me at least).

- I was fasting yesterday - good session - had a great "download" (term from my mother) session and filled out some post-it note pages. See EOT # 12616 for details.

- I spoke in church on Sunday - I had fun - hopefully it went okay - I tried to follow the spirit.

- I also enjoyed some of the other meetings at church - Lee Lower gave a fun thought in Bishopric meeting about a guy and some healing and mending relationships - really good message.

- In the next meeting, young men and young women leader training, Reese Hulbert gave a great thought on Satan and how he tries to make us run and hide - then talking about overcoming that fear and following the Lord - how can we dispel that encroaching darkness, shame, fear, and negative thoughts - super good message.

- I was praying - as I finished, I was looking at a quilt on my bed - the diversity is awesome - all of it fits and lays together to make the whole - so fun.

- During sacrament meeting, Lilly Atkinson spoke on cheering each other along - she ended with a challenge - "take one more step" and "bear your testimony" - I really liked the take one more step challenge. Sometimes, that is all we can do.

- Heather gave a great talk in church as well. I took a bunch of notes in my church notebook - great message - moving forward with joy - becoming - "be" & "coming" - breaking things apart - we all get to be part of His work.

- Plan as if for year - act as if for years - D&C 51:17

- In priesthood meeting, Ed Herrmann, was giving the lesson on new beginnings from Elder Kearon from the October 2025 general conference. Jesus went about doing good - At the end of the lesson - Ed was talking about an action strategy that they use in the military - It was...

1. Intel (info or gather info)
2. Plan
3. Rehearse
4. Execute
5. AAR - Pause (after action report)

- Small note... I was typing these notes and got to the note above this about the military action plan or action strategy. I was able to use that little piece in a meeting that I had with Shannon on 1/13/26. That is awesome. The timing was perfect. I just finished typing it before the meeting and then I had to use it. Small mini miracle and blessing. My notes were able to tie into another piece that I was looking at on Monday night (1/12/26). We were helping our daughter do some goal planning for the new year. In the pamphlet, it kept prompting for putting your goals into this format: Discover, Plan, Act, Review - As I was working with Shannon, I was drawing a parallel between the child goal setting strategy vs the military based strategy. They are very similar. They use different words and the military one has a whole section for rehearsing or practicing before doing the actual event or action. I thought that it was very interesting. I was telling Shannon that she was technically helping me do some planning and rehearsing for where we are heading. Good stuff.

Back to my notes from Sunday, 1/11/26 that I wrote on Monday, 1/12/26... I got side tracked

- After church (on 1/11/26), I spoke with Bryan Dayton and told him that I was planning to talk to Steve tomorrow (Monday) about pushing forward - gave him a few small insights into my plan from my shaving session on Sunday morning - see other notes.

- Came home, played a game with Brooklyn

- Super yummy meal after breaking my fast - potato soup and corn bread

- Made chocolate mousse

- Played a game with Heather and Brooklyn - Heather won

- I got a blessing from my dad - we talked and chatted for a bit and then I got a blessing (father's blessing) - I have had many of these - Lots of great love, advice, inspiration, and remembering my worth - I doubt myself sometimes - Here is some advice that he gave me: Take care of yourself, your family, your church calling, and then your profession. Even though profession is forth on the list, that doesn't mean that you give it a forth rate job. He also felt that I should go and meet with Steve - face to face - really try to help - even help repair the relationship. It has been super stressful. He also recommended that I read a few poems (motivational poems) - I have those in a different notebook.

- On the going out to Salida to meet with Steve, I was thinking, maybe we have a team meeting - in person - to go over plans and such - going back to what Ed said (military strategy - intel, plan, rehearse, execute, AAR (pause - after action report) - focus on the plan and rehears sections.

- I have been in so many meetings... tons of training - that is an asset (meaning church and business meetings)

- Quick 1-pagers - Bishop Shawn Smith loves the quick - at a glance - what is going on

- I saw Reese Hulbert use a few quick - at a glance - one pagers for a training meeting. They really seemed to help.

- Contact Gene to see about getting some funding for a big push. Sent him a text on 1/12/26.

- Graphical homepages

- Finish up the MVP list - Estimating somewhere between $500-$750K to finish up that push and those pieces.

- Work as if for years

Emails, paying bills, reviewing notes from over the weekend. Planning for a meeting with Steve. Reread some great poems that have a great message. Click this link to see the poems (on a different entry from a couple of years ago). Pushing up videos to a new folder inside of google drive.

Translating from post-it notes on 1/11/26

- Sunday morning - I was shaving, getting ready for church. I had a flood of ideas come into my head.

- We go for it on 4th down (football analogy)

- Reinforce the team - goal 1

- Goal 2 - We make sure that keeps working (meaning goal 1)

- Morning meeting at 9:30 am (get some communication stuff going on)

- Let people (our team) run... minimal on the micromanagement

- We focus on people... there will always be more projects and features

- CSS on forms for classic looking forms in the snow owl theme

- Look and feel to snow owl - help fix internal and existing pages look good

- Training - could be internal training, AI training, or external training

- Presentation Gallery - Keep pushing on that project

- Images for the adilas lite plan and the investment opportunities

- Abby - Talk to Steve about getting her involved

- Work with the design team - Chuck, Piper, Sarah

- Move key videos to Google Drive vs on the content server. It just can't serve them up quick enough.

- On the AI Agent - Use what we have - Set it up so that it tells people "I'm good at nav" - Polish the 350 existing prompts and tools.

- Suzi - Step-by-steps - small documents with information and instructions. She is really good at that.

- Sean and Cory - General Training

- Prepare for 100+ new accounts - What would that take?

- Open things up!!!

- If needed, we have others who can help - Dustin, Eric, and John. There are others as well.

- Shannon - She has been such a great helper to me

- Let Alan lead out - Help him succeed. He can do so much more than code.

- Get out of the way

- Leverage debt - put all of the adilas shop or adilas lite stuff into adilas as real payables - bring it out of hiding - true costs and costing

- Co-owner Advocate - possible new title, if needed

- Mini bank accounts for each person and/or department - help the team feel safe, supported, and funded

- Be in someone's corner - believe in them

- Overcoming fear - Satan wants us to run and hide

- Simple 1-pagers (one-pagers) - at a glance

Steve canceled the meeting for tonight. He wants me to finish up a couple of projects that have been hanging out. They did send a small update via email. This is what I got from Thomas:

We have updated Adi global context training with all the arsenals, including but not limited to increase context limit, RAG implementation that minimize up to 75% less token consumption, GPT5.2 update and more.  Looking forward to Brandon getting back in adi training mode.

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.

Working with Shannon. I was showing Shannon my notes from the past week. One of the entries had some notes and my spiritual experience (planning and brainstorming on training the AI agent). See element of time # 12527 in the shop for more details. Going over the power of the plan - reinforce, recruit, and then share it. It feels like a mini parallel to God's master plan. Another part of it deals with helping adilas get ready to go out to the world and be a tool that could be used.

We spent some time going over concepts and showing her what the context window was (concept) and how to help make it function at the appropriate level. She then helped me as we talked about using the CMS tables on adilas university (the corp inside of the adilas application called adilas university - corp id # 371) to create and make the global context records. CMS stands for content management systems. All of adilas is basically a giant CMS type application. We will use our media/content database table for those global context pieces to help train the AI agent and our users. It is perfect, it already exists, and has been being used since 2013. We will just repurpose a small portion and use it more heavily from within the adilas university site and corporation.

Switched over to working on the white label section on the fracture (deeper development and system code) build out. We finished up that section. Yeah! After the meeting, I sent Steve a text about using the media/content database table as a CMS system for adilas university and global context stuff. That will be super cool, and it is already done and functional. What a blessing.

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.

GoToMeeting session with Steve. We were talking about natural language processing (NLP). API issues (with our current model). Trying to overcome some memory problems and help it use our mini API's. Behind the scenes, the LLM's are getting faster, better, and cheaper. Going over models and options. Lots of talks on different subjects. Talking about API's and where things are heading. Information is becoming more and more easily to get to. Steve is seeing an increase in 3rd party AI tools. People and companies wanting to build out an integration with their AI tools and features. Steve and I have done a ton of 3rd party integrations... We don't really want to keep relearning the same lessons. Currently, he is saying no, vs yes. We've got to get our product fully to market before we do a bunch of new 3rd party solutions.

Recording notes. Prep for a meeting with Steve. We have been working on this AI agent stuff since August of 2025.

Here are a few elements of time that have some plans for where we are heading and wanting to do:

EOT # 12286 - Normal element of time plus media/content - more advanced prompts and tools

EOT # 12392 - aliases and stringing multiple prompts together - interface ideas - deeper prompts and navigation

EOT # 12497 - ideas on training

EOT # 12527 - other plans and global context

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.

On a GoToMeeting with Steve. He had a small question about some new settings. We did some debugging and got it working for him. He is working with a client that is using an ATM and then paying for invoices and giving change due back to the user. It's a special payment option from inside the cart. Basically, a new button, if turned on, that allows you see the invoice total and then a series of buttons in increments of $5 up to $250. The change due is calculated and the invoice is stamped with the correct information.

Steve and I also spent some time talking about AI training and using ChatGPT to help train the mini model.

Working with Steve and Cory on some harvesting and production stuff. Small changes on some pages. We also had to go in and remove some older pagination stuff for one of the processing pages. It was stuck on the older version and couldn't handle numbers above 2,000 plants at a time. The new code allows for whatever number is needed. After we finished, we briefly spoke about possible other options to queue up bigger batches to help ease the page and server load.

Meeting with the Nxtlinq guys. They were showing us some new updates and how the system (adilas AI agent) is able to ingest uploaded files and how we can edit the main context window (backend admin stuff). After the Nxtlinq meeting, I jumped on again with steve on our GoToMeeting session. We were talking about training it (the mini model) on core concepts and creating a stable foundation. We are going to be using help files to store global context (for now). Eventually, we would like to make a new database that will be just for AI chat, learning, and context on multiple levels (global context, industry specific context, corporation or world level context, and user level context). Steve will be working on a side AI agent (testing things through an API connection). We are trying to get the best options available.

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.

Stuff for Cory. We had a report of some errors when adding things that had flex attributes (PO's, customers, and elements of time). We made some quick fixes and then pushed up code. Wayne was on the Zoom meeting with Cory and Steve and he was able to give me page names and lines where errors occurred. He was looking at some paper trail audit reports. We fixed a few files and pushed up new code. That small fix it session went pretty slick. Basically, a small on the fly bug fix - Wayne was telling me where to go, I was fixing , and Cory was testing.

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.

Quick touch base with the AI agent to see if it was able to remember anything from the training session the day before. Sadly, still no long term data retention. Recording notes and formatting the stuff from the AI training session.

Got a text from Steve and we jumped on to the gotomeeting session. We were talking about the AI agent and where we are at. Steve had me check ChatGPT for something that he put in there just the other day. It was able to find it. We are thinking that we may need to train up the main or mother AI model or AI engine. We may need to look deeper on that. I also went over what Shannon and I were talking about this morning (see element of time # 12458). Good conversation.

Working with Shannon. Talking about the time it takes to use the AI agents. Talking with Shannon about the type of AI tool we are trying to use and setup. We spent some time talking about concerns and possible constraints, moving forward.

My constraints:

- I'm willing but should we do this? I really want it to work - I can see the potential - We need a master trainer that can help others

- We need to communicate - Steve and I

- My time

- Already put in a ton of time

- Questions on funding and budgets

- Train the mother AI engines and models or the mini model? Which one(s)?

- I need some direction - too many things on the plate and I don't know what to prioritize

- The training pieces are all over (on the web and in certain docs) also in my head - No one spot for all training currently

- Things keep changing

- I am saving my conversations with the AI agent, but it takes time to format them, and if it (the training) doesn't stick, then what?

- Putting in energy but not getting the output that is desired - we can only go fast for so long - we can keep chipping away at things, but that is it

- There are lots of parties involved, adilas, Nxtlinq, our users, and the actual AI agent

- We have a vision and we can build a number of things out... we have plans - those plans will take months and months - kinda feeling pressured

- Do we really want to have meetings every two days

- Tons of potential... how far are we willing to push it?

AI agent constraints:

- I've done x hours on the mini model, currently not retaining anything

- Storage at the database level - For them and for us - How can we help this process?

- How can we help with storage - Known needs - System level, corp level, and user level

- They are retaining the chat messages - At the Nxtlinq level - We are not

- Question - How do we really train this agent or entity?

- It, the agent, is giving bogus answers - For example - How do I get rid of an element of time - How can I tell how many elements of time I have (see stored chats from 11/25/25 - Some other user, not from me)

- Can it do what we need it to do

- Cut off from the mother, meaning the agent or mini model - Already over a year behind the data on the mother AI engine

- We don't know the model that it is based on... It really likes the security and blockchain stuff - Meaning what was the original purpose of the AI agent.

- We just need a simple bot that can translate natural language into adilas tools and prompts

- Not retaining information long term... Currently only per person, per session, and that's it

- How are they doing with the crawler to pick up content

- Demands - too much on us, build, train, market, deploy, and it doesn't even work all the way yet

- People aren't wanting it... what it currently is and can do... It take too long, it requires too many two-part authentication stuff, and it can't do advanced or multi step things...

- It is being used less and less - People want it, but if it gives them the wrong answer and isn't fast enough, they will move on

- Too slow, not helpful enough (wrong answers), too many auth steps, can't do complex actions, etc.

- Say you aren't using it... then you decide to use it... and it takes multiple steps to do the auth stuff... you have a quick question and you want an answer in a couple of seconds... you then have to do a multi-step 2-5 minute process to get your answer. Pretty soon, you say, no, not doing that... that is from our users.

At the end of the session with Shannon, we were talking about our simplified AI plan - 1. Teach it how to do some basic or system navigation, 2. Get it all trained up so that it can help with training and support, 3. The ideal is that it knows everything and can help with the higher consulting level and business level questions.

Shannon and I were also talking about the jellyfish model and helping to stabilize the team and their roles. There is a need there.

Meeting with Steve. Looking over some code for low part quantity email alerts. He is working on a some new email services. We then switched and talked a lot about training the parent and the child - AI bots (multiple agents, not just our mini). Our current model is not retaining any real information on a global level (yet). From Steve, maybe work more with the main or parent AI models.

The Nxtlinq guys are adding in more logs so that we can track some other things. They are working on a number of things including improved memory and global context stuff. Memory in AI is making training and knowledge stick. We also talked about a number of other topics. Here are a few of them:

- The costs for the infostructure and keeping the AI agent up and running.

- Talking about global information storage - we really need this, from our team to the bot.

- Talking about influencing things upstream and downstream. We need the AI bot to remember and learn, but we also have to be careful about where it gets its information.

- Light talks about an audio issue between multiple tabs. The AI agent is still listening in a different tab and responding. The simple work around is the mute button on the microphone. We may look deeper into this, if it becomes an issue.

- After the main meeting, Steve, Thomas, and I stayed on the meeting to talk about pricing and future plans.

- Being able to train the agent so that it can help with support, setup, and deployment. Figuring out the pain points and helping us as a company as well as our clients and users.

- Thomas was telling us some stories about introducing agents for other companies.

- Steve was talking about being able to help get the agent up and going and helping with oversight.

- Lots of talk about ingestion rates and values (how much we feed it).

- Human in the loop to help with the training.

- Thomas talking about manual crank windows (roll up/down the windows by hand) vs electric windows (power windows). Ideally, we show our clients and users how awesome it is with AI help. Then, hopefully, they won't want to go back to older tech.

- Getting into the BI level (business intelligence level) later on, as we go.

- If we train this agent up, it will really help our users and clients with training, consulting, etc.

- Here are our steps and phases for working with the AI agent - 1. Navigation and prompts, 2. Setup and training, and then 3. Clear out to consulting.

- Small phone call with Steve afterwards to go over our internal plan a little bit. Good meeting.

Meeting with the Nxtlinq guys. They were giving us some updates. They changed the word verify wallet to verify account. That will help out a bunch. They were giving us a number of other updates on things that they were changing and updating. We are all making good progress. They were making a few requests on and we were as well. Both sides and working well together. They are trying to get us some global admin permissions so that we can help and teach the agent. Lots of talks about ways to monetize things (we've got to pay for this thing). Steve, Josh, and Ted were heading that up. This is new territory for everybody. Anyways, the adilas AI agent (by Nxtlinq) was opened up (turned on and allowed) on every corporation and every server this evening. Here we go!

Quick phone call with Shari O. She had some questions about some sold inventory reports. Spent some time refactoring some code on the adilas third party action page. Removed tons of lines of code. Consolidated some of the sub API socket assignments into a function call.

Jumped on a meeting with Steve to go over some prep stuff for the AI agent launch. We were asking the ai agent to help show us some info. It didn't retain our last training session. It did, during the session, but then it didn't keep it long term or globally. Light AI training... see attached word doc - eventually, we want to make all of our documentation public and use it to train all of the LLM's (large language models). That would be super cool.

Working on cascading the code to get the Nxtlinq AI agent up and running for all corps. Added some code to the classic homepage to check for the AI agent. If the AI agent is not found, it auto adds it. That should help with new corps coming onto the system. Finished up the code to cascade the auto deploy of the AI agent to all servers and all corps. Pushed new code up and ran the update.

Meeting with the Nxtlinq guys. They have been removing the AIT validation stuff, at our request. It just makes it smoother. We are tracking and logging things inside the system already. They are also logging things based on the passed in user info. Here are some other notes from the meeting tonight:

- Maybe an internal survey to see what is important to them, security wise

- Shooting for a friction free environment for the users on the AI setup and usage

- Automation of orchestration and governing the management of the AI tools

- The launch is just the start. Then we finetune and optimize things as we go

- Possible customer services bots or agents monitoring support bots and prompts

- Talking about support and helping to see some automated options - less manual work - maybe use the AI agents to submit any support needs or bugs

- We talked a lot about prepping for a launch next Tuesday. We are planning on pushing the AI agent to all of our existing users. They don't have to use it, if they don't want to, but it will be turned on and available for all users.

- They, Nxtlinq, are going to do a quick video or series of gifs to help with the wallet link-up and verifying the user.

- Steve was saying that we will be trying to stay in front of our clients - prep what we can

- From Ted... our super users will become superhero users

- Small discussion about people - they need to use the new tools, or they will be left behind

- Ted was talking about the wheel. He was saying that AI will be as impactful as the wheel, in his mind.

- Helping our customers become believers

Jumped on a phone call with Steve. Mostly talking about the AI agent and how to help push that project forward. His laptop isn't working.

- He wants me to jump on the meeting later tonight

- We are going as fast as we can

- He wanted me to check on the progress on ingesting all of the adilas help files

- Work in progress... There really isn't a set or defined end to what we are doing

- Let's see if they can crawl or ingest the developer's notebook pages

- Move into deeper testing and getting some great feedback

- Ted really wants us to give the AI agent to all of our customers vs just having it available through the 3rd party solutions page - Steve and I were talking some pros and cons for that approach

- We need to include the new setting to turn the agent on/off at the user level. The main level is the corp level based on the 3rd party solutions page. The sub or individual level is on the my settings page. This needs to be built before we push the main AI agent live to all clients.

- Looking into building complex prompts or multi process prompts

- Most of our clients are using sub inventory, we need to plan and test for that. Currently, most of the cart activity is based at the parent inventory level.

- Steve was saying that we don't want any of the wallet verification stuff inside of the AI agent setup process - it causes friction and seems to be a hassle

Meeting with the Nxtlinq guys. They had a small agenda and we went over it. Nothing too crazy. They are using a crawler to go over the help files. They did have some questions about some of AI quick search prompts that did not have a help file and/or would go to some other site or external reference. We talked about it and they are going to use their web crawler and get what they can.

Thomas from Nxtlinq was talking about their AI agent, they are calling NxtGPT (GPT stands for Generative Pre-trained Transformer - AI deep learning stuff). That seems like a cool name.

I may put in writing some of our requests with regards to the AI agent. We just want to turn it on and not have to verify or set permissions. Our application has built-in error handling and user permission checks on every page. If we have to do settings inside the system and inside the AI agent, our customers or clients might say no. Too much setup... Anyways, I will put some stuff in writing and we'll go from there. Basically, I'm going to say that adilas, as client of NxtGPT and Nxtlinq, we don't want the AI agent to require permissions. The adilas.biz application will take care of the permissions at the user per corp per page level.

They reported that they are ingesting the help files and pushing them over to the agent. That is awesome. There are over 500+ help files. That is awesome and will really help get the AI agent smarter on adilas stuff.

Lastly, I really want to read over some feedback that they, Nxtlinq, gave us from the last meeting. I briefly saw it, but want to really give it a better look over. That is mostly for me. Anyways, good meeting. I sent Steve a quick text after the meeting.

Jumped on the GoToMeeting session with Steve. We were talking about some of our plans for building out the AI quick search and AI agent stuff. See elements of time # 12392 for some details and fun ideas. We also talked about the Ship A to Ship B transformation and paradigm shift. See elements of time # 12385 for details. We are currently heading in a great direction. We just need some revenue and/or funding to help it keep going. Here are a couple of other topics that we chatted about:

- Getting back to sales - we need to sell what we have

- Trying to use technology to help us, as we keep pushing forward

- Sales - It is just a game of numbers

- Teaching people some simple keywords and then point them to the quick search - keywords like: new, home, adv (short for advanced), all, last, prompts, and help. With those seven keywords, you can do tons and tons within the system. That's it, just those couple of keywords.

- Steve is watching some of the AI news... He is going to try to use it to generate some images and videos. He likes that kind of stuff. Things are progressing in leaps and bounds.

Phone call with Steve after our AI meeting. Going over tons of ideas and options... Exciting times.

- On the 3rd party solutions page, add in the other API's that Nxtlinq may need to access their data. Do this all behind the scenes so that a user doesn't have to go in and turn any of those settings on. That way, all of these API sockets will be monitored and controlled via the 3rd party solutions channel.

- We can handle the user level permissions - meaning allowing a user to turn the AI agent on/off at will. The corporation may turn it on, but not all users may want it. Basically, the corp level will be the top level and the user level will be on an individual basis level.

- Earlier today, we were talking about subsets of aliases - Steve had the idea... What about multiple levels deep? Aliases of aliases of aliases... We can totally keep it all strait but what if a user does something all the time... What if the AI agent was able to make its own aliases for common tasks. Talking about predictiveness and interpreting input and intent - We even talked about slang or certain terms that may be used in different regions.

- "Adi go" - command prompt - We already have "Adi" as our little blue dog avatar (helper or mascot). Maybe using "Adi" as a command prompt. This would be similar to how smart phone users can talk with Siri or Alexa. Ours would be "Adi". Idea from Steve.

- Sell what we have

- The value of hyperlinks - mixing command line, Gui interfaces, web, and API - we are built for this

After Steve and I got finished, I was wrapping up for the day. I was really grateful that everything was going good, meeting wise, direction, etc. I was saying a little prayer and had a number of thoughts pop into my head. Call it inspiration, direction, or whatever. I'll take it and I love it! Here are my notes:

- On the user set aliases (making their own prompts), for the AI quick search prompts, what if we used a "#" (pound or hashtag sign) for all user specific prompts. That would not compete with any of our existing prompts. For example: #xyz or #something or #somethingelse... - we could even reclaim certain existing prompts by just add the hashtag in front of it. Another example may be... The prompt or keyword for clocking in/out has an alias of "my time" - what if a user wanted to use that for his/her own prompt for project time tracking. They could create "#my time" or "#time" and it would totally work. Even though both of those values are normal keywords by themselves. It could be really cool. Imagin a hashtag and at least one letter, more if needed. Super simple for quick speed.

- Be able to build and show the prompts and what they are tied to. Simple user interface to setup and maintain their own AI quick search prompts. Very similar to the icon payee top links in the snow owl theme, but even more, and easier to get to... they would be clickable and usable in the AI quick search text fields. Anywhere in the system... That would be super cool! Even better than the icon payee top links (existing link building or special button feature inside of adilas right now).

- What if we used the "go mode" page (new AI quick search prompt page) to show their own prompts or even a fracture type interface - simple tiles and buttons - (small sample image)

- When creating your own buttons, be able to name them, color them, set an icon, a link (advanced - they have to know the URL or web link) or a simple quick search prompt. Maybe even tie the user created prompts and buttons together or make it a dual-purpose database action. Some of the buttons may need to open up a new window and some (most) will just jump to that new page. Just some ideas.

- What about being able to tie multiple prompts together in a mini list, process, or mini prompt recipe? That would be super cool. Imagine something like this: start cart, choose customer, show x or add y to the cart, simple cash checkout - simple English or natural language instructions and the system would help them walk through that process... kinda hold their hand. It won't just do all of them at once, but it will know what the process should be. We could easily create those one-to-many relationships and virtual steps or phases of the process. Just for fun, it makes me think of a data assembly line or assembly line for data. Cool stuff!

- Along this multi-prompt line... We already allow for duplicating invoices to the cart. What if we used a template type scenario and setup a master invoice and then were able to duplicate the exact thing in one click. If changes are needed, they could modify it, but cut out all of the searching and such. What about a partial duplication process... once again a mini recipe for certain steps or data assembly line controls.

- We have a page inside the current system called "my favorites". It currently has a number of buttons on that page. This was one of my todo list notes from a couple of days ago... It totally fits here (see below).

todo: Get back to the ideas of the my favorites page inside of adilas... it got taken over and a bunch of hardcoded buttons put on it. But it does have some potential. See this help file - help.cfm?id=418&pwd=favorites - or visit this page - top_secret/secure/my_favorites.cfm. Added this note on 10/14/25 - it would be so cool to let the users choose anything that they want in the system and then organize it and name it. Cody Apedaile started a draw your own interface (but got pulled off of it for budget reasons). Anyways, the goal is still there to help create your own interface and organize your own buttons as you see fit.

-  Super simple, using old school tech with a modern or new school flare... it will work

- What about helping with memory... We could help hold small comments, save/hold this or that, or even helping to string things together... Maybe help them with their memory... It won't tax the server very hard (store simple things in session - per login). Imagine small AI quick search prompts like clear memory, save to memory, view memory, etc. Super simple stuff. Use JSON storage if saving memory in a more long-term fashion. Simple interface to get things in/out of memory and even use the AI quick search field to help. That would be cool.

- This may not be ready yet - but what if we record and then help them go from one thing to the next to the next... simple session memory with a display... If we know a series of AI quick search prompts... It wouldn't be that hard to display something with a next button, help them step through the process.

Working on help files and AI quick search prompts. Got on a meeting with Steve. We went over a bunch of things. Things move so fast sometimes. We were talking about where we are heading, MVP levels for the AI stuff, questions about making the AI agent multi-tenant and able to handle different domains, corp id's, keys, secrets, etc. We spent a little time, and I was showing Steve what this can do (current AI quick search prompts), small dog and pony show, bouncing around, looking things up, showing some future plans, and making some decisions.

Here are a few other notes from our meeting:

- We already have so many AI quick prompts and keywords. What if allowed our users to setup and create their own aliases or mini prompts? I'm kinda cheating here... It is now hours later (the next morning, when I am recording this). But, we came up with some good ideas and had some inspiration on this topic later that evening (last night - click to see EOT # 12392 for more info).

- The value of simple text look-ups vs straight AI or Id based look-ups. You have to start somewhere, but ideally, you get it tuned into just normal natural language stuff. The computer wants the Id's but normal people want to speak their normal language. Find that happy middle ground or even favor the human side... a bit...

- If we go more to natural language prompts, if a decision can't be made, provide roll-over fail safes - options if things don't work out.

- We are seeing at least four levels of permissions right now. They are corp level (world level), group/category level, page level, and user level.

- In order to make the AI agent into a multi-tenant agent, it will need a way to dynamically deal with domain names, sub domains, corp keys, corp id's, and users. I will try to put some things together on this topic.

- Steve and I were talking about multi-threading and other threading questions... keeping things straight from server to server and between users and users. In this case, for AI, between serves and AI agents and AI agents and users within certain corporations. 

Making a plan. Went through a bunch of menus and found 30 or so homepages or sections that I want to add to the prompts list. Started working through my small list. Ended up doing some special coding to allow a vendor/payee id to be assigned directly to a new PO right from the AI quick search prompts. That should help out the Nxtlinq guys. Steve told me earlier today that they were looking for something like that.

Quick meeting with Steve to show him some of the progress on the new prompts and actions. He had some API questions, and we pointed him in a good direction. We were talking about the value of the URL crafting and mini API stuff. This has been a big push for us. We are excited to see if we can gain some ROI (return on investment) with these new features. We are also excited to see how our users and the adilas community take to these new changes. It is a small paradigm shift for us. That's exciting!

After Steve left, I started making a to do list, emails, and light planning.

Meeting with the Nxtlinq guys. We showed them tons of new progress. We have really spent a ton of time in there (in the AI prompts and keywords) prepping the model. They had a couple of questions, and we had some good conversations. Bryan pitched a cost sharing model and then we got into some questions about the future of AI and where we see it going. The last 15 minutes or so were Steve and Thomas going over lessons learned and what each sees as part of the future.

Bryan jumped in and he, Steve, and Alan, were talking a bit. They were talking about AI quick search stuff and then some sales. Steve and Alan had to take off. Just Bryan and I were then working on stuff. We made some plans, and Bryan is going to help me try to finish up some of the AI quick search prompts and such. Small work session. Making some plans to divide and conquer.

Meeting with Alan and Steve. We were talking about some new accounts and also helping with the accounting for these accounts (offering other services). The goal is to help fill in the gaps on the accounting side of things. Let them do what they can and then we fill in the gaps. Steve was reporting that a client was saying that they were happy to find us. They didn't know that we existed. Small talks about QuickBooks and how many people use them.

The main meeting was between Alan and Steve. I was there, recording notes, chiming in, and doing a little bit of driving (clicking on pages and reports). Here are some of my notes... Instead of being sequential, they are broken down into things that Alan said and things that Steve said. Good meeting.

Notes from Alan:

- Shifting our mindset a little bit

- What is working and what is not working

- Skating to where the puck is going to be vs where the puck is at right now

- Being proactive in our approach

- Running to the fire vs doing what is needed in the long term

- Say a budget of 30 hours - 15 hours working on big projects or using that time to do some prospecting, 5 hours communication stuff (emails, texts, recording time), 5 hours bug fixes, other 5-10 hours maybe using AI to help clean-up the system or refactoring older code

- Maybe some new dashboards

- AI is amazing when it works

- Using AI to help us modernize our interface

- Talking about time - not too rigid on timelines - we want to finish things... - everything takes time - we never tend to get to things

- Taking about proactive maintenance

- He (Alan) sometimes struggles with communication

- It is easier to just knock out projects at times, then talk to people and/or get distracted by different things

- Code fits into multiple areas - paid, fun, wow factors, etc.

- Taking time to work on their own projects (one of his wishes and/or dreams) - basically either continuing education and/or fun projects (what can we do to make it better) - fixing things that bug us (as devs) - making things easier for others

- Alan's been working on some refunds (card pointe and clover - merchant processing stuff)

- Talking about dreams and what would that look like

- Stuck in between what we want and what we have

- Fearing the slowly sinking into nothingness (an analogy about adilas - like a ship)

- Running in circles

- Chasing a ghost (phantom look and feel)

- Alan asking about the goal with the investors

- Talking about the size of the client that we are chasing... how big of a fish are we looking for? - we may be trying to get too big - who are we? can we handle that size of a fish? - what is our goal and how will we get there?

- Alan had some questions on pricing and what does our ideal client look like? how do we find that person/company?

- other sales related questions - how do you judge a company, size, needs, etc.? - what about customizing things? good or bad? - we don't have a big huge team - we have been burned with merchant processing and other 3rd party solutions

- Talking about adilas and where we are at financially

Notes from Steve - once again, not sequential, but just things that I wrote down that he was talking about.

- Learning to adapt - using AI - it is going so fast - we need to be in that race

- Talking about databases - yes, they are still really needed (good multi-relational databases)

- Steve was showing some of the AI stuff in his demos with some potential clients - that has been going well

- We are really bad at estimates (we have had our lunch eaten time and time again)

- Talking about client churn and companies falling off of the system - pretty normal - we are actually doing pretty good.

- Looking around in the system a bit

- Maybe going with $100/hour for development work and $65/hour for setup and oversight

- AI has sped up Steve's work - he is learning along the way - guiding it along - taking in small sections at a time

- Steve was talking about time budgets and not getting too tight on certain time blocks

- Some of Steve's projects are tiny and fulfilling - inch by inch and little dabs

- We need some firewood (sales and revenue coming in) - we are low on revenue

- Steve thinks that Alan needs a break - maybe getting out there and talking to people about what we have

- Sean has been helping with deployment - Cory is doing more client work

- Steve loves to figure out the angles (problem solving for clients and what they need)

- We have an MVP (minimal viable product)

- Finding people who are happy with what we have

- Investors tend to look at the reoccurring revenue - we are looking for an angel type investor who sees the vision and value and says, yes, let's push this thing forward

- We have gotten it this point without a sales team and without marketing... imagine what we could do if we get that going

- Big fish are expecting to be courted (wine and dined)

- They, our clients, have to be big enough to afford us

- Shooting for $400/month

- No big fish and no little fish (super little) - being able to offer our services and they pay for it

- Learning to say no

- Most companies pay around 3% for merchant processing... say we go less than that - say 2% of monthly revenue - start higher and then go down if you need to - if you are dealing with a big chain, we may have to negotiate with them

- Steve talking about numbers... say we have made $10Million from paying clients. If you take number and divide it by our total client count over the years, for us, it is around $12K per client

- We should be selling stuff - that is a super high number at around $12K per client

- Steve would like to get 5-10 new accounts a month

- Offer our other services - activation, deployment, and servicing the account

- We have done a lot of stuff for free... we need to change that

- Sales - can be broken down into three main things... they are like, trust, and respect

- Just tell everyone what you do (from Kiva)

- Do they have inventory? Do they need to track stuff? Great! - Nobody does inventory management like we do - QuickBooks is sending people to FishBowl and Shopify

- Being outside and out and about

- Helping people with their over needs - these are things that they can't get to - their over needs

- We could offer lots of other outside or inside services - we are $65/hour for those services

- We either do it or we don't do it, go to the next

- Stay on the good side of town

- On custom code, they, our clients tend to really like to dream and can't really afford it - we have been burned on doing too much custom - we are $100/hour, paid weekly, if yes, ok, let's go

- The bigger the lift, the bigger the pain (time and money)

- If needed, we could move forward with bigger teams - like a lawyer, we could work off of a retainer

- We can get lost in "custom world" or "custom land" - we need to steer clear of major custom

- Looking for happy clients - we have a bunch of clients who are not calling us, they are happy

- Trying to stay away from black box stuff - building settings or small bridges

- Being able to remove columns on reports (fracture or adilas lite stuff)

- Simple website stuff (easy hosting) - simple pages and some settings (landing page, contact us, and about us, plus adilas ecommerce)

- Trying to be around $1,000 and then a monthly (have to have an adilas account)

- Taking things off of their shoulders - they are already spending tons for all of these other services (mashups)

- Maybe look at some sport teams - other team sports

- Not trying to sell things, just doing some exploring

- Talking about sales and/or trimming things down a bit (financially)

- We may to stop or curve the development and really focus on sales

- Talking about the AI quick search - going beyond normal API endpoints (URL crafting, AI quick search, mini API, etc.) - Steve jumped into the test site and was showing Alan some of the AI agent stuff that we are working on.

Overall, a great meeting. Some good takeaways as well. Good stuff!

///////////////////

Bryan ran this page through AI and got the following summary back

AI Summary:

Sales & Strategy Meeting Summary

Attendees: Alan, Steve, Brandon, & Bryan

Meeting Overview

The discussion focused on expanding Adilas’ service offerings, improving operational efficiency, refining sales strategy, and leveraging AI to modernize both processes and the user interface. The team emphasized the need to balance custom work with scalable solutions and to strengthen recurring revenue and client engagement.

Key Discussion Points

Alan’s Focus

• Encouraged a proactive and forward-thinking mindset (“skate to where the puck is going”).

• Suggested a structured time allocation for projects, maintenance, communication, and AI-driven improvements.

• Emphasized AI modernization for the Adilas interface.

• Advocated for proactive maintenance and allowing time for innovation and internal improvement projects.

• Discussed defining the ideal client profile, pricing models, and balance between customization and scalability.

• Highlighted challenges in communication and prioritization but emphasized long-term goals and clarity of direction.

Steve’s Focus

• Stressed the importance of adapting quickly to AI and new technologies.

• Acknowledged issues with time estimates and scope management.

• Proposed pricing structure:

  • $100/hour for development

  • $65/hour for setup/support

• Highlighted need to increase recurring revenue and attract an angel investor aligned with Adilas’ vision.

• Advocated for focusing on sales growth (targeting 5–10 new accounts/month).

• Emphasized charging for all services—move away from unpaid work.

• Encouraged avoiding excessive custom development to protect scalability.

• Recommended prioritizing sales and marketing efforts to drive short-term revenue.

Action Items

• Define the ideal client profile and align pricing accordingly.

• Increase focus on sales, marketing, and client outreach.

• Use AI strategically to streamline operations and modernize the platform.

• Improve internal communication and proactive planning.

• Explore investor options and sustainable growth strategies.

Phone call with Alan going over plans and ideas. We are hoping to get a meeting with Steve setup for Friday of this week.

Speaking with Steve about AI security. We then started talking about possible options and where we are going. Talking about tracking time and communications. Small history and waves of selling what we have... Steve going out and selling (software on the internet - cloud), Cannabis space wave (we had some internal struggles - who would be willing to play), Steve is seeing the third wave as the AI wave. Good phone call.

Meeting with the Nxtlinq guys. Steve, Josh, Bryan, Matt, Roger, and Vincent were on the meeting. We showed them some progress and sent them over some help file links. Mostly what we were able to show them was the new documentation stuff.

One thing that Vincent said that I liked was "Remove the friction". That should be our main goal in this venture. I liked that saying. If we could remove the friction on other parts, things would be even smoother. Without getting too technical, you have to have some friction, but making things smoother would be a plus. There is a balance point.

Working on AI quick search documentation for options, keywords, and prompts. Had to combine two help files in order to get all of the data that we want and need. Here's a link to the help file. After that, jumped on a meeting with Bryan and Steve. Got new code from Bryan and merged it into master.

Quick update meeting with Steve. Showed him some of the progress we are making. Briefly showed him a few updates. Sent out a couple of quick emails and doing some light follow-up.

Going over the plan for receiving partial PO's

Meeting with Cory and Steve. Going over projects and timelines. The time part (how long things take) is one of the hardest things to control. Lots of unknowns. We then went over some other questions. Lots of 3rd party solution stuff. Our clients want that stuff, but it takes time. Tons of little mini questions and small tweaks that are needed.

Phone call with Steve to go over progress and processes. We talked about some new leads, upcoming projects, and what to do on the payroll side for the AI prompts and such. Lots of moving pieces.

On the meeting with the Nxtlinq guys. They had a couple of questions. They want to know when we will get certain deliverables done and live. We also introduced Bryan Dayton as a new adilas team member on this project who will be helping Steve, Josh, and I. That should really help. Often, Steve and I are on all kinds of meetings and don't get the time to get everything done that we need to. Adding in Bryan to the mix should really help. We will work with him to help pass the vision and help direct him in the right ways. Good stuff.

After the meeting, jumped on a phone call with Bryan. Talking about next steps and setting up some time to meet tomorrow. After that, I sent a text message to Steve with an update about what we went over and when we are meeting next. I'm excited to see where things go.

Brandon and Bryan went to the Adobe ColdFusion Summit Conference in Las Vegas. Multiple days at the conference. See attached for my notes. Good sessions and good learning.

While down there, some phone calls with Steve and Alan going over plans, projects, and funding stuff.

Working on the AI options and prompts for the AI quick search. Had a good 3+ hour long session working on the search action page and refining things.

Later on, we jumped on a meeting with the Nxtlinq guys. Going over progress and answering questions. They are wanting more options, prompts, and documentation. They are doing a great job. Some of their questions will require Steve and I to get together to make some plans. We are all making progress.

Meeting with the Nxtlinq guys. They are trying to streamline things. Removing user friction, less logins, less security checks, etc. The also changed their main permissions and sub permissions. If more are needed, we may add an advanced mode or deeper permissions. They are getting faster on the UI/UX. They reported on some changes to the voice feature (microphone). It is able to remain active vs closing right after usage. We may need some more real-world testing to see what works best. After the meeting, I sent a quick text to Steve to fill him in on the progress.

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 on more AI options and prompts. I have a small list that I would like to add and make happen. See EOT # 12286 in the shop (private).

On a meeting with Steve. We went over the adilas mini API and the new AI filters (sub filters within the main filter). We then talked about some proposals. I was pitching for some guys to help us out and work on specific projects. There were three code masters (Calvin, Brian, and Cody), maybe give them each 1% of adilas, plus $20K to cover (3-4 months). Just some thoughts. Steve wanted to know what they would be working on. I showed him the ship A MVP list that I have. Talking about how AI can help with training. That would be so awesome. Going over adilas lite and I showed him that we have the first 4 done. We also set a rough goal of putting adilas, llc percentages up for sale as of October of this year. Trying to generate some capital to keep pushing things forward. Other talks about projects and AI stuff.

Meeting with Alan, Cory, Steve, and Bryan on a Zoom meeting. Here are some of my notes:

- Talking about budgets and payables. It's been a long grind for all of us.

- Talking about options to sale a portion of the company (percentages) and what that might look like.

- How can we increase sales and improve the communication (internal and external communications). Lots of back and forth.

- Talking about ideas, solutions, and different lessons learned.

- Spent some time talking about custom work for clients. We have been burned over and over again. Also, nobody knows who is working on what. There is a real lack of communication within our team.

- We are honestly trying, but it gets tough.

- We have so many things going on... that is awesome, but it adds challenges.

- We switched over and spent some time talking about funded projects and trying to focus there.

- The subject switched over to talking about sales... Small list from Steve - like, trust, and respect - that's selling. Helping to solve people's pain. We may have to switch to our sales hat.

- Alan had a number of questions about selling or sales... what can adilas do? How do I sale this? Being able to speak their lingo, meaning our clients.

- Focus on bringing in revenue vs building. That is a hard transition for us, but we can do it. Steve's analogy - go out and get some firewood.

- Towards the end of the meeting, Steve was working his magic and basically selling us on some things... he is super good at that. We are planning on going out to sale systems.

Emails and phone call with Calvin. He is getting into tons of AI and wanted to meet with Steve and I to show us what he has been doing. We would like to meet with him next week. General to do list items. Paying bills, entering expenses, and other stuff. Had to update some API keys for the guys who are testing the AI agent for the POS (point of sale stuff). More expenses and paying bills.

Meeting with the Nxtlinq guys. They are wanting to know about progress and how quick we can get them stuff to work with. They were showing us some new changes. They are simplifying things and making it easier to integrate the SDK's and to toggle on/off certain pieces of the AI agent. We told them that we are working on putting the AI agent in the headers and footers to make it show up (if turned on) in all pages of the adilas application. They would like that done as soon as possible. We set a date for this coming Tuesday. They would love it sooner, but we'll see how it flows and goes.

After the meeting, called and talked with Steve for a few minutes. He is pretty comfortable on where we are heading. We also talked about a couple of other projects that are circling around as well.

Meeting with Steve. He and I were working on the AI agent stuff and where to go with it. We would like to include some code on our headers and footers to help the agent show up on every page. We really want to use the adilas mini API, full adilas API, and our new URL crafting (AI quick search). That is our goal. Josh joined us at the end, and we had some good conversations about ideas and options.

On a meeting with the guys from Nxtlinq. They showed us some progress and had a few questions. They are just barely being able to start using some of the URL options and prompts. We still have a ways to go, but they are making progress. After the meeting, I sent an email to both Steve and Josh with a small overview of how it went.

Phone call with Steve... going over ideas and how to put some simple look-ups into the public domain... We are thinking about building a quick mini API (short and sweet). Talking about AI agents and options. Predictive levels and seeding (prepping) the environment.

Work session with Steve on the AI quick search and URL crafting stuff with small normal text prompts.

Meeting with Bryan, Alan, and Brian from Finetech. We went over some merchant processing stuff and questions. We talked about some needed changes for Clover devices and some Card Pointe enhancements. After everybody else left, just Bryan and I stayed on for a bit. We did some light training and set it up for one of our clients to accept split payments for ecommerce. We didn't allow it directly, but we used some existing settings to let that happen. We then started talking about AI and how we are using that in some of our development and processes. I showed Bryan some of Steve and I's AI quick search stuff that we were doing (options and prompt to help generate URL's and do custom URL crafting).

Great meeting with Steve. We were going over options to help let AI agents and AI bots use the adilas application. Steve is working with some guys out of China who do that kind of things. We spent some time going over some ideas and where we could go with things. We talked about the external adilas API sockets, an internal option that involved cookies, tokens, and JSON data storage. We also talked about using the existing structure and URL (web addresses) and how that might look. Our favorite option was the web links and URL crafting ideas. See notes below...

- Use the custom_json table - if we went with internal data storage options, this database table could be used for storage.

- Cookies and tokens - We help them save and retrieve them and then they have a spot to stick and store their data.

- Mix a hash... say something like this... auto id, main id, app type id, date, and then get a hash from mixing those pieces. This would end up being the virtual token that would let you look-up the actual JSON object.

- This internal cookies, tokens, and JSON data storage would virtually provide them a small shelf space for them to use. This could totally work and we may end up using it by itself or in conjunction with other options.

- On the ColdFusion side, internal app stuff, we could do a virtual 1-off on the code pages. Basically, don't stop or interrupt the main page flow. Just build little side or frontage roads as needed.

- We were looking up existing API sockets and methods. We may end up using the addEditCustomJSON method - in search_15.cfc - possible new API

We then switched gears and were talking about using the URL... hyper links or web address links - We really liked this option.

- With simple URL's or hyper links we could virtually use the system just like a normal user - We could let AI do or make interactions vs human powered links.

- AI cold potentially help with understanding normal voice controls or prompts and even different languages - translate and convert to the options or prompts.

- Let the user talk to the system

- Steve's word or phase "URL crafting" - I liked that

- Natural conversation and then boiling things down to the prompts which will translate to the correct URL crafting option

- Normal html pages and web addresses. Once the pages come up, you could do some scraping and then using those pieces

- AI, the user, the interface, and the URL crafting - perfect marriage

- Steve had so many ideas... recording time, recording notes, etc. - so cool!!!! AI could help our users be a super user

- 3-legged stool analogy... One leg is the system and its features and functions. Another leg is the users and the money that they spend to use the application. The last leg of the 3-legged stool is education and training. AI could help be the trainer and navigator (major help on the education side).

- My mind was blown a bit today... that's been awhile since I had that much fun dreaming and brainstorming. We had help from above - guidance and inspiration. I'm so thankful for that. Just trying to give some credit where credit is due... :)

Meeting with Steve and the developers who are building the bot engine and AI agent for a voice-controlled POS (point of sale) options. They are using the adilas API endpoints and sockets to interface with us (currently). We got on the meeting and we went for a little over an hour. There were eight of us on the meeting. We would speak and then wait for them to translate. They showed us a small demo and had a small agenda ready to go. We talked about different options. Originally, they just wanted to use the adilas API sockets and endpoints. Now, it feels more like they want to build the engine inside of adilas to have more options and access. That is potentially good and bad. We want to look deeper into this before we just say yes, do it.

After the meeting, Steve, Josh, and I got on a call and talked about some possible options. We will meet again as a team on Monday afternoon to come up with a plan. We will then present that plan to the Nxtlinq (spelling?) guys.

Prep work for working with Bryan. Jumped on a meeting with Bryan to show him my progress. We talked about the next steps, and I will keep working on code review for his project. We are working on the flex attributes for quotes and invoices. This project also deals with how those things are passed through the shopping cart as well. Bryan wants to use some of this tech and these sub features for restaurants and cafes. Both Cory and Steve mentioned in our earlier meeting that they have clients that could use a similar feature but in their own ways. Good stuff.

Meeting with Cory and Steve. Going over vendor credits. Looking over a quick question on calculating taxes for invoices. Small API socket stuff. Steve left and then Cory and I were going through a list of questions and small internal tech support pieces and requests from clients. We jumped through a number of small projects. Lots of the requests are user/client preferences. Certain people like it one way, others like it another way. Eventually, it will end up being a setting of some sort. That's what it is looking like as of now. We will get to those changes when we can, once other projects are done. There is a constant demand for new and enhanced features.

Working with Steve on some code. We jumped in on a big bulk transfer page for quickly moving tons of inventory around. We did a few small fixes and got his page working. He has to go back in and do some clean-up, but it is coming along great.

Prep work to get a video ready for showing the new feature for the vendor credits functionality that we just launched. Made a quick outline, did some practice, and then made a number of videos and pushed them up live. Sent an email to Cory and Steve to show the new features. See attached for the video links.

Recording notes from last week. Going through emails. Got a text from Steve with a question about adilas API and which ones I would recommend. Light research on which API call to use to get the parent part or inventory item quantities. Sent him some info via text message.

Working with Shannon. We were talking about adilas university stuff and the value of training and education. Here are a few of my notes:

- Recircling back around, even after 10 years, to older projects and plans. Part of life.

- I was telling Shannon about how Steve is trying to use the adilas API's and provide documentation to folks. That's exciting!

- Spent some time talking about finishing up projects and doing the training portion (last part of the project). Sometimes that last part is the hardest.

- We looked at Udemy (online learning portal). Looking at the general flow, prices, how things are categorized, etc.

- We reread element of time # 12145 and talking about those points... lots of topics there that talk about the value of education.

- People want mostly intuitive features, quick training, and easy to use applications.

- Looking for expert knowledge. Reps and consultants. We have used these (reps) a lot in times past.

- Possible disconnect between pricing and learning curve. How much buy in, value, ease of use, and will this be a good experience? What are our clients looking for? Are we trying to be the cheapest or the best? There is a difference.

- Talking about value-based upgrades and user perceptions.

- Using the adilas API as a 3rd party white label - tons of potential there. Play at the wall.

- We spent the rest of the time working on content for the adilas university page in the adilas lite plan (fracture stuff).

Phone call with Bryan. He is working through a merchant processing setup. He reached out to a number of people and just wanted to talk about what to do and where to go next. It seems like a small mix between a specific merchant account and specific hardware being used. We are trying to figure out the next steps.

Recording changes in the adilas ownership percentages. Sent an email to both Shari O. and Steve with documentation.

Brainstorming on some ideas about receiving inventory and training people... the brainstorming then switched over to AI agents - job queues and prep mode... see EOT # 12195

Jumped on a GoToMeeting with Steve. We looked at a small bug and got it fix for a new API socket that he is working on. Steve is exposing all kinds of external API sockets and harnessing some work that was done years ago. That is awesome.

We then switched gears and spent a few minutes talking about possible job queues, prep work, and ordering inventory and receiving inventory and client needs. See more notes on element of time # 12195.

Paying bills and recording notes. Phone call with Bryan. Going over ways to speed up the PO and entering inventory process. Talking about training for our clients and needs. We then got on a conference call with a client to go over some custom ecommerce checkout requests. Going through emails. Quick phone call with Steve to go over some API socket stuff. He is really making some headway there. We added API sockets back in the early 2000's but it has not been fully used until somewhat recently.

This was just some brainstorming... It started out with training people and then moves into possible AI agents and bots.

On the people side - What if we trained people to help work inside of adilas... and then helped to staff them at other people's business. Almost a small staffing service for trained adilas workers to help with data entry, input, etc. - just a thought... We have seen huge needs on ordering inventory and then receiving inventory. There are multiple steps but very trainable...

This could be part of the adilas cafe and community concept.

If I had the money... It would be super cool to setup a training program to help people who want to work, get them the training, even get them certified, then get them connected with the right companies who need work done. They could then use their skills to earn money. These people and their skills would then become an asset to companies that use adilas, as a trained labor force. It still needs some more info, but it could really help out in different ways.

Switching over to job queues... and AI agents...

This needs more thought, but what if you could even setup a virtual queue of things that need to be done... It could all be done from outside of the system and then people could pay for the work to be done... Basically, abstract it enough that a person working wouldn't have to have permissions to work inside another person's system. Build the whole thing on the outside. Think prep work... prep level interface... They could do the work, on the outside, in a special prep environment, then it could be approved, pulled in, and flip it over to real or live. Like I said, it may need some more thought, but that would be super cool.

I could see a company, quickly add a job to the queue, uploading a PDF or scan (some kind of documentation), and then they get notified when it was done. That would allow someone who is doing stuff to work for multiple companies without actually affecting their live systems (everything is in a prep stage). The work would be done, recorded, and basically prepped for changes and quick import. Another thought would be to build an AI (artificial intelligence) agent to do a similar thing. It looks through a queue, does the prep work, applies the rules and training on OCR (optical character recognition) documents, performs one or more processes, and when it is done, it submits it for approval (go live status). All kinds of options.

Steve is already working with a company that is building AI agents to do voice activated POS (point of sale) functionality, payroll functions, and other tasks. What if we could keep adding to that list... expenses, deposits, bank reconciliation, sales receipts, quotes, PO's, inventory levels, ordering inventory, receiving inventory, pricing, ad campaigns, discounts, special sales, CRM stuff, ecommerce, scheduling, etc. Think of everything that adilas can already do... What if we could allow for people (real people) or AI agents to do some of those tasks... It (whatever work was done or prepped) doesn't go live until the requesting company clicks approve or some process that would allow for real prep work to become real live data transactions. That could be super cool!

Meeting with Cory and Steve. Quick review of my projects. Then on to some questions that Steve had with the adilas API sockets. We went over some internal pieces and how things work outside in the web/API realm. Good conversation. He is connecting the pieces and helping some outside developers get connected to the API. One of the companies that he is working with are some AI agents that are building voice activated POS systems.

Working with Steve and looking over his new projects. He is working on a bulk transfer for subs (parts and items). Looking over his code for the bulk transfer invoices of sub inventory back and forth. We worked on some code for a while and got it to a stable spot. He will keep working on it. We then rolled over to the external adilas API sockets and talked about some flow for a little while. Steve is working with those AI bot guys who are doing some voice interface stuff with API calls to do a voice operated POS system.

Helping Steve with a quick merge conflict resolution for a file. He also showed me some of the efforts that he and Josh are working on to do voice automation bots through AI agents. They are playing around with a company out of California that Josh knows.

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.

Paying bills and recording notes. Lots of internal tech support stuff today. Also, at two different times, we tried to jump on the GoToMeeting session but others were using the account. Steve was on earlier in a demo when Alan and I were going to use it. Then Alan was on later when Bryan and I were going to jump in. All is well. I'm glad that they were getting their stuff done as well. Busy day!

Meeting with Wayne and Steve. Using AI in adilas reports and code. Steve was showing some AI sales results. Wayne was showing me some AI appointment stuff. Wayne was going over Amazon Lex AI stuff. Briefly going over languages, intents, prompts, messaging back and forth, conversations, flow and logic, slot types, confirmations, fulfillment, code hooks, and other bot basics. They were talking about building a mini adilas bot army. Doing all kinds of things.

We flipped over to the adilas API sockets and Steve and I were showing Wayne around a bit. Steve was saying that he would like to setup and help companies that do simple services. We jumped into the Burrito King demo site and were playing with some adilas API calls.

After that Steve and I flipped over to ecommerce code and showing and selling subs. We went over a few things and had some discussion about ways to sell inventory online. Steve is thinking about adding in a new option that will be show and choose subs.

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.

Law of deferring to something that has more info (postpone action/judgement or let something else take control temporarily). Talking about the balance sheet and the P&L (profit and loss or income statement). We were conceptionally talking about some deeper accounting and deferring (delaying) of certain things.

We spent some time showing Cory and Steve progress on the vendor credit project. It should be finished up by the end of the week. We then flipped over and were talking about how the internal adilas API was structured and created. I was showing Steve and Cory was doing stuff in the background. Lots of drawing and showing flow. Hopefully it helped.

Going back to the law of deferring. I looked it up and it said - The term "deferring" means to postpone or delay an action or decision to a later time. It often implies allowing someone else to make a choice or follow their decision, as in "deferring to someone else's wishes". In various contexts, such as finance, it can refer to delaying payments or actions for potential future benefits. Overall, deferring suggests a temporary suspension of action rather than a permanent decision.

We tend to defer to the object or piece of data that holds the most information or has the best value. It all plays in, we just give certain pieces more precedence than other parts or pieces. That's how we fold the whole thing together into a working system.

On the phone with Steve going over our internal API sockets and using possible AI agents to help with code and interfaces. Steve is working with some folks who are interested in seeing what they can do and how they could interact with the different companies using the API and AI agents. We chatted about pros, cons, and known needs. Could be interesting.

Meeting with Steve. Out in ecommerce land looking at custom flags and tags for tiered pricing. Going through code and looking for why we couldn't get certain things to show up. We spent a lot of time tracking things down and ended up fixing a few small things.

Added the mini question mark icon for the settings dialog box to the mini scan cart. Sent an email out to the others. This was requested by Steve and Cory in our earlier meeting today.

Meeting with Cory and Steve. Going over progress on the vendor credit project. Cory is trying to help and is managing expectations with the clients. That really helps. We flipped over to some needs on the shopping cart side. Steve is working on a number of new settings. He is working on some new ecommerce settings. After the meeting, I started looking into adding standard settings into the new shopping cart.

On the GoToMeeting session with Steve. We were looking at the new mini scan cart and talking about how to get the gram controllers in there, inside the mini scan cart. We looked at some code and talked about options. He was also showing me some other changes that have been made and some new updates on projects, look and feel, and who is doing what.

Emails, recording notes, and paying bills.

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.

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.

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.

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.

Phone call with Steve going over plans and small recap of our previous meeting. We also talked about some other projects and how best to proceed. Something is always going on... never a dull moment.

Meeting with the SymLiv folks (Taylor and John). This was the first time that Steve had met these guys. Light intros. They have lots of asks from their clients... can you connect to x, y, z, etc.? They are looking for resort level communities and helping to control access and flow in those resort level communities. We talked about doing a full white label option or options. This was kinda fun, but they were talking about white labels of white labels (multi layering of white label products). We were talking about pricing, wholesale options, and how to proceed. Kind of an intro meeting of sorts for Steve and John.

Meeting with Taylor James, John Spuhler, and Tim Greenfield from SymLiv. They deal with different gated communities. They were looking at adilas to help them take care of the other internal processes within those gated communities. Things like simple cabin rentals, small retail shops, booking venues, owners or guests putting things on a tab and paying later, other simple ecommerce, POS (point of sale stuff), CRM (customer relationship management stuff), and scheduling options. Good little demo. They wanted to connect with Steve to get some other info and some pricing. I was somewhat pitching them the white label idea and option.

After the meeting, I called and chatted with Steve for 10 or so minutes to give him a recap. I sent the guys his contact info. He will watch for the email and we'll go from there. He was also reporting on other things that are going on with different clients and projects.

Meeting with Steve and Adilene. We were talking and showing her around adilas. Steve and I were batting things around and feeding off of one another. It was fun. We were bouncing around from server to server, client to client, and showing her all kinds of stuff. Fun little session. We got into some theory, some logic and flow, and even showed her some code. We were chatting and talking for a couple of hours. All kinds of subjects and topics.

Jumped in on the partial PO project. Stepped away from the computer and read over the brainstorming document that Steve and I had made. Working on refining the plan. Started to work on the plan with paper and pen first, then I'll go to a digital format.

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.

Working with Steve on receiving the partial PO's project. We spent some time going over the project, talking about scenarios, and looking at different parts of the system. We did some drawings and some brainstorming on ideas. We may also see a need for forecasting and predictive AI type level stuff playing into the mix. See attached for our notes.

Phone call with Steve. Going over new AI generated web content, updates on possible investors, and talking about projects and budgets. We also briefly talked about other developers, current and upcoming projects, and future plans. Small catch-up and update session.

Meeting with Steve. Looking into ecommerce changes and settings. We pulled up a branch that Chuck was working on. We made a few tweaks and wired things up. We got it all up and live and did some testing. After the meeting, I made a few more small tweaks. I also sent an email out to Wayne to ask about caching issues (web file being cached and not updated) and how to help overcome some of those things.

Working with Steve over a GoToMeeting session. We added in a new flag option on the advanced PO searches. It checks for still outstanding PO's and disconnects between the main and the sum of the line items. We went through and added some more code to make it happen. We did some testing and cascaded those pieces to other pages. 

We switched gears and talked about investors and what we are looking for in an investor. I took some notes and will work with Shannon to update the correct verbiage on the investment page for purchasing an adilas percentage. Good meeting!

Emails. Quick phone call with Steve to go over a few things. Recording notes from 3/31/25 to 4/1/25.

Helping Sean by looking at some barcode printing options. We jumped on the GoToMeeting session and played around with some samples. He is going to respond to an email and copy both Steve and I into the email. Talking about some options.

A little bit of meeting prep. Meeting with Chris and Steve. Light intros and such. Talking about our history and how the Morning Star Dealership got into debt and dealing with banks and floorplan stuff (old automotive business stuff - history). That big debt made it really tough. Going over lessons learned from being in business over time.

VC (venture capital) seems to be too risky for what we are doing. Looking more for the angle investor or something along those lines. We would love someone to buy in (own equity or be an equity partner) and then put in x and then we structure a pay back and how that works. That would be really cool.

Talking about sales and deployment and having to switch hats. Talking about how much money we can responsibly use and activate (manage). Lots of times, customers make assumptions based on look and feel. We'd like to make some changes and updates there. If we got some monies, we would need to show how the spend would return on that investment. Going over some financials and such.

Chris was saying, put yourself in the investor's shoes and what does that look like. That helps you know what they are wanting and expecting.

Chris left and Steve and I were talking about other options, plans, and where we are going. Lots of talk about some changes to ecommerce that would help.

Meeting with Adilene over an online meeting. Here are some of my notes:

- She sees adilas as a full life cycle management system or tool - that's pretty cool!

- She had some ideas about airports and how they need their vendors to pay them a commission for setting up and using airport space for their shops. Currently, there seems to be a lack of products that could help the airport oversee their sub vendors and shops. We could possibly really help them out by allowing some enterprise level reporting.

- Horses and equestrian sports seems to be a bit behind the times in their software management options. Adilene (Adi) has been having fun taking riding lessons and everything is done by paper or something super simple right now. She thinks that this may be a good vertical to checkout.

- We talked about sports venues and sports in general - even the quite sports (not as popular or smaller)

- Steve was telling Adilene that he was working with a company that wanted to automate the remitting of sales tax - show and/or pull amounts - even daily or every week - based on reports and oversight. Some of these companies really want to get their taxes and/or their cut as quickly as possible.

- Adilene loves to daydream. That's fun!

- We talked about GPS tracking - even for horses (animals) or other high value items

- GPS delivery stuff

- Tons of 3rd party solutions - already integrated as options - we are open to do more - as needed.

- Talks about sharing the cost with the customers - having them pay for custom development - we have a standard package and then they customize things beyond that.

- Bottleneck in training and deployment

- User guide and steps to success - training and education

- Help files and archiving some new videos

- Steve was talking about influencers (people) - promoting products and features - that would be pretty cool - YouTube shorts and helping people through quick videos and such.

- Being diverse and still able to penetrate certain markets. Being focused can really help with that, but if you can be diverse and still penetrate verticals and business models, that could be really cool. Lots of talk about industry specific skins and white labeling options.

- You really gain when you can meet the same need or the same challenge over and over again - selling the product with or for the customer need

- Prove the model and then keep adding on

- Find a problem and then address that client need - do that over and over again

- Dedicate a salesperson on a single vertical - help them to focus

- More talks about white labeling and industry specific skins - custom software for a specific industry or business vertical.

- We were talking about investments and such. Steve was pitching the idea of buying in at some value (a percentage or share amount) and then investing monies on the balance sheet. Instead of just normal invest and let the company choose how to use the monies, invest and have some control on what it is used for and how to structure a payback system, even up to 50% of new revenue from that investment. Rates and deals may vary, but that is what he was pitching. That could be really fun. I personally know a few places (inside of adilas or other services that are needed) that could use some loving and could provide some sweet paybacks.

Phone call with Steve to talk about updates and needs. Light prep work for a quick backend switch for Sean and the New Mexico folks (soccer club).

Phone call with Steve. Going over some updates and plans. Talking about clients, their needs, and what we are planning to do to fill those needs.

Going over brochures and contacts from the BNI meeting. Checking out a few websites and texting back and forth with different people. I have two meetings setup for next week and the week after. Trying to get out of the office a bit more.

On the phone with Steve. Talking about a new discount modal pop-up for the mini scan cart. Basically, a quick way to discount a single line item. We talked about a number of ideas and options. Looking to keep it really simple. We also spent a bunch of time talking about general adilas business stuff. Shares, percentages, and growth strategies. Making some plans.

Working with Steve. Small work session. Showing him the upload tool for uploading a CSV file for new parts/items with field mapping steps. I then showed Steve the Knox report (custom sales breakdown report) and some new changes that we had made. Next, we switched over and were talking about auto loyalty points and adding that code (new custom feature for a client) via black box stuff.

Looking into the mini display cart and some new settings. Steve and I did a little work session and we added in new settings for using an element of time to help store images for the mini display screen for the cart (dual screens - one facing the customer and one facing the staff member or associate). We roughed out the settings and got it working. He is going to go back in and make small tweaks and do some clean-up.

Meeting with Steve and Cory. Going over budgets and funding stuff. Looking for ROI (return on investment). Talking about spending money on different people and things. It's getting rough.

Steve had to jump on another call. Just Cory and I talking... talking about payroll and other projects. Cory was asking me to say "no" to other people who were asking for my time or attention and take care of the priorities that really need to be done first. How much it really takes to get things over the finish line. So many things come down to a simple setting, yes/no, do this, do that, work this way or whatever. It can get tricky.

Steve joined us again and we jumped back on to budgets. Talking about price increases, reoccurring revenue, etc. Talking about efficiency and getting more ROI. Talking about how much it takes to get a client fully onboard and fully happy and rolling (paying and happy). Talking about how to bring more revenue in. Thinking about the long game. We are being scrappy and doing a lot of bootstrapping (creative ways to make things happen).

Alan joined the meeting, and we were talking about his needs and where we are at. Everybody is running out of options. More budget talking.

Phone call with Steve about a huge data dump for a client. 30-45 systems (corporations), 5-10 year's worth of data, with tons of reports and exports. Thinking about 3 options - 1. Kelly doing it all (consulting fees). 2. Reduced storage options. 3. New reports or bulk export tools (csv or excel format). Talking about automation options from Wayne and how he would possibly do it. He would be doing things on the server level. Talking about possible automation ways that we could go with and what that might look like.

Quick meeting with Steve to go over things. We talked about the Canada deal, where that is at, what we have learned, and what are plans are. We also talked about ecommerce needs and little tweaks that we can make there. We keep refining things every day. That's part of what we do.

Recording notes from 2/10/25 to 2/11/25.

Meeting with Yogen Fruz about the website and POS system. Six of us on the call together, talking about where we are at, and how to do things. Josh, Steve, and I were on the meeting from adilas. Light talks and small frustrations, both sides. This has gone on quite a while (over five months). Trying to figure out the next steps. We kept going back and forth between the POS and the website. They are somewhat tied together (projects as a whole). It seems like timing and figuring out comfort levels is the next logical step. Still in the waiting game a bit. I showed them a quick view of the new Knox report.

As a side note, when we were talking about the website... we are proposing a combo of a fully integrated POS system, CMS (content management system), and eCommerce. That's a pretty powerful combo, when you mix all of those pieces together. Other companies either do one or the other or have one or more plug-ins to connect with the other pieces. If any outside changes are needed, they have to be directly involved, meaning the outside vendors or companies. This happens over and over again (with other companies) vs a CMS that lets the users control things from an integrated system like adilas.

Phone call with Bryan. He has a customer that is requesting ecommerce functions with a standard item (parent item) and then being able to just pick a size or a color. We do that with sub inventory, but need to make it easier for customer facing ecommerce functionality. Those two things are super common (sizes and colors).

Paying bills and going through emails. Jumped on a GoToMeeting session with Steve to go over some updates and look at a database update question for the inventory snapshot stuff.

Working on the custom sales breakdown stuff for Phillip. Small little tweaks and starting to work on the math stuff (percentages).

Bryan jumped on with Steve and I and had a bunch of questions about recipe/builds and how to convert a bottle (item marked as an each) into ounces in order to use certain products in bulk. We showed him some new stuff and how to do advanced adds on PO line items.

Working with Steve. Working with the inventory snapshot code/database and back figuring the data. We are planning on harnessing user clicks to help with catching up the rolling part/item quantity. We worked on adding in a threshold value and a quantity check to help us watch and monitor which items have been updated. Multi-hour building and work session.

Meeting with Wayne and Alan to go over options for database configuration options (code words... datasource project or bus to motorcycle or world building project). Light catch-up. Wayne was going over options for running a base service to figure out the corp and datasource (what database to use). The old datasource is the default.

Talking about efficiency and combining corporations and servers. Going over scenarios. The idea is to make the code and the schema unaware (more open - able to connect to any database). For me, I have a bunch of older notes under clustering, solar systems, and galaxies (all kinds of cross-schema options).

For us, internally, database updates may get more crazy, especially for our developers. Talking about possible load balancing stuff. We were talking about master databases, sub databases, and efficiency questions.

- Wayne was recommending a more company related approach (which businesses are connected or have a relationship) vs corp related (single worlds, all by themselves). Widen it out a bit.

- Wayne's branch... WLA/DynamicDSN

- Alan was talking about a wish list to help update things from one spot (one page or one server) vs logging into each server to run it on each server (current process).

- Wayne already uses a script (test script) to run his database updates. He doesn't like to do things over and over again. He would rather build a script or make a tool to do that.

- Wayne wants Alan and I to help pitch it to Steve and Cory.

- We may need to look at and check the edge cases (on the datasource look-up project). They were talking about some known caching issues.

- Places that we need to check... (list of us, internally)
>> shop folder - there is some session stuff but it is different then the top_secret stuff.
>> web folder - API's - most pass in a corp key that we can figure out a corp id number from.
>> public folder - hardcoded per page or FORM or URL scoped controlled.
>> temp folder - hardcoded per page or FORM or URL scoped controlled.
>> database_updates folder - may need to query (get all known datasources), then loop and do updates per schema. basically, layer and nest things vs just plain doing a single update.
>> check the process to create a new corp - some questions there (we are currently using the main datasource and building tables and inputting values based on our create new corp routines).
>> caching - check the daos, services, and cfc's - make sure we do what we need to here to make this still function correctly.
>> search for corp_id IN (? whatever the list or arguments are) - multi corp queries. Maybe be able to set a temporary master/primary corp id where needed.

Saturday morning meeting with Steve. He and I going over the inventory snapshot project. Lots of drawing and going over ideas and concepts. This is basically a mini aggregate (sum or count) of the parts and items per item and per location. We then started to code our own version of the inventory snapshot. We were putting new code on some of our internal components where we were updating item quantities.

As we were working, we started talking about machine learning and all of the new AI stuff. We have so much data... that is huge. We have to deal with both machines and people. Wach one may need different sets of data. We briefly talked about banks and getting transactions as they happen (in the field and at certain locations) and how to make that stuff hit our database (expenses and deposits automatically hitting the adilas system per corp as setup).

The rest of the session was building out the code and then testing and debugging. We merged the new changes into the master branch and it will auto deploy tomorrow morning.

Meeting with Steve to go over ecommerce stuff. Trying to debug some code on sub inventory attributes. Got stuck on some checkboxes that wouldn't work or were having issues. Trying lots of stuff. Multiple attempts. We'll have to come back to that.

Phone call with Dave Forbis. He was asking a number of questions. Lots of questions about social media connections and API's, on demand print stuff, and banks that we have integrated with (for pulling back deposits and expenses to help with bank reconciliation stuff). We also talked about old projects for campaign tracking and GPS tracking. He was looking around and trying to get things lined up. Good call.

Emails and reviewing tons of PDF files from Hamid, for the business functions, on the presentation gallery.

Quick meeting with Steve to look into an ecommerce bug. We found some poorly placed div tags (HTML code) and got it working again.

Zoom meeting with Sean, Bryan, and Steve from the adilas team. We were meeting with Cody from Alliance - a civil engineering division out of northern Utah. Going over project time tracking and invoicing. Permission templates.

Small idea from Cody - be able to flip flop subs of time from the main elements of time to other elements of time. For example, say your guys are clocking in/out on a certain project. They make a mistake and it, the timecard, should have been on a different project. Currently, you have to make that record inactive and copy/paste the info to the correct spot. They would like it if you could just change the main time id (project id) for the sub and then it virtually gets moved to the correct spot. I made some notes on my to do list, on my computer. Great idea!

Working with Russell. Doing some planning. We had to break a bigger document into smaller pieces (categories and sub categories). He was getting me into using notion and some of the cool things that you can do with that program - robust web tools. Light planning on the custom sales breakdown report for Phillip. Working in Adobe XD and doing some layout stuff. Steve joined us and we got into a small bug out in ecommerce land. Russell had to go, but it was good to get Steve on there with Russell again. It's been awhile since those two have met up and talked.

Meeting with Cody. Going over the PDF reader code that he wrote (parsing and stripping out data values for tax withholdings). We then jumped over and started looking for a new project for Cody. He ran a global find and replace for the list contains vs the list find functions. I need to check that out and get it all merged into the system or the master branch.

After that, we switched over and he will be working on the total time for sub dates and times. I showed him some existing payroll stuff and we spent a bit of time looking around and finding the different pieces of the puzzle. His project will be in the sub dates and time, not in payroll, but they are similar (calculating total time). We also did some just in time project management (our specialty) and planning. This project was started by Steve and Eric last March of 2024, and it is already 3/4 of the way done but it needs some light detail work. I'm hoping that Cody will be able to follow things along and help make it just a little bit tighter, which will allow us to fully use it better.

Emails and playing with percentage ownership changes (Microsoft Excel stuff). Paying bills. Two phone calls with Steve to go over percentages. Going over Yogen Fruz stuff. Talking about software and hardware integrations. Even talking about possible middleware application for a print queue or print log. Maybe tying in the print log to Windows or Android specific middleware or software. After that, spent some time talking to Heather (my wife) about updates on different subjects. Recording notes.

Working with Steve and Chuck. Going over reports. Working on and building the dream - that's what we are pitching and selling. Talking about showing them the mock-ups. Helping to put a visual with the pitch. Steve has been kissing a lot of frogs (potential investors and venture capital stuff). He's hoping to find the one (just being silly... like a fairytale). Sell the sizzle...

Switched over to the website proposal and series of questions. I took a bunch of notes here:

- Need for website to be tied into the inventory management system.

- They want a CMS (content management system). They want to control all of the pieces and be able to make the changes. Steve was pitching our own mini CMS type system. Chuck was pitching WordPress with some plugins.

- Talking about running all of the services (one-place shop) for the client. We are your dev team.

- We have so many pieces that are close... they just aren't fully done.

- We may have to help them with a mashup right now. Then, later on, we may be able to build out all of the pieces for them (internally). Chuck is worried about the time to really build it out (right now).

- The power of mock-ups. If you have 14 different plugins... to install, configure, and manage, it can get messy. If WordPress goes down, it makes us look bad.

- Maybe pitch two options... one for WordPress and plugins route - the other, just adilas, we build it all and keep it all up for you.

- If we build it, things take time. real time is needed for planning, building, and we need real budgets, etc.

- We really need to control all of the pieces. They want full control and speed to market. If we build it internally, we have assets that we can throw at it. Basically, fully outsource it to us and we will run with it. We are your one stop dev shop.

- Maintenance fees to keep things going.

- Back to selling them the dream.

- We will save you so much time and effort by systemizing things.

- Talking about social media... that (social media posts and such) becomes the changeable web content, the main website is more of the backend stable piece, that's where you order and interact with the actual products and inventory.

- Talking about real native "mini" apps that tie into the adilas system backend. Keep them small, open or create the doorways, we will go from there. Basically, just a mini portal into their world. Mobile first approach.

Chuck had to take off. Steve and I were talking about inventory thresholds. We were also talking about the future of where things are heading. Lots of mobile stuff. Everybody wants efficiency. Josh is really helping to push on things. That is huge.

Small side note - Brandon was riding snowboards with Aaron Hill, on Friday 1/10/25, up at Beaver Mountain. They were talking about ways to make their clients sticky. When they had to go their different directions, for the day. Here is what Aaron said to Brandon - "Really make those clients sticky! Win that battle! Make it good!". Great advice!

Various meetings, throughout the day.

On a Zoom meeting with Cory. Looking over some gram control settings.

On a meeting with Cody. He got a few things tweaked for the check write stuff. Looking at pagination on the label builder. He was also showing me some work that he was doing on the infinite scroll (scroll, get more results, scroll, get more results, repeat until finished).

Working with Steve. Debugging things. Found problem with list contains vs list find functions. Pushed up the new file.

Emails and reading over a response from Chuck about a custom website.

Meeting with Bryan and Sean. Going over recipe/builds and internal build PO's. They are dealing with a single inbound ingredient and multiple possible outputs. They were looking for help with math and automating things. Lots of back and forth between all of us. Good conversations. They are going to go play with the different pieces, settings, and existing tools to figure out options, work arounds, and needs. They will be meeting with Steve tomorrow to go deeper into some of the pieces.

Switched to Yogen Fruz stuff. Getting into custom reports and cash flows. Talking about daily closeouts - sweeping the floor. Steve was saying, let's help them so that certain things never happen (helping us/them stay within the lines). We also talked about being able to help them with their inventory (body shop line - bath and hair products - different company). Steve and Josh are setting things up to create some budgets and then work through those things (list of tasks, projects, and estimates). I spent some time and pushed up a video of part of our conversation. See attached.

Meeting with Steve and Cody. We were talking about current needs for the adilas system. Here are some of my notes:

- Going over forms, accordions, modals (popup windows), client-side validation, ease of use, dashboards, custom homepages, buttons, containers, canvases and pallets (like an artist with paint - a pallet or possible colors and tools), asynchronous loading, preset pages that load certain things, sizing things, moving things around, etc.

- New custom homes... Imagine using the new drag and drop interface (what Cody is working on) and then be able to swap out our homepages (existing homepages) with new custom home pages (built by the users or as an industry specific skin or white label). Eventually you could do lower-level pages as well. Think full custom... for the whole system.

- Getting Chuck involved, right off the bat. Chuck is the frontend designer. Responsive design (phones, tablets, and other devices).

- Where we are heading... not just a new label builder, we are building packaging, designs, full layouts, etc. Steve was saying that if we offer a custom and internal solution, we could potentially help with overcoming minimums on custom design layouts and print projects. Almost like a print shop. Making dynamic graphics. Making packaging with the correct information right on it, just making as many as needed. Basically, you could skip the full packaging and then adding a label on top of that. If people want to print other things... then let's talk about it. This could be making gift cards, employee cards, custom packaging, 3D printing, etc. Not just for labels, it could be for more.

- Light looking at sheets and sheet labels. We want to launch an MVP (minimal viable product) and then sort of tease them (our clients) going forward. help them catch and see the vision. If you can give our clients a vision of one, they can see the possibilities of doing thousands.

- It's all about efficiency, ease of use, helping them get into the correct direction. We talked about galleries and ways to add the data (whatever that is) to the different things or places. Almost a bunch of options and pick and choose what you want and how you want to organize your data.

- I will have the responsibility of hooking up both Chuck and Cody. Letting them get together to go over some gui (ui/ux) stuff (graphical user interface or user experience stuff).

- Steve was talking about how so many people have tons and tons of photos and helping them organize them (in bulk). This was just an idea. It's just data and some management type things. Maybe some bulk galleries with notes, flags, tags, and ways to organize things. It's all just data... print it, organize it, share it, etc. More talk on flagging and tagging items.

I thought that it was a great meeting. Steve and Cody were having fun and doing some great brainstorming stuff. I was chiming in every once in a while, but it was mostly Steve and Cody. Super fun!