Phone call with Josh. He wants some help doing developer work for potential clients. They, Josh, Cory, Steve, and Eric have been doing some fun projects. Lots of look and feel, email campaigns, and new ecommerce skins. He has some potential clients lined up, just needs to fix certain things. He was asking me where I'm at with things. I'm off the side of the bus (not with everybody else). He wants me to work with Steve and the crew on development projects that need to be done. I'm trying to do some planning and working with ChatGPT (AI) to help line out the master plan stuff. We have never had that, meaning a master plan. I'm not trying to get it, the master plan, too detailed, but we need it. I feel that it is very important. We will always have more projects and development work. To me, it's just another checkbox and/or request. We have tons of those, meaning checkboxes, done and pushed out. Just for fun, here is a link to a 50-page document, just with features inside of adilas.

It's not just planning, I'm circling back around, finishing things up, reinforcing the foundation, and refining things. I'm trying to simplify things, make it easier to understand, explore new avenues, use AI to help us get rid of the rub and/or friction. Tons of things. In sales we talk about features, advantages, and benefits. We have the feature part down... We need to circle back around and make sure that we can show the advantages and the benefits. Some of that is look and feel and some of that is flow and simplicity. Just as a sample, here is an element of time entry that shows some of what we are doing and how we can harvest these AI conversations to help show the simplicity of what we are really trying to do. See EOT # 12793 in the shop. This entry has four new documents that are super easy to read, yet tell a huge amount of what we do and offer. We are working on graphics, help files, documentation, etc. We tend to go so quickly, that we don't put the finish on it.

One of the biggest things that people complain about is what it looks like (look and feel of the UI). We have great tech and functionality. We need to circle around and put that finish on our product that people are looking for. I love it, and I totally see it. There is nothing wrong with what he, Josh, is asking. I also know that it takes major resources to do all of that. I really want to see if we can get some investors to help us with some gas money, help us along the path. We have put every extra cent into this project that we could and/or can. That is awesome, but it is also taxing.

Josh recommended that I call Steve and see what he needs help with. I just know if I do that, I'm back in the mix of going a million miles an hour without a plan. We joke about it, but there is some reality to the situation, we are hanging on the car or train as it is going down the road and/or train tracks. We are working on it while it is going, making corners, going up/down hills, etc. In real life, the plan is - just follow the money, but then it never ends and you don't know where you are going. It starts getting complicated. Everything has to keep going and connect to tell the story. I really feel like me not being on the train is important right now. I don't know the timing of everything. We'll get it all figured out.

After we got done talking, it took me a couple of hours to get back on level ground. I think that I have some mental anxiety about where things are at right now and where things are going. I've been in this battle (the adilas project) for 20+ years. I've been burned out and reanimated a number of times. It's a repeating cycle. It has been pretty stressful. I really want to see it succeed, but the current demands are saying, jump right back in at full speed. I need to be on the outside right now, if for nothing else, for my mental wellbeing. I'm working on other parts of the system. There will be great ROI (return on investment) of what I am doing, it just may not be super visible right now. I know that it is going to help.

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.

Back working on Cory's little deposit status tool. Also made some small CSS fixes to force a minimum size for text fields. We had some users that were squishing the screen sizes down so low you couldn't read anything. Now, most of the form fields have a minimum size and it won't go below that. Changed quite a few files. Pushed up new code.

Small fixes for Shari O. on some payroll forms. Looked around, sent off a text to Shari O. I might need her help. The fix deals with an alignment issue and I don't have the originals. She wants me to move some of the form fields around for perfect printing but I'm not sure how much to move them.

Started working on a small piece for Cory. She needs a special bulk deposit status clean-up tool.

Meeting with Cory. Going over some questions on vendor credits (special accounts). Talking about the balance sheet and how those vendor credits are tracked. She then had a small list of things that need to be changed. Light tech support stuff. She also requested a couple of code changes to some pages and new custom tools to help make her job easier.

Emails. Small bug fix for a client. Pushed up new code and sent a small email to let them know that the new file was up and live. Emails and text messages with Cory to setup some work session times for later in the week.

Small CSS fixes for Cory. Fixing some of the production stuff. Had to go in and force the field size widths and make some CSS changes.

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.

Emails, paying bills, reviewing notes from over the weekend. Planning for a meeting with Steve. Reread some great poems that have a great message. Click this link to see the poems (on a different entry from a couple of years ago). Pushing up videos to a new folder inside of google drive.

Translating from post-it notes on 1/11/26

- Sunday morning - I was shaving, getting ready for church. I had a flood of ideas come into my head.

- We go for it on 4th down (football analogy)

- Reinforce the team - goal 1

- Goal 2 - We make sure that keeps working (meaning goal 1)

- Morning meeting at 9:30 am (get some communication stuff going on)

- Let people (our team) run... minimal on the micromanagement

- We focus on people... there will always be more projects and features

- CSS on forms for classic looking forms in the snow owl theme

- Look and feel to snow owl - help fix internal and existing pages look good

- Training - could be internal training, AI training, or external training

- Presentation Gallery - Keep pushing on that project

- Images for the adilas lite plan and the investment opportunities

- Abby - Talk to Steve about getting her involved

- Work with the design team - Chuck, Piper, Sarah

- Move key videos to Google Drive vs on the content server. It just can't serve them up quick enough.

- On the AI Agent - Use what we have - Set it up so that it tells people "I'm good at nav" - Polish the 350 existing prompts and tools.

- Suzi - Step-by-steps - small documents with information and instructions. She is really good at that.

- Sean and Cory - General Training

- Prepare for 100+ new accounts - What would that take?

- Open things up!!!

- If needed, we have others who can help - Dustin, Eric, and John. There are others as well.

- Shannon - She has been such a great helper to me

- Let Alan lead out - Help him succeed. He can do so much more than code.

- Get out of the way

- Leverage debt - put all of the adilas shop or adilas lite stuff into adilas as real payables - bring it out of hiding - true costs and costing

- Co-owner Advocate - possible new title, if needed

- Mini bank accounts for each person and/or department - help the team feel safe, supported, and funded

- Be in someone's corner - believe in them

- Overcoming fear - Satan wants us to run and hide

- Simple 1-pagers (one-pagers) - at a glance

Helping cory fix a bug with my cart favorites. We did a simple reverse if statement and it went back to what it was. We will get with the developer and help them refix things and then relaunch the code. In the meantime, it is back to how it was and people can use it. My cart favorites is short for my cart favorite buttons (custom POS buttons with special functionality built-in all controlled by settings).

Working with Steve and Cory on some harvesting and production stuff. Small changes on some pages. We also had to go in and remove some older pagination stuff for one of the processing pages. It was stuck on the older version and couldn't handle numbers above 2,000 plants at a time. The new code allows for whatever number is needed. After we finished, we briefly spoke about possible other options to queue up bigger batches to help ease the page and server load.

