Great two-day conference. Took tons and tons of notes. See attached.

So, Sharik Peck, owner and founder of Rezzimax allowed me to come watch he and his team put the conference on. I brought my mother, who loves that kind of learning and content. Those people (the participants) were her kind of people. That was fun to watch all of them interact. I ended up loving it as well. I learned a ton, tried out the products, and even contributed a bit to the conference (questions and comments). My main goal was watching what they were doing, how they interacted with the conference participants, and observe little tips and tricks that I could pick up and use when I do some training events and conferences. Good stuff!

Here are some of my notes. Once again, this was more of me observing and picking out tiny tidbits of information vs taking notes on what they were really doing and talking about. I hope that makes sense.

- The Dream - telling a small story. Dreaming and then trying to put the dream into reality. Just the motion of following a dream led to a whole other set of ideas, situations, experiments, and achievements. Basically, the whole journey that ensued and is still going. All from following or attempting to follow a dream.

- One of the main goals was sharing knowledge and getting manuals and resources out to their users. One of their biggest problems was - How can we replicate "Sharik" (fill in the name of whomever is a major key player or awesome influencer)? Sometimes, to start with, lots of the main knowledge and/or know how resides in a few key players. We have to get that information out, virtually duplicate that person, and let others help run with it.

- They spent some time, right at the first, trying to get the conference attendees to help pass the word along. They did a whole section on the affiliate program that they are using. This could be done through referral links, commission structures, affiliate program website, training, certification, and specific tracking of coupons.

- They used some guest speakers to help spread the word. They also have done some research, written articles, and gotten things published, in order to get the word out. Some of that takes times and networking. Along with that, it is always good to bounce ideas off others in your field. Collaboration and idea farming.

- "Form follows function" - they kept saying that

- Small pieces of world building - I saw interconnected system, relationships, finding and fixing problems, addressing pain and disfunction, and seeing how those interrelated pieces worked together to almost create a world. This is an older entry dealing with some world building concepts.

- The smallest change in a system can play through and create new problems and new solutions. Trying to get a good balance - along the way.

- Straightening out disharmonies

- Helping people help themselves - teaching them coping and learning skills

- Deprogramming - things that run in natural or normal habits that may be unwanted or causing problems and issues. Deprogramming, in a way, means undoing or rerouting paths and avenues.

- Lots of experimenting and being okay with that - nothing happens by magic.

- Practice and hands on training - they were giving additional instruction during the practice session. The instructors were miced (had microphones attached to them) as they were walking around and helping others with the practice session. Everybody was able to gain from the instruction and feedback given to individuals.

- Durning the presentation, they would bounce out to a well formatted video to help encourage the participants to go to their YouTube channel for more information.

- Talking about alignment and getting things in-tune or aligned - This was tied into a foundation and going back to the basics. This included basic knowledge and basic techniques. The alignment seemed to be a key factor.

- Focus your mind on what you are grateful for... One of the best sources of change.

- Over the years, Sharik has gone onsite and helped out many people - where they are (to their place, their home, or their business). That seemed to be a reoccurring theme.

- Look where you want to go - If you do, you'll have a better change of getting there.

- Victim or Advocate - Question - I make things happen or things happen to me?

- Thinking about thinking - an active approach

- They used their tagline over and over again. It was - "Tune out pain and tune into life!"

- He, Sharik, tries to surround himself with people who have lots of skills, knowledge, and talents.

- They had products and samples that they gave out and let people use, try, and experiment with.

- Their packaging was very professional looking. Nice glossy info sheets, nice visuals, everything looked very professional.

- Matching frequencies - we don't want to stay out of sync very long. We tend to want to match what we are hearing and/or feeling.

- Great interactions between the instructors and the conference attendees.

- Consistency and creating good habits.

- Don't be afraid to try something new. Learning over time and recognizing patterns.

- There were a few different times that Sharik would talk about the process of inventing - He would wake up, write things down, react to things as they keep coming (from any source), and keep moving forward based on where he was and where he wanted to go. I loved the stories.

- Quite a few user stories (from the participants) and testimonials. You could tell that everybody liked the products and the procedures (protocols).

- Lots and lots of great hands-on practice sessions. He even had a number of people (assistants) who could help him out, there at the conference.

- They kept referring back to their website for videos, information, manuals, products, etc.

- They had a new product that got introduced at the conference. You could tell that a lot of time, energy, money, planning, and excitement were part of the new product release. They introduced their mini's or mini version of their calibrated vibration tuner. It was pretty cool! Everyone there got one to play with and experiment with it. Lots of ideas and scenarios started to play out. The participants were expressing ideas and possible solutions, almost imediately. That was really fun to watch.

- Feedback was requested and very welcome.

- Sharik has been doing some public speaking at different events for quite some time. Great way to get the message out there.

- Loved the light flexibility in their agenda. They switched things up on the training as needed. If you were a person who fully expected perfect clockwork, you would have been disappointed. If you were ok with some flexibility, they you were spot on. They still kept it moving but there were definitely some custom alterations on the fly. I really enjoyed it.

- Recipes - basic steps to get a certain outcome or output. They called them "rezzipes" for Rezzimax but they were virtually recipes - simple steps to get certain results.

- Harvesting ideas from others - giving credit where due.

- Lots of personal stories, details, knowledge, hints, tips, and experiences. That made it fun.

- They kept showing success stories - it almost made you want to be one of the success stories. Almost a level of marketing without actually marketing. That was cool!

- They ended the first day pretty casually and soft - they didn't teach clear to the end. Sort of a soft ending on day one. Light interactions, hands-on experimenting, networking, etc. Quite a few people hung out and chatted, asked questions, and had some great interactions.

-------------

Day 2

- Small suggestion from my mom - A bag with your logo on it. We got lots of goodies and new toys. My mom recommended that a bag would be nice. It would be reusable, helpful, and people could see your logo and name as the people carry their stuff.

- Sharik started the day off by asking for feedback.

- He had a few people that could only be there part of the day. He was willing to change his agenda to help accommodate some of the people who needed to leave early. Those people wanted to cover a specific topic. That showed great flexibility and a personal touch.

- He, Sharik, made some fun and great introductions to those who were helping him out. His fun introduction added credibility to the presenters and/or helpers. Whatever their role was.

