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.

Phone call with Steve. We were talking about the current load and how much is going on. It's hard to keep up. Steve is feeling pretty overwhelmed. He and the other team members are running the ship while I am off on the side trying to work on plans and investor stuff. It's pretty rough. There is also some underlying tension from a miscommunication and overstep on my part. See EOT # 12731 for some back story.

Here are some of my notes from the meeting with Steve:

- We started out and I read a post-it note full of some things that I think Steve has issues with - my personality traits. See attached, if you want for the post-it note. We are all working hard, but we have different opinions on what will help and where to focus. Similar but also somewhat different directions. Neither one is bad, just different approaches.

- He is busy taking care of business and paying clients. He is trying to only work on funded projects and projects that have ROI (return on investment).

- Trying to fill in the blanks (needs of whatever is needed).

- Steve is shooting for full AI projects - code, planning, fixes, etc. Steve is heavily leaning on AI as the backup or fallback. He is totally going in the AI direction for as much as he can.

- He showed me a small website that a guy built using just AI. Here's the link. I pulled it up. It looks great. It is pretty impressive. It doesn't have any real content, just a shell, but it looks amazing. We talked and chatted about that for a while. There is some fear that some of these guys are going to take over and build what we have built over the last 20+ years. Basically, a question of what is stopping them from taking the next step and building it out on their own? I see it, what we have and offer, as way deeper than that, but there is some worry and unknowns.

- He is seeing or thinking that people don't want any real interface... they just want a simple chat type interface and AI will do everything for them. I was telling him that our full interface and existing pieces need to still be there. There is value there. It is nice to be able to do anything that you want (say an AI chat window), but there are also times and places for a quick and easy button or link. We need both. Our interface is not our real product.

- We talked about how Wayne is working with some AI agents to work on the database and some database updates.

- Steve is feeling a little bit of panic mode. He watches and reads a lot of tech news. Huge changes are happening all around us.

- Only working on funded projects.

- Relying on Craig for all money type decisions (controller level control for funds).

- There is an urgency to what we are doing.

- AI is going so fast, it is scary. He is scared.

- Small talk about IP (intellectual property) and how we can't stop AI. If they want to do something, they can just do it, change it a bit, and run with it.

- He wants me to look into complex binary (tech stuff). He is planning on doing some more research there. Basically, skipping the code and going right to binary level commands.

- Brief talk about how people interact with things. He was saying that people don't want to do any data entry. They just want the AI agent or system to do it. Something like this, I have a document, I upload it, I then have the AI agent enter it into the system. Thanks, all done. AI does it all. As a side note, there may be some automation things that we can do, but don't think that everything will be like that.

- Talking about taking care of the business right in front of us. I don't deny that... and I know that there is a need there. We have been doing that for the past 20+ years. It is also a small trap, in some ways. It keeps us from breaking out of our form or container. We are somewhat maxing out our current model.

- If you read between the lines, he and the team are busy, with paying clients. There is a demand for what we are doing.

- We finished up the meeting, and he was going to go jump into another project that is needed. He is working super hard. He is trying to fill in the gaps as best as he can. I'm super grateful for that.

- After the meeting, I was talking with Heather (my wife). We were talking about an analogy of a malt shop or ice cream shop. Say you have a line out the door, small rush, tables need to be wiped, and dishes need to be done. Everybody is busting their buts, except for one guy in the back who is dreaming of a better way to do it. That doesn't fly very well. Sad to say, I'm that guy. I'm not trying to hurt anybody, and what I am doing is super important, it just gets judged pretty harshly. I fully understand. I have been in there busting my but as well, for years and years. I just know that there is a better way. The story above changes when you say, this small rush has been going on for years and years. We have all been pushing on things. It is not just one night, where things get busy. That longer timeframe makes a big difference.

- Tying this back to adilas (above ice cream shop analogy). We offer custom code. That is awesome and totally part of our model. However, we get so tied up in doing custom code that we can't finish what we really need to. We end up getting stuck in that scenario, kinda like the malt shop. There is a balance. You have to have the money to keep going, and that is super important (work right in front of you). You also need to look to the future as well. I heard a guy say one time, there is a difference between working in your business and working on your business. We need both. It's a fine line and tough balance.

A number of follow-ups and emails. Sent an email to Adi, Adilene Dominquez, about some of the new SWOT stuff that we were uncovering. Also sent an email to Jennifer Murer from Harris Computer about the same SWOT analysis stuff. There is so much more than just SWOT analysis stuff in that document. I can't wait to start harvesting some of the content. Heather, my wife, came in and we went over some stuff as well. Some of it is way too technical for her but we can split it up and make it more consumable - based on audience. Emails and paying bills.

Back working on the SWOT analysis stuff with ChatGPT. Making good progress. Going super deep into the adilas history stuff. I also spent some time talking with Heather (my wife) about adilas and why we are doing what we are doing. Trying to boil all of the different things down and put them all together. There is a lot going on.

