Finishing up doing some prep work for a lunch meeting. I spent a couple of hours working with ChatGPT and feeding it some of my numbers, research, and financials. Our plan was to make a small multi-page document that would cover a brief overview of where we are at today, current financials, where we are heading, some growth opportunities, projects, sales forecasts, what we are asking for, and how the funds would be used.

I really enjoyed where the chat was going and heading. We, ChatGPT and I, didn't finish before the lunch meeting. We got some of the first pages, done to a point, and left off on the upcoming projects. That got pretty deep and needs some more loving. That's okay, I want to return back to those topics and really get them right and correct. I had a bunch of other things printed out for the lunch meeting, but we ended up just talking vs looking at deep or hard numbers or documents.

I went into Logan and met up with Chase. Originally, it was going to be with Matthew Coltrin from Pitch Launch and Chase Combe, one of his investor friends. Matt couldn't make it, so it ended up being just Chase and I. Chase is from Hyrum, UT. We had a great meeting and chatted for about 1.5 hours over lunch. After lunch, I went to a local park and recorded some notes. This is kinda funny, but I also finished my lunch. We were talking so much that I had to get a take-home box and ended up finishing the rest of my lunch at the park. Here are a few of my notes:

- Some of the most fun topics were adilas history, and how what happened then had a cause and effect, that framed up what happened back then and also what is happening right now. That was super fun. Chase was asking some great questions that just led to the next small topic or side tangent. Great questions.

- Chase recommended that we pull out the old independent rep/consultant model and tighten it up a bit. I mentioned that it worked slick, but we had some of the rep/consultants overpromising, not helping their clients, and a little bit of wild west stuff going on. We may have to retweak it, but it worked super well back in the day. Not only for reps, but we did the same thing for developers and tech guys. I'll bet, if we pulled it back out, and tightened some things up and made some rules and expectations, it could work great again. This is a possible way to get sales up, without asking for money or doing some kind of capital raise.

- We talked about a couple things that adilas has tried to avoid in the past. Some of these go clear back to the Morning Star Automotive days (original home of the adilas.biz application - custom write-up for a multi-location used car and trailer dealership). The two topics were traditional loans (borrowing money/debt) and employees. Adilas has tried to avoid both of those with some success. We talked about a tipping point, where at some point, those things may need to come into play. If not, you can become limited by capacity, unless you have tons of sales or some other source of revenue.

- We talked about how not all money is the same. Some of it comes with virtual teeth (downsides) vs other money that is more friendly. One of the things that he said was only take the money that we wanted to vs just taking any money (investments).

- By way of advice, he told me to dump down the "ask" (request for funding) with more clear we need X, you get Y, this will create Z benefits. He said that a 3rd grader should be able to understand it. Along those lines, he also said that if it was too open or broad, you can lose an investor in them weighing out the opportunity costs. A few small options are okay, but don't overdo it. You have to have a small, tight, ask. Great advice.

- You may not be able to just pull something out that used to work awesome. You may have to adapt from where you are at and what the new goals and/or environment bring to the table. It's fine to recycle certain things, but you want to keep heading forward and/or maintaining ground that you have gained. This isn't always true but try to keep heading forward if possible.

- Use USU (Utah State University) as a resource. You have a bunch of new talent that are looking for jobs. I would also add Bridgerland or B-Tech to this equation. They are a local tech school. They, both USU and Bridgerland, could be great resources. I told Chase that I on purpose moved back to Cache Valley, Utah, because of the college and possible interns and such. We did a bunch of this back in 2013-2017. We ran out of funding and had to somewhat abandon it. Maybe head back that way and see what we can do in the independent developer, tech, or salesperson (rep/consultant) model.

- One of the problems that we had with the older rep/consultant models was dealing with reps that got enough clients and stopped recruiting more sales, leads, and companies. They almost got to a content level (satisfied level) and then just stayed there. We would like it to keep going. He mentioned that instead of an ongoing commission, maybe we could just do some finders fees or bird-dog fees (person who gets the account to sign-up) and then have adilas or some other method of retaining and caring for the client.

- This is a common thing, but sometimes an admin or founder works in the business and really has their hands in deep. There is an old saying, you can either work "in" your business or "on" your business. I think that I need to pull out of the deep, in the business stuff. It is still really important, but if you spend all of your time there, who is steering the ship or driving the car (working on the vision of the company)? There has to be a mix.

- One of the questions that Chase was asking was dealing with our existing team. I mentioned that we are somewhat maxed out or tapped out, based on our current team size and abilities. We want to grow, but there is almost no room to grow, with what we have. It comes down to skills, talents, virtues, time, capacity, and bandwidth (what you can handle). I would love to make some of the "ask" (for funding) about improving and increasing our talent pool and bandwidth. That would be awesome. As a small side note, in part of our fracture - adilas lite plan, one of the first things that we have identified is some underlying team organization and stabilization stuff. It is currently listed under the codename of the jelly fish model. See this website for more info - Web link to the company structure - jelly fish model. One of our primary goals is to get 4 different main departments - Growth, Retention, Admin & Billing, and Product Development.

