Meeting with Wayne over the GoToMeeting session. Wayne and I were going over the main login information and process. We looked at the auto login for the ecommerce site as well. Just gathering ideas. We talked about the adilas cafe options. Wayne is getting close to having some of that code done at a super entry level. He is going to work with John to get a small skin and good-looking interface put on it. Lastly, Wayne and I chatted about his brother and some possible involvement from there.

Meeting with Cory. She had a question about using the find and replace functionality for a client. We actually did the find and replace and it worked slick. It did a deep flip flop and full find and replace including histories, line items, sub inventory, etc.

Next, we spent some time looking at some data questions. Looking into a payment search question and then into employee timecards and timeclocks. We used some existing tools and also did some queries behind the scenes to look at raw data.

On the phone with Bryan to go over tables, joins, and options for pulling in sub inventory. It can get pretty deep, if you are starting from an existing query or even a brand new query.

Lunch meeting with Jonathan Johnson from Epic Enterprises. Jonathan is a business consultant here locally in the Cache Valley, Utah area. Great little meeting and he was asking some great questions and feelers to check out parts and pieces of my plan for ship B, fracture, or adilas lite. We talked about pieces of the business plan and how to plan things out and proceed.

- One of the main topics was dealing with talent and getting excellent talent to help run the business.

- Went over our rough plan and talked through steps of the plan. See elements of time # 10179 for more details.

1. Company Structure - Adilas Jelly Fish Model
2. Product Development - Adilas Value Add-On Core Model
3. Education & Training - Internal and External - Adilas University
4. Community & Outside 3rd Party Solutions - Adilas Marketplace
5. Social & Efficiency Options - Adilas Cafe & Community
6. Deeper Product Development - Adilas Lite - Fracture Project
7. Budgets, Finances, Marketing, & Sales - Other Business Plans

- Lots of talk about division, departments, and managing the entity and the projects. Defining those roles and what is needed. Once that is finished, we will put or assign/invite the who (people and talent) to the what.

- We talked a lot about inviting and enticing the talent. Not all of the talent will be hourly or employee level people. Some of the talent or high-end knowledge workers contribute in different ways. That was a small paradigm shift for me, thinking wise. More of projects and contributions vs hours and physical output.

- What needs to be done for the product development pieces - plans, marketing, sales, and roll outs.

- Talking about building out a pitch deck to help pitch the project and product (the whole package).

- 5 main personality types - There are five major roles that need to be fulfilled in a company. Instead of just roles, ideally, you actually have people in place who can carry each of these roles and own it. Otherwise, you just have a smaller number wearing multiple hats. The five people are: An organizer, a doer, a creative type, a consultant, and a salesman. The goal is to align talents with tasks. I grabbed this bullet point from entry # 5295 - another meeting with Jonathan Johnson (early on, back in 2019).

- Talking about the root words in authority (author or create), accountability (count or manage), and responsibility (respond or react). Who does what and how that all plays into the mix.

- See attached for a napkin with some notes on it - Here is what Jonathan wanted me to do - 4 steps he wants me to work on... 1. Define the division and structure of the company, 2. Invite the talent to fill the roles defined, 3. Product development MVP, and 4. Build the pitch deck. All of these need to be at least good enough. Shooting for an MVP level on all of them.

Meeting with Alan on defining roles and responsibilities for parts of the adilas jelly fish model. See element of time # 2284 inside of adilas for details. Not finished yet but some great discussions.

Master Adilas Plan - Jellyfish Model

- The adilas jellyfish model - covers almost all of the departments and sub sections of what we are trying to be as a company. It is not the main product, but more of our internal and external departments, areas, and general areas that we will keep refining and working on.

- Possible numbers for the jellyfish model. Going from top to bottom and from left to right.
1. adilas.biz
2. Admin
3. Monthly Reoccurring Service
4. Sales & Marketing
5. Setup & Training
6. Tech Support
7. Design
8. Custom Code
9. Consulting
10. R&D
11. Project Management
12. Internal Development & Maintenance
13. Adilas University
14. Adilas Marketplace
15. Adilas Cafe & Community - Adilas World
16. Databases, Networks, Servers, & IT

Tons more details and bullet points on element of time # 2284 inside of adilas.

Emails and tech support for ship A and merchant processing options.

Eric and I were looking at the auto deposit gift card payments update. Merged and pushed up new code. Ran the update on all servers. The new code will handle all auto deposits going forward.

Working with John. Helping him debug the cart to work with his discount engine. Light review of adilas financials.

Recording notes from yesterday and today (7/10/23 to 7/11/23).

Meeting with John to go over the SWOT analysis. Lots of talk about consistency and product feedback. Working on the opportunities section. Great conversations. At some point, I'd like to copy and paste some of those notes to make them more visible.

Planning with Aspen. Doing some brain mapping on a huge board with post-it notes. See attached for some pictures. Lots of high-level planning for adilas lite, fracture, and sub projects within our bigger vision. Once again, see attached. We also got Aspen paid for her work.

