Matt from the Cache Food Pantry - Meet at 2 pm for a live demo and meeting

Adilas Pitch Options:

Web link - adilas_pitch.pdf - Visual pitch containing 11 slides about what we do at adilas. This is a PDF version of the PowerPoint slides.

Web link - adilas_pitch.pptx - PowerPoint slides - 11 slides - presentation ready

Web link - adilas_3_part_pitch.pdf - Text version of the pitch. It covers an introduction, what we have available today, and where we are heading - all in simple text/paragraph type form.

If you just need some quick web images, see attached for some screenshots of the presentation.

Meeting with Shannon. Talking about outcomes, intent, effort, and willingness to keep trying. It's a good thing that we have tomorrows (plural). We are all trying. Less is almost more in a way, talking about confidence - what you show or what you feel you need to convey. We spent the whole time redoing some of the graphics on the 3-part pitch and presentation. Changing graphics inside of Affinity and then placing them inside of PowerPoint. Wonderful session and she helped me simplify considerably, that is huge.

Shannon is going to take a break, she is in her last trimester for her third child. She is due in just a couple of weeks. I am so grateful for her help.

Recording notes from 6/19/26. I'm a little bit behind. Thank goodness for post-it notes and quick notes on a text file on my laptop.

Working with Brayn. We went over the quick pitch video that I made last Saturday evening. I will refine it, but I have to start somewhere. He then showed me what he does when doing a pitch. He uses the main adilas web page and then he jumps into the presentation gallery to go over functionality. After that, we jumped into his AI project and worked for a bit. He had just changed some things before jumping on with me. We may have to roll those back and then redo those changes. The new changes broke his current functionality. He is going to rework some things and then get back with me. Totally doable, just forced under a time constraint. It will work out great.

A couple of different sessions on Saturday evening. Working on the adilas PowerPoint presentation slides and then a video. Spent most of the time working on the graphics and collages for the presentation. added a number of new slides. See attached for some of the new images and graphics. Finished up the first round of video. Great start.

For the note, this video was made around 11:45 pm on Saturday night... No practice, just a one-take wonder. Please don't judge me too harshly. Kinda a rush job - Still kinda fun - Web link - 7 minute adilas pitch video (video is out on Google drive).

Light pitch video prep session. Planning and then prep work for recording a small video. New images for Brandon and Steve. Putting together a small PowerPoint slide deck. More work on the PowerPoint presentation. Working on slides for systems, problems, and solutions.

Working with Bryan. Checking out his code that he was working on for the adilas AI agent. He was showing me the search functionality and how things work. Talking about actions, logs, suggestions, and histories. Trying to help get the agent live. He has some chat sessions (chat docs) with ChatGPT that go over tasks, requirements, and other help in both building and testing it. Going over voice and sound responses and TTS (text to speech) stuff.

Talking about projects that are only half done or half baked. It hurts so hard when you get pulled out or pulled off of a project. Especially when you see the benefit of what it can do. We also talked about the education and how to help other people learn or know what to do to use it. Shooting for the MVP on this project. We can circle back around again later. Bryan was talking about a master's program, working super hard, fully dedicated, becoming a master in a specific subject, then graduating, moving on, and leaving that project. Bryan was saying that he has taken month long vacations from things, based on funds and money. Doors keep opening up.

Meeting with Hamid. We looked over some of his progress. He is working on the adilas API site. He has been working with ChatGPT. He's making progress but also having to trim things back. AI keeps wanting to push things further and further along, beyond his abilities. He is trying to figure out those push/pull area and help it help him get what he really wants. We are just looking for a simple site, but it has him clear out in some other servers, tech stacks, and frameworks. We talked about trimming it back a bit and going with some of his original ideas and concepts.

Working with Russell and Abby. Talking about AI video generation and where things are going. Working through the page options and documentation, from our current joint project. We are documenting the pages so that we know how to use them. We started paring down the dev docs to only what we actually needed. The original document had some extra pages so that we could test the search and mock-up what it would look like as a fully functional documentation system. Starting to pare things down and refine it.

Working with Abby. She gave me some new adilas data engine images. See attached. We also talked about being consistent and how to do that with so many different topics and concepts. We decided that we are going for the gallery type approach or style. Not exactly the same but at least a similar feel and flavor.

Meeting with Shannon. Talking about systems and systems thinking. Fun topics. Here are some of my other notes.

- We have a number of half done projects. We keep chipping away at that, but it does make a mess, if nothing else, it kinda looks less attractive.

- MVP (minimal viable product) - have we passed that yet? Or not quite hit it? Where are we planning on landing? Some of those are variables. Technically, we have been selling our product since 2008, are we there yet or is it still missing a few things? What does that look like?

- Talking about progression. Love/hate relationship with that topic. It takes a lot to really turn progression into output.

- Custom code - Without saying it, this has been our model and mode of operation. Follow the money, but that does delay of the bigger picture. Custom is our superpower but it is also our Achillies heel (opposite sides of the coin).

- Even though we are making money right now, it limits sales in the future (due to the main product not being fully done).

- Talking about the jellyfish model and breaking things up into separate business entities. Adilas, adilas shop, adilas university, adilas marketplace, etc. They could all operate under one umbrella, but there are changes that are needed. In a way, I would love to get those pieces more independent and get them the resources that they need - time, money, talent, people, budgets, etc. At that point, turn them loose and see what they could do.

- Talking to Shannon about schedules. She is expecting a baby and is getting close. We may only do a few more sessions before she has to take a break.

- Talking about bounding boxes... decision fatigue, option fatigue, and how systems allow for unlimited usage but that may overwhelm people as well. People want things to be easier, but seeing all of the interconnected pieces may overwhelm people and clients.

- Building bridges and being able to start simple and then scale up. We have some fun AI chats about possible simple interfaces (bridges) that we could build. I would love to head in that direction. Here are a couple of quick links: Web link - MVP POS bridge or Web link - MVP time tracking bridge

- Stepping stones and taking the next step. We keep doing that over and over again. We can't jump any faster or higher than anyone else, but we keep adding in the next steps and then we can make those next steps. That has been fun.

- Shannon and I spent some time going over the adilas core concepts overview document. We went through some of the topics of systems, vision, and tech, tools, and maintenance.

- Talking about needs... Shannon was helping me to see that Steve is basically saying, I want a life preserver or a boat, not a plan about how not to get into the drink... :) Immediate action is needed. Not someone who says I can make that or here is what I think will help. Going back to the custom code and half done projects, I feel like we are getting sucked into a trap and delaying future sales by just servicing the current needs. There needs to be a balance and a mix. I don't want to deny that we need to service our customers, but we have been doing that for 20+ years. It is wearing us down without anything to replenish the reserves.

- People have a hard time seeing why something won't work for someone else... We tend to cascade our own strengths and abilities on to others. Certain things work for us or comes naturally to us, but it's hard to see that not working or being natural for someone else.

- Survival needs - trying to avoid pain in places that have caused suffering in prior times. Big motivator... not always positive and comes with some hurt and trauma. There are also some good lessons that we can learn.

- Shannon was saying that she was reading in Isiah and a scripture that said something like - you have sold yourselves for naught - you have chosen bondage due to fear - something that may not have been as big of a deal but you made it into a big deal. It all comes down to choices, perceptions, fears, faith, and other variables or emotions. We live in an interesting world.

Emails and light tech support. Checking out the data 39 server for a client. Recording notes from my meeting with Steve.

After that, meeting with my dad... It may be time to stone soup it (let multiple people contribute to the mix)... making a list of people to go talk to. I told my dad that Steve challenged me to get the car out of the garage. My day was saying and/or asking... load my lips... what am I supposed to say? People are willing to help sell this thing, but they don't know what to say and/or do. We need to help them. It is currently too broad and wide open. They need some direction.

Working with Steve and going over things. Mostly we were talking about sales, current status of things, and projects. We also spent some time talking about options for working with Andrew. Here are some of my notes. Somewhat all over the place.

- Steve was saying that if someone says no, he likes to ask why wouldn't you choose our software?

- If you are doing sales, you need to ask closing questions. If you don't ask those questions, you never get a firm yes or no answer.

- Making sure that the fit is good. If it doesn't fit, meaning what we have to what they are wanting, you just move on.

- Steve keeps having to do more Metrc updates - statewide tracking system.

- Part of the game is dealing with clients and helping them to mix and build things.

- Levels of comfort with functionality... how deep do we go? Often, we have a lot to offer and say. Some people don't really care. They just want to make sure that it gets done.

- The customer is always right

- We need to generate more revenue and really trying to sell this stuff, meaning adilas products and functionality.

- Steve was talking about some older discussion with a business advisor. Maybe we need to talk with him again and see what he says. Steve is betting that he will start talking about sales and revenue.

- For sales - it usually ends up boiling down to like, trust, and respect.

- Micro management to the crazy level.

- People seem to object to the look and feel.

- Get out there... Somebody needs to talk to somebody - sales.

- Steve likes to focus on getting people on the system and then helping them mold the system with input, ideas, and funding.

- Talking about AI and gaining from that tool.

- As a challenge, Steve was saying - take it out of the garage and go test it. Challenge to us... get somebody and bring them to the table.

- 20% commissions. Normal for sales.

- The ideal would be an angel investor of some sort.

- Talking about sales. We spent some time talking about Josh and Andrew. They are both out there stirring the pot a bit. They have different styles, but they talk to people.

- Helping and doing some sales - get out there.