- They showed a new mobile app to go along with their new minis (calibrated vibration tuners). Super small demo. Talking about upcoming changes. The users wanted to be able to read/write new hardware names (be able to name the devices - in English vs multi-digit serial numbers). They wanted ways to name the device, assign them to a room, or attach a type to the device. Basically, ways to flag and tag things so that they could organize their environments. It was all about organizing their flow.

- They (the users) wanted to be able to turn things on and off remotely. Using technology to help their clients and patients sleep better.

- They also wanted full control to program multi devices with plans, modes, times, timers, and custom options.

- The end users wanted to know timelines, they were really excited to get using it.

- Currently, they are using Bluetooth to connect. They want to be able to do all functions, remotely, including ways to control all of the micro functions, timers, wake-up, go to sleep, modes, cycles, etc. Ideally, they would love it if they could program something remotely and then the device could go pick up that information from a central server or central location. Basically, a web app of sorts. Going beyond Bluetooth.

- Users wanted to know about updates, notifications, communications, and how to provide feedback.

- Not only feedback but also recommendations and feature requests.

- Sharik was asked a question and jumped back into a small history of where they came from. The electric toothbrush story. That was part of the start of the whole dream. In his dream, he was told, "Vibration will heal the human nervous system. Go figure it out!". Through experimentation, they went through over 800+ electric toothbrushes. This is a side note, but I've known Sharik for years. At one point, he was experimenting with handheld sanders (from a hardware store). The toothbrushes were too little and small and the handheld sanders were too big or too powerful. They ended up with their own tuners that allow for calibrated vibration (speed, intensity, and frequencies) and even waves and patterns. All part of the invention process. Kinda fun.

- It was fun to see journeys come full circle

- Back to the minis and the new app - the users wanted to know protocols - who to talk to, what to send in, how to communicate, etc.

- Sharik invited the developer to show the new app. All of this feedback was being thrown at him while he was presenting. They were recording it and others were taking notes. There was no way for the developer to actually take all of the notes for the requests, ideas, and suggestions as he was presenting. It really helped to have other helping to either record or jot down the notes.

- Just for fun - Sharik said about the programmer - "A programmer on a mission!"

- Note about the media guys who were helping - they had two guys recording the conference. One was the primary tech guy. The other was more promotional and marketing. They were capturing testimonials along the way. They miced (used microphones) all of the speakers. If someone else made a comment, they tried to resay it or recap over the microphone. Sharik was also recommending that the attendees get with the media guys to get their stories and/or testimonials. Pretty cool setup.

- Jumping back into the conference and some of the topics. Lots of time spent on "Trauma" - aka problems, issues, and pain. Without pain or needs, no solution is needed. Once trouble or a problem exists, a solution or answer is needed or wanted.

- Pornography, drugs, alcohol, PTSD, life events, etc. All forms of trauma or issues. Some of these things are taken in by the eyes, ears, hands, mouth, touch, feel, or other ways. Eventually, they get into us and/or affect us in some way or another.

- Teaching the law of opposites - joy and misery, happiness and sadness, inhale and exhale, push and pull, etc. Being ok with being uncomfortable. Pairing these opposites and finding patterns. Back to trauma - front door and back door approach. There is always a way in, look around and be creative.

- Let it go! Exposing yourself and being vulnerable. "IT" will come later. It meaning, what you are looking for. Sometimes you just need a catalyst for change. Replacing negative with positive (thought).

- Standing next to the event, not in it (trauma and events). Can you remove yourself from it and virtually watch it play out, what can you learn, do, observe, as you look at it from a different angle. If you only look at things from a single vantage point, you may be limited as to what options are available.

- Going almost empty and then rebuilding and replenishing.

- Trauma has attachments - it could be other traumas or connections with other events or situations. Usually, it is not just a single thing... there are relationships and multiple interconnected pieces.

- Forgiveness and understanding. Forgiveness doesn't make it right. It does have power to help you. At some point, you may need to ask, how is this all done? Where does that lead you?

- Having a safe place to recover and seek healing.

- The ability to connect to the music within you.

- Saying prayers - for self and for others - looking beyond yourself.

- Sharik was sharing his story and tons and tons of other experiences. It makes it real.

- Triggers

- Learning lessons and then passing on those lessons learned. Experiences just happen!

- At one point, they went over a number of FAQ's (frequently asked questions). They had a preset list and it made it easy to just jump through them and/or skip around as needed.

- Different people do things in different ways - that's ok and even encouraged...

- Great discussions and awesome feedback and ideas from the participants. There was enough flexibility in the presentation to allow for that.

- Inspiration and being open to new ideas. Sometimes it takes time to come to an understanding.

- Freely give, freely share - keep it open.

- Each participant comes from a completely different place. Acknowledging the pioneers in the room. Go explore. Learn from your experiences. If you are experimenting, try it on yourself first - controlled experimenting. Fun discussion.

- Mixing and combining techniques and skills.

- Finding out what nature does and either using it (nature or natural ways) or trying to simulate it. Helping to integrate those type of techniques and processes.

- There are tons of other things that can be added into the mix. Take what we have and what we offer and then add to it and even enhance it. Build off of a stable base.

- Back to a topic in the main presentation - deep questions and sequences - Am I safe? Once you feel safe or relatively safe, you can open up and/or work from there. Interesting.

- Making time to care for ourselves.

- Stick to the basics - back to recipes.

- This is from my mom - She can hear the main presenters but can't hear anybody else (other people who asked questions or chimed in). That bothered her a bit. She knew that I was taking notes on my observations and leaned over and asked me to write that down. That can be hard to fix and tends to fall on the presenter to restate the questions and comments. Just noting that was requested (restate what is being said by others).

- Pathways - things that are used over and over. What works for you? Use that and then build and go from there. Along those same lines - think about strategies and figuring out how to duplicate or predict certain outcomes and behaviors.

- Light humor lubes the discussion and/or topics being taught or discussed.

- Gathering information - connecting the dots - even over time. Be patient! Along the way, seek for opportunities and find alternate paths or pathways.

- Sove a problem, then move on to the next... the deeper you look, it will become a map of the environment. That's pretty cool!

- Going back to basics - the goal is the big picture.

- Repetitive processes - that's how we learn.

- More videos and referring the participants to subscribe to the YouTube channels (plural).

- Lots of techniques, tips, and tricks.

- They were talking about self-healing... at times more advanced help is needed - meaning surgery or other advanced help. That is okay! Start with self-healing and go from there. There is a point that we need other people and their skills and knowledge.

- Talking about pain - if you take it all away, sometimes you do something stupid - keep it real - without any pain, you can push things too hard. Pain can be a great teacher. Knowing your limits.

