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.

I had a few fun ideas over the weekend. These are mostly dealing with a transition to pitch and sell what we have. Often, I keep looking forward to this view of the future where certain things fall into place. I hope that I'm right, but I think that I need to roll with what we have, right now, and then see if that can help us get to that future vision. I tend to prep and prep and prep and maybe even some more prep... Part of my personality. I want it to be nice, awesome, and tight. For now, we may have to roll with it a little bit, vs trying to cross every T and dot every I. Here we go... :)

Here are some of my notes - these are from 1/25/26 and 1/26/26:

- Be honest about what we are doing. Tell it like it is vs just paining the picture of the future. We have come a long way.

- Be our style - emphasis on "our" style

- Think audience - small to medium - for clients, investors, and entrepreneurs

- List out the investment options - show the whole gamut (scope). Think all of the business functions, sub parts of the adilas lite (fracture) plan, and the known areas for investment opportunities. Say someone was interested in education, AI integrations, POS (point of sale) functionality, CRM, CMS, ERP, ecommerce, scheduling, custom code, industry specific skins, marketing, sales, etc. List them all out.

- Point them (interested people) to the web for more details.

- Explain the push window (date range for trying to raise capital).

- Ask them to share with friends, family, and known acquaintances - we are looking for those beginners and lower intermediate investors.

- If they join in, become part of the family, we could give them view only access into the adilas backend. Make sure that they can see what they want to, but also keep and make it safe.

- Big fish vs smaller fish - we want to keep some of our culture.

- Light history about where we came from and what we have been doing.

- Small stats on what we are doing right now... monthly reoccurring revenue, accounts receivable (A/R's), team size, accounts payable (A/P's), etc. Let them see the picture.

- Why the push... explain the why

- What is our culture - explain a little bit about our culture

- What are the goals and vision

- Grassroots and community oriented

- Introduce yourself - this has been my career for the past 20+ years - what do you love and why

- Trying to build a community where others can share and participate

- For me, on the community funded projects - open it up more - clean it up - flag and tag projects to certain key categories - maybe even reopen the actual donation and payment options. We had shut that off due to security and hackers. We could spend some time and tighten that up. That would be fun.

- Reread my church notebook from 1/25/26. I took some good notes and there were some good talks and discussions.

- One of the songs we sang today was hymn 237 - "Do What Is Right". I like that song and it hit a little bit different today. If you aren't sure what to do, do what is right and let the consequences follow. Great message.

- I saw a cool flyer at church today. It was well designed. I was looking at it and trying to get some ideas (layouts and designs). Maybe a fun side with some good whitespace, a nice design, and a simple message. Then the other side could have more information.

- This was huge for me... use existing pieces and artwork - graphics from the teaching gallery, main website, and the presentation gallery - tie it all together.

- If I were holding someone's hand (virtually)... what would I say or tell them? Go in that direction.

- Building a house - analogy - you prep, you plan, you build the outside (earlier versions), and then you work on the inside and do finish work. That is basically what we are doing with the adilas.biz project.

- 3-part pitch deck - introduction, current offerings, and future plans and future buildout

New notes from 1/26/26

- See the text message that I sent to myself. My dad and I were grabbing a breakfast burrito. He was rattling off a bunch of names and possible contacts. That will be a great start.

- Post the BATC interview videos - maybe some other ones as well - just a thought - link to Google Drive adilas videos

- On a call earlier this morning... I mentioned that the adilas part or the software that we were building was the only thing that survived the downturn (recession) in 2008/09 from the old Morning Start Automotive, Inc. business (used car and trailer dealership that Steve owned).

- I reread some notes from yesterday... I liked these ones... people - the plan is people, the purpose is people - and bringing people to Christ and helping people to the next step

- On profitability - we are saying 40% cost, the rest (other 60%) is currently being dumped into development and R&D

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

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.

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!

This is mostly for me... but last night I couldn't sleep very well. I kept having the idea that I needed to include others and other business owners in the fracture project. This could be helping them build out their own systems and/or helping them get started on the white label journey. Anyways, meeting with them, helping them get things lined out, making plans, and getting their feedback, ideas, and suggestions. Group or community effort of sorts.

This is by no means official, but I was thinking about a six-month planning period, six months prototyping and getting funding, and then rolling things into a two-year build out. Once again, just putting things on paper. In reality, we'll need to check scope, project requirements, and who we have that can help. Lots of other variables. That's just what I was thinking.

I know some of the local business owners at the technical college, local ski resort, a bike shuttle company, a special race event, a high-tech manufacturing facility, and my dad (great resource to a number of other business owners). Anyways, just recording this as an idea for fracture.

This may not go here, but I was also thinking, if they commit to working on the white label projects (multiple versions) I could even cut them in on a small percentage of the main adilas system. Basically, a way to get them to help us push things forward. Once again, just thoughts and ideas.

