After hours meeting with Wayne, Alan, John, Bryan, and I. Wayne pretty much drove and I took notes. It went for three hours. We have the first two hours recorded (see attached). The last hour, we thought that we were done and it kept going with ideas and more clarification stuff. It may be a lot to read, but I've got 5 pages of notes, all dealing with fracture and where we are heading with adilas lite. Some of these topics are deep, backend, and server and database related. Good meeting.

I have no problem saying this... I was definitely not the smartest person in the room. I've been doing this kind of stuff for over 20+ years and I was impressed. That makes me excited.

Once again, if you want to review the notes, there are a bunch of good things in there for our upcoming fracture or adilas lite project.

These are a few of my takeaways:

- We need to communicate and get some standards setup. This could be what we call things, what code to use and how it looks and acts, and other style guide level stuff.

- Our plan is to build the whole new parts and pieces into an open API socket connection level application. We could then use API sockets as well as let outside developers use the same API sockets. We talked a lot about this. This is where we want to head. The new adilas lite platform will be mostly run on API sockets.

- Rules and assignments - the concept of building the rules and then assigning who plays with those rules was a big part of the discussion. Follow a story-based design for logic, testing, etc. Make all of this data driven.

- Think generic - what is available - what do you want or need? Make everything configurable. Multiple levels of configuration. See notes.

- We will be building a very robust data dictionary and then using that in the rules, validation routines, etc. This is basically a database that shows columns, names, values, rules, defaults, and other information about those columns and/or fields. This is huge and will help us use a more data driven approach vs hardcoding all of the rules, values, and validation per column. We will have a generic set and then let each corp, location, and user tweak a copy, if they want to get that deep. If not, we will use the main master data dictionary list information. Only change and copy what is needed.

- Events and turning everything into small bite sized pieces. Very minimalistic approach. Make as much of this application asynchronous (nonlinear) as possible.

- Let's do the aggregates (data warehousing stuff) right off the bat and get those values in place and being used. We are very good at transactional data and data storage. Let's really make an effort to break into the aggregated or business intelligence (BI) levels. That is a huge goal of ours.

Went over to Bryan's house and we had a brainstorming session on his new upstairs patio. Beautiful view and good times. It rained on us but we were protected from most of it. See attached for a scan of my notes. Lots of ideas for fracture or adilas lite.

Here are a few notes:

- Mobile first - plan accordingly. Allow for mobile and desktop settings (show/hide for fields).

- Be able to setup your own data assembly line - based on what you care about. We will try to provide the pieces and modules and you can put it together how you want it and/or need it.

- Lots of talk about API sockets and small microservices.

- Lite or simple apps - for each layer - if you want more, just choose the next pieces. Play with aggregates (sums, counts, averages, maxes, mins, etc.) unless you need more details. If yes, just keep peeling back the layers.

- We have a friend that was pitching us on Deductr a long time ago (back in 2015 ish). It was a quick mobile app for simple expense tracking, simple mileage tracking, and simple categories and reports. Adilas can do so much more but we need to present it in a way that feels easy like Deductr (aka Hurdlr).

- Choose your own adventure or choose your own business process - similar concept. When I was a kid, I used to love reading the choose your own adventure books. As I grow up, what if I could do the same thing and put together my own business adventure (map it out based on needs, wants, and decisions).

- Talking about free versions of our software/web apps. We could also have or offer upgrades. If someone really wanted to play the reoccurring revenue game with us, we could allow them to sponsor and/or fund certain modules or sub modules and then pay them a reoccurring commission on clients who use those pieces. Bryan and I were talking about possible ideas and how that might work. Fun stuff!

- We talked about growth, slow and steady, and natural (organic) growth.

- At what point does the scale start tipping? What feature or add-on will really make it go? Or do we need to pull back some of the complexity and make it even more simple. If you want deeper, you just ask for it (layers) and then you get what you want vs having to have the whole thing every time.

- Lots of talk about pain points and how that tends to help with growth and being willing to pay for a solution to those pain points. If someone pays for an enhancement or feature, we tend to roll it into the mix. Kinda a piggy backing type system where one person pays for something, everyone gains (piggy backs) and then next person pays for the next enhancement. It has worked great for us. Sometimes we call it idea farming.

- Creativity is a chance - there is a possibility of failure with creative stuff - that doesn't mean don't do it - you just have to know there is a chance involved.

- It may be ok to use older code, if needed. Keep rolling forward and revamp, refactor, and rewrite as needed.

- Bryan and I also talked about API socket connections, simple website builders, easy payment solutions, dashboards, widgets, advanced reporting, and simple timeclocks. Tons of fun topics. See the attached notes for some other ideas.