- If you are going to make any promises, make them clear and upfront. Along these lines, I would really like to eventually build out some profit sharing and what not. We have tons of ideas on the adilas trust and where that could go. Maybe we could setup some benchmark values where we will try to small incremental changes. Like Russell always like to say... "Small drops in a bucket will add up. Just get it started."

- Just a thought for me, what if we make the general ask for funding really simple. Then if we want, we could put more stuff out on the investment opportunities website, if they want to get a little bit deeper. Here is the link to that site - Web link - adilas investment opportunities.

- I think that I am going to set a goal for the commercialization round, funding round or capital raise, for adilas at $2 million. I would then like to show what we will do with those funds and how that will increase the value of the shares of adilas.

- A couple of closing thoughts... Stabilize the team, tighten up the ask, pull the independent rep/consultant model back out, put more complex investment options on the website.

Multiple folks checking in this morning. Cory had some questions about payables and a company that reported that one of the payables wasn't showing up in their system. We briefly looked into it. Showed Sean and Marisa some of the progress on the limited flex grid tie-in stuff. Small mini demo for them. Reviewing notes on the adilas trust and ideas for the changes in company structure.

Somewhat of a mix of different things. Reviewing and planning an MVP (minimal viable product) for the client facing scheduling app for ecommerce. Doing some research and reading inside of pass elements of time in the developer's notebook. One of the items was some new time template settings on element of time # 8004. The other was some notes on the bike shuttle scheduling for a client on element of time # 8137.

Sending some emails over to the merchant processing folks to get some approvals on terms and policies for a client. This was required for underwriting for their merchant account.

Jumped on a GoToMeeting with Steve to go over some code for bulk printing custom labels. Steve also reported that he spoke more with Alan on the options for multi member LLC and the adilas trust options for a new corporation and entity structure. Good stuff.

I then jumped back into the research and planning for the client facing scheduling stuff for ecommerce and elements of time.

Meeting between Steve, Chuck, and I dealing with options for the multi member LLC or adilas trust. We started out and Steve was still on a call. I popped into my notes from yesterday and also showed Chuck a spreadsheet that I was messing with to calculate salaries and guaranteed payments. We ended up in a great discussion that covered a number of topics. We were drawing, doing scenarios, and throwing questions back and forth. Nice interchange between all of us. Fun stuff. Here are some my notes:

- Time and Money - resources and adequate compensation for effort or time.

- How are taxes going to work? What is the timing? What if one of our guys/gals already has a business, what happens there? Do we need to change things after we get this year's taxes done and/or could it be at any time?

- If owners and percentages, what about company loans or loans being pulled out by the individual members? Meaning, say Chuck or someone was trying to buy a house. They are required to get all profit and loss statements and any liens or outstanding items or other debts from the company. How do percentages play into that? Looking down the road a bit. Chuck just wants to make sure that any company debt (say on adilas' side) won't affect him and vice versa.

- Question from Chuck - Do write offs take place on the adilas entity (business) or on the other outside or sub-contractor level (their personal business)?

- Chuck and Steve were talking about flex time, vacation time, sick time, etc. Possibly treat this like a mini account of sorts (like loyalty points). We would need to track this and get weekly updates from our guys and gals. We could keep really good records as this would eventually be tied to a monitory value.

- Dealing with scheduling... we could potentially have our own little scheduling app that shows who is doing what and who is working and who is off. Coordinating schedules to improve communication and make sure that we have coverage.

- Steve was talking about levels of write offs for each level of person - employees basically don't get much, 1099 and sub-contractors get some, and owners potentially could get even more (based on by laws and requirements, in writing as terms or business procedure docs). As you go up the levels, the write off benefits get better and better.

- Light talks about retirement plans and continuing guaranteed payments even through retirement (semi or full).

- Steve wants to keep the team as small as possible and maximize the profits. He also wants to work on other perks and deductions.

- We are trying to setup a community type business model.

- Back to flex time and vacation time - the ideal would be about 14 days off of paid flex time or vacation time per year.

- What if someone is not performing? Tye could work to make it up, get fired, renegotiate contract hours, change goals, and reset expectations.

- If someone is really struggling and it is out of their control, there may be a level of mercy that needs to be extended.

- We talked about a possible cap on accumulated flex hours. We talked about a range of between 500 and 750. At a 30 hour work week, that is between 4-6 months worth of accumulated flex hours.

- We talked about death, retirement, and how certain scenarios would play out. That still needs some loving but in death, a spouce or other stated person could keep receiving payback until the flex hours were diminished or used. In retirement, the person would keep drawing until the flex hours were used up and then real retirement benefits would kick in. Basically, they could say that they are retiring, but official retirement wouldn't start until all of the flex hours were paid back (get them back down to 0 flex hours).

- Steve would like to look into other retirement options for key persons. In another meeting, we talked about extending certain values for 20 years after the death of a member or whatever. Still up in the air. We could also figure out what the value of the shares (percentages) are worth and then make a payoff or buy back plan that would serve as a form of payment. Basically, a way to sell the shares back to adilas, if they wish.

- Our model is built on a reoccurring revenue model.

- Trying to avoid the master/slave type relationship - they were talking tons about employer/employee type relationships - more of a community or family

- Possible bonuses based on profits

- Birthdays and extra flex time - just having fun

- We can write the rules - what do we want to do and/or have?

- There has to be accountability of each person

- Chuck and Steve were going over options - Say there was a sum of money - where would it go and/or how would it be distributed? Bonuses, perks, savings, nest egg, re-invest, improvements, maintenance, updates, tax liability coverage, etc.

- Ownership and potential are big motivating factors for us to make it work

- The ideal would be a 4-day work week or a smaller or below 40 hour work week.

- On tech support and other services, we may need to coordinate days off and make sure that we have sufficient coverage

- Huge team effort - communications - community effort

- We could automate some of the flex time processes and procedures - we are a software company - :)