- In their videos... there was a lot of consistency - well done. Some of them felt repetitive but yet different.

- Sharik's wife kept helping them, whoever was presenting, with reminders and helping them if they forgot something.

- Giving service - helping and doing good

- Public speaking and facing fears

- They were talking about sharing energy and sharing energies (plural)

- The feet are great messengers to the brain

- Simple steps - set timing - set steps - make it repeatable

- Watching friendships and relationships being made from the conference attendees - fun to watch

- People cheerleading each other and supporting each other

- Good laughter and fun times

- Emotions tied to injury - making new paths to the brain

- Putting all of the pieces together - creating a system and using other systems that already exist

- This was big for me... what have we found... letting people know... passing on that knowledge

- Just noticing - some of the attendees were standing, going up, getting closer, taking pictures of slides, videoing, recording, and taking notes - internal thinking

- People want to learn - some great questions and follow-ups

- Telling the brain "the map"

- Being developed on the fly... people testing things on the fly. They were putting ideas into play on the fly (meaning the attendees and the presenters). This was especially true as they were playing with tuners and techniques.

- Alignments - keep coming back to simple alignment concepts

- Improvements and seeking improvements

- Major participation - he called someone up to the front, let them do it, and he was commenting and lightly direction what was being done. Very hands on.

- Watching for reactions - seeing through their behavior

- Things working together

- Talking about sensitivity and visiting or building up those areas over time.

- Following protocols - set steps to follow to get certain results

- Translating ideas and concepts to different applications

- Personal stories and tying them into parts of the bigger or main story

- Helping to solve problems - daily

- Constant message of gratitude - being grateful

- Good resources - that helps to bring back that knowledge quickly

- Sensitive individuals - start where or wherever they are at - helping them quickly get back to recovery

- If it takes time - take that time

- When they are ready... there is always a timing that goes along with healing

- Question - Are you trying to solve things or just make things better or easier? There is a difference.

- Thanking others

- Explaining why we do the same things over and over again - finding those patterns and reasons

- For me, I loved the stories and how much Sharik and others had helped others, all around the world, making a difference.

- If you do some pain... Make sure you put a smile on their face before they leave.

- Some of the participants want a way to share and pass on advanced tips and techniques. They talked about a Facebook group(s) and making them public or private, depending.

- Wanting to stay connected

- Mindfulness and being focused - going there on purpose

- Self regulating

- A tool to help - not the end all solution

- Primitive reflexes - a return to a pattern - there are both good and bad primitive reflexes - ways to help overcome ones that are unwanted

- Light it up (an area of the body or a pathway to the brain) - the brain loves information - food for the brain

- Asking others to help us get the word out - work of mouth

- Technique - cross grain or crossing - going across the midline and then back again.

- Transforming and transferring energy

- Test it as you treat

- Work on the weak side

- Working through barriers

- Accelerating processes

- Isn't that cool (both ! and ?) - statement and question

- Combos

- Tests

- X is tied to Y, is tied into Z, is tied into... Everything is interconnected.

- Reviewing, even at the risk of sounding like a broken record.

- Spent some time going through scenarios (different changes or alterations based on the circumstances)

- Integrating both sides - of the body or of your environment

- Keep working on things that need help - wake it up - then integrate it

- Mirror therapy

- Don't put limits on what people can do - the mind and body are amazing

Reading and making comments on some research that Danny was working on. Research on YouTube channels, videos, using blogs, etc. See attached for some screenshots of Danny's research. Watched a small movie from Bryan on his homemade time clock app and project management tool.

Here are a couple of links that I sent to Danny:

- List of over 13,000+ blog entries from the developer's notebook inside of adilas.

- Idea to reuse some of our existing content in a number of different spots or other outside blogs.

Emails and texts back and forth to John about the adilas cafe. Working with a document for Danny and YouTube training videos. I then met with Danny and we went over options for some of the videos and training assets that we both have and/or need. Danny and I were talking about things, and he was saying that he knows a company that doesn't even release the next changes until the training is ready, done, and up for viewing. See attached for a screencap of what we were talking about.

Here a couple of the links that I sent to Danny:

- Entries in the developer's notebook talking about YouTube videos - lots of good resources. Once it comes up, do a browser search for the term "YouTube" to help pinpoint some of the options.

- Entry in the developer's notebook talking about a thing called education mode.

As a side note, on 8/14/23, I added this little link to a video on the education mode.

Went into Logan to meet with Aaron Hill. We went biking (off the clock) and then came back to his office and did a two-hour consulting session. As part of our session, I gave Aaron a small demo on what adilas can do. See attached for some notes.

- Aaron is able to help with the consulting and seeing things from the outside.

- I can't get bogged down in doing the smaller or bigger tasks. My current role is to help get the vision out there and get it all going.

- We'll meet every couple of weeks to report on progress.

- Investors are looking for the full package and lots of potential.

- The (this) education piece is huge.

- We need to keep someone on staff that has their thumb on education and knows what is going on there. It's a vital piece of the puzzle.

- We could start with some of our older stuff. Instead of reinventing the wheel, we could use some of the older training stuff and use that to train the trainers. We have tons of assets, either on our older YouTube channel or Brandon has the raw recordings on some external hard drives that we used when we were doing the original trainings. We just need someone who is willing to get in there and pull out or break out those pieces and/or gems. It's a big project. Not sure on the numbers, but I'll bet that it could be somewhere between $10-20K (ten to twenty thousand dollars). It's worth a lot.

- For me, check to see if Sean or Danny would like to help with this education project and virtually bank some hours (work with the idea of a later payoff).

- Task, find that person. Who will help and run with the education side of this thing?

Steve and Sean were talking about deployment and how we need to be onsite, at times, to help the people get going. Sometimes there really isn't a good time, we just have to do it and let other things flow around us. Sean is making some plans to go help a company with a new setup and deployment down in Texas. Steve was encouraging him to grab it by the horns and go for it. That's how we used to do it, back in the day.

Steve had some questions about searching Microsoft Excel for field lengths. We looked it up and found that you can use the function =LEN(D12) where D12 is the cell address. That will give you the character count or string length. That is very similar to how we do things in other languages. Anyways, just a little tidbit.