- Back to updates and waiting until the last minute to do those updates. This was dealing with maintenance on the system. Sometimes we know about something, but we wait until it really needs to be fixed. It depends on funding and availability of the developers.

- You have to keep asking... Who is going to pay for all of this?

- Steve was talking about what he is seeing... Real customers that want something. That is where he is working right now.

- Level of control. What level do we need or does that matter?

- We need help inside

- Steve was saying this to me... Don't have a major freakout if you can't find what you are looking for... I think that this is his way of trying to help me set my own expectations.

- What have investors been saying... adilas is worth 2-5 million, need to be in a vertical (set business or industry), and reoccurring revenue needs to be higher.

- Dealing with what investors have been saying... What is our response to that? How will our plan work? These were discussion topics between Steve and I.

- He gave me a homework assignment to rework the sales doc. This is the document between Steve and Andrew.

Meeting with Shannon. Going over older documents from Andrew. We reviewed quite a few of them. Talking about the progression and how we feel about certain things. Talking about direction and where and what to do. 

Defining work/contribution parameters:

- How to assess actual involvment/contributions?

- If contirbutions and help ceases - how will that affect the arrangment if revenue continues to increase by other means?

- No employment agreements

- This also does not mean management or leadership over all sales and marketing - CMO

Swapped out a graphic on the adilas 3-part pitch. Converted it to a PDF. Then sent it to a guy via email. I'll do more of that when I get some time. I just wanted to get it out today before I go on a small trip with friends. See attached.

Web link - adilas_3_part_pitch.pdf

Meeting with Bryan about AI stuff. Going over his AI to do list. He was showing me around a bit. He is doing a great job. We bounced around to a number of places and such. It still needs some work, but I was impressed. Hopefully the next step is helping it get live, even if it isn't fully done.

Phone call with Andrew. He wants to be the main sales and marketing guy for adilas. Steve had kicked me over a document that had some strategies and breakdowns in it. I had read through it and then got on a meeting with Steve to talk about ideas and options. I asked Andrew about some of those things and we chatted. Here are some of my notes:

- He would like to be a 15-20% co-owner in adilas. We also talked about a proposed 20% commission on new sales. He would like to focus on sales, marketing, and overall business strategy. He would like a small team of a few people to help him.

- One of his primary focuses would be on automation and seeing what we can automate. Ideally, almost every task, in one way or another.

- We are a tech company and need to be future thinking - AI levels.

- With our team, he wants to know what we are good at, as well as what we are not good at? Trying to figure out where everybody fits.

- Andrew was pitching a small board or council type scenario, to help with decisions and direction. Currently, most of those decisions are done by Steve or Steve with my help or Cory's help. He thought that it would be good to get that divided into an actual small board.

- We talked about some contingencies to the document that he and Steve have been working on. Fairly small changes, but better definition on certain things and expectations.

- I pitched him on the white label idea. He didn't really like that direction. He wants to work directly with us, under our main umbrella vs on the side.

- As we were talking about him, his group, and other possible investment groups, he was saying that as the lead sales and marketing guy, he would have some major say in who and how things would go down. Currently, he is not in that position. We are still kinda bouncing around a bit.

- We left off that I would talk to Steve again and then get back with him.

Meeting with Hamid. Touching base and showing each other progress. He is working with AI to do some website coding. I am working with AI to do some graphics. Comparing notes and checking in. He needed some logo files. I passed him over a few new ones. Light code changes on his side. We will hit it again next week.

Recording notes and then a phone call with Steve. Talking about salespeople and where we are heading. We kicked around some ideas and talked about other things, projects, possible deals, etc. Nice phone call. I told him that I would call and talk with Andrew tomorrow and then get back and report back to Steve on how that went.

Working on graphics for the desired outcomes, end products or results of using adilas as a toolset. Spent some time working with ChatGPT to try to have it help do some small, detailed changes. See attached for some images to help prompt it to make the correct changes. See this chat session with ChatGPT for more information. https://chatgpt.com/share/6a343839-cafc-83e8-8043-b11163514bf4

Also, I got a document from Steve to look over. I read it and sent him some suggestions via text. He responded that he wanted me to make the changes and then send it out to Andrew. I told him that I would call him later this afternoon.

Working on graphics. Jumped on a meeting with Shannon and got some input on the graphics that I am working on. We then started working on the vision section of the adilas core concepts overview document. That document is still in brainstorming mode, but making progress. See attached for our current progress.

Recording notes and light graphic work. Got a few new images from Abby dealing with bridging the gap between operations and accounting. See attached. Emails and then working on the desired outcome graphic. See attached for the progression of that graphic. I started with ChatGPT and then tweaked it and then had AI give it another go. Interesting workflow.

Small note from ChatGPT as I was working:

One thing I've noticed across the work you've shown me over the last few months is that the strongest Adilas graphics usually emerge when three different perspectives get mixed together:

You --> the system architect ("Does this represent the concept correctly?")

Shannon --> the communicator ("Will people understand this?")

Abby --> the designer/storyteller ("Can it be simplified and presented better?")

Heather --> often the practical/business perspective ("Does this feel useful and relatable?")

That combination tends to produce better results than any one person working alone.

Here is the chat session link for the graphics: https://chatgpt.com/share/6a331774-7da0-83e8-8ed6-8259f912e245

Recording notes and jumping back in on topics and graphics from the end of last week. Trying to record parts of the story. Doing some photo retouch on the advanced mixing and blending concepts for world building. Added a couple of graphics to element of time # 12939 and also to the adilas ai assets page.

Working with Shannon. We were talking about pain vs suffering and even how that can roll over into shame and other things. Working on the core concepts overview document. We couldn't decide who the actual audience was. So, I claimed it. I wanted a spot where we could brainstorm a bunch of ideas and then we will filter things down into beginner, intermediate, advanced, and maybe even a techy level, if needed. We read through some sections and did some more brainstorming and filtering things down.

Shannon and I had some good conversations and were able to talk about vision, being overwhelmed, depressed, doubt, fear, and how to keep going, even when faced with some of those other emotions and/or realities. Very interesting. It helps to have a buddy along for the journey. By ourselves, we tend to get stuck in the mud and want to give up.

Working with Abby and Russell. Working on responsive layouts. Most of the session was small tweaks and then retesting things. I've been saying this, but we really are getting close. We talked a lot about CSS and learning and knowing what is possible. If you learn it, you need to use it. If not, it goes away. The secret is learning and applying it.

Working with Abby. Looking at new graphics. She isn't done yet, but new graphics for bridges, engines, and she also gave me some feedback on my stuff. One of her recommendations was to break it, a bigger world building graphic, into smaller parts and pieces. Basically, break it into phases. See element of time 12939 for what that suggestion looks like, after I finished it up on 6/16/26 (Tuesday).

Working with ChatGPT on some images for simple world building. Changed the flavor of the graphics to more of a business like presentation. There is some great info on this chat session. Also, some great new graphics. See attached. Ran out of time to get them fully integrated, but that will happen next week. Good stuff! This one was fun! https://chatgpt.com/share/6a2e2fca-99c4-83e8-8f5c-a96a4da3584d

Recording notes and doing some prep work. Pulled out the smaller video recorder analogy from the adilas core concepts overview document. Ended up working on some adilas graphics for the adilas 3-part pitch. I got lots of samples. See attached.

New chat session with ChatGPT on the adilas graphics for the world building. Lots of work with funnels and mixing concepts. Here is the link: https://chatgpt.com/share/6a2ca267-cb5c-83e8-bc64-2c68ceeb9ada

Recording notes from 6/10/26 to 6/11/26.

Meeting with Hamid. He is working on the adilas API site called "play at the wall" website. He is using ChatGPT and VS code to do the site. We spent the whole session working through prompts, code, making changes, and light testing.

Bryan is working with Gemini and ChatGPT to help build in AI for adilas. He is trying to help make it interact with adilas through the quick search and direct prompts. His progress is looking good. I was impressed. I gave him a number of new pages to check, including the adilas mini API. He didn't know about that yet. We were building it out back in December of 2025 when we were working with the Nxtlinq folks and their AI agent. Anyways, gave him some new resources and talked about things. He is making great progress. Towards the end, we talked about things and plans for the next six months.

Showing Shannon the visual journey that I shared with ChatGPT (web link). We were talking about how long does it take to explain it (adilas) and how long to really get it? Talking about the green overlay graphics and how they show that we use the whole system to provide the functions that we have. Here are some of my other notes from the work session:

- Show different interfaces, chooser options (custom homepages), quick search, etc.

- Help them (our users and clients) see the progression - they won't catch everything the first time. Using the graphics... help them get it... help them catch the vision... oh, I get it... - that is awesome.

- Switched over to the big core concepts overview document. We spent most of the rest of the session reading and doing light editing there on that document. See attached for the progress. We only got about halfway through.

- Talking about solving the Rubik's cube - there are many different ways - either by math, complex algorithms, set patterns, or by story. I think that the story method is easier, at least it makes it easier for me. We are geared for stories.

- Just being silly... Shannon was saying that the word history could be broken into... "his story" (small stretch but fun).

- Bring in that human element.

- I want to pull out the video recorder story. I liked it. It might be fun as a standalone story. See attached.

- We read through the first couple core concepts sections.

- Desired outcomes solve the major pain points... I would like to do an infographic on pain. If you can solve the pain, they will invest time and effort into the solution. That's the hope.

- Nobody really wants all of this stuff (text, documentation, graphics, and info), until they think that I (we) can solve their pain or I (we) have the solution. That's the motivation.

