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 cats, 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 stuff - get an update.

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

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

Working with Bryan. Code sign-off. Small close frameset button on the classic split cart. Then looking at some eBay code (API stuff). Light fixes and pushing up some code. We had to fix some merge conflicts.

Quick phone call with Hamid. He jumped on the GoToMeeting session, but Bryan and I were still on the meeting. I gave him a call, and he said that he is working on the play at the wall website for adilas API socket stuff. He said that he is working with ChatGPT to get some ideas and how to make it both fun and informative (small pun off of "play" at the wall).

Working with Bryan. Small code fixes. We had to param some values to help with the new code that we pushed up yesterday.

Working with Bryan on some code review. Going over some of his new code to allow charging a credit card fee on the online bill pay section for ecommerce. It's a new setting that allows or disallows the credit card fee. Fixed a few merge conflicts and pushed up the new code. He wanted it live on data 0 for some testing. After we did some testing, Bryan was just checking in on me, mentally and physically. It's been kinda crazy.

Meeting with Bryan. He had a code conflict that needed to be fixed. We got in there and I helped him get some of his merchant account settings changed around. We then went through some code. He has a small bug that he will go back and work on. We were then talking about the future and where we are heading and going. I was trying to show him some of the vision of what we are learning and how things get tied together. I bounced to a number of pages and was doing some drawing. Fun little session.

I have so many things, all over the place. I am really trying to gather things together and organize them into a cohesive suite of tools, features, advantages, and benefits. Good stuff. Keep chipping away.

Bryan was mentioning grad school and how sometimes people will dedicate years to a single subject to try to bring it all together. In a way, I'm kinda doing that but without going to school. A giant gathering and refining process. I'm learning tons along the way.

Working with Bryan. He was showing me some of the work with Google Gemini as an AI agent. He is playing with a small chat option to help to use Gemini within the adilas website (certain tasks or to help with repetitive work). Bryan was talking about having a small team spending some partial time on some of these projects (a few hours a week). That would help us make progress and eventually getting things done on the trickle affect (drop by drop or drip by drip). Talking about the sales engine and pushing on projects that will allow other people to help sell adilas. Showed Bryan some of my AI chat messages.

Web link - time_web_gallery.cfm?corp=748&id=12760

Adilas Key Contributors:

Steve Berkenkotter - Main owner and business partner - original ideas, concepts, and training - sales, relationships, dreamer, visionary, custom code, coordinator, builder of the first industry specific skin, and the list goes on. Huge player in the adilas story and timeline. One of the original owners in Moring Star Automotive - where the system came from. There are three known Steve's in the system notes. Most of them are this Steve (99 out of 100 times). He won't admit it, but adilas was his brainchild.

David Berkenkotter - Steve's brother and business partner in Morning Star Automotive. David was a system user and helped us create the adilas quick search. He liked using that feature, the quick search, but it only existed on one page originally. He wanted us to put it on every page. That ended up being in the header. He was also one of the original partners in adilas. Power user in the system. Sadly, he passed away due to cancer.

Shari Olin - Commonly known as "Shari O.". She worked in the accounting department back in the Morning Star days. She has been somewhat of a mother hen to help all of us crazy chickens keep going. She helps with customer support, training, payroll, bill collection, and tons of backend office functions. Major power user. Just being silly, but she can have the mouth of a sailor but the heart of an angel. Part of the adilas admin team and a great friend.

Craig Leitner - Also part of the original Morning Star team. Craig was the automotive floorplan and bank guy. He is a power user in the system and does a lot of bank reconciliation and other tasks. He currently works with Steve and asks as the adilas controller (money flow guy).

Cory Warden - Originally an adilas rep and consultant. Cory become part of the team after being a rep for quite some time. She helps with customer care, client support, project management, and keeping the team on track. She also does all of the news and updates and other training material. Cory does tons of oversight type services for our clients. Power user and part of the admin team.

Sean Carlton - Sean was a manager at a Cannabis dispensary in Colorado that used adilas for years and years until they sold. Steve recruited Sean to help with sales, deployment, and training. Sean brings lots of usage experience. Often, he is one of the helpers if we need to send someone onsite to help with a deployment or training session. Power user.

Brandon Moore - I'm one of the guys that writes most of the developer's notebook entries. Originally, I was hired by Morning Star, the automotive dealership, to help with data entry, accounting, and website stuff. I ended up being one of the main adilas developers and architects. I build content, write code, help other developers and team members, and help with training. Helped start the project back in 2001 under the Morning Star name.

Chris Dunsey - One of the first adilas interns (developers). Helped with a number of projects. Ended up being somewhat of a consultant later on.

Shawn Curtis - Kinda a funny story. He was taking a developer's class at Bridgerland. He knew my brother Russell. He asked to join our developer class and became one of the first interns along with Chris Dunsey. Shawn ended up helping with payroll and other projects. Some of the photo galleries in the system came from Shawn's help. He also worked on the media/content (file upload) pieces. Later on, he did more payroll work and acted as a buddy to Brandon and did some consulting work. We worked together for years and years.

Russell Moore - Russell is my younger brother. Originally, he was added to the group because of his graphic skills. He ended up being a great backend developer and project manager. He has also acted as a trainer and mentor for Brandon along the way. Much of the current system came from projects and efforts that Russell was involved with. He has also been Brandon's AI tutor in recent years. Great help to the system. Huge contribution.

Chris Johnnie - He is an entrepreneur who teamed up with Russell to help create a company called "Adilas For Business" or "AFB". Eventually, both Russell and Chris sold their pieces back to adilas. They were honestly the first ones to really try to run as a white label of adilas. This was back in 2015 and 2016. Chris really helped to push the product to the next level along with Russell's help.

Danny Shuford - Longtime friend of Steve's. Danny helped with some website design, sales, and videos for adilas. He even got into creating custom PDF labels for clients. Light development work.

Marisa Shaw - She is Danny's daughter. Danny brought her to an adilas training event in Denver, CO. Marisa was the star student. She ended up helping with some graphics, flyers, marketing material, teaching, instruction, and planning. Power user. Very helpful.

Shannon Scoffield - Shannon is Brandon and Russell's sister. Her maiden name is Shannon Moore. Huge help and virtual assistant to Brandon. She has helped with training, project management, and content creation. Most of the major content sessions were or have been with Brandon and Shannon working together. When they, Brandon and Shannon, were traveling, Shannon was one of the primary adilas instructors. If she was teaching Brandon was taking notes. If Brandon was teaching, Shannon was taking notes. Power user.

Cheryl Moore - Cheryl is my mom. What an asset. She owns a small business and has owed a few different ones. When we were doing training sessions, she came to every one of them. She asked wonderful questions and was a great supporter. Sometime, I would use her as a test subject - can my mom do this? If yes, we are good. If not, we may need to keep tweaking it. Thanks mom!

Wayne Moore - Wayne is my dad. He was my hiking buddy and more than willing to talk about ideas and concepts on our walks and hikes. He helped out with video stuff and was a great coordinator for making other connections. He worked at Bridgerland (technical college) and helped us get setup with classrooms, computer labs, and other great connections. Huge cheerleader! There is another Wayne, Wayne Andersen, he is a backend developer, systems guy, and database guy.

Wayne Andersen - This Wayne lives in Portugal and helps with all of the backend security, server, and code testing. Major skills, writes code, helps push all of us to new technologies, partially retired but loves to play with tech stuff. If you search for Wayne and it deals with concepts and coordination stuff, that's my dad, Wayne Moore. If you search for Wayne and it sounds like a master backend guy, that's Wayne Andersen.

Alan Williams - One of the lead developer's at adilas.biz. Alan joined us in 2015 and quickly came up through the ranks. Trainer, CTO, team lead, master developer, prototyper, and system architect. Alan has helped with many projects and features over the years. He also helped Brandon with some of the prep work for the adilas lite (fracture) plans and project. Sometimes called "Dr. Alan" by the other developers. Example: This might be a project for Dr. Alan.

Bryan Dayton - Bryan has been one of the most versatile guys on our team. Originally, he joined a development class out of curiosity. He and Brandon live in the same town and know each other from church. Bryan has done more custom code or small system projects than almost any other developer. He also joined the team in 2015. He helps with sales, custom projects, pushing on projects that he thinks will yield a return. Lots of work on the adilas lite and fracture project. Very hard working and versatile.

Dustin Siegel - Developer who helped with numerous cannabis and cultivation type projects. He worked directly under Steve to help with that business vertical. Many of the original pages that Steve built were taken over and remade by Dustin.

Eric Tauer - Developer and custom code guy. Originally, Eric knew Steve and lived in Salida, CO. As a note, adilas is Salida spelled backwards. Eric has a background in database work and data warehousing. Eric has done tons of custom systems for clients. Often, Eric would pioneer certain features or logic, as custom code, and then we would bring those features into the main adilas application.

Garrett Kirschbaum - Adilas intern and then full developer back in 2015. Stressful time of building and expansion. He and others helped run the adilas shop with Brandon's help. Garrett was a great developer and helped us standardize a number of tools and features. He was the first developer to work on sub inventory, back in the day. He also did other projects and helped with some developer management stuff.