Meeting with Bryan to push the flex attributes for PO's. The flex attributes allow for custom data endpoints per main group (12 main player groups). We currently only have flex attributes for customers, elements of time, and now PO's. Eventually, we want to add this same feature for each of the 12 main player groups. As a side note, originally, these flex attributes were going to be called real in-line database extensions and were going to be the big brother of the flex grid tie-ins. When we get everything out to the fracture level, we want to make sure that we have the flex attributes built out for each main player group. The main player groups are: Deposits, invoices, PO's, expense/receipts, balance sheet items, stock/units, customers, vendors, employee/users, parts/items, elements of time, and quotes.

Another thing that is really wanted, and we would like to build for fracture, is a granular level of both visibility and searchability. The clients want to be able to see everything and then be able to filter it down as well. That seems to be a reoccurring theme and request. Currently we have a number of prebuilt reports. That is great and all and needs to continue. However, to make it even better, we need to provide options on the advanced searches that show every field, every connection, allow for toggle on/off (show/hide) fields and columns, filters for each section, and options for both show and export. Once again, full visibility and full searchability. That's the goal. Adilas - all data is live and searchable.

Bryan and I got his code all merged in and pushed up to data 0 for testing.

More recording notes from 5/31/23. Fun to relive some of those memories and ideas. Lots of good stuff on that day.

Checking in on the next couple of projects. One is a repair job, another is a new build out. I've also got to get with some of the guys to push code. None of that stuff was really ready. Left a voicemail with Cory asking for priorities.

Recording notes from 5/31/23. Lots of good stuff and some new changes and ideas were going on. That is right about the time that we started the transition between ship A (current adilas platform) and ship B (fracture and adilas lite). Lots of good stuff.

As a fun side note, as I was recording some ideas... I had the idea about - what if we build out features and modules and charge accordingly? That's where we want to go anyways. We could pay a commission on those modules to whomever helped up build and fund them. Just treat it (the reoccurring commission) as part of the cost of using a specific module. Almost like a sponsor or sponsorship of a certain part of the adilas platform. See element of time # 10244 in the shop for some other ideas.

Met with Eric to look at some code. We chatted about some time zone offset questions and date/time stamps that a 3rd party was asking about. We then got into a small discussion about better data modeling (see below). Eric has worked with numerous companies that have built and destroyed whole systems. We talked about some pros and cons and where we are heading for fracture as well as ship A and ship B stuff. We then flipped over to the enterprise vendor catalog changes that Eric was working on. We did a small code review, light clean-up, and merged in some code.

Eric and I – talking about the data model (database stuff)

- Problem with the unique id's – too much reliance on the existing primary keys – switch it to combo primary keys

- Any time you repeat things, you may want to look at the data model

- Cross-corp issues – for example – cross-corp loyalty points

- Po/Invoice lines – database table – breaking large datasets into corp-specific tables – that's how we solved the performance issues – there may be a better way to do that

- Better DB conventions vs table naming for corp-specific tables

- Enterprise level – aggregates and query data

- Shareable data models – associated tables

- Problems with text-based fields that combine records – for example: customer phone numbers

- Lots of talk about associations and setting up those relationships – master lists and who has access to that data, association, and/or relationships

- Refactoring things as we are in there working on things – smaller nibbles – iteration process – keeping chipping away at it along the way

- If we have a multi-page flow - make sure we use a common standard vs every page being different. A list of set standards.

- ETL - extract, transform, load - This is part of data warehousing and we would love to do it along the way vs just at the very end. Let's plan it into the fracture or adilas lite project.

Texts, emails, and started recording notes from the end of May. I'm a little bit behind, but there is some good stuff there. I want to get it all recorded.

Meeting with Aspen and going a small review of what is happening (daily). Emails, text messages, and then recording notes for today (6/13) as well as adding in a video link for the group pivot meeting on 6/6/23.

Phone call with Cory. We had to back out some code. We fixed a known issue but created a small disconnect for a different client. Both clients are using the same report. One client offers or extends credit to their clients (invoices on account). The other one just deals with cash and needs the report to filter on a per salesperson basis and doesn't care about any other relative data. The disconnect is the date on the invoice payments. If you extend credit, the invoice payment date may be different than the actual invoice date. If you just do cash type transactions, they always match up. Anyways, we reverted some code and pushed up the old code until we can figure out a plan moving forward. I hate doing that (reverting code) but sometimes it helps calm the tech support lines. My ideal would be just fix it and let it move forward. Sometimes, if it is under pressure, people aren't very patient and thus the quick revert.

Emails and research. Meeting with John. Quick update on servers. It sounds like Wayne and John are working on a small mini project for the adilas cafe model. After that, John and I spent time working on the SWOT analysis. We were going over our strengths and weaknesses and making notes on each entry. We pretty much spent the whole time going over that. The current authoring file is on the Adobe Cloud. Lots of little comments, links, and researching out stats and what not.

