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

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

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

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

- "Adi go" - command prompt - We already have "Adi" as our little blue dog avatar (helper or mascot). Maybe using "Adi" as a command prompt. Idea from Steve.

- Sell what we have

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

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

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

- Be able to build and show the prompts and what they are tied to. Simple user interface to setup and maintain their own AI quick search prompts. Very similar to the icon payee top links in the snow owl theme, but even more, and easier to get to... they would be clickable and usable in the AI quick search text fields. Anywhere in the system... That would be super cool! Even better than the icon payee top links.

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

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

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

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

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

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

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

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

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

Meeting with the Nxtlinq guys. Going over progress. Then talking about multi-tenant options (settings, domains, corps, keys, secrets). We setup some small dates and goals to get an MVP up and live. Other small talks on different subjects. Fairly quick meeting.

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

Here are a few other notes from our meeting:

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

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

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

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

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

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

Working with Russell. Talking with Chuck for a few minutes and catching up. They, Russell and Chuck, were on a previous meeting. After Chuck left, Russell and I did a little flashback and were talking about CSS and modern tech. Sometimes it is hard to try to keep up with all of the changes. The old basics are still super important. A developer needs html, JavaScript, CSS, SQL, and some kind of backend technology.

As we were working today, we were talking about exposure, in development, leads to some new ideas and knowing what is possible. Not all exposure is good, but certain kinds of exposure can really help you imagine what is possible. Once you know that, it isn't super hard to then go try to figure it out. Granted, the term "isn't super hard" is relative...

We did some training on the VS code interface, some speed tips, some Git tips (code repository and branching stuff), and then spent some time tweaking a little bit of adilas code. We changed some older hardcoded values (in the CSS) to use flex box instead of older direct positioning. Good little training session.

Working with Shannon. Small recap on what we were working with last time. Talking about templates and going from static to dynamic templates. We briefly talked about when I started creating web pages, each one was a static page (copy and paste) from template of sorts. Then once we added database connections, we really were able to use a dynamic, data-driven template page. That was a huge building block.

We then switched over to adding new content for the fracture plans. Working on the modular architecture sections. At the end of our session, we were talking about old CSS and more modern CSS stuff. We even looked at some examples (some of our old stuff). Crazy how fast things are changing and what it takes to keep up in this high-paced world.

As a side note, we were working on some new documentation and using AI to help us refine some of the content. It started to joke around with us a bit. That was kinda fun. It added a couple of sarcastic prompts. It made me laugh and Shannon and I had a small discussion on "joke settings" and "changing levels" on those settings.

Working on help files for sub inventory attributes and templates. Also started to work on help files for parent attributes and high-level templates.

Small data clean-up for a client. I had some old code but had to tweak it a bit. The new request was specific for just certain changes.

A couple of sessions today. Total time was just under five hours. Here are the notes from the different sessions.

Organizing my to do list. Back working on new AI quick search prompts. Started adding a number of new part/item prompts. These are things like printable lists, grouped inventory, global mark-up, view ecommerce items, and find & replace functions. Updating help files for ecommerce settings. Working on adding things like part categories, sub attributes, and parent attributes. Some of these still need some help with their help files. Once that is finished up, I will provide the correct documentation and let our users know. Currently, a couple of those are hidden (for now). I will expose them once we fix the help files.

Working with Abby (my daughter). Going over some ideas for projects. She is going to do some graphics for some of our projects. She is hoping to do 15-25 hours a week. I will pay her for now until it gets approved from adilas. We went over what she had done, the last time that she worked with us. She is excited and has some direction. We'll see where it goes. I'm excited to see what she comes up with. She is very creative. We spent some time going over timelines and versions of adilas. Abby is going to make up some graphics to help show some of those things and how the development story unfolded. Should be fun.

Recording notes from the day. Busy day. There are a lot of moving parts and pieces to this game we are playing. Very interesting... :)

Meeting with the Nxtlinq guys. They have automated and worked with 350+ tools to date (adilas AI quick search prompts). We were talking about testing. Going over the auditability (following the audit trail) and tokenization tracking. We want it to be more loose and they want it to fully follow full block chain tokenization stuff. Functional testing vs real user experience testing. Talking about really beating things up. We are trying to get things done within about a week as far as all of the tools. We are shooting for sub 500 total tools. That means I have another 100 or so still to go before next week... I hope I make it... :) I've got a list, a plan, and a bunch of notes... What I don't have is time.

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

Working with Shannon. She and I were working on the adilas fracture and adilas lite content (planning). We kept bouncing between creating new content and what is going on inside of adilas. Fun to see how things are working together and we are making progress in leaps and bounds. It feels like we are sewing things up and bringing things together. Today we were working on sections for customize everything and setup wizards. Good session.

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

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

Six different sessions throughout the day. Starting at 7:30 am and ending around 1:15 am (on the 14th). Long day. Here are a few of the things that we did.

- Working on help files and emails.

- More work on help files and navigation options. Recording notes from Saturday, big work session day. Back rolling through the additions, changes, and updates for the AI quick search prompts. More navigation and help options. Trying to expose some of the different resources like switching corporations and the developer's notebook.

- Working on new prompts for the API sockets and other key pages. Spending some time in the invoice and deposit sections. Things like apply payments, show invoice payments not yet deposited, sales tax reports, etc.

- Adding in a new payee lookup for the mini API, at Matt's request (from Nxtlinq). Started working on the new code.

- Working on some new code for a vendor lookup and an employee lookup for the mini API. Working on the code, testing, and pushing things up. More work on documentation. Then went to all servers and pushed up new database records for help files (10 new ones) and new permissions (7 new ones). Did that for all of the servers. Email to the guys at Nxtlinq with some instructions.

Recording notes. Working on new modal popup to help with the normal quick search that shows up on every page. I want to help people get to the prompts.

New AI quick search prompts, options, and keywords. Doing some more detailed ones and ones that we had missed. Kinda filling in the gaps a bit. New nav options, new help options, and other values. Ran out of time, didn't push up the new code. It will be good when we push it up.