- We could also use certain internal time clocks to help capture certain data points

- Concepts of the adilas trust and allowing things to continue onward and keep things going over time.

- Sufficient for our needs

- We have one of the best teams that we have ever had - keep a good core team

- On the application side, keep making things smoother, better, and taking less clicks to get things done.

- As part of the conversation, Chuck was offering some help on the management side of things. He has some untapped skills in management, project coordination, and general business skills.

- Steve was expressing some ideas of offering basic business seminars and helping people learn good skills in their business. We could use adilas as part of our demos and training events. Show what is a best practice and how it all works. This could be really fun. Almost more of a focus on concepts vs products - of course, we could use our product to show the concepts.

- Just a couple of ideas - after the meeting was over - if you get a percentage gifted to you, let say that you can't sell it for at least a year. This could be a holding or maturing type timeframe. Another idea is if you sell a percentage, adilas gets first dibs. If the sale of the percentages is extended to an outside party, adilas would like to have some say over that and also be able to issue a processing fee of $1,000 or more to resubmit percentages to the state and what not. Some sort of compensation for work that needs to be done in order to keep everything up to date and fully legal. If shares are being sold to multiple persons, maybe fees per person to help cover overhead, paperwork, and refiling with the state. Just some ideas.

Great meeting and brainstorming session on the adilas trust and how we want to structure the adilas llc company. This has been a dream for years, it is actually gaining some traction and we are really excited. See the attached notes about some option.

Server meeting with Steve, Wayne, John, Shari O., and myself. We talked about some scheduled maintenance on the data 3 box and database. We then talked about the amount of time it takes to run certain database updates (tons and tons of records). Both Wayne and John are working on a spreadsheet of where the server guys use and spend their time. Our goal is to figure out some of the things that they do and what kind of patterns we can glean from the process.

Steve had some questions about being able to merge in corps from different databases into an already existing database. That gets super deep and can cause major issues. We looked into that years ago and ended up bailing out due to it being so intense and id number craziness (mixing and matching and cascading new and old id numbers through a system that is already in use). Tons of possible conflicts.

We briefly touched base on existing projects. The server guys have been busy with normal life stuff this past week and didn't get much new stuff done. We checked in on the changes for the corp-wide settings and multiple datasources per server box.

John wanted to know about a budget or allowance for server monitoring. We are trying to keep a tighter budget, but some things come and go (ebon flow). We talked about needs and keeping a good balance between what is needed and/or extras that just cost money. Along those line, Steve was asking Wayne and John if he could get some ammunition or good information on one of our clients that is kinda pushing the limits and may need to be upgraded to their own server.

We switched modes and Steve was asking both Wayne and John about their thoughts and ideas on our company structure and what they would like to see and/or participate in. We got into a great discussion on what we are calling the adilas trust or multi member LLC, where ownership and percentages are distributed to some of our key players. Great discussion and I took some notes.

The last topic of the meeting was trying to stay focused on a single project at a time. Sometimes, if we get too much going, nothing gets done or finished. Staying focused is a big key.

Quick phone call with Calvin to touch base and talk about some future projects and wish list pieces. We have been working on some custom labels and would like to get back to that project. It was on hold for a few months as Calvin was working on some other projects.