If you want to really learn about the adilas story... You should read this chat with ChatGPT. For the record, it is a little bit long, but really good information.

https://chatgpt.com/share/69a9d788-a288-8007-949a-58d1ed5ccde2

Meeting with Abby and doing some graphic editing. She is doing well and working on some new graphics. She was getting stuck on certain layouts, ideas, and options. She is doing great. You can tell that she is new at it, but doing exceptionally well. Fun session. We went over a bunch of things. Even Heather jumped on with us and gave her some feedback on her graphics.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

- Came home, played a game with Brooklyn

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

- Made chocolate mousse

- Played a game with Heather and Brooklyn - Heather won

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

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

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

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

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

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

- Graphical homepages

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

- Work as if for years

Went over to Heather's parent's house. A construction company was fixing the road by our house. We didn't have any electricity. I brought my laptop, a bunch of old post-it notes, and a notebook. Spent some time going over my notes and transposing them from post-it notes to a physical notebook. I'm kinda glad to slow down for a bit. Rewriting the notes, it is helping me really internalize them, meaning my notes. I want this to work vs just a quick fix for the AI training.

Quick phone call with Josh to touch base on the training and where things are going.

Working with Russell on the graphical homepages project. Only got about half an hour today. We ran late on an earlier meeting and then I got pulled off because my wife needed me to pick up our daughter. Short meeting today. Working on layout stuff. I got a couple of screenshot graphics from Russell to help with the project. See attached.

Emails and playing with percentage ownership changes (Microsoft Excel stuff). Paying bills. Two phone calls with Steve to go over percentages. Going over Yogen Fruz stuff. Talking about software and hardware integrations. Even talking about possible middleware application for a print queue or print log. Maybe tying in the print log to Windows or Android specific middleware or software. After that, spent some time talking to Heather (my wife) about updates on different subjects. Recording notes.

Phone call with Steve. Heather, my wife, joined us for most of it. We were going to talk about a new internal shopping cart but Cory wasn't able to join us on the call. Today was Labor Day and she was off.

We ended up talking shop and talking about adilas in general. We covered the gamut and talked about all kinds of topics. I took a bunch of notes and was even writing Heather some notes as Steve was talking (interpreting and filling in gaps). Here are a few of the topics that we spent some time on.

- Defining the company structure and what does that look like or what will it look like? We all wear lots of hats and do all kinds of stuff. Who controls what, who manages what, and who reports to who? That all (company structure) needs to be defined. We've been able to skate along and skip some of this, but we really, really, need it now. We are getting too big not to have it. This lack of structure is starting to affect other parts of the puzzle. It is amazing what we have done, up to this point, but we also see that some changes are needed. We both agree on that, we just aren't sure how that needs to be done. We need a plan for this.

- Communication lines and who knows what and when do they know it? Some of our communication lines have been struggling.

- Steve and I were both able to vent a little bit. We are coming from different angles, but both wanting similar things. Heather chimed in a few times as well. I think that it was good for all of us on the call.

- The terms "plan" and "projects" are not the same thing. If we have a project, then we have to make a plan for it, meaning the project. The project is not the plan itself. We also talked about short term, long term, etc. The plan that we are talking about is a long term plan (small mock-up outline - not the finished product). Not just the next project. There is a huge difference.

- We have been really good at bootstrapping (working with minimal funds or funding and making things happen on a shoestring budget). We are super good at just in time project management. We are really good at seeing a need and coming up with a solution. We are not very good at long term planning. We also struggle with communication and expressing ourselves.

- Steve is very good at sales. He is good at watching out for people and helping them achieve their dreams. He hates being in debt. He hates owing people money and not being able to pay people for work that has been done. Especially, in a timely manner. That just adds stress. He is one of our best doers - he just goes for it. Super hard worker. He has sold more adilas systems than any other person. He has trained countless companies, employees, and consultants. Originally, he was the mastermind and brains behind the whole concept of adilas. It's been an amazing journey. One of his strong points was explaining what he wanted and then letting us figure out what steps needed to be taken to get there. He has done this over and over again.

- Due to lack of funds or any outside funding, we have had to run super thin and lean. In some ways, that has been really good and we've advanced the ball further than anybody else could have (us and our team). That same lack of funds has a downside as well. That doesn't give any flexibility for creativity, experimentation, testing, documentation, and even marketing. We are missing some key pieces.

- We spent some time talking about selling part of our company to raise some money. That has pros and cons as well.

- ROI (return on investment) and budgets

- We tend to follow the dollar - if a client wants something and is willing to pay, even if it not quite or even close to enough, we tend to go that way. Steve was talking about an old saying - "A bird in the hand is better than two in the bush." Meaning, you just keep getting what is available and real vs chasing something that may or may not come to pass.

- Building up a company, any kind, especially a SaaS (software as a service) company takes time and money. No way around that.

- All of us have been running at max for a long time. That takes a toll.