This is more for me, but in a way, I'm also hanging out some of our dirty laundry (sections that aren't fully done yet or that we are still working on). It is probably good for me. I don't like doing that. I like it to be fully done and ready (ish) before pushing up live. I saved everything to a new code branch. I'll merge it in on Monday. Good work session.

Looking into ideas on the reverse shopping cart for specific items for a vendor. Did some brief research. It sure would be nice if we could use existing tools to search for PO items. Then once they show up, be able to do the reverse shopping cart stuff. This feature has been requested many times, clear back from 2009 and 2010. Maybe a switch or something to help use the same pages. Started looking at other bulk tools. Small tweak to the bulk transfer parts page. I was checking it out and then looking at other bulk tools.

Recording notes and looking at some JavaScript and what it would take to make a few changes on some pages (math calculation stuff). Then working on some new AI quick search prompts. Light code and logic refinements.

Working with Russell. We jumped in and played with writing ColdFusion in VS code editor. We then spent some time inside of Chat GPT playing with snippets and converting Sublime Text snippets into VS code snippets. It went pretty well. I ran out of my free version (number of requests) for Chat GPT. I may need to get the paid version here soon. After that, Russell was showing me some of his AI image generation stuff that it was doing. We were playing with some images and then having it make some different versions of the images. Fun stuff. Mostly an exploratory learning session today. I enjoyed it.

Working with Shannon. Looking around a bit on some of the existing pieces that we have pushed out recently (AI quick search stuff). Small tour and update for Shannon. That was fun. Looking at potential and current paradigm shifts (our way of thinking). We looked at some plans that we are making and also spent some time looking at some graphics (prep stuff and planning). We know that we will have some needs for more content (writing things up) and graphic design work coming up soon. Looking to see what we can have Abby (my daughter) do to help us out. She would like to start working with Shannon and I next week.

Switched over to planning and writing out content for adilas lite and fracture page (plans). We were on the customize everything section. As we were talking, we got into a conversation about the adilas transactional core and the strong foundation of permissions, settings, and templates (grouping things together for storage, speed, consistency, and organization). We haven't talked too much about templates yet. Templates help you group, organize, and setup a pattern of sorts - make it quick and repeatable. We talked about industry specific skins, bulk settings based on functionality, and other templates that exist right now. Technically, even the organization of the adilas database is a template of sorts (what goes where and how do things work together). We got into talking about organization within pages, dynamic content, what is static, what is dynamic, and what is alterable by a user, based on permissions and settings. We talked about different levels within the settings and how to group things together. We see at least four levels in the settings at this point. They are corporation level (world level), group level (main players), page level, and user level. Fun conversation.

Recording notes from the past couple of days and doing emails. Paying bills and recording expenses.

Opening up the time id in the edit mode for sub dates and times. This is in case the sub time record gets put on the wrong main element of time. This was a request from a potential client. I thought that it was a good idea. I could see how this could be useful.

Spent some time getting back into the partial PO project. Looking into tracking PO back orders and partial payments or partial receiving PO line items. I'm glad that I wrote some notes (almost 20 pages). It's been almost four months since I was on this project. It took a few minutes to get my head back in the game.

Helping to open up the date field on vendor credits. It actually took a bit of work. I thought that it would be pretty easy, but it had some hidden catches. Anyways, we got it done. This was a request from Shari O. and Cory to finish up vendor credits and other special account transactions.

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

Talking to Bryan about AI quick search options. We went over some vision stuff and where we are wanting to go vs where we are at. Then we switched over to talking about changing out our prices (lowing them) so that people will buy more. He was showing me some examples: Say we charge a $100/hour or $150/hour, how many hours of custom programming would we get? What if the price was $50/hour or $65/hour, what would that look like? Bryan was showing me some potential curves and what some of that might look like. Fun ideas. We may want to play with this and see what happens. Not everything will go this way.

After the meeting with Bryan, I switched over and did a multi-hour session on AI quick search prompts. Adding photo and scan prompts to all of the main sections. Doing some crisscrossing of the different sections. Switched over to other main navigation pages and their prompts and shortcuts. One thing that was different with this section was, I would code it, test it, create the prompt documentation, add it to the help file, push it live, retest it live. I wasn't just coding or just doing documentation. I was doing all of the pieces, then repeat. Small little sections but finishing them up. That was kinda fun. I never let it get out of balance, I would code, test, and make sure that the documentation was there. Good little session.

Working on new AI search prompts and actions. Going through Bryan's list and adding code, prompts, and help file entries.

Reading over some notes from Bryan. He was doing some prep work on the AI prompts, keywords, and options. Small changes and cascading changes to prompts and help files.

Formatting a number of AI quick search prompts. Worked on the stock/units, elements of time, vendor/payees, and VIN/serial number prompts and keywords. See this help file for some of those pieces.

Quick meeting with Bryan. He was doing some research for me on new AI quick search prompts to help round out the navigation section. He passed me over a bunch of things via the GoToMeeting chat. I'll try to work on them before tomorrow evening, meeting with the Nxtlinq guys.

Recording notes from 9/25/25 to 10/4/25. I was way behind after going to the Adobe ColdFusion conference. Feels good to get caught up again.

Working on tightening up the logic on the employee/user quick search. Started to record the employee/user prompts and keywords into the bigger prompts help file. Finished up the help files (for now). Had to combine four help files to fit it all in. Sewing... but no needle and thread... digital weaving and sewing.

Working on prompts and documentation for employee/users. Another long session. Click here to see some of the prompts, keywords, and options.

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

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

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

Notes from Alan:

- Shifting our mindset a little bit

- What is working and what is not working

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

- Being proactive in our approach

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

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

- Maybe some new dashboards

- AI is amazing when it works

- Using AI to help us modernize our interface

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

- Taking about proactive maintenance

- He (Alan) sometimes struggles with communication

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

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

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

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

- Talking about dreams and what would that look like

- Stuck in between what we want and what we have

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

- Running in circles

- Chasing a ghost (phantom look and feel)

- Alan asking about the goal with the investors

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

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

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

- Talking about adilas and where we are at financially

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

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

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

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

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

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