Going back through my post-it notes and recording entries from today and all of last week. Got behind a bit. I also got on the phone with Steve for a bit to go over some more possible options for the adilas trust or how we want to split some things up (shares and percentages). Making progress. All part of the plan that keeps unfolding in front of us. I honestly don't think anybody could plan for everything that has and is happening. I surely couldn't comprehend it all. You almost have to take a step and then deal with what you see. You can plan certain things, but there are many things that just start happening and unfolding along the way. It makes it responsive and more dynamic as you go. Good stuff!

On the phone with Steve. He had just gotten out of a meeting with our main accountant for adilas.biz. Steve was asking him some questions on company structure, shares, stocks, percentages, and other options dealing with setting up the adilas trust (future company or arm of the current company). That has been one of goals for a number of years now. Anyways, Steve got some new info and wanted to chat about some options and ideas. We also chatted about some of our 1099 guys and how to best structure things to help them get the best benefits and write-off options.

Steve, Shari O., and I working on ideas for the adilas trust. Talking about ideas, options, and plans. I took some other notes and sent them around after the meeting. Steve will be meeting with our CPA on Monday to go over some ideas and options.

Steve, Shari O., Cory, and I on an admin meeting to go over an employee/employer audit. Looking into solutions and options to reclassify if needed. Most of our guys and gals work from home, use their own stuff, and control their own schedules. In our books, that is 1099 or sub contractor work. The state of Colorado wants adilas to be setup as a full employer. They do make a case but there are some big holes in it. We are going to be asking our CPA, other professional resources, and maybe even setting up a meeting with the auditor.

We spent a lot of time looking at ideas on what we are calling the adilas trust (possible future company or company structure to help make sure that adilas is able to move forward in the future).

We went through and did a list of pros and cons and what we want to do with our model and future company structure. Our model has already been changing. Lots of good questions and ideas. There are also a lot of unknown variables. Trying to figure out what path to take. We also talked about options such as: Fight it (appeal it) or just take it and move on.

There was some talk about maybe forming an ESOP (employee stock ownership plan) type company. Cory was going to do some research and get back with us.

Working on budgets and plans. See attached for a scan of my notes from a 3x5 card that I made on Sunday as I was thinking about what to do.

Here is a type written list:

- A budget - maybe even separate budgets, budget by person, budget by area

- Build in savings

- Build in repayment

- Steve and I need to communicate

- Shut people off - no pay, no service

- What kind of business are we?

- Make up some rules

- Balance

- Protect each other

- Delegate - where possible

- Work together as a team - what does that look like? A team and Z team

- Make a community - effort - stone soup

- Allow for agency - you can't force it - multiple lessons on Sunday about this

- Small and simple things - progress by degrees

- adilas trust

- possible board or management agency - some kind of a council

- Pitch a timeframe like 3 months, 6 months, 1 year, etc.

- Pitch the pitch

- Co-founders and dependables

- Open & honest discussions

- Lean on the Lord

- Trystorming

- Allow for investments for labor, time, or money

- What about prospecting?

- Start, stop, continue

I also spent quite a bit of time tonight looking over numbers and coming up with budgets and options. Lots of good stuff going on.

On Friday, June 11th, 2021 we had an internal conference day for just the adilas team. We went from sales to internal code to ideas and plans. All over the place. See attached for my notes. Many great things were discusses. Once again, this was an internal team meeting, but we don't mind sharing what we were talking about. :)

//////

The attached notes are better formatted, but I wanted to push some of them here for searchability:

//////

Group Sales Meeting

Marisa, Danny, John, Cory, Sean, Steve, Dustin, Shari O., Dawn, Brendan, Steve (mac), Brandon, Chuck, Alan, Kelly, Bryan

- Kelly was saying that there is some public records per states

- We may try to pull our own list

- Questions... who, what, where, how good, etc.

- Maybe look at a sample of 10

- We may need a more focuses approach

- What about different industries?

- We need to get the name out there

- Kelly was pitching a social presence

- Do we know anybody who wants to do the social stuff

- Word of mouth

- Testimonials

- Some new video graphics

- To the penny, to the gram, every day

- What about small streaming commercials – focused and pointed

- Kelly recommends that we maybe focus on a slightly larger pool

- Dawn – maybe focus on start-ups or that small to medium range

- Get them at the beginning – maybe even tradeshows

- It is a pain in the but to switch over – pain creates options for change

- Focus on services... deployment, oversight, consulting, training, best practices

- How can we deploy something easily and repeatable?

- It is tough to get some of the people started, but once they get all in, they tend to stay

- Kelly has done this over and over again

- Using the professional resources that are available

- From Kelly – Help get the clients all the way in – full system and platform

- Getting the success on the first implementation and then building from there

- What about focusing on those who are having trouble and/or are struggling

- Dawn loves the support, training, and feel good part of it – duplicate that feeling to others

- How quick can we respond – we jump pretty quickly on custom needs, development, training, and support