Charles or "Chuck" Swann - Charles was an instructor at Bridgerland for web development. He builds custom websites, does amazing mock-ups, prototypes, and is a CSS master (styling a website using code). Chuck worked with Russell to help with redesign work, projects, and vision. Chuck worked fulltime for a number of years and now works and coordinates work done by a small hand-picked design and development team. Anything that needs some design loving gets passed over the Chuck and his small team.

Steve McNew - Friend of Steve Berkenkotter's. This Steve helped prep some whitepaper documents to help with getting adilas standardized and some internal audit type stuff. Mostly white papers and putting things down on paper. He ended up getting hired by the local school district and wasn't able to finish the process, but he got it started. He asked some great questions, and we had some good conversations.

Abby Elkins - Abby is Brandon's daughter. Her maiden name was Abby Moore. Abby, when she was little (10-12 years old) helped with some of the original concept artwork for adilas. Later on, she helped with content for the presentation gallery and then the adilas lite plans (fracture). Currently, she is working graphic artwork for different adilas pages. She's now in her mid 20's and has some awesome art and content skills.

Aspen Moore - Aspen is Abby's younger sister and Brandon's daughter. Aspen helped Brandon with some planning and counseling (mental help). Aspen also did some general business consulting with her dad Brandon.

John Maestas - Developer, backend server guys, and designer. John came to us through Dustin. John was uses as a jack of all trades on the backend and frontend. He did numerous projects, documentation, payroll, and page redesign projects. John was also very help to Brandon in working on the notes and comments on the SWOT analysis document. Many other projects as well. Good vision of the future.

Kiva Berkenkotter - Steve's wife. She helped Steve with various projects and planning sessions. At one point, she was in charge of paying commissions and collecting monthly reoccurring payments. Huge supporter to Steve!

Heather Moore - Heather is Brandon's wife. What a trooper. Cheerleader, support, ideas, and consulting. Huge asset to Brandon (me). Thanks Heather!

Jonathan Wells - Designer and mock-up guy. He helped to map out the system and created a number of deep mock-ups for adilas lite (fracture) projects. Great job catching the vision and putting those pieces into a visual representation. We still refer to his work when talking about fracture (future project for adilas).

Jonathan Johnson - Business consultant from Epic Enterprises. Met with Brandon and Steve in end of 2019 into 2020. Really helped us see some needs and opportunities. Later, helped Brandon with some other consulting when trying to define the fracture plan.

Calvin Chipman - Windows software developer. Calvin also did a bunch of web-based work, database stuff, label printing, and API socket stuff. Calvin was the first developer to use the adilas API's to create a native mobile app for a client. He also built a number of special developer tools used by some of our team to speed things up. He's the tool guy!

Cody Apedaile - Bryan Dayton's cousin, Cody helped with a bunch of JavaScript code and changes. He also spent some time working on the UML diagram for the adilas database. We didn't get things finished, but he was working on a new build your own interface (custom to you) for adilas. We ran out of funding. We want to get back to that project at some point.

Dave Forbis - Dave was the official "high tech gofer". He did a bunch of things. Graphics, project management, brainstorming, planning, sales, and helped with managing developers for the adilas shop. He was another great student. He came to a number of training courses and brought so much to the courses. He was also a big support to Brandon during some rough times.

Josh - There are three Josh's. Josh Wheeler, Brandon's friend and developer. Josh Sagert, developer and adilas user (worked tons on the discount engine), and Josh White, Steve's friend from California. Josh White has brought us a number of bigger leads and bigger players, like franchises, and other higher-end clients. Anything recent is Josh White, from California. He helps with networking, sales, and dreaming of new things.

Suzi Distelberg - Sales, training, and deployment. She also worked with some custom projects and doing step-by-step user guides. She has helped with all kinds of projects and even gone onsite for setups and training. Great asset!

Kelly Whyman - Kelly is Dustin's wife. Kelly was single handedly the best independent sales rep that adilas had. She did training, consulting, and sponsored a number of custom projects. Kelly helped Steve and Brandon with reports, functionality, and other things. She got so good at things, state contracts snagged her up to work at state and multi-state level stuff.

Molly Hennessy - Molly was another independent sales rep and consultant. She had numerous clients and got into doing SOP's (standard operating procedures) and other high-end documentation and training. Molly was an entrepreneur and even started creating some of her own product and services. If you search adilas on google, some of the other results are from Molly. Super creative and a great consultant.

Hamid Karbasi - Developer - He has worked with Brandon doing small websites, training, and small tasks. He currently is a manager at a retail store and brings some managerial type skills to the table. Willing to talk about concepts and how they apply to retail and other environments. He is also lightly helping with some planning for fracture.

Gene Spaulding - Friend, entrepreneur, and businessman. Gene is an old college friend. We had a number of friends in common. He has been a small mentor to me over the years. Way back, before adilas, he helped me get my first business loan for a project that I was working on.

Sharik Peck - Friend, entrepreneur, public speaker, physical therapist, and businessman. Good influence and mentor in ways. Sharik and I used to exercise together back in the day. Many of fun walk, run, and weightlifting session. Learning some conference and training skills from him and his wife. They have done really well pushing their product lines and doing some marketing. Trying to get some ideas.

Bridgerland Technical College - Use to be Bridgerland Applied Technology College. Not a person, but a huge help. This is a local technical college in the Logan, UT, area. Brandon's dad, Wayne, worked there. Tons of assets. They provided classrooms, training options, computers, and even an small incubation spot (starter office space) for the adilas shop during the startup phase. Huge asset!

McCorvey's Pro Shop - Also known as Bowling World. Client that had multiple locations. The started out with around 30 and grew up to the 90+ location level, all using adilas. Long time client.

Emerald Fields - They were the first client that wanted their own fully dedicated box and server. They had multiple locations and requested some custom code, reports, and features.

Beaver Mountain Ski School - Client that we helped them track their ski school (snow sport) lessons. Students, instructors, classes, and schedules. Custom interface dealing with elements of time and flex grid.

Bear 100 - This was the first event or annual event client that we did. They used the system for about a week each year. They had 350+ runners and their families that would be on the site for multiple days straight. It was a 100 mile running race with 13 aid stations and a small social portal for the family and friends to watch their runners. This one was special as it had custom input options to upload CSV files to populate the database vs normal HTML form field entries. Records were sent in batches from remote places to adilas for storage and race progress.

High Valley Bike Shuttle - Online ecommerce and scheduling client. They also have a cafe and small retail store. Fun online scheduling and bulk flex grid projects.

Herbo - Mike Roundtree, owner of Herbo, was the first company to do a small white label of adilas. Mike has been a great asset to Steve and the two of them have worked on projects, plans, and dreams. Herbo also has a custom payment solution that they are trying to market and get rolling. Mike has been a great supporter for years. He is also a certified CPA and that credential helps us and him. We would like to get other CPA's on board as well. Thanks Mike!

Nxtlinq AI - AI assistant. These guys really pushed us to get an AI agent inside of adilas. Tons of development took place and lots of prep stuff. We wanted to do a 3-part plan for integrating AI. 1. Teach it how to navigate using the AI quick search (check - done), 2. Teach it all things adilas. and 3. Teach it how to be clear up at the consultant type level. We only got the first phase done. Lots of other plans and such, but we ran out of funding.

Grok AI - Steve loves using Grok. He has built a number of image generation options inside of adilas. He is also working with Grok to feed it data to help with analytics and AI insight. This is not finished yet, but we may end up using Grok as an AI assistant inside of adilas. We have simple and emerging connections available right now but need to really polish things up before going live with the AI assistant options.

ChatGPT AI - We have started using ChatGPT to help with code, explanations, explore resources, planning, and help with training and flow for people and other AI bots. Currently, Brandon, Steve, Bryan, Alan, Josh, Russell, Chuck, and Wayne are using AI in either ChatGPT chat sessions or some other form of AI. We have some using Copilot, Gemini, Claude, etc. AI is actually helping in many ways. ChatGPT is a big one for use. Anyways, they are earning their place in the adilas key contributors list.

There are so many more that I can't list. Developers, users, power users, reps, consultants, trainers, clients, accountants, friends, family, and even critics. They have all helped out the idea farming process and progression. Good stuff! We couldn't have done this alone. It takes a community to do what we are doing.

Various emails, text messages, and phone calls. Touching base with some of the team members. Physically on the phone with Shari O, Bryan, and Alan. Texting others.

Working with Bryan. He had some questions and such. He is working with some accountants on some things. He would like to create a QuickBooks alternative for users and accountants. Help them easily switch over to adilas. He had some plans mocked up and is lightly working on some ideas and options.

We then looked at some other questions that he had. Towards the end, we talked about other full-service options to help people do all of the backend stuff, using our system and helping them run and do what they do. Imagine something like they have an adilas account, but they use some other mini app (scaled down) and it helps them push data into adilas without using the main adilas user interface. Adilas would then just become the storage engine, in a way. It still exists, but it would be used and consumed differently. Skipping the main user interface (UI) and helping with custom data input and then providing custom output reports. So many options. I told Bryan to keep catching the ideas, even if we can't fully build them out right now. We need to keep catching the ideas and plans.