Working on the daily sales and profit reports. We had a client who wanted to see all invoice payments per day, even if they didn't sell anything that day but just got some payments from invoices that were on account. We have a number or reports that already show that data. The client wanted that data to show up on a special report. The existing report only showed data based on the main invoices that happened for a specific date range. It's ok for main invoices, invoice line items, and invoice payment to have different dates. That's how we track accounts receivable (A/R's).

So, we went in and opened it up a bit more. Also added in some notes on the error messages to show any other details that were needed to help the users. Pushed up the new code and let Cory know.

Texting some of my contacts to meet for lunch or whatever. Light networking with friends and acquaintances.

Meeting with Aspen to go over parts of the plan. She ended up doing some research on fracture and I was recording notes and such.

Notes from Aspen - see below

Adilas Lite Weekly Objectives

6/12/2023–6/17/2023

1. Smooth over the relationship with Ship A

1.1. Propose prototype testing for Ship B components on Ship A

1.2. Win-win for all parties–helpful features that Ship A won't have to pay for directly, Ship B gets the assurance that their components work, Team harmony improves

2. Get Ship B Organized

2.1. Variety of Meetings, prepare documents for a more technical meeting with Wayne on the 14th

2.2. Project Management Document Summary, start on strategies

3.Complete Personal Hours, Etc.

4. Classification of Projects Under MVP and Non-MVP Categories

4.1. Helps focus efforts

4.2. Both need to be clear

4.3. MVP needs to be built with potential Non-MVP build-ins in mind

Meeting with Wayne. Talking about payments. Ways to speed checks up getting over to Portugal. We may end up helping him do remote deposits via photos of the check and speeding things up that way.

He and I talked about practical stuff. How are we going to write our code? How will things get implemented? Basically, the why, the how, the when, the how much, the what, where, and way. All of those types of questions. We really want to make sure that things get fully tested and are stable. Making some plans.

Emails and light tech support. We had a client that wanted and needs some bulk tools to remove some reoccurring elements of time. Currently, you have to remove those elements of time one by one. There are no bulk tools for destroying and/or removing events. That could be a great future build.

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.

Code review with Bryan. Working with Cory on projects and small fix on a timecard report for Steve. Working on paid projects for ship A. Notes were added into adilas timecards.

Just thinking about some ideas for financial products for adilas and adilas lite (fracture).

- We could offer short term investments - 2-5 years for payouts on investments or loans. These could be higher interest rates as we would be paying them back quicker. May need to research rates.

- We could offer long term or longer term investments - 5-50+ years - These could be lower interest rates as we would be paying them back either over longer periods or potentially letting them sit in the long term liabilities (loans and long term payables) for long time periods. They, the lender/investor would still get paid, it would be more of a long term deal where they were making money off of the interest while still having the payable on the books and financials (balance sheet).

- There are at least 4 main entities that I can think of right now. They are the main adilas, llc (main or mother ship), the adilas shop (development, IT, and R&D stuff for adilas and special projects), the adilas university (education and training entity), and the adilas marketplace that could have a number of subs underneath and/or somehow associated with it. See the adilas jelly fish model for rough sketch of the corporate structure and how they all play together. Long story short, adilas creates a number of byproducts and has a constant need for other supporting products and professional services. That's pretty cool! All of these could be their own business or entity.

- On the adilas marketplace concept, maybe treat it like virtual real estate or a mini mall type venue. Tons of different options. See attached for a small graphic of what it could be like (just a concept). I'd love to see business funding, investments, marketing, and planning to join the existing ideas of accountants, CPA's, attorneys, bookkeepers, consultants, custom code, developers, graphic design, hardware, merchant processing, sales, tech support, and other third party solutions. It could be anything, either built under the adilas umbrella and/or a complete independent third party. Tons of options there. Along with this idea... maybe treat it like a railroad. We own the railroad tracks but others can own cars, businesses, etc.

- Back to other financial products for adilas - We could offer options for ship A - current adilas. We could offer packages or options for ship B - future adilas buildout - fracture or adilas lite.

- We could offer options for sponsor for certain features. This could be all internal, approved third parties, or a mix of whatever. Small side note, I was exploring this concept more on 6/14/23 about possible sponsors for modules and features.

- This is more for me, but I'd like to meet with some of my friends to get some ideas from them. Allen Marler, Sheldon Archibald, Matt Funk, etc. Good guys that I know and that I could learn from.

Paying bills, emails, and sending out instructions on how to log time in the adilas shop. Recording notes.

A few quick notes and ideas...

- On a hike yesterday morning, I was thinking about the adilas cafe. Imagine a person sitting down looking at a menu or a person looking at a digital menu board. What do you want? What do you want to do? Our menus may not be food items, but it could be what would you like to see? Do? etc.