- The end goal is a reoccurring revenue stream or model. We are getting there, it just takes a lot of everything to keep that up and running.

- After the meeting with Steve, I was talking with my wife Heather and my daughter Amber. We chatted about a few things. Amber was saying, maybe downsize and then rebuild. If it's hard to manage right now, how will you manage it if it's bigger? We also talked about a possible board, council, or someone to help manage things. We may need more than one leader. We need to define and fill the correct roles. It's way too big for a single person. We'll have to plan that out and then make it happen. Good phone call.

Met with Russell over lunch. We ate, chatted, and got into some good discussions. Here are some of my notes. See attached for scans of my handwritten notes.

- Russell recommended some books to read. Good source of learning. Author - Robert C. Martin - "Clean Coder", "Clean Code", and "Clean Architecture"

- Ideas on project management, saying yes, saying no, and some time management concepts.

- We talked about the addiction of "progression" and the pros and cons of that addiction.

- Provide the stable (for you, your family, and others) - then go from there. As a side note, this word "stable" kept coming up throughout our conversation.

- What if it fails? Are you going to be ok? How many eggs do you have in one single basket? Asking yourself questions like that sometimes helps you get a better, more rounded perspective.

- Consistency over small pushes. It may be better to be consistent than push like crazy all at once. Similar analogy to floods vs drips (water).

- Little bitesize pieces

- Dedicated "Lunch" time or some other dedicated time. Carving out something that is special and time for you.

- If it is your project, you will care for it and make it happen (see it through). On a different note, if you can get others to buy in and give them ownership and let them make parts of the bigger project their dream, it becomes more stable over all.

- A good testing strategy is needed. It will build confidence by the bucket load.

- Lots of talks about expectations - Testing and getting everything built out.

- Efficiency - That sounds great, and it has its place, but sometimes there are more things than just pure efficiency. You almost have to play this little balance game.

- Russell was talking about the book and podcast "The Working Genius". He was telling me what some of his strengths and weaknesses were. Fun topics. It helps you get your vision of who you are and how you work and/or interact with others and other tasks.

- Over time, it is interesting to watch strengths and weaknesses playout over time. Letting things play out (both naturally and forced - at times).

- "Keep the stable" - Russell Moore - We kept coming back to this. I think he was trying to get me a subtle message of sorts.

- Continuing education time - make the time for it.

- Not only consistency, but consistency patterns

- Planning out the details of the journey. Looking and planning ahead.

- Russel and I were talking about my wife Heather. She has said over and over again that we are chasing too many things or trying to be too much for everyone. She's probably right and correct.

- Chasing the dragon - (the dream, the final or finished product) - It can be really fun but it could also be really dangerous (both mentally and physically). Just for fun, we were talking about the thrill of it and also the long term phycological effects of that chase. True on all accounts. I love the chase but sometimes it really does affect me (burnout, stress, anxiety, etc.). There is a cost to what we do.

- There is so much more than just building it - That is one of the pieces of the puzzle (the whole).

- Marketing - Pushing it to the next level

- Technical debt - it can crush you! This is when you have so much older code that needs to be updated, maintained, and adjusted. It is called technical debt. It can crush you, it may also crush your soul, your spirit, your will. It can be a huge burden.

- Minimal on the heavy lifting. Who is doing what and what kind of time commitment does that take? Where and what is your job? Don't get sucked into the jobs around the job (whatever that job is).

- Sharing your knowledge. That is fun and it pays dividends.

- If you don't take the time to do continuing education, the world will move on without you.

- Spend an hour a week with Russell.

- Ideally, if you can swing it, 5 hours a week on continuing education. This is your future. You have to future proof yourself.

- Lots depends on the funding... If not, either bail out or keep chipping away at it. Exploring options. Usually it is not just black and white, there are options if you will look for them.

- The dream is awesome but be ok with the maintaining of it as well. It not just the new building of a certain project. Sometimes, you have to pull back and either do some upkeep or be willing to maintain what you have. Here is a link to a small flower gardener (image) with the same question - plan more or take care of what I've got?

- Why does a designer or dreamer code? I'll tell you why, we don't like being stuck. We'll get in there and figure it out in order to make our dreams and ideas come to life.

- From Russell - what is your best path? His answer - Produce features and be able to get revenue (quickly).

- Russell also recommended a video called "Minimal Viable Architecture" by Randy Shoup.

I met a friend and his wife for dessert. My wife was with me as well. My buddy is a high-end developer in the Salt Lake City area. I was telling him all about our plans to build out ship B (adilas lite or fracture). We had a great conversation, and he was a great sounding board. He was praising us, the current team, for making it happen and supporting our families for years and years.

One of my biggest takeaways from our meeting was dealing with the tech stack. Basically, what servers and technologies are you built on? Or how did you develop and deploy your code? What backend servers and frontend frameworks are you standing on? We talked about legacy systems, pros and cons, and quite a bit about perception (what people think - right off the bat). He kept saying that "the tech stack matters". Meaning, investors and others may have a say in what technologies are being used and developed. He didn't have one specifically that he recommended, but we did chat about a few options.