Stuff for Cory. We had a report of some errors when adding things that had flex attributes (PO's, customers, and elements of time). We made some quick fixes and then pushed up code. Wayne was on the Zoom meeting with Cory and Steve and he was able to give me page names and lines where errors occurred. He was looking at some paper trail audit reports. We fixed a few files and pushed up new code. That small fix it session went pretty slick. Basically, a small on the fly bug fix - Wayne was telling me where to go, I was fixing , and Cory was testing.

Multiple sessions throughout the day, all working on the AI agent launch. We are just a day or so out from the live launch. Here are a few of the things that I was working on today.

- Doing some planning for the day. We have a bunch of things planned to help with the AI agent roll out. Sat down at the table, away from the computer, and wrote out about three pages of notes. If I go right to the computer, I get an idea and just want to do it. Sometimes, it really helps to step away from the computer to do some planning.

- Started coding by adding in a new user level on/off switch for using the AI agent at the personal settings level. Tied that mini switch clear down to the login level of the application. Cascading code throughout the system to match the new setting.

- Working on bulk flipping the AI agent on for all corps. Tightened up the mini API to specifically look for the Nxtlinq web id to see if access is allowed or not. Read through a draft copy of a new entry from Cory for a news and update on the AI agent inside of adilas.

- More planning for a bulk update to help turn the AI agent on for each corporation and get the correct API sockets turned on as well.

- Checking code and then cascading database changes to all servers. Running updates to add the new user level setting for show/hide for the AI agent. Pushed up a couple of files and did some light testing on data 0.

Working on some PO chaining and linking for Cory. Using flex grid tie-ins and reflexive flex grid tie-ins (going from main or parent to child tie-in - both directions). This is a sub part of the partial PO project. Added new code, did some testing, pushed up new changes. Small tweak to the help file. Sent Cory an email letting her know.

Cory and I flipped over to do some clean-up for a client. We looked into an old bulk tool for cleaning up deposits (invoice payments that need to be deposited). Had to make a small fix on that but got it working. Then we reviewed some questions about vendor credits, vendor commissions, and how to distribute those vendor commissions and track what was given and to whom (payee/users who get the commissions). Talking about some backend accounting options. Talking about different ways to track things.

Working with cory. Looking at flow for the partial PO project. Talking about what to push live first. We may end up breaking the project into smaller parts and pieces. Bulk edit and bulk flipping PO line items. Auto filling in some sub inventory stuff, where possible.

Getting back into the partial PO project. Re-reading some of the plans and looking into what it will take to get this going. Keep getting pulled off of the main project by the need to fix some stuff on sub inventory. There is a big pull there and has been for years. Anyways, went on a walk and tried to iron thing out and figure out a plan of attack. Recording some new notes and ideas on the project. More reviewing the project notes. Sent a text to Cory asking to meet with her to see the functional side of the partial PO project.

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

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

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

Going over the plan for receiving partial PO's

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

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

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

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

Recording notes from yesterday and today.

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

Prep work to get a video ready for showing the new feature for the vendor credits functionality that we just launched. Made a quick outline, did some practice, and then made a number of videos and pushed them up live. Sent an email to Cory and Steve to show the new features. See attached for the video links.

Small fixes for Sean and Cory on the mini scan cart. They had sent me an email asking for a few small tweaks and changes. Added code to dynamically hide the "on account" checkout button based on money type selection and settings. This just makes it a little tighter. The other request was looking into the formatting of prices and discounted prices for line items in the mini scan cart. Added code to check the corp-wide settings for the number of decimal places. The corporations/users are able to select up to five decimal points of accuracy. Did some testing and pushed up new files to all servers.

Meeting with Cory and Steve. Quick review of my projects. Then on to some questions that Steve had with the adilas API sockets. We went over some internal pieces and how things work outside in the web/API realm. Good conversation. He is connecting the pieces and helping some outside developers get connected to the API. One of the companies that he is working with are some AI agents that are building voice activated POS systems.

Checking out the online ordering process for booking a reoccurring event (online scheduling). Looked at code, data, and sent an email report back to Cory and a client who had some questions.

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 Cory. Fixing some inventory issues for a client. They had setup a PO with sub inventory (normal). They then used up all of the sub inventory and months later, removed the PO line items (where it started). We had to go back in and un-remove it (if that is a word). Small data clean-up. This was years ago, that these actions were taken (back in 2023). Sometimes it gets kinda crazy.

Law of deferring to something that has more info (postpone action/judgement or let something else take control temporarily). Talking about the balance sheet and the P&L (profit and loss or income statement). We were conceptionally talking about some deeper accounting and deferring (delaying) of certain things.

We spent some time showing Cory and Steve progress on the vendor credit project. It should be finished up by the end of the week. We then flipped over and were talking about how the internal adilas API was structured and created. I was showing Steve and Cory was doing stuff in the background. Lots of drawing and showing flow. Hopefully it helped.

Going back to the law of deferring. I looked it up and it said - The term "deferring" means to postpone or delay an action or decision to a later time. It often implies allowing someone else to make a choice or follow their decision, as in "deferring to someone else's wishes". In various contexts, such as finance, it can refer to delaying payments or actions for potential future benefits. Overall, deferring suggests a temporary suspension of action rather than a permanent decision.

We tend to defer to the object or piece of data that holds the most information or has the best value. It all plays in, we just give certain pieces more precedence than other parts or pieces. That's how we fold the whole thing together into a working system.

Added the mini question mark icon for the settings dialog box to the mini scan cart. Sent an email out to the others. This was requested by Steve and Cory in our earlier meeting today.

Meeting with Cory and Steve. Going over progress on the vendor credit project. Cory is trying to help and is managing expectations with the clients. That really helps. We flipped over to some needs on the shopping cart side. Steve is working on a number of new settings. He is working on some new ecommerce settings. After the meeting, I started looking into adding standard settings into the new shopping cart.

Small fixes and checks after a meeting with Steve and Cory. Working on the pay PO page and the display for the payables homepage. Showing vendor credits with other totals at the top of the page.

Small internal tech support things with Cory - time card clean-up and helping with payroll and commissions. Talking with Steve about AI integrations and new settings and filters on the fulfillment pages.

Meeting with Steve and Cory. The whole meeting was a little bit over an hour. The first 45 mins were spent reviewing where we are at on partial PO and vendor credits project. I showed them some of the pages and code. We went through a few different scenarios and what not. I took a few notes on places that still need some loving. Making good progress. We should have this vendor credit portion done by the end of June.

Meeting with Steve and Cory. We stared out by doing a recap of our plan and going over a number of scenarios. I got some questions answered. They want us to hyperfocus on the MVP and go from there. Anything extra, needs to sit on the side. We may end up circling back around. We talked about voids and limiting those options (making things go away after other transactions or sub cause and effect processes have taken place). Some of those interconnected processes can get super crazy if too many things start interconnecting and then you void something. We spent some time and went over vendor credits (new project) and how all of that will work out and play through. We had some great conversations, and I got a bunch of questions answered. I'm ready to start building.

Meeting with Cory. Quick fix. We had to alter the default expense types for an employee. They had set it to a value that didn't exist and were getting a small error. We made the fix, and they were good to go (simple user error).

Working with Cory. She had a list of things to go over and check on. Small data clean-up for a client. Checking on a few removed line items (from a PO) and their subs. Looking things up in the database.

Spent the whole last part of the meeting talking about mental challenges (mine) and how to overcome those things. Topics included burnout, more and more projects, unknown finish lines, demands, payments, etc. Small venting and meltdown session. Sorry Cory! :)

Quick meeting with Cory. Touching base on projects and such. We did some backend checking of settings and what pieces control what outcomes. We then did some database look-ups to see if we could see anything in the client's data. They are using adilas to hold and control the data and then using an outside 3rd party to show and display that data (API stuff).

Emails and fixing a voided PO for a client. They, the client, wanted it un-voided so we did it and added some history notes to the system. This was a small fix for Cory and one of her clients.

Meeting with Cory. We were going over the project for the partial PO's and the PO receiving process. Going for MVP on this one. One of our goals is to build new features and functionality without breaking things (has to be safe for everybody). Cory wants to see a plan. The backend accounting piece will be the tricky part.

Meeting with Cory. Looking at a possible bug with some sub inventory tracking for a client. This was from way back in 2022 and dealing with auto transfers (custom manufacturing code). We spent some time looking at visibility for sub inventory. Lots of backend searching. Everything was looking pretty good. We ended up doing some light database changes and updates behind the scenes. Cory would look-up possible id numbers or values in question (once again, from back in 2022 - a two-day time period). I would search for them in the background and bring up raw data. If there was a problem, we would fix it and move on. Multi-hour session. We got it all fixed.

Meeting with Cory. Checking on an API socket connection for a client. We ran a couple of connections and did some testing. They were missing a setting for ecommerce transactions and showing parts/items on the web. We then switched over to the new federal withholdings and calculations. We pulled up the percentage methods and took some time to look at tables, values, formulas, and ran a number of hypothetical calculations. Light talks about other projects that are either in the works or coming up.

Recording notes from yesterday. Phone call with Cory to go over projects, priorities, and plans.

Meeting with Steve and Cory. Going over budgets and funding stuff. Looking for ROI (return on investment). Talking about spending money on different people and things. It's getting rough.

Steve had to jump on another call. Just Cory and I talking... talking about payroll and other projects. Cory was asking me to say "no" to other people who were asking for my time or attention and take care of the priorities that really need to be done first. How much it really takes to get things over the finish line. So many things come down to a simple setting, yes/no, do this, do that, work this way or whatever. It can get tricky.

Steve joined us again and we jumped back on to budgets. Talking about price increases, reoccurring revenue, etc. Talking about efficiency and getting more ROI. Talking about how much it takes to get a client fully onboard and fully happy and rolling (paying and happy). Talking about how to bring more revenue in. Thinking about the long game. We are being scrappy and doing a lot of bootstrapping (creative ways to make things happen).

Alan joined the meeting, and we were talking about his needs and where we are at. Everybody is running out of options. More budget talking.

Emails. Back on the CSV upload with mapping options for parts and items. Added the upload code and did some light testing. Pushed file up to all servers. Sent out an email to Sean and Cory to let them know how to use it. After that, I paid a few bills and cut a couple of checks for Cody and me from inside of adilas. Quick phone call with Sean to go over the new tool.

Meeting with Cory and going over her short list of to do list items. We went over a small quote and touched base on all of the other projects that are needed right now (once again, just the short list).

Meeting with Cory and going over needs and projects. We talked about the new Texas 130-U form (title and registration stuff for Texas stock/units and trailers), getting a report of gift cards and current values, using the classic homepage as a click through (behind the scenes) option, and other needs. We spent a little bit of time looking into a possible disconnect on the advanced time search form. We may have to go in and look a little bit deeper.

The other thing that we talked about was PO backorders and partially receiving PO line items vs receiving the whole PO. This is a request from a client that is doing a lot of just in time manufacturing and needs to know what is still on the incoming side of the backorders. Cory and I will be doing some planning and prep stuff next week to line out this project and give them a quote/estimate.

Clock in/out issue that Cory sent to me. Quick backend database change. Texted cory that it was fixed.

Meeting with Russell. Working with Russell to bring in small pieces of the layout that we made in Adobe XD. Building the form, the toggle to show hide the other part of the form, and working on custom CSS (cascading style sheets - layout and view code stuff).

Meeting with Wayne and Alan to go over options for database configuration options (code words... datasource project or bus to motorcycle or world building project). Light catch-up. Wayne was going over options for running a base service to figure out the corp and datasource (what database to use). The old datasource is the default.

Talking about efficiency and combining corporations and servers. Going over scenarios. The idea is to make the code and the schema unaware (more open - able to connect to any database). For me, I have a bunch of older notes under clustering, solar systems, and galaxies (all kinds of cross-schema options).

For us, internally, database updates may get more crazy, especially for our developers. Talking about possible load balancing stuff. We were talking about master databases, sub databases, and efficiency questions.

- Wayne was recommending a more company related approach (which businesses are connected or have a relationship) vs corp related (single worlds, all by themselves). Widen it out a bit.

- Wayne's branch... WLA/DynamicDSN

- Alan was talking about a wish list to help update things from one spot (one page or one server) vs logging into each server to run it on each server (current process).

- Wayne already uses a script (test script) to run his database updates. He doesn't like to do things over and over again. He would rather build a script or make a tool to do that.

- Wayne wants Alan and I to help pitch it to Steve and Cory.

- We may need to look at and check the edge cases (on the datasource look-up project). They were talking about some known caching issues.