- Here are some notes from the chat session from yesterday:

Level 1 — Features
What do you need?
CRM
Inventory
Scheduling
Accounting
Reporting

Level 2 — Results
Why do you need it?
Operational Control
Customer Awareness
Financial Visibility
Accountability
Process Efficiency

Level 3 — Architecture
How does it happen?
Connected Data
Flex Grid
Operations Lead Accounting
Data Assembly Line
Time-Based Architecture

Level 4 — Philosophy
Why was it built this way?
Systems Thinking
World Building
Results-Based Design
Challenging Tradition
Built By Dreamers

---

Alternate adilas formula wording... normal adilas formula: Mix(functions + players + concepts) = Results

Use Players
Mix Functions
Apply Concepts
Create Results

---

My role as a teacher and translator - teaching complex topics

Multiple sessions. Working on the what makes adilas different graphic series. Ended up pulling in tons of older graphics and working on creating a visual language for adilas. Fun session. We already have one, meaning a visual language, it just needs to be brought into the light a little bit more. Working with Heather on the 3-part pitch. Light edits and changes. Reading over some other documents. More work with AI on what makes us different and the adilas visual language. Finished up the chat session on what makes adilas different.

Two really good breakthroughs from this ChatGPT session.

1. Other companies sell modules and fixed features like CRM, POS, eCommerce, etc. We mix ingredients (players, functions, concepts) to get CRM, POS, and eCommerce. That is a completely different way of looking at software. You get the whole thing... then you mix and blend the ingredients, functions, and concepts to get what you want.

2. One of my personal roles is - I'm a teacher and translator between tech talk and deep concepts and how that really plays out for humans.

Here is the chat session link. It started out wanting to do a series of slides and/or graphics for what makes adilas different. By the time we got finished, it had some great stuff on the visual language and map of how adilas communicates and uses graphics. I loved the session. Here's the link: https://chatgpt.com/share/6a2a467c-9244-83e8-ba63-046be9536efe

Work session with Russell and Abby. We started into creating our own documentation for our own project. Ended up having to add some other pieces such as image captions, mobile menu views, and other small to do list items. It is so fun to watch how this unfolds and what it takes. We are around 45-50 hours into this project, with AI and with master Russell leading this project. This has been a great learning experience.

Working with Abby. She helped me on my layouts and graphics that I was working on. We wrote down some ideas. I will add/edit them later. I gave her some ideas on a new graphic that she is working on - the story of your business and video stuff. I sent her a copy of the core concepts overview document that Shannon and I were working on. It has a section that talks about how adilas records the story of your business, like a video camera. The goal for the new graphics is to show the concept of what we are doing. It isn't actual video that we record, it is data, histories, relationships, and transactions. However, the concept is the same... a record is being kept, and you can get back to it as needed.

Recording notes from the past couple of days (6/8/26 to 6/9/26). Working on a document of what makes us different. See attached.

Went into the Bridgerland Business and Innovation Hub with my mom and dad. We got the super deluxe tour from Sterling Petersen. He is the director of Custom Fit, there at the college. My dad used to work for that department before he retired. We got the full tour. My goal is to use some of the new facility for adilas stuff, later on. This was just a deeper tour. They have board rooms, classrooms, computer labs, bigger event venues, video shoot rooms, podcast recording booth, and even possible office space. Great location and great venue. Lots of potential.

Phone call with Bryan and touching base on things. We are going to meet up later this week to do some code review and some planning.

Working with Shannon. More work on the 3-part pitch. We then rolled into a small session on what makes us different. We built a small list and then ran that list through ChatGPT to help get a summary. We really want to focus on desired outcomes and results. See attached for some documents.

Here is the chat session link for what makes us different: https://chatgpt.com/share/6a283e11-7ba0-83e8-a0af-0dda34a0ea6f

Small list:
- All Data Is Live And Searchable
- Operations Lead Accounting
- World Building
- Results-Based Design
- Adilas Formula - Mix(Functions + Players + Concepts) = Results
- Flexibility & Adaptability
- Connected Data Relationships (Flex Grid)
- Time-Based Architecture
- Built By Dreamers
- Challenging Tradition
- 20+ Years of Organic Evolution

Working on final touches for the adilas 3-part pitch. Light graphic work and adding the graphics to the 3-part pitch. Switched over and did some light research on adilas stats, receivables, payables, liabilities, invoice counts, gross sales, etc. Ended up having ChatGPT help me with some images. Then working on a rework of an image to help it read better and match my style.

Email and some prep stuff. Then jumped on a Google meet with Wayne. We did some AWS roles and permission stuff. He is looking to add something new and needed a deeper admin option for setting up the new roles and permissions. He is really the server admin guy but some of the stuff is still tied to my user account. He was walking me through what to do. After that, we looked at some code, chatted about development, talked about testing, talked about AI and how that is going. Good little catch-up session. At the end, he had some adilas permission questions, and we went over some of that. I am grateful for his help.

Paying bills and entering in receipts. Emails to Wayne about AWS stuff. Recording notes from 6/3/26 to 6/6/26.

Recording notes from the last few days - 6/1/26 to 6/2/26. Added a couple of new graphics to the AI assets page.

Finishing up a graphic for the pitch launch flyer. Sent Matt an email with some info, a small paragraph about adilas, a small intro flyer, and the new graphic for their flyer. Here is the paragraph that I sent him. Somewhat of a modified elevator pitch.

Adilas is an all-inclusive business platform that brings the solutions you need to keep your business growing and running smoothly. The project started over two decades ago and is currently sold as a SaaS (software as a service) product. The two main areas of functionality are operations and accounting. That
combination provides a huge mix of functions and features. We offer a standard data platform product with options to extend and/or apply custom code on top of the application. We invite you to visit our website for more information - adilas.biz.

Meeting with Hamid. Going over what we have both been doing for the past few weeks. Both of us have been busy with different things. I showed him some of the AI and graphic stuff that I have been working on. We talked about setting aside some time for the pitch launch in July. Catching up and planning to meet up again next week. He is going to keep working on the new mini website for the adilas API's - play at the wall.

Work session with Abby. Got the adilas logos - authoring files. Talking about life and how there really is an abundant model. Counting your blessings. Working on the bridging the gap image. Looks great. See attached. She also helped me do a few more tweaks to the 3 tips from Steve graphic.

Working with Shannon. Going over graphics, new changes, and full review on the 3-part pitch. We reread the document a number of time and even talked about some visuals. See attached for the current version.

Helping Abby with some basic HTML. Working with Russell on data tool tips and other small features. Working on adding in tags and tag searching. Planning, testing, playing with skewing images for screen captures and other practice topics. Good work session.

Site from Russell - his portfolio. It has some good adilas stuff - https://mooredigitalsolutions.com/tag/adilas/

Working with Abby. Small work session on the train image and bridging the gap. See attached for some graphics. Small training with image selections and feathering (blurring selection lines for cropping images).

Phone call with Matt. He is with a company called Pitch Launch. He lives here locally in Northern Utah, where I am at. We met for lunch a couple of weeks ago. I was texting him and we jumped on a quick call. We went over some questions, and he wants me to make a small 3-5 minute video about what I would pitch if I were doing a pitch. We chatted for a bit. After that, I spent some time working on the future offerings part of the 3-part pitch. The future offerings is part 3 of the 3-part pitch. The other two parts are the introduction - who we are, and the second part is what we currently have to offer (current offerings - current adilas system).

AI can generate content like there is no tomorrow, but to get a fully finished and polished product or end result, it can become very difficult (or it just takes time). For example: I'm working on a flyer. I have generated over 60 graphics for the flyer. I don't like all of them. Some of them that I like, I have to lightly tweak, touch up, and/or alter.

Shannon and I were looking over a graphic dealing with problems that businesses face and/or have. Kinda funny, but I was showing Shannon and she flipped it on us (adilas). We are trying to help other businesses solve the same problems that we have, just in different ways. Anyways, Shannon was making a comparison of us (structure or company wise) to the graphic of the top problems that businesses face - we have the same problems. The graphic was dealing with disconnected data, but if you change the words (wherever your pain is), it is the same problem, just in a different format. Seriously, every one of the problems could be related to things that we are dealing with, every one of them. We read over the swot analysis and got some great ideas. See attached for a copy of the public facing SWOT analysis.

While we were reading, we pulled out some info about how the SWOT analysis document talked about Fracture or adilas lite. We were looking for information for the adilas 3-part pitch. Here are a few things that we pulled out.

The planned Fracture architecture aims to address this by allowing users to expose only the tools they need.

The Fracture project represents a major opportunity to simplify how users interact with the platform.

By allowing the system to reveal only relevant tools, Fracture can reduce complexity while maintaining the depth of the platform.

Later on, we were looking for some verbiage on what our future direction is. We grabbed this information.

Strategic Direction

Looking forward, the strategic direction of Adilas may focus on three key themes.

- Platform Refinement

Improving usability while maintaining the depth and flexibility of the system.

- Ecosystem Growth

Encouraging developers, partners, and businesses to build solutions on top of the platform.

- World Building

Continuing the vision of creating configurable operational environments where businesses can build their own systems.

Emails and phone calls. Small fix for some code. Reviewing some older developer's notebook entries from 5/1/23 to 5/11/23. I had the thought that I needed to go back and do some reviewing. Everything is going so fast. It's been three years since we tried to switch between ship A and ship B (internal pivot). I was reviewing May of 2023, seeing what was going on, leading up to that decision. Interesting times. We are, and we were, doing the best that we could. Lots of moving pieces.