He was also asking questions about, maintenance, technical debt, dependencies, libraries, and who is going to build it, maintain it, and improve upon it? Great questions. He was basically recommending that we widen that piece as much as possible, especially if we are building from the ground up. Prep the field and make it as future proof as possible. Great ideas.

My mind was going nuts all day. Literally a whirlwind. I didn't write down the start and end time on this one. But from about 12 noon until 11 pm ish I was brainstorming, thinking, recording notes, talking to people, phone calls, texts, etc. It was super fun. Once again, these notes don't have any specific order, they were just what I recorded on small little post-it notes. I should have used a bigger notebook... :)

- We need a matrix and the ability to monitor every choice and setting. Full data driven and choice driven billing for our clients. This needs to be baked into the beginning design for fracture and where we are heading.

- What about possible open-source code and/or having our clients pay for their own accounts? That would take some of the hardware and server pressure off of us. Just a thought. Along with this, we could set it up to use any domain name, any site/server or hosting company. Whatever. Keep it super open, if we want it to be.

- As far as hosting and packages, we could have our own options as well. Things like simple home use, shared servers, semi dedicated servers, full dedicated servers, clusters, etc. Make some options and then make them available.

- List out your services that you offer and/or have available.

- Packages and bundles - tiny, small, medium, large, extra large (xl), double X (xxl) or whatever. Maybe set some limits for the different sizes or limits withing a certain range (keep it kinda flexible). Allow for variable billing.

- Stripe seems to have some awesome automated merchant processing features. It may be fun to plug into this. We could also use something like Datacap and then have access to even more merchant processing options. Just thinking along these lines. This could be for our clients as well as for us, as a company. Currently, we are using USAePay for our internal merchant processing stuff. I'd like to expand and really open that avenue up a bit.

- You (meaning me) may need to fully jump off. Earlier today I was giving Steve an analogy of jumping off of a moving train. The best place is either on or off, not somewhere in the middle. If I'm going to jump, do it and get clear. You don't want to be too close to that moving train. Once again, just an analogy.

-  Some of this stuff is for me, but was part of the brainstorming session. Anyways, I'm going to list it anyways.

- I know some bankers. I'd like to meet up with them and just pick their brains. Thinking of Mike Hall, Brent Wallis, Kevin Moser.

- I could use some of my percentage ownership of adilas as collateral, if I needed to get a loan.

- I have a buddy that helped me out, back in the day with my Learn To Freeride (LTF) project. His name is Gene Spaulding. He currently does a lot of stuff with nursing homes, memory care, and retirement homes. Good resource. Maybe even checking with him if he needs a product to help manage all of his beds (rooms for his clients - elderly folks). Regardless, he's an awesome resource.

- I know a guy by the name of Jud Eades who is an entrepreneur, a friend, and a total stud. He does all kinds of fun stuff. I could see if he has ideas and/or is interested in helping me build a reoccurring revenue based product.

- I know lots of other business people who have ideas and different know how. I would love to tap into their minds. Just being silly, but started thinking about too many people and decided to stop (for now).

- Use eye candy to show what we have done

- Talk with my wife Heather