- Looking around in the system a bit

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

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

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

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

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

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

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

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

- We have an MVP (minimal viable product)

- Finding people who are happy with what we have

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

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

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

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

- Shooting for $400/month

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

- Learning to say no

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

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

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

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

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

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

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

- Just tell everyone what you do (from Kiva)

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

- Being outside and out and about

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

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

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

- Stay on the good side of town

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

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

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

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

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

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

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

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

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

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

- Maybe look at some sport teams - other team sports

- Not trying to sell things, just doing some exploring

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

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

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

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

AI Summary:

Sales & Strategy Meeting Summary

Attendees: Alan, Steve, Bryan

Date: [Insert Date]

Meeting Overview

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

Key Discussion Points

Alan’s Focus

• 
  

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

  
  


• 
  

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

  
  


• 
  

  Emphasized AI modernization for the Adilas interface.

  
  


• 
  

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

  
  


• 
  

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

  
  


• 
  

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

  
  

Steve’s Focus

• 
  

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

  
  


• 
  

  Acknowledged issues with time estimates and scope management.

  
  


• 
  

  Proposed pricing structure:

  
  
  
  
  • 
    

    $100/hour for development

    
    
  
  
  • 
    

    $65/hour for setup/support

    
    
  
  
  
  


• 
  

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

  
  


• 
  

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

  
  


• 
  

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

  
  


• 
  

  Encouraged avoiding excessive custom development to protect scalability.

  
  


• 
  

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

  
  

Action Items

• 
  

  Define the ideal client profile and align pricing accordingly.

  
  


• 
  

  Increase focus on sales, marketing, and client outreach.

  
  


• 
  

  Use AI strategically to streamline operations and modernize the platform.

  
  


• 
  

  Improve internal communication and proactive planning.

  
  


• 
  

  Explore investor options and sustainable growth strategies.

  
  

Checking emails and light research. Small AI quick search changes. Reading over notes from the Adobe ColdFusion Summit Conference from last week. Scanned my notebook and made a multi-page PDF file of my notes. Recording other notes from 9/22/25 to 9/23/25.

Documentation and then working with Bryan again to get his new code implemented into the system. Lots of back and forth, testing, documenting, and pushing up code.

Meeting with the Nxtlinq folks. We presented on what we have been doing. I showed them some new stuff and all of the new prompts and documentation. Hopefully it is helping them out. I am happy with it. The new prompts are already making my life easier (I have been using them).

Working with Bryan to get his new prompts and AI quick search options live and online. He did quite a bit of work. We got together to do some work. He is going to go back through some stuff and do some clean-up. We will meet back up and try to merge and push things up live.

Working with Shannon. Small recap of what we are working on. I showed her some of the new AI options, keywords, and prompts. That is going well. We then switched over to working on new content for the adilas cafe project and fracture (adilas lite). Good session. Next time we will be adding in more content to the fracture and adilas lite plans. Good stuff.

Working with Bryan on his new keywords and prompts. We also did some work on allowing for the calculate payroll to be used through the AI prompts and keywords.

Reviewing the document that Suzi made for some simple step-by-step instructions. Looks great! See attached for the file. Switched over to doing more documentation of the AI quick search prompts, keywords, and options.

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

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

Working with Russell. Talking security with Russell on the AI quick search. Talking about customer data, employee data, banks, financials, and tons of other data. After that, we switched over to training on CSS.

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

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

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

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

Working with Shannon. Working on adilas lite content and new content for the adilas cafe page and plan. We went over the overview, personal profile, ways to work, and ways to play.

Going over the plan for receiving partial PO's

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

Working on documentation. Pushed up new code and did some work on the AI prompts and keywords help file.

Working with Bryan. He is coding some of the nav options for the AI quick search. He is working on the employee/user options. We went through a few of the new prompts and I answered some questions. He is going in a good direction. We will meet up tomorrow at 3 pm to see what we can mix together. I am hoping to mix what I am doing with what he is doing - all in the AI quick search stuff. After Bryan left, I started working more on documentation and such.

Here is a link to the AI quick search prompts help file that I am working on.

Documentation and recording notes for keywords, options, and prompts for the AI quick search. Got a small PDF from Suzi with some step-by-step instructions. I briefly went through it and sent her back some quick feedback. Great start, just need to tweak a few things. Jumped back to filling in information on the AI quick search prompts page. Pushed up new files. It is rough, but we got small descriptions on all AI quick search prompts.

Working with Bryan on AI prompts and keywords. Small Saturday work session. We reviewed our notes from yesterday. Made a few new notes and pushed them up to element of time # 12286 in the shop. We then did some pair programming, and I showed him what we were doing and what we were working on.

We started coding some things for employee/users and payroll. Good back and forth training and working session. Towards the end of the session. I committed my files and pushed them up to bit bucket. Bryan then pulled them down and started to work on things. We went through a few of them together and setup a time to meet on Monday. He is off to the races. We will touch base, but hopefully he can keep pushing things along.

Working with Bryan on AI keywords, options, and prompts. Bryan reached out to Suzi and we checked in with her. Lots of planning. We want Suzi to help do some step-by-step guides to help us show user scenarios inside of the adilas POS (point of sale system). We wanted her to do at least 10 scenarios from super easy to more complex.

Small data clean-up for Sean and a client out in California.

On a call with the Springbig folks. We will be redoing the Springbig integration. It has been a couple of years and either something on our side or their side has changed. They are going to resend us some testing credentials and access to the sandbox. Sean from adilas was on the meeting with us as well. We spoke with Maria from Springbig.

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

More copying and pasting keywords and prompts into the help files. Just trying to get a base to work from. Started working on a small JavaScript function to help copy text to the clipboard for a user.

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

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

Working on printable prompts... copying and pasting existing documentation into help files and such. Still needs some more work.

Training session with Russell. Working on CSS training. He was switching between him telling me what to do, then letting me make some decisions, to letting me try things all by myself. Making progress. Didn't seem quite as lost today as other days. That's good, I'll take it.