Working on adding in AI generated graphics to element of time # 12909. Spent most of the time reworking the middle section of one of the graphics. See that element of time for more details.

Recording notes from the past few days.

Infographics from Steve's main 3 points.

1. Look at what we have - deep, deep
2. We are building daily - progression
3. We help you by bringing value - multiple ways

I also did some other infographics on the parable "The Sower" and how best to help AI grow/thrive and provide good structure.

Here are the two ChatGPT chat session links:

Steve's 3 main points - https://chatgpt.com/share/6a18ff2d-d09c-83e8-b3bc-6682fedbf1e3

AI needs good ground to grow and thrive in - https://chatgpt.com/share/6a18ff73-add0-83e8-b1e2-568b7ebe50fc

Work session with Shannon. We did some review and went over some of the new changes. Sometimes things change so quickly. I showed her where I have been working and some of the new videos and images. We bounced into a number of different pieces and documents. We ended up reading some notes from element of time # 12893 from 5/26/26. It was dealing with the known problem of non centralized data and separated systems. We read over that entry and then started working on a new MS Word document for how some people think that AI will automatically solve all of those existing problems. We spent the rest of the session working on the new document. See attached for our progress. We will pick it up again next Tuesday and work on it more.

As a fun side note, the document is not that AI is bad, it is more along the lines of AI needs a base or platform to build on and get fed good data, in order to do what it does and/or can do. When all tools break, people will keep moving up and down the tool chain. We see world building as the current highest level. AI at the world building level can be super cool, it has the whole platform to be built from and stand on. It will really thrive with that big of an existing platform. It creates the underlying super structure for the whole. Kinda fun.

Working with Russell and Abby. Russell has been working on the photo gallery pieces for our documentation project. He showed us what he was working on. He did some prep work and even added in some container queries for custom CSS sizing. Normally, we would do CSS media queries to adjust sizes. Those deal with the entire window. This was the first time for me to use container queries for sub container sizing changes. We did some testing and light tweaks. We also made some other gallery tweaks and changes. Great to watch and participate as he is building. I think that it has been an excellent training exercise. I'm learning a ton.

Working with Abby. She is working more on the adilas, bridging the gap between operations and accounting concept artwork. We did a small work session and tried a few new things. I was giving her some suggestions, and she was making the changes.

Working on the adilas videos and research page for the adilas lite and fracture plan. Went through each video and made a small little image to highlight some of what the videos were about. Light research on animated gifs. Opted to just do simple graphics for each video instead of animated gifs. See the video and research page for the new images.

Recording notes from last week (5/20/26 to 5/22/26). Other small odds and ends. Light research on phrases like "centralize the data" or "catch the data". These have been a reoccurring theme and seem to be the start of the problem and/or disconnect for other systems and software packages. I would like to show the problem of non centralized data, using multiple system, and then struggling to bring it all back together. That seems to be one of the biggest problems in business. There are others, but that is a big one.

Here is a link to the developer's notebook - subject: centralize the data and catch the data - Web link

Here are some notes from a small brainstorming session on 5/21/26.

The main problem or challenge

1. Non centralized data
1.a. Data on different devices or computers
1.b. Data controlled by different people or groups
1.c. Data location may be spread out
1.d. Data is random, deep, and not organized
1.e. Not all data is digital

2. Using multiple systems
2.a. Each system or software package is separate - doesn't connect or interface with other systems
2.b. Spreadsheets, files, documents, images, paper, emails, web stuff - mixed data and locations
2.c. Time gaps or batching between systems - delays in data flow, duplicate entry, manual exports and imports, bottle necks
2.d. Spreads the data out, slows it down, and even isolates the data by system, by machine, or by person or group
2.e. Accessing data - who gets that data, how do they get that data, where does it go, what do they have to do to get that?
2.f. Even if you get all the data... now what? You have got a mess!

3. Once you have it, meaning the data, what do you do with it?
3.a. Outcomes, results, flow, and look & feel - all variables
3.b. Do you have a system or place for everything? Can you get to it? How easily?
3.c. Let's talk scale... How is that looking?
3.d. Where is the future going? Have we addressed that?

---

The solution - adilas.biz

1. Centralized data

2. One unified system - able to catch all of the data

3. Once you have it, the data, then what? - Full system ready to show and provide outcomes, results, flow, and configurable look and feel.

Web link - adilas presentation gallery - 50 slides of what we do and what we offer! Enjoy!

Lunch meeting with Matt Coltrin with Pitch Launch. We grabbed some burgers and spent about 1.5 hours chatting about all kinds of stuff. Matt tries to get investors together to get some education and then to hear some pitches from local businesses. We are going to give it a go and make the pitch. The date is out in early July, but something to work towards. We would love to get some investment into what we are trying to do. Good meeting!

Recording notes from 5/18/26 to 5/19/26. Light graphic work to push up images. See element of time # 12891 for the new images.

Meeting with Ryan from Peak Technology Partners, a business sell-side banking entity. They had reached out to us and we setup a call to talk with them. Nice call. Nothing too special but chitchatted and talked about products, services, goals, and what not. Their pricing and retainer fees were higher than we are looking for, so we chatted and passed some information around and we'll both move on. Pretty casual meeting.

Went into town with my dad and Bryan to go through the Btech (Bridgerland) business and innovation hub open house. Before it was called that, adilas used Bridgerland for 4 months when we were starting the adilas shop back in January of 2015. They have really pushed it further, added classrooms, labs, board rooms, office space, and the list goes on. I really think that they are on to something. So much potential. There is tons of potential for adilas to help with things like that as well. We could help with training, software, systems, innovation stuff. It could be really cool.

As a side note, since we took my dad, and he used to work for Bridgerland, we got the VIP tour and treatment. Good stuff!

Work session with Shannon. Going over the adilas 3-part pitch. We are trying to discuss and present adilas to the public. We feel like you have to engage a little bit to really know what it is all about. Small talk about AI and who uses it and how they use it. Talking about Abby and her thoughts and feelings. It is interesting to see the different sides of the coin. We then talked about how are we using it, meaning AI? We jumped back in and did some editing and reading over content. See attached for what we are working on.

Heather wants me to show the real things that make us different... taking the lid off of some of these things - flow, concepts, new models, how we make it work, the real meat. Heather wanted me to work more on describing the problem and/or challenge and how adilas provides solutions for that. I started out on paper and then rolled into a chat session with ChatGPT. The subject was an old flyer from back in 2013 called what is adilas?

Start of the ChatGPT session - dealing with the old flyer - the goal is to start covering the real problems of non centralized data, using multiple systems, and bringing it all together - https://chatgpt.com/share/6a15c889-1934-83e8-9d79-41f41a6024d2

Recording notes and uploading images. Ended up doing some photo retouch work on one of the AI images.

Meeting with Abby and Russell. Working on the image gallery. Great session. We were testing things with big images, small images, size changes, modal popouts, next and previous navigation, dynamic captions, styling, etc. Fun stuff. Just for fun, I passed Russell over a few new infographics to help us test and see what they will end up looking like in the documentation flow. Exciting.

Meeting with Abby. We looked at some graphics that had some soft watercolors, or softer aesthetics. See attached for a couple of screenshots of adilas bridging the gap between operations and accounting. We then had an interesting talk about AI hypocrisy. Abby loves working with adilas, but she can see that AI is being used more and more. She loves what it can do but has a real problem with the environmental requirements of using AI and having AI data centers. Interesting conversation. She loves adilas and the culture, I will work with her to help her feel comfortable. We talked about bridges, trains, ice bergs, assembly line, conveyer belts, etc. Talking about other things and how we can fit them together. I grabbed a few new screenshots. See attached for a couple of new ones.

Pushed up some code for Bryan. Looking over some of my new documents. Recording notes from the past couple of days. Light graphic work.

Quick touch base with Bryan. Going over ideas and plans. Trying to decide where the best possible use of time, money, and resources would be.

Meeting with Shannon. Showing Shannon what I was working on the past few days. She liked the mash-up image. These were images from ChatGPT. See elements of time # 12891 for some of the graphics (quite a few). We went over graphics, text, and options. We want to grab the main statements and power statements from the AI chat session. We are thinking about doing almost outline style for the new 3-part pitch. I am so grateful for Shannon's help with that.

Working with ChatGPT to get some visual assets ready for the adilas 3-part pitch. Spent time going over the data, text, and working on visuals and layouts. Multiple rounds working through detailed layouts, mock-ups, and wireframes. Tons of new graphics. Finished up the first round of all 7 main sections. See attached for some of the new graphics. Some of them won't be used, different versions, but I want to put up a bunch of them to show the progress.

Full image chat session with ChatGPT - https://chatgpt.com/share/6a0e5633-1100-83e8-b9c9-c8e7a221fe95

Meeting with Luke from Frontrange Business Advisors. Going over their pitch and some adilas stuff and what we offer. We chatted for a few minutes. He is going to send over some other information and we'll go from there. As a fun side note, I used three of the new infographics in my presentation to him. I grabbed the new infographics from the adilas AI assets page.

Working on the 3-part pitch for adilas. Got some final copy done and started working on images and visuals.

Full chat session for the finalized 3-part pitch text - https://chatgpt.com/share/6a0cff65-9bd0-83e8-a910-61b8580536e5

I was supposed to have a meeting, but the guy had to cancel. I ended up spending some time doing emails and light catch-up stuff.