- Get more testimonials from our clients

- We have some experience to offer to those who want it

- What about pitching best business practices

- It's ok to be non-traditional

- Being Relevant!

- Focus on helping over sales – from Steve (mac)

- Simple things that bring the relevant pieces

- Social webbing – group effort

- Danny, straight up, I don't want to be the social media guy! We have to find the right person and/or persons (small little team)

- We are not QuickBooks... what does that mean? Be our own style!

- Packaging this platform based on the target audience

- Formulating a plan – ease the lift – maybe a monthly meeting with some planning

- Influencers and YouTube options

- Small info tips...

- New age marketing – we have to play to the current market

- Big Dumb Animal Pictures – super simple

- We have to do a cost analysis to see which one(s) make more sense for us

- John, what if we setup our own little social piece (aka maybe the adilas cafe) – we could allow all of our users and power users to pitch and promote – we may need to approve things, but we have tons of very knowledgeable people and users

- We are looking for engagement – back and forth – a relationship – maybe get an intern to help handle this

- Danny – Switching over to the modal message marketing

- How to save the app to your phone

- Make the email piece better

- Small web tool to help with building special html links to embed promotions, direct add to cart, discounts, campaigns, etc. A simple form to help with the backend tech of those URL's and web links.

- Maybe, we need to upgrade our email platform. It is a small holdover from years gone by.

- What about the delay on the outbound emails?

- Marisa – maybe outsource things as needed

- Steve – would like more input on the bulk tools

- Better filtering and target marketing

- Steve wants to work direct with Dawn and Branden

- Matrix and target marketing – even predictive

- Maybe a little itty bitty (super small) native app on the different phones – iOS, Android, etc.

- Steve wants to get into possible predictive marketing

- Steve – looking for great feedback and even ideas and dreams...

- Archiving, saving for later, dismissing, etc. We have the data, what do we want to do with it? – Wet clay...

- Danny – Going back to past clients

- Version 1 vs Version 2 – type attitude

- What kind of clients do we want? We may not want certain kind of clients.

- We love people who like details and are willing to play

- We love people who take things to the fullest level

- We love people who just need a small little piece – there is a gap in their current model and they need some help. We can then grow from there.

- Do a full comparison of what we offer

- Pitch what we do differently – we help deploy and maintain your ERP

- White glove approach

- Playing with the tools that we have and flipping those into marketing messages

- Chuck – maybe check out some groups on Facebook

- Blog posts, articles, info snippets, quick videos

- Talking with Kelly – how have we helped small businesses become bigger or big business – showing the potential – dreams to reality

- The small goals to achieve – steps to get to the next level

- Small goals lead to bigger goals – getting some small successes along the way

- Clients and expectations – not all money is the same – budgeting and planning – what kind of client do we want

- Reoccurring revenue vs one-time revenue

- A quote is just one of many pieces that needs to be done

- People, skills, and cogs in the wheel

- We all care... where would you and your skills fit in best

- Seeing the bigger picture

- Maybe looking at personalities and figuring out the mixing and blending of our options and resources

- Slowing down and taking the time to see where we are at? Virtual time travel – child, youth, adult – as a company

- What's the difference between a goal and dream? A plan!

- The internal group summary that we did... a great start

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

Second session - Servers & Infrastructure - Refining Our Processes - Tech Support & Training - Project Management

Steve wants us to show the online label builder

- We had some good talk about where we want to go

- We pointed to our internal summary report

- Steve McNew – helping with the strategic marketing plan, technology road map, timelines to position, plans for action

- Scale – can we grow and can we shrink

- Conversation between big and small – perspective – big and small (sales, number of team members, lines of code, etc.)

- Molly – Is adilas the big guy or the small guy? Think of code (lines of code). We could be considered a big guy if you were looking at code and functionality.

- We like being small (ish), but what if we are big already

- If we want to grow, that means that we want to get better – grow in a good manner and sustainable manner

- The underlying services that support the whole

- Be your own style!

- Steve McNew – old classmate with Steve Berkenkotter – guest speaker – part of the adilas team to help us get some things more standardized – processes and procedures

- Defense contractor for the military – 28 years

- Testing, software, management, auditor

- He has already called, interviewed, and talked with a number of different team members

- He did a 20 page audit and report on what he was seeing

- Getting into some testing and processes – he would like to see more of this

- Not trying to derail the train – we are trying to polish the Ferrari (spelling – awesome car)

- Whitepapers – catering to a higher audience – going beyond stick figures and into technical docs – not everybody will want to read some of these, but there will be some that require it

- Steve B – if we try to sell our product to those who can't afford it, it doesn't really work. They have to be able to pay for what we do (really do – billing for our time and efforts)

- Fin-tech – financial technology

- Using whitepapers as part of our marketing plan