Meeting with Cory and Sean. Looking into some Springbig settings. Looking into their API connections and automated stuff from their end. We also fixed a small auto clean-up process that was erroring out. Pushed up new files.

Working on the AI keywords and prompts. Did some reverse prompts, made it so that you could specifically ask for certain prompts and the page would show the correct sub section of the page or documentation. We stayed in the hotel in Las Vegas, and I couldn't sleep, so I got up and started working on the reverse prompts.

If anybody wants to try it... Use the adilas quick search, click on any topic (say invoice, P.O., part, customers, deposits, etc.) then type the keyword "prompts". It will take you to a page that shows prompts for that section. It works pretty slick. If you can't spell "prompts", use "keywords" to get the same results. For example: invoice prompts or invoice keywords, you get the idea.

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

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

Working on documenting the AI options and AI prompts. Lots of work. Going through things prompt by prompt testing and documenting. Spent the whole day doing this. Six or seven different sessions throughout the day. Somewhat of a marathon day. I got quicker as the day went on. Ended up finishing up the first round (still needs some work), but at least usable. I had to skip some of the documentation. I'll get back to it later on. I pushed up files and did some live testing around 2 am on data 0.

Working on the AI options and AI prompts. I have been spending a bunch of time on this code and logic the last few days and weeks. I'm making great progress, and it is fun to see it shape up and turn out like we are wanting it to be. Started working on documentations and what that will look like. That's going to be a big project in and of itself.

Recording notes from the past couple of days - 9/17/25 to 9/18/25.

Spent all afternoon working on AI options and prompts. I'm making tons of progress. Most of it is hidden right now but I will try to document it here soon. I want to get it working and tight enough before I get people to really beat it up. Uploaded some of the changes.

Meeting with the Nxtlinq guys. They were showing me some progress. We gave them 7 new prompts last meeting. They were showing how they can already use all 7 of those in what the AI agent can do.

Went into Bridgerland technical college (B-Tech) for a software development committee meeting. Lots of discussion about AI and what students should and shouldn't use it for. This is a hot topic right now. Some great conversations. We then went through their presentation and had somewhat of an open share or open forum type meeting. They fed us and we gave them suggestions, feedback, ideas and such.

My hiking buddy, Brian Stewart was recommending that we (at adilas) sign up for a Square and Shopify account. Then go in and see how easy they are to use. Our stuff tends to be more complex and complete vs super simple. There is some real value in super simple. This is my take on it... We are trying to make it more technical so that we can simplify. That may seem like a random way to simplify (making it deeper or able to be split into miniature pieces, but that is where we are heading. The same is true for the adilas lite or fracture project.

Showing Shannon how we can almost take it to a super simple Google type level - with our AI quick search interface. As we were talking, it came out that sometimes we tend to fall back to what you know when things get crazy or stressful. Good insight. Working on content for the adilas lite project - codename fracture. Also, spent some time roughing in the content for the adilas lite - other business plans.

Seeing the vision through the clutter. Sometimes you have to make a mess in order to really get things cleaned up. We spent some time talking about the value of documentation. Just for fun, Shannon and I were talking about recording notes and ideas. We were making fun of "my post-it note garden..." :) I have them planted and growing around my office (not really, but it was kinda funny to call it a post-it note garden).

Emails. Then jumping back into the AI options and prompts for the AI quick search. Trying to document things as well. Working on a new solution to help add multiple line items to an open cart through an AI options or AI prompts. It took quite a bit to make that happen. Here is the new prompt instructions:

- multi add cart lines [array] - This will add multiple line items to the current cart. The array needs to be in this format: [part id space quantity, part id space quantity]. For example: Say you have two items with id's 5555 and 7777. Say you wanted 3 of one of them and 8 of the other. The actual prompt would look like this: "multi add cart lines [55555 3, 7777 8]". The square brackets are required for this prompt.

Just for fun... Here are a couple of other prompts that work on the testing corporation inside of adilas on data 0.

------------------------------

Working sample for corp 53 on data 0

part id - 255729 - baby ruth

part id - 255733 - caramel squares

part id - 255735 - fun dip

prompt to add 1 baby ruth, 10 caramel squares, and 3 fun dips

"multi add cart lines [255729 1, 255733 10, 255735 3]"

part id - 414640 - snickers with almonds

Here is one with 4 items, including the snickers bars

"multi add cart lines [255729 7, 255733 13, 255735 3, 414640 2]"

This next one assumes a quantity of 1 per item. No quantities are added to the prompt.

"multi add cart lines [255729, 255733, 255735, 414640]"

Here is a link to some other AI options and AI prompts - https://data0.adilas.biz/top_secret/help.cfm?id=535&pwd=ai

--------------------------------

Emails. Small data clean-up for Cory and a client who was doing some practicing before going live.

Working with Russell on some CSS training. We spent some time working with the box model and playing with content, padding, boarders, and margins. We then played with specificity and playing around styling with different elements. We then went into some OOP (object oriented programming) concepts and looked at some code and samples. It is important to think about everything as an object. That really helps.

Recording notes from yesterday and today.

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

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

On a quick Zoom meeting with Cory. We were looking into a 3rd party solution and trying to get it ready for one of our clients. We jumped into some code and did some light research. Cory took some screenshots and will send an email out to the 3rd party to see if they can help us with the integration.

Working with Shannon and Suzi. Started out with Shannon. We were reviewing some progress on the AI quick search. We did some testing and made a few small changes. Talking about the need for documentation. Suzi popped in and we went over some instructions and direction for a project she will be helping with. She is going to be making some screenshots and documentation on how to run simple POS (point of sale) functions inside of adilas. After Suzi left, Shannon and I went back to working on rough content for adilas lite - fracture plans.

Suzi jumped on with Shannon and I around 12:30 pm vs 11:30 am. I probably wrote it wrong in the email. We got it all figured out.

Working on new AI options and prompts for the AI quick search. Started working on new quick search main categories for AI, images, media/content, navigation, cart, and help.

Text messages, reaching out to a client, then typing up some directions for Suzi to help us build some scenarios and user stories for the AI agent to follow some directions and instructions. Other emails and trying to do some follow-ups. Lots of moving pieces.