Working on graphics for adilas. Recording notes from the past couple of day.

Working on distributing some adilas percentage ownership to both Wayne Andersen and Shannon Scoffield. I appreciate their help. Recording things inside of adilas, sending out emails and texts, and uploading images into adilas. Light graphic work. Refining a graphic that ChatGPT made but it needed some tweaks.

Recording notes from 5/11/26 to 5/13/26. Uploaded a number of new images and infographics.

Working with Hamid. Showing him what I have been working on, lots of AI stuff. He then showed me what he is working on. We ended up doing some clean-up and we will be restarting on his play at the wall (API socket page) website project. He is working with AI to try to build it up. He got lost and it's hard to figure out what is new, real, and needed. Not a big deal. There is a learning curve there.

Meeting with Bryan. We were doing some more planning on the MVP POS system. We were looking at what pieces need to be manual and what pieces we could start automating. Bryan was taking some notes. We started into a small outline and walking through the steps. As we did, we were looking up existing code pages, database tables, and method names. We added these technical notes to our plans. We then started talking about the ecommerce checkout and setup processes. I think that it was helpful to have Bryan see us walking through the steps. We also talked about possible errors, redirects, and validation along the way. I was trying to encourage him to think of a bad user, someone who didn't follow the steps perfectly. What do we need to add into the process, to keep those people in line or on task. Helping to round out the ideas and such.

Meeting with Shannon. Steve and Wayne were on the meeting when we jumped on. They were talking about email campaigns and how that all works. They were talking about code, flow, and the underpinning and workings of the system. We would like to add on features that we could use and mark-up and resale. Talking about other code changes and updates. Wayne is working on some new MVC changes (MVC = model, view, controllers). After Wayne and Steve left, I spent the rest of the time working with Shannon. We finished up the help file for the GPS core. That has been an ongoing project for weeks now. We just had an hour or two here and there, but we got it done.

Working with ChatGPT on some infographic specs. Trying to standardize things. See attached for some images and the infographic spec sheet.

Here is the chat session link, working on infographic specs. It starts out a little bit funky but gets better. https://chatgpt.com/share/6a069cd5-ba14-83e8-aa51-3271acc5c5aa

Working with Russell and Abby. Looking at AI image generation. Lots of playing and checking things out. Learning and adapting to change, that seems to be the secret. Nothing is fully stable (in a way). Russell was showing us some new stuff and even full AI app generators. One of the experiments we did today was taking a picture that we liked, asking it to describe it, then taking that info and applying it to other photos, sites, ect. I was playing with AI, giving it images and then asking about those images. Trying to get a flavor for what I want for my images. Playing with little drips and drips, little drips of information and/or progress. Then letting those small drips add up over time to really amount to something. Eventually, it will fill the bucket. More work with AI asking it to help with the correct prompts. Taking the time to and really looking at your prompts.

Work session with Abby. I got a number of new screenshots. See attached for some new graphics concepts and mock-ups.

ISO 8601 Date Format Updates for Delivery Transfer Endpoints

Four different sessions throughout the afternoon and evening. Working on fixing some graphics to help with the help files. Pushed up the new infographic that Shannon and I created this morning with ChatGPT. Trimmed the graphic out and made a couple of sub graphics out of it as well. Jumped back into ChatGPT to work on some other time based graphics. See attached for a number of new infographics. Concepts of time as a foundation, time as a wrapper, and as time clue - for supporting, wrapping, and connecting everything together. Working on the 1-page flyer with a 3-way pitch. Pushing and getting further along in the process. Finishing up one of the info graphics on the branch. Working on graphics going from a separated or mash-up system to a more systemized environment and system. See attached.

Here is the link to the ChatGPT session on the 3-part pitch. https://chatgpt.com/share/6a04cc1b-26bc-83e8-ab77-d88df058d8d0

Adilas is a connected business platform designed to help companies organize operations, accounting, workflows, inventory, reporting, and business relationships inside one unified system.

Many businesses struggle with disconnected software tools, duplicate entry, spreadsheets, and gaps between operational activity and accounting. Adilas focuses on helping bridge those gaps by connecting business processes together in real time.

We provide a flexible core platform that businesses can start using quickly, while also allowing for customization, growth, and long-term adaptability.

Our long-term vision is to continue building a connected ecosystem of businesses, developers, AI-assisted tools, services, and community participation that can evolve together over time.

Meeting with Bryan. Talking about setup wizards. Bryan has done some research on wizards, looked at some samples, and best practices. He had looked up multiple videos and tutorials dealing with wizards. We did a full walk through video last time (our last meeting), however, it never got recorded. We had to go off of some partial notes. We setup some time to work on this again on Thursday.

Meeting with Shannon. Review of things that are going on. Small updates. Working on the adilas GPS core help file. We spent a ton of time working on the section dealing with time and tracking objects and data over time. We even worked with AI to help us summarize some of our pieces. See attached for a couple small screenshot of the help file. The actual help file may be found here - Web link - help.cfm?id=479&pwd=core

Helping Bryan push some code up live. Emails and making a follow-up appointment with a business advisor. Watched a video from Russell about a guy who was really good at making AI images with ChatGPT. It had some great content and ideas. Spent some time doing some research on the 1-page flyer that I'm working on. I'm calling it the Adilas 3-part pitch. The three parts are an introduction, current offerings, and future offerings.

Emails. Talking with a guy about some funding options. Back and forth on the phone a couple of times with the bank guy. Reviewing notes from last week. Trying to figure out what to work on next.

Paying bills and recording expenses.

Reworking an older graphic to have a little bit more information. The graphic is for the adilas value add-on core. The new graphic has an added AI layer or level 6 text. Other small changes. See attached for both the old graphic and the new one. I may run it through AI later on, to get it looking even better. Making progress.

Here is a link to the full sized adilas value add-on core model graphic - 1200px wide - Web link - value_add_on_core_model_with_ai.jpg

Working on 110 images that Abby sent over to me. The new images cover a couple of different topics. The topics are:

- The adilas GPS core
- The compass core - another version of the GPS core
- New graphics for the adilas value add-on core layers
- Fun concept images and graphics showing a floating city, built on top of the adilas transactional core and other value add-on core layers.

Abby also sent me a one-minute video showing the topics listed above. Adilas - a platform to build on. What a treasure chest of images. See attached for some of the images.

Emails and recording notes from 5/2/26 to 5/7/26. Ended up fixing a few images, light tweaks. Some of those entries had a number of images. Uploading the different images and graphics. I enjoy that. Reviewing a few small videos that Russell sent over to me. The videos were dealing with developers and use of AI stuff. There were three videos, each about 8-10 minutes a piece.

- Asynchronous agents - agent workflow - make sure that you do this... attempt, fail, learn, fix, verify, repeat

- Frontend planning - approve the plans before a single line of code is written - recommending Kombai as the frontend UI tool

- Start in ask mode, then switch to plan mode, then when ready - switch to agent mode - this is dealing with using AI in VS code.

- Really knowing the code and the problem will help in the long run. AI might be quick, but it can also quickly code over your head and your ability to debug and/or fix.

Really good phone call with Steve. By the time the phone call was over, I was feeling better. I was able to express a few things and we had a great talk and chat. Here are some of my notes.

- Steve was telling me about all of the AI projects that he and Eric are working on. He was talking about planning and how it's hard to out plan AI.

- The current goal seems to be get the data from the user as quickly and easily as possible, then get it into the database. The user is not limited to the normal interface. That part of the system seems to be changing.

- More talks about the converging POS system and ecommerce. It is also tied in with menu boards and other touch type interfaces. Along with this convergence, Steve was talking about customer functionality like customer favorites, loyalty points, and other CRM functionality stuff. Everything seems to be mixing into joint or interconnected systems. That is exciting. That's what we do. If you mix all of this with AI, you can get some super cool results.

- Business is not static. If yes, it is dead. Business is dynamic.

- Using AI to rewrite some of our older code. Big time savings.

- Steve was talking about using AI to help with code, display stuff, and refactoring of older legacy code.

- We talked about new plans for certain features and more bulk tools. That seems to be what people want and/or are asking for.

- Steve wants me to come back on the inside and work on code and projects. We had a good chat and I explained what I am doing and where I am heading. I need a break right now, if for nothing else, mental health. I am bringing value in different ways. Including planning, content creation, graphics, AI work, meetings, and helping to pitch the vision. It is all part of the same project. I need to keep doing what I am doing.

- I told Steve that I will be cheering for him and will be helping where I can. I'm on purpose on the side. That's where I need to be right now. It's allowing me to do things that I have wanted to do for years and years but haven't been able, because of demands, budgets, and other factors. This is where I need to be.

- By the time the phone call was over, I felt like a small weight was lifted off of my shoulders. I have put thoughts, reasons, and needs in emails, texts, and have stated things before in meetings and over the phone. Steve may not fully understand, but we were able to talk about things in a very nice and civil way. I'll take it! We will keep building from there. I honestly felt better after the call.

Working with Russell and Abby. Back working on the documentation project. Working on some cross site scripting validation. Working on adding in images and image galleries. Using AI to help buildout this whole project. There are times that we have to manually alter things, but trying to get AI to help build as much as possible. Abby and I have been mostly watching Russell and asking questions and being another pair of eyes. Great learning experience.

We are getting close enough that Russell gave me an assignment to get some pages ready with content. Russell wants some juice, real content, images, and stuff. We want to do a deep semi-real test.