Working with Bryan. Working on web payments page. This is for invoice payments after the fact, the invoice already exists and they are just making a payment. Pretty elusive error. The page seems to be redirecting itself to the same page and losing some of the prior context. We were trying to find where it resubmits itself. Eventually we found a JavaScript function that was happening in the page header. It was looking for a certain URL variable. If it was not found, it was resubmitting the page and adding the variable. That is fine and well but doesn't work for pages that are submitting form fields.

We ended up getting some help from ChatGPT, after hours of digging. We honestly could not find the error. Funny side note, the original function looks like it was written by an AI bot, and someone added it to the page to help automate something, we then had to use a different AI bot to help fix the problem. Bryan spent hours looking around, then he got me involved. We spent hours together trying to figure it out. AI both helped and hindered on this one. Two-edged sword... :)

Meeting with Bryan. Code review on his smart cart tiered pricing buttons with size variations. Fixing a number of merge conflicts. We then got in there and did some editing and testing. We pushed up new files to the data 0 box for testing. Good session. It was 2.5 hours straight to get it up and going. That included running some database updates on all servers.

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

- Pricing has always been a crazy battle.

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

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

----

Adilas Pricing Summary

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

- 0.4% of gross revenue

- Minimum: $59 per month

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

Setup & Training (One-Time Fee)

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

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

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

Additional Services

- Ongoing training: $65/hour

- Custom development & integrations: $100/hour

----

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

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

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

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

- The per location question always comes into play.

- We need to set some minimums.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Meeting with Bryan. He is playing around with Gemini (AI agent) that is built into Google Chrome. He is having it do certain user interactions and following it through the process. He is trying to figure out a way to harness what is already built into the browser. He was showing me some demo options and navigating the internal shopping cart. He was also playing with it out in the ecommerce realm. We were exploring all kinds of stuff. Bryan was having fun looking into existing options within the Google suite of tools that already exists. We were talking about using logs to help the AI agent learn on the fly by being able to search the logs and find patterns.

Working with Bryan on shopping cart text colors for readability. Most of the carts were good to go. We had one client that had a super dark theme and the text for the mini scan cart line items was coming back as white text with a white background. We did a small override and forced a text color for the line items. Pushed up new files.

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

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

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

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

Emails and requesting a few main website changes from Chuck. I wanted a few new link options from the main header, under the adilas world menu option. I wanted to add the presentation gallery, fracture - adilas lite plans, investment opportunities, and a link to the adilas API. Quick phone call with Bryan. He found a couple of pages that needed some CSS updates. Small quick code changes on the classic cart. Working on the form field CSS stuff for the classic cart. Ended up going through each of the cart options to help with look and feel. Pushed up the new changes.

Lunch meeting with Bryan. Talking about goals, direction, and what we are seeing. Some of our conversations were talking about our team, the next vertical, and what are our plans to get there. Where do we want to be in a month, two months, a year, etc.? Great conversations. I gathered that Bryan has been out selling this thing (adilas software) for the past couple of years here and there. Not fulltime, but he has been hitting the streets. He has some good information and things that I could glean from his experience.

As a side note, what if our next business vertical is selling our kick butt business engines to entrepreneurs or outside parties and helping them skin it and market it. That is right in line with our value add-on core model. Let's do that. We have a generic business tool, on purpose. Now let's start putting the industry specific skins on it. Build out the API, build out the ways to do the custom skins, etc. Go in that direction. Keep finishing up the MVP (minimal viable product) for a full-on business engine. Go sell the engine.

As a follow up - as I was driving home, I had a few thoughts. I sent Bryan a text saying that our next business vertical could be selling our business engine to other parties. He wrote back and asked, who would be our competitors? What language would they write it in? Are you thinking open source or something different? Great questions. I wrote back and said... I'm not sure. On the language question, if we build it, we will code it, using the languages that we use, and then put it on our servers. If they used an API, they could host it and use any language that they want. Some good questions, we might want to look into this a little bit deeper. Fun lunch meeting and fun to think about ideas and options.

Quick phone call with Bryan. He has a kid's group that just needs a super small kid friendly interface for simple POS (point of sale) functionality. Think mini POS. They are a potential client. We talked about tracking things by location (booths or tables or what they call themselves, if they have a brand or store name) or by person (kid's name). Super simple. Just add an item and have it flow into an invoice. Maybe allow for discounts, if they want, but nothing fancy. No inventory tracking (using unlimited items) and be able to take cash and cards (checkout options). Easy setup interface and then populate the store and quick buttons based on what they setup in their mini store. Be able to give them some simple reports. Super simple stuff. Great ideas.

I got up and started doing some planning and brainstorming. I was just planning on doing a little bit and the ideas kept coming, so I wrote them down. Here is what I got.

- Do some 1-pagers (one-pagers). Maybe even 4 or 5 of them. Quick reference stuff that could be used alone or used together as part of a group. This could be for sales, intros, quick guides, showing pieces. Make them all simple 1-pagers.

- Include the elevator pitch on one of the 1-pagers

- Show correct web links on the flyers or 1-pagers

- Link to the plan - fracture or adilas lite

- Old adilas GPS core image

- Old adilas formula flyer

- Old adilas map or interactive map flyer

- Maybe update some of those older one-page flyers

- Link to the presentation gallery

- Talk about ways to invest - 1/10th of a percent, 1% (full percent), 10% - show some levels and options

- 75% of the company (adilas, llc - adilas.biz) is available for purchase

- We are doing a capital raise - Looking for 2 million to 10 million for a new buildout

- Setup some small rules - this would be for investments and raising capital for the new buildout. Straight prices, don't worry about taxes (basically with tax included). Simple 1-pager, you get x percentage for y dollars. Super simple and cut and dry. No promises of future value. Basically, if you buy in, you then own part of the company. In the case that it sells, you would gain from that sale. There are differences between buying a percentage and active funding of projects. Maybe make small 1-pagers per section with some super simple rules. Add links to the web site for investment options.

- Talk about options for commissions - 10-20% - leaning towards 20%

- White labeling - minimal starting investment of $100K - buy in at a percentage (could be small), then do a plan and figure out the scope. Detail things out. Then figure out the plan from there and how complex the new white label is going to be. The initial $100K pays for the ability to build on top of the kick butt engine and the detailed scope and development plan. The rest will be determined from that point. The goal with the white labeling is geared towards future revenue and rolling things out in scale (future reoccurring revenue from multiple clients or business verticals). White labeling is an investment and plan for the future. If the project feels like less than $100K, we may push you in the direction of custom code vs actual white label.

- Dealing with white labeling - This is something that gets built on top of the adilas engine, ideally built by our team for a 3rd party vendor, that 3rd party vendor would then run the marketing, billing, tech support, etc. for their clients. We would most likely host their white label on our servers, and let it ride on top of what we have. It could even limit access to the underlying pieces. If someone wants to host it themselves, code it themselves, and just use API's (backend connection sockets and such), that is different. That would be a 3rd party solution and would go through the adilas marketplace.

- For white labeling deals or buildouts, we will end up setting some rules and prices for monthly fees, profit sharing, wholesale costing, dedicated or shared hosting, and other details.

- Talking about scope, timelines, feature creep, and change orders. If the plan changes, in any way, we need to be able to adjust (change orders). That could affect scopes, timelines, deliverables, budgets, milestones, etc.

- For me, think about the trystorming type approach with a known need to circle back around and refine things

- Contact info on the 1-pagers and in the packet(s)

- Old graphics about ecommerce, system players, choose your skin, show your stuff, etc. See image.

- Ideas - You could go around with some flyers and do some seeding...

- Get people to go door to door in neighborhoods and/or in business districts

- Promotion codes and lead tracking - tie back to commissions and affiliate programs

- Social media influencers and people who push products - sometimes people trust these guys/gals/people

- We start with the main adilas MMLLC (multi-member LLC) - then we open it up into the other MMLLC's - adilas.biz, adilas shop, adilas university, adilas marketplace, adilas cafe, and maybe adilas funding or adilas management - there could be others - adilas employment, adilas staffing, etc. Along with that, allow for investment options of 1/10th %, full percentages, and bigger percentages (say 5 to 10% and above).

- When ready... maybe a small glossy folder with a few key 1-pagers in it - small packet

- We need to do some market research on the pricing. This will help us be more confident in our pricing. We have to follow the market value. There is an optimal range. And, the market is changing dramatically right now with AI and SaaS mixes.

- Most credit card processing fees are around 2.5% of your credit card sales per month. We are pricing adilas around 5% of your total sales (cash and card) per month. Also remember, most companies are doing the mash-up option and paying for multiple systems to make up the whole. Paying 5% for one integrated system, is great!

- Small samples on pricing... Basically, take a monthly sales number and times it by 5% or 0.05. Samples for some starting numbers: Monthly sales from $0-$400 x 0.05 = $20 (smallest monthly fee). Then show values for $1K, $5K, $10K, $20K, $40K, $60K, and $100K - using the same formula. Make a note about multiple locations. Simple math. If one or more of the locations are at a different size (sales volume), no problem. We can set those values. Once a monthly is set, we can hold that number for six months, and then we may review it if needed.