Quick breakdown of the different projects:

#1 - Company Structure - Jellyfish Model - Knowlege workers vs hourly workers, define divisions, departments, the who (talent), combine areas as needed, optimize structure, overtime, and compensation. We also want to deal with the different personality types - organizer, doer, creative, consultant, and the salesperson (someone who does sales).

#2 - Product Development - Value Add-On Core - Players, features, each summarized (possibly in a video or multiple videos). Define the current core. Figure out industry specific skins. White labeling options. On the industry specific skins, go minimal for the start. Custom code - data driven, not code driven. BI (business intelligence) level - Model needs to be fully planned out because it doesn't exist as a standalone layer at this time. It is built into the system as a whole. We need to extract those pieces and make a better plan for those numbers, values, and pieces of BI. Enterprise - define it and prep the database to make the jump eventually.

#3 - Education and Training - Adilas University - Internal and external training needs - video clips, organize them (library of sorts), tracking education, SOP's (standard operating procedures) per industry, in general, and company specific options. Make all of this data driven. Easier interactions, easier interface, all dealing with settings (show/hide, rename, aliases, sort order, defaults, etc.). Once again, both internal and external training needs. Online and in person trainings. Minimize the need for education by building out a better interface (fracture and adilas lite). Dynamic content and settings. Program education directly into the interface. Be able to turn the education mode or help mode on/off based on needs and per person.

#4 - Community and 3rd Party Solutions - Adilas Marketplace - Access from the adilas cafe or as a standalone app. Adilas creates tons of byproducts (both products and services). This could be things like consulting, design, custom code, data entry, bank reconciliation, accounting needs, etc. We want to offer ways to both buy and sell both products and services through a controlled interface. Think of a mini Amazon or mini eBay type marketplace. We need a spot to send, organize, and direct 3rd party solutions. Advertising and marketing efforts. More white labeling options (in the marketplace). This section could be further explored and has lots of potential.

#5 - Social and Efficiency Options - Adilas Cafe & Community - White labeling, standardized portal, single login, single sign on, able to jump to any corporation on any server where permissions have been granted. Options for work, play, buy, sell, train, social, and participate. User profile page. Interface with other corporations, get assigned, hub type environment. Mini marketplace for adilas based products and services. Sales and creation of new accounts (automated setup options). Tired pricing. News and updates, this wouldn't be forced on anybody but would be more available. We could allow them to customize their news and update feed. Dynamic billing and making payments for our (adilas) clients.

#6 - Deeper Product Development - Adilas Lite or Fracture - Customize everything. Setup wizard, question to help with setup, industry specific settings and presets, sizes, features, and options to customize as needed. Show/hide almost everything. Other settings such as toggle on/off features, columns, reports, navigation, etc. Everything is configurable to some extent. Sort orders and the ability to move things around (vertically, horizontally, and free form). Settings and making all of these decisions data driven.

Inside of fracture (code name before we got adilas lite) we want to make some server changes, code changes, frontend and backend changes by using frameworks and different languages (code stuff). Entirely composed of API sockets. This will make everything more portable and will also allow other outside developers options to build custom pages, features, and interfaces. Another advantage of using the API sockets for everything, it will standardize how everybody interfaces and interacts with the system or application. It will also let other developers play along without letting them see the underlying code. They just see documentation, examples, and final output from the API socket calls or API endpoints.

Fracture will include testing plans, sections for unit testing, integration testing, automated tests, and good coverage on testing in general. Everything will be modularized and broken into smaller mini components. We plan on using dynamic billing for usage, features, storage, etc. Entirely new interface with the ability to setup your own navigation and your own dashboards. We want lots of white labels and white labeling options. Tons of industry specific stuff as well.

Be able to turn on/off the education mode. We would love to capitalize on numerous lessons learned from 20+ years in the business. Lots of prototyping, new databases with good indexing and normalization. Directly program in teasers and marking. There has even been some talk of using AI (artificial intelligence) to help with suggestions for products and features that they might use or want.

Everything will be mobile ready and responsive. Client-side and server-side validation. We also want to prep things and have a maintenance plan in place as well. That is something that has been somewhat missing from past versions. Basically, take what we have and build from there - learning from the past and building for the future. Everything has a life cycle, prep for the next phase or part of that life cycle.

#7 - Budgets, Finances, Marketing, & Sales - Other business plans - interactive wireframing presentations, SWOT analysis, funding and repayment stuff, timelines, mission statement, profit sharing, budgets per section, per person, per product/feature. Writing business proposals, project scopes, sales pitches, standardization, and master table of contents. Lots of good marketing and campaigns for sales. Sources of profit and ROI (return on investment). Prototyping, testing, and market research.

#8 - Other - Networking and meetings as well as more research. Get in there and get it done!

Emails and tech support for High Valley Bike Shuttle for Drew, dealing with online scheduling. Light research on some of his settings and what not. Sent out an email to everybody about an update meeting for adilas lite or fracture.