- John M – unit testing – confidence of the developer team – currently only Wayne and Alan are doing this (unit testing)

- Going to ease into this – refining our testing plan

- Version control and when do we update these systems? The older way was wild west... we may want to figure out some specific micro builds.

- It would be nice to keep track of the versions and options.

- The balance between core and custom development

- The application needs some spring cleaning – what is being used, what isn't, what is going slow, etc. – Refactoring

- Priorities – customer priorities or our internal priorities – what is the mix and blend of these pieces

- We all ware many hats... we may need to define that so that we don't overstretch ourselves

- We all use (and can use) the system in different ways – how do we translate that information to our clients, other developers, and other team members (upstream and downstream)

- 2 minute videos – no more

- Work instructions – even giving it to someone who has never done anything in the system

- Danny – Shoutout to Steve and Brandon – we have done great – what is coming next? Resources?

- Talks about earn and burn ratios

- Prices have to match the services

- We are a growing business

- Kelly – going from 1.5 to 10 (millions) – that is a huge change

- We are competing with companies that are hugely funded... what do we want to do?

- There are some real things in our path – there is tons of potential – what do we want to do with it – also, sometimes there is shelf life on potential or advantages

- We don't want debt – however, there is a time for debt – cost analysis and being smart about it

- Making choices, but also being willing to fail

- Marisa – look at our new website

- Steve – there are some percentages of adilas that are available – not looking for vulture capital (just being silly – vulture vs venture)

- Someone looking to take on some risk but helping us to get to the next level, without taking over the company

- Kelly – pitching our vision and business plan – we have to define the vision – Danny seconded the define the vision before looking for the funding – goals, sales, budgeting, maintenance, and getting a business plan.

- Adilas Trust option – co-founders

- Possible option – Maybe take some of IP (intellectual property) and sell that to a new entity and then restructure those new pieces

- Dustin – thoughts on corporate structure – we are all on our own little islands – Ferrari to a tricycle – frontend compared to backend – splitting up those pieces and functions – he wishes that we could be more collaborated.

- John – teams and buddy projects – small sub teams – full stack (all levels) vs specific skills or somewhat limited skills – this needs to be part of our plan.

- Sean – we already have some small teams that are working on some of these projects – cogs of the wheel – buddy tagging the workflow and processes

- John – the adilas docs project – and being able to go to it and also add to it – working on standardizing the pieces – filling in the gaps

- Danny – Navy Seals – two is one, and one is none – at least two on a project – two-by-two

- Kelly – scale – having a back-up

- Danny – accountability back and forth

- John – confidence levels

- Kelly – what about a succession plan?

- John and Dustin – real life buddies and how they help out each other – seeing a different angle or perspective

- Marisa – tooooooooo much weight gets put on single persons

- Kelly – relieving pressure and helping with scale

- Marisa – Cory, Kelly, and Marisa – wonderful training slides, presentation, and delivery for the conference. Awesome job!

- Alan – modularize things – able to be reused – code concepts can relate to business functions – one to many relationships – translating knowledge into real life and different scenarios

- Chuck – last summer Chuck was on a joint project with he, Russell, and a different John. It worked out awesome – Keep pushing towards that kind of rollout of the project

- Molly – thinking and coming up with ideas. Keep it going!

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

Next Session - Deployment & Oversight - Design & Layout - Internal Core Development - Custom Development 

- Deployment – where are we going and how can we make this all work – team effort

- Shari O. – first touch and setup corp, Sean and Shay first hour or so, Sean helping to coordinate the next steps and pieces

- Sean does a great job of reporting back

- Report on things, record the notes, get back with us to help us keep pushing

- Doing great with testing and prototyping

- Kelly – who is on settings, who is on planning, maybe even looking at pre-deployment options

- Before Kelly even does a demo, do some consultation – figure some things out without doing any pitching or selling. This is called listening.

- What are you looking for, wanting, expecting, hoping for?

- Make the demos custom to the pain points or key wants and needs

- The prep work is huge to help them be successful

- This platform is not a turn on and go type system – there may be pre demo, consulting, custom planning and demo, then custom hand holding to get them going down the road

- Picking the point of contact... who is going to own this thing?

- Owners, managers, and users

- Users want the easy button – Steve calls this the tail wagging the dog vs the dog wagging the tail – what is and how can we get buy in?

- Tools are great, but solutions to problems and pain points are even better

- Give to get! If you give too much, it can get you into trouble.

- What is the cost to fixing things... on the other hand, failing does help with major learning – there has to be a balance

- We tend to remember pain – setting people up for success

- Often users are looking for a quick switch. This system takes work. Please sell it that way.

- Not going to custom too quickly – learning the manual way – then automating it

- User buy in – light pain and then helping them learn a better way

- Change proposals and scope of work – setting up boundaries