Demo with Calvin Chipman to go over some AI technology that he is using and working on. We jumped on a zoom call. He is thinking about an exit strategy and trying to jump in on the AI race while it is hot. He is using an AI agent to go over dead or old leads and trying to reconnect with some of those people. We did a demo, and he will send me a video. He is using his Gmext product (group mass texting) to help send out those SMS messages (texts for a chat bot). Fun little fusion and combination and what he is doing, what he already has, and where it could go. I enjoyed the demo.

Emails and then a phone call with Josh talking about AI agent options. Looking for some scenarios and user stories to help with flow. POS or shopping cart stuff.

On a GoToMeeting session working with Bryan to help him get lined out on a custom data upload project for a lady who does candy vending machines.

Small fix for Cory. She sent me an email that was reporting some CSS being shown at the top of a page. It ended up being that one of our developers was not allowing output and was suppressing whitespace. It ended up not using some custom CSS that we had wrapped in cfoutput tags (Adobe ColdFusion stuff), in order to pull in special corp-wide settings, colors, and look-and-feel settings. pushed up new files to all servers.

Small updates for the SpringBig loyalty points. We have a future client (hopefully launching this next week - going live) that is currently using them to track their loyalty points. All of our other clients we have transferred over so that they are using adilas loyalty points. Anyways, it has been a minute or two since we had to do anything with SpringBig. Just circling back around to make sure that everything still works. Did some research, added some new code (copied from another page), and then sent a follow-up email over to Cory with some information and instructions.

Recording notes from 9/12/25 to 9/13/25.

Recording notes from earlier this week 9/9/25 to 9/11/25.

Went over to Brian Stewart's house to go over some AI consulting. I paid Brian to help us look into some options for how we could use AI inside of adilas. We met up and he had a small questionnaire that we went through. Lots of talking about this and that. He then showed me some of his proof of concepts (small mini projects that he has been working on).

Next, we switched gears, and I then had him go into the system and look around inside of the adilas system. This was his first time ever seeing it. Lots to take in. We ended up in a small demo site and had to configure a bunch of things. It wasn't setup very well. Anyways, we did a small demo and it kinda overwhelmed him. He was able to see where we could use some AI help and hopefully to help simplify the setup process and the training. All and all, a good session.

Small fix for Benning Construction. They only wanted certain checkout fields for the mulligan stuff (golf tournament - custom ecommerce checkout). Ended up doing the same thing for their donations to St. Jude Children's Hospital. Small checkout changes.

Working on the AI quick search and logic for the search action page. Added in a number of aliases and worked on -key:value pairs for the customer lookup functions. Making good progress.

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

A few different sessions throughout the evening working on changes for Benning Construction. They wanted a new item for their charity golf tournament (custom ecommerce site). They want to offer pay-for-mulligans for the tournament (pay for a do-over shots or second chances). They are going to let them, their participants, buy as many as they want... kinda funny. $25 per mulligan. It is for a charity golf tournament (just for fun). I added new item category, new images, new item, and turned things back on for the ecommerce website.

Meeting with Hamid. We did some catch-up and then jumped into CSS. We are going over some course files and small practice stuff from a Udemy course. We are somewhat co-working on the practice files. We will do things, talk about them, and then go in and play around a bit. We are then sharing what we are learning. That seems to help both of us get a lot out of the practice sessions.

Working more on the AI quick search. Created a new help file to list out options and AI prompt helpers.

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

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

- Project overview hub - Adilas ecosystem

- Ambitious roadmap for next generation SaaS map

- Clean, modular, teaser, further explanation

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

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

- Technical depth and community

- A vibrant hub for

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

- Grow into a dynamic dashboard overtime

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

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

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

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

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

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

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

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

- Vision - building a sustainable interconnected world around it

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

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

Working on AI options and prompts. Good long work session. Did all of the old quick search options and tied them into the new AI quick search. Trying to define all of the existing routes, what help files go with what, new simple text options, and paths. Lots of URL crafting and updating the AI quick search. Pushed up the file to do some live testing.

Got an email from Sean with some data that needed to be tweaked and altered for a client. Working through his list and doing some clean-up.

Working with Russell. Talking about video streaming options. We may need to look into some pay for streaming services, build our own media player, share links from google drive. Talking about plans and cost/benefits analysis. Russell is trying to get me some exposure so that I have seen certain things and know about some of the new coding options and practices. Exposure allows you to change when you are ready. We then switched over to training. Going options and making snippets inside of VS code. We worked on some CSS training.

Emails and a small fix for a client and their custom ecommerce site. They wanted to show a notice that online registration was closed for a charity golf tournament.

Meeting with the Nxtlinq guys. They were showing us a demo of what they are working on. More usage of the natural language and then converting that into options and prompts for the AI agent. Cool stuff. They had a couple of other questions, and we said that we would provide some user stories, scenarios, and requirements for the cart. Once that is done, we want to get a full sign-off on the cart functionality before rolling into the payroll functionality. After the meeting, I did some light clean-up of some of the records (customers and customer contacts) and sent them a small follow-up email.

Working on more AI options and prompts. I have a small list that I would like to add and make happen. See EOT # 12286 in the shop (private).

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

4)Add the DL scan field to the queue page as they are always scanning and winding up at the queue.

3)When you use the name/id search from mjhome_2 page, you can type in a first name or a last name and it will start predictive search, like it does when you are searching a customer from the shopping cart icon.

1) Add a box for digital signature on the invoice

2) Add a setting so that when you search a customer by these page settings: https://data4.adilas.biz/top_secret/secure/mini_scan_cart_customer_search_action.cfm?bName=Blythe

or these page settings:

https://data4.adilas.biz/top_secret/secure/customer_search_action.cfm 

the inactive customers don't show up

Work session with Shannon. Going over some plans and what is going on in the adilas world. We then jumped in and finished up the last three sections on the adilas marketplace.

------ start - ai options and prompts -----

done - build a function to pull out sub filters - pass in the whole string and what we are looking for. return the trimmed value.

- make a new help file with everything all listed out... help ai know what to do.