- In sales, if there are custom needs, we are willing to talk and chat about quantity discounts, franchises, seasonal usage, clients not using the sales features but using other parts of the system, etc. We can provide special quotes and structure deals. We can't go lower than 2.5%.

- This is for me... Just as a reference, we at adilas, pay about 15% for servers and web hosting. As of end of 2025, we are paying around $12K per month just for servers.

- $1,500 starter package - list it out - setup, turning things on, and up to 15 hours of training and/or help getting things configured and going. Monthly fees are separate. This is just the starter package. If you don't need the training hours, it is $500 for a one-time setup. You have to have a prior system to just do the new setup fee as a standalone. If custom circumstances exist, we recommend that you get ahold of us and we can figure out a deal. The goal is to get you going and make sure that you off to the races.

- Once the training and setup hours are done, if you need more help with monthly tasks, special tasks, or whatever, we bill at a rate of $65/hour. This could be for consulting, setup, bank reconciliation, data entry, etc. We want to help you get going strong and we offer services where needed. The future goal is to use the adilas marketplace or adilas cafe to help fill these needs.

- Get the flyers done professionally - make them nice

- Use a temp service to help get the word out - get them the information and/or packets and let them manage it

- At some point, we will need an internal training meeting for our team members

- Make some new page (web link) redirects - some of the files and places have longer web addresses - make a number of smaller redirects - folders and path stuff - links like the adilas lite or fracture plan, investment opportunities, and the presentation gallery.

- Fix the adilas pricing page - show some other options - line it out a bit. It is pretty simple right now.

- Help work with Bryan on his sales channels - Finetech (merchant processing) and Host Huskie (web hosting). We could do similar things over and over again as needed.

- The existing software package (adilas.biz) can handle 75-90% of any business - out of the box.

- Just a thought - what if I put all of this into AI to see what I get - that would be cool. Maybe wrap it all up together.

- Get out of the way!

Phone call with Bryan. I was driving home from meeting with Gene and got a call from Bryan. I'm really proud of him. He is chasing the dream and really trying to find a way to tap into existing sales funnels and lead generation sources. He is trying to work with Finetech (merchant processing company) and also Host Huskie (website and web hosting company). They both have needs and clients that are looking for software solutions. Trying to get a good sales engine going and functioning. Our goal is to work together to finish up some industry specific skins and get them out there. I really like his direction. I told him that I would help him where possible.

Paying bills and recording notes. Meeting with Bryan. We were looking at some of his restaurant table assignment stuff. This is new functionality with saving quotes and assigning flex attributes to the quotes and invoices from within the shopping cart. He added some new functionality and we walked through things. Small code review.

Working with Bryan. Small CSS changes. Going over his MVP list for restaurant style management. He is working down his list and only has a few more things on the MVP part of the list. There are still some other things, but he is getting much closer. I'm proud of him.

Meeting with Bryan. He wanted to do some planning on the Finetech and host huskie projects. We looked over some of his notes. He is gathering some little bites, chunks, and getting a number of recommendations from ChatGPT. Harvesting some of our user's feedback and recommendations. That is huge.

Working with Bryan on some ecommerce changes. Small bug fix.

Meeting with Bryan. He was showing me some AI chats and discussions that he has been having and talking about direction going forward. He was showing me some stuff on his restaurant and table management stuff. New features inside of adilas.

Good meeting with Steve. We went over tons of different things. Here are some of my notes.

- Fixing the Grok AI Agent. It is available but not yet trained. We have it hooked up, but hidden... Just us can play with it right now. It will be an ongoing project. We made it so that we could push it up live but, once again, no one knows about it and we don't want them to know about it yet. Steve wanted it to show some people that there is some potential (seeding the discussion).

- Lots of talk about sales and generating revenue. Steve wants to work with people who are willing to talk to anyone and then when they want a demo, he and Sean can step in. He doesn't want to train them on everything, just a simple salesperson who can generate leads. He wants our team to do the demos.

- Steve was asking about Alan. We jumped in and looked around at both the system (timecards) and bit bucket. I reported that I had met with him and it was a great meeting.

- We talked about adilas and expectations. There are a lot of undefined rules and assumptions. We are planning on refining some of that as we go. It just is what it is right now.

- Steve is doing tons of small mini projects for Cory. He is really busy doing all of the little things. I would say he is getting buried. I have been there so many time. I feel for him.

- We talked about a couple of possible partners and outside businesses that have expressed interest in what we are doing. Currently, there seems to be lots of demands and not much show of support so far. It is just starting out, and we aren't sure where it is going. We want the leads, the customers, and the work, but so far, it hasn't really produced.

- We are trying not to waste time and energy, but we really don't know where to go. We are basically, trying to follow the money. Picking up the pieces.

- Steve and I talked about options in sales and also trimming down our current team. We have to cut some costs. It is rough sometimes.

- We spent some time talking about payment processing and how they do their billing. They, the payment processors, usually do a percentage of the monthly credit card sales. We would like to do something similar but instead of doing just the credit card processing, we would like to do a small percentage of the total sales per month. We are thinking from 1% to 1/2 of a percent. Somewhere in there. Trying to figure that out.

- Steve was talking about robots and even payment processing is becoming more automated and even mobile. He was talking about advancements in robots and other technologies. He reads a lot and likes to keep up on that stuff.

- We would like to get our Grok AI agent up and working. We feel that we may be able to control that better than having an outside party program and control it. That is still a lot of work. Steve really feels like if we don't embrace the full AI wave, we will be left behind.

- Bryan popped in for a minute. I told him that I would text him when we were done. We were spoused to meet but Steve and I got started late.

