Working on the vendor credit project stuff. We already launched round one of the project. This is just to help it out a bit (round two). Research on vendor credits. It, the topic, covers way more than just vendor credits. Lots of great entries. There were over 50+ entries that mentioned vendor credits. Great review of where we have come from and where we are going. I loved the review session. Tons of fun accounting things coming in the future. Also, a small review of MVP lists for changes that we want to make.

Small note for me... I was doing some research on vendor credits... I only got to the end of 2023... Still need all of the other research since then. The older stuff was a great review and helped me see some pieces and patterns. Even where we are heading. Web link - developer's notebook on vendor credits.

Small data fix for a client on the data 9 server. I had to un-void a PO. I let Cory know once it was updated and she was going to reach out to the client. Recording notes from the day.

Meeting with Abby. I was showing her some of my mock-ups and getting some feedback. We were talking about small levels of the iceberg analogy (only show what is needed, hide all of the rest - like the part of the iceberg that is under the water). She is working on a new graphic about the concept to help record your business story. We talked about the idea of different checkpoints and stops along the data journey. I showed her some older drawings for the concepts of the data assembly line. Some of the pieces are very similar. We also talked about AI and where she stands. It, AI, is not really her thing. She feels conflicted and wants to be true to her values and stance on the subject. I can respect that.

Got up early and started working on wireframes and mock-ups for the food pantry - industry specific recipe maps. Worked on the admin homepage and client/household detail page mock-ups. Went into town to meet with Matt at the food pantry. Showed him some of my progress. We went over some questions and started going through flow and general intake processes. We were mostly focusing on the volunteer check in and assistance flow. We got out paper and pen and did some scribbling and drawing. I already had some of it mocked up, we just made some minor tweaks. I took a few notes and he basically gave me permission to simplify everything. He wants it super simple.

Small session before bed. Graphics and playing with mock-ups. Working on building an admin homepage. Just getting started. I'll finish it up tomorrow morning.

Quick CSS changes to help with the order of operations. There was some new CSS that was added at the end of the section and was overwriting things above it. Small order change to help it play better. Recording bills and recording notes from the past couple of days.

Small fix on the invoice homepage. Some of the top navigation was broken due to a JavaScript error. Ended up making both JavaScript changes and CSS changes. Light debugging with AI's help. I worked for a little over an hour and then Russell joined me. Once Russell joined, we worked with his help on some other fixes for the invoice homepage. He was able to help me make a few changes that I hadn't gotten to yet or couldn't figure out.

We then spent the rest of the session working on the documentation project. Russell was working on adding in a book reader tool. It has vertical page views, multi-page layout options, and zoom functions. It was fascinating to see his creativity and what he can do with it. He uses AI, then reviews it, has it change it, or he changes it himself, to meet his wants and needs. So fascinating to watch and learn.

Phone call with Steve. Talking about updates, changes, etc. We spent some time talking about vendor credits. Steve recommended that we use the vendor switch to help with auto adding the other part of the transaction. If the vendor is marked as an inventory vendor, we could update COGS (cost of goods sold) or a service vendor, we could update the expenses. As a recommendation, he recommended that we check out loyalty points. It has a similar auto flip to keep things square and right.

We started talking about Yogen Fruz and some of their touch level cart buttons (touchscreen stuff). We jumped onto a GoToMeeting and he was showing me the buttons to add new things to the cart. They looked more modern, as compared to the older my cart favorite buttons. Steve was saying that things seem to be heading towards bulk building of the menu trees. He is using AI to build some of these things. The AI was recommending three screens... phone, touch pad (mobile or tablet), and normal desktop mode or sizes. See attached for a couple of screenshot samples of the new buttons that he is working on.

Steve was saying that coding with AI is almost to a throwaway code level. It is almost easier to just rebuild it with new changes vs going in and changing it. Steve is really trying to help clients out and really solving client needs.

Recording some notes from earlier today and yesterday.

Small data fix for Sean. He had done an import (uploaded new inventory items) and was missing the vendor. I had to go in and update a few records and tables to get it correct. Phone call with Sean to do a quick follow-up. Spent an hour fixing a file for Sean. Adding in a default vendor field for a CSV part upload page. Pushed up new files to all servers.

Light research on vendor credits. We already allow for these, through special accounts. Cory and Steve want me to look into helping to tighten things up a bit. They can get kinda interesting. All kinds of situations may arise and/or be needed. I watched a couple of small videos online how other software products take care of it. As a note, it seems like a challenge, no matter how you do it. Here are a few things that I found - small notes:

- Vendor credits can come from returns, discounts, or overpayments

- You want your A/P's decrease

- Back in the day, we use to go to the actual PO or expense and put a new line item on the record stating that we got some kinda of vendor credit. We would then alter what was owed and/or paid. The old way was a very manual process.