John and I started talking about the need for a testing server. Steve and Sean took off and it was just John and I on the meeting. Some of our developers have been asking for a dedicated testing server. We kinda have one, but it still contains some older live customer data. That company got purchased by another company and isn't actively using the server, but it has things that we need to leave alone and not touch/destroy. We used to have a dedicated testing server, but we weren't actively using it and decided to shut it down. We have a need sometimes and then it chills out and we won't need it for a month or two.

The two of us did a good long session and came up with some pros and cons, budgets, and advantages of getting a new dedicated testing server. John started a Google doc and we put some info on it. Here were a few things that we came up with (these may change in the future - just a quick copy of what we were working on):

Pros

- No clients on that box - able to beat it up and even kill it without affecting anybody
- Be able to swap out the database - at will - really test with real client data without causing problems with their data
- Mock things up without worrying about cleaning it up
- Be able to point any code branch to that server so that it could interact with the data
- Code stability and testing
- Eventually move over to Lucee (as the backend server-side scripting language) - This could save us $20K per year - if we could cut out the Adobe ColdFusion licensing ($100/month per server). This is a recurring monthly fee.

Cons

- Cost per month or cost per year
- Another server to maintain
- We have to get with Wayne or John to get things planned and changed around, plus all of the current changes on live testing on servers while clients are still actively using those same boxes.
- Admin team only sees the costs not the benefits of getting a good testing environment - in John’s words, “They are not out in the weeds banging around. We need this.”
- We have a number of huge projects that haven't fully gone live yet, due to some little hitch or merge or overwriting code. Thousands of dollars of development that we can't use or sell yet.

Maybe use data 5 - Currently about $400/month - $200 CF and $200 DB

Budget of 5K per year

What does it cost in other resources and labor - Wayne, John, other devs?

Timing (when to do things - during business hours or after hours), loads (time of day and tasks and amount of data), and planning (looking ahead and when do we do this or that)

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

John and I will fill in more details later. After the meeting ended, I wrote a few other things down that were going through my mind during the meeting. Here a few other notes:

- Taking the time to listen. Sometimes that is really hard. Often, we are going a million miles an hour and are almost being too efficient. If we slow down a bit, we could gain some valuable insight and information. Our normal is push, push, push. That is good sometimes, but not for every case. Slow down and take the time to listen - at home, at work, and with others.

- We had a need for some specific training this morning, but no one knew where to find it or if we even have it. I know we have it, because I did it years ago, but it has sat un cataloged and undocumented. We really need to go in and go through our older videos and do some cataloging and documentation of what we've got. Even if we want to do some new training, it would be great to see what we already have, even if it for nothing more than training the trainers. There is good content, drawings, explanations, demos, questions, and solutions. Eventually, this all needs to be a part of the adilas university site and media catalog. This hasn't been cataloged yet, but here is the Adilas.biz YouTube channel with hundreds of videos, that need to be cataloged.

Research on video editing software and screen capture software. Checking out a couple of older external hard drives that had older videos from prior adilas training sessions. I saw tons of good info and data. It's just in huge chunks (hour long bocks or bigger). We will need to go through it, break it down, inventory the clips, and then publish those pieces. The content is older, but still a great asset and could be a great underlying base. I literally have days and days worth of footage (hundreds of hours).

We may go back and harness and grab some of that training material. If nothing else, it will give who ever does the new training something to stand on vs just pulling it out of the air. Lots of Q&A sessions, drawings, analogies, real user questions, explanations, demos, step-by-steps, etc. Once we inventory things and start to expose that content, that should help. Once again, it may be just as beneficial for our internal team (person who does the new training) as it will be for some of our clients. Great resource.

Here are a ton of YouTube videos - going clear back 10+ years. adilasbiz - YouTube

Here are some other older training videos. We'll be circuling back around and breaking these things into smaller and smaller pieces. We will also make them searchable, organized, and documented. That's the plan.

Research on investing and a company that invests in SaaS type models (software as a service). Pushed up some code for Dustin. Recording notes. Phone call with Shari O. and doing email stuff. General to do list stuff. Looking up adilas videos on YouTube and adilas university.

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

Morning sales meeting. The guys were going over the new business cards and asking for feedback. We got into a discussion about the user interface and how intuitive or non-intuitive it is. Danny was talking about possible small videos and things to help people get started. We also talked about doing some client feature stories and showcasing real clients and how they use the system. Danny had some fun ideas with small videos and what not.

Michael piped up and said that he has some film and video editing skills. We didn't know that. that is awesome and he and Danny may be working together to get more adilas content up on YouTube and other social media platforms. That's exciting!

All of the guys were giving their updates and what not. Shari O. and Sean were going over buttons and client settings for a small mexican restaurant. They are working on some menu items and how best to display and show things. We talked about a number of ideas and options. Towards the end of the meeting, John and I were looking at some look and feel things. Talking about page layouts and site-wide decisions for style guides.

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

Working with Danny, Sean, and Shari O. on the rafting site (demo site). They, especially Danny, were requesting and wanting some kind of SOP's (standard operating procedures) or some kind of a quick start guide. See attached for our notes. New notes are at the bottom. Mostly the session was just checking in and some light communications for today.

One of my observations is we have things all over the place. We have things inside elements of time, in physical notebooks, in emails, on adilas university, on YouTube, in help files, on different google drives, and the list goes on. We have a ton of resources, but they are not yet linked, cataloged, and organized for use. It's too spread out. That would be an awesome project to get all of that together and available to the public. That could be a future fracture type project. Training and education are huge spokes that we need in our wheel. There is a whole other side to this thing and it's on the education and training level.

Totally random, but a fun side note or thought - Think how cool it would be to go through the different system players (all 12), all of the different system business functions (12 of those as well), and the underlying core concepts. That would be awesome. Beginner, intermediate, advanced, and deep dive or backend levels. Show how things act, cause and effect relationships, where they show up for roll call, how things happened historically, how they effectually show up for roll call, and even how they financially affect inventories, banks, P&L's, balance sheets, and other financial relationships. That would be sooooo cool! I would love to work on that project.

I would love to get into the how, why, and what we are doing. The how and why really seem like fun topics. The "what" is pretty normal but allow us to do the other parts of the puzzle or passing the data along the virtual data assembly line. Getting into 3D world building and all kinds of cool stuff. So many things that we want to do and build. We just need help getting to that next level.

Meeting with Danny and going over options for embedding YouTube videos into adilas pages. We would like to use media/content, a custom player page, and make the whole things data driven. We went over some samples and even let Danny build a few pages. As a fun side note, Danny has been building out a number of quick tip videos (under 3 minutes) and we are trying to get those out to the public and spread their access links all over our site (where needed).