Working with Abby. I showed her some of the new graphics that I was working on with ChatGPT. She then showed me what she is working on. I got some screenshots. See attached for a couple new graphics. She is getting close on her little movie about the adilas core and adilas value add-on core model. We made a few changes, but it is coming along. I was impressed.

Writing up a document to pitch to Andrew. Finished it up and had Heather help me review it. Small changes and then pushing it out to both Andrew and Steve.

Phone call with Andrew. We spent about an hour going over a number of things. Here are some of my notes.

- Dominos and getting things to start falling. You have to have some of your other things ready, in order to get the best benefit of the dominos effect.

- AdiVison - a place to store SOP's for any corporation

- Sometime, often, the terms scale and custom don't mix super well

- Running things through project management - taking steps and only biting off what you can chew

- Focus on people, products, and processes

- Getting our people on board

- Marketing - kind of like an eye exam or eye test - this one or this one? Just simple questions and see what people like better.

- Talking about prices and values - currently, there is a disconnect between what we charge vs the value we bring. It's all about perception and packaging.

- We spent some time talking about ownership of both a company and the ideas

- Dealing with ideas and plans, if someone has a better idea or plan, great, let's check it out. If not, let's go with the plan presented. I can see what he is saying here, but part of me is like - wait, we just don't go for it based on it being the only thing presented. I'm a little bit more cautious.

- Talks about leadership

- Who is on the team and who is ready for the mission (going for it)?

- Building websites vs PowerPoint presentations. Websites can give more real-life options and allow for variations and flow. I feel the same way. We are planning on working more and more on the adilas presentation gallery website for just that reason.

- We also briefly talked about extending some possible ownership shares and percentages over to Andrew. He has a lot of great ideas, energy, and plans. We just need to get the funding to put them into action. If we don't get the execution part of it, they are just ideas and plans. How can we take it to the next level on a low to no budget? That is the question. The other option is waiting until there is a budget and then going for it. That may never happen, or maybe it just might. Time will tell.

- I told Andrew that I would come up with a document to pitch getting him some stairstep equity in the company. Small percentage with options to get other percentages based on revenue, funding, and/or product releases.

Working with Bryan. He ran some documents through AI to get a review. We looked at his partnership assessment stuff. To be quick it was saying yes, potentially very beneficial, but the value depends entirely on execution (not just frameworks). It has to go beyond AI planning. We need clear deliverables and execution expectations. These need to be focused and rollout or execution over the next 30-60 days. We spent some time talking over plans. Bryan is working with Gemini AI to do some things.

We spent the rest of the session doing a recording on how to setup new corporations and how we could potentially start automating some of those things. Automate certain things, hide other things, and make the whole process much smoother and more standardized. Bryan recorded the session. I was talking and drawing and Bryan was asking questions. Fun to go back through things. Lots of potential for speeding things up and making the whole process feel easier.

Working with Shannon on help files. We did some show and tell on the new graphics from ChatGPT. We then worked more on editing help files. We got into some deep topics and will need to circle back around. We want to workshop on the topic of time as a wrapper - why, because, it brings value, stable, 3D time tracking, etc.

On a phone call with Steve, going over plans and updates. We were talking about merchant processing and seeing if we can get connected with higher ups. Currently, we have had merchant processing since 2008/2009. We would like to get to the next tier and be able to offer our own stuff to our clients. They require a huge amount of transactions, in dollars, even just to talk. Steve has some connections and is working on some of those angles.

- Steve is seeing a blending of digital menu boards, POS, and ecommerce apps/sites all coming together. This is what one of his big clients is wanting to do. Basically, self-serve order or ticket creation process. The customers could use a kiosk, a phone, a tablet, voice to text, AI, etc. All kinds of options. Then the employees, or whomever, including bots, could then fulfil and process the order. You could also have a single pay location, if needed as well. We have been doing things like this, or at least along these lines for years. I can remember Eric making a shopper app. At that time, it was a mini barcode reader that the people could hold and take around the store. They could scan whatever barcode they wanted, and it would add it to a quote. Then they could say that they were done and it would convert the quote into an invoice so that they could pay for it. This was years and years ago.

- You can see some of the technologies coming up and maturing over time. Similar requests, just new technology being used.

- One of the current trends is touchscreen menus. Going further, they want to take those touchscreen menus and mix it with the goal of going straight to ecommerce and checkout. See attached for a sample menu board as a concept.

- More and more companies are wanting a full streamlined interface and data flow process. That's what we do. Fun timing, we just need to get in there and do it. Steve is seeing more and more companies wanting a fully connected system or systems. We have been preaching that for years. Hopefully the current trends and customer wants/needs will drive some business our way.

- Real-time numbers and accounting. This has always been a want for owners. They just weren't sure how to get it.

- Steve was talking about Andrew, new guys that Steve is working with. They were talking about a poker or gambling analogy. You don't play every hand that you are dealt. You have to know when to fold and when to call. For example: fold, fold, fold, call.

Three different sessions working on stuff. Emails and then working with ChatGPT to make some more concept graphics. Spent some time adding them to the adilas AI assets page (new AI page in the adilas lite section). All of these new graphics came from AI content and prior chat messages. See attached for a copy of the new images. There are quite a few new ones.

Meeting with Shibga about podcasts. Took a bunch of notes on a some post-it note cards during the meeting. He was talking about using interviews as a way to build up your content as well as build rapport with others in your industry. He was saying that if you do a direct pitch, most people say no. If you ask for an interview and build rapport, people will say yes to that and then it could blossom into a valid conversation. Shib was representing a company called ashmedia.org. Their pitch was spend an hour a week on podcast stuff and then let them do all of the editing and pushing things to different social media platforms.

By way of a note, way back, Steve had the idea of going to every major city and putting on free business seminars and conferences. Basically, teaching people about business and business skills. We could then use our product, adilas, to show those concepts. That's an old dream, but it got resurfaced as I was talking to Shib. It has a similar flavor of sharing and building rapport, then seeing if the conversations come up. The modern way of doing something like that is podcasts vs in-person seminars. Big cost difference and big time demand difference. It doesn't mean that it is bad, it just may need some updating, meaning the dream.

Emails and sending out a request for information from Shari O., Cory, and Sean. They are the ones that help with onboarding new clients, setup, configuration, and deployment. Trying to gather some of this information together into a single place.

Paying bills. Small to do list items. Adding small placeholder graphics to the adilas lite and fracture pages.

Making a spot for all of the AI assets. Ended up doing some emails and reading through an implementation and strategy audit guide from Andrew. Lots of questions about processes, onboarding, training, and setup stuff. Spent the rest of the afternoon working on the AI assets page for adilas. Started having AI build me a bunch of simple images. See attached for some of those images.

Emails and recording notes from 4/27/26 to 4/30/26. Adding graphics, screenshots, and AI chat PDF's to the elements of time.

Working with Bryan. Going over some of the Gemini stuff that Bryan is looking into. AI learning over time. Using AI for chats, questions, tasks, filling out forms, training, and full service. Talking about database scaling, both ideas and issues. Tons of drawing. Going over existing database logic, session management, servers, corporation creation, and setup stuff. Instead of just jumping into the mini POS or MVP POS, we are seeing that the next logical step may be some pre or prep work, before a client sees anything. It appears that the turnkey setup is the next step. This deals with automation of the corporation creation, setup, and configuration steps. We may not do this fully, meaning full automation, but we will move the ball closer by working on that process. Bryan wanted some help with budgeting and coming up with a rough budget for the project. We setup some time to work on it again next week. The current goal is to keep chipping away at it.

Meeting with Steve and Andrew. Talking about all kinds of ideas and possible solutions. Andrew was showing us his AdiBrowse, AdiHome, AdiChat, and other Adi features. He is using Adi, the dog mascot, for all kinds of possible tools and features. We were talking about the concept of having a possible browser at the adilas level (built-in). Talking about inside AI agents and outside AI agents like Gemini and others. Just to give you an idea about Andrew works, he is loading and working on three projects at a time. One on the phone and a couple of others on iPads. All at the same time.

Talking about how to scale businesses. He has helped other companies with this task. Bringing value to the table. There is a pricing disconnect - between what we bring to the table and what people are willing to pay. We went on and talked about plans, possible solutions, and how to work together. I grabbed a bunch of screenshots of things that he is working on and also showed him a few small things. Good back and forth. I also told him that we are idea farmers and sometimes have to sit on things (like planting seeds and waiting for them to grow). Eventually, we circle back around to things and work on those projects.

By way of a note, I'm going to add a bunch of screenshots and infographics that Andrew has done with ChatGPT and AI. I didn't get all of these tonight, but they all kinda fit here, in this discussion. See attached for the graphics.

Working with Russell and Abby. Back looking into the dynamic documentation project. Looking over security aspects of the project. We were doing some testing on the XSS (cross site scripting) validation.

Working with Abby. Looking over graphics. I got a number of new screenshots. She also finished up a small video on the adilas value add on core. It is looking good. See attached for a number of new screenshots.

Emails and reading through documents dealing with adilas help and support options. This was a proposal from Andrew.

Quick meeting with Bryan. Help on his eBay items and shipping stuff (new 3rd party solution). We made a quick fix and then he pushed it up for some testing.

Reading emails from Andrew. He sent over three agreements and one dealing with Adi options.

- One agreement handles revenue and customers.

- One agreement handles leadership and equity alignment.

- One agreement handles capital and control opportunity.

- Adi becomes the face of the platform. Adi is the dog avatar or mascot.