- We already allow you to claim and use a vendor credit. We can back tie it to a vendor, a PO, or an expense/receipt. Without being super technical, you are somewhat declaring a new "almost like cash - asset" that can be used as a form of payment on a PO or expense/receipt. Currently, the missing piece is a possible offsetting entry to help keep things in balance. You can't just declare a new virtual asset without adjusting the COGS or expenses or inventory portion of the financials.

- You can map to an expense on the income statement. You can also decrease the inventory value, based on what happened.

- Other software companies had to create normal bills and then negative bills to record the entry.

- Apply the credit to the actual bill

- You may have to make a deposit or put a check back in the bank from the vendor

- There seems to be a need for clearing out the account - a manual offset of some sort

- So many situations... they keep changing... not just one simple solution

- We were thinking of doing an auto entry on the COGS for that vendor but it may not always go straight to COGS. There are a number of possible variables that we may need to consider. As a follow-up to this note, Steve and I were talking about maybe looking up the vendor type switch to see if the vendors were inventory vendors or service vendors. We met over the phone and then on a GoToMeeting session later in the day, after I had written these notes. If we do go with the new option, then we could maybe automate things based off of that.

- As a fun side note, eventually, we need to add in values for in-store credits. those too have some tricky questions about how they came to be and where they came from. All part of the fun.

Working on some wireframes for the food pantry adaptation project (industry recipe map). Working in a graphics program to setup some default layouts and assets that I could use over and over again. Super simple placeholders for page layouts, form controls, buttons, titles, notes, etc. See attached for a couple small samples.

Recording notes from 8/20/26 to 8/22/26.

Small tweaks to the play at the wall website that Hamid made. A few more small changes. l sent a quick email to Wayne about some changes. After that, I spent some time playing with VS Code and Claude AI making some CSS changes to a practice CSS page. Having some fun playing around. I was flipping between ask mode, plan mode, and agent mode. Trying to get my feet wet a little bit. Good work session. I took a break for dinner and then came back and did another small session. More color and CSS tweaks. Ran out of AI credits for this session. Here is a quick link to what I was working on - web link. This is just a simple CSS sample page.

Work session with Hamid. We were checking out the play at the wall website that Hamid had completed. The domain is playatthewall.com - He was excited as it was live. We ended up making a few small changes and pushing up new code to a spot inside of adilas - web link. We will get with Wayne (our server guy) to see how to update the actual domain site.

As part of our work session, we were using AI to help us do some CSS code changes to help with things called media queries (show it this way at a certain screen size). Fun session. It was new territory for both of us, meaning using AI to fix things through an agent vs asking for help and then making the changes by ourselves.

Working on dataflow and mock-ups for the food pantry industry adaptation project (industry specific recipe maps). Decided to use flex grid for the members of the families vs customer contacts. With flex grid tie-ins, I have more flexibility and bulk tools. The customer contacts seemed like a perfect fit until I found out that I needed tons of custom fields per family member (like over six custom fields per family member). I did a few more sketches and mock-ups on paper. I'm planning on using as much of the normal adilas pages as I can, as long as they don't look too complicated. I think that I am ready to start moving into more actual graphics (wireframes or mock-ups) vs small sketches and hand drawings.