- What if we offered our business functions such as CRM (customer relationship management) or POS (point of sale) options vs customers, invoices, PO's, items, etc. Basically, we have 12 business functions that we offer. We also have 12 business application players that help us get the business functions that we want. Maybe just some different ways to pitch or let our users choose what they want to do or see.

- I'd like to setup some rules for participating in the new build out (ship B). This is part of the bigger community effort. I'd like each person to be able to make their own timecards (already available, just need a small instruction doc to line it out). All actual hours will be held in sub dates and times (subs of the main element of time). I'd like to tie it out to an expense/receipt so that it goes into the accounts payable (A/P's). We could then clean out those payables weekly, monthly, etc. as needed. If something sits in the payables for over six months, we ask the person if they want to roll that over to the balance sheet as a form of investment. If yes, it would then start accruing interest and be held similar to a loan or investment. We could pay simple interest of 5% annually (just guessing at that number right now).

- If that model works well for our internal team, when we are ready, and if we want to, we could do something similar to potential approved outside parties. This needs more thought, but I wanted to put it out there. This would be an even deeper community effort of sorts. We would still setup rules, control things, but I have no problem with others who want to help and/or help build it out. Along those same lines, we would make sure that the rules and who they reported to (and any other rules or specs) would be assigned and set forth.

- Flipping over to ship A (existing adilas platform or application). What about an MVP for ship A? Getting that fully done could pay some major dividends. It could also help smooth things out and create harmony and unity. I would really like that. Here is a quick link to a possible MVP plan for the current adilas system.

- Only run as fast as you are able.

- I was thinking about the SBA loan. I would love to get it paid off or at least help pay it down. It's not huge, but it would help with the stress load.

Prep work for getting the guys and gals to log their hours in the adilas shop for ship B (adilas lite or facture). Setting up permissions for time, special reports, and checking each user to make sure that they had the correct permissions.

Met with my sister and my mom. Both have small little shops and want to sell things online and use things like Venmo and PayPal to get paid. Super simple ecommerce needs. Another thing that they really needed was someone to help them. They can both text, email, shoot pictures, and do other phone and computer stuff. They don't know how to make business cards, crop graphics, and/or setup merchant processing with store fronts.

Anyways, I thought that it was a great meeting and really helped me see the need for helping some of the small independent vendors and mom and pop shops sell their stuff. We could easily handle what they want... it's just a mater of making it easy and simple to do.

Futuristically, this may be a great little thing for the adilas marketplace. I would love to see a spot where a user/vendor could add their items, list them, we help them track things, and then we do all of the ecommerce stuff and get them paid out (with a small fee to make it all happen). We could easily do that.

Meeting with Aspen. She was doing a summary of the notes from our intro meeting the other day (6/6/23). See element of time # 10221 in the shop for the summary. I was recording notes and then going over the summary with Aspen. Quick but good meeting.

Adilas Lite Concepts

• a slimmer, prettier, more stable model--core in particular is very stable
• begins as basic skins, then is highly customizable--clients can choose to use only the certain pieces that meet their needs
• has defined prices and is built to be profitable
• built with room for expansions, future developments in technology, and is white label capable

To Do

• get specific about what documents/sub plans belong in the larger plan/proposal/blueprint
• set up Adilas Lite team meeting time; clarify roles and management
• clarity blockades to sales by connecting with sales team and clients
• market research, risk mitigation planning, clarify SBA loan liabilities
• be thinking of marketing strategies/aspects that would get investors excited
• keep Ship A running and profitable

Paying a few more bills and recording notes. Worked on notes and entries from 6/5/23 and 6/6/23. Lots of crazy days.

Also, as a side note, I ran across some entries on watchers and feeders and doing daily category sums, counts, and other data per location, per day, per category. That may be something that we look back into for fracture.

Code review with Bryan. Looking at the super sub invoice line item search. Going over sort options. Looking at form params and matching things up. Light refining of the back and forth - refine my search options. Talking about being able to save the reports to help with saving steps. He was going to keep adding to the page features and then get back with me.

Checking on and paying bills.

Quick phone call with Cory to get the next project. Reaching out to Bryan to setup a meeting time. Jumped on a GoToMeeting session with Bryan. Light code review. He was going to fix a few things and then we were going to get back together.

Recording notes from today. For some reason, today was a bit more draining than some of the other days. All part of the game.

Emails and giving Bryan a small assignment for helping with ship B stuff. Bryan would like to help us out. I also read a bigger email from Alan about teams and some of the pros and cons of running with a specialized team. He would like to help code, lead, do project management, and be part of the team that does the system architecture stuff. I sent Alan a reply and said, great, let's define your role and involvement. Good stuff!