- Adi is the interface. Adi is the assistant. Adi is the operator. Adi is how users interact with everything Adilas already does.

Multiple sessions working on the mini POS or MVP POS plans. This was actually five different entries, but they are all related and all happened on the same day. See attached for some of the documents. Here are some of my notes.

Planning on the mini POS. Great little session with ChatGPT. "Start simple. Grow into the full system." I gave it some notes and got some good direction. We still need to go to the next level, but making progress. Created a PDF of the conversation.

Working with Bryan on the mini POS or MVP POS. We were going over the ChatGPT chat and plan. We ended up talking about a thing that Bryan found called the university of the people - possible free entry point - thinking about lesson plans, simple usage, and helping people progress. We would really like to make a simple or free version, along with classes or course curriculum. Make it as easy as possible for entry and people to learn. 

Bryan was asking - how to transition from MVP to more features and tools? Keep funneling it down.

Help our team flip the switches quickly - manual setup and configuration steps. Make that faster.

Light planning. How can we build a guided bridge into our ecosystem. Did a secondary session with ChatGPT to help explore the ideas and options.

I really liked this line - Guided Entry Layer Into the Adilas Ecosystem

Capturing the Core Vision

Create a lightweight, mobile-first MVP POS experience that allows small businesses, events, vendors, and simple operators to begin using adilas quickly and comfortably, while preserving a guided path into deeper operational tools over time.

Primary philosophy: Simple First. Expand Forever.

Secondary philosophy: Help businesses gradually grow operational maturity without forcing painful system migrations.

The bridge itself becomes part of the product.

Branching from the MVP POS into the MBP timeclock and project time tracking mini app. Reviewing some AI chats from earlier today. Finishing up the chat session dealing with an MVP for "any" time tracking mini app as a bridge to the adilas ecosystem. See attached for links and PDF's.

MVP POS chat - https://chatgpt.com/share/69f0f80f-3638-83e8-9b55-8175e21262d2

MVP "Any" Time Tracker chat - https://chatgpt.com/share/69f40537-f6a0-83e8-b579-e52bc143c958

Working with Shannon. Got some feedback on the adilas lite stuff. She thought that it was too wordy and too busy/heavy. I will see what I can do to help modify that. We then jumped into the adilas GPS core help file. Reading through a few sections. As a side note, it is really tough sometimes to boil things down and make them really simple.

Recording notes from the end of last week.

Podcast interview. They mostly wanted to know about me as a person and what makes me tick. I got to talk a little bit about adilas and what we do, but most of it was dealing with being an entrepreneur and developer. After the interview, they wanted some feedback on their product and approach. Small marketing pitch for some of their services at the end. It wasn't too bad.

Reviewing a document that Steve asked me to write. Small edits, proof reading, and sent the document off to Steve for review.

Working on PDF's, graphics, and linking up content. Lots of time working on graphics for the adilas lite and fracture site. Working on banners, new images, etc. Changed up a few things on the adilas lite and fracture pages. Made each section have a separate graphic and also added a new banner showing more than two decades of development work. Steve had asked me to write a small letter to Andrew and Don, about the possible purchase of adilas percentages. Busy day!

Recording notes, pushing up files, and reading over other texts and documents. Small website changes for old main website top menus. Added links to the fracture - adilas lite plan, investment opportunities, and the presentation gallery. Working on some other graphics. Added a banner image to the adilas lite page.

We ended up meeting later today. I was talking with Heather's parents prior to our meeting. Heather's dad, Jim Wilson, challenged me to make a one-pager to pitch what we are doing with adilas. He recommended that we make it non-technical, show that we have proven the model, and currently generating revenue. Shannon and I spent some time going over some of Abby's new graphics. We made a couple of tweaks and sent her a couple of suggestions. We then looked at the new mini graphics that I pushed up for the adilas GPS core help file. We reread some of the text and made a couple of small graphic changes. Just to make things flow better, with the graphics (combo).

Recording notes and filling in more content for section 11 of the steps to success. Web link - steps_to_success.cfm

Working with Russell and Abby. Looking over some new changes. Russell helped me get some AI stuff setup in my code editor. Then we jumped back into the documentation search functionality for our build project. We are deep in the details of the search results. It is close, but we have found a few small discrepancies, code from AI. Working through those things. Going over scenarios, what would you do if... (fill in the blank). Small training session. We finished some of that stuff up and then moved on to some load testing. Talking about scale. Towards the end, we got into a discussion about time it takes to make changes, graphics or code. If it takes a long time, start thinking - how can I make it go faster.

Meeting with Abby. She has been working on the compass graphic and system main players. She is even working on a small video of the application players. See attached for a few new mock-up images.

Working on linking in some of the older steps to success. Light work on section 4 and section 11. Section 4 is meet the players and section 11 is financials and accounting.

Recording notes from earlier today. Working on some mini graphics for the Adilas GPS core layout help file. Web link - help.cfm?id=479&pwd=core

Getting stuff going for working with Charlie at Touchstone Business Advisors. Uploading a number of PDF files for his review. I also sent out an email to Shari O., requesting some adilas tax return documents.

Meeting with Bryan. Going over plans for the mini POS. See the EOT # 12814 for some other ideas. He has been wrapping things up with some of his other connections and obligations. We were talking about the "almost" product dilemma... small things that hold people up from fully jumping in. That could be small connections (outside services), certain features, size, perception, etc. We also talked about some of the small sales funnels and how those work. We see lots of needs on the smaller POS side. Just an entry point. We are somewhat backwards, meaning adilas, we have the big picture options and not much on the super simple stuff. We may need to provide some of the simple things and then let them, our customers and clients, grow into the bigger pieces. One of the biggest goals is getting people in... really easy. Everybody needs to start out smaller and then grow into it. Let's help them.

Switched over to what Bryan is working on. He is working on Stream POS connections and some security stuff. Bryan is seeing the needs and requests of different parties. We are trying to listen and then trying to build things out to help these potential customers. Sometimes we run into areas that need funding, just to play and/or connect. Some of the other companies charge us to integrate with them as an outside vendor or reseller of their products (certain connections). We already have customers that want these smaller or mini products. Trying to build out the MVP for these mini pieces. I setup some time later this week to do some more planning. Everything takes time.

Talking about Andrew and how to approach some of what he is doing. He is providing so much content and plans, it is hard to know what to do with that. Not sure what to do there. He is generating so much, through AI, but I don't have any direction on what to do with everything that he is coming up with. Shannon and I were talking about scale and education. Two known needs. We then spent time working on the world building levels inside the GPS core help file.

Emails. Then going through a number of to do list items. Worked on adding some new content to the steps to success pages. Spent some time on department settings, payroll, timecards, time templates, and flex grid tie-ins. Also spent some time working on the meet the players page.

Web link - top_secret/steps_settings.cfm

Web link - top_secret/steps_players.cfm

Recording notes from 4/14/26 to 4/18/26.

Working with Bryan and Oscar on an API connection. We had to do some checking and debugging of Oscar's code. We also pushed up some small changes on our side. We got it much further than where it was. Bryan is going to go back and rework some stuff to help get it ready for the next testing session. This was new code dealing with pushing things up to eBay from adilas.

Meeting with Mike and Jennifer from Harris. Touching base, sharing some background, vision, and where we are heading. Good meeting. They, Harris, buy companies, but they don't really do portions and small investments. They want to own and hold the company for all time. They don't try to resale it. Anyways, good chat and what not. They were highly recommending that we find a vertical or sector and really focus on that. We have heard that over and over again. We, on purpose, are general or horizontal. That is both good and bad. It can also require deeper pockets to get the marketing and advertising going. People want to be marketed to for their specific needs.

Mike also recommended that if needed, we split or sub divide the product into different smaller brands so that you can actively chase those sectors and business verticals. I told them that we want to be the underlying business or data engine. Similar to how the Intel chip gets used by various different computer and laptop companies. They don't make the computers, but they are sold as part of multiple other stacks and/or products. We would love to head in that direction. See plans in the adilas value add-on core model for what we would like to do with industry specific skins. All part of the master plan, we just have keep heading in that direction. Yee haw!

Going back through some of my to do list items. Recording notes for earlier in the week.

Adding some small links on one of the AI dashboard pages for Steve. Small graphic ideas back to Abby. She sent me a small sample of a graphic and I replied back to her with some other samples (ideas and possibilities). Looking into some of the green skin theme ecommerce settings. Mostly just looking around. Made a few small changes to one of the pages. It took a few minutes to get into the swing of things.

Prep for a meeting with Steve. Looking over some new assets, photos, and documents from Andrew. Sent him some light feedback on the images. Started reading over a large document with a plan for AI + social media marketing engine.

Meeting with Steve. Going over the mini POS ideas that we are doing with Bryan. Talking about other distractions and requests. So many demands. We then moved into talking about AI's and how quickly they are moving and what they are able to do. People are wanting everything connected. One thing that we can do well is - bringing client bills down (how much they are paying) and getting them all setup. All kinds of stuff going on and happening along the adilas front. Talking about email services and email campaigns. Emails with full tracking and money generation (full tracking). Basically, not just an email campaign, but an email campaign that is tied into your ecommerce, POS, and CRM functionality. Great blend of functions and features.

After talking about emails and email campaigns, we went into tons of other areas and sections of the system. We went over a bunch of new AI stuff that Steve and Eric are doing. Dashboard, new ecommerce changes, etc. Great progress. Not all of the pieces are fully done, but they are looking good. This is somewhat unsaid, but the current goal is "following the money... working with those who are willing to pay". Steve was talking about how they, adilas, are really only focusing on helping companies that have pain and are willing to pay.