- Bryan is working with some CPA's and trying to get them to see the vision of what we are doing. Long ago, that was Steve's vision. He wanted to fly around in his plane (he's a pilot) and go see all of the CPA's and show them how adilas works. Funny but cool, old memory. Still a possibility.

- Steve has been around a lot of salespeople. He was sharing some of his experiences. We need people in places where there are a lot of other people (businesses). We don't have anything right now, as far as a salesperson or a sales team.

- Sales is just a game of numbers. You also have to be willing to be told no. Not all personality types can do that. Steve was mentioning that we have started a bunch of people but they haven't worked out. This may not go here, but I'm going to add it in anyways. Steve and I were talking on Monday, 1/12/26. I had a meeting later on Thursday, 1/15/26, with Shannon. She made an interesting observation. We used to have a rep type model, where the rep, an independent, would go pedal and push our product. They would then get a commission and also be able to get monies directly from the client to help with anything that the client needed. That was very successful. They, the reps, would max out and eventually stop, but each one could handle a certain number of clients. We had some reps that were making great money. Because it wasn't super organized, we decided to pull that back internally. Due to budgets, we have not been able to fill that same role that those reps were providing. We have way more control over what is being done, but we don't have anybody out there pushing on things. Interesting observation.

- Back to the meeting with Steve. After we talked about sales for the first little bit, I changed gears and did a mini pitch to Steve about focusing on people and trying to stabilize the team. That conversation always comes back to funding and where do you get the money from? This has been a common theme over the years.

- I was drawing and showing some ideas. We have focused on features and functionality so much. We keep building lists and slowly clicking through things. I really feel like we need to change the focus to people and the team vs the next cool thing. The sad part is, we have done this for years and years and years. We keep thinking, when we get such and such done, it will all get better. We get to that point and then there is always something more. I honestly can't even see the end of what is wanted (feature or functionality wise). It feels like a perpetual or ongoing list of wishes and demands.

- We jumped in the system and were looking at sales, numbers, trends, year over year totals, etc.

- We may want to allow the developers to go back and bid (put out estimates) on custom code projects. That's what they used to do, back in the day. We tried to pull that all under the main adilas roof as well. That was super expensive. We may need to figure out a hybrid and see if we can make that work. We don't want a full wild west again, but we may need to bring some of the independent pieces back in. It just costs too much for us to fully support a full staff of full time developers. We'll figure it out.

- Our costs are around 40% (roughly). So, if you had a system sell for $100. We would use $40 to pay for servers and other small things. The other $60 would be profit that could be split and/or divided to create some sort of incentive. Steve is trying to see if he can get anybody to play that way. We just have to get more clients. He was pitching a 50/50 split of the profit. So, for a $100 deal, that would be $40 overhead (costs), then split $60/2 or $30 per entity that is helping with the sale.

- We were talking about setup, activation, and selling systems. We are seeing a growing demand for enterprise level functionality. They, our clients, just expect us to have it all built. They really want it, but it is only partially done, not all the way yet. We end up getting stuck in the middle, footing the bill, and not being able to just sell what they want. We already have vendors, customers, and items on the enterprise level. We just need so much more. Well, you have to start somewhere.

- Steve was talking about 10 free hours of training and then rolling into $65 per hour after that. We can help with anything that is needed, whether that be training, data entry, bank reconciliation, inventory help, balance sheet and accounting work, etc. We offer a lot of services. Basically, what do you need? We can help.

- Steve wants to find some power users and see if they would like to work for us. We have had great success by hiring people who were once adilas users and then bringing them in and onto our team. They already know and love adilas. They tend to find a good home with us. It just comes down to budgets again.

- As we were talking... I was pitching things and it kept getting met by something like... We've tried that... We need to do something different. I don't feel like that. If we did try things, the timing may have been off, the wrong person, or it wasn't really tried. I don't want to just keep randomly trying things. I think we need to focus on people, talents, skills, and personalities. If we can get the right people in the right places, and get them trained and supported, it will work. I know it!

- We may need to try things again! Lots of things are changing and been changing over the years. We have been doing this since 2001. Adilas became a real entity in 2008. We need to circle back around and focus on people.

- The topic switched to AI. Steve wants us to use AI to build code for us. He thinks that we can reduce our tech needs by 60%. He uses it tons and tons. I use it as well. We want to get our other developers up and going on it. It's not that they aren't... we just need to keep going. We need to look at it as a tool, not the only answer. It does have pros and cons. It definitely has its place. Certain things still need the human touch.

- We ended our meeting by him telling me that I could look around and work on a plan and then bring it back to him. We have to make some changes. That is for sure. I just don't want to randomly do things that may hurt us in the long run. It takes me so long to train new people. I hate to see them just go away. We have a team, but yes, they are kinda tired. We have been running hard for years and years, almost without any breaks. That is rough. We will figure it out. That's the new goal. Figure out how to make this work and stabilize the team.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

- Came home, played a game with Brooklyn

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

- Made chocolate mousse

- Played a game with Heather and Brooklyn - Heather won

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

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

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

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

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

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

- Graphical homepages

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

- Work as if for years

Working with Bryan. Looking over the new changes for the smart group rules and being able to do tiered pricing based on quantities and custom sizes. We looked over some of the code. Light clean-up. He is going to turn the branch over to me and I will do some testing and fix some merge conflicts. Talking about circling the wagons and touching base (communications and watching out for each other).

Bryan has been meeting with some accountants and getting their take on modern accounting and such. He is seeing where they have needs and wants. Sounds fun. We then switched over to do some code review on his branch with new tiered pricing rules and assignments for selling things by size. After we looked over some of his new changes, we then flipped to a different branch that was dealing with flex attributes for shopping carts, quotes, and invoices. We looked at a bug and got it fixed. He is going to tighten things up and we should be able to do the final code review next time.

On with Bryan for a code review session. Working on his dynamic rules for tiered pricing using something other than quantity. It is pretty deep. Lots of logic changes and tweaks. We still need it to be a little bit tighter. It's getting close.

Meeting with Bryan. Looking over some different projects. He is working on two main projects right now. Most of our work was looking at his changes to the my cart favorite buttons and the smart groups (tiered pricing). He is working on some code that deals with changing the rule type from normal tiered pricing based on quantity to rule types based on other dynamic fields or settings (like sizes, diameters, or something).

He is going to refactor a few things and clean it up a bit. Our plan is to meet again later today or tomorrow to do a deeper code review.

On a meeting with Bryan, looking over some new rules for smart group buttons and tiered pricing, based on sizes, vs quantities. He is making good progress on that project. He has a client that wants to bulk price things based on some sizes.

After the meeting, I made a small custom email change for Shari O and Applejack RV Park. Made changes and pushed up new files. Sent Shari O. an update email letting her know that everything was good to go.

Working with Bryan. Going over one-to-many relationships for parts and items. He has some special pricing issues and questions for one of his clients. We talked about existing options and where we want to go with things. Currently, we have parent to sub items, parent to flex grid tie-ins, or smart group rules and assignments. These are all special one-to-many pricing options.

Going over which one would work best and what we need to change to make that happen. For his current scenario, we spent some time talking about the rules and assignments for smart group buttons. Currently, those rules are based on quantities. We were talking about doing some rules or rule types for sizes or some other characteristic. Good discussion.

Bryan and I met up to look over progress for the restaurant and simple food service functionality. Bryan Dayton has been helping to chip away at this for the past year or so. We did a small review session and took a bunch of notes. Bryan then had the idea to take the new notes and add them to the old notes. We ran them through ChatGPT and it did a great job summarizing things up. We then read over those notes and talked about next steps. Here is the link to our small discussion.

https://chatgpt.com/share/693c91f3-a6bc-8007-a331-7ea33d2b84f2 - notes from Bryan and I from ChatGPT - restaurant and simple food service functionality

After going over plans and notes, we switched briefly over to some other projects. We will meet again on Monday to get into some other projects. We also briefly looked at some hours that have been recorded over on the ship B (adilas shop) side. Both Bryan and I (and others) have been banking some hours on projects that don't have full funding (yet) but we know that they will be needed.

Working with Bryan to look at some future development for a school that tracks native american students and some of their goals and progress. Going over plans and talking about ways to setup the one-to-many relationships that they need. We briefly went over some document management (custom documents and assignments) and connecting to custom paperwork options. We also talked about stepping away from the computer to do some planning. Sometimes that really helps. Otherwise, you get distracted.

On the GoToMeeting session with Abby. We were working on graphics and doing some practice. We started out doing some vector graphic stuff and then moved over to photo editing and making combination images or composite images from multiple sources. Little bit of mixing and blending. After Abby jumped off, I merged in some code for Bryan. Small bug fix.

Working with Bryan to fix some bugs on his local box for flex attributes. Once we got that fixed, he went in and made a small edit to the advanced invoice search with flex attributes.

Small tweaks for Sean. He needed me to un-void a PO on data 16. Then on a phone call with Bryan to make a few quick edits. Pushed up a few files on data 6 for testing in recipe and production land.

Phone call with Bryan going over next steps and priorities. We launched a bunch of new code last night for him. He has been meeting with different folks and getting requests and ideas from them on what they would like adilas to do and be. Trying to help make it easier and more marketable. Some of our clients want it to be more simple. We may have to go a little bit deeper before we can do that (more complex controls to make it look or appear more simple). Small to do list items.

Recording notes from 12/1/25 to 12/3/25.

Working on the flex attributes for invoices and quotes. Quick meeting with Bryan to show him the progress. We looked over a few things and did some test transactions. We created quotes, restored quotes to cart, made a few invoices and then duplicated those invoices. We have a little bit more work on the submit cart page, but getting much closer. Some of this stuff (code pages) are things that Bryan is wanting for restaurant functionality like areas, sections, tables, number of guests, reservations, etc. Good stuff. Making progress.

After Bryan left, I spent the rest of the time testing code and fixing merge conflicts. This was a pretty big branch, and we ended up with 20 files with merge conflicts. That is because we started it, this flex attribute project, almost 9 months to a year ago. Lots of cart and invoice changes during that time. Anyways, we got it all merged in.

Work session with Bryan Dayton on flex attributes for invoices and quotes. We are getting closer. Working on showing both invoice flex attributes and quote flex attributes inside the cart. Lots of moving pieces. Bryan was fixing some merge conflicts and I was coding the new logic for showing and updating the flex attributes. We got all the way to inserting the new flex attribute records. We ran into a little snag but will hit it again with fresh minds and eyes. Good long work session today.

Working with Bryan. Talking about the AI options and how the training is going. We had ChatGPT convert a handwritten scan and had it make a visual display. That was pretty cool! Then we were talking about plans and direction.

We switched gears and flipped over the flex attributes in the cart (for invoices and quotes) project. We made some small plans and looked at older code commits on the branch we are working on. We then jumped in and did a good long work session on adding flex attributes to invoices and quotes and being able to use them inside the shopping cart (working on the details). We spent a lot of time working inside the mini scan cart and creating a modal popup window for editing the flex attributes. It is getting closer.

Emails and paying bills. On the phone with Bryan going over some ideas. Talking about custom development, running specials on development (prices), helping with training manuals, and having a custom code budget per customer, if needed to help make the sale.

Paying bills and recording expenses. Quite a few from the trip that Bryan Dayton and I made to Las Vegas for the Adobe ColdFusion Summit conference. Checking emails. There were quite a few emails going around in preparation for launching the AI agent next Tuesday.

On the phone with Bryan. He had some questions about reoccurring or recurring invoices. We talked over the process and other options that we could add in, if needed, including full automation and dynamic data (changing invoice prices and totals vs a fixed reoccurring process). We also talked about getting back to some of the restaurant functionality that he was working on back in August of this year. We set a date to get back to that in a couple of weeks, before Thanksgiving.

Emails and reviewing a super cool video on Affinity Studio - It has some awesome custom menu options and is a well done promo video. I watched it and then sent it out to a number of our people to show that what they are doing. I would love to be at that level where we can push something like that out and create those kinds of tools, features, and razzle/dazzle. Pretty cool!

Paying bills, phone call with Bryan about transitional invoices and options. We have the functions and functionality, but nobody knows how to use them... We need more training and easy ways to get at what is possible. I was explaining to Bryan how it all works. We also talked about moving away from sub inventory, depending on the scenario. Sometimes parent inventory tracking works better than subs, for certain scenarios. We also need to get to the ICC (internal cost corrections) project up and going. That has been a requested feature for years.

Recording notes from yesterday and today.

Working with Bryan. We got him all setup with a VPN (virtual private network) and FTP (file transfer protocol) access to the servers. We talked about flow and some pros and cons to some of these pieces. We talked about security. He used to have access, then we changed servers. We then jumped into adilas and started working with the new AI quick search prompts. He was curious on the progress. He turned on the AI agent for his own corp. Light talks about direction and progress.

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.

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.

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

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

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

Notes from Alan:

- Shifting our mindset a little bit

- What is working and what is not working

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

- Being proactive in our approach

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

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

- Maybe some new dashboards

- AI is amazing when it works

- Using AI to help us modernize our interface

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

- Taking about proactive maintenance

- He (Alan) sometimes struggles with communication

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

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

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

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

- Talking about dreams and what would that look like

- Stuck in between what we want and what we have

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

- Running in circles

- Chasing a ghost (phantom look and feel)

- Alan asking about the goal with the investors

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

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

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

- Talking about adilas and where we are at financially

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

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

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

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

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

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

- Looking around in the system a bit

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

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

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

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

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

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

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

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

- We have an MVP (minimal viable product)

- Finding people who are happy with what we have

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

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

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

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

- Shooting for $400/month

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

- Learning to say no

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

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

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

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

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

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

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

- Just tell everyone what you do (from Kiva)

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

- Being outside and out and about

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

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

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

- Stay on the good side of town

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

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

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

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

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

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

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

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

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

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

- Maybe look at some sport teams - other team sports

- Not trying to sell things, just doing some exploring

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

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

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

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

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

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

AI Summary:

Sales & Strategy Meeting Summary

Attendees: Alan, Steve, Brandon, & Bryan

Meeting Overview

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

Key Discussion Points

Alan’s Focus

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

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

• Emphasized AI modernization for the Adilas interface.

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

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

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

Steve’s Focus

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

• Acknowledged issues with time estimates and scope management.

• Proposed pricing structure:

  • $100/hour for development

  • $65/hour for setup/support

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

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

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

• Encouraged avoiding excessive custom development to protect scalability.

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

Action Items

• Define the ideal client profile and align pricing accordingly.

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

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

• Improve internal communication and proactive planning.

• Explore investor options and sustainable growth strategies.

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 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.

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.

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.

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.

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

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

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

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

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.

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.

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.

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.

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).

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.

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.

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.

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.

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.