- url help... search_action.cfm?aiSearch=[prompt]

- mini api help - web/adilas_mini_api_calls.cfm?useCorpKeyId=[]&mode=[]&aiQuickSearch=[]

- samples - expand as needed

- calls and actions to the url's - double thread, simple response, stupid simple - maybe out in web or public, predictive level, show subs, mini async calls, predictive material to work with, show all categoies, show all items under that category, same with customers

- cart stuff...

- items by vendor [] ai quick search and mini api

- items by category [] ai quick search and mini api

- my cart favorites - expand when ready

- edit cart line [], adv edit cart line [] - when looking up, remember line sorting and lines with 0 qty (skip)

- invoice mini [555], invoice mini last, invoice mini max

- invoice max

- invoice edit main []

- invoice edit lines []

- customer log []

- credit card checkout (checkout credit), cc checkout, external cc checkout, maybe spell it out as well

- on account or payment on account

- loyalty points

- gift cards

- cart groupings (sorting things)

- cart stuff - remove line [], change qty [], cash with change due, adv checkout, start cart for 5555

- classic cart settings, mini scan cart settings, view classic cart, view kush cart, view mini scan cart, deliver options, split cart, bulk edit line items, save cart, save quote, save as new quote, refresh cart, choose subs, add sub inventory with a quantity, auto open next sub package, cart as a whole discount, show discounts, other special cart functions... look them up and add items

- help all, help [], help -title:[], help -main:[]

- back, back [], forward, forward []

- bank home, bank running, bank reconcile, bank bulk verify

- developers notebook [] - expand when ready

- my home or just home

- gps core

- interactive map

- items by vendor [] - ai quick search and mini api

- items by category [] - ai quick search and mini api

- mini calendar

- ecommerce settings

- email settings

- media content [] - - expand when ready

- news and updates

- my settings, my profile, my password, change password

- homepages [] - expand when ready - this could be a big section

- a/r's, a/p's, payroll, fulfillment, settings, cultivation, production, back orders, special accounts, adv exports, reoccurring invoices, go through permissions and pages - expand

- chooser

- corp admin, corp wide settings, admin corp wide settings, corp look and feel, corp stats

- history home, history [date]

- switch corp, switch corp [corp name]

- my favorites

- p&l, p and l, profit and loss, income statement, adv income statement

- page level actions... submit, select, select option, tab, shift-tab

- public shortcuts (corp id 7 simple prompt) - not sure what this means... it was part of my notes. maybe think on this a bit.

- bulk tools - expand as needed - define as needed

- labels - expand

- existing normal quick search options - see search action or help file

- edit main, edit lines, verify, history, add photos, add media content, add payment, edit payment, printable, etc... normal actions per section

- duplicate time, working with time, add sub, add flex grid, add limited flex grid

- for me - if they are already on an existing main player... maybe remember the type and the id... then the other edit main, edit line items, history, etc. will play through better. help it remember where it is or what it is dealing with...

- for me - change the options and prompts to an accordion style page - printable list - translate or interpret language - also make a new help file that is public facing

- take time to record what is possible... help train users and ai agents - think the value of education

- add links to the ai quick search from the main headers and chooser page

- last [count] - for example: customer last 10 or invoice last 25 or po last 5

- stats - use this to get basic stats for a section - for example: customer stats, invoice stats, po stats, item stats - maybe even some keywords... today, yesterday, this week, last week, two weeks ago, tomorrow, next week, this quarter, this year, last year, etc. maybe allow for day, month, year, range.

- special reports - daily weekly, closeout, knox report, grouped, etc. think of special options and reports that are used all of the time.

- logout

- images and media searches - general, specific main player groups (customer images, item images, expense images, etc.) - maybe some small filters like -from_date:[], -to_date:[], -caption:[], -user:[], etc. media could be similar...

- organize all of the ai quick search pieces according to the main business functions. that will help show what we can do. don't get stuck on the number 12. it could be whatever... - link to the presentation gallery - business functions

- show [], show prompts, show homepages, show pos options, show crm options, show payroll options, etc.

- what about creating some more quick search permissions... things like help, ai, images, media/content, navigation (nav), etc. That would be cool and would create some great crossover between the older quick search and the newer quick text options and prompts.

------ end - ai options and prompts -----

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

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

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

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

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

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

- We are honestly trying, but it gets tough.

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

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

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

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

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

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

Paying bills and recording expenses. Recording notes from last week and today - 9/3/25 to 9/6/25.

On with Bryan looking at code. He was trying to fix an online bill pay page for paying for invoices after the fact - making payments on account. We ran a test payment and it worked. We then pushed up the code live and did a live payment and it worked. He then sent out an email to the client to have them try it.

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

Multiple sessions throughout the day. Building more AI options and prompts for the cart, the AI quick search, and basic adilas navigation. Spent some time planning. Then building a new AI search helper function to sub divide the simple options and AI prompts. Lots of time playing with AI and learning some RegEx (regular expressions) stuff. Couldn't quite get it to work. Went through different versions. Finally switched over to a simple RegEx find and then pulling out what I needed. The new function can easily find any valid next key/value pair within a simple search/option/prompt string. I'm excited about that. This should really help speed things up, development wise.

Multiple sessions throughout the day. Emails and looking over documents. Going over new samples provided by the Nxtlinq guys. They provided a zip file and I was browsing and looking at the info on the page. I sent a couple of pages off to Wayne to look at, to get a second set of eyes on the new code samples.

Working on the Nxtlinq integration project. Working on some samples. Did some live testing, off the side, so that no one would be bothered. Worked a little bit with ChatGPT to get some code all lined out. That was kinda fun. We built it out and tested it locally and then pushed up some code live on data 0 for testing. I then sent some emails around to let a few people know. Finally, I sent off an email to the guys at Nxtlinq with a few small questions.

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

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

Working on getting the AI agent into the headers and footers of all adilas pages. Did some planning and some AI research as well. Small work session. The Nxtlinq guys sent us some samples. I was looking through things and pulling them apart. I only want to add just what I have to. Nothing extra. Making progress.