Another session working on the AFB timeclock project. This is a small unmanned, no login required, timeclock where a users just enters their user id and the system clocks them in/out. Kinda like a standalone dummy terminal just for clocking in/out. Anyways, made some changes and did some testing. Changed some query names and added some new logic to make sure that everything passed the validation and flow. Pushed up the code and emailed the client.

Back on the AFB timeclock project. A client had put in a request, and we were going to look deeper into it to see if we could determine what was going on. For the record, I couldn't make it fail but we tightened it up a bit more anyways. Spent time reading the emails and reading over the code, logic, and flow. Wrote down a few ideas of things to try.

Met a friend for lunch to talk about some of the ins and outs of banking and loans. My friend's name was Mike Hall, former banker for years and years. He is now retired. He was a master and even won a number of different recognitions and awards. I had a bunch of questions for him, and we chatted after finishing our lunch. Here are some of the things that I learned.

- Sell the vision - it really helps if you can transfer the vision to others - Mike talked about a client that would take him out to the site (physical location) and show him what he was thinking. Any way to help show that vision.

- Be excited about it - You've got to love it - Having that real entrepreneurial spirit

- He had clients that would bring in others to help pitch the pitch - key contacts, clients, end users, etc.

- Numbers are numbers, very black and white. Eventually it comes down to the person who is pitching it and/or the person who has to carry the weight (financial burden). Sometimes the person's attitude can tip the scales. Say the numbers are 50/50 (could go either way), do they believe in the person (character).

- Don't overkill on the numbers. Help them see the intangibles. That is huge - what benefits will this bring, what are the cause and effects, what happens that is hard to place a number on, etc.

- Collateral is a big piece. Another big one is cash flow. You can have a great idea that is making money but it you can't cash flow, it tends to die.

- We talked about Sears and JC Penny's and how they had the entire catalog market - they were set. Eventually they went under due to be so tied to brick-and-mortar stores vs going digital like Amazon (using technology). You got to be willing to change.

- If there is some set criteria, make sure that you hit it. After that, the banker tends to make or go off of gut feeling on how well it will do.

- We talked about relationships (with your banker). If you have a good relationship, it becomes easier to talk about the hard conversations and/or give insight if things are going well or not so well. Bankers don't like it when a missed payment is the first sign of trouble. They would much rather have a good relationship (open) with you and your business.

- We talked about investors and venture capital (VC) stuff. He said, there tends to be good VC guys and bad VC guys. He hasn't met too many that are in the middle. He was saying be really careful of companies that stack the deck. Is it a win/win or is a winner take all (super one-sided, especially for failure). We also talked about private capital or private equity.

- Keep the expectations real. It's not a war - us vs them. Play well together (meaning investors and borrowers or owners).

- Make sure it's a good fit. It's ok to agree to move on and play/transact with other lenders.

Quick phone call with John. We jumped on the GoToMeeting. Sean was on there and asked about the group meeting about the pivot that we had last night. We reported to him. I then helped John get passed a small payroll issue that he was having on his local box. I did some checking on an employee/co-owner draw and gathered some history info. Quick phone call with Shari O. to chat about the meeting. She will pass me over the recording when it gets uploaded. I then sent out an email to all of the guys/gals with the notes from last night's meeting.

Group intro meeting for Ship A and Ship B - current adilas (ship A) and where we want to take adilas to create the next level (fracture or adilas lite - aka Ship B). We had 10 people on the call/meeting. I took a bunch of notes, Aspen took some notes, and we recorded it. See attached. After the main meeting, a few of us hung around expressing other ideas and then after everyone else left, Aspen and I had a small chat.

Notes from Aspen and Brandon talking after everyone had left:

- Start emphasizing what we are doing

- Fixing the scary things (rounding off corners and refining things)

- She (Aspen) would like to try to pitch it a bit (build it up and be able to help pitch it)

- Help Steve with a viable product and plan (MVP's) that he can sell. Help him to see that he can sell anything, including things that are poorly planned out. Imagine what he could do if we gave him something to work with (MVP's - minimal viable product, plan, person, etc.).

Reviewing with Aspen and going over the adilas lite group meeting introduction and agenda. I made a new sales graph for adilas revenue since 2008 to current. That was kinda fun.

John and I had a great session working on a S.W.O.T. (swot) analysis - that stands for strengths, weaknesses, opportunities, and threats. You basically have a brainstorming session and list out different things under each category. We made some pretty good lists. Many of the same things could be viewed as both strengths and weaknesses. There was quite a bit of crossover between the different categories and topics.

John was working Adobe XD while I was listing things out. We had small conversations about each section. It was really fun. I took a small screenshot (not even a fraction of it). The document still needs some refining and work, but a great start.