- I have a full business plan that I did for the LTF project (older personal project dealing with teaching snowboard freestyle tricks and moves - early to mid 2000's). Look at the LTF binder, just to get some ideas.

- Recruit help. Think about all kinds of avenues, people, places, things, etc. Be creative!

- Include the Lord

- Sufficient - That goes a long ways

- Apply It! - Whatever you learn, keep applying it. That seems to be one of the secrets.

- We (adilas) hired a business consultant a few years back. Get back with him and review of what you learned from Jonathan Johnson and Epic Enterprises Consulting.

- Check in with Aspen, my daughter and see if she wants to help. She has a great gift for organizing and such. I could use the help.

- Talk with my mom and dad. I would like to ask my father for a father's blessing as well. That would help me out.

- Planning things out and then funding that development.

- Strategic funding based on needs and plans.

- Willing to listen and record notes. I love sharing what I have learned. Writing things down helps my memory. The old saying - The faintest scratch is better than the sharpest mind.

- I'm willing to let others play a role and add to or even take away as needed.

- Freedom from the adilas grind - that's worth a lot.

- I may be able to do more and help more by not being tied down.

- Make a list of pros and cons

- Include some prayers (lots of them) and some fasting - ask hard questions of God and of yourself

- A couple of books came to mind - Who Moved My Cheese, The Go Giver, How To Win Friends And Influence People, Rocket Fuel, etc. Read those books.

- Be willing to help and give. I enjoy that.

- Follow a dream

- There is a level of excitement that I'm feeling. This is kinda fun!

- I have a book called "Differentiate or Die" - I'd like to read that. It was given to me years ago and it has been in my office but I haven't gotten around to reading it yet.

- Get some training

- Work on some funding

- Be a cheerleader

- Help fix the existing foundation. Make this part of the plan.

- Be open... to... whatever...

- Bridgerland - It's a local technical college here in my town. There are lots of options there. I know a number of people, they have training resources, and they have even asked for a demo (multiple times) of our products. I'd like to explore some options there including offering to help them build something that they could resell and/or pitch to other technical colleges. Almost a white label type option.

- I had a dream the other night about including other businesses in our planning and roll out. Keep exploring those ideas and avenues.

- Leverage your percentage of ownership.

- Ask... What do you need? How can we help? What do you want? Where is your pain?

- Go back and do it again. Trystorming and being willing to circle back again.

- Talking with Heather, my wife, and going over what I was making, what I could make, and how to keep a good balance. I'm not going to lie, there are parts of it that are just plain scary.

- We may need to get back to doing a family budget. We used to do that a long time ago. It's been pretty smooth sailing and we haven't done that in quite some time. We may need to circle back around.

- I'm kinda scared to dip into savings. Super grateful that we have some.

- During the day, we talked (Heather and I) about existing expenses, promises, and upcoming expenses dealing with raising a family (vehicles, wisdom teeth, other doctor bills, etc.). We listed a few things out.

- From Heather - We don't want to relive LTF! - Understood and I agree. Lots of lessons learned. If someone has time, some time in the future, I'd love to tell them about that project and product. Huge building blocks of my career, part of my life, and part of the journey. It wasn't all bad... :)

- Look at the risk/benefit trade offs

- From Heather - She'll let me do this - new venture - if we don't take out a personal loan and don't clear out our savings.

- We have been super blessed.

- We can't see the future. We don't know what is coming.

- Keep adding to savings as part of the plan.

- Light fun with numbers. We started adilas in 2008 from a project that started in 2001. The first adilas deposit was for $100. As of 5/31/23, adilas has made over $7 million and growing. That's kinda fun.

- The current goal is the business plan. That may end up being more than just one document. It may be better to say plans (plural).

- Need to call our accountant and check on taxes (for me personally)

- We have a number of projects planned for around the house that will still need to be completed this summer (paint back porch, cut down the dead tree, etc.). Heather wants to make sure that I don't get too busy and that I can still help out and do the planned projects around the house.

- From my daughter Amber - We were on the back porch talking - Here are some random thoughts that I wrote down from our conversation. From Amber - Do what makes you happy! Question - wouldn't having more be more stressful (meaning another whole adilas product)? I told Amber that I was trying to work myself out of a job. She had a few questions about that. Foreign concept to her. We talked about - if you are enjoying the job, it's not work. Good fun!

- More notes from Amber - You could always find another job. For example, snowboarding or whatever. Something that you enjoy! Maybe something part time or something like that. You could teach an art class, spend more time with your hobbies, actually get a job where you have a window (you work in a cave), get out and get outside, something. She was having fun giving me advice.

- AI (artificial intelligence) - this may replace certain jobs. Creativity and interpersonal skills - you can't replace that (currently).

- I like helping people - do something along those lines.

- Aber was being super kind - She said - You should draw stuff. I love the t-shirts, cards, your life jacket (kayaking PFD), and other things that you have drawn. Go have fun! You could totally use your drawing talents.

- Next I talked to Aspen for a bit - she was very logical and had some great questions. For example: I wrote down - Do you feel comfortable dropping all of your responsibility on other people? Who is going to do what you were doing? What about family timing (meaning with our family and who is doing what - in general)? What about retirement? Who is going to help with marketing? Etc. Very logical questions. It was great.

- I told her that I was playing a small game, similar to the old fable called "stone soup". Bring what you've got, throw it in the pot, we are making stone soup. She thought that "a community effort" was a better way to say it than calling it stone soup. She is probably right.

- A few more questions and comments from Aspen - If you have a passion about something, we'll trust you. Prove yourself! Different question, how will this look for taxes?

- Both grandmas and grandpas (Heather and I's parents) are a great resource. I'd like to let them know what we are doing.

- Talking to my son Tanner about what was going on - He said, it sounds like Legos (little building blocks).

- This is totally random, but also came from Tanner - We were talking about trying to skip things that we didn't like or couldn't do. Just being silly. All of the sudden, Tanner tells this story about one of his friends. His friend is in a wheelchair and has some disabilities. Tanner was really sore from doing something and said, I think that I'll skip leg day today (dealing with weight lifting and going to the gym). His little friend chimed in and said, I skip leg day everyday. Tanner and his friend had a good laugh at that. Anyways, it was super funny and broke the tension around the dinner table. Good stuff!

- Talk with Steve about some ideas

- Aspen recommended that I talk with Kelly (adilas power user)

- Called and spoke with my mom and dad over the phone. I then went over to their house and spent an hour with them talking about things. Great little visit. They recommended that I do some fasting and praying. My dad will be willing to give me a father's blessing this coming Sunday. Pay your tithing, server the Lord, and pray for help.

- My dad gave me a scripture to look up: 1 Nephi 4:6 - Led by the spirit, not knowing beforehand the things which I should do.

- I told my mom and dad about a dream that I had on Monday night about including other business owners in this software re-write and that is exactly what my parents recommended for me to do. I thought that was very interesting and awesome!

I joined later on. Helping my wife Heather after ankle surgery. When I joined, Cory, Shari O., and Steve were on the meeting. I was pretty quiet for the first part. Mostly just listening. We went over numbers and budgeting stuff. As we were going over some of our projects, Steve was recommending that we include Mike on some of the upcoming features and marketing efforts. There was also some talk about real time sales tax redemption and money transfers. They are (Stev and Mike) are trying to figure out some angles on state compliance systems and using sales tax redemption and tracking as a possible angle. Good ideas.

Cory was recording the budget numbers. We also talked about other projects and bids. Lots of verbal reports. At the end, Cory sent around the budget spreadsheet numbers.

I was late getting in, helping my wife out. Sean was checking in and he reported that he just got off of a phone call with Steve as he was traveling up to Denver. Working on emails.

Poor Bryan - he was having major internet issues. He and I got to chat at the beginning and at the end. Steve came on and we got to hear from Steve for a while (I'll share some notes below). Part way through, Bryan's internet connection was going in and out and the poor guy kept trying to connect and then got booted, time and time again. I was on the whole time, Steve most of the time (while he was on the meeting), and poor Bryan in and out the whole way through. Finally, Bryan sent me a text message and said that he would hook up with me later on. He was making a great effort but some of that was out of his direct control.

Anyways, here are some of my notes:

- Bryan and I spent some time looking over Chuck's first round mock-ups. I was drawing and showing Bryan what we were thinking about. We got kinda techy and talking about flow, processes, settings, and ideas from the mock-ups. Good session.

- Steve popped in and he and Bryan were talking about videos and marketing. Lots of good back and forth. Bryan's brother is the one pushing the videos. Steve would be very interested if he (Bryan's brother) wanted to work on a commission basis - he does the videos and then gets a kickback from sales.

- We have tried a bunch of different things. Trying to figure out where we get the best bang for our buck - ROI (return on investment).

- Small section talking about our sales and marketing teams and how they have to deal with a level of client rejection. If they get too much, it tips them over the edge, and they start doubting their skills and confidence. Pretty natural but very much a real thing.

 - The costs (huge costs) of training someone to be high-level power user in adilas. You almost have to take an adilas power-user and then go from there vs trying to get a non adilas user and get them trained up. The costs are too high, and the skillsets need some in the trenches experience. Interesting!

- Steve was talking about allowing people to invest in marketing and then try to get some ROI on those efforts. It's really hard for us to do it internally, based on funds and available personnel who could really do what needs to be done.

- YouTube and YouTube influencers - that seems to be a very modern trend that is getting some results. That also takes someone fulltime who is pushing on things, knows what they are doing (adilas power user), has a following (other people like them and what they do), and they keep creating new content (daily, weekly, monthly, etc.). You need a mix of all of those pieces.

- Adilas has been a frontrunner and forward-thinking company since the get go. We just haven't been able to capture the full market. We were doing software as a service before SaaS became a buzzword. We were doing cloud, web-based software, paperless office type functions way before they were cool. Tons of other frontrunner type approaches. We have been pioneers and out on those front lines. We've been doing this for the past 20+ years. We started wtih modem speed internet connections and Microsoft Access Databases. We've come a long way. So, how do we market that? That seems to be the question of the day.

- Bryan was trying to reconnect to the meeting and Steve and I were just talking. I mentioned that Heather (my wife) said that we are too broad and trying to help too many people or do too many things. In the very next breath, I mentioned to Steve that I had a phone call with one of our clients (Drew at the bike shuttle and coffee shop) and they wanted all of these other things. Some of which were standard and some of which were custom. Steve was saying that we are caught somewhere in between those two realms. Some want it to be simplified and others want even more with choices, settings, permissions, and pick and choose functionality. It gets crazy deep.

- Seems like people want everything under one roof and they want it for free. That's a tough ticket (super powerful, low cost or free, looks great, and is easy to use). Sounds great! Sign me up! How do we get there?

- Just thinking about possible funding options - What if we were free (the whole adilas transactional core) and just charged a small cover fee? Credit card do it... everybody wants to use a credit card processor because it helps them make sales and run their business. We would also do something along the lines of the value add-on core model where we provide the main adilas core (full adilas account that takes care of all of the transactional data - what it is right now). We then could charge for any of the additional layers. We could even charge for the core and then add-on fees or charges for the higher levels. All kinds of options. Just as a quick review - Levels are: 1. Transactional core, 2. Industry specific skin/functions, 3. Custom code, 4. Business Intelligence (BI) (sums, counts, aggregates, stats), and level 5. Enterprise level (multiple corps in array and interconnected with roll-ups, roll-downs, controls, and full control over the flow of data.

- We can also sell other professional services, training, consulting, analytics, custom code development, design, marketing, hardware/software integration, etc. We are not limited as to possible avenues where we could monetize our efforts. Currently, our monthly application fees are our bread and butter (SaaS type levels of a monthly subscription or usage license). We could sell digital real estate (web hosting, database serves, mirrors, shared hosting servers, semi-dedicated servers, fully dedicated servers, and other special server configurations). We can sell storage (active and archived or cold storage - for data). We could flip our model so that is fully based off of usage, throughput, bandwidth, storage, counts, amounts, and transactions. Tons of options.

- We sure are gaining a lot of feedback and insights on what we can do with fracture (future adilas project). This is where we are headed. We just aren't sure how to fund that. We have an awesome testbed; we've done tons of little prototypes (they are working and in production), have tons of feedback from our users and other outside critics, we've been making plans, we have learned tons of lessons dealing with settings, permissions, interfaces, transactional data vs aggregate data, speed, servers, configuration options, look and feel, solving pain points, and bringing all of these pieces together. So.... what is our plan and what can we do to bring these pieces more fully to market? Where do we go from here?

- Switched gears and started talking about using some other video conferencing software packages. We've been using GoToMeeting but have been having some issues. Steve and I briefly talked about Google Meet, Discord, Zoom, or whatever. Just looking at options.

- Steve left and Bryan was able to rejoin for a few minutes. I told Bryan that Steve was very thankful and grateful that he, Bryan, is adding his timecards and time clocks to the adilas system. That is very helpful.

Emails and playing with numbers for a retirement type program for adilas, co-founders, and co-owners. I was asking my wife and kids for some ideas and suggestions. I then was playing with some small calculations and seeing how things would look and/or work out. I also did some research and reading up on ternary operators in JavaScript. This is a shortcut for setting a single variable with either a true or false type logic (normal if statement stuff) without writing out the full if statement and setting the variables in the main if or the else clause.

Here is a sample: I got this online on one of the sites that I was looking at and it made sense to me. "variable = (condition) ? true-value : false-value;"

Recording notes and rereading some older documents on where we were and where we came from (business wise). Heather came down and we talked a little bit about the current state of adilas. We chatted for a good 45 minutes. The good, the bad, the ugly, the potential, the sequence of events, cause and effect relationships, etc. Good conversation.

See elements of time # 8089 for notes from a history bio and old web page with tons of verbage and details about some our our origins, as a company. I would really like our guys and gals to know what we are doing and where we are going. It's worth money to me to be on the same page (virtually) with our team.

John asked me for some file over email. I knew that we had them, but I hadn't been able to get back to them and review them. The files in question were tons of great R&D files on fracture done by Jonathan Wells. I started to review the files and got completely sucked in and inspired by the level of detail, the work and research that was done, and the possibilities. Great stuff. Anybody who is researching the fracture project, needs to review those Adobe XD files. Wonder full. The originals were done between 2019 and 2020. There are numerous screenshots that have been posted, but the real value is in the raw files, including the clickable desktop previews (mini click through slides and links on the actual documents).

Towards the end of this session, Heather (my wife) came down to talk with me. I showed her some of the things that I was playing with and learning about. Great enhancements and much easier to consume and digest. I loved working with Jonathan Wells, sad that it had to end (time and budgets), but we got a lot of great stuff (R&D, research, mock-ups, ideas, and direction) from the efforts.

See attached for a small list of XD files that I was looking at.

Working with Alan on a backend database project. We were flipping a table name and it was giving us problems due to master database privileges and permissions. We got in there and were able to get it fixed. Emails and small updates.

I also wanted to record a small conversation between Steve and I on the GoToMeeting session this morning. We were talking about ways to encourage companies to move out of the shared environment and onto their own dedicated servers, once they reach a certain size. One of our developers was reporting that a medium sized company was creating around 6,000 new database entries per day. That was for a medium sized company. That got us thinking about some of the bigger companies and how many records they are creating per day.

I mentioned to Steve that my wife, yesterday, simply said... "Do you have a limit that requires a company to leave the shared environment?" I had to answer, no. We currently don't have any limits and/or rules in place to help us with those decisions and/or levels. While Steve and I were talking, he mentioned that his wife said a similar thing the other day as well. Kinda funny, but we didn't even think of putting in a limit and/or rule to protect ourselves. That idea had to come from the outside. Long story made short, I'll bet we'll start looking into some rules and limits and make them standard.

Out of the office for vacation and family reunion on my wife's side of the family.

• Working on the special load options for the cluster level (level 3) database structure. Going table by table and adding custom code and instructions.
• Being a project manager and lead developer for both the interns. I helped one intern put his clients (20,000+) online for a digital migration. We finished up and billed the client. I also helped an intern start working on a custom invoice project. We were carving up existing files and making some custom changes. We also started doing some grouping by item price and description. Fun little project. Got an intern started into his own adilas account to track time and custom projects.
• Working on the steps to create the cluster level tables and populate them with data. Creating steps to help with the process. Testing along the way. A new developer came over. We got his laptop up to speed and installed ColdFusion and MySQL database stuff. My wife was also helping me with some copying and pasting code prep.
• Working on a special counter function to help show record counts for various tables and record sets. This will be used to show progress while copying and transferring data.

• On the phone with Steve going over upcoming projects and current tweaks. We talked about 3rd party vendors, eCommerce, kiosks, custom code, and splitting databases. We also talked about options on part numbers to use the auto generated main part numbers and how that could be used. We also talked about a client and his trucking systems and possibly offering additional services for them such as accounting and payroll. Anyway, he is excited and pushing the ball forward.
• Helping my wife get setup on the next project. We are starting to document the adilas database tables.
• Got some new files from a developer. Made the changes and posted them online and emailed he and Steve with updates.
• Working on the teacher/student interface and the new behavior tracking section. Lots of work on layout options for touch screen.
• Phone calls and tech support. Lots of accounting type questions. Average costing options and special mappings for deposits and refunds.
• My sister came over to work on the database project. We spent a couple of hours writing table descriptions for the different tables. We worked on all the “P” tables like payee, parts, paycheck stubs, payee permission list, etc., etc. Great session.
• I got a call from a contact about a possible technical contact and a guy who knows code stuff and may want to do some adilas code projects. Anyway, I chatted on the phone with him for about half an hour. He has been such a good support. I would love to start using him as a project manager of sorts. He could do a great job. I'm excited to see where that could go. Good stuff.

• New logos for a client.
• On the phone with a client. We went over tons of different scenarios on the balance sheet. Including distributions, loans, paid in capital, outside funding, etc Good little session.
• Small changes to a client contract. Added new credit hours and posted the changes online. No charge.
• More logo work for a client. Emails and follow-up.
• Jumping back into the full database copy and scripting all of the tables out. Started on the populate process. This pulls data from a master database and pushes new records to a new solar system. Both my sister and my wife were prepping files.
• Reviewing brainstorming notes for the full database copy project. Lots of loose pages with notes clear back from December of 2013 about different levels and pieces that are needed. Good review. A developer was over tonight helping with copying and posting code. Good stuff.

• Working with both my wife and sister on database updates and SQL update statements. More prep work for doing full database copies. Also working on adding database indexes to all sort orders and field status values. This will help when doing database queries.
• Working on database code for new clusters. A cluster is a box, server, or domain level structure. It goes:
  -Level 1 – Universe,
  -Level 2 – Galaxies (linked servers),
  -Level 3 – Clusters (individual servers, boxes, or domains),
  -Level 4 – Solar Systems (databases inside of a cluster or box),
  -Level 5 – Individual Worlds (corporations inside of a database or solar system). The levels go all the way to 10 but we only needed the top 5 for this entry.
• On the phone with Steve going over things. We talked about options for dynamic css (cascading style sheets), 3rd party skins, and interface pieces. We also talked about upcoming projects, progress on the database project, and the use of API socket connections in the near future. We are seeing a large shift towards full API requests and access to backend data pieces.
• Planning, paying bills, and recording notes.
• Making decisions on where to put certain tables that play both at the cluster level and at the solar system level. Did some research on existing table structure and layout. Checking for dependencies between tables for certain joins on tables.

• Reviewing notes in my notebook.
• Fixing default sort orders for images and photos. Part of the database clean-up. Adding photo caption counters to upload pages. Fixing all of the photo galleries to include a caption character counter and new default sort value. Also doing some page navigation clean-ups.
• Working with a developer and my wife on formatting prep files for the new database creation. More work on standardizing photo gallery and photo upload pages. Posted all new photo gallery pages up and online. Found a small error in the caption size for elements of time. Fixed the field size (expanded it) an did some light testing. Both the developer and my wife helped work on database stuff and prepping files for me. Great help and future time saver.

• Working on a digital file conversion and update. We got a digital text file with barcodes and quantities. We had to load the text file, group it, do the math, look-up products and barcodes, check quantities, and update the system if there was a problem, etc. Got the update pushed to a live server and emailed all parties involved.
• Posting a news and update page with the highlight on the expanded chooser page (choose your custom interface).
• On the phone with Steve doing a quick update and touching base on current projects.
• Prepping SQL (database) stuff for the full solar system copy.
• Got a call from a client. I ran the inventory update for them this morning. Well, they forgot to tell me that it happened a couple days ago, so the update that I did had the wrong numbers. Anyway, we voided out the old update and ran it again with some different dates. Hopefully that fixed everything and corrected the inventory according to a date in the past. Kind of crazy...
• Emails and updates.
• Prepping files for copying the database. I had both my wife and sister working on different copy and paste formatting projects.
• Emails and light tech support.
• Prepping more database files.