Phone call with Bryan to help him get his local system all up to date and caught up with the master code branch. We had to trouble shoot his Git and Bit Bucket stuff.

Working with Shannon. Light overview of what is going on and new changes that are playing through. Things are always changing. We got into some plans, changes, and some vision for the future. That was fun. We also talked about how to teach an AI agent and how to help it know how to play with our stuff (do work inside the system). That turned into a small discussion on machine learning. We went over some security things and what we are doing to help secure things. You have to think of all kinds of options.

We then switched over and worked more on the content for the adilas marketplace plan. We are making good progress there.

Emails and tech support.

Working on the adilas mini API. Added security for the part lookups. Adding in options to help with the customer lookup options. We also added in options for searching customer business names, first names, last names, customer phone numbers, and customer email addresses. Light testing and playing around with different search options.

Recording notes from 8/27/25 to 9/2/25.

Meeting with Greg Weess from Calder. Talking about options for selling part of the adilas business to raise some capital and other possible options. We are just looking into what options we may have. We don't really want to sell, but we really do want some sort of angel type investor who sees the vision of what we can do and where we can get to. Lots of talks and options.

If wanted, here are some adilas investment options that we see as options.

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

Working on the adilas mini API and what it can do. Added some security options to help keep it safe.

On a meeting with the guys from Nxtlinq. Going over progress and doing a little bit of show and tell to help each team see the progress. They are making improvements on the user interface and being able to keep the AI agent screen on top. They also showed us a possible version where the AI agent interfaces and works with a SPA (single page application) type interface. That looked a lot nicer but would require us to rewrite quite a bit of code.

Mobile first design. Working with Russell on some training. I don't need to know everything... I just need to know how to figure it out...

Russell wants me to keep doing the training, using AI, and then experimenting with what I'm learning. Exposure is really important and seeing things and how they work. We spent some time working on some practice files. Inside of our practice file, we have a touch image slider, navigation buttons to do next and previous images, and we can click on individual dot indicators to jump right to a specific image. Playing with JavaScript and CSS and mobile first design stuff. Started working on the other page content.

Working with Shannon - new content for the adilas marketplace plan. Most of the session was listing out professional services.

Recording notes from last week. It was a busy week, and I didn't them all fully recorded.

Emails and tech support. I then had to help a client with a custom ecommerce checkout process. They wanted it a little bit tighter, so we added some code and a redirect if other things were needed. Sent them an email with instructions to the client. We also got an email from the same company with some other updates. They found another small bug and we went in and fixed it. I'm so grateful for users who push on things and then let us know if things need some help. Good stuff.

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

Working on a mini version of the API for the adilas API sockets. This is a super quick, human readable, API call that has minimal fluff. Building and testing things as we are building. Here are some samples:

for the web/adilas_mini_api_calls.cfm page...

URL.useCorpKeyId or FORM.corp_key_id - pass in the corp key id value - Example: USE-0053 or Adi-22

URL.aiQuickSearch or FORM.ai_quick_search_field - search string or option/prompt value

URL.mode or FORM.mode - default is blank, if blank, it will show JSON. If it has a value like mode=show, it will show a CF dump (visual) of the object.

valid aiQuickSearch values...
customer types [filter]
customer lookup [filter]
item categories [filter]
item lookup [filter]

Sample URL for the AI quick search look-up page (in the public web folder)

https://data0.adilas.biz/web/adilas_mini_api_calls.cfm?useCorpKeyId=USE-0053&mode=show&aiQuickSearch=customer%20types

https://data0.adilas.biz/web/adilas_mini_api_calls.cfm?useCorpKeyId=USE-0053&mode=show&aiQuickSearch=customer%20types%20VIP

https://data0.adilas.biz/web/adilas_mini_api_calls.cfm?useCorpKeyId=USE-0053&mode=show&aiQuickSearch=customer%20lookup

https://data0.adilas.biz/web/adilas_mini_api_calls.cfm?useCorpKeyId=USE-0053&mode=show&aiQuickSearch=customer%20lookup%20Sponge

https://data0.adilas.biz/web/adilas_mini_api_calls.cfm?useCorpKeyId=USE-0053&mode=show&aiQuickSearch=item%20categories

https://data0.adilas.biz/web/adilas_mini_api_calls.cfm?useCorpKeyId=USE-0053&mode=show&aiQuickSearch=item%20categories%20Candy

https://data0.adilas.biz/web/adilas_mini_api_calls.cfm?useCorpKeyId=USE-0053&mode=show&aiQuickSearch=item%20lookup

https://data0.adilas.biz/web/adilas_mini_api_calls.cfm?useCorpKeyId=USE-0053&mode=show&aiQuickSearch=item%20lookup%20bit

Internal tech support. Had to look-up some settings on a main API connection for a client. They had not turned on a master switch "show on the web" to yes. It was still marked as no and was denying access to the API. After that, I had to do some backend changes for Sean and Cory and a deployment that they are working on. We had to flip some vendors on PO's and items globally in the system. This took some time and we had to look up vendors and sub vendors under the different PO's.

Working with Shannon. Talking about the translation layer and how the AI bot will interpret and then translate to the correct prompt. Started working on content for the adilas marketplace. Trying to show how the adilas application creates needs and wants that can be supported and serviced by other outside professional and businesses. We call it byproducts, but basically, as people use the system, they will have wants and needs. It becomes a full system once things get intermixing together.

Here is an analogy that we did for a ski resort and comparing it to adilas.

To illustrate how byproducts fit into the adilas business model, think of a ski resort. The main goal is to get people up and down the ski hill. However, people coming for skiing may also need things like rentals, lodging, a ski school, food services, ski patrol, retail shops, etc. You get the idea. The ski resort doesn't have to own or run all of those other entities. However, the main service offered by the ski resort creates a host of other opportunities and services that can readily be paired with the original product. Inside of adilas, we play the role of the ski resort and facilitate opportunities for other entities to provide the additional services.

Cory and Sean requested that we add the delivery stuff for the mini scan cart. Took some time and did some research, coding things, light testing, and pushing code up to data 0 for some testing. Let Cory and Sean know to go do some testing.