Right at the end, we had the thought to do a SWOT analysis for smaller sub sections. Our first attempt was dealing with general adilas and the new fracture or adilas lite product that we are going to create. We could do a SWOT analysis for the main adilas (ship A), fracture (ship B or adilas lite), adilas university, adilas marketplace, our development team, etc. It might be nice to break things down a bit.

Reading some great poems that my dad sent to me. Went out to the lake to read them just to be outside. See attached.

Small ideas - what if we did some small sessions or workshops to help small business owners get setup with a website and simple ecommerce stuff? We could help them, hold their hands, and give them access to the ecommerce world. We could do this one-on-one or we could do small classes and then help them afterwards, one-on-one. Basically, make it easy and give them step-by-step instructions. The more intuitive, the better. Maybe even provide small web templates for them to use to setup other pages for a simple website. It may also be nice to tie it in with merchant processing or whatever. The whole package as a mini product.

All kinds of little things. Emails and reviewing the adilas docs. John had been in there making some changes. Sent an email out about the pivot group meeting tonight to go over ship A and ship B stuff.

Small notes for me - There is a huge value in education alone. If you combine education, training, and maintenance, you have a huge piece of the puzzle. Those pieces will help support the whole. I added in a few research links to our Google doc for master plan research.

Meeting with Aspen. We reviewed notes and made some new plans. See full sheets of paper. We have 5 of them. See attached. She was making them into more solid documents and plans.

Touching base with John on the plan and progress there. We did some planning and brainstorming. We talked about paper and pencil/pen and what other tools are available. John was showing me some flow chart drawing apps like draw.io (diagrams). We talked a lot about the words light or lite and what that means. We talked about different levels like in skiing and snowboarding. You have true beginners, greens, blues, blacks, double blacks, and orange (freestyle or terrain parks). Basically, beginner, intermediate, advanced, and super advanced (custom).

 Our first major plan is to help funnel down some of the existing entries from the developer's notebook into smaller categories and such. As a fun side note, dealing with plans and docs, John has already done some of this type of stuff and work for some of his school projects. We may tap into that as some resources.

As a request, John wants me to start digitizing things earlier. I tend to use pen and paper and then digitize things after the fact. It may depend on what is happening and what the things are. sometimes my pen and paper model is super fast and effective. John and I spent the rest of the session going over ideas for business plans and what that will take. We talked about doing a S.W.O.T. analysis tomorrow. That stands for strengths, weaknesses, opportunities, and threats (swot).

We talked about who may play what roles, going forward. We really want to build things that will be stable. That includes clustering, mirrors, back-ups, and enterprise level capabilities. We also need it to be sustainable, who will support it, build it, sell it, etc. (statement and a question). We need to build those pieces into the mix. Building the dream together.

Phone calls, texts, and reaching out to some of my contacts. I'd like to reach out to Sharik Peck, Aaron Hill, Jonathan Johnson, Mike Hall, and Josh Wheeler - to start with. Maybe others later on.

Brainstorming on quick and small ecommerce packages. And then help them get it all setup and going. Kinda a free trial basis for a couple of months. Work some magic to do some quick sprints if needed (custom or general code work to help them out).

I also sent a big text to Steve to tell him yes, I'm planning on running with ship B (adilas lite). I told him last week that I would officially let him know on Monday what my decision was. Well, this was it. I'm in!

Random Monday morning. Phone call with John, going over ideas and game plan. Phone call with Cory to get a new project. I'm going to be fixing the AFB timeclock app. Checked in on the GoToMeeting session. Chatted with both John and Sean on the GoToMeeting session. I then got on a phone call with my sister. She has a number of small items that she would like to sell online through ecommerce.

- People over things

- People need help - for example, my sister and her little business. It's almost too small for anybody else to care about.

- Barter system - My sister is a master at that - "Come shopping at my house" - she has all kinds of arts and crafts that she makes, builds, and sews. Super creative. Along those same lines, maybe we could say something like "Come shopping at my software application". We could barter, trade, buy, sell, or whatever. Almost our own little adilas marketplace (of sorts). We have a lot to offer and goods and services could be bought and sold with more than just normal money. Fun idea.

Recording notes from 5/30/23.

Just some thoughts going through my head...

- Mini or free versions for user/employee timeclocks, project timecards, or simple POS (point of sale) stuff like Square or Clover. Maybe use Stripe, barcodes, receipt printers (quick and easy hardware options), and touch and/or mobile ready. Super simple options. These could be some great gateways or doorways into the bigger adilas system.

- What about simple things for every main player without going to the financial level? That would be super cool.

- As an example, say a real object takes 3-4 steps. I'm thinking about just doing steps 1 and 2 or even just step 1. Keep it super simple. Once again, this is just an example. The actual number of steps may vary based on what we are trying to do. Simple expense tracking, simple invoice or sale, simple declaration of some kind.