Just for fun, here is an older embedded video clip showing a demo of a liquor store and how they use adilas.

Chuck checked in and we quickly reviewed a few things. He and I met yesterday so we were pretty much on top of things. As a side note, he did inform us that he got admin permissions for our YouTube account and will be helping there.

I spent most of the rest of the session working on an error that Cory got from Kelly. It was a cause and effect error. The other day we increased the character limits on one of the fields. That was working great. The cause and effect came into play as those new bigger records got pushed over to invoices and quotes as additional customers and additional contacts on those invoices and quotes. Anyways, we got it all figure out and pushed up new database updates and new code to all servers. Finished up the session doing emails and clean-up there.

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

Anyways, here are some of my notes:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

I woke up this morning dreaming about adilas and what value it brings to the table. I went downstairs to record a couple of thoughts and ended up staying down there for a quite a bit of time, just recording ideas as they came to me. I then took a small notepad of post-it notes upstairs and kept coming up with different ideas. These could be expanded upon, it was just a quick, record what thoughts are coming to your mind, type of thing. I had all of these little one-liners written on about 9 pages of post-it notes. Kinda funny.

- 20 years of experience

- 250 customers

- Working model

- Trained team

- Data like crazy - tons of it

- Usage patterns

- Able to handle multi-industries (business verticals)

- People use it - daily

- Success stories from some of our clients

- Database model and database schema (what rows, columns, tables, indexes, data types, records, values, etc.)

- Code repository (huge code base)

- 10 full versions with back-ups of each version (over time)

- Documentation (things written, recorded, and organized)

- Commercial product

- Developer's notebook - full story and all that we have learned

- Able to do custom out of the box

- All of the custom code (as an asset)

- Plans for fracture (upcoming and future project)

- Established billing and revenue

- R&D and prototyping

- Graphics, visuals, and other artwork (even sketches)

- Presentation gallery - Full presentation ready gallery for business functions, attributes, key players, and core concepts

- Concepts - these are worth more than our code

- Pioneering paths and ideas

- Over 6.5 million in sales

- Willing to push the limits and try new things

- We know the pit falls, the costs, the good, and the bad - we've been playing in this arena for quite some time

- No one else is doing what we are doing and how we do it. Our approach to bring operations and accounting together is unique.

- Our story is fully recorded

- Reoccurring model and reoccurring revenue

- Support a team of 15-20 individuals and their families

- Thousands of users that use it every day

- Refinement and bug fixes

- We've built and maintained this application - we know what it takes

- We are doing it - following a dream

- Tons of video recordings and trainings

- Knowledge and experience

- Minimal debt

- Generating revenue right now

- Plans and vision for the future

- 40+ servers

- Ok with being who we are right now

- We don't have to have every client - Ok with serving those who like what we do

- Relationships with clients, vendors, 3rd party solutions, users, and team members

- Tons of intangibles

- Ecosystem

- 12 main players, 12 business functions, 12 core concepts

- Data assembly line

- 3D World building concepts

- The concepts are worth more than the code - We are one of millions of possible options vs everybody will go down the main primary path that leads to what we are doing and trying to do. If they (any other company or software system) choose to follow us, they will come down the core paths that we have found and are exploring. These are the core concepts that we are built on. There is tons of room down here (like exploring a giant cavern with tons of off shooting tunnels and shoots).

- We keep taking the next little step and keeping linking things together

- The depth of what we do and what we cover

- High-end software as a service (online SaaS model), we cover anything to do with operations and accounting, we have a standard package and can built out custom on top of that.

Danny was one of the first ones on this morning. He and I were going over some the tips and tricks for using Chuck's presentation gallery. We lightly looked around and chatted about the progress. After that, John joined and he and I helped Danny with some links to YouTube videos. Danny and Marisa are making new smaller videos and then posting them around the site, where they are needed and may be referenced easily. These are like embedded help files or help videos on the pages that use those features. This is just a small snippet, compared to the bigger project, but making progress.

I also spent some time this morning paying bills, scanning receipts, and other to do list stuff.

Watching some new mini YouTube videos that Danny and Marisa were working on. John was sharing some new client leads from a gun shop. Merged in code for Eric. Merged in code for Dustin and had to fix some merge conflicts. Just busy to do list stuff.

Emails and reviewing some of the outlines that Sean was working on. Watched a number YouTube videos from Marisa and Danny (adilas YouTube channel). Here is the link to the YouTube channel that they are working on. They are hoping to add to it.

https://www.youtube.com/channel/UCXfe0qjqW-yE5KXwBSgzCIg/videos - new adilas channel

https://www.youtube.com/user/adilasbiz/videos - older adilas channel (100's of videos)

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

Steve texted me and said that he was on a demo and would join when he could. Danny popped in for a bit and we talked about harvesting some of the existing video training that we already have and what that could look like, if we were to put some scripts to it (SEO stuff). Recording notes and other odds and ends.

Eventually, we'd like to go back through all of these videos and catalog them and find little gems of content and/or training - https://www.youtube.com/user/adilasbiz/videos

50 million videos... on YouTube... close to a year and a half of training that we recorded. I'll bet over 100 hours of training that was recorded. We haven't categorized it yet, but here is the link: https://www.youtube.com/user/adilasbiz/videos

Danny, Steve, and John were talking about SEO (search engine optimization), training, and getting the word out there. We have tons of stuff, but no one knows where it is and how to get it. We are looking to change that up as we go forward.

Sean was talking with Steve about reaching out to our clients and getting them all on board and updated to the newest levels. We are really excited to get in there and start taking care of our clients better and better from the inside vs the older outside independent model. Really good stuff. We are trying to mature and develop as a company and as a family unit.

Meeting with a number of folks. The goal was dealing with the shopping cart. We had Steve, Chuck, Jonathan, Cory, and a client on the meeting. The first part of the meeting was the client going over some of their requests. Here are some highlights from them...

- They would like to be able to send text messages from the customer queue

- They would love to have a hand-held scanner and have it automatically be able to update an unmanned cart. Some talks about using the built-in cameras on certain tablets and such. Other talks about hardware and software problems and solutions. Through the web, sometimes those pieces are hard to get to perfectly talk to one another.

- Lots of questions about barcodes, labels, and auto/bulk actions.

- They would like possible popup/modal type windows to see customer notes, maybe the last invoice, and even a modal popup on the ++ or advanced add to cart (haggle tools)