- Places that we need to check... (list of us, internally)
>> shop folder - there is some session stuff but it is different then the top_secret stuff.
>> web folder - API's - most pass in a corp key that we can figure out a corp id number from.
>> public folder - hardcoded per page or FORM or URL scoped controlled.
>> temp folder - hardcoded per page or FORM or URL scoped controlled.
>> database_updates folder - may need to query (get all known datasources), then loop and do updates per schema. basically, layer and nest things vs just plain doing a single update.
>> check the process to create a new corp - some questions there (we are currently using the main datasource and building tables and inputting values based on our create new corp routines).
>> caching - check the daos, services, and cfc's - make sure we do what we need to here to make this still function correctly.
>> search for corp_id IN (? whatever the list or arguments are) - multi corp queries. Maybe be able to set a temporary master/primary corp id where needed.

Working on populating new code for 2024 tax year 1099's and W-2's. Spent a bunch of time in Adobe Acrobat editing forms, creating form fields, testing tab orders, alignment, and previewing data and data overlays. Also went into some of the backend logic and did some small tweaks and updates. Pushed up new code and new forms to all servers. Let Shari O. and Cory know that new forms were up and live.

Phone call with Shari O. going over MMLLC ownership and new member options. Phone call with Cory to talk about orders and PO based back-orders (inbound order status stuff). Light research on MMLLC's (multi member LLC's) and options for gifting percent ownership.

Meeting with Cory over a Zoom session. There are two reports that are giving different information. Looking deeper into the reports and which items are not matching up. Lots of deep diving and looking under the covers. We were running raw queries against servers and databases. Really trying to figure out dates and values. We have to circle back around and re-write some logic on the sub inventory reports.

Fixing some flex attributes and their data for a company on data 10. They have six corps, and all need the fix. Basically, they setup a flex attribute as a text value, now they want to convert that to a date/time stamp (physical database change). Built a custom tool and ran it on all corps that needed to be flipped (converted between the different data types). Let Cory know that we got it done.

On a Zoom session with Cory. Fixing some deposits for a client. Emails. Meeting with John Maestas (old adilas developer). We were talking about the state of the union type discussion. Basically, where are things at and who is doing what, inside of adilas. Just catching up a bit. After that, more emails and recording notes from 1/8/25 to 1/13/25.

Various meetings, throughout the day.

On a Zoom meeting with Cory. Looking over some gram control settings.

On a meeting with Cody. He got a few things tweaked for the check write stuff. Looking at pagination on the label builder. He was also showing me some work that he was doing on the infinite scroll (scroll, get more results, scroll, get more results, repeat until finished).

Working with Steve. Debugging things. Found problem with list contains vs list find functions. Pushed up the new file.

Emails and reading over a response from Chuck about a custom website.

Meeting with Cory over a Zoom session. Light tech support. She was helping another client with some Metrc issues. Touching base on other projects. Flex attribute questions. Tips and accounting for tips. Then lastly, we talked about a client's need for some automated emails and reports. She is going to send me some emails with the different needs and projects, so that we can track things and get them done. Nothing was hugely on fire, just some - it would be nice - updates and changes.

Phone call with Cory. We need to do the end of year payroll stuff. We talked about some other projects. Touching base and making some plans. I then spent some time looking into an error with PO flex attributes. Cory sent me over a small bug report and I started to look at it.

Emails and recording notes. Looking into a small sub inventory error. Sent off some versioning information to a client that is getting audited. Fixing a series of small errors and bugs. Cory and Sean were sending me things and I was fixing them. Pushed up new changes and sent out emails to update Sean and Cory.

Looking at bank check print settings for a client. Phone call with a client. Jumped on a quick Zoom meeting with Cory to go over some payroll questions for Stone's Trailers.

Multi hour Zoom meeting between Sean, Cory, and Brandon. We went over an email sent to us by the Canada company and went line by line over the email and made a bunch of notes. Brandon has a copy of those notes and they were also sent to some key adilas players.

Meeting prep. As the meeting got started, we had Sean, Cory, Alan, Steve, and I on the meeting. Here are some of my notes: Kinda all over the place.

- Sean has set up the logins for the new users up in Canada.

- Looking at what it will take to come up with an MVP (minimal viable product).

- Steve bought some new hardware. He will be playing with it and getting it all wired up and configured.

- How do we keep pushing the ball down the road?

- Setting up limits. We want to play but don't want to get ran over.

- Going over a list of to do items.

- Steve really chimed in on where he thinks that we are at. He really took the ball and ran with it today.

- Risk vs Reward - We spent quite a bit of time going over options.

- Steve is excited about the number of items that the Canada company has. It's really pretty small.

- Number of locations - lots of potential there

- Steve was talking about a book - "The Art of War." - Making deals and business stuff.

- Show what we have done - clover integration - $23K, features, advantages, and benefits, list out an MVP, show a percentage of what we have to still do, things that are not on the list... wishes, future desires, tablets - online orders and delivery, website, ecommerce, we do the POS software. We can help with hardware but that's not our specialty.

- We have some depth - adilas - operations and accounting

- Look at what we can help them with...

- Mission statement - help your business succeed

- Could be some scale problems as we go along

- Promises made and expectations

- Deployments - it can get dicey (interesting)

- We have... list it out - we have a solution

- Get them talking and thinking about something else - distract them what they are worried about - sometimes, what someone is worried about, they are not as big of thing as you think. However, if all you ever do is just think about that one thing, it can change your focus. You aren't taking in the whole picture. Get them seeing the whole or bigger picture.

- Hardware - pros and cons - come up with a valid solution and then allow them to choose, buy, or configure their own system

- We can see our way through a bunch of things - looking down the road

- We can setup corps... we haven't really done much mirroring of corps and settings

- Alan - Sunk costs, new costs, and building going forward

- Alan - Getting direction (where are we going as a company?) - He likes where we are going

- Cory - He (Aaron - owner) needs to invest in us. Money and time - how long will it take and what do we need to still build out?

- Steve and Cory going back and forth - nice little volley back and forth - risk and reward stuff.

- We want Eric to ask for his other stores to be on adilas. Eric is a store owner.

- Alan - Once they are up and running, they may not need more right away

- Steve - We can build anything... there is a line or an end zone - a goal is in sight

- Goal - What will it take to get this thing to launch?

- Alan - Questions about customer support and server up time

- Alan - Other possible services - customer support, training, etc.

- Alan - They are trying to see how serious we are? Almost a test on us

- Alan - We get our hardware stuff up and running and we show that we have a solution

- Steve - Give us a list and we'll cross it off

- Steve - Like a game of football - How much time is left in the game and what are our plans?

- Steve - Pushing this company further down the road

- Steve - This could be our golden ticket - Let's punch it!

- Alan - If we don't do this, then what? Let's use our current team and get it done.

- Alan - this is not vaporware... this is right here in front of us

- Steve - They could be the last client that we ever need

- Helping them see the future and wanting to stay with us

- Steve - What about global ecommerce stuff and then locations where people could pick things up

- Steve - They, are looking for us... they hate some of the competition

- Cory - We may need to fake it (customers, gift cards, and loyalty points) - We have all of those pieces, they are just at the corp and cross-corp levels. Not at the enterprise level yet. If needed, we could just have them run per corp until we get the other pieces. That's our fall back.

- Alan - Just noting that we only have some data (not all of the locations). If needed, we could do it per location

- Cory - Wanting to setup some action items

- Steve - Wants to start a list, send it around, tout our horn, and show who is doing what

- Steve - Assume the sale

- This is a test

- If you are going to fake it until you make it, you need to pretend that it really works and it already exists - smoke and mirrors. We've been at this for over 20 years. There really is a lot there.

- Alan - We can't over promise - stick to the basics

- Steve - We are working on... Steve-hardware, Alan-enterprise, and Brandon-reporting

- Communication - short and sweet but keep it moving

- Steve - Asking about customers... direct vs enterprise

- Sean - On new customers, they just need a few fields... such as: first name, last name, email, cell phone

- Alan - Let's do the customers and gift cards at the corp level - We'll clean-up later

- Steve - He is planning on using one printer to handle both receipts and cup labels - sticky receipt paper

- Steve will work with josh a bit to help with direction

- Alan - Enterprise is a value add-on piece. We need to figure out the pricing structure there.

- Alan - We will gain some momentum as we keep doing the enterprise stuff - this is where we are heading.

- Alan - We add a lot to adilas but we never up our prices - We need to manage that better to recoup or get ROI - Dynamic billing

- Steve - no Metrc (statewide compliance system), under 100 items, not even tracking inventory yet - Let's do this thing!

- Sean - On ecommerce, they aren't really tracking inventory, they just need to use their menu and go for it.

- Steve - simple on what they need, scale on the reporting and needs - here we go

- We are figuring out where we are going... Okay, let's go!

Meeting with Cory. Going over balance sheet items and questions. Costs on unlimited items, PO payments, paying things over and under, and payee corps. Talking about other projects and needs.

Phone call with Sean to go over some things for a client.

I was driving home from the Colorado and Canda trip. I pulled over at a gas station and jumped on the call. Everyone else was on the GoToMeeting session. Here are the notes that Cory took. Thanks Cory!

Hi Brandon-

Here are my notes- messy!

- They could use some more training

- They were asking for Customers and Loyalty points (Data had issues)

- They want enterprise reports (they don’t even have two corps to see)

- They brainstormed a list of what is needed

- 3 month trial

- Also interested in another software- Snappy PC

- Fight against loyalty points and gift cards

Question:

Are they using adilas since you left?

What are their expectations?

- Very strict culture

- They think enterprise is bigger than it is

- Dashboard with FranPOS- they don’t like it

- **Steve wants to know what the MVP is for them

- Brandon said it will take a few hours to come up with that

- Brandon said he will send them an email letting them know Sean is their point of contact and that we met and are coming up with an MVP.

- We need to let them know we have already invested 150K and we need to get a commitment from them.

- Phillip likes the customization but is leery about some of the processes.

- Example- When you add a new item and how to add a new button- this is so much work! All of this can be sped up. Buttons are not required, but they like them.

- They add new items quarterly so that will be some work for them.