Good conversation. I was glad to see what they are working on. Communications have been limited.

Code review with Bryan. We went over ideas on the mini POS (drawings and such) and then moved into code. A few small code changes for the eBay integration, making it more dynamic. We then got super deep into the adilas API stuff. It got pretty deep. We were partly doing some API training, quick fixes, and then some testing. We got it to a stable point for Bryan's new functionality for ChannelBox (third party solution).

Meeting with Shannon. Going over new changes and updates. We looked at a few graphics and talked about making the little mini POS thing for Bryan (upcoming project). We then spent the rest of the time working on the help file for the GPS core.

Recording notes from the past couple of days from 4/13/26 to 4/15/26. Didn't quite get everything done on the Tuesday 4/14/26 date. There were a lot of notes that day.

Working with Abby and Russell. Talking about the concept of a platform (adilas) and then supporting and building a floating city on top of that platform (system or application). Russell did a couple of drawings and Abby took some screenshots. The underlying pieces that connect everything are through the platform and/or API socket level connections. We then flipped back into working on JavaScript and CSS for the documentation project. We are trying to detail out the search options. We got the search fixed up. Much better now. Other small changes. Some manual and some AI augmented changes. Good work session. As a side note, Russell and I are helping to train Abby, as much as we can, while working on this project. Lots of little teaching opportunities while debugging, testing, or experimenting.

Meeting with Abby. Going over the master plan and the AI level (level 6). See attached for tons of new screenshots dealing with the concept of the adilas value add-on core model. Working through some ideas.

Small changes, emails, and more research on adilas CSS demo page. Going over ideas and options for quick changes. What would that take? Using CSS (cascading style sheets), how could we make major look and feel changes without redoing the whole app or system? Lots of possibilities there. We already have a number of themes; we could possibly use AI to help us with some other themes that would retrofit into the existing system.

Here is a small link to the CSS demo page. If you are a developer, there are some small notes inside the HTML page source. We used this small page and section to run a small internal game for our employees and developers. They had to leave the HTML alone and could only change the CSS. Russell Moore won the competition and submitted five different options. Later on, a few years later, he helped us create the snow owl theme that is currently being used. Tons of potential there.

https://data0.adilas.biz/css/ - older adilas CSS demo page

Light research for a phone call with Andrew. Gave him a call. He was driving, so we just chatted for a few minutes. He was working all day, while driving. He was just talking to ChatGPT the whole time that he was driving. Interesting way to travel.

Working with Bryan. Working on our pitch and a plan. We want to speed up and get some turnkey onboarding (instant start), QuickBooks equivalent (simplicity), full operational expansion (inventory, POS, manufacturing, CRM). We would also like to do some module separation, UI/UX improvements, with the major benefit of faster customer onboarding. Something to replace Clover, Toast, Square, QuickBooks, Shopify, etc.

From Bryan... the problems we must solve
- onboarding is too complex for new users
- UI/UX slows adoption and sales
- User default to known industry software packages for familiarity
- nonmodern UI/UX experience - expectations

We then talked about some things that we could do. This ended up in a small brainstorming session of sorts.

- Scope - figure that out, where are we headed for this lift
- Friction and pain points
- Map it out
- Time to first invoice (<10 minutes) - we want it less than 10 minutes. Super simple setup.
- Solving the same problems over and over again
- Helping the accountants adopt the new solution - if the accountants are onboard, they can help influence and push the clients

For us...
- Database scaling - known issue. We can make more and more of them, meaning databases, but we can't intermix them right now.

- You need a full staff member to run it, meaning adilas. If you just touch it every once in a while, you really don't get the full benefit of it.

- Some people and clients that we are looking at - Andrew with Hosthuski and Brian with Finetech - both have an existing set of clients and a possible sales funnel, even though it is small. People come to them and they reach out to people and small businesses that need tools and services.

- API integrations with delivery systems

- Canned business solutions or fully custom solutions - there is a difference - this gets tough.

- Auto launch a corp and be able to move it later if needed. Back to database scaling and mixing.

- We build and develop - we would love to have others sell it and support it.

- We all live on little islands, and nobody knows what he other are doing - meaning the adilas team

known needs:
- Need to simplify
- Turn modules on/off
- Create our own buttons and nav options
- Map out the system
- Known bigger pieces - db (database), nav, permissions, settings, functions
- Super small mini POS - vendors, part categories, items, cart favorite buttons, etc. Simple.
- Quick setup form... quick vendors, part categories, taxes
- Quick corp-wide settings (limited view)
- Simple forms first, then link to full pages if needed. think layers...
- Quick users with preset permissions
- Quick access to the last few invoices
- Quick access to setup (layered with nav, if needed)
- Quick sales graph and charts.
- Layers - pretend that we are dealing with the cache valley kid's market - see EOT # 12656
- Mapping out the mini POS system - pages, flows, screens, etc.
- Maybe look-up some ideas on wizards and quick setup flows.
- Old idea of a simple app for users, timecards, and project time tracking. We have all of those pieces, similar to the normal POS stuff. We just want to make some super simple versions.
- Ask Wayne where he is at on the db (database) stuff - get an update.

//////////

It is now a couple of days later... 4/18/26. I have been thinking about some of this stuff. Here are some of my new notes from this morning.

- What if we did this mini POS just using the existing adilas API sockets? That would be huge, cool, and great starting point for other users and developers.

- What would that take? Meaning a mini app using just the API's?

- Why would we do this? What would that solve? - I would say, it could be a huge stepping stone for others who may want to play along those lines. I can also think of a number of other ideas and reasons.

- Internally, we use Adobe ColdFusion. I would like to make a version that is in plain vanilla HTML, CSS, and JavaScript. Mobile ready and phone first design. Most of our internal products are desktop first with possible mobile responsiveness. Flip that!

- We could look into some simple frameworks, but I'm half temped to just keep it plain jane or plain vanilla.

- Is there a way to use what we already have without tons of new development? That would be awesome.

- A long time ago, I heard someone say that eventually, you have to eat your own dog food. That may sound silly, but they were talking about consuming what you push out for others to use and consume. Virtually, you have to eat your own dog food. If we have to use our own adilas API's, we would be using what we are pushing out for other to use. I love it, let's do it!

- What if Bryan, Alan, and I (and maybe others) start our own little side company and use the adilas API's as the backbone. We help to strengthen the core (adilas) while still being able to do other development projects. It's an idea. We could make all kinds of little mini apps and then tie them back into the adilas backend engine. That could be really powerful. I would like to expand and explore these options more. One thing that I was thinking, we are good at building, but sometimes not that good at selling. We may need to hook up with smaller sales funnels to help with that part of the equation. Just some ideas.

- I'm planning on teaching ChatGPT how to connect to the adilas API. I would like to get some information about that process and then be able to share that information. That could be huge, as far as other outside developers and development work. All kinds of new apps and mini processes, all connected to the main adilas engine. As a note, see the planning page on the adilas marketplace. These plans are a good fit for what we are doing and where we are heading.

- For me, instead of just telling AI (one of the models) to just create this or that, let's start super small. Then build things up step by step, make sure that we understand and can back what is going on. I was thinking of using the mini demo API connection first, then building a little mini sample app, then moving into the mini POS option. Step by step, little by little, keep it manageable. Tiny baby steps!

- Another small note - what if we took a single corp, set it up, and then added smaller locations and users per account. If they never have to login to adilas, we could technically keep a bunch of information together in one place vs having to setup a separate corp per account. This won't work for all parties, but it could work super slick for small parties and/or certain situations. The alternative would be a super small corp (world) per entity vs a small location (real or virtual) per entity. See this world building help file for more information on possible breakdowns of how to organize things. This could be pretty handy if all of the locations or sub entities were using the same merchant processing account. Once again, this would only play true for certain scenarios. Just some ideas, if nothing else, keep thinking about it. Lots of possible solutions.

- This may not go here, but think about Amazon, eBay, or other big sales sites. They sub divide the pieces and then use one platform to allow for checkout, money distribution, credit card processing, etc. There would have to be some planning, but in a nutshell, that is what we want to do with part of the adilas marketplace. Keep expanding on this...

Working with Shannon. Going over things, things are constantly moving and shifting. Part of the game. Reviewing the end of last week. Going over phone call with Josh, new stuff from Abby, and the limited SWOT analysis document. We then spent the rest of the time working on the help file for the interactive map.

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 Bryan. He is meeting with people and wants to see what it would take to put together a plan for a super simple version of adilas. Almost like a mini white label version where it could be super simple and beginner friendly. I was telling him that we may want to start with the bigger or high-level settings and templates. I see this step as quick group settings applied as a group or in bulk, thus the templates and settings idea. It could also be filtered down into permissions and what shows up, based off of those high-level settings (system wide). Great ideas. we are going to meet tomorrow to see what that might look like and do some planning.

I then got a text from Abby and jumped on the phone with her for a bit. She had a couple of questions. We ended up on the phone for almost half an hour. She is having fun with some of the graphics and concepts for adilas. We talked about funding and how she may have to put some hours on the side right now due to budget constraints. She is good with that, for now. We chatted about some other things, and she has a good attitude and good vision. I love it.

Recording notes from the past few days (4/8/26 to 4/11/26). Adding new files and graphics to the element of time # 12793 in the shop. This was from a meeting with Abby, earlier this week.