- The also spoke about major needs for tiered pricing - the same options that work on my cart favorite buttons and smart groups and tiered pricing. As part of this discussion, there were options mentioned about parent attributes, barcodes on buttons, advanced barcodes (QR codes), mini conversions, etc. This becomes a bigger and bigger need. It also needs to be more standardized. Lots of options, but because it could go so many ways, it is hard to find the correct path. Too many options.

- Along the tiered pricing vein, there was also a request to be able to assign items (subs or child packages) to a pricing tier through the build new PO process (bringing in the items and assigning them to a pricing tier as part of the inbound process).

- They really want a fully interactive cart, yet still locked down, yet still super powerful, yet super simple, yet, yet... Lots of requirements.

- Training mode, how to get to the best training and how to connect the dots. We have help files, news and updates, videos, etc. - but we need a way to get to that really quickly. They, the client, were also requesting that each new feature has a full tutorial and/or video. They only wanted the things that were fully done to be added to the news and updates.

- They would love for more onsite or local training options. They love the time and are willing to spend the money. They would love to get the training options to be standardized and regular (scheduled and consistent).

- They love the bulk update cart functionality

- Being able to bulk print labels and skip steps (save as a quote or cart checkout). The also wanted to be able to flag certain items that they only need one label vs multiple new labels per quantity, etc. It sounds like it could be pretty deep. There were also requests to be able to bulk print labels from the PO. Calvin's new adilas label builder does do bulk labels for invoices and PO's. They just might need some training.

- Online orders, ecommerce, and even options for delivery.

- In the cart, being able to see it at all times. Having some sort of split screen where there are items or look-ups on one side and all of the items on the other side. Lots of one pagers with asynchronous connections and easy flow through the sections and/or pages.

- We love ideas and helping to push the ball forward. The needs keep coming. We just try to keep solving those pieces as we can.

- We also allow the clients to chime in and help us prioritize, fund sharing, and have a say in where things are going.

////// more notes after the client left - Just Chuck, Jonathan, Brandon, and Steve

- Steve - a big thank you out to both Chuck and Jonathan - you guys are stepping up the game. He was also talking about collaboration between the different developers and how cool that will be.

- There may end up being 8-10 versions or variations of the shopping cart. At some point, we need to separate the logic from the view/design. Jonathan was also talking about putting the specialty features into settings so that each cart may be more configurable. Good stuff.

- Questions from Jonathan about market analysis and what does that say for us? Sadly, the reality, we haven't done anything there. Lots of options.

- There were some talks about having a system to run your stuff vs trying to marry all of the individual pieces together. There is pain on both sides, but we are heading towards the systematic type approach. Trying to bring all of these things together.

- Time to value - how many clicks to get those needs fulfilled. Not that we can't do it... we just need to figure out how to help speed up the process and make it easier and more easy to get to those pieces and features.

- Smoothing out processes and making it easy to get to the places that they need to. It kinda comes down to navigation and visual flow process. Aka - the full user experience.

- Steve was talking about how making these pieces work together to get all of the POS (point of sale) systems, inventory tracking, CRM (customer relationship management), CMS (content management systems), accounting, reports, and backend storage all in one place. That is the dream.

- Some of our clients are virtually starving for instructor lead training. Jonathan is saying that there is a barrier to entry to this... meaning the learning curve to fully know adilas. We need to help provide it and also help to standardize it. Small talks about competition, reps/consultants, and ways of teaching the processes, pieces, and principles.

- Small mention of the adilas café and how some of that would help us provide training and service type options. You could get training from the adilas university or you could get direct training and/or hire a certain person to help fill a certain need. Think of all of the power users that could offer services and/or training. What if we could show user stats on who has done what and what level they qualify.

- From Chuck - what about a monthly webinar? We could plan it out, record it, charge for it, etc. We could do digital meetings, in-person training, instructor lead trainings, etc. As we keep updating the system, we need to keep updating the videos. Maybe even using YouTube as a primary source of training. Possible Facebook groups, tips of the day, etc.

- From Chuck - doing light idea mining when we are out and about. For example: Hey, what processes do you do to sell things? We then record that and start making some settings, permissions, and selections together to help them with what they are doing. Presets per industry. Sometimes it is so overwhelming... we could really create virtual profiles and help with settings and configuration stuff.

- From Chuck - small talks about web components and being able to customize things on the fly. Separating logic, functions, views, displays, processes, etc.

- Lots of settings and even helping those people get to those settings and help it make sense for each industry. Settings and configuration options. Groups, categories, settings, nested presets, tiered pricing, labels, etc.

- From Chuck - he really doesn't like it if we do a process and then virtually dump him in an unfamiliar page (backend navigation). That comes back to page flow and user interface. We will keep working on this. If we send the users to the correct spot, we don't lose them and we even help them know what the next step should be. This may take some mapping and design stuff.

- Trying to stay small but still looking for talent and help.

- Help file on barcodes - https://data0.adilas.biz/top_secret/help.cfm?id=413&pwd=cart - barcodes can really speed up shopping carts and there are tons of options. This is an area that could still be developed out further and enhanced. Just an idea.

See attached for a number of other resources. There are a couple of videos and some research on shopping carts and POS interfaces (point of sale interfaces).

- Camp adilas overview - see screenshots - lots of new work on the mobile side of things. Exploring all of the different screenshots and options.

- We spent some time and did a small review of the demo yesterday.

- We still used world building but we related it to pieces that they could understand (going from full abstract to hey, this makes sense - speaking their language and at their level). That is huge. We talked about how we could do the same thing in a more general way.

- The demo felt more prepared and more simplified. That was good.

- One thing that came up... tracking history and seeing who does what in the system (the hidden audit trail and use of different logins). We introduced this later on in the demo but they really got excited about it. We may want that to surface earlier as what is going on and a key feature.

- When doing the ecommerce demo... that was a little rougher. We had to keep switching between systems due to images, settings, and being able to flip to the more pretty and mobile ready version. We had a few rough spots in this part of the demo.

- Lots of talk about the permissions page (aka the football field of permissions). We want to get the permissions broken down to a better level that is easier to understand and to copy/apply. They (our users) are wanting to break them (the existing permissions) into custom permissions, sub functions, and other functionality. Deeper control, yet a simpler interface and experience.

- We spent some time and talked about the new sales outline that Chuck is working on. We used it in our demo, our morning meeting today, and almost every other meeting today. Pretty cool. We like the direction that we are headed. Click here to see a small sample.