- Feature creep – setting that scope of work – cause and effect of what they want and what they give – expectations and timelines

- Sometimes I start with NO – interesting

- A saying no - sandwich... Yes, I'd like to, no, I can't. Yes, I would love to help do this... - people think that no is a bad word

- Having a plan to say yes, vs just saying yes

- We like to please people – that is awesome – what does that cost?

- Help make the plan to say yes. Maybe, no (first), however we could do this...

- Making things repeatable

- What are the internal costs to do deployment?

- Say $350 for a setup fee – does that cover it? If yes, great. If no, where does that put us?

- Maybe on the setup, prep, an activation fee (define this – turning on the lights), setup and deployment fee (range), training, custom code, imports, labels, etc.

- We like to cater to everyone – that had bitten us

- Actual prices and then use discounts if needed. You can't really ever raise a price after the fact.

- Back-up our prices

- Use adilas to run adilas!!! This is our communication tool, let's use it.

- We are good at the dreaming and software building part of things, we need some major loving on the service side

- There is demand!

- What pulls at our time - It is time, money, skills, etc.

- Kelly – earn has to be more than burn

- Flipping the demand to sales or services that could be provided

- MVP – minimal viable product, plan, player, etc.

- Intangibles

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

Next Session – Show and tell! What are you working on?

Calvin – Advanced file and folder finder, resize images, convert images

Brandon – harvesting assets from element of time

Steve – parent attributes report, items not on a recipe (manufacturing), modal message marketing for customers, log notes for vendors and employees (payee/vendor logs), backorders homepage, mini units, auto add item (quick PO behind the scenes), bulk update on the vendor – master copy paster... :)

- Branch 122 – fun

Bryan – cfqueryparams – stop SQL XSS (database hacks – cross site scripting)  - SQL injection – converting from dynamic queries to secure dynamic queries - Example: Corp_id = #Trim(some form or URL var)# or Corp_id = <cfqueryparam etc, etc,> - this stops the SQL hacks

Bryan is also working on eChecks for eXPO, Hypur checkout in the shopping cart (eComm), new API's for delivery (with documentation and samples)

John – Payroll project to allow holiday date picking, timecard flags, timecard totals (pre summing the math to go faster and lead towards bulk payroll), new timecard reports showing grouped sums and totals.

Page templates and style guide defaults with Chuck – Going from old school tables and links to the newer grid and mobile ready code. Part of the adilas docs project. Build once, use many (effective copy and paste). Basic templates (3 new ones). New information icons and popups (modals). Style guides and usage of those pieces.

Servers with Wayne

Chuck – Huge new web site!!! Awesome Job!!!

Global Design Dashboard, adilas docs, and new presentation gallery (sales tool).

Danny – message marketing, custom labels, sales team meetings – hats off to all of us! Keep listening and keep finding solutions. Open table – follow your highest excitement and be yourself! Be happy!

Alan – enterprise level catalogs, refactoring code (custom page settings), standardizing code for speed and reliability.

Random comments – Cory really liked having access to all of the team members, right here at the conference. Marisa – great to meet everyone – keep floating the boat. Sean – he likes the team. Molly – loved watching and wants to be involved. Chuck – idea of everyone joining slack

Work session between Shannon and I. We were working more on the internal questionnaire summaries. We are getting closer to the end. We were working on the section about the adilas trust today. That is question 22 of 25 total questions. We have 3 more questions to go. Yeah! See attached for our progress.

Working on more summaries with Shannon. We went over a few more questions. The two for today were - where would you like to focus and what are your thoughts on the look and feel and UI (user interface) for adilas? See attached for our progress. These are the summaries for the internal questionnaire for the adilas trust.

Topics for the day were ideas for the Adilas Trust - internal revenue sharing and how do we want to structure time commitments, scheduling, and maxes and mins for how we play the game. See attached for more info. Working on the summaries for the questionnaire that Shannon and I are compiling. As an interesting side note, we also talked about some of the limiting factors to what we do. They are funding, access to help and support, time, knowledge, and skills and talents. We are all trying to push things forward, but it is not an even or well paved road. We hit obstacle after obstacle along our journey. The more we have to transition, the more we have to somewhat slow down - at least it feels that way. Good venue for venting and discussing things openly today. Good stuff. 

Sean was the only one on this morning. We were talking and chatting about quotes, orders, and expanding that part of the system. He has a client with a need to virtually sell all kinds of stuff without actually having things in your inventory. That would be perfect for an order (using a quote but calling it an order). We also talked about how a single quote/order could then populate one or more invoices to eventually solve or resolve the requested amounts. That quote to invoice (possible multi) relation would need to endure and be accessible over time as the products get pushed out to the customer or client. Fun discussion.

After Sean checked out, I went back to making modifications to the Adilas Trust and adilas.biz offerings document.