- On these simple transactions, what if we could show some super simple account or financials? Keep stepping closer and closer and/or prompt the user to see the next steps to get the whole process.

- That's another way to think of a "lite" version for adilas lite. Start there and then build the next step and then the next. Keep it going, little by little.

Recording notes from 5/29/23. Our users really need good tools to get their work and stuff done.

This is for me - I went and visited Dorthy Marshall today. We chatted and she is getting older. She has a trilogy that she wants to finish. Just thinking that it would be fun to help other people accomplish their dreams.

Recording notes from 5/25/23. Sent an email to Brandon Mull (see attached) about world building and a sci-fi story idea about a small computer software company that is building a dream app and discovers world building along the way. Kinda fun.

Spent hours trying to catch up on emails.

We really need to do something to help with the adilas email services. It is becoming a handicap and an issue. When the servers are up, it works great, but when the server is down, no good. We don't control that server and that's the problem. We may need to commission a new server and/or move some things around.

Recording notes back from 5/23/23. You should see my stack of post-it notes. Big (tons of post-it notes that need to be recorded).

- Some ideas on a new name for the adilas system - adilas express, adilas quick opps

- We may need to budget for some more people to help us out.

- A mini or free version of adilas. Maybe timecards for employees or project time cards.

- How can I get the developer's notebook to make money or provide funding right now? We have so many entries and some good stuff. Maybe just ask and have someone put the info into the right place. Going back to Harry's ideas of piece work.

- What about using AI (artificial intelligence) to help filter and come up with data? Feed it what we want and ask for a summary. Just ideas.

Meeting with Aspen. We worked on an outline for the meeting on Tuesday with the rest of the team. We have lots of planning ahead of us, but we have to figure out first things first. Our current goal is getting things ready for the Tuesday team meeting. See attached for some handwritten notes.

- I'm stepping down as the lead developer. My new title will be the project coordinator for the adilas lite project.

- Note for me - stick with wireframes and pencil and pen drawings for right now. Enough to get things started. We'll refine it later on and make it look awesome.

As a side note, Aspen is good at organizing things. I'm excited to tap into that a bit. I'm kinda all over the place sometimes. Just part of who I am... :)

This didn't happen with everything else going on. Busy day.

Emails and personal phone calls to key adilas players. Touching base and answering questions about some of the new pivot stuff. It's all new for everyone. Trying to help where I can.

Phone call with Steve to go over hours and commitment for adilas (ship A stuff). I wanted to chat with him and ask permission to have a team meeting to discuss direction, options, and next steps. I've got a bunch of other notes... not sure if they were before the phone call with Steve, during, or after. I'm recording these notes on 6/24/23 from post-it notes that I made on 6/1/23. Anyways, here are some of my notes.

- Look for it - Seek and ye shall find - What are you looking for? Often, you find what you are looking for (good, bad, ill, faults, goodness, blessings, etc.).

- Ask for it - Knock and it shall be opened unto you.

- Bring what you can and throw it in the pot - We're making stone soup.

- Following a dream - The next phase or step of the journey

- Plans for adilas percentages - 20% of my percentages to go to help both teams A and B (normal adilas - ship A and fracture or ship B). 5% for getting the plan prepped and ready. 5% getting the funding. 5% for releasing an MVP (minimal viable product), and then 5% for ROI (return on investment). The ROI part was right from Steve during our conversation. I remember that much. That was brilliant.

- All of us would like to be able to fully turn all modules on/off at any time. That would be huge.

- I will give adilas (ship A) 10 hours a week. The rest of the time I will be working on ship B (fracture stuff).

- My biggest job is helping and dealing with people - the code and projects and products come later.

New transition today. I popped onto the morning meeting because that is what I normally did. I let the guys know that I wasn't going to be doing that any more. Sean was on the meeting and we chatted for a bit. By way of an update, he is doing great working with the dynamic adilas label builder. He is also willing to do some checking out of what our competitors are doing and providing me some competitive research. Nothing too huge.

John joined the meeting, and we were looking at some mock-ups. We would like to allow our users to interact with options to setup their own space, look and feel, etc. We would also like to do some early prototyping. Get it out and in their hands. Even things like settings for click vs hoover and other simple choices that affect their space (what they do and use - their space, their flow). We already have a bunch that we have paid for and haven't been able to use it yet. We have a ton of R&D stuff that Jonathan Wells did in Adobe XD for fracture, adilas cafe, and a new shopping cart.

A picture is worth a thousand words. Dramatize it, push up XD docs from Chuck on the content server. We have done tons of really good R&D. Let's use that. This is how we are going to get fracture up and going and off the ground.