Meeting with Abby. Talking about graphics and her current project. She is working on a new graphic for recording the story or digital storytelling. We talked about some ideas and direction. I then showed her the adilas blueprint that I was working on and how it has the five phases of world building in it. We then dipped out and looked at the individual smaller pieces of that graphic (see EOT # 12939) for smaller pieces. After that, we talked about hours, jobs, work loads, and where we are heading. We even talked quite a bit about mental stress and striving for a good balance. Life can get pretty tough sometimes.

Recording notes from the past couple of days. Scanning some of my notes for the food pantry project. See EOT # 13037 for more information and the actual scans.

Looking over the DevDocs or documentation project that Russell, Abby, and I have been making. Looking over code and playing around with different features. I then rolled into a work session with Russell. Doing some code review. If you change one thing, it changes the whole outcome. Russell and I were talking about life and life lessons. He was doing some code review and I was watching and doing some small other tasks as he was doing his stuff. Towards the end, we got into some exploration and deeper code review. Most of the functionality is done and we are actually doing real final code review on html, CSS, and JavaScript. We ended today partway through the CSS review.

Went to the park for a change of pace. Worked on some drawings and mock-ups for the food pantry custom data and workflow diagrams and screens. They are just hand drawings, but see attached for what I'm working on. Just for fun, I passed these notes back through ChatGPT. Nothing major, just reporting in. Click here to see the chat session - https://chatgpt.com/share/6a851427-b398-83e8-8e84-fadc1d2f3cf7

Recording and reviewing some notes from last week. I'm just chipping away at things and making light progress. It is fun to see where I have been and where I am headed. I enjoy that review process. Just for fun... two weeks ago, I was working on the adilas mini pitch. Last week, I was able to get version 2 of the adilas blueprint finished up. This week, I should be doing some more mock-ups and graphics for the food pantry industry recipe adaptation.

I also spent a little while doing some CSS training. Working on text alignment, spacing, and other text formatting options. Continuing education stuff.

Drawing some mock-ups for the food pantry project. I knew that this was the next small phase, but I kept making excuses not to jump into it. I basically had to break into it... it was a small mental barrier of sorts... it wasn't too bad, once I got in. This is just me, but I've done this tons of times, this just felt different in a way - my thinking was different - what do you want, how can you simplify it, hide all complexity until needed.

As long as I'm confessing... I was excited to be designing a new flow and product, but at the same time, thinking, man, how much work is this going to be? I have a little bit of mental trauma due some really long and ugly projects with zero funding and backing. Years and years, grinding through things. Those tend to suck the excitement out of the prospects and projects. Anyways, I am excited to see where this goes.

Reviewing a YouTube video that Steve sent to me. This is my second time watching it. I decided to take a few notes. The video was a tech talk from Tom Enden at a Wix Engineering Conference. Here are some of my notes:

- Being proud of code that I didn't write.

- Going beyond the building of the systems and into what is possible.

- He was proposing that English, real conversations and dialogue, are a rung in the ladder (changes in coding languages). That's the new coding language (English or plain speech).

- The power of dialogue and being involved, participating, guiding, prompting, etc. Not outsourcing thinking but making people think.

- One of the next topics was dealing with who owns the code? Distributed authorship and being original and yet building on top of other choices and decisions.

- We never have controlled all of the pieces; this seems to be a continuation of the same process. We assemble and put things together.

- Leveraging AI and being willing to stand behind it.

- Talking about "taste" and what you want. He was talking about taste as a skill.

- Judgement and choosing what to build. That is becoming the work now vs pure coding.

- Great video, I enjoyed it. Less than 20 minutes. Here is the YouTube link - Web link

Prep work for the food pantry recipe map project. Going over questions, writing up ideas, and working on prep work for wireframes for simple flow, dataflow, or specific workflows.

Met with Bryan to go over some code. We mostly talked and went over some black box stuff. He is on hold for a couple of projects. He is currently working on the Adi AI agent, a new left-side menu system for KOR systems (small white label) and a custom invoice for a client. After Bryan left, I recorded a few notes from yesterday and today.

Going over CSS rules and practice pages. Working through the W3Schools website on CSS. Pulled up a practice document and did a bunch of playing. I've done CSS for years, but I have never really taken a class on it. Trying to make sure that my basics are solid. Continuing education stuff.

Watching some videos on CSS and basic rules. Working through a few sections on W3Schools and CSS training. 

Learning as you go along. Learn things as you need them. You don't need to know everything up front. There is too much. We spent some time playing with AI and image generation. We looked at some of the videos that he, Russell, is doing. We then flipped over to the documentation project that we are working on. Russell was making a few changes, and I was playing with the app (experimenting). We did a little bit of light code review and playing with the actual image galleries and tools. Fun hands-on learning today.

Working with Bryan. He showed me some updates for the Adi AI agent stuff. We merged in a number of new changes. We then pushed it up to data 0 to do some testing. Fun to watch him work and see what we have to do to make things work. It gets pretty tricky. We had a few small glitches, but making progress. At the end, we setup another time to talk and work with this and other small projects for tomorrow.

After Bryan left, for another appointment, I spent some time looking around a bit and playing with some other new features that I see inside of the system. I believe that Steve and Josh have been working on adding some other nav and header stuff. It is still in a beta mode, but just checking things out. It has the branding of KOR or KOR ware (anyways, a slightly different branding).

Work session with ChatGPT. I was looking for an old, saved email and ran across an older version of the adilas blueprint document. I read it and then worked with ChatGPT to create a newer version of the blueprint. Great session. Here is the chat session link: https://chatgpt.com/share/6a7bda35-5d70-83e8-8a7f-5086c886a10c

Just for fun, here are a few things that we cover and go over:

The Adilas Blueprint moves from where we came from, through how the platform works, into where we believe it can go.

Foundation & Purpose - Sections 1-5 Purpose - Adilas in a Nutshell - The Problem We Are Trying to Solve - Origin & Development Philosophy - A Working System and a Working Prototype

The Adilas Model - Sections 6-10 The Adilas Formula - World Building & Industry-Specific Recipe Maps - The Transactional Core - The Data Assembly Line - World Structure & Time

Building on the Core - Sections 11-15 Simple First. Expand Forever. - Ship A & Ship B - The Value Add-On Core - Business Intelligence & Digital Storytelling - AI as a Layer and Cross-Layer Capability

What Makes It Adilas - Sections 16-17 What Makes Adilas Different - Community, Ecosystem & Shared Building

Future Direction - Sections 18-20 Where We Are Heading - An Open Future - Discussion & Exploration Points

The basic journey: Understand the problem - Build on a proven core - Mix the right ingredients - Build the business world - Generate desired outcomes - Keep expanding what is possible.

Here are links to both the older version 1 of the blueprint and the newer, more up to date version 2 of the blueprint. See the chat session link above for the process of updating the blueprint.

Reviewing and then jumping into making some wireframes for the food pantry project. Still in the prep steps of that process. Reread a small chat with ChatGPT on this industry specific recipe and workflow mapping project. Basically, how to assemble and configure the recipe for each industry, depending on which one we are working on. Think, reusable blueprint for other implementations.

Later on, I was looking over their assistance application documents and reports for the food pantry. Comparing online assistance application with the pre-printed forms. There are a number of differences. We will need to standardize the input to get the best results. Also, after making those comparisons, I spent some time looking at the required reports and making sure that we are catching the correct data.

Here are some of my notes, after rereading the ChatGPT session on doing industry specific recipe mappings.

- Think in business objects... 1. Households (the real customer), 2. Persons or people - adults, children, dependents, and their relationships, 3. Visits, 4. Alerts, 5. Notes, and 6. Reports.

- Workflow mapping - instead of pages... what is the workflow or journey?

- MVP Bridges - keep one platform, create a focused front-end, hide complexity, expose power only where or when needed, let organizations frow into the larger ecosystem.

- Mini skin framework, industry recipe map, ingredients (existing pieces, parts, and functionality), mix and blend, then adapt or add industry adaptation stuff to round out the project. Focus on the desired outcomes and needs.

- How can I/we help?

- Find the moments - at times, the system (software) needs to both appear or disappear. Help guide where needed and other times be in the background (transparent).

- This recipe may become one of many.

- Instead of selling modules, we are using existing, proven components, and assembling or configuring them for a different industry.

- Once again, having fun comparing industry recipe maps and world building. I think that it is fun. They work well together and even allow for crossover. See elements of time # 13015 in the shop for an earlier breakthrough between industry recipe mappings and world building. As a side note, that was only a week ago.

- Reusable blueprints for other implementations

Phone call with Josh. He wants me to jump in and help them do a bunch of user interface changes inside of adilas. I told him that I was working on some other pieces and projects. Everybody thinks that the existing adilas platform is our full product. In some ways, that is correct. In my mind, the existing system is just the working prototype of what it could be, not the actual final product. We get judged super harshly on what it looks like. That was not the original goal. The original goal was more of a "could we" and "can we" do this and that? Okay, now that we can see that, the goal needs to switch, but that was not the original goal. The current adilas.biz system is just a prototype of where we want it to go.

The other thing that we keep seeing is that certain people are judging us saying, why don't you do this and that? They are great questions and they have a valid point. However, they kind of just expect us to do it, not thinking about how much that costs or the time that it would take. We have taken a different path through the woods, people like a lot of what we have done and/or are doing. They just expect it to be fully done and wrapped up (all shinny). We have been building this out of a garage and bootstrapping it along, the whole way. this is where we are at.

I really hope that we can get someone to see, wow, if I put some money in and help fund this (gas money or seed money), we could take this whole product, system, application, and platform super far. If not, meaning we don't get outside funding, we'll just keep chipping away at it as we can. I know that it is bigger than I am.

I really like the idea of being a pioneer and helping to pave the road for other future generations. I don't have to build the whole thing, I just want to keep helping and smooth the way for others.

Emails and reading through some feedback from Steve and Grok on the adilas mini pitch. It has some great stuff in it. I have attached the feedback (copy and paste from the email) to this element of time. See attached.

I then switched over to do some planning for the food pantry industry project. As I started, I had the thought to review an older document about taking control of the documentation processes. I have read this document a number of times. Great read. This time, I pulled up the document on one screen and put it into a screen reader on my other screen. It was much easier to read it this time around. I was also able to stop the screen reader and circle back around on key points that interested me. In a way, I'm a want-to-be project manager... :) I've got a number of big projects ahead of me. I've been learning and trying to apply things for years. I've done tons of projects. It has been a process for me. I enjoy it. See attached for a copy of the document that I was reviewing. Once again, I recommend a screen reader for reviewing its contents.

Recording notes from 8/4/26 to 8/7/26. Many of these new entries had a number of graphics and images. Fun to see things come together.

Adding some new links to the adilas pitch, similar to what I did for the mini pitch. More fixing up the bigger adilas pitch (10 slides) with small graphic changes, text changes, and small mini links out to bigger pages. Adding some links to the investment opportunities page and other adilas lite - fracture pages for the new adilas mini pitch. Trying to spread it around. I think that it could be a great little marketing document for adilas. Short, simple, power packed, and visual. Good stuff.

Meeting with Hamid. He showed me some of his progress. We pushed up his code to the live server. We then sent an email to Wayne asking him to wire up the domain playatthewall.com to the site. In the meantime, we pushed it up to a folder on the adilas server. Next week we will jump back into some more CSS stuff and training. Until the mapping to the real domain goes live, you can see his small promotion website here.

Meeting with Adesh from Solen (investors and software company). Good meeting. Talking numbers, history, story, direction, fun conversation. He said that he would take the info along and pass it along to his internal team. As a side note, of all of the investor meetings that I've been on, this one was pretty casual and fun. I enjoyed it. Sometimes, they can be pretty stressful and you're not sure what they are looking for. Anyways, it went well.

Finishing up the adilas mini pitch. Added a small plus sign, in the bottom righthand corner, to each of the mini pitch slides to show that you could click on the graphics for more information. Paying bills and recording notes. Looking around at some new changes inside of adilas.

Working with Abby and Russell. We were working on changes and grid system training. I put the mini pitch into the documentation project while Russell was making other small changes. It was super fun seeing it come to life with real images and content. I was using the auto build sub navigation, gallery options, sliders, search options, etc. Fun session today. See attached for some small graphics.

Meeting with Abby. We all, most of us, have a need for people, interacting with people, for mental health. We were going over some new graphic ideas for "cookbooks for businesses". See element of time # 13015 for details - dealing with industry specific recipe maps or industry recipe mapping. We went over the new mini pitch together. I also got some new graphics. See attached.

Working with Heather to simplify some of the PowerPoint slide presentations and show what we are working on. Going over existing graphics and slides. Talking about ways to remove some of the clutter. Working on a 4 to 5 slide mini pitch. Changed up one of the main systemized approach graphics. Made it bigger and more simple. Along with that, I started a new ChatGPT session to help with the new images for the mini pitch. See attached for some of the new graphics. Fun session.

Here is the ChatGPT chat session link for the session: https://chatgpt.com/share/6a7383e6-7850-83e8-9d1a-b92b80d32da0

If you want to access the actual PowerPoint presentation, 10-slide version, click here: PowerPoint Link. If you want a PDF version, click here: PDF Link

We have also prepared a small 5-slide summary for what we are calling "The Adilas Mini Pitch". If you want to access the actual PowerPoint presentation for the Adilas mini pitch, click here: PowerPoint Link. If you want a PDF version, click here: PDF Link

Emails and recording time. Other small odds and ends. Reviewing and planning the new site for the food pantry. Added some new verbiage to the adilas value add-on core model (master plan).

As part of my review, I was re-reading over some plans that I was working on with ChatGPT for the food pantry - https://chatgpt.com/share/6a5287b4-8b28-83e8-9057-76e9a8d209cb

Here are some of my notes from reviewing the prior chat session:

- Industry adaptation project

- Guided experience for one specific workflow

- Not software... more of a "Volunteer Operations Console"

- At the software level... What do I need to know right now? Try to stay ahead of them.

- Goals: 1. Simple client intake - paper and online - make it simple, 2. Find people instantly (by name, address, barcode, and household), 3. Protect volunteers - alerts and possible workflow disruption feature, meaning, we may need to stop the normal flow until the alert is dealt with or acknowledged, 4. Track visits, and 5. Future client app - this may be a round II or phase II option. Focus on the MVP first.

- Workflow mapping - what do they actually do and in what order?

- This is an MVP bridge type app - keep one platform, create a focused front-end, hide complexity, expose power only when needed, and let organizations grow into the larger ecosystem.

- Mini skin framework - industry specific recipe map - ingredients, workflows, industry adaptation, and generate desired outcomes.

- Serve people over software - focus on the people and serving them

- Look for moments vs screens - aka "Workflow mapping" - Think flow and questions and how can I help vs just interface and software.

- Plan it, meaning this mini project framework, as a case study or industry recipe

- Industry recipe maps and world building - somewhat interchangeable terms - this was a new discover for me. I personally like world building better, but if someone is struggling with what that means, you could always say something like: Another term for world building is "industry specific recipe maps". Instead of selling specific modules or software pieces, you assemble industry specific solutions from a number of proven components. You take business functions and application players (like customers, invoices, inventory items, vendors, etc.), mix them together and these become your ingredients. You then setup specific workflows, industry adaptation, and generate desired outcomes. It becomes an industry specific recipe of sorts.

- Think reusable blueprints - per industry

Emails, paying bills, working on content for world building and tying things into the adilas core concepts. Working on the sections for decisions, choices, and consequences. See attached for my progress.

Great meeting with Hamid. We jumped on ChatGPT and passed it some of his older code for a new website called "Play at the wall". Eventually, this will be an adilas website to help with API sockets and API endpoints. He was working on generating new content. We went through a process of taking the code that he was working on and then passing it back through ChatGPT to help with some clean-up. Good session. Here is the chat link, if needed. https://chatgpt.com/share/6a6bf039-222c-83e8-b0e9-46d4a9243ea0

Emails, recording notes, and then some page changes out in the adilas lite - fracture section of the site. Adding some links to the PowerPoint slides so that you could get to the full-sized images from each slide. Pushed up a number of small changes and files. Added a video link to the adilas pitch from the videos and research page.

Work session with Russell. We have gotten our documentation project done enough that I got some live code on my machine today. That was fun. I was playing around with things and doing small samples. it should be really fun. We are still doing some code review, but it won't be too long, and I will branch off of his code branch and start making it real for adilas and the adilas presentation gallery stuff that we want to put in it. I'm excited.

Working on the world building document. Reading and brainstorming on ideas and concepts. See attached for my progress. Still just roughing things in.

Meeting with Bryan. Going over some new changes. He is working with all of the main quick search prompts and being able to show the prompts and keywords to help the users. He's making progress and doing well. We pushed up a couple of small changes. Small chats about the future and what we are seeing and hoping for.

Recording notes and reviewing a video from Cory about vendor credits. Emails and then jumping back into the changes on the help files and help navigation stuff. Updated the "all help files" page as well. Pushed up some new code to test live on data 0.

Emails, phone call with Bryan, and light research. Recording notes and hours from last week. Adding links to some of the help files. Reworked the help navigation on the main help pages. Made it look a little bit more modern. Added a show/hide more options with other navigation buttons. Exporting some new mini screenshots and graphics. Almost got the new changes finished. I will wrap it up tomorrow.

Recording notes from 7/22/26 to 7/24/26.

Small fix for Bryan and the Adi AI agent. Merged in some new files and pushed them up for Bryan. Steve wants us to turn the Adi AI agent off until we get a few things fixed. It's kinda sad. Mostly, people, our clients, are freaking out about having all pages run in the Adi shell (iframe). They are used to seeing the full URL with id's and such. Some of them like to use multiple windows, multiple tabs, etc. I think that they don't like change. It is way better than what we have, but they are making blanket decisions and just turning everything off, even if people like it. Oh well, we'll get there. Just a bump in the road.

Meeting with Hamid. We were extracting some of the HTML and CSS from his Next.js code project. Trying to put things back together. The first time, and second time, he sent me some files, there were tons of them (in the thousands). We now have it down to 4 files vs too many to count. The current code needs to be reworked and formatted. Making progress and harvesting code from his project. See attached for a small screenshot.

Went into the Cache Food Pantry to work with their staff. I'm experimenting and seeing if we can help them out with a super simple adilas system. Spent the time with a couple of the key players, watching what they do, taking notes, and sketching a few things out on paper. See attached for some of my notes. It should be a fun project.

Work session with Russell. Working through parts of the documentation project. We are suckers for eye candy. Make it look good. Russell was working on polishing up the different image galleries. We are both using this project as continuing education stuff. Great practice sessions with a purpose.

Working on world building concepts. Trying to combine a couple of documents together with concepts of world building and how adilas is kinda like a digital video recorder for your business. Working on how those two concepts work together to help with digital storytelling. See attached for my progress (still kinda rough).

Small code fix for the parts homepage. It was hiding or collapsing the search form when you first go to the page. Added some code to help it show the search form under certain conditions. It will also hide the search criteria as needed. Small changes. Pushed up some new code to data 0 and sent an email to Wayne, Cory, and Steve.

Reading emails. Working on the adilas core concepts overview document. More brainstorming and reading over the older documents. I'm not sure why, but I keep being drawn back to these underlying core concepts. They have a real value, both as building blocks as well as underlying rules, principles, and instructions. If someone just sees a list of the core concepts, they may think... that is great and all, but how does that affect or dictate what goes on in my business? I'm trying to go through the core concepts and create links back to how they help, organize, and create the underlying structure of world building and how that works for businesses. My focus today switched from just going over core concepts to how do these relate and facilitate world building. That was a fun switch for me.

Sat in on an online webinar about buying and selling a business. The host was Ross from the Front Range Business Advisors. He did a great job and brought a lot of personal experience and information to the table. Here are some of my notes:

- Why certain deals don't close - what are the deal killers.

- Lots of prep work. He kept coming back to this topic.

- You need to have some written processes in place.

- Key players (person or persons that are critical to the deal and/or success of the business). This is a big deal. The new owners need to see themselves and/or some other person filling that role. What does that look like?

- Flushing out some of the real concerns. Lifting the rug and really showing what is going on. Over disclose and then manage what is needed.

- Communication is a huge key - alignment is needed. Things tend to unwind in silence.

- Owner's emotional attachment to the business. What is your identity and who you are? Are they tied to the business? That can create and cause problems down the road.

- Due diligence and looking for those skeletons in the closet.

- Often a buyer is looking for SOP's (standard operating procedures). You need to make the value of the company transferable.

- Take time and make sure and look at client relationships, operational knowledge, vendor relationships, brand/reputation, and employee loyalty.

- Small discussion on cold feet and a tire-kickers. This could be people who aren't sure, just looking for information, and/or aren't fully committed (yet).

- Confusing between buyer enthusiasm and buyer readiness. There is a difference.

- One of the biggest problems is trying to do renegotiation at the finish line.

- Dealing with emotional pressure, not data. Digging into the feelings of or what's behind the questions?

- Preparation is one of the main keys to really selling a business. Clean the books, reduce the owner dependency, align the advisory team, and prepare seller psychology (ask yourself hard questions).

- Figure on a 2-3 years exit prep (it could be shorter, but it takes time). Balance and look at both data and emotional factors. Make a strategic exit plan.

Working with Bryan. He was working with some Grok AI voices. I made a small fix on the parts homepage to show/hide the search criteria. While I was working on that, Bryan was changing out the browser voice stuff. We pushed up some code for Byran. We then talked about normalization and working on voice to text options. We may have to take a break, due to budgets, but Bryan wants to get a list of the next phases and pieces of where it could go. We are joking around, but... we are teasing and saying that he has the Adi AI agent to a 5th grade level. We of course, want it to a college or PHD level, but we are making progress.

Jumped on with Cory, Steve, and Wayne to look at a bug on the ColdFusion servers. Somehow, it was not registering the form scope or form submission values. Nobody could login. We got it fixed and rebooted a number of servers. Wayne is going to look deeper into what might be going on and see if he can see anything in the logs. Crazy stuff. Good team effort to get it fixed.

Looking at new changes to the Adi AI agent with Bryan. He was making a number of new changes and such. Some great little changes. He is getting into the groove and making progress. We pushed up some small changes to data 0 for testing and setup a new time to meet on Monday. He has a couple of other things that he wants to tweak and alter. Good stuff.

Small label builder fix. Added an option where the label could be static and not tied to an application type (one of the 12 main players). Recording notes from 7/13/26 to 7/16/26.

Work session with Russell. Cleaning up code in the documentation project. The AI agent had added tons of inline styles and CSS stuff. We tried to have AI do some cleaning it up, but it was either taking too long, cost too many credits, or wasn't doing a good enough job. Interesting to see what it can do and what it cannot do. There is a cost to everything. If you go super fast, you end up with tons of bloat and extra code. If you try to trim it down, it either takes time or credits (tokens). Most of the changes were in our own documentation of the tool itself. Good work session.

Working with Bryan. Quick touch base and then made some plans for tomorrow. His new Adi AI agent went live this morning. Minimal hiccups. We had one client complain about the new Adi shell wrapper vs normal URL's. They have a custom flow and monitor the URL addresses. We helped them turn it off, so that it went back to the old way.

Working with Bryan. He was showing me some new changes. He is working with AI to help with the AI agent. He is clicking through things and resolving different issues. He has made some great connections and good progress. We made a few more changes, checked things out, and he pushed up some new code. It is looking good. The next major thing is code review, fix a few merge conflicts, and push it live.

We got it all fixed and then I tried using it on my local environment. It was struggling a bit. We spent some more time and got it working. There are a few quirky things, but all in all, we got it rolling.

Went into the food pantry and did some observations. Briefly met with Matt, the owner. Then I went out on the floor and worked with one of the volunteers at the front desk where people were checking in. They, the food pantry, already have a software system but they are looking at making some changes. I was mostly just watching what they were doing. The nice lady at the front counter was very helpful.

We did look over the existing software system. The existing system that they have does track what they need but it is too complicated. I went with the intent of making some notes, but I ended up just watching and observing. My main takeaway was keep it super simple, repetitive, and streamlined. I'm planning on going back and really taking some notes. Today ended up being just the feeling and vibe of the food pantry.

Getting a list of ChatGPT sessions that I have done over the months. Lightly looking over some of them. Quick casual browsing. Web link - developer's notebook for ChatGPT sessions.

Meeting with Bryan. We are working on his Adi AI agent. He was going over the current level of functionality. He was showing me a number of sub searches and showing me what it does. We then got into a section that was dealing with layered frames and framesets. His AI agent is running in an iframe or higher level frame set. It gets kinda funky when you are navigating up and down frames. Some of the older code used to be the top most frameset. Now, with the newer AI agent, it is no longer the top most frameset. Not impossible, but it does complicate it a little bit. Working over some issues and getting some ideas. He is going to go back and play around with it, and we'll meet up again tomorrow.

Working on the simple CRM and user experience project for the food bank. Prepped some information, sent my information and a voice dictation over the ChatGPT to go over some ideas and direction. I then sent a small follow-up email to see when I could come and do some observations.

Here is the chat link for the start of the food pantry user experience: https://chatgpt.com/share/6a5287b4-8b28-83e8-9057-76e9a8d209cb

Touching base with a few people about the first pitch night last night. Quick text messages and thank you's. Recording some bills and expenses. Recording notes from 7/6/26 to 7/10/26.

Went into town, to a city called Wellsville, UT. I participated in pitch night and did a small pitch for adilas. I did the pitch and then answered some questions and what not. Good stuff. Great learning session. I have spoken about adilas, numerous times. This was the first time with a set or semi-set pitch and sides on a PowerPoint presentation. Good session. Not a super huge crowd, maybe 15 people. All in all, good practice session.

Odds and ends. Texts, emails, paying bills, phone calls, etc. Small changes to the PowerPoint presentation. Added in some different screenshots of the presentation gallery (larger sales tool). Got some feedback and then took them back out. Heather helped me make some decisions and helped make it better.

Working on adding in the adilas AI assets to the adilas lite (fracture) plans. That page, adilas AI assets, has existed for a number of months but wasn't ready to be fully public until just a few days ago. Adding it into menus, as buttons, and links from other pages. Scanning images and entering some receipt payments.

Emails and then making some small CSS changes for the watermarks. Working with Wayne to figure out a plan. Apparently, the old way of doing it (we've been using for years) was actually causing some slower load times. Downloading some new printer drivers. Trying to get some things ready for a presentation tomorrow. Printed out a bunch of flyers and graphics. Got a zip file from Hamid and unzipped it and looked around. It is for a new smaller website. We may have to narrow it down a bit. The zip file included too many files (bloated). We will work it out and tighten things up. I think that he just wanted to show me his progress. He is trying to just use AI to build this one vs doing it on his own. We are all playing through the AI learning curve.

Working with Russell and Abby. Russell helped me look over some code to help with some adilas stuff. Small changes. We then jumped back on to our document project. Going over the different pieces. Working on the little mini functionality and even documenting the pieces that we have, existing functionality. Small session documenting the document today.

Working with Abby. Showing her some new graphics and where we put different things. Some of them, meaning the new graphics, were from here. She then had me do a practice presentation using the PowerPoint slides and give her a mock pitch/presentation. Talking about where we are heading.

Adding some new content for the AI assets page. Adding links to different pages on the adilas lite plans. More links, graphics, and AI content on the AI assets page. Added in some graphics on the investment options page for adilas.

Recording notes from the end of last week. Light clean-up.

Working with Bryan on his AI agent. We were working with some navigation and page redirects. We did some work on the login action, choose corp action, new and updates, logout, and my settings action pages. All of those places needed some deeper redirect logic to help with show/hide options for the new AI agent that Bryan is working on. Good work session.

I had to update some Git and Bitbucket settings on my local machine. I then spent some time adding graphics to the adilas value add-on core model page in the adilas lite section of the website. Lots of new graphics from Abby. Here is a link to that value add-on core section.

Later in the day, I did another session and spent some time working on the AI assets page. Adding in links to simple documents. I didn't quite finish but got a small start. Here is a link to the AI assets page.

Rereading some document dealing with offers that we have extended to Andrew. Sent Steve a text with some suggestions. Recording notes from 6/25/26 to 6/27/26. Lots of new graphics, see those entries for more details.

Working with Bryan. He has done nine mini versions with ChatGPT to work on the Adi AI stuff. He did a few with Gemini and then switched to other AI models. Working on intent detection, phrase normalization, intent routing, TTS (text to speech), learning over time, and AI assistant stuff. He was showing me some of his chats, plans, and actions. He has some other plans for the future. Some of the things are close, just not quite all the way done. Talking about Bryan's AI testing and training data. I wasn't sure if we were trying to harness that (his testing and training data) or just moving it forward and will let it start from scratch and then move forward.

After reviewing things, we spent the rest of the session going over code and making some small tweaks. We removed a couple of settings and started working on the key places where the session variables change. We got in pretty deep on some of the pages that handle dynamic redirects based on saved settings and default homepages vs just normal straight links and navigation. We got it to a stable point and will have to circle back around. It gets super deep.

Working with Russell and Abby. He had made a number of changes and was showing us some things. Adding in image and text sliders to our project. Watching him and talking about new changes. The whole session was working through a small tick list of features to add and changes to make. Super fun to watch his process. Playing with the tools and finding and fixing small errors. There is a difference between developers and their testing vs a real user and how they actually use the tool. Good session.

Meeting with Abby. Going over adilas engine graphics and then moved into some new graphics for recording the story. Went over some ideas with Abby and talking about direction. We went over some older graphics that had funnels, inputs, outputs, and tools graphics. Mostly a brainstorming session on graphics.

Printing documents at FedEx/Kinkos, then later at Staples. Went in and did a live demo with the local food bank. We are going to work on some custom code together. They currently have a system, but it is way too complicated. Took some documents to Gene's house. I also dropped off some documents at Jim Wilson's house as well. Talked with Jim for a half an hour.

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.

Showing the presentation to my mom. She recommended a few small changes. Pushing up files online for the adilas pitch. See element of time # 12962 for the pitch stuff. Recording notes from 6/23/26.

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.