- As we build things out (in the sales flyer)... we would like to connect these to videos - we talked about keeping things generic and highlighting the pieces vs our brand (white label options).

- There were some conversations about talking about world build and getting it into a more simple thing analogy right off bat. Maybe even some scenarios that deal with beginner, intermediate, and advanced concepts. Once again, help it be more consumable.

- Brainstorming on world building ideas... We could start with a web layout, index page and then it goes from there, or icons and a more structured layout. We spent some time talking about how to help get our users and others to get their heads around the concepts. We ended up watching two videos to help us get into the frame of mind. The links are below.

http://www.brandonmull.com/site/video-bestbook.html - Brandon Mull (author) - What makes a great book (world building concepts)

https://www.youtube.com/watch?v=RN4Ka0IXdp0&feature=youtu.be - Shannon Moore - System thinking - fun video from an older training session

1/10/24 Marisa emailed the following evaluation of needs for Adilas:

To be honest, no, we would not be ready to move over. Adilas has quite a ways to go to be ready for the hospitality industry, especially for campgrounds/parks of our size. I would say if you wanted to look at your biggest competitor it would be RezExpert. That is the only software that we seriously thought about switching to but ultimately decided to stick with what we have due to price. Our only cost at this time using Campground Master is $100/year for any upgrades and customer service. 

Graphical User Interface for Campground owners.  

Link to xd share https://xd.adobe.com/view/5c903c5b-0451-4fca-5613-5ed795812d1e-2aa1/ 

We have had a number of meetings on this project, here are some other resources and meeting notes. Many of the different notes have screenshots to show the development of the project and where it is at and/or going. See below for more details.

Meeting on 10/10/19 - click to see meeting notes and screenshots - research and ideas

Meeting on 10/15/19 - click for notes and screenshots - concept art and mock-ups

Meeting on 10/29/19 - click for notes and screenshots - more mock-ups

Meeting on 10/31/19 - click for notes and screenshots - mock-ups of the revenue and expenses sections

Meeting on 11/7/19 - click for notes and screenshots - first full mock-up - multiple pages and topics

Meeting on 11/12/19 - click for notes and screenshots - full mock-up plus some mobile screenshots

Meeting on 11/19/19 - click for notes and screenshots - mock-ups for mobile

Meeting on 11/21/19 - click for notes and screenshots - more mock-ups for mobile

Meeting on 11/26/19 - click for notes and screenshots and a video of the meeting (virtual tour of the app to date) - full mock-ups and mobile mock-ups

Meeting on 12/3/19 - click for a couple of screenshots - moving from graphic concept into first round of coding.

Meeting on 12/5/19 - click for notes and screenshots - mock-ups from graphics to code

Meeting on 12/10/19 - click for notes and screenshots - more mock-ups from graphics to code

Meeting on 12/12/19 - click for notes and screenshots - code mock-ups - playing with different backgrounds

Meeting on 12/17/19 - click for notes and screenshots - code mock-ups

Meeting on 12/19/19 - click for notes and screenshots - code mock-ups and browser testing

Meeting on 1/23/20 - click for notes and screenshots - starting into the customer side - new website mock-up for WanderWays

Demo video 1/28/20 - click to view demo (youtube) - 3 minute video to showcase the product to date - marketing efforts

Meeting on 2/12/20 - click for notes and screenshots - new website almost done and interactions between designer and backend code writers

Meeting on 2/19/20 - click for notes and screenshots - new color pickers and settings for look and feel

Promo video provided by Marisa on 2/26/20 - youtube video - 3 minute promo

Meeting on 2/26/20 - click for notes and screenshots - working through settings and starting into project management

Meeting on 3/21/20 - click for notes and screenshots - Working on settings, color pickers, site admin, roles & permissions

There was a small break in the project and we had to set it by the side, dealing with funding, and availability. There were a few small meetings and progress, but nothing major to report.

Meeting on 7/22/20 - click for notes - Meeting to get the project back on track and moving forward.

Meeting on 9/2/20 - click for notes and screenshots and a new mock-up - Reporting on the customer frontend pages and application.

Analogies for defining deeper processes

Steve - Business is like a pirate ship - (who is the crew, are they good/bad, who is doing what)

Kelly - Business is like a body - (what is your tool to get to your goals)

- Goals and sub goals to get to the bigger goal. Adilas is just a tool. The people who use it are the ones making the goals.

- Talk is great, but we need to work on some implementations (getting out there and doing it).

- How do we implement the tool... this drives customer satisfaction.

- Adilas is so flexible that sometimes that is a problem

- Kelly was not saying don't be flexible... but we need a standard starting place

- There are new things that get launched all the time... without any training - this keeps deepening the need for good reps and consultants

- Unintended consequences

- Pressure and pain drives the current development cycle

- Everyone looks to a system to be "The" solution - systems can do a lot of things, but they can't save you from yourself

- Good physical control of the system is a huge key - stick to the plan and then go from there

- Many of the business owners don't even know what they are doing and then that translates to their business processes

- Helping to setup mini goals for the client... miniature options for success

- Addressing the physical before jumping into a digital realm

- Sometimes, a companies leadership will drive things right into a ditch

- Kelly has been doing some research on what other developers and companies do to help standardize things

- A good setup will make or break the whole deal... from there forward (what milestones are set and achieved and was there a good handoff between the software company and the rep/consultant)

- Accountability practices

- When a client has a question, have tech support use the user guide as their answer. As a side note, Shannon and Brandon are working on the adilas user guide.

- On numbering... instead of using a straight 1, 2, 3, 4... system (single numbers). Maybe think more along hundreds 100, 200, 300, 400... (lots of room to add and subtract as needed)

- Sub attributes - Kelly doesn't think that piece is fully "strong", yet we are building upon it. Steve thinks the concepts are pretty good. We just need to fix some of the coding pieces to help get reports, searches, and exports more up to speed.

- Steve was talking about the complexity of even servers - we had a meeting this morning that just dealt with servers (hours and hours). So many moving pieces and working with somewhat limited funding and talent options.

- Due to our current size, we almost have to say - in order to setup clients, you will need to setup an adilas specialist (in your company) and we will help train them. They will then help push that ball forward.

- Some of our squeeze points deal with persons who have the skills, talents, and time. We have masters like Steve, Brandon, Kelly, Daniel, etc.

- Start by defining the language that we are speaking - adilas is its own language - A good starting point - how do we communicate things, as a company

