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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

- API integrations with delivery systems

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

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

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

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

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

//////////

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

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

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

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

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

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

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

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

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

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

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

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

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

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