John and I talked about trying to centralize all of the data and assets. I have a bunch of it. We have pushed up a bunch to the adilas content server. We also still have quite a few assets and raw authoring files with the guys/gals who made them - Jonathan Wells, Chuck, Russell, Marisa, etc.

As part of our discussion, John was showing me some of the projects that he worked on for school. He's got business design docs, pitches, proposals, flow charts, etc. I'd like to tap into some of those planning and system scope documents. Not necessarily for his project, but more for what we could do for our projects. Once again, show them don't tell them. That is huge and reoccurring theme. Show them, don't tell them.

Here are some other notes from our meeting:

- We could make some awesome customizable dashboards

- Realtime data on what is going on (tables, graphs, charts, and quick aggregates), help them see everything without overwhelming them. Full visibility.

- "Show them" and then do it over and over again.

- Talking about dream salaries between John and I. Where would you like to be, salary wise?

- Keep idea farming - that's what we do

- Shari O. joined the meeting. She loves to do some gaming. I'd love for her to come up with some ideas on how to turn adilas and the daily work into a game of sorts (the game of business). Shari O. said that she could do some light research and maybe come up with some ideas. As we were talking, she said that she changes games based on moods. That's good information. We may want to come up with something similar - what mood are you in? Ok, let's play that way. This is just a dream right now. I'd like to see where it goes.

- Keep gathering things together. Eventually, we will make our own world.

- More ideas for the application and/or system - education mode, game mode, nuts and bolts mode (just get it done - speed mode).

- More talks with Shari O. about Facebook groups, other social groups, having meetings, setting up schedules, and giving people power to run what they want to do. Make the whole thing a team effort.

Paying bills, emails, and brainstorming. It's been a super full day.

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!

Meeting with Bryan on the super sub invoice line item search page project. Lots of new form fields and filters. We were talking about flow and processes. What comes first and how do we pre-load and filter that data in an effective way?

Sean and I talking about the new pivot with adilas ship 1 (ship a) and ship 2 (ship b) - an email that we got from Steve this morning. Sean is going to be looking at some other business software packages and sending me ideas and screenshots (light research and getting ideas). We had a good little talk.

The rest of these notes were just thoughts, ideas, and notes after talking with Steve. My mind was just gushing with thoughts, emotions, ideas, worries, excitement, etc. The whole gamut or range of feelings.

- Operations has to lead the accounting. You can have operations without accounting, but you can't have good accounting without operations.

- Jumped on a call with Steve - Good chat - It felt like he was coaching me and giving me some great advice. Almost master to apprentice type talk.

- Keep heading north - that has been our general business plan - keep heading north!

- Steve was talking about a limited team (working on his house) and how effective that was - lessons learned

- This is an abundant model - we are not limited to just what we have and/or is right in front of us - tons of options

- Track everything - time, hours, plans, money, notes, etc. Track everything!

- Creating a super tight plan - almost a watertight level - As part of that, make sure and leave some flexibility into the mix. Things always keep changing.

- As of June 1st (6/1/23) no more adilas funding on ship B (adilas lite or fracture)

- Steve is going to be taking care of ship A (current adilas platform) and I'm going to be dreaming, building, and working on ship B (adilas lite and fracture).

- Going for dreams sometimes takes blood, sweat, and tears - be ready for that

- Lots of experimenting, playing, and messing around. It's all part of the game.

- Selling the sizzle - every restaurant that has steaks can sell the steaks. The one who really makes it sells the sizzle, not the steaks.

- Along with the blood, sweat, and tears - Steve was saying that there may be a lot of unpaid labor that needs to happen and go on before it really turns the corner. Keep tracking everything.

- So many pieces - we are in a complex industry - lots to do and coordinate

- You will always need customer service stuff. Customer care, support, deployment, etc. Remember the service piece.

- Steve has been a great salesperson - We are where we are because of him selling stuff - All kinds of stuff

- We would like to create a succession plan. Not necessarily an exit plan but more of a succession plan.

- We talked about ownership percentages and sub plans for distributing some of that equity and ownership percentages.

- Conflict of somebody spending money we didn't have - that causes stress

- Being mentally tough - easier said than done when it really comes down to it

- Suppressing things (good and bad) and letting the tiger out of the cage

- Removing a roadblock

- Being a participant - Get in there and play the game - Be there and participate

- "Icing" - That goes a long way - Easy, simple, pretty

- Not putting yourself in a box

- We need more than a business plan - Be willing to rewrite the business plan 3 or more times. That's ok!

- I gave Steve an analogy of him pushing me out of the train, at the same time, him saying good luck, and me saying thank you... Kinda funny!

- The plan will keep evolving

- Learning to fall down - That's part of many of the games we play - Get in there and learn to play!