Got a call from Harry, my dad's friend. He was watching videos on how to make Facebook work for you. We have so much content, no one knows about it. Harry was pitching an idea of doing piece work for dollars (based on content, posts, videos, images, etc.). The whole thing was reusing what we already have. If we could get the right person, and pay them a piece work fee or rate, we could push out soooo much good content. It just needs the right person to virtually recycle that content and push it out in the correct channels and spots. Great idea from Harry!

Went into Smithfield to meet with my dad and his friend Harry. We chatted about updates, changes, and plans. I offered to help get them started and/or pay for an adilas power user to help them get started. It may be a great way to help people get going and get started. Basically, assign them a buddy to get them up and going and then they can take over and/or sub it out. After Harry left, I went over some new developments with my dad and lightly was pitching him on our master plan and possible ways of raising funds for adilas projects. That was kinda fun and he was a good listener and was encouraging me to keep pushing on things. We'll see how it all plays out. One of the biggest distractions is time... it takes time to make these plans and then it takes time and funds to make them happen.

Went into Smithfield to meet with Harry and my dad. Both had watched the videos on adilas university and were ready to go. We spent the 1st hour talking about options for selling part of adilas or getting outside investors. That was very helpful for me to have someone to bat things against and get some conversations going. Good stuff.

As we went further into our meeting, the value of good education and training and marketing was very plain to see. The next big question, how do we get there? After that, we flipped over and setup a new corporation and some users for Harry and his daughter. Just trying to get things started. We spent some time and did some settings, permissions, and going over defaults. We did record part of it, nothing too major. Great meeting and my head was spinning afterwards thinking about possibilities.

There were a few of us on the morning meeting. My internet kept dropping in and out. As we started the meeting, Sean and Steve were talking about 3rd party solutions and some of their needs. We are seeing a need and demand for better documentation of the adilas API sockets. We have them, we use them internally, and outside parties use them. We just need to keep giving that section some loving to really make it shine.

Steve asked me about my meeting with my dad and his friend Harry. I mentioned to them that they wanted to see rentals and reservations, as one of the first things that they wanted to know how to do. We can do it, but that too needs a little bit of work and automation. I will keep working with Bryan to keep fine tuning the elements of time and the rentals, reservations, and availability layers that we are working on.

After that, Steve asked a few code questions. He reported that he has been in conversation with some older independent adilas reps. They contacted him and may come join us, internally on our team. That would be cool!

John was showing the guys a demo of the new pages that he has been working on for new look and feel stuff. We talked about hiding some of the text in the forms and making it look simpler. As we were talking, we were telling John that some of those processes are very repetitive and once they learn it, they want to go as fast as possible. As a older side note, when we were working with Jonathan Wells, he had the idea of the education mode where you could turn on/off extra helper verbiage or helpers (handrails of sorts). Great idea.

It is amazing how fast GUI's or UI (graphical user interfaces) change. In a way, we and everyone else is competing with the big dogs as far as expectations and demands. That makes it tough. Along those lines, it would be really cool to gather more info on how our clients are using our system and what they like and don't like. We have tons of data, just no really way to process it and make an analysis of it. That would take a whole other person to really get in there and dig through settings, usage, traffic, choices, wants, needs, etc. That would be really cool but feels like one of those projects that is still out there a ways.

The last topic of the day was another plug for the datasource project and getting everyone on their own database (bus to motorcycle project). It has my vote as well.

Went into Smithfield to meet with my dad and Harry. We met for a couple of hours. They wanted a small overview. I had scribbled some ideas on a post-it note. We got through a few of the pieces. We recorded it, but halfway through, my laptop shut down and needed to be plugged in. That screwed up the video. Anyways, a good little meeting. We are going to meet again next week in order to keep pushing forward.

Prep for a meeting with my dad and his friend Harry. I made a small list on a post-it note for some ideas that I wanted to go over with them. Here are a few of the ideas and notes:

- Go over the elevator pitch for adilas

- Playing the game of add-on as a business model

- Finding pain points and coming up with solutions

- History of where we came from and how things developed over time - it's part of our story

- Demo login and letting them get in and start playing around

- MVP - minimal viable product, plan, person, presentation

- Graphics and world building concepts

- General rules and setup - what's the flow process