- Takeaway: Need to have buttons on the enterprise level in order to roll these systems out

- We need to decide where we draw the line: the code is done, the rest is custom.

- We may need to have Josh tell him this

Up helping with the Yogen Fruz deployment with Sean up in Tronto, Canada.

Here are some notes and recap:

Sunday - 10/27/24 - Drove to Colorado. Needed to get a passport and Utah didn't have a passport agency place.

Monday - 10/28/24 - Spent the day in Denver getting my passport. Had to go back to the passport agency a couple of times. One for the initial appointment and another time to pick it up and verify information. While waiting, did some research on my cart favorite buttons, smart groups, tiered pricing and rules and assignments for the smart group buttons. Met up with my brother for dinner.

Tuesday - 10/29/24 - Went to the Denver temple in the morning. Spent some time playing around with Affinity Designer and learning how to control color and saturation levels. Graphic stuff. Drove to Salida, CO. Met up with Steve at his house. We chatted about some upcoming projects and challenges. I really liked his house. He had redone some rooms, cabinets, counters, rest rooms, and such. Super cool! Craig came over and gave me a bunch of adilas checks. We talked about goals and ideas for the Canada trip and venture. After that, I met up with Mrs. Shari O. up in Buena Vista, Colorado and we had dinner together. Great time and fun chatting. I then got to go see Shari O.'s house and dogs. Super cute. Visited my friend Andy Maupin and then drove up to Denver.

Wednesday - 10/30/24 - Slept in my car in the airport parking garage - fun! Flew up to Canada and Sean picked me up in Tronto. We went to the hotel, got settled in and got some dinner. After dinner, we went and found a store to get some snacks and other food for the week.

Thursday - 10/31/24 - Trick or treat... We got tricked... :) We went to headquarters and met with some of their team. We got there at 9:30 am in the morning. We didn't leave until after 12:30 am, that night. Super long and stressful day. Tons of hardware issues. They wanted us to fully configure the old FranPOS units (7 year old Android tables with a locked software system installed). We were attempting to run adilas (web-based system on that unit). The browser part worked great (normal adilas stuff). The ability to interface with the peripherals and hardware were crazy tough. We couldn't get anything to work. Totally beating our heads against the wall. Trying all kinds of stuff. We did have some help from one of their team members (Harsha) and that was about it. At one point, it looked like that was the end... The main boss on their team was saying, it doesn't look like we will be able to deploy this software. Sean and I asked for leave to go to the computer store and purchase some things that we knew would work (new hardware). We were also somewhat waiting on another one of their team members who hadn't come in yet. He was a tech savvy guy who had been able to hack the locked code on the FranPOS on the last visit from Suzi from the adilas team. Without going into crazy details. We got some new hardware and started setting it up. We were also blessed and the other IT guy (George) from their company came and was able to get some things going through on the older hardware. Pretty stressful day.

Friday - 11/1/24 - Went to the mall (Square One mall in Tronto) to help get the system up live for the client. We were needing some help from the IT guy. He was a little bit late, we had it mostly running before he came. He put the icing on the cake and made it work. In the meantime, I ended up recoding some of the my cart favorite buttons, making them bigger, and styling the mini invoice (customer receipt) format. Sean was doing some training and by mid way through the day, it was going super smooth. If it wasn't for the hardware issues, we could have been in and out in just a few hours. Anyways, good day and they seemed to like the system. Answering random questions here and there. By the end of the day, they had done over 150 invoices (sales tickets) through the system.

Saturday - 11/2/24 - Went back to the store (Square One) to help out and see if they had any questions. Had lunch with the owner (Eric), great guy. I spent most of the day fixing small little things to help with flow and settings. Fixed a few information messages and added a new setting to control the auto print option for the mini invoice. Good day.

Sunday - 11/3/24 - Woke up early to update all of the time zones on the servers (daylight savings stuff). Sean and I went to church and then did some site seeing (Niagra Falls and such).

Monday - 11/4/24 - Back to headquarters. Worked on uploading customers. Sean was helping and doing some training. We spent some time and put together a small email with a list of to do items. We then had a meeting with some of their team to go over the email and to do list. That was really good. I met with a couple of people and setup some new accounts for some of the accounting people. Towards the end of the day, I got a chance to chat with the main operations boss (Phillip). I enjoyed that. Trying to show him what we do and how we do things. He has a lot of things going on.

Tuesday - 11/5/24 - Sean dropped me off at headquarters and I worked there all day. He took the rental car back and flew home. I spent most of the morning working on loyalty points and getting data entered into the system. Various questions, different sessions, etc. Towards the end of the day, I did some group training for four of the main people (Phillip, Rex, George, and Harsha). I thought it went good, hopefully they enjoyed it. There is a lot to cover. At the end of the day, I found a good spot to stop and did some light planning. One of the guys gave me a ride home (Rex). He was pretty cool! Just being silly but I got back to the hotel and said, "I'm alive!". I was super happy. We still have some things flapping in the wind but nothing that we can't tie up and/or fix. All in all, I was pretty happy.

Wednesday - 11/6/24 - Took a cab to the airport and got all checked in. I spent some time going over emails and what not. I hadn't checked them too much for the past week or so. Somewhat behind. Flew home and drove from Denver to Grand Junction, Colorado.

Thursday - 11/7/24 - Drove home from Grand Junction, Colorado to Logan, Utah. Stopped along the way and had a 2 hour phone call meeting with the adilas team (Steve, Alan, Cory, Sean, and I). Had a little car trouble but got home safe. What a trip!

Phone call with cory to go over item imports for a client. We actually called back and forth a couple of time to make sure we were on the same page. This is basically, a custom data upload for a client. This new upload will load an enterprise system and then the enterprise system will push content down to smaller transactional corporations on the same server. Conditioning and setting up a new custom upload page. Did some local testing and then pushed up live. Sent an email with some instructions.

Phone call with Cory. Going over projects, priorities, updates, and a couple of small bugs.

Meeting with Steve and Alan. Going over budgets, pay offs, timing, talking about the approach, don't talk about positions, pitch the sale ($150 internal vs $75/hour - using some of our guys directly). Steve was and has been selling pieces of custom code to our clients. He would like help there and have the guys pitch their own services.

We spent some time talking about our identity and who and what we want to be. Taht is coming along. Here are some other general notes from our conversations (multiple topics):

- Help protect our clients...

- Set some caps on how much our developers can charge

- Communication back to the clients - weekly reports and billing

- Billing - weekly

- We can't let our developers rough up our clients

- Helping our guys succeed - plans, billing, communication, oversite, etc.

- Possible kickback - commission to adilas

- It takes so much time to crunch things up - sales or custom code - the reality of what it takes

- Can't keep pushing things over to the balance sheet (code or projects for Kelly) - it costs of too much. We pay the developers and we owe money back to Kelly.

- Consultation document or a checklist type doc

- We are generic on purpose - if you want it custom... you've got to pay to optimize it

- Setting up boundaries and being firm on that

- An add-on cost for custom work - they need to pay for it - they may need to keep paying for it (reoccurring) - maintenance

- Selling what we have

- Our development and sales focus is as a general business tool

- Elevator pitch - web based, SaaS (software as a service), we focus on operations and accounting, we have a base model, and we allow custom

- We want to be generic. We want to cover a number of industries. We want to be a great companion software for any business.

- This is who we are - defining ourselves and what we do

- Plans for our upcoming meeting with the developers - take care of business and setup another meeting where we have some plans all made up.

- The developers may have some ideas on how to make things work

- How can we get some of the cool stuff exposed to the public? Selling what we have. - sales - nobody is pushing it, our tools and features, as a product.

- Alan had the idea of using an outside marketing firm - when ready

- There is a need for marketing, education, etc.

- YouTube influencers - quick, short, and powerful mini messages - short and to the point

- Podcasts - how to run your business, tips, tricks, and best practices

- Piece work - we have tons of stuff - what if someone could harvest that kind of stuff? - YouTube, Facebook blogs, podcasts, etc.

- Alan would like to talk about the future - looking short term, medium term, long term, etc. - talking to Steve, Brandon, Shari o., Wayne, Cory, etc.

Phone call with Cory about the deli style barcodes and tightening it up a bit. Making a few small changes to help out with the actual client and what they are doing and how they are using it. Pushed up code. Recording notes from yesterday and today (9/16-9/17). Fixing some internal shopping cart messages. trying to make the style match for the new mini scan cart.

Emails. quick phone call with Cory. Making changes to some stock/unit API's inside of adilas. Added some new image helper info to the getBulkStockPhotos method. Modified two other stock/unit methods and included some other columns. Pushed up new code for testing and let the client know about the new changes.

Meeting with Steve. Responding to the problems and requests, that's what we do (just in time problem solving). Steve jumped off and I started working on implementing the new deli style barcode (complex barcodes) stuff into the mini scan cart. Before I did that, I spent some time and beefed up the sample deli style barcode tool. I also checked in with Bank of America about some funding options. Reviewing some documents from Cory on deployment practices and light budget numbers.

Zoom meeting with a client. We had Steve, Cory, Sean, and I on the meeting and two of their people. These are some small notes and request:

- On PO's, they want the part reference number added to the PO creation section (multiple pages). Basically, they want another column on a number of pages so that it flows through the PO or inbound inventory section.

- Mins and maxes per item (single quantities as well as case or box size values). They want these values to help with the ordering and re-ordering process. We talked about possible use of parent attributes. I'm not sure about that. They want those (parent attributes) to play into the mix with rules or then enforce those rules. That's the part that I'm not sure about. They want the mins and maxes (along with case sizes) to help build the PO for them.

- When receiving the PO's - they bulk flip the quantities. That works great. They would like some help with the subs or sub inventory counts on that process. Basically, a bulk flip on the subs as well.

- Remove "on account" options for counter sales - invoices where no customer is assigned.