internal_shopping_cart_r1.mp4 - on Google Drive - small future cart demo

cart_touch_and_discount_options.mp4 - on Google Drive - current cart demo with my cart favorites

Looking at code with Bryan. He is getting closer on some of the restaurant code that he has been working on (rooms, tables, and servers). He is adding in flex attributes for invoices and quotes. They, the flex attributes, also get passed through the shopping cart which will be pretty cool. There are more things than just restaurant level functionality that will be taking place, but that's a start. Good session. He basically turned that branch over to me to do a deeper code review. I will review it and merge it into the master branch.

At the end of the meeting, we were going over plans for the upcoming Adobe ColdFusion conference at the end of September. Making plans and shooting around ideas.

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

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

Recording ownership percentages for adilas co-owners inside of adilas. On the phone with Bryan to talk about database field validation on merchant processing auth keys. We have a client that is trying to input values that are not allowed. The system is setup to not allow certain words, phrases, and strings (cross-site scripting protection stuff). They were given this auth key from the company, but it violates some of our validation routines. We had to open it up a little bit for that page. Crazy stuff.

Paying some bills and documenting expenses in the system. Other small to do list items.

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

On a conference call with Bryan and an adilas client. They were requesting some small changes to a custom section of their ecommerce checkout process. They are going to send an email with details and more information (paper trail). Promised these changes by end of day tomorrow.

Working with Bryan. Looking over some files to help with some merge conflicts. Making changes and trying to retrofit things that were made on both old and new branches. We kept running into some issues. We may make a new branch and then plug in pieces vs trying to update the old code from the old branch. Basically, change the direction of how we are retrofitting things together. That should help.

Meeting with Bryan. He had an older branch that had multiple merge conflicts. Going through that process. We had to get his local box up to speed with new environment variables and settings. We ran out of time to do the merge conflicts on the old branch. We will do that at a later date. We then flipped over and did some more work on getting Bryan's local machine up and running. After that, we looked at Cody Apedaile's checkwrite and label builder code. Bryan wants to use some drag and drop functionality to build out a restaurant interface type environment. Bryan and Cody are going to be working together on that project.

Got a phone call from Bryan. We went over some of his current projects. Some of our code branches are getting older and have a number of merge conflicts that we need to work through. All part of the game. I then spent some time emailing back and forth with Cory from adilas about the partial PO project. That project somewhat got put on hold while we were working on the custom checkout process in ecommerce for the Benning Construction charity golf tournament project. Just circling back around and getting things oriented as to where to head and go next.

Meeting with Bryan. Fixing some small bugs out in ecommerce. We made the changes and did some live testing. Once we got that finished, we switched gears and looked at Bryan's code for his Plaid API stuff (external banking API). We did some more testing and tracked down a number of different variables. Trying to make the whole process smoother.

Work session for the Benning construction site. Added a new top header logo. They provided a nice flyer. Took a bunch of the images off of the flyer to rework the header graphic. Working on the custom code to help with the donations page. Had to open up the pricing field. Meeting with the construction company and Bryan and Suzi from the adilas team. Quick meeting. We are getting closer. After the meeting, then working on a small to do list of items. Small cosmetic stuff.

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

Phone calls with Bryan. He and I are working on the Benning Construction website. He passed me over some code via email. We also heard back from the client, and they are wanting a fancier looking site. Lots of lastminute changes. We'll see what we can come up with.

Internal tech support, helping Bryan with questions for a client. Multiple phone calls with questions. Lots of internal PO and inventory stuff. He needed to know how to switch vendors, mix vendors, convert between pounds and single packages (each). Also questions about printable invoices and forcing things to a certain size. Answering questions. Some of the topics I haven't done in years. It was stretching me a bit.

Working with Bryan. Going over new web requests for the Benning Construction golf tournament. Bryan was making changes, and I was doing different stuff. Prep work, custom black box takeovers on ecommerce pages, new logos, removing search filters, opening up a price field for donations, etc. Hours of work, back and forth, between Bryan and I. We had a GoToMeeting open and would ask each other questions, go on mute, work a little bit, check back in, etc. We pushed up some code and did lots of testing. Great little work session on the custom ecommerce site.

Working with Bryan on ecommerce stuff. We went in and rolled back some code that we did yesterday. We then had to do some magic to help out with which merchant processing accounts are allowed out in ecommerce land. We made a few switches and pushed up some files. Mostly pretty quick changes. Nothing too major.

Follow-up meeting with Benning Construction (gold tournament project). Quick touching base on project and new requests. They got us some requests at the last minute. We worked through a few of them. We have a few more to do before our next meeting, next week. Quick phone call with Bryan after the main meeting to go over plans and schedules.

Working with Bryan on the golf tournament site and some new page flow options. We made a few changes, merged in some code and pushed it up to data 6 for some testing. Some of the new code is mixing event scheduling with Bryan's quick cart code (limited ecommerce flow).

Meeting with Bryan to go over some new requests for the Benning golf tournament. They sent us a whole email with a list of things that they wanted to tweak and change. Bryan and I were going through requests and looking at options. We added a new generic customer to help skip login and make the flow easier.

Working with Bryan on his Plaid API look-ups (external banking stuff). Lots of string manipulation and regular expressions (dynamic text options). The API returns vendor names all mixed in with account details, reasons for the purchase, and other un-needed details. We have to parse through all of that data and only record the meaningful pieces. Lots of moving parts.

Emails, phone call with Bryan, and internal tech support. Looking up data for a client on data 7 and then sending an email with my findings.

Working with Bryan. Viewing chart of accounts and expense types. Light training on how expense types and chart of accounts work. Going into the five level deep options and how we classify our chart of accounts - destination, category, group, sub group, and actual accounts.

Quick meeting with Bryan to go over some ecommerce pieces. He may go in and help to hide some of the shipping info and pages within the existing ecommerce page flow. We could use that for a client that we are working with. They don't ship anything. We then flipped over to work on the external banking stuff and the Plaid API. Fixing his pages to handle the test and live app mode. Merged and pushed up some code.

Meeting and follow-up with the Benning Construction company. They are going to be using adilas to run a golf tournament later this Fall. We went over progress and made a few small assignments. Making progress. Good stuff.

After the meeting, Suzi, Bryan, and I talk about plans and went over assignments.

Emails and then watching a video from Bryan and one of his clients. Going over needs for parent attributes and how best to see and process those pieces. Bryan Dayton sent me a video, and the lady had all kinds of parent attributes for her snack food business. She wants to put all of this info inside of adilas and be able to search and filter things accordingly. Currently, she is just using a bunch of spreadsheets to keep track of everything. Bryan and Sean, in the video, were helping her see some of the cool things that a data table could do with sorting by columns, local searches, exports, etc.

Meeting with the Benning construction company to help with their golf tournament. Touching base, showing a quick demo, and asking some questions. Bryan and Suzi were the main adilas contacts. A lady by the name of Jessica will be the contact on their side. Bryan sent them an email with information requests. We setup a meeting for next week to touch base. They need some of it done by mid-July and then the remainder of the site done by September.