- People want organization and structure - being too thinly spread can be a big problem

- Allowing dreaming and custom options - we love it but that could be a problem - we may get in trouble by giving them too much or too many options.

- Maybe have them run with the standard options for 6 months and then talk about going into the custom realm - we have seen problems with people going into full on custom too quickly.

- Like an airplane - put the oxygen on yourself first and then help others around you - you end up selling what you do

- Setting clear expectations

- Maybe have some tools and education (training materials) about how to run a business and how to use the tools - Steve has had the ideas of putting on basic business seminars across the country. We could use the adilas tool as the backbone of the basic business training sections.

- We are seeing a bigger and bigger need for training, guided training, and even self training. This could be checked and/or quality assurance based on skills, tests, scenarios, sign-off's, etc. In traditional learning environments, there is standardization, testing, feedback, etc.

- What about using elements of time to help monitor the virtual checklist of what has been done and to what level?

- We do need a team, but at what level do we need to get to? That gets tough. People resources are always tough to manage.

- More training sessions - pros and cons to our current model - people want to learn in privacy - some of the training sessions get out of control (high jacked).

- Vocabulary and what things do and what we call things is a big part of the puzzle

- Some people don't want to know the why (that takes time)... they often just want to know how (show me quickly so I can do it)

- Education from gaming - 2 minutes or less - quick YouTube type mentality

- What kind of users are you? Do you like to self train? Do you want the easy button? Do you shoot from the hip (all the time) or are you a detailed oriented person who likes to organize and manage things? Great questions... help pre-qualify them in a way. The adilas system works best if the users want to put the things into the system (feed it) and play the whole game.

- Sadly, we can't fix everything... sometimes, we have to just go to the next person

- AI (artificial intelligence) and where things are going - automating setups and then automating tech support - keep going where things are going (skate to where the puck is going)

- Working on your company vs working in your company - focus on working on it and making it better

- What is the low hanging fruit and where can we start?

- How many touch points are needed to get someone setup? Who setups up the quote? Who turns things on? Who setups up things? Who does logos and watermarks? Who does labels? etc. - you get the idea - try to automate as much as possible.

- Somewhat of an internal bulletin board - who is doing what and what changes are going on in those shifts

- Just adding bodies doesn't always help things - events happen, how do you deal with that - there has to be an internal training process to take care of those things. It comes down to core things that are needed. Who is going to do those things (virtual checklist of what is needed)? Light talks about templates.

- Function vs fashion - where do you spend your time? We may not be able to solve everything but we can try to take the edge off of things. We want to show them what is possible. We want to present a nice package. We also want to make sure that things work (functionality) for them.

- Steve and I are trying to get out of the way. We are trying to fully get the process all setup and dialed in. Sometimes, if we are a pivotal part of the puzzle, it just doesn't happen, we are maxed out.

- Going back to consistency... We know we need it, we are trying to work through it and then actually using it. What can you expect every time? We also need a timing of those events... when should we do things, not just what should be done. There is a difference.

- Sustainability - We need to keep doing this (our business) for years to come... let's set ourselves up for success.

- Building our own processes to help with project management, task management, and to do list checkboxes before doing x (fill in the blank). Templates and automation processes. Help share the load.

- Things are changing super fast... nobody knows everything - we are currently letting different parties run with what they think needs to be done vs having one person giving orders and then getting a good return and report type process. Currently, it is somewhat of a community type effort.

- Why are we doing it and should we do it? Check this out before you jump in. Think of the consequences first.

- Kelly is going to help get a group together to help bring up the structure level and get the oars (some driving and direction) into Kelly's hands. We need a good driver who won't run us aground. We are going to let Kelly run with some things on the core management side of things.

- We are going to be starting at the very beginning and then going from there. A great place to start.

Ideas for a balanced approach... imagine a plate on a pivot point or a fulcrum - how much of each section could you load up without tipping things over or what is the virtual balance point? Good questions. We are seeing needs in the following areas. There may be more... System development, number of clients, and education

 -System development (look and feel, new functions, logic, database, and basic functionality)
 - Number of clients (sales and number of system users - feedback, funding, and ideas)
 - Education (how, when, why, where, how much, etc. - videos, graphics, text, verbage, flow processes, industry specific, trends)

- Here is a good question, how do you manage the demands? What about funding? What about skilled people power (skilled talent)? Those are resources that need to be managed and balanced as well. Interesting.

- We talked about possibly stopping development (system development). There are pro and cons to this. We also talked about - can we even stop that? It seems to keep going on for as far as we can see.

- We talked about how good reps and consultants are filling in the gap between new clients and education and new clients and new system development. They, the reps and consultants, become a virtual motor or engine to help people keep going, train others to do what is needed, and push things forward. There is no standard training material that is provided by adilas right now. The good reps and consultants provide those missing pieces. They are a super valuable piece of the puzzle.

- If we keep building, how to do we support (education) that new development?

- If we made a full on system user manual, would anybody actually read that? There might be a few, but most would like to know that one exists, but they want their information and training quick and on demand. Almost the "google it" - type mentality. A quick YouTube search, looking for videos that are 2 - 5 minutes (max). What would help us be the most successful in that realm?

- What if we put in small videos and started using the small little gear on the side of the snow owl look and feel theme (additional page settings)? Put some small videos in place and help the education process by putting assets in the right place.

- Shannon and I will be turning and going back to filling in some more content on the user guide. We will be turning all of the content into different elements of time in the adilas university site. We are then able to show/hide content, edit things, add photos, show user threads (sub notes and comments and/or forum type discussions), add videos, add other media (Excel, Word, PDF, images, etc.). Turn it into our own content management system (CMS). Making these changes will be a game changer for us. That will really help. Exciting.

Working with Bryan and merging in some code for refunding Expo payments. This is a 3rd party solution and payment service. They are also trying to be a white label solution and help to resale adilas using the Expo name.

Part way through, Shawn showed Bryan and I some YouTube videos that he made with multiple takes of himself singing the same song. He said that it might be fun to do something similar and have adilas both show a teacher and a student and show some basic adilas concepts. Great idea. Who says it has to just be one person. It could even be animated and/or two fun characters having a conversation. It all comes back to time and available funding. Some fun ideas.

• Letters to Dave, Bryan, Garrett, and Calvin
• Bear 100 CSV and Record new Bear 100 notes and requests
• Google Maps Stuff
• Headers, footers, and CSS stuff
• Check the Adilas Logo on the YouTube Video Section...It looks bad