- We did some training and drawing (scenarios) dealing with dual payments or mixed payments using multiple credit cards, cash, and gift cards - small training.

- Small demo on the deli style barcodes and how that will work. Basically, an on-the-fly barcode that has item numbers and prices encoded into the barcode. We have to split things apart and basically interpret the barcode vs just reading it and matching it up to an item in the database. You break it apart and do some reverse look-ups of sorts.

- On PO's, show current activity (per vendor for a given date range) and/or a show all items button - quick links.

- Talking about other stores going live and some possible timeframes (rough).

- Quick internal talks after the client had left the meeting - who is going to do what - tasks and projects?

- Cory and I stayed on the meeting once everyone else had gone. Going over some existing bulk pricing tools and other upcoming projects.

- One upcoming need is for a client that needs help with the adilas API settings. They are requesting new info, a few new columns to be returned, and easy access to backend data and values.

Quick meeting with Shannon. We touched base and then jumped off to work on our own projects. We will hit it again on Thursday. Emails and paying bills. Phone call with Bryan. Quick code merge for Cory - restoring quotes to cart and helping flip the invoice type. Yesterday was a holiday. Today felt like a Monday, even though it was a Tuesday. Random odds and ends.

Going over projects with Cory. Worked on a small fix for restoring quotes to cart. She has a client that wants a small change. We talked about the customer to additional vehicles project. it was on hold (paused), but we need to get it out of mothballs and start it back up. We also talked about tips and credit card transactions. We want to expand that out to other non credit card transactions (really beef it up, including tip splitting between employees/users). Lastly, we went over some ideas on request PO's and how speed up the tie-ins between the PO's, the actual received quantities, and the quantities recorded on the subs. Small work session of sorts.

Working with Bryan on payroll JavaScript math. Doing some conditional logic changes. Merged in some code and did some testing. He ended up working on a small bug and I worked on some update tools for cory and padding barcode with 0's. We got back into looking at the error and tied to find it. More working on the barcode padding with leading 0's tool. Mixed session going back and forth between my projects and his.