Meeting with Bryan and talking about searching parent attributes. He is working with a client who is taking parent attributes to the next level and needs some supporting options for running and filtering data accordingly. When I say taking it to a new level, imagine someone who has hundreds of possible options that they want to track. She, the client, does healthy snacks and wants to track all kinds of nutrition facts, allergy stuff, texture stuff, sugar content, carbs, and everything else that is needed for her business. Pretty deep. I only saw a minute of a video, but I could tell that she needs some better tools, for what she is trying to do. We chatted about some options.

Working with Bryan and looking at ways to quickly verify expense/receipts. We already have bulk tools, but this was basically a shortcut for users who wanted to use the plaid API (external bank stuff). We want to add the receipts and mark them as verified (two steps for the price of one) at the same time. This could potentially save our users a few steps. This is just me, but I'm kinda torn... If we add this external bank help... it may speed things up for some of our clients. It also teaches the users bad habits. Instead of putting in the expenses as they happen (ideal), they wait and try to have the system put it all in for them (automated after the fact). They, our users, are back to batching things vs running on real-time values. You lose some details. Anyways a small bittersweet.

We merged in the code, and it will go live tomorrow morning.

Meeting with Bryan. Looking over his progress on the Plaid API stuff (external banking API). We did a little bit of work with some of the dates. We like to see dates in a certain format and our code works well with that format. The Plaid API likes the dates passed to it to be in a totally different format. We flipped a few things around and got it pretty close. Bryan is going to go in and try to track things down a bit more and then we will re-meet to push up new changes.

After Bryan left, I did a little bit of clean-up, recording of notes, and paying bills.

Meeting with Bryan to go over the planning for the upcoming golf tournament that we are going to be running through adilas for a construction company. We went over a bunch of known needs and did some planning and brainstorming. Bryan was taking notes. I was drawing and highlighting different parts and pieces of what we need to do and how we can get those things done. He took a bunch of notes and a few screenshots of our drawings. We also setup some more time next week to touch base and keep pushing the ball forward. Good work and planning session.

Meeting with Bryan and looking at advanced expense/receipt queries and underlying results and values. He was doing some special query stuff to try to work on the Plaid API code (outside banking utility stuff). On his local box, he had an expense/receipt, but we couldn't get it to pull up through the new code. Because he was testing things, he had added in a new vendor and then deleted it. The old record was still tied to that vendor id number. The system couldn't pull that record because the table join was broken, due to him manually removing the vendor (practice stuff). It took us a few minutes to figure out why we couldn't get it to work. One of those days... :)

Meeting with Bryan. We jumped into the data 11 server and were checking out some merchant processing options. We had to fix one of the merchant accounts and change some settings. We then briefly talked about another project that will be coming down the pipeline. We went ahead and setup some time on Friday to work on that other project.

Working with Bryan and going over a comic book ecommerce demo and what they are doing. Brian Mowris from FineTech has a few clients that are in the hobby store arena. They are looking for quick ecommerce, full POS, and all of the other fun stuff that adilas could bring to the table. These are smaller customer but there could be a lot of them. We watched a demo and I took a few notes. We then got Brian Mowris on the phone and chatted with him. We feel like we are 85% of the way there, out of the box. We talked about a few funding options and how best to proceed. Good stuff.

Working with Bryan and going over new code to be able to switch locations out in ecommerce. He also introduced a quick mode that skips certain steps and limits how much editing of customer and profile type information. He is calling it quick shop mode. Light debugging and looking over new code. We made a few changes and then did some code branch management stuff to get everything all good to go. Fixed a merge conflict and got the new branch all merged into the master code branch.

Meeting with FineTech folks. Bryan Dayton and I were on the meeting on the adilas side. We didn't really know what the subject of the meeting was. The FineTech folks had a number of questions about merchant processing, onboarding, custom quotes, and possible white label stuff.

We explained the integration of Clover devices, emphasizing the use of the Cloud Pay Display app for connectivity. We then discussed the technical aspects of merchant processing, device compatibility, and the need for API credentials. Jennifer inquired about onboarding processes, training, and the potential for customization. I provided contact information for key Adilas team members for support and training. The meeting concluded with a discussion on industry targeting and the importance of clear communication for updates and new features.

From Bryan - Check and push Healthy Bite code

Working with Bryan. Looking at session values and switching locations out in ecommerce land. He is calling it the quick shop settings. We spent some time and reworked a query to only pull items per location that have 1 or more in the total quantity per location. Should be some good stuff. He still needs to work on it a little bit, but making great progress.

Quick phone call with Bryan to go over options for ecommerce, searching inventory, filtering data, and only showing certain results for different locations. The old code just looked at a single web location. The new code needs to flip locations and just show what is what for that store or location. We briefly talked about a couple of options and ways to apply those filters.

Recording expenses and paying credit card bills. Other general to do stuff.

Was going to be working on the vendor credit special account functions. Got a call from Bryan and he needed some help pushing up some code. Switched over to help him out. He is working on a new 3rd party API socket for the Plaid banking API stuff. Light testing and pushing up new code.

Meeting with Bryan. Looking over the availability to switch the store locations out in ecommerce land. Looking over his code and such. We merged in some new code. We then switched and were looking at a bug on the Plaid API code. Plaid is a bank account extension or a banking API socket option. Looking at error handling and try/catch type processing. Our session turned into a small work and testing session.

Paying bills and adding scans for documentation.

Meeting with Bryan and pushing the Plaid (bank stuff) code up for a new 3rd party solution and bank integration. There were a few merge conflicts in the adilas 3rd party solution pages. Fixed those and pushed up new code. Also looked at his current code for allowing multiple locations outside in ecommerce land. Small chat about other upcoming projects.

Emails and sending a guy a link to the adilas investment options and opportunities.

General to do list stuff. Recording notes. Quick meeting with Bryan to go over allowing multiple locations to be used out in ecommerce. We jumped on the GoToMeeting session and looked around a bit. Made a small plan. I had to go pick up one of my daughters. We had to wrap it up before we were fully finished. Hopefully it was enough to get started.

Phone call with Bryan to go over some ecommerce questions. He has a client that wants to use multiple locations out in ecommerce land. Normally, we use a setting and then just use that single location/store out in ecommerce land. We talked about what would need to be done to make it all work and how long that may take. We will dig into this tomorrow over a GoToMeeting session.

Benning golf tournament plan. Meeting with Bryan. Going over deliverables for the golf tournament. He had a document prepped with an outline. We then went through the outline and filled in either questions, assumptions, and/or plans. It went pretty smoothly, as far as a brainstorming process. Bryan has all of the notes.

On a Zoom call (demo) with Bryan and Suzi and HollyJo from Richmond city (Utah). Suzi was doing the demo. She had some open tabs to help speed up the demo. She started in on payroll options. She was showing user profiles, templates, permissions, and such. Talking about clocking in/out and how to do that on their phones, using a small mini app. Next, she jumped into different reports and how to navigate around. After that, she switched over to showing some scheduling for parks, practice fields, pavilions, and library reading times. HollyJo has a number of needs for project time tracking. We went over a few options there. Quick but a good demo.

Emails and looking at a siteplan for a new website for adilas. See attached. A couple different phone calls with Bryan to go over plans for the golf tournament folks. They got back with the Finetech (3rd party solution that we work with) folks and want to move forward. We gave them a demo a couple of weeks ago. Going over needs and making some small plans. More emails and recording notes.

Working with Bryan on merchant processing stuff. Going over settings for Clover and CardPointe and which auth keys go where, in the setup and settings pages. This is the trick, who holds the knowledge... that is hard to track down (meaning which developer built it and what do they know). Making sure that things get put into help files and passed along.

Had to postpone the demo. She got pulled into another city project/meeting. Bryan let Suzi and I know about the change in plans before the demo.

Emails and paying bills. Meeting with Bryan to go over some questions that he has for the Richmond city demo. We talked about a public facing calendar page for our clients. We have a great internal calendar, but nothing that is visible to the public. We have some clients that could use the public calendar feature. We may need to look into that as a tool and/or feature.

Online demo - with Finetech business solutions (merchant processing) - they wanted a demo for one of their clients that were looking to do a golf tournament and maybe use adilas to help them get reservations, sign-ups, and such for the golf tournament. Lots of talk about ecommerce type stuff, customer info, event info, and custom data tracking. I was giving the demo and showing a bunch of stuff. It went about 45 minutes. Lots of good back and forth questions and answers.

Phone call with Bryan Dayton afterwards to do a small recap and review.

Meeting with Bryan and going over ideas and concepts for an upcoming demo. We also talked about a lady who has small snack boxes and wants to sell things out of the snack boxes and have everything all tracked out correctly (ecommerce stuff). We talked about some ideas and what not.

Working with Bryan. We jumped in and reviewed some notes from yesterday and started to make some changes and do some light fixing of pages and flow. This is all dealing with online scheduling of unique events (like concerts, tournaments, and training events). We were changing info on settings, refreshing images, small bug fixes, and helping the tie-ins (auto flex grid tie-ins) run smoother. We also looked at some custom paperwork options and other needs that may be wanted. Good work session. Pushed up new code.