More work on the percentage offering documents for the Adilas Trust. The current document has 4 pages. The first is the offering (what percentages are available and how that will work). The second page is some sales and revenue history and company valuation stuff. Pages three and four are quick Q&A's (question/answers). Sent a copy off to Steve for his review.

Working on the percentage offering document for the Adilas Trust. We are planning on gifting between 10% and 20% to the Adilas Trust. That is where we will help all of the adilas dependables track their dividends, investments, etc. Good stuff.

Working on some new documents dealing with the structure of Adilas, LLC as a company and options for moving into the Adilas Trust entity. Some of this work was looking through older notes and writing up an offering (percentages) document for the main Adilas, LLC entity.

Phone call with Russell. We talked about a wage increase as of November 1st of this year (in a couple of days). He is working and was telling me about his school load and what he hopes to do over the next semester and other classes that are coming down the pipeline. Russell has done a great job and we would love to get his help on a more permanent basis as a key dependable.

After that, phone call with Russell, I did some review of some notes that Steve and I have been making for the adilas trust entity.

Steve and I met for almost an hour going over ideas, sales, company background, rules of the adilas trust, talking about selling percentages to help cover things, and other topics. Good conversation. I took a bunch of new notes and have them on my local computer (laptop). We are planning to make an initial internal offering for adilas percentages from November 1st to December 31st. We are changing up some of the internal ownership structure and want to let our guys and gals know what we are doing. All good stuff, we hope, just something new that we haven't done before. The story is unfolding and we are getting a more clear view of what we want to do and what we have to do. Steve and I were brainstorming and roughing out things that we wanted to put into the official memo and notice. Exciting times.

Brandon has almost 4 pages of notes on his local computer with ideas and things that we are planning and going to be doing.

Just Steve and I on the morning meeting this morning. The first part of it was just some catch-up and random to do list stuff. Towards the end, Steve and I were talking about shares, percentages, ideas, and options. We would like to setup the adilas trust and help give back to our guys and gals who have helped us build up to this point. Good stuff. Great conversations and making progress. Brandon has some notes on his local computer.

Shannon and I were summarizing input and talking about funding and funding options. See attached for where we are on the adilas trust questionnaire summaries. We also got into some good discussions on where we are, what we've been doing, and even some plans for future funding opportunities.

Great meeting with Steve. We were talking about the adilas structure, company, percentages, and options for the adilas trust. Brandon has a Word document on his laptop with some notes that were recorded.

Steve and I got on a GoToMeeting session to talk about options. We spent some time going over ideas and drawings for the adilas trust and how we could set that up. I have another Word document with a bunch of notes. Steve and I met for a good hour, talking and going over ideas and options.

Calvin called and we chatted for a bit. Calvin was pitching a proposal to work on the adilas label builder and getting that whole product web ready and transferred over to adilas vs being custom Windows based software that he developed. We talked about budgets, timelines, expectations, and other options. One of the things that Calvin was pitching was outsourcing a JavaScript grid layout engine. If we got that built, we could use that same layout engine to configure custom labels, custom invoices, customer receipts, check printing, PDF forms, and other layout type projects. Good stuff.

Here are a couple of other quick side notes from the conversation with Calvin. We talked about doing focused sprints vs big long drawn out projects. One, the developer's lose momentum and two, sometimes funding runs out. Time and resources, those are major pieces to the puzzle. Plus, this is the major killer, transitions... you lose so much in the start/stop, start/stop process. We gain some advantages as we do small pushes to minimize the length of the project and the number of transitions that will happen. We already knew this, but sometimes it is a good reminder on efficiencies and flow.

After the other meeting and phone calls, I merged in some code for Steve on branch that he was working on.

Talking with Steve about receivables and payables inside of adilas. Basic business stuff. Constant state of flux. After that, Steve and I were working on some more custom code together. We then got into some budget talks, possible options for selling percentages and even doing an internal family round for funding options. We talked about the adilas trust and ideas there.

Shannon and I spent another session doing summary work on the ideas and responses from the questionaire about the adilas trust business idea. Lots of thoughts and ideas about the adilas jellyfish (octopus) type model. See attached.

Funny topic of conversation - We work a lot with wet paint - Something can happen and then minutes later (wet paint), we are pushing on it, pitching it, and building on it. We virtually work a lot with wet paint (no time to dry before we start using it). I thought that was kinda funny.

Emails and then meeting with Steve to talk over ideas and options. We spent some time talking about our ownership structure and options in case we wanted to see if we could get some more funding by offering a certain percentage (basic share stuff) and what that may look like. Just talking and playing around with ideas.

- Businesses - going up the chain

- Our optimal size seems to be high side of small and low side of medium. Basically, small but almost to medium.

- We are really good at building stuff on our platform

- Light talks about the adilas trust, adilas café and community