Server meeting with Wayne and Cory. We need to redo the barcodes and QR codes. As part of this change, we need to change out old Java libraries for Barbecue (barcode library) and iText (for PDF's and QR codes). Wayne has a new server ready for testing - data 100. We need to figure out who is going to be testing things and figuring out who is going to do what. We want a bunch of our users to jump on and use it in a different way or manner. Talking with Wayne about building some custom tags or special functions to help generate those barcodes or QR codes. That would be awesome.

Who is going to replace Wayne as the server guy for adilas. Talking about a new person who might do a good job. She just barely started working with us but Wayne is encouraged by her aptitude and skill level already.

These are just some notes for me - New project to allow quick look-ups for recipe/builds (be able to change the line items for both ingredients and output items). Be able to search for items based on RFID tag, barcodes, product names, descriptions, etc. - pass along the information so that it sticks. Cory sent me a video on this. I put it in her folder, locally, it's about 10 minutes long.

Emails, tech support, and some quick changes for Cory and Sean on an auto create sub inventory packages page (backend tool). Paying bills and recording expenses.

Data clean-up for Sean and Cory. We originally bulk populated the inventory levels (quick setup for a company). Well, we did that and now they are wanting to roll some (not all) of the pieces back. Light data clean-up. Built a small page to help with missing part or item descriptions. Fixed some data live on the data 9 server.

Small data clean-up project for Cory. She sent me an email with detailed instructions. Gave her a call to confirm and then started working on it. Had to unroll some sub inventory and changed some unlimited items to normal parents vs sub inventory items. Lots of backend database work and clean-up (query and sub query stuff). Sent them an email once everything was finished.

Emails and recording notes. Reviewing a video from Cory about some vendor stuff. The items in question were missing some item descriptions (these came from a bulk data import - original data was missing some info). Quick phone call with Cory to go over a small plan. Small phone call with Bryan. He was asking questions about doing a data import for stock/units. We talked about the need to match up makes and models to help with the import. They may end up doing the import manually as they only have about 100 stock/units. Recording notes from the last few days.

New payment type for EBT (electronic benefit transfer - modern-day government food stamps). Added it to data 0 and then cascaded it to other servers. Meeting with Eric to help with ecommerce gift card payments and other money types (payment types). We did some local testing and resolved a code conflict. After working with Eric, went back to updating servers with new money types. Let Sean and Cory know that the new payment type was up and live.

Paying bills and a couple of phone calls with Cory. She needs a new touchscreen ready interface for changing cart quantities. We had switched things out from an open entry field to a drop-down menu (imagine a list from 1 to whatever number - say 1-20 or whatever) but they need even more touch friendly options. The plan is to build a new setting to allow a touch quantity modal popup to help with quantity changes. It should look pretty good. She also needs some barcode updates for items that were entered wrong from a digital upload.

Quick fix for Cory on a bulk tool. Fixed while on the phone with her. Bryan called and had questions about stock units and how to apply internal repairs and outside repairs. We did a quick into to those pieces over the phone.

Just an observation: People (our clients and our reps and helpers) have a need for helpful training, quick access for questions, and also a need to be able to turn fields on/off and rename them as needed (speak their language). As a side note, we added a field called "external_alternate_id" to all 12 of the main player groups. We may want to expose that field for use. We knew that we were going to need it, added it to the database, but haven't fully gone through the system to expose it yet. It may be time.

The other thing that seems to be needed is the ability to turn fields on/off (show/hide) and be able to do custom naming on certain fields. We have this on a few things... We need it on all things, if possible. Help the company speak their language. That makes them more productive and better able to use the system for their needs.

Recording notes from yesterday. Working on a special create sub inventory tool for Cory. Building the logic and doing some testing. Sent an email out to Cory and Sean to let them know that the new tool exists.

Added in some clean-up for the main PO's amount for the new bulk tool for Cory. Did some testing and pushed up new code. Phone call with Cory to go over the new tool. She also had me look at a small bug on quotes and removing line items from a quote (after a restore to cart function).

Spent some time looking into an error message for updating saved quotes. The bug was dealing with the new line sorting and grouping. It was only returning valid line items. If something had been removed, it was not updating that when it went to the database. The cart was showing it correctly, it was just the save to database function that needed some help.

Other small fixes. Added line item level groupings to the review cart page (we had missed that one - back when we were doing the cart line grouping stuff). Also, small fix on the history homepage and the historical reports. Some of the links were blending in with the report header (same color). Small change to make it look better and show the drill-down links.

Building the helper tool for sub inventory for Cory. Ox in the mire (early morning on Sunday). She needs it later today and I didn't get it done. Going through the build logic - PO's, items, PO line items, and sub inventory stuff. I didn't quite get it done so I texted her. Come to find out, the project is going live next week, not later today or tomorrow. My bad.

New code for Cory and being able to auto add a sub (child inventory package) to an existing item in the database. Building a small helper tool to populate the data.

Meeting with Cory on importing inventory for a client. They are wanting a bulk tool to help with adding subs - only active items that are normal parts (not the unlimited ones). The plan is to make it into a small migration tool for Cory so that we can use it for other corporations. Email tech support with Wayne.

Meeting with Suzi and Sean over a GoToMeeting session. We were going over the adilas label builder. We have an existing piece but it needs some major upgrading. Here are some of my notes... It sounds like it's pretty painful from the user side.

- In the current label builder - on step 2... help show the width and height on the label drop-down. Also use smaller decimal.

- On step 4, the label is so small... they would love to see it bigger (zoom to scale)

- When editing, the top 5 fields need to be editable. These are the name of the field, the height, width, the _x and _y positions (where on the canvas the fields starts).

- Be able to see it while you are doing it, be able to save it while you are doing it. Currently, you have to make an edit, switch modes, then save it, then go back.

- When going from page to page, it isn't saving the new changes. You have to almost make a change, go save it, make a change, go save it. If you try to have it do too much at a time, it gets lost.

- She (Suzi) has to go back, go back, go back... very frustrating.

- She is recommending that people don't even use it. The current label creation tool is that bad. They (she and Sean) are building out the labels, showing the people, and not showing them the actual tool. They are taking on the hard part in order to save frustration.

- She has seen some demos that have really nice label building tools.

- I have a bunch of notes from past brainstorming sessions - dealing with wish lists for the adilas label builder. I also have some document on my local computer from some brainstorming sessions with Cory, talking about next steps on the label builder.

- She has also seen other tools that are really hard to work with for label building (other products). You really need a way to connect the database to the label builders.

- They are wanting full colors, static text, dynamic text, QR codes, barcodes, horizontal text, vertical text, graphics, data driven value, etc.

- Snap to grid... both yes and no options. Along with that... a nudge (using arrow keys) would be super helpful.

- Suzi was talking about how at another company, they used Adobe Illustrator (full on graphics program) to do super custom layouts.

- They need ability to do super small text (font size)

- They may even need round labels, not just square or rectangle labels.

- The current decimal level is way out there... like 10 or 20 decimal points. We just need to format things, for a visual for the end user.

- Some of our competition has some really fancy label builders. No idea on the price tag, but there are some sweet label builders out there.

- Not just simple labels... they are looking for super fancy labels... full color, full gloss, full layout options, etc.

- Suzi has a number of samples of fancy labels, if we need them as samples.

- Sean and Suzi were talking about the cost of labels - pros and cons of going with preprinted logos. It depends on what things change and how often you need the label options.

- Both Sean and Suzi have used it (the current label creation tool) but it is painful.

- The work has to stick... every time. It's way to fidgety.

- Be able to zoom in and out.

- Add a save button on the show grid layout step.

- They want to combine step 4 and 5 - do it all on one page.

- They want to be able to add a custom label size... be able to enter perfect width and height. Currently, you can pick from a bunch of single labels (presets) or a huge list of Avery sheet labels. They would like options to enter custom labels (sizes and dimensions).

- Be able to switch between inches and centimeters.

- Be able to align elements, copy elements, paste elements, etc. Easier for the end users.

- The barcode text needs to be able to scale (font size of the bars) - we need to be able to fit a 24 character barcode on a 2" label.

- Instruction and education (writing and on video) on where to access the labels - for each type - customers, invoices, PO's, and items.

- Be able to work easier with subs (parts) and sub packages (parent/child inventory).

It was going to be a meeting with Wayne and Cory but Wayne wasn't able to make it. Going over a number of needed projects. Bulk find and replace on items and vendors. Also being able to merge customer records. Small update on mini scan cart. Small show and tell to show Cory some of the new features. We are looking forward to the discount engine (next major project).

Phone call with Shari O. She had some questions and spent time going over merchant processing stuff. Meeting with Cory and Bryan (over an hour) doing a mini scan cart demo and walking through the different settings. We didn't cover all of the settings, but we did walk through a bunch of them. Cory had some great questions. This was the first time she had seen some of the new pieces.

Emails, checking on some funds that we transferred to help cover costs. Built out two new API's for Cory. They are dealing with getting sub inventory attributes for a single part category or getting all parent attributes per corporation. Created the new files, coded them, tested them, created documentation, and copied the documentation and pushed up new changes to all servers.

Tracking down an error for Cory. It was an undefined line in the variables. The error message didn't give us much to work off of. We had to dump the page line by line until we found it. I made a temporary patch job and then let Alan know.

Emails. Looking into Virginia state payroll withholdings. Made a bunch of changes. Did some testing and pushed up files. Let Cory know so that she could reach out to the client.

Meeting with Michael from Cannapages (3rd party developers). They need two new API sockets (endpoints) to help automate some of their code/buildout. Called and talked with Cory.

Sorting line items. Allowing for different sorts (manual, natural, and level 1).

Meeting with Cory. Checking on some older projects. We walked through some settings and flow to connect PO date/time flex attributes with elements of time. We did a couple practice runs. We also checked on some payroll settings for a client that wants a new state added.

More sorting line items. Allowing for the URL's (web links) to help with the sort orders (presets based on sort numbers, natural numbering, and sub line level grouping). Making good progress.

Various sessions throughout the day. Mostly working on the new code for tying in PO date/time flex attributes to elements of time. Finished recording some notes from yesterday. Working on calendar output for the flex attributes being tied to elements of time. Did some more testing. Started to look at the PO flex attribute output and showing what is connected to something (better visibility). Made a new way to tie in flex attributes with elements of time (tighter tie-in). Quick meeting with Bryan to look over progress on his project. Back working on PO page level output for tie-ins with time. Looking good. Final clean-up and pushing up files. Live testing and emailed Cory with an update.

On the meeting with Bryan - He showed me where he is at for the cart line item groupings. He is making progress and can show 1-3 groupings. He is still working with the session stuff but it is coming along. I could see great progress from yesterday. We will meet again on Monday to look a little bit deeper.

Quick meeting with Bryan on the GoToMeeting to go over his new cart line item groupings and settings. We looked around and talked about a few small changes. Making progress. We will meet up tomorrow and start integrating those new settings. Phone call with Cory to touch base and report on a project. I haven't started it yet but will jump on it next.

Looking into the void expense/receipt logic with splits (payments on account). Ended up doing a small data clean-up for one of three expenses. One had some bad data. The other two were cleaned up using existing internal void tools and logic. Sent an email off to Cory with information. The existing code seemed to be solid. Not sure what happened on the one expense/receipt. We got it all taken care of.

Phone call with Bryan going over questions about support, logging, and how we handle support tickets. We talked about some other questions as well. Quick Zoom meeting with Cory to go over a needed fix for elements of time and tying in PO's based off of flex attributes. She is going to send me more info via email with requirements and a valid login.

Looking into fixing a data issue on data 6 for Cory. She sent me an email and I started looking into it. I ended up in the "voidTicket" method for expense/receipts and looking for possible errors and adjustments that might be needed. I left off getting ready to look at live data to make sure that the void process was still fully working and would back out split payments (payments on account) correctly. Took a bunch of extra notes on where I left off.

Emails, phone calls, and touching base. Quick phone call with Cory to touch base on some plans. Spoke with Wayne on the phone for well over an hour. Some of it was just dealing with life, death, suicide (my son recently and Wayne's little brother years ago), and then talking about adilas stuff. Here are some of my notes. As a side note, Shannon helped me convert my post-it note level notes into these digital notes.

- What people see with their eyes and their perception. If you have 8 different people looking at the same product, they see 8 different products or solutions. People have such different views.

- If things are measurable then you can go to a measurable standard, but it is still perception. It's hard to have people agree on things even when you can measure it. It is even harder when you have to have people interpret concepts, principles, things that cannot be measured but have to be interpreted or understood other ways.

- We talked about change and discussed some analogies in physics. If you have a swinging bar, pendulum, how much does it take to change that? Do you have enough force to really change that momentum, to set something different in motion?

- Sometimes, Wayne really likes having peers that know what he is talking about - that is an important part of building a working community. It's important to be able to bounce things off of people that can really consult, help, and understand things. That is helpful for all people.

- God (our Heavenly Father) has plans for me (and you) - there is a plan and God continues to do His work.

- Wayne expressed that while talking with another developer that "our" way has been ingrained, it is the known norm, it is the default path - It feels to some of the developers like, "will it ever change?" What would it actually take to change?

- From this, dealing with change, Brandon was thinking, instead of just jumping into the coding side what could he change that could change the outcome? Like what if he helped plan the project instead of just took the next coding assignment? How does that change things?

- We don't want to sacrifice in the wrong way. Sometimes we are willing to sacrifice but how much more value does it make it to have the sacrifice in a way that benefits the greater goals?

- If Brandon moved more to helping plan this out what could that change? Could that help it move further down the road? Would that be an unwise or undo sacrifice?

- How do you break free of the default patterns and cycles?

Emails, fixing permissions for Cory, also a quick PDF address change on a number of custom PDF's. Recording time and notes from last week (3/26 and 3/27).

Projects for Cory. Did some PDF changes for a client. Changing state withholdings for Colorado. Checking on Oklahoma state withholdings, formulas, and table data. Recording notes from earlier in the week.

Meeting with Cory. Handing over the torch to Alan to work with the developers. Being wise about how we are spending our development money. She lined me up on a few different projects. Pretty short meeting.

Meeting with Bryan. Going over golf club (image a country club) type business options and how to use adilas to help with certain tasks. Things like scheduling tee times, tons of restaurant type needs, etc. Bryan was asking all kinds of questions. We have all of the tools, they just need to be tweaked a bit. Eventually, our meeting got into a who knows what type conversation. For example: So and so knows about this part, and so and so knows about this other part, etc. No one knows all of it. I was telling Bryan about some custom work we did for a Mexican Burrito place and how we were using ecommerce to help them place their orders with certain choices. I know that Sean and Dustin know about tons of other stuff. Alan has helped with other setups and custom code. Steve, Shari O., and Cory all know other things.

We talked about normal cart stuff, delivery, fulfillment stuff, custom webpages, and setting up custom skins or custom flow processes. I ended up doing some consulting, talking to Bryan about custom skins, and setting up a demo site. It takes effort to configure the tools. Once set up, the flow is much easier. Ideally, we would like to gather up all of the knowledge and put it in one place for use by others who want or need it.

Small little bug fix for a new shopping cart. It was erroring out on a page include (sucking in variables from another page). I made a few changes and pushed up new code. Sent an email to Steve and Cory. Recording notes from the day.

Started out doing some emails and recording some notes. Then meeting with Cory and Shari O. Looking at a small convert to PDF error on data 1. Other systems seemed to be doing fine. Just a problem on data 1. We also looked at a possible error out in statement land and math dealing with tips. Also in statement land, we had a request to apply a data filter to what was going to be on the statements based on amounts owed (paid or pending invoices).

We then spent some time looking at payroll settings and checking code on bit bucket (code differences between old and new code). We couldn't find anything that really stuck out. We then went and tried it on a play site, and it worked great. Cory is going to check the settings for the company in question. Also dealing with payroll, Cory and I jumped into a couple of state websites and pulled new tax and withholding tables and formulas for a couple of states. We need to update those values inside of adilas.

Lastly, we went over some priorities and talked about other projects. I've got the top 3 priorities written down in my notes on my computer. They are checking some older bad data for a report dealing with sub inventory, helping Bryan with the custom project to connect PO's to elements of time, and updating some state withholding formulas. We also know that a custom data import is coming towards the end of the week. Busy times.

Phone call with Cory to go over some questions and then check up on priorities for what project is next. Recording notes from today and the past couple of days. Quick phone call with Bryan.

Meeting with the Cannapages guys over GoToMeeting. We started out by debugging an API call. We tried a few things. I then had to login to the client's site, flip some switches, and then try it again. They are pulling menu info, but we had to turn on some ecommerce settings to let the pages (API sockets) play through.

They also expressed a desire to get two more API endpoints for pulling sub inventory attributes (list of values) and parent attributes (list of values). They then take that data and loop over it to populate their menu forms. I sent an email out to Cory with an update.

Quick meeting with Cory. We went over a small recap and small check-up on how things were going on different projects. We talked about some of the next and upcoming projects. Super short meeting.

Closing elements of time behind the scenes for Cory and Kelly for a demo corp on the Herbo server. Spent some time working on the pub-15 for 2024 - entering withholding table data.

Working with Eric and Cory and trying to merge and push code. Merge conflicts between Wayne and Eric's code.

Meeting with Cory. Fixed a few elements of time to help close them up. On retention (potential adilas department - upcoming), Cory and I were joking around on who is going to take what. Going over other projects and rehashing to do lists for Eric, Bryan, and myself. We spent a lot of time talking about the chart of accounts project for Kelly. I was pitching a certain thing, and we were trying to see if it would meet her needs.

Going over meeting notes from this morning (# 10813). Light training on customer affiliate programs for invoices, ecommerce, and customers. After that, we chatted and talked about some other internal needs and ideas. See notes below:

- A lot of the meeting kept coming back to - what are the rules? How do we define things?

- That is something we are really missing and what is needed in defining some structure.

- Efficiency - how can we create more efficiency?

- Retention - clients, users, internal, more??? Retention may need to include all of those pieces of the puzzle. We need help internally, Brandon wants to help to keep sharing the vision and helping other people succeed as they try to define and implement more structure.

- Make a new graphic to show the structure... this could go along way...

- If working in different departments, report to the correct supervisor based on the project and/or task.

- Helping people know who they are accountable to report back to.

- Start with simple budgets - incentives, bonuses, etc.

- Flex grid to help track budgets - super simple

- Easing pain points

- Guidelines on budgets - make up some rules

- Budgets - start right off or wait? could go either way.

- Staffing - prioritize the biggest needs

- Understanding the biggest pain points

- Biggest resources - other people who are already doing those things

- Get some feedback and input from others - help them invest in the solution

- People are one of your best assets

- Customer support - Sean, Cory, and Shari O.

- Counseling with others - Getting that input from others - Perspective changes - May take a little bit longer

- Communication - Getting people on the same page, then getting it going, then helping it keep going

- Leadership and defining roles

- Processes - plans - what does that look like?

- Talk in person - setup a time to meet, call, text, etc. somehow meet

- Micro meetings

- Department text thread (quick blast) or department email - Group communication format

- Following protocols - Going up the chain - Somehow making a note or list of items to talk about

- Discussion and re-defining expectations - Softer conversation first - If it becomes reoccurring, escalate it

- If we need to, we could use the advisory board to help make hard decisions

- Finding and seeking out good talent

- Not everybody is a leader, that's ok

- Apply my areas of expertise to customers, users, and internal people - training, consulting, support, setup, planning

- Retention Department - Responsible for things such as: Training, Setup, Customer support, Consulting, Adilas University, and their own research & development

Going over new reports and who is going to work on those reports (assignments out to developers for certain projects). We talked about coming up with a solution to our bad data issue that we were going over this morning (a corp on data 10 from over 1.5 years ago). We came up with two possible solutions. We are going to be running a limited number of records through on a testing server. We will then go in and manipulate the testing data to simulate the bad data that we found. We will then figure out how to fix that data and make it correct and/or correctable.

Sharing info with Cory and Shari O. on some ideas for changing our main company structure. I referred them to some documents and brainstorming sessions from last week (1/15/24 to 1/20/24). Shari O. was really emphasizing the need for open communication between key players. We have been having some issues with communication channels.

Meeting with Kelly and Cory and Shari O. over a Zoom meeting. The main goal of the meeting was to look at some bad data for a client on data 10. We can't make it happen again, it was data from well over 1.5 years ago, and everything since then has been good. I'm just being silly, but it was a bit of a beat-up drill and a brow lashing of sorts. The good thing is we found the issue (limited number of bad records). At least we have a starting point to work from. We do not have a plan yet but that will come.

I was pitching the idea of a known issues report. Instead of just showing data (normal reports), we could actually look for bad data or errors in our code or data mismatches. That would be a small level of AI (artificial intelligence) on the reporting side. Imagine a report that said... check this and that... these things are known to be off the rails. That would be super cool. Side note, we actually started a known issues report way back (3/11/09)... at least listing out known areas that might have trouble. We just haven't been able to get around to building out that report. The actual report is in our code at this location... (top_secret/secure/known_issues.cfm). It has a huge list of possible problem areas, date mismatches, flow problems (something happened out of order or out of normal flow), and id/relationship possible problems.

As soon as we get a chance, it would be super cool to help uncover these and other possible problems and issues. Kelly had the idea of working backwards to help find the errors and exceptions.

One big take away, and something that we want to keep in mind for fracture (adilas lite) are these key pillars... We track money, inventory, finances, and full histories (Kelly was saying that those pieces are huge keys to what makes adilas awesome).

Debugging the add/edit customers page with Cory. Jumped on a client meeting with Wayne, Steve, Cory, and the clients (a few different people). They, this other 3rd party solution was wanting some custom ecommerce (menu) type stuff. Including a new sub domain pointer, ability to inject meta data, and customer headers on existing ecommerce pages and websites. The whole thing is for more or better SEO (search engine optimization).

Wayne did a great job explaining what we do and how we do it. He also mentioned full take overs on ecommerce pages and ways to interject custom code without rewriting everything. I thought that he did a great job. Good stuff!

Meeting with Cory and Shari O. to go over projects and questions. Shari O. had a request for being able to sell stock/units and special fees and presets (pack or specific fees or collected values for each sale). We currently allow for 5 preset items to go along with the sale of a stock/unit. She was requesting 10 (increase it by 5). We talked about options, and I gave them a rough quote what I thought it would take. If the client was tech savvy enough, they could recipes. That is unlimited and could be easily configured to add multiple (unlimited) items to a sale (into the shopping cart) from a single button or click. Anyways, just a free option that already exists.

We spent some time talking about payroll and the need for other states, more HR (human resources) options, and deeper payroll/HR functionality. That would be awesome, and we'd love to add that in. It just depends on who is paying for it.

The other main topic was going over some new reports that have been requested. Both for sub inventory and more accounting level stuff.

Emails and light tech support for Cory. She needed some backend database values for a client who is using the API to do sub inventory reports. Reaching out to Alan to setup a time to meet and chat. He had reached out to me.

Three different meetings. First, I jumped on a meeting with Eric to look over some tip stuff. We ran an update on data 11. We also looked at a CFC (code and database queries) and I made some suggestions. Something was erroring out with invoices and combined tip amounts.

----------

Met with Cory for a bit to go over a new quote for Kelly. She really wants a new report format for both the balance sheet and the P&L (income statement). Her end goal is to get us closer to a consolidated report that she could mix and blend corporations and financials. She is calling it a chart of accounts report. That's kinda what it is, but we'll just go with it for now. We went over a video that Cory and Kelly recorded a few days ago. I took some notes. It was a pretty good video and really explained well what she was looking for. Her main goal was visibility and exportability.

Here are my notes: The video does a great job but Cory has that.

- kelly wants all existing columns in a full grid...

- combined view system generated and user-maintained items

- going clear back to the top level groupings

- they want to see destination, groupings, types, accounts, etc.

- visibility

- all three parts (bsi, p&l, expense types, deposit types, bsi types)

- destination, category, group, sub group, account/type (item name), system generated or user-maintained, drill-down - show everything

- they want chart of account numbers

- need balance sheet numbers

- show active and inactive

- show sort order

- working toward a consolidated report - multi corp - enterprise

- corp id and corp name

-----------

At the end of the day, I was helping Bryan with some code. He needed something merged and pushed up to a server. We did and then tested. We ended up rolling it back. He will look deeper and we'll push it up later on. It was for a custom report and needed to be tested with actual live data.

Going over plans and research with Bryan. He would like to work on a new horizontal time view page. Instead of having people down the sides and times across the top (what we currently have), he would like to run locations down the side and days or dates across the top. Sounds great. We have some other ideas on elements of time # 8004 for more ideas on horizontal and vertical time or date views.

We also went over some feedback from Kelly and Cory on a report that was showing some data errors for sub inventory. Recording notes.

Note form Cory about what the meeting was going to be about: Cannapages has been trying to connect to Leafly through our API. We have opened up two API's for them but they are still having issues. Steve suggested a quick meeting with you to help facilitate this.

Here are my notes from the call, conversation, and meeting:

- They, the Cannapages guys, are super into their own vertical. They had some deep questions about things that are very specific to their industry. We use a very general or generic tool that has lots of dynamics. That works great for our clients as they are able to setup whatever key datapoints that they need. That is not very good if you are trying to standardize things and play with economy of scale (lots of people doing the same thing). There is a need for things to be standardized.

- Lots of talk about setting standards for certain 3rd party solutions and integrations. We can allow our users to set them up or we could automate things and either lead them through a valid setup and/or force them to use certain attributes and flows. If things are more standard, it just helps downstream flow and data transfer and sharing. Basically, a way to get normalized data for a specific integration and/or 3rd party solution.

- Our developers have full access to the whole adilas database. Some of the outside developers have to use API sockets and connections to open up specific endpoints. That is great and all but can be very frustrating, if they don't know which endpoints to use (virtual windows and doors into the data and records). Lots of talk about documentation and ease of use, from an outside developer's point of view.

- What is the best or biggest value for our customers or for the people using it? Some of our customers are real clients and some are outside developers. Keep those different parties in mind when developing. They have different needs.

- There are costs to do industry specific hook-ups. There needs to be a plan, settings, requirements, and set standards per integration. Otherwise, the outside developers feel like they are chasing their tails.

- Making things human readable... Many of our API sockets (backend developer endpoints through the API) are coded to id numbers or techy look-ups. Some of these outside developers really want an easy way to get at the data (plain English vs techy id look-ups). We spent some time talking about building different attribute look-ups based on text or names vs id or control number stuff. That led to talks about requirements, possible mapping options, and making settings that help with setup and automation. Otherwise, there are too many variables.

- This 3rd party needs lots of specific and categorized data (called meta data). We talked a lot about meta publishing data and being able to construct the names and associated data values. We need to put the data in the correct columns and in the correct format (standards). That makes it easier for filtering and matching things. Eventually, things will get parsed or broken up into smaller and smaller parts and pieces. This allows for things to be tagged and flagged as certain things. Once again, getting clear down to the meta data level.

- They gave us a few wish lists for the existing API. Cory took some notes there. Basically, was to standardize things and make it go and flow faster for them.

- I didn't know this, but the Cannapages guys are actually building a standalone side project to help some of our clients. Imagine something like this... a bulk tool that takes raw inventory data from adilas, strips out what they need (for their industry), standardizes it, allows for bulk edits and classifications, and then takes the new data (in bulk) and adds it to their database. They then serve up that modified data to an outside 3rd party that does or has a key industry specific website and data filtration process. I didn't really know what they were doing until this meeting. We are not even as close to industry specific as these guys are. It's basically a 3rd party bulk tool to provide data to another 3rd party. Kinda interesting.

- The last major topic was data and views. We have data (what is needed and recorded) and views (what it looks like) for multiple different parties. We have to have views and data for employee/users, data and views for state compliance agencies, and data and views for outside or normal customers, clients, and patients. That's a lot of different data and possible views (what it looks like). All of that, based off of stored data that got stored and entered into the system. Pretty high requirements.

- Some of the above notes may apply to our future fracture and adilas lite build outs. Whether it is dealing with different views, industry specific skins, normalizing data, and making the API sockets and endpoints easier to use and consume (plain English vs techy id/number stuff). Lots of good lessons being learned by being in the trenches.

Meeting with Cory and Shari O. on projects. We went over some yearend documents and forms and progress there. We spent quite a bit of time on some new quotes. One was a revamp on a prior quote. We added in some new requirements and needs for histories for flex attributes. Randomly enough, there were other requests for other hidden history records and reports. Some of our clients want us to watch almost every single place and record histories (some visual to the users and some that are hidden and only seen by administrators). I thought that was very interesting and something that we need to be on top of for fracture and adilas lite.

One of the places that they want us to watch was settings and who turns things on/off (like a gram controller for the shopping cart) and other setting changes. We also went over more requests to tie things to elements of time (like PO's and E/R's). We have some clients that are using elements of time for help with production runs and delivery options. Interesting what people need.

The last quote that we worked on was for a better or more standard report or export for the balance sheet, P&L (income statement), and general chart of accounts (deposit types and expense types and balance sheet types). The requests was for a report that showed each segment in a nice grid like fashion. On some of the existing reports, the values are all there, they are just hyphenated, the request was to break each data piece down and export it in a simplified grid, no other formatting. I think that the end goal is to pull it into Microsoft Excel and do some tweaking of the data and values there. Just guessing.

The last thing that I wanted to say was put in another plug for better aggregated data to help provide some better speed and business intelligence (BI). We have this planned as part of the fracture and adilas lite project, it just takes time and resources to get there. There is a whole project called the adilas value add-on core model where we will be working on these layers over and on top of the transactional core. Just for fun, here is a link with other references to the adilas value add-on core model.

Emails and then back on printable 1099's and red data overlay forms. Texting back and forth with Steve, Cory, and Shari O. about 1099 tax forms. Came up with a plan. Phone call with Will to help him with some questions on options for uploading images for customer websites. On the 1099's, we decided to not do the red magnetic ink forms this year. We pointed the users to file those online. We only have the printable black and white W-2's and 1099's on our site this year.

Meeting with Shari O. and Cory. Going over plans and priorities. We talked about yearend stuff for payroll and 1099's. I'll be working on that here this week. We also talked about a quote that a client would like. It's joining PO's, flex attributes, and elements of time. We watched a 15-minute video that Cory and Kelly made with the requirements and requests. We may modify it a bit, but it looks like a good project. This one has more of a manufacturing type flavor to it.

Recording notes and then jumping back on the yearend payroll updates. Met with Bryan to look at some code. Pushed up a new API socket to help with pulling customer info based on a last date modified. Then back on to the payroll updates. Pushed up the 2023 W-2's and sent a message to Shari O. and Cory.

Sent out some email updates to both Shari O. and Cory with some changes that they had requested. I then got back on the yearend payroll updates and changes. Working on some JavaScript changes to help with some settings that were added (form fields that will either be on the page or hidden - not there). Making sure that the functions work with all scenarios.

A number of different and random things. Emails, recording notes, code review for Will, providing feedback and suggestions, custom email addresses requested by both Shari O. and Cory for clients and new adilas internal users. Quick meeting with Bryan. Merged in some code and pushed things up for testing. Updating the 517 Blake Street address with the new PO Box 852. Changed out personal phone numbers for Steve and I with the main adilas tech support number 720.740.3076. Changed tons of files. Merged in new changes. They should auto rollout tomorrow morning with the other new code from today.

Jumped on a meeting with Cory and Shari O. Going over yearend payroll stuff and tax forms. We then got into a discussion on average costing and a thing called internal cost corrections (ICC). We have some of our older clients that came on (started using our systems) before we had sub inventory. Some of them are wanting us to add in either average costing options or be able to virtually update the COGS to match-up what has come in/out of the system on a per item basis. The best solution would be to get them to buy into and/or use sub inventory or parent/child inventory. Anyways, we were talking about some options.

Quick meeting with Shari O. and Cory. Going over priorities and a light overview of where we are heading in the next couple of weeks. We looked at schedules. Checking emails.

Going over an API socket build out and request that Bryan is working on for a client. This one was special. It was a vendor requesting information about another vendor's saved settings. I don't know much about it but it sounds like we are sub-contracting out one vendor to provide another vendor with the data and information that they need. Kinda the Texas two-step. Anyways, Bryan and I were talking about what is needed and requested. The good thing is the data requested is not a security issue. It's pretty simple data. Bryan is going to ask Steve and Cory for more information and insight into this small request. Anyways, going over ideas and options.

Weekly meeting with Cory. We were talking about servers, uptime, downtime, and what went on over the weekend. We had a number of servers down over the weekend due to a system maintenance issue and system migration slowdown from the main data farm (commercial hosting company). We couldn't control it. They were planning a 5 hours outage and it almost tripled. The good things were that not all servers were affected. However, we had a few servers that were down for around 17 hours. We couldn't do anything; it was all on the server side of the equation.

Next, we talked about real costs to get a new company up and fully running on our system. It takes time, money, and dedicated time to really get someone in deep enough to help them stick (stay on the system). Those clients need the support and help to really help that transition happen. At some point, they, our clients, need to see value and/or commit from their side of the fence.

We have done this in a number of ways. We used to use independent consultants. That works pretty good until that main rep or consultant either gets too busy or goes somewhere else (takes a different job). We have also done it internally (our own reps and consultants) and that has been somewhat effective. We can get into trouble if the client needs help and we don't have enough people or resources to really help them out, at the drop of a hat. The other thing that we have seen is our people are ready and the client is either too busy or won't make the time to really get the proper training. It can drag on for months and months. There are some challenges there.

I showed Cory the bulk clear customer loyalty points feature and we did some light playing and testing. Planning the next steps and next projects including yearend stuff and discount engines.

Got a text from Cory to help look at a database issue on data 4. Jumped on a Zoom meeting and was working on debugging things. Eric joined us as well. With his help, we were able to find and fix the error. I was in the right area but was super focused on one particular part of the problem. I kept trying to fix a certain value to see if that is what the problem was. With Eric's help, we widened our view and were able to find the problem. The problem ended up being a lone parentheses that was in the wrong place.

Jumped on with Cory and Shari O. to show them some progress on my bulk clear loyalty points project. Small show and tell. We merged in a small branch for Chuck and then talked about some clean-up on pagination on certain pages that is needed (go to the next page - pagination). We talked about yearend stuff and getting the known pieces done before the end of the year. That one, yearend tax stuff, comes up every year. We have to update 1099's, W-2's, and other reports. We also have to add new tax withholding tables and update values. Maintenance stuff.

Emails, tech support, and checking on the WordPress site and Cloudflare issues with the main site. Phone call with Steve talking about SG&A costs. Quick phone call with Cory to go over customer loyalty points. Quick GoToMeeting with Bryan to help with some questions. Recording notes from 11/20-11/22.

Jumped on a Zoom session with Cory to help give some advice on an API socket connection for a client. After that, I jumped on with Bryan on the GoToMeeting session. We did some planning on a new 3rd party API socket project. After we finished, I did some light research on running old Adobe Flash videos (.swf's) to see old content that never got updated to a newer version. I found a flash player called "Ruffle". I downloaded it and played around with it. I was able to watch some of the older flash videos.

Got an email from Wayne saying that we need to update our QR code generation library to a newer version. Emails and wrapping up the day.

Meeting with Cory and Shari O. going over projects and priorities. After that, we jumped in and went over an API socket connect for a company. Light tech support helping them get connected and going.

Cory had a number of 3rd party solutions that needed to be looked into. We spent some time looking at their integrations and checking API sockets. The two companies were Dutchie and Headset. Made some small changes, looking around, and then showing Cory some other changes that we made.

Fixing a bug on the calculate payroll page. The error was some older code that was doing a loop over a query with a grouping. That code used to work fine but doesn't seem compatible with the newer code. Bryan and I were working on this bug. We got stumped for a bit. I was trying things and running a series of tests. He put the errors into ChatGPT (AI or artificial intelligence bot). By the time we were done, we had a working solution. It took both of us to get a working page again. We pushed up code and Bryan sent an email out to Cory and others. 

Meeting with Cory and Shari O. Going over projects and priorities. Small updates on where each of the current projects stand. We talked quite a bit about the need for more special line items and maybe even making them more dynamic. Special line items are things that our clients get by default (things like labor, part number other, fee, shipping, freight, discount, supplies, etc.). They also have some special functionality that nothing else has as far as how they play, how they show up for roll call, and special grouping on certain reports. The other feature that Cory has been using recently is the percentage add-on feature that takes the cart total and then figures out a percentage to make that number stick and pass through the cart as a fee or whatever. We may end up doing a project to help with these features (dynamic special line items).

Toward the end of the meeting, we were talking about yearend payroll updates and changes that are needed (taxes, rules, forms, new rates and formulas). That comes up every year. One of our constant maintenance items for the adilas application.

Looking at a video that Bryan made. Emails, phone calls, and recording notes. Going over plans with Cory for a client import for customer loyalty points. General stuff.