Meeting with Bryan to go over plans for a demo with a company that wants to book and track golf tournaments. We took some notes and then started working on some images and settings out in ecommerce. We ran into a few snags, fixed a few things, and made a list of other things to check out. Some of these pieces were done back in 2022 and haven't been used since then. They just need a little bit of dust to be wiped off. Most of these were for the unique event scheduling pieces from ecommerce (concerts, tournaments, meetings, training events, etc.).

Phone call with Bryan. Going over some plans for setting up a demo site for a golf tournament and helping with registrations and team sign-ups. Emails and pushing out some possible demo dates for the client.

Quick phone call with Bryan to go over options for filling out custom paperwork online and then tying that form or document to the correct customer record. We talked about what we did for the travel agency and the gun shooting range with their waivers and custom paperwork. Small overview of the process. He had another potential client that needed something similar. I told him that we have done that but most of that custom paperwork stuff is custom. We can upload and tie things into customer records out of the box, but filling out forms and then tying things together is custom.

Emails and recording notes from 3/24/25.

Also, spent some time reworking some of the content and verbiage on the adilas investment opportunities and options page.

As a side note, I wanted to record two other wish list items from some of our guys. Bryan Dayton has been asking about a feature that would take a PO and virtually convert itself into an invoice for a single customer. Basically, you buy it from your vendor for a specific person or business and then need to make that outbound invoice or transaction.

Another wish request is from Sean Carlton. He is needing the ability to either duplicate a transfer invoice or create a transfer template of sorts. He has a client that needs to move product back and forth (in bulk) from a warehouse to a sub store/location for events. The same values (ish) are moved from the warehouse to the sub store/location for each event. Looking for ways to speed things up and duplicate a process, over and over again. See EOT # 11879 in the shop for some other ideas.

Meeting with Bryan to go over his new stuff for flex attributes for quotes and invoices. This also includes some new cart based code to help things pass back and forth through the shopping cart pieces. Currently, this new code is only done or existing in the classic cart, but just trying to make some steps going forward. We will expand it out to the other shopping carts later on. We spent most of the session doing a code review and making some small changes. Bryan is going to work on some of the merge conflicts and we will get back together to push it all the way up into the master branch.

Meeting with Bryan. Trying to find some old notes on where we are at on the cart (invoice and quote) flex attribute stuff. We found a few things and I passed them over to Bryan via chat messages. We then got into how to revamp and reuse pieces from elements of time to do what ActionStrategy needs (outside company that Bryan's brother owns). Just being silly, but lots of pirate level lessons... By pirate, I mean, commandeering things, using what we have to make other things, being creative, changing settings, little bits of custom code (either actual or we could show them where we would use it), etc. We had fun talking about things like use this, don't use that, maybe try this, etc. Fun session.

Networking meeting with the BNI. Took Bryan Dayton, Jonathan Dayton, and met up with Brian Mowris there at the BNI event. Talking with people and handing out business cards. After the meeting, all four of us went out to lunch together.

Meeting with Bryan Dayton and his brother Charles Dayton. Charles owns a company called ActionStrategy and they do consulting, project management, and planning for companies. We looked at his software and what it does. We then had some fun conversations about how it might look if we merged both companies together to offer more options and features for their/our users. Lot of fun, just playing around with ideas.

We, Bryan and I, then gave Charles a fun mini demo of adilas and how we use it and have used it. We put a bunch of links through the chat window for him to look at. see list below.

Web link - help.cfm?id=381&pwd=time - elements of time - general

Web link - help.cfm?id=383&pwd=template - time templates

Web link - help.cfm?id=391&pwd=sub - subs of time

Web link - sales-gallery/bf-calendar.html - calendar and scheduling overview

Web link - sales-gallery/cc-vision.html - where are we headed

Web link - help.cfm?id=323&pwd=flex - flex grid options - custom out of the box

Towards the end, we did a small mini consulting session with Charles. He was telling us what he has and what would be required. We took some notes and then showed him how we could do that inside of adilas. Lots of talking and drawing and even jumping into certain parts of the system to show him what the existing interface looks like. Fun little brainstorming session.

Email with some instructions for josh and how to access the Knox report (link to a small 7 minute video on the Knox report). Recording notes from this morning. Then working on the quick cart line discount stuff for touch screens and the mini scan cart.

Started to build out the first round of new price and discount settings. Got into a number of YF tech support things. Some texts back and forth and then some small phone calls and emails. Just trying to help.

Phone call with Bryan to go over some bank automation and pulling in data through an API (plaid) for catching bank activity (expenses and deposits). Going over thoughts and ideas and possible steps.

Clean-up and pushing up some force page refreshes for the mini cart display and the mini scan cart.

Getting some video links put together for Bryan Dayton. He has a customer that was interested in seeing what we have been doing. I sure would like to get some time to help with the education side of things. We have a ton of stuff, but most of it is pretty old (or at least older - past 4-6 years). Here are some links that I sent to him.

Interview Videos - On site at Bridgerland College - Local tech college in Logan, UT - They invited me to come over and show them what we are doing.

https://www.youtube.com/watch?v=KnUp2t4Q4A4 - interview video 1 - 11 mins

https://www.youtube.com/watch?v=1QdFlRSS-TE - interview video 2 - 10 mins

https://www.youtube.com/watch?v=Xjw82g8q_8M - interview video 3 - 10 mins

https://www.youtube.com/watch?v=htM3qJjZmQU - interview video 4 - 19 mins

Main YouTube Channel - 454 videos - https://www.youtube.com/user/adilasbiz/videos

From Bryan: Rental Templates and Turn-key Adilas setup design for HostHuski

My notes: Working with Bryan on settings and how to help automate things to make a turnkey type solution. We did lots of drawings and I took a couple of notes. I passed those over to Bryan via the GoToMeeting chat stuff. Basically, it was the light steps on how to create a new corporation, set things up, and add one or more users to the new corp. Basically, just trying to figure out how much it would cost to automate some of those pieces. Just looking for some rough ideas. We came up with a $10K ish pricetag to automate those things. They can all be done manually right now, this would just make it faster and more automated.

Working with Bryan on recipes and production stuff. Messing with add/edit recipe line items. For us internally, we need to setup the sort order on the action page and/or the processing page. It was looping over the entire form scope and doing all of the line inserts in a random order. Ideally, we would like it to build the build (make the PO and the PO line items) in the same order that the recipe line items are in. That would make more sense. Anyways, I think that it would really help if we could help that out and make that smoother. Bryan and I looked at the code for a little bit. I had to jump off for another meeting.

Notes from Bryan: Turnkey Adilas setup for HostHuski

My notes: Working with Bryan. Talking about AI and SaaS (software as a service). Going over the Knox report and playing with it. There are a lot of things happening, all around us. Bryan showed me some of his work on the quote and invoice flex attributes and how they flow through the shopping cart. Talking about how to bulk create sites inside of adilas. Talking about automating the corp setup, corp-wide settings and defaults, templates, and other quick corp creation process options.

Still on with Bryan, but we switched over to some questions on recipe/builds and how to get your items all lined up. A client had some questions. Jumped on a Zoom session with Amy and Bob Tippetts from Grand Peaks Prime Meats, up in Idaho Falls. We spent some time trying to help them be willing to go in and play around and try things (use the system). We want them to write down their questions and then we will help them out. Hopefully they enjoyed the small training session.

Side note, it is crazy to see how much training can either make or break a deal. Often the system can do it, but they (the users) don't know how or what to do. It then becomes our job to help train them and help them know what to do and how best to run or deal with things. It's fun, but it does take time.

Intro to ChatGPT with Bryan. Trying to login and get setup. Their security code (2-Factor authentication stuff) to my email inbox kept timing out. Anyways, Bryan was showing me around using his account. It can really help with thinking outside the box. Bryan showed me a couple of usages that he does with ChatGPT. Things like: revising emails and email helps, summarizing data, code hints, itineraries, building business plans, sales stuff, notes and journaling, and asking it questions. Prompt it to keep refining it into what you really want. Start somewhere, then refine it. Sometimes, it (AI or ChatGPT) is great to help generate ideas that you may not think of. Asking it to change and/or alter the flavor as needed (once again, adding in the prompts). Good session.

I'm kinda slow on the AI adoption process (I'm resisting it). I know that I could use it and save time, I just haven't done it yet. This was a good intro for me.

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

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

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

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

Meeting with Bryan to go over some planning and building out a demo site with both flex attributes and flex grid tie-in (building forms and drop-downs). Spent the session actually building it out.

Emails, paying bills, internal tech support, and merged in some code for Bryan. Small change on the QuickBooks API stuff that he is working on. Pushed up files to all servers.

Working with Bryan. He was trying to setup flex grid and flex attributes for an upcoming demo. We did some planning and looking at the different pieces and what would need to go where. We were using simple notes, outlines, and even got into some table/data simulations in Microsoft Excel. Sometimes that really helps to show how the data will look and how it will be related, connected, and stored. You can even see how you would query and filter things as well. Great planning and mock-up tool.

Spent the last 15 minutes doing emails and cleaning up.

Bryan and I met for lunch. We were talking about adilas, sales, clients, research, and using ChatGPT to help us look over all our notes and help us make some plans and summaries. Bryan is going to help me with that.

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

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