Emails. Got some good information from Wayne on video live streaming. See attached.

Working on gathering information for a letter of recommendation for Cody. He did a great job and worked for us for about 6 months. The only reason that we had to stop working together was because of budgets (tight). We would love to have him back if possible. Just for fun, here are almost 80 entries in the developer's notebook where I was working with Cody. Lots of good stuff. Click here for the link.

Working on some to do list items. Planning, brainstorming, paying bills, emails, and API stuff for cory (internal research and gathering data). Reviewing video streaming stuff from Wayne. He was doing some research on how to do that. He ended up converting a bigger MP4 video into an HLS version or format (a bunch of smaller clips that are played together in a play list type fashion). Anyways, I watched a few videos and looked around a bit. Interesting conversion process. We'll see where we go with that.

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

On a Microsoft teams meeting with the folks from China. We went over the AI quick search and did a number of walk-through demos. They had a couple of questions but seemed fairly happy with the progress. They are planning on playing with it and even trying some language translations on the AI agent (bot). That would be super cool.

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

Talking with Russell about AI models and back and forth. Talking about security and validation routines. Talking about scraping pages and pulling stats, even if the client doesn't know. Going over AI options vs AI prompts - creating an AI consultant for adilas. Baby steps - take one thing at a time. Talks about API sockets, endpoints, URL crafting, and mixed solutions. We spent some time talking about human interfaces... speaking, writing things down, OCR scanning and reading (ocr - optical character recognition), AI chat/prompt bots, etc. Russell is curious about the implementation and what we end up doing,

Russell and I were talking about mixing API sockets and session values. Good options.

Switched over to the CSS training. Working on the JavaScript for changing images and creating an image slider.

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

Working with Shannon... showing her some of the new stuff. We went over options for using cookies and URL's... potential for letting AI agents use adilas. Talking about AI agents and how that could really help with education and training. We also spent some time talking about inspiration and how we each get help in different ways. Shannon and I dipped into this subject for a good little while. That's how we get our answers and direction. Switched over to working on content for the adilas university page and plan.

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

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

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

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

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

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

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

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

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

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

- Let the user talk to the system

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

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

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

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

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

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

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

Recording notes from end of last week.

Phone calls with Bryan. He is working on a couple different projects. One is dealing with CSV to PO (bringing in new inventory) and they got some duplicates. The other questions he wanted to ask were dealing with the Plaid API (external banking stuff) and recording external reference numbers from bank transactions and id's from outside software systems.

We then jumped on a meeting with both Bryan Dayton from adilas and Brian Mowris from Finetech. We were debugging and checking out an error with Card Pointe. For some reason, one of our merchants (clients) was get an authorization error. We checked the credentials and were able to make a manual transaction happen but could get it to connect to any hardware terminals. We will pull in Alan (other adilas developer) next week, as he was out of the office with his family.

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

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

Meeting with Hamid. We went over some of the things that I am learning with Russell and on the Udemy CSS course. We then did a small practice file and did it together. That was fun. It also gave me a chance to use what I know, in a teaching environment. I enjoyed that. That helps it (the learning) stick better.

Training on CSS. Working with selectors and combinators (CSS theory). Going through videos and practice files - course in on Udemy.

Emails and recording notes. Light research on a funding company and responding to some email enquiries.

Internal emails and small research and review for both Sean and Cory on different subjects. Sent an email to Wayne to follow up on being able to stream videos from the adilas content server. Sent some links to Sean that either migrate and/or copy customers, parts, part categories, vendors, or chart of accounts from corp to corp. He has a client that had an old system and wanted to setup a new system and use some of the older values. These are files that help copy between corporations on the same server.

Working on content with Shannon for the adilas university project. We were talking about resource coordination, and I was telling her some of my dreams and visions. Here are some small notes:

- We want other people to come in and help with the training - adilas marketplace and adilas university

- These new parties (adilas marketplace) will have or help provide active and living training pieces

- Not a specific idea or plan, very open right now

- Adilas will do some training

- We will also open it up and let other people do their own training

- Resource coordination, putting together whatever combination that is needed

- Training is a resource

Meeting with Russell and doing some CSS training. Working on setting up a small card (page element) with images, buttons, and icons. Lots of CSS and dynamic placement of items and content. Practicing CSS by building a mobile friendly card or app for a recipe app.

Recording notes. Doing some research on our current mini scan cart and ways to help it out. I have a big list on my local computer of things that we either wanted to do and/or are prepped or ready. Small wish list or feature list of sorts. Reading over those to do list entries. Back working on the code review for Bryan and his invoice and quote flex attributes project. Going in and setting up a number of defaults, even if not being used. Trying to prep certain pages for future usage with quote and invoice flex attributes.

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

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

Working with Shannon on content for the adilas university plan. We went through and read through some sections dealing with a video libraries, tracking education and progress, SOP's (standard operating procedures), internal & external needs, and online & in-person training events. Slowly working on new content and plans.

Checking out some code for Bryan. He has a branch that needs to be merged in. It has 40+ pages that have been changed. Checking things out. This is for new flex attributes for invoices and quotes. Small merge conflict fix and then running code locally on my machine for testing. Going through pages and making small tweaks.

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

Emails and recording notes. Had to call tech support for PB&T bank. Couldn't get into the online account. Checking out a code branch for Bryan. He wants me to work on it and merge it into master. It has a small conflict, looking at code to find the conflict.

Checking email and recording notes.

Email to Wayne about streaming videos. We would love to be able to do that easier from the adilas content server. Then a semi-lengthy email to Chuck and others about the shopping cart and updates to my cart favorites. Phone call with Bryan to go over a page that does an upload from a CSV file and allows for dynamic mappings to be used. He would like to help some clients with possible EDI (electronic data interchange or transfer) type stuff for buying and receiving inventory.

Here are the two videos that I sent to Chuck about the shopping cart.

https://www.adilascontent.biz/videos/internal_shopping_cart_r1.mp4 - small future cart demo

https://www.adilascontent.biz/videos/cart_touch_and_discount_options.mp4 - current cart demo with my cart favorites