- Operations and accounting - horse and the cart - operations has to lead (it's the horse) and accounting follows (the cart)

- Permissions and settings - configuration

- Going over flow and processes

- Systems and relationships

- Simulating reality or simulating the real world - what really happens and why?

- Non-linear system - concept of the data assembly line

- Adilas quick search and standard navigation

- Our current goal - fill in the gaps

- Help files and videos

- Reach out and ask for help - use the whole team

Danny and Sean popped into the meeting. Nothing major going on but just talking about sales, demos, and how to put our best foot forward. We talked about getting small quick screenshots and samples to help go along with our demos. Currently, we bounce inside of a demo site, show someone around and then bounce somewhere else. I use the word bounce, and we are fine with that, but to a new user, that seems like you have to know a lot, in order to jump or bounce around. They want to know that we have certain things and want to get their hands held for the first little bit.

Because we are so flexible, it sometimes intimidates people and new users. That might be a good thing to remember for fracture (future project). Maybe setup a super simple step 1, 2, 3 process that always work (for example, the normal front door entance) and then show them how they can change that if they want to (side doors, back doors, basement doors, garage doors, etc.). Dustin was calling it handrails. I might be nice to have different training modes or education modes. If you turn it on, meaning education mode, it virtually tells you what to do. If you turn it off, you can bounce wherever you want (like normal). Almost an analogy of training wheels vs freeride or normal bike riding (without training wheels).

As a small side note, my dad (Wayne Moore) was saying the same things yesterday. We were looking at the main adilas.biz website and he was saying, I like the verbage but I want to see it (super tiny clips or screenshots). For example: It says "real time visibility and control with inventory management". Ok, what does that mean and can you quickly show me (a picture is worth a 1,000 words type mentality)? Just some quick screen shots.

As a note, there may be different levels. We may need a quick overview, a quick this is that (demo style), and then a deeper how to or let's really learn and master this. I can totally see a need for different levels of screenshots, examples, tutorials, and step-by-step walk throughs. Good stuff.

Steve, Wayne, Harry, John, and I were all on a meeting. Steve was talking with my dad (Wayne Moore) about all kinds of ideas and direction stuff. It was pretty heavy on the education and training side. Partway through the meeting, Steve had to jump on another call/meeting. I stayed on and talked with them about all kinds of stuff. See attached for some notes.

Looking into a merge request from Eric. I wrote him back after making some changes. On the phone with my dad talking about being a teacher to teach adilas courses for LinkedIn. We really need to get into the training end of stuff.

Small demo for my day (Wayne Moore) and Harry (my dad's friend). They were pitching that we need some training courses. They want to go pitch adilas, but don't feel that they know what it can do. We talked a bunch about LinkedIn training courses. See attached for some of my notes. The first part was for the demo and then we started talking about all kinds of education type options.

- Wayne - training courses - in LinkedIn - people need to see it

- Adilas course that could be as deep as we would like... overview, beginner, intermediate, advanced, deep-dive

- Helping people know what is possible

- Get people where they need to go and then come out with a skill

- YouTube is another option

- We could get a lot of traction if we help train the public on what we have

- Putting the pieces together - where do you start and where can it go (easily) and with some work (more in-depth).

- The crazy things that we are doing - everybody needs.

- Global communities

- Tapping into other resources - including going into LinkedIn - allowing them to get all of the resources (course materials) so that they could do it on their own

- Helping show the adilas world - we have to show what we have

- Just in time learning and training - being able to move from step to step (building out the whole)

- We already have pieces - we need to string it all together - at the professional level - having our own plan of how to navigate the elephant

- Wayne was really pitching the training aspect of what we have and do

- Harry - you get what you pay for - If they pay for it, they become invested and involved - time, money, etc.

- Time - that is the tricky piece - sometimes we feel like we are so busy

- The digital world of learning - certificates, learning, etc.

- Adilas keeps changing... that is part of the game

- Steve was commenting on how we used to do videos - way back - we couldn’t even get things edited before they changed

- Wayne and Steve were talking about setting up new courses on LinkedIn - Wayne will see what it takes to add in new courses

- Steve was showing them some of Danny’s adilas quick tip videos

- Funding - getting enough to get that part of the puzzle going

- Talking about invoice reminders, online payments, etc.

- Steve was showing them the warranty registration stuff - video from Chuck

- Steve was explaining how our model has changed. We used to use outside reps and consultants. Now everything is done internally, using adilas trainers

- Steve was pitching ongoing training courses for our clients.

- Wayne has a degree in curriculum and training

- Steve was showing his older YouTube player - older stuff - but still valid - we need to update it and keep it fresh

- Speed and cadence of what we are going over - full outline and layout

- Just in time online courses

- People are pretty picky - we have to capture their attention pretty quick or maybe even faster

- Keeping up with the constant changes

- From Wayne - make the world our audience! Getting the information in front of the decision makers

- We can schedule more meetings, or we are on every morning at 9:00 am on the GoToMeeting channel

- From Steve - how do we make this go forward? Plans, compensation, ideas (even out of the box).

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

After the meeting, my head was swimming. I came up with a couple of other ideas, just for fun.

- What if for training we gave a new user 3 accounts vs just one account. Here is my thinking - One could be for the start of the lesson (work area), one could be for the finish of the lesson (what is expected or a finished product), and one could be for fun (we keep whatever, their own playground). All of the other systems could be reset to any stage by rolling back a database. Assuming that the training was planned out enough to roll things backwards and forwards as needed. This could all be scripted and rolled around as needed. It would really help with training and keeping things standard.

- What about making things plane Jane type interface or only as much as is needed. Keep it simple. Just a thought.

- Being able to reset the database at any time could be really cool.

- We aren't ready for this yet, but for fracture, it sure would be cool if we could have certain settings and defaults on speed dial. Basically, if someone wants a certain setup or package, the database (aka the backend scripts) could help us flip flop things in a hurry. Currently, we have to setup all of the pieces, settings, permissions, naming conventions, show/hide, sort order, and other aliases in a manual format or fashion. That takes quite a bit of knowledge. If we could get our settings and options dialed in, that would really help and speed things up. We could configure and virtually show/hide certain things in a click of the button vs hours of individual configuration. Lots of options here. It could be size wise (tiny, small, medium, large, extra large, huge) or it could be industry specific (this for that, and this other stuff for some other industry - tons of options). Preconfigure whatever we can. If they want to still tweak things out, it all exists, it just gives them a quicker starting point.

- Not sure where to take this... but I was thinking about books and choose your own adventure type style books. If you want to do this, go to page x or y. If you want to do this other thing go to page z. What if we helped setup our training in the same manner? If you want to put this on account, do this. If you want to pay for this, do this. You get the idea.

- Train the world

- Super easy setup and configuration, you could then tweak it if needed to get super custom

Touching base with Steve and Sean. Planning and scheduling demos. Talking about getting my dad (Wayne Moore) involved in some adilas sales. He is really good at talking with people, organizing things, and taking things to the next level.

Cory and Dustin joined the meeting and we switched gears and started talking about a possible error or errors. This took quite a while. We talked about possible date picker problems and using our new date picker. Everything keeps moving. The ground we stand on is in constant motion. That seems to be our reality.

We then switched over to other projects. Cory had a list and we went through that along with multiple things from emails. We got into a discussion on the hierarchy of different settings and which ones take precedence over other things. That can get tricky. It gets even trickier when you get layers of logic involved. Anyways, making progress there.

Helping Danny with a merge to push up 30+ files that have built-in or embedded video help file links. We had to fix a small merge conflict and then pushed up the files. Steve and Sean were talking about leads, sales, the game of numbers (touches, demos, etc.), and just plain getting out there and stirring the pot.

One of the biggest problems that we have is keeping our users and clients up to date. We have people who don't even know what we have, and it's been available for years. Steve and Sean were talking about almost having to resell our existing clients on the new upgrades and changes. This in-house, virtual up sale, would be based on who is using what and who hasn't even played with the new features, permissions, or functionality. Sean was recommending that we use the system to see who is using what. We can tell, we just haven't written those pages to check on some of the different usage areas. If we use the system, that would help us figure out usage and compliance from the backend. We could then make a more targeted approach to who needs some follow-up and possibly some handholding. The goal would be to help our clients keep moving forward.

Steve was talking about a simple child's game of red light/green light and playing that with our clients. Red means no, yellow means not all the way, and green means yes or they are using it - meaning features, tools, permissions, and functionality. As a side note, we have to respect and use caution, just because we could check out what our users and clients are doing and using, doesn't mean that we should do that on every aspect. It could flip and go the wrong way and turn into spying. Not that we want it to get there, just saying, you have to be careful and only cross certain lines. This is a small poke, but if you don't define some lines, you may end up like Google and know way too much about your users (just being silly).

Our goal would be deeper customer care and helping our users be more engaged, entrenched, and/or sticky. If we help them get what they want and need, we become more needed and in demand. We want to get them all the way in, so that they love adilas and don't want to leave.

"Use technology to keep pushing our product!" - Wayne Moore, years and years ago, speaking to Steve and I. Small little quote that Steve keeps bringing up from time to time.

At the end of the session, John was showing me his super backend admin site and documentation. We talked about getting things written down and also the security risk of doing that. There are pros and cons. Wayne joined and we got into a small discussion about permissions and roles. 

Working on main elements of time and custom verbage and naming using the db_field_settings table. Lots of real values and settings as well as display names, short display names, and other custom verbage. The current time project is turning into a hybrid of new actual settings (do this or that) and tons of custom filed level settings with dynamic verbage and what not. Almost two different flavors... One is what it should do or shouldn't do and the others are what to call or name things. Interesting.

Going through pages (in the adilas site) and noting usage and which pages use what pieces of the elements of time. Planning out the new settings and where they will end up going.

I talked to my dad on the phone, he was hoping to get me back out to the campground to show the progress, but most of what I have to show right now is just planning. It's still progress, but not as spectacular as real code doing what we want. We'll get there. Anyways, I sent him an email with notes and a few links to what I was working on.

On a phone call with my dad. He is working at a church owned campground as a volunteer (service missionary). They are having major struggles keeping track of scheduling, changes, and sub amenities (things to do or schedule there at the camp - like a challenge course, an archery range, food pavilions, kitchens, special events, and service projects). We talked about a number of ways that adilas could help them virtually fill in the gaps and help them track some of the smaller pieces. They, the church, already has a booking system for the main pieces, it just isn't very easy to get in there, make changes, or keep things up to date. They, the service missionaries, are having to do data exports, printouts, spreadsheets, and tons of manual - by hand writing - changes to the schedules that they are getting. Lots of pain.

I did some planning and brainstorming on some new and older settings that we could use. Here is a small list.

- See element of time 6967 in the shop for ideas on horizontal time view reports

- Time across the top, main category down the left side, show a visual relationship based on time. Configurable horizontal grids for time.

- Name each horizontal grid template

- Be able to create new horizontal grids, assignments, filter by search criteria, edit, delete, search, view, etc. We would hope that eventually, each horizontal time view would even get its own URL address (quick and easy access).

- Possible new settings - setup times - start/end, block sizes, and what would show down the left side (people, users, customers, vendors, locations, items, hardcoded lists, etc.)

- Other settings - what will it look like? What will be pulled? Make the whole thing configurable.

Went into Smithfield to help my dad and Harry with adilas stuff. We got into inventory tracking, creating new users, and using the quick search features.

Went over to my dad's house and gave a guy a demo of adilas and what we do and can do. It was fun, we ended up talking quite a bit about potential and how this product could be used in so many instances and scenarios. Good meeting.

Meeting with Craig and Steve to go over finances, bills, ideas, and direction. The meeting started out with just Craig and I. We went over a bunch of things and then Steve joined us later on. Craig brought a fun flavor to the meeting. Steve and I have hashed over some of these things so many times, we kinda get jaded or set in our ways. It was nice to have a fresh view and someone who would pose hard or uncomfortable questions. I really enjoyed the meeting.

All of the meeting notes are on Brandon's computer. Here is a small portion of them.

- We need to find the balance point - not running faster than we are able but still pushing it

- We have been spending some monies on certain projects - we really need to get a return. For example: Research on AWS (amazon), R&D for fracture, WanderWays, SEO

- Funding options -  The main 3 are: sales, borrow, investments

- Steve was saying, we have two main choices - steer towards deployment and fully funded projects - sell stuff or pull back and just do what we can - head back into smaller waters - slim down and tighter budgets. As a side note, we even talked about cause and effect if we were to actually gain from a small dip... lose some weight.

- Failure to launch - this is a problem if you never get off the launch pad.

- Picking our battles

- There is need for what we do

- Dealing with charging for our services - $65-100/hour

- Trying to sell a new car but it keeps having issues - makes it hard to sell - people are willing to pay more for certain products if they are reliable

- Fixing the servers - question: do we need more money or what to help make it better. On the positive side, people really use our products and they hit it hard, we really push the servers that we have. It's not like nobody uses it, the opposite is true - people throw everything that they have at them... we still need more.

- Maybe stop development - we need to sell things - harder done than said... - try to switch gears - cross training - maybe change the word or phase sales into networking... connecting the dots - get some more hunters out in the field - swap people around - focus on the deployment and setup process - focus on funded projects - on the dev side

- Being able to say "STOP"

- Learning when to put our foot down - limits and levels

- Selling the current 2021 model

- Switch who we are targeting - trailer dealers, bowling pro shops, etc. - sell what we have to offer

- It's just a $100/hour - managing expectations - sometime people want a perfect number or a nicely wrapped quote or project cost. It's just $100/hour. Otherwise, we lose our shorts.

- We get pulled off on tons of outside distractions - external distractions, custom projects, and outside 3rd party solutions

- The code is splitting - new school, old school, high tech, low tech, etc. scripts, tags, functions, includes, different styles

- Having a real game plan - we really need this - a full plan and then let everybody know about it

- Fracture is a real word - a life style - part of where we live and breath - keep heading in that direction. As far as we can see, things will keep fracturing. Plan on it and build accordingly.

- Like race car driving - we need a good driver, but maybe not the best driver, especially with an attitude, they may need to go

- You can always fill a spot... (even in management) - like a bucket of water, if you put your hand in, then pull it out, it will fill back in - finding that range that fits

- There are multiple battles - in front of us

- Using a talent scout, like my dad - maybe look around at the college (talent just getting out of school) or for people who have the skills - draft

- Find and gather up the low hanging fruit

On the meeting with Steve and Danny. Going over small items, projects, and new changes. Lots of moving pieces. Steve was showing me a shopping cart demo done by Spencer (outside developer) and how cool it was.

Web link - Adilas/Main_GUI.html - demo page for the short and sweet cart

Steve was also showing me some of his cross-corp (enterprise level) vendor mapping project. It is looking good. We talked about a few tweaks, but making progress.

After Steve left, Wayne joined the meeting. We logged into some of the remote VPS servers and made a few changes. He also helped me with my local box, as it was running slow. While rebooting my local machine, I called and talked with my dad. He has done some grant writing in the past. I briefly talked to him and asked him if he would be willing to help me and play that game again. He said yes and we'll set something up. Fun stuff.

Went into Smithfield and helped setup my dad and MaKell for doing PayPal and ecommerce. We did about an hour worth of training.

Went into Smithfield to work with my mom and dad on a business called Moore Repurposing. They basically get donations and then take the items and try to sell them and/or repurpose them. They are going to be using adilas as their backend tracking solution. We spent some time talking about what is needed, how things will work, and some other overarching goals. We then sat down at the table and started writing out a virtual checklist to help them know what to and how each thing tied in to the bigger puzzle. Super fun couple of hours. We made a to do list and then started working through some of the pieces. Lots of our work was done with paper and pencil/pen to start with and then we moved to the computer once we had a plan. Good stuff.

When I got on the morning meeting. Steve and Dustin were talking about their projects and times that they could meet up and work together. They have become a great little team. That makes me really happy. Below are some notes between Steve and I. We were talking about some upcoming meetings with both Russell Moore and Jonathan Wells. Both are designers and graphics guys.

- Graphical homepages (graphical mini dashboard per main 12 player groups), custom dashboard with little widgets that could be moved around and configured per user, mix and match pallet (mini windows - movable and dockable)

- We would like to look into what it would take to build on a JavaScript framework. There are multiple frameworks out there, what does that mean, what does that look like, and how are the pieces managed between the different systems? Lots of questions.

- Projects for Russell - He could work his magic on the corp-wide settings page, 3rd party solutions page, help out Alan with the invoice due date project, and help us get more data tables in place and integrated into the system.

- Getting help from Russell on some of the snow owl theme settings for some of the older AFB headers and such. There are a number of knowns spots. One is the adilas community funded project, the snow owl theme settings, the ecommerce settings, the custom email settings.

- Looking at resources and what do we want to spend on what and how quickly could those expenditures turn around and produce some results.

- We talked about consolidating our ideas and projects, using the adilas community funded projects page, report, and section. We could used it for project management, reports, progress, and a centralized location or hub for developers, clients, reps/consultants, and others. One spot will all of the updates and progress.

- There will always be ongoing development, product refinement, and what is coming (future). The system keeps morphing out in front of us. Sometimes that is hard to predict.

- Help prepare our users for impact - this is a huge system with tons of branching options and paths.

- Keep working with Jonathan on putting together a list of what adilas can do - whitepaper/graphic/map - Getting it all organized - a virtual road map - big dumb animal pictures - this would help so much with sales.

- Helping Jonathan get more system training from myself, Shannon, and Steve. The more training that he gets, the more he will be able to start pulling all of the pieces together. We would like to keep him on the education and sales side of the equation.

- Permissions homepage and how we simplify that - currently, it is kind of a monster or as my dad says - a football field of permissions.

- Mapping out the system functions and what is available. Steve wants a map the adilas world - what do we have and how is it organized - scroll as needed - zoom in/out - etc. Use this as a training and sales tool.

- As we were talking about mapping, we jumped into some of the existing adilas maps and navigation interfaces. We talked about the adilas interactive map (vintage around 2010 ish), the GPS core interface (vintage around 2013 ish), and helping to bring that dream to life. On the newest version of the GPS core graphic, we have included some sub navigation dealing with permissions, settings, training, etc. For the record, currently, that graphic is just a small mock-up of what it could be. The real intent was to use that core interface to interact with different app modes. They could be things like data/work mode (what do you have), permissions mode (who gets to play), settings mode (how does it work or function), training mode (what can I do), usage/stats mode (show me what I've got). Anyways, some cool ideas already exist. Maybe help Jonathan keep going in that direction.

- Use the map and be able to show what new trails are coming. Steve would also love to tie the upcoming pieces out to the adilas community funded projects to help with eduction, funding resources, progress, and a centralized hub for all of our projects.

After our meeting, I spent some going over emails, recording notes, and getting caught up. Today is Monday, back at it again. Part of my process this morning was recording some notes from a couple of meetings we had on Friday. Lots of moving pieces. I'm so grateful for pen and paper and being able to scribble things down quickly and then fill things in later with all of the details. If it weren't for paper and pen, I wouldn't be able to remember enough to fill in the gaps. Great little tools.

Steve and I talking about projects and priorities. More and more pressure to get organized and get all hands on deck working in the same direction. Right now, we don't have a shortage of able body hands, we are just all over the place. We have guys on this project and that project, we have others on custom work, we have other on core projects, we have others that we don't know where they are at. We really want to keep focusing on the list, and adilas tick list. Along those lines, we setup another meeting with Cory for Thursday to keep going over the list and making adjustments as needed.

From Steve - "Not a lack of work... there may be a lack of organization."

Steve was also quoting my dad, "use technology to help you as you go along."

Anyways, we were talking about how hard it is to control certain timelines and the pull of other projects (almost distractions of sorts). Eric popped in and had a few questions. We setup some time later this week to work on special accounts (rewards, customer loyalty points, gift cards, etc.). Some times budgeting time to work on certain projects, with mixed participation, really helps. Some times if I plan time for me to work on a project by myself, it seems like a softer schedule than if someone else is committed to the same time. A buddy, on some of these projects, really helps.

New sites for:

• Chris Scholle
• Chris Johnnse 
• Dave Forbis "Foretech Services"
• Wayne Moore

Concept based sign-off procedure-we need to build it.

Reread the project management document.

• Budgets
• Plans
• Sign-offs
• Code review
• Timelines
• Client involement
• Communications
• Deployment
• Wrap-up

First $5,000 paid in by Wayne Moore - Logan, UT. 2/7/15

Second $3,000 paid in by Wayne Moore - Logan, UT. 5/4/15

Third Calvin Chipman did some internal development out to a light demo mode

Fourth: Josh Sagert did a google earth simulation tied in to cell phones.

• Recording notes in my notebook.
• Posting the new behavior tracking and teacher/student interface pieces online. Small help file graphic tweaks and light testing.
• Brainstorming notes and ideas of how adilas could really benefit teachers and educators. See notes on other pages. Lots of notes. My mind has been going nuts.
• On the phone with Steve talking about schools and teachers. Lots of good ideas.
• More brainstorming on ideas for teachers, educators, and students. Lots of fun, cool, ideas. We could really help these guys and gals out. I really think that we could help there!
• More brainstorming on schools, teachers, and educators in general. I scanned the five pages of notes and sent them to my dad and to another contact that has been helping with marketing and other aspects of adilas. I would like him to spearhead that little project.
• Working on help files for the teacher/student interface. Also modified a page to help teachers both add and view (access) data as quick as possible. Helped an intern with installing software on his new laptop.
• Paying bills and recording expenses.

1. 12 Main Application Player Groups - Customers, invoices, quotes, vendors, PO's, items or parts, stock/units, deposits, expense/receipts, employee/users, user-maintained balance sheet items, and elements of time.
2. We have photo galleries for each of the 12 main application player groups. Each gallery can hold 100 images per item or individual in the group.
3. We also have a full blown content management and digital file catalog and/or archive system for each of the 12 main application player groups. We also go further and allow files and documents to be stored and cataloged at the system level (as a whole), at the group level (by any of the 12 main application player groups), or by individuals within the different groups.
4. Another huge piece that we are doing is business world building concepts. This includes all 10 levels that we currently know about. They are: 1. Universe Level (the internet and all adilas pieces), 2. Galaxy Level (linked servers - both data and content servers), 3. Cluster Level (individual boxes, domains, or servers), 4. Solar Systems (databases within a cluster - could be one or more per box), 5. World Level (corporations, entities, and companies within a single solar system or database), 6. Location Level (stores, departments, or physical or virtual sub dividers of a corporation or business), 7. Group Level (see the main 12 application player groups listed above), 8. Individual Level (items, objects, and entities inside of a group. for example: customer 111, invoice 345, deposit 222, po 474, etc.), 9. Data Level (how and where are things stored in the database? what relationships exists? what is the story?, 10. Run all levels over "Time" (time is the current bottom level structure that we play in, on, and through. this same statement could be re-written as objects and data wrapped in time)
5. Operation lead accounting over time. Our use of time and how it plays into the whole story of what is going on. It allows for characters, relationships, overcoming trouble or problems, decisions and choices, cause and effect consequences, accountability, etc. That is where you get the whole story or being able to capture the pieces of the story. In short, we call it roll-call accounting. The system is able to go backwards and forwards over time to tell what the relationships were, are, and may be. This helps show how things were/are connected or accounted for over time. It is awesome!
6. We have taken a traditional model or business model and created a fully integrated system. You no longer have to have 4-10 different pieces of software to run your business. You can use the full adilas.biz system or platform to run your business. You have access to all of the pieces, any time, under one roof. It works because it is a system.
7. We have built the entire foundation on two main concepts. They are: permissions & settings. You can do almost anything with those two pieces. Permissions are who has access and what can they do? Settings are the how, when, how much, how many, and what to call it. This could also include show/hide, open/close, limit, defaults, etc. Settings and permissions may be applied on multiple levels. Technically, a person could add both permissions and settings on all 10 business world building concepts listed above (universe, galaxy, cluster, solar system, world, location, group, individual, data, and wrapped in time). That is a huge piece of the puzzle.
8. One last thing that really needs to be there is the ability to be flexible. No two things are the same. People and businesses want access to features, functions, data, and processes from different angles and in different ways. This means that you have to 1. Be able to catch the data. 2. Can you get at the data that you caught? This also includes options for editing or changing the data. 3. Can you show it back to the user in the way that they want it? This goes out to custom levels and deals with interface, API socket connections, webservices, feeds, imports, exports, data trafficking, flow, controls, etc. What are you looking for? What is your goal? This is the results and/or interface of the application.

1. 12 Main Application Player Groups - Customers, invoices, quotes, vendors, PO's, items or parts, stock/units, deposits, expense/receipts, employee/users, user-maintained balance sheet items, and elements of time.
2. We have photo galleries for each of the 12 main application player groups. Each gallery can hold 100 images per item or individual in the group.
3. We also have a full blown content management and digital file catalog and/or archive system for each of the 12 main application player groups. We also go further and allow files and documents to be stored and cataloged at the system level (as a whole), at the group level (by any of the 12 main application player groups), or by individuals within the different groups.
4. Another huge piece that we are doing is business world building concepts. This includes all 10 levels that we currently know about. They are: 1. Universe Level (the internet and all adilas pieces), 2. Galaxy Level (linked servers - both data and content servers), 3. Cluster Level (individual boxes, domains, or servers), 4. Solar Systems (databases within a cluster - could be one or more per box), 5. World Level (corporations, entities, and companies within a single solar system or database), 6. Location Level (stores, departments, or physical or virtual sub dividers of a corporation or business), 7. Group Level (see the main 12 application player groups listed above), 8. Individual Level (items, objects, and entities inside of a group. for example: customer 111, invoice 345, deposit 222, po 474, etc.), 9. Data Level (how and where are things stored in the database? what relationships exists? what is the story?, 10. Run all levels over "Time" (time is the current bottom level structure that we play in, on, and through, this same statement could be re-written as objects and data wrapped in time)
5. Operation led accounting over time. Our use of time and how it plays into the whole story of what is going on. It allows for characters, relationships, overcoming trouble or problems, decisions and choices, cause and effect consequences, accountability, etc. That is where you get the whole story or being able to capture the pieces of the story. In short, we call it roll-call accounting. The system is able to go backwards and forwards over time to tell what the relationships were, are, and may be. This helps show how things were/are connected or accounted for over time. It is awesome!
6. We have taken a traditional model or business model and created a fully integrated system. You no longer have to have 4-10 different pieces of software to run your business. You can use the full adilas.biz system or platform to run your business. You have access to all of the pieces, any time, under one roof. It works because it is a system.
7. We have built the entire foundation on two main concepts. They are: permissions & settings. You can do almost anything with those two pieces. Permissions are who has access and what can they do? Settings are the how, when, how much, how many, and what to call it. This could also include show/hide, open/close, limit, defaults, etc. Settings and permissions may be applied on multiple levels. Technically, a person could add both permissions and settings on all 10 business world building concepts listed above (universe, galaxy, cluster, solar system, world, location, group, individual, data, and wrapped in time). That is a huge piece of the puzzle.
8. One last thing that really needs to be there is the ability to be flexible. No two things are the same. People and businesses want access to features, functions, data, and processes from different angles and in different ways. This means that you have to 1. Be able to catch the data. 2. Can you get at the data that you caught? This also includes options for editing or changing the data. 3. Can you show it back to the user in the way that they want it? This goes out to custom levels and deals with interface, API socket connections, webservices, feeds, imports, exports, data trafficking, flow, controls, etc. What are you looking for? What is your goal? This is the results and/or interface of the application.

• Emails and writing POS (Point of Sale) tech specs.
• Emails, phone calls, and permission based tech support.
• Emails to Steve about doing numeric date indexing as a later project. To add it right now might make it hard to manage. There will still be time...
• Working on database stuff.
• Went in to Logan for a workshop on intellectual property like trade secrets, trade drivers, patents, trademarks, and copyrights. 30 miles.
• Went over to Bridgerland to meet with a guy from Garden City, Kansas. He was teaching a class on high level chemical processes for boiler and refrigeration stuff. My dad setup the meeting for us to kick the ball around a bit. Fun meeting.
• Recording notes in my notebook. I also gave a small adilas demo to the guy from Kansas. He wanted to see our website and product. Gave him a verbal quote of $2,000 for a custom piece and under $200/month.
• Working on the new database structure.