Research on the data assembly line, new school accounting, and 3D levels. Found a bunch of old entries that Shannon and I were working on for the user guide. See section 11, for concepts on financials and accounting. Here are a number of links to show where some of the information is.

General adilas notes from back in 2008. This is when Brandon and Steve were working on the balance sheet. This is when the concept of allowing the data to flex until everything is correct or back to a stable spot. Web link - developer's notebook - balance sheet stuff in 2008

Writing out the progression of what we have learned thus far. These entries go forward from 2008 to the end of 2014. These are some notes from Brandon while helping to train some new interns and developers who were helping on the adilas project. These notes will be shown in two sections. One is the general notes from October of 2014. They will show the general flavor of what is going on at this time in history. The other notes will be specifically 10/14/14 where the actual entries hit the developer's notebook. Here are those links:

Web link - October 2014 - General developer's notebook for the month of October 2014.

Web link - time_web_gallery.cfm?corp=371&id=2894 - Specific date in time when the concepts first hit the notebook as a single entry. Progression of operations and accounting.

The next major time period was in March of 2015. This was a different set of developers that had questions and wanted to see how operations and accounting played together. This will have two sections as well. This will have the month of March 2015 and then a specific time when the process was described in more detail, with a slightly different flow, which helped in presenting the ideas. Here are those links:

Web link - March 2015 - General developer's notebook for March 2015

Web link - time_web_gallery.cfm?corp=371&id=3618 - Specific date when the process was explained using a giant Whiteboard at Bridgerland Technical College.

Adilas Key Contributors:

Steve Berkenkotter - Main owner and business partner - original ideas, concepts, and training - sales, relationships, dreamer, visionary, custom code, coordinator, builder of the first industry specific skin, and the list goes on. Huge player in the adilas story and timeline. One of the original owners in Moring Star Automotive - where the system came from. There are three known Steve's in the system notes. Most of them are this Steve (99 out of 100 times). He won't admit it, but adilas was his brainchild.

David Berkenkotter - Steve's brother and business partner in Morning Star Automotive. David was a system user and helped us create the adilas quick search. He liked using that feature, the quick search, but it only existed on one page originally. He wanted us to put it on every page. That ended up being in the header. He was also one of the original partners in adilas. Power user in the system. Sadly, he passed away due to cancer.

Shari Olin - Commonly known as "Shari O.". She worked in the accounting department back in the Morning Star days. She has been somewhat of a mother hen to help all of us crazy chickens keep going. She helps with customer support, training, payroll, bill collection, and tons of backend office functions. Major power user. Just being silly, but she can have the mouth of a sailor but the heart of an angel. Part of the adilas admin team and a great friend.

Craig Leitner - Also part of the original Morning Star team. Craig was the automotive floorplan and bank guy. He is a power user in the system and does a lot of bank reconciliation and other tasks. He currently works with Steve and asks as the adilas controller (money flow guy).

Cory Warden - Originally an adilas rep and consultant. Cory become part of the team after being a rep for quite some time. She helps with customer care, client support, project management, and keeping the team on track. She also does all of the news and updates and other training material. Cory does tons of oversight type services for our clients. Power user and part of the admin team.

Sean Carlton - Sean was a manager at a Cannabis dispensary in Colorado that used adilas for years and years until they sold. Steve recruited Sean to help with sales, deployment, and training. Sean brings lots of usage experience. Often, he is one of the helpers if we need to send someone onsite to help with a deployment or training session. Power user.

Brandon Moore - I'm one of the guys that writes most of the developer's notebook entries. Originally, I was hired by Morning Star, the automotive dealership, to help with data entry, accounting, and website stuff. I ended up being one of the main adilas developers and architects. I build content, write code, help other developers and team members, and help with training. Helped start the project back in 2001 under the Morning Star name.

Chris Dunsey - One of the first adilas interns (developers). Helped with a number of projects. Ended up being somewhat of a consultant later on.

Shawn Curtis - Kinda a funny story. He was taking a developer's class at Bridgerland. He knew my brother Russell. He asked to join our developer class and became one of the first interns along with Chris Dunsey. Shawn ended up helping with payroll and other projects. Some of the photo galleries in the system came from Shawn's help. He also worked on the media/content (file upload) pieces. Later on, he did more payroll work and acted as a buddy to Brandon and did some consulting work. We worked together for years and years.

Russell Moore - Russell is my younger brother. Originally, he was added to the group because of his graphic skills. He ended up being a great backend developer and project manager. He has also acted as a trainer and mentor for Brandon along the way. Much of the current system came from projects and efforts that Russell was involved with. He has also been Brandon's AI tutor in recent years. Great help to the system. Huge contribution.

Chris Johnnie - He is an entrepreneur who teamed up with Russell to help create a company called "Adilas For Business" or "AFB". Eventually, both Russell and Chris sold their pieces back to adilas. They were honestly the first ones to really try to run as a white label of adilas. This was back in 2015 and 2016. Chris really helped to push the product to the next level along with Russell's help.

Danny Shuford - Longtime friend of Steve's. Danny helped with some website design, sales, and videos for adilas. He even got into creating custom PDF labels for clients. Light development work.

Marisa Shaw - She is Danny's daughter. Danny brought her to an adilas training event in Denver, CO. Marisa was the star student. She ended up helping with some graphics, flyers, marketing material, teaching, instruction, and planning. Power user. Very helpful.

Shannon Scoffield - Shannon is Brandon and Russell's sister. Her maiden name is Shannon Moore. Huge help and virtual assistant to Brandon. She has helped with training, project management, and content creation. Most of the major content sessions were or have been with Brandon and Shannon working together. When they, Brandon and Shannon, were traveling, Shannon was one of the primary adilas instructors. If she was teaching Brandon was taking notes. If Brandon was teaching, Shannon was taking notes. Power user.

Cheryl Moore - Cheryl is my mom. What an asset. She owns a small business and has owed a few different ones. When we were doing training sessions, she came to every one of them. She asked wonderful questions and was a great supporter. Sometime, I would use her as a test subject - can my mom do this? If yes, we are good. If not, we may need to keep tweaking it. Thanks mom!

Wayne Moore - Wayne is my dad. He was my hiking buddy and more than willing to talk about ideas and concepts on our walks and hikes. He helped out with video stuff and was a great coordinator for making other connections. He worked at Bridgerland (technical college) and helped us get setup with classrooms, computer labs, and other great connections. Huge cheerleader! There is another Wayne, Wayne Andersen, he is a backend developer, systems guy, and database guy.

Wayne Andersen - This Wayne lives in Portugal and helps with all of the backend security, server, and code testing. Major skills, writes code, helps push all of us to new technologies, partially retired but loves to play with tech stuff. If you search for Wayne and it deals with concepts and coordination stuff, that's my dad, Wayne Moore. If you search for Wayne and it sounds like a master backend guy, that's Wayne Andersen.

Alan Williams - One of the lead developer's at adilas.biz. Alan joined us in 2015 and quickly came up through the ranks. Trainer, CTO, team lead, master developer, prototyper, and system architect. Alan has helped with many projects and features over the years. He also helped Brandon with some of the prep work for the adilas lite (fracture) plans and project. Sometimes called "Dr. Alan" by the other developers. Example: This might be a project for Dr. Alan.

Bryan Dayton - Bryan has been one of the most versatile guys on our team. Originally, he joined a development class out of curiosity. He and Brandon live in the same town and know each other from church. Bryan has done more custom code or small system projects than almost any other developer. He also joined the team in 2015. He helps with sales, custom projects, pushing on projects that he thinks will yield a return. Lots of work on the adilas lite and fracture project. Very hard working and versatile.

Dustin Siegel - Developer who helped with numerous cannabis and cultivation type projects. He worked directly under Steve to help with that business vertical. Many of the original pages that Steve built were taken over and remade by Dustin.

Eric Tauer - Developer and custom code guy. Originally, Eric knew Steve and lived in Salida, CO. As a note, adilas is Salida spelled backwards. Eric has a background in database work and data warehousing. Eric has done tons of custom systems for clients. Often, Eric would pioneer certain features or logic, as custom code, and then we would bring those features into the main adilas application.

Garrett Kirschbaum - Adilas intern and then full developer back in 2015. Stressful time of building and expansion. He and others helped run the adilas shop with Brandon's help. Garrett was a great developer and helped us standardize a number of tools and features. He was the first developer to work on sub inventory, back in the day. He also did other projects and helped with some developer management stuff.

Charles or "Chuck" Swann - Charles was an instructor at Bridgerland for web development. He builds custom websites, does amazing mock-ups, prototypes, and is a CSS master (styling a website using code). Chuck worked with Russell to help with redesign work, projects, and vision. Chuck worked fulltime for a number of years and now works and coordinates work done by a small hand-picked design and development team. Anything that needs some design loving gets passed over the Chuck and his small team.

Steve McNew - Friend of Steve Berkenkotter's. This Steve helped prep some whitepaper documents to help with getting adilas standardized and some internal audit type stuff. Mostly white papers and putting things down on paper. He ended up getting hired by the local school district and wasn't able to finish the process, but he got it started. He asked some great questions, and we had some good conversations.

Abby Elkins - Abby is Brandon's daughter. Her maiden name was Abby Moore. Abby, when she was little (10-12 years old) helped with some of the original concept artwork for adilas. Later on, she helped with content for the presentation gallery and then the adilas lite plans (fracture). Currently, she is working graphic artwork for different adilas pages. She's now in her mid 20's and has some awesome art and content skills.

Aspen Moore - Aspen is Abby's younger sister and Brandon's daughter. Aspen helped Brandon with some planning and counseling (mental help). Aspen also did some general business consulting with her dad Brandon.

John Maestas - Developer, backend server guys, and designer. John came to us through Dustin. John was uses as a jack of all trades on the backend and frontend. He did numerous projects, documentation, payroll, and page redesign projects. John was also very help to Brandon in working on the notes and comments on the SWOT analysis document. Many other projects as well. Good vision of the future.

Kiva Berkenkotter - Steve's wife. She helped Steve with various projects and planning sessions. At one point, she was in charge of paying commissions and collecting monthly reoccurring payments. Huge supporter to Steve!

Heather Moore - Heather is Brandon's wife. What a trooper. Cheerleader, support, ideas, and consulting. Huge asset to Brandon (me). Thanks Heather!

Jonathan Wells - Designer and mock-up guy. He helped to map out the system and created a number of deep mock-ups for adilas lite (fracture) projects. Great job catching the vision and putting those pieces into a visual representation. We still refer to his work when talking about fracture (future project for adilas).

Jonathan Johnson - Business consultant from Epic Enterprises. Met with Brandon and Steve in end of 2019 into 2020. Really helped us see some needs and opportunities. Later, helped Brandon with some other consulting when trying to define the fracture plan.

Calvin Chipman - Windows software developer. Calvin also did a bunch of web-based work, database stuff, label printing, and API socket stuff. Calvin was the first developer to use the adilas API's to create a native mobile app for a client. He also built a number of special developer tools used by some of our team to speed things up. He's the tool guy!

Cody Apedaile - Bryan Dayton's cousin, Cody helped with a bunch of JavaScript code and changes. He also spent some time working on the UML diagram for the adilas database. We didn't get things finished, but he was working on a new build your own interface (custom to you) for adilas. We ran out of funding. We want to get back to that project at some point.

Dave Forbis - Dave was the official "high tech gofer". He did a bunch of things. Graphics, project management, brainstorming, planning, sales, and helped with managing developers for the adilas shop. He was another great student. He came to a number of training courses and brought so much to the courses. He was also a big support to Brandon during some rough times.

Josh - There are three Josh's. Josh Wheeler, Brandon's friend and developer. Josh Sagert, developer and adilas user (worked tons on the discount engine), and Josh White, Steve's friend from California. Josh White has brought us a number of bigger leads and bigger players, like franchises, and other higher-end clients. Anything recent is Josh White, from California. He helps with networking, sales, and dreaming of new things.

Suzi Distelberg - Sales, training, and deployment. She also worked with some custom projects and doing step-by-step user guides. She has helped with all kinds of projects and even gone onsite for setups and training. Great asset!

Kelly Whyman - Kelly is Dustin's wife. Kelly was single handedly the best independent sales rep that adilas had. She did training, consulting, and sponsored a number of custom projects. Kelly helped Steve and Brandon with reports, functionality, and other things. She got so good at things, state contracts snagged her up to work at state and multi-state level stuff.

Molly Hennessy - Molly was another independent sales rep and consultant. She had numerous clients and got into doing SOP's (standard operating procedures) and other high-end documentation and training. Molly was an entrepreneur and even started creating some of her own product and services. If you search adilas on google, some of the other results are from Molly. Super creative and a great consultant.

Hamid Karbasi - Developer - He has worked with Brandon doing small websites, training, and small tasks. He currently is a manager at a retail store and brings some managerial type skills to the table. Willing to talk about concepts and how they apply to retail and other environments. He is also lightly helping with some planning for fracture.

Gene Spaulding - Friend, entrepreneur, and businessman. Gene is an old college friend. We had a number of friends in common. He has been a small mentor to me over the years. Way back, before adilas, he helped me get my first business loan for a project that I was working on.

Sharik Peck - Friend, entrepreneur, public speaker, physical therapist, and businessman. Good influence and mentor in ways. Sharik and I used to exercise together back in the day. Many of fun walk, run, and weightlifting session. Learning some conference and training skills from him and his wife. They have done really well pushing their product lines and doing some marketing. Trying to get some ideas.

Bridgerland Technical College - Use to be Bridgerland Applied Technology College. Not a person, but a huge help. This is a local technical college in the Logan, UT, area. Brandon's dad, Wayne, worked there. Tons of assets. They provided classrooms, training options, computers, and even an small incubation spot (starter office space) for the adilas shop during the startup phase. Huge asset!

McCorvey's Pro Shop - Also known as Bowling World. Client that had multiple locations. The started out with around 30 and grew up to the 90+ location level, all using adilas. Long time client.

Emerald Fields - They were the first client that wanted their own fully dedicated box and server. They had multiple locations and requested some custom code, reports, and features.

Beaver Mountain Ski School - Client that we helped them track their ski school (snow sport) lessons. Students, instructors, classes, and schedules. Custom interface dealing with elements of time and flex grid.

Bear 100 - This was the first event or annual event client that we did. They used the system for about a week each year. They had 350+ runners and their families that would be on the site for multiple days straight. It was a 100 mile running race with 13 aid stations and a small social portal for the family and friends to watch their runners. This one was special as it had custom input options to upload CSV files to populate the database vs normal HTML form field entries. Records were sent in batches from remote places to adilas for storage and race progress.

High Valley Bike Shuttle - Online ecommerce and scheduling client. They also have a cafe and small retail store. Fun online scheduling and bulk flex grid projects.

Herbo - Mike Roundtree, owner of Herbo, was the first company to do a small white label of adilas. Mike has been a great asset to Steve and the two of them have worked on projects, plans, and dreams. Herbo also has a custom payment solution that they are trying to market and get rolling. Mike has been a great supporter for years. He is also a certified CPA and that credential helps us and him. We would like to get other CPA's on board as well. Thanks Mike!

Nxtlinq AI - AI assistant. These guys really pushed us to get an AI agent inside of adilas. Tons of development took place and lots of prep stuff. We wanted to do a 3-part plan for integrating AI. 1. Teach it how to navigate using the AI quick search (check - done), 2. Teach it all things adilas. and 3. Teach it how to be clear up at the consultant type level. We only got the first phase done. Lots of other plans and such, but we ran out of funding.

Grok AI - Steve loves using Grok. He has built a number of image generation options inside of adilas. He is also working with Grok to feed it data to help with analytics and AI insight. This is not finished yet, but we may end up using Grok as an AI assistant inside of adilas. We have simple and emerging connections available right now but need to really polish things up before going live with the AI assistant options.

ChatGPT AI - We have started using ChatGPT to help with code, explanations, explore resources, planning, and help with training and flow for people and other AI bots. Currently, Brandon, Steve, Bryan, Alan, Josh, Russell, Chuck, and Wayne are using AI in either ChatGPT chat sessions or some other form of AI. We have some using Copilot, Gemini, Claude, etc. AI is actually helping in many ways. ChatGPT is a big one for use. Anyways, they are earning their place in the adilas key contributors list.

There are so many more that I can't list. Developers, users, power users, reps, consultants, trainers, clients, accountants, friends, family, and even critics. They have all helped out the idea farming process and progression. Good stuff! We couldn't have done this alone. It takes a community to do what we are doing.

Research and prep work for working with ChatGPT on the SWOT analysis document. We ended up going so much deeper than just the SWOT analysis (strengths, weaknesses, opportunities, and threats). I did some research in the developer's notebook and did some sub look-ups as I went through the session with ChatGPT. I really enjoyed it. Here is the full link. For the record, it is pretty big, but golden... Tons of little gems.

https://chatgpt.com/share/69a9d788-a288-8007-949a-58d1ed5ccde2

Here is a small section, from the end of the chat session. I thought that it was pretty good overview of what we did.

From ChatGPT: Brandon - before we wrap this huge session up, I want to say something.

You came into this conversation asking for help with a SWOT analysis.

But what we actually uncovered together was:

The Adilas Story

The One-Page Overview

The Strategic SWOT

The Value Add-On Core Model

The Big Picture Map

The Explanation Ladder

That's basically the foundational narrative of the platform.

And honestly, it's a lot clearer now than when we started.

Emails and recording notes. Added the video link between Brandon and Russell, discussion on the white label investment options to the adilas investment opportunities page. It is kinda raw, but covers some great questions and answers. Here's the history, on 2/11/26 Russell and I met to go over some training. We recorded the video on that day (eot # 12683). Then on 2/23/26, yesterday, I reviewed the video (eot # 12718) and made a few more notes. I asked Russell and he said that I could share it. I thought that it had some good content in it.

Reviewing a video from a meeting with Brandon and Russell, from a couple of weeks ago. As a note, Russell is my brother (younger), but we have worked for years together on training and projects. Russell sent me the video, but I was too busy to go back over it. The goal was to get some of the Russell's questions, from the video, and then address those questions in order to be more prepared for future talks and chats with investors. This video was originally part of a practice session about pitching the white label investment option for adilas. See element of time # 12683 for the original notes.

Here are my notes after rewatching the video.

- Question from Russell - what am I going to get for my investment of X? I don't care about owning it, I just want to make sure that I get the tool that I need, in order to sell it.

- What about future availability and being able to change or fix things in the future?

- What's a good flow so that I can sell it to my customers? I am willing to play for that. I don't need it perfect, but I do need to know that it can do what I need it to do.

- Possible matching funds - say something like $10K them and $10K us

- Salesman like to promise things (known fact)

- White label skins are part of the master plan

- Part of the plan is helping them, our clients, see that it is up to them to pitch and sell this thing (what we create). We help with the plans, the backend tech, and getting you a product that you can sell.

- People want us to build, build, build - our plan is not to do that, meaning for free. We don't mind building and building, but we can't do that just based off of promises.

- We already have 75%-90% already done. We help you get what you want and then you go from there.

- It goes back to that plan and what can we do? - Sell me on it

- Read over the document to get the idea of the rules and how things will play out (link to the investment options pdf).

- How are we going to find these partners, entrepreneurs, and angel type investors? - Work with other entities

- Russell went back to his "flow" stuff. That was really important to him. If he can get that working, he is good with everything else. After the flow is set, then we talk pricing.

- Figuring out a benchmark (features and pricing) and having whatever is needed for the industry. Then making sure that he has all of that plus other important stuff. He was talking about reselling the services on a mark-up. - Making your own package, and then selling that package, etc. - Wholesale costing.

- Make sure that you can find those people - If they can sell it, get the flow down, and make it really rock, then game on - It has to look good, function well, takes care of my customers, or I can slide it under (meaning price it better than my competitors), then I will invest. I need to feel secure that I can make this work.

- Get into some of these investor groups and see what they say - Making the pitch and then getting some feedback - Ask them to put me through the ringer of education - I want to know what investors are looking for - Get involved with people in those sectors.

- Russell said that he is more interested in white labeling vs straight investments.

- Talking about levels of control - control of the company vs harnessing what we already have - often, buying in means I want to take control - There is a difference between normal investing vs white labeling.

- Russell wanted to make sure that his stuff is protected

- Audience - Bringing code and visuals to the audience

- Planning and coding - Plan well and hit the mark - Projects need to be 80% planning and 20% coding - We plan and then make exactly what we are shooting for.

LTF was a product done by Brandon Moore back in the early 2000's. It was originally a Flash based product that was distributed on an interactive CD-ROM. Most people don't even have an optical drive anymore (what you use to read a CD for your computer). This is a link to the project as a Windows .zip file.

LTF - Learn To Freeride - Volume 1 - Flatland, Rails, and Jibbing (.zip file) - After downloading, for Windows run the LTF_win.exe file. That will start the program. For Mac, download the Adobe Flash player and open the start.swf file (Flash file). There used to be a better Mac version but I'm not sure where it went.

Learn To Freeride was a company that taught snowboarding freestyle skills and moves. Back in the day, one of the only ways to distribute content was via CD. People were still on dial-up modems for Internet connection. The original CD had about 270 video clips, built in video player, music, and three different skins (classic, retro, and punk). This was before apps, but basically, it was an app. Kind of a cool piece of history.

How this ties into adilas.biz - Brandon was working on this project in 2004-2006. This was right about the time that Steve Berkenkotter, founder of adilas.biz - recruited Brandon to help on the adilas.biz project. Brandon had taken out a business loan to pay for and fund the LTF project. Steve offered some database and web work, and Brandon took him up on it to help pay off the loan. If you want more history, here is a small history document covering that time period. Click here for the PDF file - adilas_history_bio.pdf

Recording notes from yesterday and today. Things change so quickly. It's hard to keep up. Pushed up some videos for the adilas lite plan showing the interview with Brandon, back in 2013 at Bridgerland. If you go to that page, go to the section labeled interview to see the video links.

Reviewing the first two (2 of 4) videos from the Bridgerland Technical College (BATC or BTech) from back in 2013. This was an interview about adilas and what are story is about. The first two videos are about 10 minutes a piece. Good audio and the videos were mostly of myself (Brandon) talking about adilas and some of the journey.

BATC_video_1.mpg - Video 1 about 11 minutes

BATC_video_2.mpg - Video 2 about 9 minutes

There are notes from this morning... 1/12/26 - these notes may seem personal - they are what happened on Sunday 1/11/26 - I recorded them on Monday. They play into the mix as this is the backing for us trying to do what we are doing. It is personal, but still super important (to me at least).

- I was fasting yesterday - good session - had a great "download" (term from my mother) session and filled out some post-it note pages. See EOT # 12616 for details.

- I spoke in church on Sunday - I had fun - hopefully it went okay - I tried to follow the spirit.

- I also enjoyed some of the other meetings at church - Lee Lower gave a fun thought in Bishopric meeting about a guy and some healing and mending relationships - really good message.

- In the next meeting, young men and young women leader training, Reese Hulbert gave a great thought on Satan and how he tries to make us run and hide - then talking about overcoming that fear and following the Lord - how can we dispel that encroaching darkness, shame, fear, and negative thoughts - super good message.

- I was praying - as I finished, I was looking at a quilt on my bed - the diversity is awesome - all of it fits and lays together to make the whole - so fun.

- During sacrament meeting, Lilly Atkinson spoke on cheering each other along - she ended with a challenge - "take one more step" and "bear your testimony" - I really liked the take one more step challenge. Sometimes, that is all we can do.

- Heather gave a great talk in church as well. I took a bunch of notes in my church notebook - great message - moving forward with joy - becoming - "be" & "coming" - breaking things apart - we all get to be part of His work.

- Plan as if for year - act as if for years - D&C 51:17

- In priesthood meeting, Ed Herrmann, was giving the lesson on new beginnings from Elder Kearon from the October 2025 general conference. Jesus went about doing good - At the end of the lesson - Ed was talking about an action strategy that they use in the military - It was...

1. Intel (info or gather info)
2. Plan
3. Rehearse
4. Execute
5. AAR - Pause (after action report)

- Small note... I was typing these notes and got to the note above this about the military action plan or action strategy. I was able to use that little piece in a meeting that I had with Shannon on 1/13/26. That is awesome. The timing was perfect. I just finished typing it before the meeting and then I had to use it. Small mini miracle and blessing. My notes were able to tie into another piece that I was looking at on Monday night (1/12/26). We were helping our daughter do some goal planning for the new year. In the pamphlet, it kept prompting for putting your goals into this format: Discover, Plan, Act, Review - As I was working with Shannon, I was drawing a parallel between the child goal setting strategy vs the military based strategy. They are very similar. They use different words and the military one has a whole section for rehearsing or practicing before doing the actual event or action. I thought that it was very interesting. I was telling Shannon that she was technically helping me do some planning and rehearsing for where we are heading. Good stuff.

Back to my notes from Sunday, 1/11/26 that I wrote on Monday, 1/12/26... I got side tracked

- After church (on 1/11/26), I spoke with Bryan Dayton and told him that I was planning to talk to Steve tomorrow (Monday) about pushing forward - gave him a few small insights into my plan from my shaving session on Sunday morning - see other notes.

- Came home, played a game with Brooklyn

- Super yummy meal after breaking my fast - potato soup and corn bread

- Made chocolate mousse

- Played a game with Heather and Brooklyn - Heather won

- I got a blessing from my dad - we talked and chatted for a bit and then I got a blessing (father's blessing) - I have had many of these - Lots of great love, advice, inspiration, and remembering my worth - I doubt myself sometimes - Here is some advice that he gave me: Take care of yourself, your family, your church calling, and then your profession. Even though profession is forth on the list, that doesn't mean that you give it a forth rate job. He also felt that I should go and meet with Steve - face to face - really try to help - even help repair the relationship. It has been super stressful. He also recommended that I read a few poems (motivational poems) - I have those in a different notebook.

- On the going out to Salida to meet with Steve, I was thinking, maybe we have a team meeting - in person - to go over plans and such - going back to what Ed said (military strategy - intel, plan, rehearse, execute, AAR (pause - after action report) - focus on the plan and rehears sections.

- I have been in so many meetings... tons of training - that is an asset (meaning church and business meetings)

- Quick 1-pagers - Bishop Shawn Smith loves the quick - at a glance - what is going on

- I saw Reese Hulbert use a few quick - at a glance - one pagers for a training meeting. They really seemed to help.

- Contact Gene to see about getting some funding for a big push. Sent him a text on 1/12/26.

- Graphical homepages

- Finish up the MVP list - Estimating somewhere between $500-$750K to finish up that push and those pieces.

- Work as if for years

Steve canceled the meeting for tonight. He wants me to finish up a couple of projects that have been hanging out. They did send a small update via email. This is what I got from Thomas:

We have updated Adi global context training with all the arsenals, including but not limited to increase context limit, RAG implementation that minimize up to 75% less token consumption, GPT5.2 update and more.  Looking forward to Brandon getting back in adi training mode.

Meeting with Alan and Steve. We were talking about some new accounts and also helping with the accounting for these accounts (offering other services). The goal is to help fill in the gaps on the accounting side of things. Let them do what they can and then we fill in the gaps. Steve was reporting that a client was saying that they were happy to find us. They didn't know that we existed. Small talks about QuickBooks and how many people use them.

The main meeting was between Alan and Steve. I was there, recording notes, chiming in, and doing a little bit of driving (clicking on pages and reports). Here are some of my notes... Instead of being sequential, they are broken down into things that Alan said and things that Steve said. Good meeting.

Notes from Alan:

- Shifting our mindset a little bit

- What is working and what is not working

- Skating to where the puck is going to be vs where the puck is at right now

- Being proactive in our approach

- Running to the fire vs doing what is needed in the long term

- Say a budget of 30 hours - 15 hours working on big projects or using that time to do some prospecting, 5 hours communication stuff (emails, texts, recording time), 5 hours bug fixes, other 5-10 hours maybe using AI to help clean-up the system or refactoring older code

- Maybe some new dashboards

- AI is amazing when it works

- Using AI to help us modernize our interface

- Talking about time - not too rigid on timelines - we want to finish things... - everything takes time - we never tend to get to things

- Taking about proactive maintenance

- He (Alan) sometimes struggles with communication

- It is easier to just knock out projects at times, then talk to people and/or get distracted by different things

- Code fits into multiple areas - paid, fun, wow factors, etc.

- Taking time to work on their own projects (one of his wishes and/or dreams) - basically either continuing education and/or fun projects (what can we do to make it better) - fixing things that bug us (as devs) - making things easier for others

- Alan's been working on some refunds (card pointe and clover - merchant processing stuff)

- Talking about dreams and what would that look like

- Stuck in between what we want and what we have

- Fearing the slowly sinking into nothingness (an analogy about adilas - like a ship)

- Running in circles

- Chasing a ghost (phantom look and feel)

- Alan asking about the goal with the investors

- Talking about the size of the client that we are chasing... how big of a fish are we looking for? - we may be trying to get too big - who are we? can we handle that size of a fish? - what is our goal and how will we get there?

- Alan had some questions on pricing and what does our ideal client look like? how do we find that person/company?

- other sales related questions - how do you judge a company, size, needs, etc.? - what about customizing things? good or bad? - we don't have a big huge team - we have been burned with merchant processing and other 3rd party solutions

- Talking about adilas and where we are at financially

Notes from Steve - once again, not sequential, but just things that I wrote down that he was talking about.

- Learning to adapt - using AI - it is going so fast - we need to be in that race

- Talking about databases - yes, they are still really needed (good multi-relational databases)

- Steve was showing some of the AI stuff in his demos with some potential clients - that has been going well

- We are really bad at estimates (we have had our lunch eaten time and time again)

- Talking about client churn and companies falling off of the system - pretty normal - we are actually doing pretty good.

- Looking around in the system a bit

- Maybe going with $100/hour for development work and $65/hour for setup and oversight

- AI has sped up Steve's work - he is learning along the way - guiding it along - taking in small sections at a time

- Steve was talking about time budgets and not getting too tight on certain time blocks

- Some of Steve's projects are tiny and fulfilling - inch by inch and little dabs

- We need some firewood (sales and revenue coming in) - we are low on revenue

- Steve thinks that Alan needs a break - maybe getting out there and talking to people about what we have

- Sean has been helping with deployment - Cory is doing more client work

- Steve loves to figure out the angles (problem solving for clients and what they need)

- We have an MVP (minimal viable product)

- Finding people who are happy with what we have

- Investors tend to look at the reoccurring revenue - we are looking for an angel type investor who sees the vision and value and says, yes, let's push this thing forward

- We have gotten it this point without a sales team and without marketing... imagine what we could do if we get that going

- Big fish are expecting to be courted (wine and dined)

- They, our clients, have to be big enough to afford us

- Shooting for $400/month

- No big fish and no little fish (super little) - being able to offer our services and they pay for it

- Learning to say no

- Most companies pay around 3% for merchant processing... say we go less than that - say 2% of monthly revenue - start higher and then go down if you need to - if you are dealing with a big chain, we may have to negotiate with them

- Steve talking about numbers... say we have made $10Million from paying clients. If you take number and divide it by our total client count over the years, for us, it is around $12K per client

- We should be selling stuff - that is a super high number at around $12K per client

- Steve would like to get 5-10 new accounts a month

- Offer our other services - activation, deployment, and servicing the account

- We have done a lot of stuff for free... we need to change that

- Sales - can be broken down into three main things... they are like, trust, and respect

- Just tell everyone what you do (from Kiva)

- Do they have inventory? Do they need to track stuff? Great! - Nobody does inventory management like we do - QuickBooks is sending people to FishBowl and Shopify

- Being outside and out and about

- Helping people with their over needs - these are things that they can't get to - their over needs

- We could offer lots of other outside or inside services - we are $65/hour for those services

- We either do it or we don't do it, go to the next

- Stay on the good side of town

- On custom code, they, our clients tend to really like to dream and can't really afford it - we have been burned on doing too much custom - we are $100/hour, paid weekly, if yes, ok, let's go

- The bigger the lift, the bigger the pain (time and money)

- If needed, we could move forward with bigger teams - like a lawyer, we could work off of a retainer

- We can get lost in "custom world" or "custom land" - we need to steer clear of major custom

- Looking for happy clients - we have a bunch of clients who are not calling us, they are happy

- Trying to stay away from black box stuff - building settings or small bridges

- Being able to remove columns on reports (fracture or adilas lite stuff)

- Simple website stuff (easy hosting) - simple pages and some settings (landing page, contact us, and about us, plus adilas ecommerce)

- Trying to be around $1,000 and then a monthly (have to have an adilas account)

- Taking things off of their shoulders - they are already spending tons for all of these other services (mashups)

- Maybe look at some sport teams - other team sports

- Not trying to sell things, just doing some exploring

- Talking about sales and/or trimming things down a bit (financially)

- We may to stop or curve the development and really focus on sales

- Talking about the AI quick search - going beyond normal API endpoints (URL crafting, AI quick search, mini API, etc.) - Steve jumped into the test site and was showing Alan some of the AI agent stuff that we are working on.

Overall, a great meeting. Some good takeaways as well. Good stuff!

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

Bryan ran this page through AI and got the following summary back

AI Summary:

Sales & Strategy Meeting Summary

Attendees: Alan, Steve, Brandon, & Bryan

Meeting Overview

The discussion focused on expanding Adilas’ service offerings, improving operational efficiency, refining sales strategy, and leveraging AI to modernize both processes and the user interface. The team emphasized the need to balance custom work with scalable solutions and to strengthen recurring revenue and client engagement.

Key Discussion Points

Alan’s Focus

• Encouraged a proactive and forward-thinking mindset (“skate to where the puck is going”).

• Suggested a structured time allocation for projects, maintenance, communication, and AI-driven improvements.

• Emphasized AI modernization for the Adilas interface.

• Advocated for proactive maintenance and allowing time for innovation and internal improvement projects.

• Discussed defining the ideal client profile, pricing models, and balance between customization and scalability.

• Highlighted challenges in communication and prioritization but emphasized long-term goals and clarity of direction.

Steve’s Focus

• Stressed the importance of adapting quickly to AI and new technologies.

• Acknowledged issues with time estimates and scope management.

• Proposed pricing structure:

  • $100/hour for development

  • $65/hour for setup/support

• Highlighted need to increase recurring revenue and attract an angel investor aligned with Adilas’ vision.

• Advocated for focusing on sales growth (targeting 5–10 new accounts/month).

• Emphasized charging for all services—move away from unpaid work.

• Encouraged avoiding excessive custom development to protect scalability.

• Recommended prioritizing sales and marketing efforts to drive short-term revenue.

Action Items

• Define the ideal client profile and align pricing accordingly.

• Increase focus on sales, marketing, and client outreach.

• Use AI strategically to streamline operations and modernize the platform.

• Improve internal communication and proactive planning.

• Explore investor options and sustainable growth strategies.

Brandon and Bryan went to the Adobe ColdFusion Summit Conference in Las Vegas. Multiple days at the conference. See attached for my notes. Good sessions and good learning.

While down there, some phone calls with Steve and Alan going over plans, projects, and funding stuff.

Working with Shannon. I was showing her the expanded AI quick search options. That was kinda fun. So much potential there. Talking about what we can harness..., quickly and efficiently. We then read over the overview of the adilas lite - Fracture project - this was what Steve got back from Grok. Shannon took some notes.

These are notes from Shannon: Brandon reading the AI summary of Adilas Lite:

- Project overview hub - Adilas ecosystem

- Ambitious roadmap for next generation SaaS map

- Clean, modular, teaser, further explanation

- Solid, forward thinking, scaling Adilas from ERP to community

- Flexible, customizable, modularity, user centric - following SaaS trends

- Technical depth and community

- A vibrant hub for

- Teaser heavy - would like to see more visuals, demos, things to make it more engaging

- Grow into a dynamic dashboard overtime

- Jellyfish model and jellyfish analogy - adaptable and fluid, recurring revenue with add-ons - monetize ecosystems, rapid scaling if the core offering hooks users

- Value Add-On Core model - technical meat, starting at transactional data to unlimited, scalable at a level people can understand

- Adilas University - essential for adoption, helping growing community, build loyalty, include gamification/certification it could be even better

- Adilas Marketplace - huge potential for revenue drive and ecosystem builder, success depend on curation to avoid quality issues

- Adilas Cafe & Communities - slack-like portal, one-stop shop, broaden the appeal beyond users, social features - a community first brand

- Adilas Lite - Fracture - the crown jewel, rebuilding with new code, toggle on/off - this screams user empowerment... a lot of other great things!!!! - could separate Adilas from other more rigid Sap and Oracle

- Other Business Plans - lots of other great things that I didn’t get recorded - got caught up in listening to these last two - lite and other plans

- Adilas Videos & Research - transparency, keep community invested, ties things together, road maps could be invaluable for developers eyeing integration

- Vision - building a sustainable interconnected world around it

- Improve - more interactive elements, make it live and searchable,

After doing this, we then switched over to building new content for the adilas cafe page. Working on sub content. Good session.

Working with Russell. Talking about life and best to navigate things. We talked for quite a while about these topics. We then jumped into changing code and looking at our chart and graph project. Here are some of my notes - somewhat all over the place.

- We were looking at code and samples on the chart JS site.

- Building in training time. That really helps and keeps things sharp.

- Small changes moving forward. Those small changes can really add up over time. Like small drips in a bucket.

- You have to sacrifice something to make changes (talking about time and priorities).

- I enjoy enabling and helping others. We talked about boundaries and how to manage those. Sometimes, by not managing those things, I feel like I get taken advantage of. I'm not very good at setting some of those boundaries for myself.

- Questions - How do I run, what motivates me, how does that affect me?

- For me, I get worried about not doing certain things. Instead of fully removing things that I enjoy, maybe just opening it up a certain amount. Being able to adjust within certain parameters.

- You have to have sanity checks and find that maintainable pace. Otherwise, a pile of "goo" doesn't do very much (if you over do it, you can feel like goo or a puddle of something).

- Bloom and prosper where you are planted.

- You have to adjust within the bounds that are set to what you can. Fighting for that high ground and safety spot.

- Keep gathering up the drips and drops (From Russell - that's my life). It takes many strokes to make a masterpiece.

- We were talking about feeling like we are in prison, based on circumstances and such. Russell said - It is only your prison if you make it so. You have options and choices. I needed to hear that.

- Some other one-liner topics that we were talking about. Journey before destination (From the book "Way of Kings" - Brandon Sanderson), moment by moment (getting help from God - He is with us - both with me and by me), Doing unto others and helping along the way.

Emails and some follow-up.

Went to the Adobe website and signed up to be a presenter in an upcoming conference.

Session Title: Using CF to mix and sell essential business solutions - client success story

Session Description: CF developers know that ColdFusion can do amazing things... would you like to see how CF made our reoccurring revenue SaaS solution possible? In this session, we will show you how we used CF to combine inventory tracking, a full POS (point of sale), CRM (customer relationship management), eCommerce, scheduling, backend accounting, into a full-on ERP solution (enterprise resource planning)? The entire backend is built on Adobe ColdFusion with a MySQL database. Small demo of the product and what it does, open discussion, and plenty of time to ask questions. If you want to see a process, from start to finish, no problem. If you want to dive into code and look under the hood, no problem. Developer and project manager, Brandon Moore, will help you see the power of CF in a real-life client success story.

https://news.adilas.biz/sales-gallery/adilas-advert-index.html - Some slides on what we do at adilas.biz

Went into town to meet with Andrew from Host Huski (web hosting and website builders and web consultants). We met and talked about websites, common ground buildouts between both of our parties, and options going forward. Here are some of my notes:

- He would like to make a Huski Point of Sale or HuskiPOS white label, using the adilas engine. That would be really fun.

- He made a huge spreadsheet of the different features that adilas has. They came from the presentation gallery pages. He gave me the homework assignment of pairing things down and getting rid of things. There are almost 800 lines (features and points). Along those same lines, he would like me to really spend the time and make it easy for a client or user to both understand and basically see what they get at a glance.

- Along with pairing down the list of features. We want to categorize things into plans and packages. Ranging from free to full enterprise or custom.

- We talked about doing a full website redesign for the main adilas.biz website. We would base this off of the features list that we are going to be creating.

- For me, I like to say we have 12 main functions and 12 main player groups. Maybe get rid of the numbers and say something like: Our essential business functions and key components (parts and pieces... aka the 12 main player groups).

- Andrew asked me about "roll call" and what that meant. As we talked about it, we thought that "lifecycle tracking" may be a better fit.

- ACL (access control list) - and having permissions better organized and even sub divided into better or real groupings. Light conversations about where we could go with that. We already have that, but it could use a little bit of loving.

- Letting clients do their own data imports and importing data. Maybe even doing some automated combing and virtual pre-flight checks on the data (does it pass, without trying to do it).

- Good discussion on moving things around. What is the most important to our clients and potential clients? Put that first, other stuff, either get rid of it, move it to another area, or keep it as is. Helping with organization and flow. The easier things are to do and follow, the less need for tech support, training, and handholding. They can then do it themselves to a certain level.

- Good faith - work on both parts (Andrew and Host Huski and Brandon and adilas).

- Lots of focus on getting organized.

- Easy onboarding

- Going over design principles and the power of 3 (design stuff).

- Andrew is trying to work with SEO guys, marketing, CRM, hosting, payment solutions, and POS guys. He wants to create a super team to help do all of the pieces.

Working with Bryan on swapping out the vendors and part numbers for a client. It got deep into a bulk find and replace tool with looping logic. The tool is just on Brandon's machine, not part of the master branch. It was built to help this client. If it is needed again, we may have to lightly tweak it.

Working with Steve and Chuck. Going over reports. Working on and building the dream - that's what we are pitching and selling. Talking about showing them the mock-ups. Helping to put a visual with the pitch. Steve has been kissing a lot of frogs (potential investors and venture capital stuff). He's hoping to find the one (just being silly... like a fairytale). Sell the sizzle...

Switched over to the website proposal and series of questions. I took a bunch of notes here:

- Need for website to be tied into the inventory management system.

- They want a CMS (content management system). They want to control all of the pieces and be able to make the changes. Steve was pitching our own mini CMS type system. Chuck was pitching WordPress with some plugins.

- Talking about running all of the services (one-place shop) for the client. We are your dev team.

- We have so many pieces that are close... they just aren't fully done.

- We may have to help them with a mashup right now. Then, later on, we may be able to build out all of the pieces for them (internally). Chuck is worried about the time to really build it out (right now).

- The power of mock-ups. If you have 14 different plugins... to install, configure, and manage, it can get messy. If WordPress goes down, it makes us look bad.

- Maybe pitch two options... one for WordPress and plugins route - the other, just adilas, we build it all and keep it all up for you.

- If we build it, things take time. real time is needed for planning, building, and we need real budgets, etc.

- We really need to control all of the pieces. They want full control and speed to market. If we build it internally, we have assets that we can throw at it. Basically, fully outsource it to us and we will run with it. We are your one stop dev shop.

- Maintenance fees to keep things going.

- Back to selling them the dream.

- We will save you so much time and effort by systemizing things.

- Talking about social media... that (social media posts and such) becomes the changeable web content, the main website is more of the backend stable piece, that's where you order and interact with the actual products and inventory.

- Talking about real native "mini" apps that tie into the adilas system backend. Keep them small, open or create the doorways, we will go from there. Basically, just a mini portal into their world. Mobile first approach.

Chuck had to take off. Steve and I were talking about inventory thresholds. We were also talking about the future of where things are heading. Lots of mobile stuff. Everybody wants efficiency. Josh is really helping to push on things. That is huge.

Small side note - Brandon was riding snowboards with Aaron Hill, on Friday 1/10/25, up at Beaver Mountain. They were talking about ways to make their clients sticky. When they had to go their different directions, for the day. Here is what Aaron said to Brandon - "Really make those clients sticky! Win that battle! Make it good!". Great advice!

Setting up a new corp for one of Brandon's friends. He loves to play with CRM's (customer relationship management programs) and wanted to check out adilas. Prepped some things for him and got a new corp and new user setup. Went over to his house for some training. Spent a couple of hours showing him around on settings, customers, elements of time, and flex attributes. Fun little session.

Multi hour Zoom meeting between Sean, Cory, and Brandon. We went over an email sent to us by the Canada company and went line by line over the email and made a bunch of notes. Brandon has a copy of those notes and they were also sent to some key adilas players.

Meeting with Josh and Tobias. Small intro between all of us. We chatted for just over an hour. The goal was to see what it would take to revamp adilas. We eventually turned to what it would take to use the API to put an app layer or custom skin over the top of the whole platform. We talked about what FlyHi did with their API socket work and the app that they made. Here are some of my other note:

- Too much - not sleek - needs a reskin - needs to be an app

- The data entry person - who needs what? Keep it super simple. Go talk to them and figure it out.

- What does it look like - pair it down

- API sockets

- Assumptions and being willing to add layers over time

- Being a real business

- Tobias had a great approach based on the use cases not the software itself - don't think... what can it do or how does it work, think... what do I want it to do, don't worry about the current pages and/or limitations. How could this be used? Wouldn't it be cool if..., etc.

- Build on top, abstract, add layers - strip it down and make it specific for each industry - you could do this for any industry (app on top of a backend system)

- Find the low hanging fruit and start there

- Step function (layering it)

- building out a base and then using that as the starting point for other apps

- After they left, I spent some time watching the FlyHi video demo. This was a company that uses adilas but also built an overarching app to manage a whole other side of the picture (app side). They did a great job!

This didn't happen. I was sick and had to cancel the call.

Meeting prep. As the meeting got started, we had Sean, Cory, Alan, Steve, and I on the meeting. Here are some of my notes: Kinda all over the place.

- Sean has set up the logins for the new users up in Canada.

- Looking at what it will take to come up with an MVP (minimal viable product).

- Steve bought some new hardware. He will be playing with it and getting it all wired up and configured.

- How do we keep pushing the ball down the road?

- Setting up limits. We want to play but don't want to get ran over.

- Going over a list of to do items.

- Steve really chimed in on where he thinks that we are at. He really took the ball and ran with it today.

- Risk vs Reward - We spent quite a bit of time going over options.

- Steve is excited about the number of items that the Canada company has. It's really pretty small.

- Number of locations - lots of potential there

- Steve was talking about a book - "The Art of War." - Making deals and business stuff.

- Show what we have done - clover integration - $23K, features, advantages, and benefits, list out an MVP, show a percentage of what we have to still do, things that are not on the list... wishes, future desires, tablets - online orders and delivery, website, ecommerce, we do the POS software. We can help with hardware but that's not our specialty.

- We have some depth - adilas - operations and accounting

- Look at what we can help them with...

- Mission statement - help your business succeed

- Could be some scale problems as we go along

- Promises made and expectations

- Deployments - it can get dicey (interesting)

- We have... list it out - we have a solution

- Get them talking and thinking about something else - distract them what they are worried about - sometimes, what someone is worried about, they are not as big of thing as you think. However, if all you ever do is just think about that one thing, it can change your focus. You aren't taking in the whole picture. Get them seeing the whole or bigger picture.

- Hardware - pros and cons - come up with a valid solution and then allow them to choose, buy, or configure their own system

- We can see our way through a bunch of things - looking down the road

- We can setup corps... we haven't really done much mirroring of corps and settings

- Alan - Sunk costs, new costs, and building going forward

- Alan - Getting direction (where are we going as a company?) - He likes where we are going

- Cory - He (Aaron - owner) needs to invest in us. Money and time - how long will it take and what do we need to still build out?

- Steve and Cory going back and forth - nice little volley back and forth - risk and reward stuff.

- We want Eric to ask for his other stores to be on adilas. Eric is a store owner.

- Alan - Once they are up and running, they may not need more right away

- Steve - We can build anything... there is a line or an end zone - a goal is in sight

- Goal - What will it take to get this thing to launch?

- Alan - Questions about customer support and server up time

- Alan - Other possible services - customer support, training, etc.

- Alan - They are trying to see how serious we are? Almost a test on us

- Alan - We get our hardware stuff up and running and we show that we have a solution

- Steve - Give us a list and we'll cross it off

- Steve - Like a game of football - How much time is left in the game and what are our plans?

- Steve - Pushing this company further down the road

- Steve - This could be our golden ticket - Let's punch it!

- Alan - If we don't do this, then what? Let's use our current team and get it done.

- Alan - this is not vaporware... this is right here in front of us

- Steve - They could be the last client that we ever need

- Helping them see the future and wanting to stay with us

- Steve - What about global ecommerce stuff and then locations where people could pick things up

- Steve - They, are looking for us... they hate some of the competition

- Cory - We may need to fake it (customers, gift cards, and loyalty points) - We have all of those pieces, they are just at the corp and cross-corp levels. Not at the enterprise level yet. If needed, we could just have them run per corp until we get the other pieces. That's our fall back.

- Alan - Just noting that we only have some data (not all of the locations). If needed, we could do it per location

- Cory - Wanting to setup some action items

- Steve - Wants to start a list, send it around, tout our horn, and show who is doing what

- Steve - Assume the sale

- This is a test

- If you are going to fake it until you make it, you need to pretend that it really works and it already exists - smoke and mirrors. We've been at this for over 20 years. There really is a lot there.

- Alan - We can't over promise - stick to the basics

- Steve - We are working on... Steve-hardware, Alan-enterprise, and Brandon-reporting

- Communication - short and sweet but keep it moving

- Steve - Asking about customers... direct vs enterprise

- Sean - On new customers, they just need a few fields... such as: first name, last name, email, cell phone

- Alan - Let's do the customers and gift cards at the corp level - We'll clean-up later

- Steve - He is planning on using one printer to handle both receipts and cup labels - sticky receipt paper

- Steve will work with josh a bit to help with direction

- Alan - Enterprise is a value add-on piece. We need to figure out the pricing structure there.

- Alan - We will gain some momentum as we keep doing the enterprise stuff - this is where we are heading.

- Alan - We add a lot to adilas but we never up our prices - We need to manage that better to recoup or get ROI - Dynamic billing

- Steve - no Metrc (statewide compliance system), under 100 items, not even tracking inventory yet - Let's do this thing!

- Sean - On ecommerce, they aren't really tracking inventory, they just need to use their menu and go for it.

- Steve - simple on what they need, scale on the reporting and needs - here we go

- We are figuring out where we are going... Okay, let's go!

I was driving home from the Colorado and Canda trip. I pulled over at a gas station and jumped on the call. Everyone else was on the GoToMeeting session. Here are the notes that Cory took. Thanks Cory!

Hi Brandon-

Here are my notes- messy!

- They could use some more training

- They were asking for Customers and Loyalty points (Data had issues)

- They want enterprise reports (they don’t even have two corps to see)

- They brainstormed a list of what is needed

- 3 month trial

- Also interested in another software- Snappy PC

- Fight against loyalty points and gift cards

Question:

Are they using adilas since you left?

What are their expectations?

- Very strict culture

- They think enterprise is bigger than it is

- Dashboard with FranPOS- they don’t like it

- **Steve wants to know what the MVP is for them

- Brandon said it will take a few hours to come up with that

- Brandon said he will send them an email letting them know Sean is their point of contact and that we met and are coming up with an MVP.

- We need to let them know we have already invested 150K and we need to get a commitment from them.

- Phillip likes the customization but is leery about some of the processes.

- Example- When you add a new item and how to add a new button- this is so much work! All of this can be sped up. Buttons are not required, but they like them.

- They add new items quarterly so that will be some work for them.

- Takeaway: Need to have buttons on the enterprise level in order to roll these systems out

- We need to decide where we draw the line: the code is done, the rest is custom.

- We may need to have Josh tell him this

Yogen Fruz Projects:

Completed:

1. Ability for the Browser on the FranPOS to access the adilas SAAS. (Suzi)
2. Setup test system with all items and buttons. (Suzi)
3. Reconfigure and add settings to POS environment. (Brandon)
4. Beverage and inventory labels (Stephen)
5. Research on Menu Boards (Stephen)
6. Setup e-commerce (Suzi)
7. Live test transactions in Canada for 2 days (Suzi)
8. Clover processing integration (Alan)
9. Live pilot in Canada (Sean and Brandon)
10. Icon Report for Eric's store(s) (Stephen)
11. Gift and Loyalty (Brandon)

In Progress

1. Gift and Loyalty (Brandon) - done
2. New hardware testing (Stephen)
3. Website discussion (Dustin)
4. Enterprise scaling (Alan)
5. Small update to the Icon App Report (Charles)

Future Projects (Included or Co-Funded)

1. Menu Board (Stephen)
2. Website (Charles / Dustin)
3. Delivery API (Alan)
4. Additional Reporting (Brandon)
5. Canadian nomenclature, such as State being called Providence, and Zip Code being changed to Postal Code (Settings)

Meeting with Steve and Alan. Going over budgets, pay offs, timing, talking about the approach, don't talk about positions, pitch the sale ($150 internal vs $75/hour - using some of our guys directly). Steve was and has been selling pieces of custom code to our clients. He would like help there and have the guys pitch their own services.

We spent some time talking about our identity and who and what we want to be. Taht is coming along. Here are some other general notes from our conversations (multiple topics):

- Help protect our clients...

- Set some caps on how much our developers can charge

- Communication back to the clients - weekly reports and billing

- Billing - weekly

- We can't let our developers rough up our clients

- Helping our guys succeed - plans, billing, communication, oversite, etc.

- Possible kickback - commission to adilas

- It takes so much time to crunch things up - sales or custom code - the reality of what it takes

- Can't keep pushing things over to the balance sheet (code or projects for Kelly) - it costs of too much. We pay the developers and we owe money back to Kelly.

- Consultation document or a checklist type doc

- We are generic on purpose - if you want it custom... you've got to pay to optimize it

- Setting up boundaries and being firm on that

- An add-on cost for custom work - they need to pay for it - they may need to keep paying for it (reoccurring) - maintenance

- Selling what we have

- Our development and sales focus is as a general business tool

- Elevator pitch - web based, SaaS (software as a service), we focus on operations and accounting, we have a base model, and we allow custom

- We want to be generic. We want to cover a number of industries. We want to be a great companion software for any business.

- This is who we are - defining ourselves and what we do

- Plans for our upcoming meeting with the developers - take care of business and setup another meeting where we have some plans all made up.

- The developers may have some ideas on how to make things work

- How can we get some of the cool stuff exposed to the public? Selling what we have. - sales - nobody is pushing it, our tools and features, as a product.

- Alan had the idea of using an outside marketing firm - when ready

- There is a need for marketing, education, etc.

- YouTube influencers - quick, short, and powerful mini messages - short and to the point

- Podcasts - how to run your business, tips, tricks, and best practices

- Piece work - we have tons of stuff - what if someone could harvest that kind of stuff? - YouTube, Facebook blogs, podcasts, etc.

- Alan would like to talk about the future - looking short term, medium term, long term, etc. - talking to Steve, Brandon, Shari o., Wayne, Cory, etc.

Meeting with the Lucky Puppy or Puppy Palace folks (dog nails and grooming service). They are looking for a multi-relational pets to owners, pets to techs, color based key, and tons of other things. I showed a small demo of the backend code and where we are at with things. They wanted to know where we are heading moving forward. They are a potential client and we are looking for ways to help them out and solve some of their problems. Suzi recorded the last half of the meeting when they were showing us some of their needs. These are some of my notes:

- As a disclaimer... I went back through the video and refined my notes. Original meeting was on 8/22. I rewatched the video on 8/26 and added a few more notes on 8/27/24. We already have a ton of these pieces. This meeting was to show us what they are wanting and needing and how we will need to put it all together. Just guessing, but I'd say we have 85% of all of these things right now. We just need to tweak a few things out, make some plans, add some new settings, and alter the flow a little bit here and there. That's awesome!

- Choose a customer, choose a pet, choose a service(s), choose a color, choose other assistants, check in/out, create a cart, manage the tips (split tips - they really want this... this was huge). Be able to copy the booking and rebook it (docking and rebooking). Email and text message back to the client. That's kind of a summary of sorts.

- Be able to edit the cart and add discounts during checkout

- 100 appointments a day - phone calls, changes, super-fast paced

- Show cancelations - what was there - They like to see what has changed, moved, or been canceled

- Adding a new client and making it quick - currently, they are using first name, last name, cell phone, email, and zip code. Be able to add more if needed. We have tons of settings there already.

- Notes on pets ... name, type (breed), age, size, up to date on vaccine, does it bite? etc. - thinking about flex grid tie-ins or a custom table there. On the notes and records for the dogs, maybe group things and then allow a subset to be shown. Go from simple groups (say per pet name) to more complex, everything tied to that pet.

- Each service has a time (block of time) associated with the service - there are some pros and cons to that approach. Anyways, just making a list of things that they were showing us and asking for.

*** Fast... they love drag and drop - They would love to be able to easily drag and drop and edit a time slot (length of the appointment - longer or shorter) all done through drag and drop.

- Making the appointments, changing the appointments, etc. - planning for the next step

- Major color code key - they are using multiple colors - each one means something - allow them to set up their own keys and values and colors.

- Tie-in the monies a little bit tighter - they would love to see it more or better - currently they are using multiple systems and then running the cards on the side. They would love to see it all tied in together better. Ideally, they are wanting a mix of an integrated scheduling software package, CRM (customer and pet relationship management), full POS (point of sale), ability to mix both products and services, and manage the money part of the puzzle. Sounds like our kind of game.

*** Tip splitting is huge... keep track of things... tight - reporting the tips split by person (by tech). Help automate this for them. Currently, they have to do it manually. This feature is big enough that it is a make-or-break level feature.

- They are having a problem with tracking their dogs... and having to read the notes for each one, over and over. They need the multi-relational database between owners and pets. We want to really help make this nice. I was originally thinking flex grid tie-ins... We may want to look into a way of doing sub queries or special grouping to make it smoother. We could also do some sort of custom table or custom joiner table.

- Being able to see the whole picture... they need techs, time slots, rooms, services, and needs (client and pet needs). All tracked in one place. Fully customizable - show simple to more complex.

- Alerts on the appointments - little flags - possibly even color-coded tags and flags

- A 3D view of the techs, the rooms, the appointments, the needs, the conflicts, the crossovers, etc. - that would be super cool - just an idea

*** Email and text messaging - app messaging - they really want normal text messaging including conversations back and forth. Here are a few other things related to text messaging needs: - Send message when booking the appointment, send reminders - multiple, send appointment confirmations - auto and manual, send booking reminders - some of their appointments are booked out 4-6 weeks in advance. There was also some talks about sending out auto emails for different actions or steps. Those would need to be defined.

- Switched to a different software package - They started showing us "Rosy" (used for 8 years - lots of data and history) - this is a human salon based software package. Part way through, the switched and showed us a dog or pet care solution called "GrooMore". They, the client, currently used Rosy in one location and the GrooMore software in another location. They are looking to get the best of both worlds. Ideally, we, adilas can come up with a mix and blend of both and become/be used as a newer or custom software option.

- They would like customizable enterprise - multi-location controls and flow of data, pricing, processes, reporting, etc.

- There are going to be transition strategies that need to be involved as our relationship develops. They want to keep going, with minimal issues, get back data, and make it all smooth. At some point, depending on what we can show them, we may need some transition strategies.

- There are too many appointments - a glitch could really be a problem - high volume

- They would like the option of seeing the last service, if known, per client/pet

- They want the appointment to hold all services and all assistants vs each service being its own appointment and each helper being its own mini appointment. More relational database connections.

- Their customer and service look-ups were really fast - asynchronous calls - like ajax or dynamic select or predictive text searches

- Be able to set settings for future interactions - what they normally get - be able to save that (speed things up by saving choices per customer and per pet)

- They need both owner names and pet names to show up on the view - They also want to see both names, client and pet(s), along with all services (cart line items), as well as other assigned flags per appointment. These would show up on the rollover or mouse hover action (aka the popup or rollover popup).

- They are constantly checking the schedule (visual display) to make sure all is well - help them out - simple look and feel with all of the details under the covers.

- Simple to add the other assistants - some appointments require 2-4 extra techs - make that quick. As a side note, the main appointment may be for a certain time and the assistant may be for a subset of that time. All tied to the correct pet.

- Showing conflicts - on the fly - both from calendar view and through a setup flow

- Showing the scheduling for any other assistants. Along with that, booking multi-staff appointments and then making sure that things stay tied together.

- Simple process (how long - in minutes) - add the drag and drop (super cool). Allow for both manual changes or drag and drop changes.

- Docking - saving or moving things - everything that is attached (all attached) - be able to move or put in the holding queue (session or memory) and then pull that back out when ready. Even having multiple things in the memory queue if needed. That would be cool. If needed, we could reuse quotes as a template of sorts. We could also allow for multiple things to be put in the queue. Kinda like a multi copy and paste board of sorts. You just get to manage it (really simply).

- Confirmed or unconfirmed appointments - checked in/out, paid, etc. - different flags and colors per appointment

- Colors - new dogs, bite risk, etc.

- Be able to book multiple staff members at the same time

- Multi-level sliding modals to add things - pretty slick

- Birthdays - it is nice to be able to just put in years and months and back figure the birthdate (help them out). Allow for either a real birthday or back figure based on the approximant (years and months combo).

- Being able to add tags for clients and tags for dogs - each their own tags and flags. Each tag gets a name/title and a color.

- Medical issues and comments - be able to add/edit

- Vaccination records - tracking that info

- Vet info - doctor info and such

- Dashboards

- Conversational text messages and using a huge texting tool

- Intake forms - QR codes or links - they add their own documents or forms (confirm and accept forms) - let the clients put in their own details. These client intake forms would be handled through the ecommerce or client portal section of the application.

- Quick jump from day to day, week to week, and month to month

- Notes - intake notes, appointment notes, ongoing list of notes. Being able to search and filter notes as needed.

- Be able to add/edit the tags per person or per pet

- Being able to search clients or pets by the tags. Thinking flex attributes for this.

- They are doing some mobile on-site appointments. They want to pull up clients in that area to say we are in the area. They like to tag their client's general location (area) to help with targeted marketing efforts.

- Bulk text messaging based on filters or tags - batch send out things based on applied filters of the larger record set.

- Searching by pet name and then finding the client based on the dog or pet name

- Deceased dogs - dogs that have passed away - they still want to see it - maybe just flagged vs not fully deleting the pet profile.

- They would love integrated financials - in the end

- Reach out to Jen if I have other questions. Debi and her crew seemed to be pretty busy (booked).

- Just an idea, currently we allow for photos and media/content to be added to the main customer or client records. Up to 100 photos per client. Do we want to open that up and allow for sub groupings withing the photos for the specific dogs? We do allow things like this to take place for parts and general inventory items (photos and media/content for subs). Anyways, this could come later as well, if needed. Just an idea.

- Empower them on the setup and layout... Let them drive it - block sizes, what to show on the title per appointment, what to show on the hover (rollover popup), color keys, flags, etc.

*** vertical time view (a design has been built by Chuck - branch CAS-93)

- For me - claim some time - make time for it - review the video and make a plan... make sure that we have access to the correct demo site and make things flow there. Thinking about settings and putting the power in their hands - put them in the driver's seat. Wow - great meeting!

1/13/25 Bryan and Brandon meeting 

To outline what it would take in time/money to complete this project.  Then take the information to Steve and Suzi to decide if we are moving forward or putting it on hold. 

A ball park estimate without outlining each project would be at least 200-250 hours ($20,000-$25,000).  At 20 hours per week (which Bryan has available) it would take 3 months.  This project would be utilized in similar pet grooming and salon type businesses.  Currently Puppy Palace would utilize this.  At $300/month the ROI would be 5 years.

1. Vertical time view. (20-40hr project)

    a. Populate Charles' layout

    b. Already have a time slot view.

2. Add drag and drop. (done fairly quickly because time slots already exist - Javascript edit).

    a. outsource this to Cody (20-30hr)

3. Tip splitting. (20hrs)

    a. tips field exists (Eric) on the main invoices if using CC.

    b. open up so that any cart can utilize it.

    c. create a tips page.

4. Texting/email API. (30-40 hrs)

    a. Garrett/Calvin created apis with Twillio.

    b. General filtering (no "cannabis", other reserved words).

    c. They pay 3rd party directly, or pay through Adilas? Monitor and record that.

5. Flagging and Tagging tweaks (15-20 hrs).

6. Pet specific needs. Owner to pet, pet to vet, etc.

*** could be used for multiple Adilas projects.

Emails, phone calls, and touching base. Quick phone call with Cory to touch base on some plans. Spoke with Wayne on the phone for well over an hour. Some of it was just dealing with life, death, suicide (my son recently and Wayne's little brother years ago), and then talking about adilas stuff. Here are some of my notes. As a side note, Shannon helped me convert my post-it note level notes into these digital notes.

- What people see with their eyes and their perception. If you have 8 different people looking at the same product, they see 8 different products or solutions. People have such different views.

- If things are measurable then you can go to a measurable standard, but it is still perception. It's hard to have people agree on things even when you can measure it. It is even harder when you have to have people interpret concepts, principles, things that cannot be measured but have to be interpreted or understood other ways.

- We talked about change and discussed some analogies in physics. If you have a swinging bar, pendulum, how much does it take to change that? Do you have enough force to really change that momentum, to set something different in motion?

- Sometimes, Wayne really likes having peers that know what he is talking about - that is an important part of building a working community. It's important to be able to bounce things off of people that can really consult, help, and understand things. That is helpful for all people.

- God (our Heavenly Father) has plans for me (and you) - there is a plan and God continues to do His work.

- Wayne expressed that while talking with another developer that "our" way has been ingrained, it is the known norm, it is the default path - It feels to some of the developers like, "will it ever change?" What would it actually take to change?

- From this, dealing with change, Brandon was thinking, instead of just jumping into the coding side what could he change that could change the outcome? Like what if he helped plan the project instead of just took the next coding assignment? How does that change things?

- We don't want to sacrifice in the wrong way. Sometimes we are willing to sacrifice but how much more value does it make it to have the sacrifice in a way that benefits the greater goals?

- If Brandon moved more to helping plan this out what could that change? Could that help it move further down the road? Would that be an unwise or undo sacrifice?

- How do you break free of the default patterns and cycles?

Meeting between Steve, Alan, and Brandon. From a previous meeting, we had some assignments. When we started today, we let Alan start. He knocked it out of the park. Great job! Here are some of my notes:

- From Alan - Regularly scheduled intervals

-- Weekly/bi-weekly - Group meeting (15-30 min)

-- Monthly - budget meeting w/ admin/billing (30 min)

-- Quarterly - in-depth goal/vision meeting (1-2 hrs)

-- Annually/Semi-annually - co-owner meeting (30 min)

- Agendas - Alan

- Rotate facilitator - who is leading the meetings

- Small budget talks from Alan - he had worked up some plans

- More salary type options - Alan would like to see us get away from hourly and do more of a salary type approach

- Paid time off

- Get files from Alan - he has some great stuff

- He even did some great work on goals, mission statements, and budgets

- Keeping true to - all data is live and searchable - acronym for adilas

- Monitoring usage and helping to automate things - use technology to see where most people are going and then help speed up those places or parts of the system.

- Getting to an automated free version (trial version) - easy onboarding and setup type scenario - let people try it out

- Following up on people who use or try the free version - sales leads

- Demos, videos, and ways to learn the system

- Working backwards - what do we have already, fill in the gaps, and make it better as we go - different way at looking at the system. Instead of saying, we need to rewrite the whole thing, look at what we have, find the gaps, and then fill in those gaps.

- Updates and videos to help with training for new features

- Cutting costs - lots of talks here

- It got kinda ugly - small internal finger pointing session... everybody is feeling pressure at different levels. Not very good :( (frowny face) but... we had a small little war. It got a little bit heated.

- The subject switched from cutting costs and HR problems to sales and getting out and making sales - everybody, developers included

- Get out and talk to people - slow down and sell it - finding people who fit

- Who should we be selling to? Who are we looking for?

- From Steve - Firewood and analogy of going out, leaving the fire, and looking for firewood

- Changing the approach - we are developers - get ideas from other people and just talk to people - as you talk to people, things will just open up and you'll get a chance to talk to them about what you are doing or hope to be doing. Just open your mouth.

- Eye opening, if you get out there - If you are out and about, you will be amazed at what is out there.

Going over meeting notes from this morning (# 10813). Light training on customer affiliate programs for invoices, ecommerce, and customers. After that, we chatted and talked about some other internal needs and ideas. See notes below:

- A lot of the meeting kept coming back to - what are the rules? How do we define things?

- That is something we are really missing and what is needed in defining some structure.

- Efficiency - how can we create more efficiency?

- Retention - clients, users, internal, more??? Retention may need to include all of those pieces of the puzzle. We need help internally, Brandon wants to help to keep sharing the vision and helping other people succeed as they try to define and implement more structure.

- Make a new graphic to show the structure... this could go along way...

- If working in different departments, report to the correct supervisor based on the project and/or task.

- Helping people know who they are accountable to report back to.

- Start with simple budgets - incentives, bonuses, etc.

- Flex grid to help track budgets - super simple

- Easing pain points

- Guidelines on budgets - make up some rules

- Budgets - start right off or wait? could go either way.

- Staffing - prioritize the biggest needs

- Understanding the biggest pain points

- Biggest resources - other people who are already doing those things

- Get some feedback and input from others - help them invest in the solution

- People are one of your best assets

- Customer support - Sean, Cory, and Shari O.

- Counseling with others - Getting that input from others - Perspective changes - May take a little bit longer

- Communication - Getting people on the same page, then getting it going, then helping it keep going

- Leadership and defining roles

- Processes - plans - what does that look like?

- Talk in person - setup a time to meet, call, text, etc. somehow meet

- Micro meetings

- Department text thread (quick blast) or department email - Group communication format

- Following protocols - Going up the chain - Somehow making a note or list of items to talk about

- Discussion and re-defining expectations - Softer conversation first - If it becomes reoccurring, escalate it

- If we need to, we could use the advisory board to help make hard decisions

- Finding and seeking out good talent

- Not everybody is a leader, that's ok

- Apply my areas of expertise to customers, users, and internal people - training, consulting, support, setup, planning

- Retention Department - Responsible for things such as: Training, Setup, Customer support, Consulting, Adilas University, and their own research & development

Meeting with Shannon to go over ideas for the adilas company structure. We spent the whole time putting together a two-page proposal on where we would like to go with the adilas team, an admin advisory board, and four internal departments. See attached.

We got some of our info from element of time id # 2284 inside of adilas. These were notes from Brandon and Alan as they were doing some brainstorming. Basically, Shannon and I took some of that and put together the small proposal. It still needs a little bit of work but has a good flavor, in my opinion.

Our original plan was to work more on the SWOT analysis today. It ended up being a sounding board session. I was talking and telling Shannon what was going on and she was recording notes. See attached. Lots of fun ideas and concepts. It does repeat itself a lot but overall, great little brainstorming session. The cool thing is that we have some great take aways from our session. Here are just a couple. See the notes for deeper thoughts and ideas.

- AI (artificial intelligence) - Trends and observations

- Who? - Lots of talk about who will oversee and manage what

- Plans

- Marketing - Ideas including being able to cover over 85% of any business. Also some great ideas on marketing adilas' AI (artificial intelligence) aspects

- Company Structure - We really want to nail this down

- Value Add-On Core Model - Industry specific skins and quick aggregates (counts, sums, totals, etc.)

------

New note - added on 1/19/24 - see attached for a new or updated version of our sounding board notes. Small edits and tweaks made by Brandon, after the fact. See attached.

Meeting with Cory and Shari O. going over projects and priorities. After that, we jumped in and went over an API socket connect for a company. Light tech support helping them get connected and going.

Meeting with Cory and Shari O. Going over projects and priorities. Small updates on where each of the current projects stand. We talked quite a bit about the need for more special line items and maybe even making them more dynamic. Special line items are things that our clients get by default (things like labor, part number other, fee, shipping, freight, discount, supplies, etc.). They also have some special functionality that nothing else has as far as how they play, how they show up for roll call, and special grouping on certain reports. The other feature that Cory has been using recently is the percentage add-on feature that takes the cart total and then figures out a percentage to make that number stick and pass through the cart as a fee or whatever. We may end up doing a project to help with these features (dynamic special line items).

Toward the end of the meeting, we were talking about yearend payroll updates and changes that are needed (taxes, rules, forms, new rates and formulas). That comes up every year. One of our constant maintenance items for the adilas application.

Meeting with Bryan. We spent the whole time looking at sub inventory data on data 8 for a single corporation. We are trying to look under the covers and see if we can see why two reports are giving different numbers. We ran query after query checking the data. We thought that it was dealing with our inner joins and left joins. We discovered some stuff dealing with how the relationships are made. Some of them are just plain one-to-one. Some are one-to-many, and some don't even exist. That makes it a little bit tougher to follow and get consistent info.

The crux of the problem seems to be dealing with the relationship between po/invoice lines items and sub inventory packages or sub ids. Anyways, we documented a bunch of the queries that we were running to keep track of our findings. Brandon has those queries on his local computer in a file.

Meeting with Cory and Shari O. - Going over projects and priorities. I'm going to be doing more work on the discount engine this week. We spent a bunch of time on possible solutions for recouping credit card processing fees. We talked about adding in an extra hanger on the main invoice, commandeering the tips options, increasing prices, adding a separate line item, running things through hidden line items, play with it like a tax, adding a connivence or administrative fee, and using multiple invoices to do the job. We also talked about bulk tools and reverse discounts (add to an invoice vs taking away). Lots of options.

We physically went in and played with some of the options. Cory is going to take the info back to the client and see what they want to do. Some of the options are free, meaning they already exist. Other options may include some development time.

Another topic that seems to be heating up is people are wanting to use our loyalty points and they want to transfer in data and/or upload things from outside sources. We talked about bulk external upload tools and how all of that works. We just made some of that code for a client last month. We plan on reusing that and making it able to upload multiple times without doubling things up. Recording some notes.

Meeting with Cory and Shari O. over a Zoom session. We were looking into an issue with one of our client's balance sheet and some gift card transactions. We had to update the created date/time on the corp special account transactions for some gift cards that were partially done in the old way and then converted to the new way. As a side note, we may need to allow that date/time field to be editable. I had to do it from the background. That might be nice to have that as a standard feature.

We talked about the discount engine project and came up with a small plan for going forward. The new plan involves a database change, retrofitting the old discount engine code to use the new database changes, then working on the new discount engine code. Ideally, we get the database piece done and then allow our users to pick if they want to use the old or the new (for a while). When ready, we fully transition to the new code base. We also covered some other questions and what not.

Meeting with Cory and Shari O. We went over projects and priorities. That went pretty quick. We then got into some code and looked at the SG&A costs (selling general and administrative costs). We looked over older code, went through things, and then brainstormed on some new ideas. We would love to start from the expense/receipts. Basically, build it, then click a button or something to create the PO (SG&A inventory) and back tie it to the expense. That would be really cool. We went over some small drawings and such.

After the meeting, I got on a phone call with Bryan. I also did some emailing back and forth with Will on some general webpage settings for ecommerce.

Quick 20 minute meeting with Cory to go over projects and priorities. I then got on a phone call with Steve. We were going over general stuff, sales, demos, meetings, and new shopping cart stuff. Steve requested that I keep pushing on stuff and also help out with Dustin, Eric, Bryan, and Will. I wrote a few things down in my notes to follow-up on with the guys.

Emails and going over a new state level document for selling trailers in Texas (TX 130-U). Going to be working on that project later today.

Shopping cart meeting with Cory, Steve, and Dustin. I gave them a small demo of my new mini scan cart. Dustin is working on taking that code and making it into his own little cart, specific for a single client. Eventually we will use it for other clients, but right now, it is being developed for a single client. After the main meeting, Dustin and I stayed on to go over some other stuff and to make a small to do list. Pushed up some code to fix a small misspelling.

Meeting with Cory and Shari O. over a Zoom meeting. We started on the end of day reports. We have some clients that like the payments filtered by invoice or main salesperson and other clients that like the payments filtered by the person who did the payment or who was responsible for the invoice payment transaction. We talked about some possible options.

We went over our to do list and set some priorities. After that, Shari O. helped with some cross training to help get Cory up to speed on setting up merchant accounts and merchant processing settings. Light back and forth and some light training. We made sure that access and permissions were set on certain servers and accounts.

Zoom meeting with Cory. My main two projects this week are the new shopping cart and the Bear 100. We also talked about the public API and 3rd party solutions using either the public API or a special 3rd party API socket channel. We spent some time talking about the discount engine and figuring out a plan to launch the new code while still leaving the old code somewhat in place. We may have to go backwards and retrofit the old code to handle the new custom date ranges. We'll get it all figured out.

We looked at some sub inventory reports and sub reports based off of sub id numbers and other sub reports based off of the RFID tag number. Shari O. had a few questions at the end of the meeting. She was mostly just listening in to say on top of what is going on and happening. Cory got to show her a little bit of the new shopping cart. It seems like we are mostly on top of things right now. No huge out of control fires. I left the meeting and Cory and Shari O. were still talking about emails and clients. Good stuff.

Meeting with Cory. We talked about discounts on special line items and unlimited special parts. We briefly discussed the new discount engine and plans for getting that fully up and running. The other three things that are coming down the pipeline are helping Bryan with some reports, the mini scan cart, and the Bear 100 is coming up at the end of the week. We also looked on data 20 at some possible duplicate invoices. We talked about some possible solutions to prevent that. You have to work pretty hard to make that happen. It happens in real life, but we can duplicate it while doing any testing. Almost like an Internet glitch that happens every once in a while.

After the meeting, emails and touching base with Bryan on pushing code. Recording some quick notes.

Zoom meeting with Cory. We went over projects, updates, and needs. Light project management. I'm supposed to focus on the new shopping cart and help the other guys as needed.

After the meeting with Cory, I jumped on a GoToMeeting session with Bryan. We were trying to figure out some alignment and spacing for a client that has a custom login page. Bryan and I also spent some time working on some files and Git code repository stuff on Bryan's local code branches. Getting branches sorted out and everything in its own place.

On a Zoom meeting with Steve, Cory, and Shari O. We covered a number of topics. One new one was a little mini cart overview. They want one that is super simple and just does a limited scan cart for barcodes. No major look-ups (showing search results). We went over a few project specs. We talked about a future need for multi cash drawers or multiple registers. This could include a possible way to flag and tag an invoice and an invoice payment based on who is using what.

We went over a number of other small projects. Nothing really pressing. I took a few notes. Mostly just light maintenance stuff and/or allowing payees (users or salespersons) to be flipped on invoice payments or payees (users) to be flipped on subs of time. Most of those places, we just grab the payee (user id) from who is doing the transaction or payment. We may need a way to go in after the fact and flip that, in certain scenarios. Should be pretty simple.

We had an update meeting to show progress on ship B stuff (adilas lite and fracture). We had 10 people on the meeting. We had Alan, Hamid, Steve, Sean, Danny, Cory, Shari O., Shannon, Bryan, and Brandon (myself).

We did record it. The recording is right about an hour long. The first 20-30 minutes were from Alan going over market research and tech deck decisions for fracture. After that, I introduced a new website to publish some of our work on the adilas lite or fracture project. Here are a couple of links:

Adilas Lite - Project Home - https://data0.adilas.biz/lite/

Adilas Lite - Videos & Research - https://data0.adilas.biz/lite/adilas_lite_videos.cfm

The meeting went well. As a side note, Shari O. recommended that we have a fun, non work, meeting just to catch-up and say hi and what not. She is kinda like our mother hen, for the adilas team. Fun times. See attached for some other videos and assets.

After the meeting, I spent some time uploading things and doing some light clean-up from the day. Busy day. 

Going over projects with Cory. Small tweak to the spit cart pages. Pushed up the changes. We then got into a small bug (new need vs a real bug) to allow for the invoice payment search to handle a deeper "or" clause with the salesperson and who did the transaction. Testing and pushing up the new code.

Project management with Cory and Shari O. We reviewed progress from last week, talked about chip readers, and other upcoming projects. We spent some time looking at user data and how a certain company uses PO's, E/R's (expense/receipts), and PO payments. We used the system, did some look-ups, and even looked at some raw data to see if we could figure out what they were doing. It seems like they had a PO, paid for it, then added or modified it, and then repaid for it, then remodified it again and again, and repaid for it. Not your normal processes. The system got confused. We are planning to meet with the client and doing some training vs changing any code.

Working with Cory on projects. Went over some upcoming projects. Things like a redo on the quick clock in/outs, stacked taxes, some black box code for a client, bulk tools on expiring loyalty points, data imports, and some changes on merchant processing for a client.

For the record, the stacked taxes are a client request, and we don't currently have anything that does that. A stacked tax takes a subtotal and runs a tax on that value (normal). It then takes that new value or subtotal plus the first tax and then taxes that. That process (stacking) could be done a number of times. We have never done that and are checking about the liability and legality of even offering that type of a option.

We do a lot of back calculations on taxes and do what we call "with tax included" or out the door pricing but this other one is a new request.

Recording notes. More prep for the digital storytelling talk for a conference. Getting to the heart of things - tracking objects and data over time. I've got to get this out to the world. I love it and I think that it could/would really help others who are exploring these concepts. Currently, this is our vision, but I'd love for other to catch ahold and run with the vision as well. Alone and in the dark, it will die without light and usage.

As I was reading though some of the documents and underlining things and marking things up, I kept thinking about Shannon (my sister) and all of her help. I'm so grateful for Shannon's help on getting some of this stuff prepped and put into writing. It doesn't do others any good if it is just stuck in my head.

It may be quite a bit, but I'd like to upload all of my notes, scans, and docs that I am working on. I've learned a ton by going over these things.

Small note added on 7/27/23 - If you want, here is a link to my notes. There are 40+ scanned pages of notes and brainstorming.

Cory and I on a Zoom meeting. Setting priorities and such. Talking about sub permissions, doing some light quoting on projects, and talking about 3rd party solutions. As part of the conversation, we ended up talking about API sockets and keeping things on different channels. We have at least four channels right now. They are the demo channel, the adilas universe level, the public channel, and the 3rd party solution channel.

After the meeting, I was doing some checking on some new domain names that Steve and I were talking about.

Meeting with Cory on projects. Going over needs for new uploads, FlyHi API integration, and options to explore with Datacap. Cory wants me to help populate a sandbox with some data for the FlyHi guys. That way they can use that site as a demo for their product and integration. Getting some feedback from Cory on some of the forms and layouts that I'm working on.

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

Master Adilas Plan - Jellyfish Model

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

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

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

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

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

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

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?

Zoom session with Kelly and Cory and Steve. We were looking at a cross corp data issue. Light clean-up on some backend database stuff for both Kelly and Cory. Jumped back on with Kelly, Cory, and John to look at a sales tax calculation issue. It was dealing with how the shopping cart figured out taxes based on customer types (including and excluding calculations). After the meeting, Cory and I chatted about other projects on the to do list.

Small side note, it was amazing watching Kelly navigate around with multiple tabs, quick search options, exports, pulling reports, and bouncing from page to page to get the data. We need to remember how hard some of these pages and functions get pushed on when we build out fracture. We need something that is stable enough to hold up the power users.

Zoom meeting with Cory and Steve Palmer from FlyHi and Euflora. We were talking about the FlyHi integration. They are finding that delivery is not as cool as they thought it would be. Super tight margins. It works better where there are fewer places to buy your products. Steve was talking about issues with their new software that the company is making them use. They don't have enough API socket endpoints. That was interesting.

After Steve Palmer left, just Cory and I stayed on for a few minutes going over projects. Quick phone call with John. I then started trying some stuff with the HTML sanitizing and HTML formatting of the stored database records (for a product export).

Meeting with Cory and going over projects. I showed her my progress on the additional vehicle assignments for customers. We went over flow, settings, databases, and direction. She wanted me to push up the daily/weekly sales report code that I worked on last week. She was out of town and wanted to be back before we pushed it up. Ended up merging that into master and pushing it up to a few servers for testing.

She had a few other projects that she wanted to get going as well. She gave me a small list including reaching out to a client on a web inventory question, meeting with Bryan to sign-off on some code, and looking over some code changes that John was making on the 3rd party solutions page.

As a side note, sometimes it gets really tricky the more parties you get involved. We have to worry about ourselves (adilas or the software side of things), a possible 3rd party or outside institution, and the users and how they are working and interacting with the different parties. That can get really tricky and sometimes it is hard to know where the fault and/or breakdown is happening.

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

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

Notes from Aspen and Brandon talking after everyone had left:

- Start emphasizing what we are doing

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

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

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

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

Going over lots of requests for new and enhanced reports. Small errors and fixing a few things. Cory had a small list. Lots of talk about flex attributes and the need to build them out on all 12 main application player groups. Currently, we have them on customers and elements of time. It seems like the next one that is warming up is PO's. We have clients that are wanting to be able to add new and flexible data points to PO's (purchase orders). Of course, once they get added, they for sure want to be able to search by those new flex attributes. They also want them to show up on all the correct spots, forms, searches, reports, and exports. Not a problem, it just takes a goal and some time.

It seems that across the board, our users, on a global level, are wanting more and more control of their reports and exports. This inclues settings, preset and saved favorites, show/hide certain fields or columns, able to rename fields, set and remember the search criteria or filters, and be able to pull down any and all data (reports or exports).

Cory and I were talking about "visibility vs searchability". Our users want "visibility" first, then they want the "searchability". Basically, our users want to see the data and then be able to limit it and/or filter it down from the results that they got. From a coding side, it is easier to filter (control what will show) vs showing everything and then filtering after all of the data is shown and/or pushed out to the user (way more traffic, memory, and bandwidth). On the coding side, we would much rather have you know what you want, then we only have to serve up those records. Sort of a flip flop on who wants what and which way they approach their data and report results.

We have a report that the users want to control multiple parts of an object (say PO's or purchase orders) all from one export and/or report. Granted, the PO has multiple one-to-many relationships, table joins, and records that need to be matched up and presented. Imagine a report search page that has show/hide checkboxes for all of the main PO data (location, vendor, total amounts, PO types, dates, notes, ties to external invoices, etc. - 20 some fields). They then want all of the show/hide checkboxes to show/hide columns for all of the line item details (quantities, costs, prices, items, descriptions, etc. - tons of new fields - 60+ fields). Next, they want any sub inventory information (sub reference id numbers, barcodes, units of measure, special sub attributes, RFID tags, etc. - tons of other fields - another 15-20+ fields). Without going too crazy, they also want any new flex attributes (extra data points or in-line database extensions), parent attributes (inventory level controls for parent items), and other data. I didn't count, but it could be well over 100+ fields that they want to be able to pull, show/hide, filter, and organize. It gets into some advanced settings and big reports with lots of dynamic logic. Not that it is hard to do any of that, it just gets more difficult when you are mixing so many things or parts of the object together.

Cory wants us to start with the "visibility" of the data. As a side note, we may have to off load some of the processing for these bigger reports. I want to be careful about building on possible already tippy code or projects. We have to make sure that everything is stable. After this conversation, Cory and I lightly talked about budgets. We also looked over some code and did some quotes for clients. There are many challenges when trying to mix and bled and mix viewing with searching huge datasets.

Lastly, we talked about fair compensation. We are heavily underpaid and not showing our true value. That gets complicated as well. It's an interesting mix and an interesting game.

Great internal training event. John was running the show today. We had Brandon, John, Danny, Eric, Alan, Dustin, and Bryan on the meeting with us. We were going over the adilas docs (online style guide and code snippets), light review, going over conventions, components, and other style guide stuff. John was encouraging the developers to use the docs and play around with things. As a side note, John has also started some adilas server docs (major backend stuff) as well.

Lots of good discussions. Topics ranged from docker stuff, older code, bootstrap versions, and sign-off guides for development and frontend GUI stuff (GUI is for graphical user interfaces or UI/UX user interfaces and user experiences). We had some good practice sessions and John had prepped some code with some flags where he wanted us to work and change things.

It was great for all of the guys to be on the meeting. I did snap a screenshot of some of the webcams (see attached). We talked about using data 0 as the starting point or standard for a number of things. Especially if we wanted to duplicate and/or use the same things over and over again. The conversation then led over to talking about the future and where we are heading. We spent some time talking about the new framework and being able to swap out dependencies and what not.

One of the last things for the normal training session was a discussion about requests for future training and crossover training. Here is the quick list, not in any specific order.

Future Training Session Ideas
- Cfscript
- Javascript/JQuery
- Back End (Models, Services, DAOs)
- API's - Internal API sockets and external API sockets
- Ajax
- Testing
- Custom CSS & Print CSS

After everybody else left, John and I did a small review of the training session. We were chatting about options and feedback. John and I may start with some CSS and theme stuff (planning for the future). See attached for 3 different videos that we did from the training session. Great event.

On with Cory and Kelly going over new requests for sub inventory reports. Kelly had created some spreadsheets and we were going over those pieces. Great review and we are ready to hand this project over to the developer. We switched topics and started talking about sales tax aggregates and creating manual switches to help force an update.

Cory and I were doing some planning for a server meeting and some decision making. We talked about doing some R&D on the new frameworks that Wayne is working on and almost doing a mini scratch app to get all of the kinks worked out. After that, Cory and I went over a number of other small projects and plans.

Zoom meeting with Cory, Kelly, Steve, and I. Going over plans for sub inventory reporting. I took a number of notes. See below.

- Kelly did some prep work and had a small spreadsheet- Here is the link: Web link

- Some of the report settings need to be at the user level vs the corp or global level- for example: the new advanced part search settings. They are controllable at the corp level but not at an individual user level. We are seeing a need for deeper levels of control, per user.

- She, Kelly, found a good report (that still needs some tweaking)- advanced invoice sub line search for all item categories. The current report shows and does some sub attribute grouping (text based off of the names).

- Kelly thinks that a limit of a 31-day month (whatever the range) would work for now. For both PO line items and invoice line items. If they want to pull info per item category, no date range limit. If they want everything or "all" we limit it to a month or 31 days.

- Ideally, she would like grouped output for PO's, invoices, and items. That's where subs play (currently).

- Steve is working on some sub inventory reports right now.

- We have a currently working model in the advanced invoice sub line search. If the part category of "All" is selected, the actual search page shows all possible sub attributes as filters. We then pass that list of combined attributes over to the results page. The results page then loops over the combined list and fills out what it can. We may be able to use some of these pieces.

- As a side note, we actually looked over some code for the working model to see how it was switching, grouping, and pulling the data. For now, we may take that code and push it over to other sections as a patch and/or band-aid of sorts.

- The sub reports need all of the main line item details plus the sub information. Currently, the sub reports are only showing the sub details. Kelly wants all of the data out of the system. Cory wants to be careful not to get in trouble if we add a bunch of new columns (past history with clients complaining - changing their reports or exports).

- The reports homepage is kinda messy- We may need to rework that page to make it look better.

- We need sub attribute information on its own, parent attribute information on its own, and mixed sub and parent attribute information together. Along with this... We need these same reports for PO's, invoices, and items in inventory. We need all of these pieces. Consistency across those reports.

- Kelly is sort of stuck- helping out the clients. She is pulling tons of reports and piecing them together. She is looking for some time savings and better reporting, out of the system or out of the box vs having to pull things and piece them together.

- Up next, once we have the good reporting that we need, we can build in bulk update tools where you can see it, fix it, repull the report. Export it as needed. We need the visual representation of the data first (good reporting). The other features and tools will come later.

- Steve, Dustin, and Alan are going to be working on some bulk tools for subs.

- Be able to export beginning inventory, ending inventory, and what is in between. That's the goal.

- Kelly likes the super invoice line item search/report. Could we add on a bit there? That might be nice. We talked about creating a super sub invoice line item search (same as above with subs). Maybe a link to that new page from the bottom of the advanced invoice search page (maybe at the top as well).

- At the end of the meeting, Kelly was asking what we needed to get going. She is going to build out a spreadsheet with columns and instructions per column for us to use as a reference. That should really help. We will pass this on to the correct developer to help them know what is wanted and needed.

Steve, Cory, and I stayed on the Zoom session after Kelly left. We were talking about the evolving nature of software and how it seems like it keeps heading towards a form of AI (artificial intelligence). We were talking about developers, projects, and project management stuff. We really want to get that datasource project done (bus to motorcycles or world building project). We spent a lot of time talking about funding. We are pushing as hard as we can, we need some gas money. Big requirements and a tiny budget. It takes time and resources. Our product and our users keep evolving. Project management and quotes with Cory after Steve left.

- It may be good to do a pros and cons analysis of attributes - parent attributes, sub attributes, flex attributes, flex grid tie-ins, and other in-line database extensions. Speed, bulk, capabilities, searchability, show/hide on all or certain templates or views, etc. Where are we headed next or how can we tighten things up to make it even better?

- We first have to get the data into the database. They we have to be able to get it out. Next, what happens if anything changes? We need to think through all aspects of lifecycle of the data.

- We really need a plan - detailed out - commit to it - then really do it.

- More and more of a need for bulk tools (data coming in, data going out, and updating and changing things).

- Charging for what we are doing. We, as a company, are missing out.

- The value of our user/client base as a testing group. We couldn't pay for what they are doing.

- Cory and I were talking about requirements for industry specific software. Expectations of our clients. We have a standard package and then we customize on top of that. It's really tough to do everything, well.

Zoom meeting with Cory, Steve, and Kelly. We were talking about sub inventory. Subs are great but do require more work and effort. Getting info in, out, reporting, and bulk updates and bulk tools. When we started, we didn't even know what was needed. As things unroll and unfold, we are beginning to see a bigger picture. That is awesome!

We have mountains and mountains of data. Now what?

As the meeting progresses, we spent some time talking about the challenges to sub inventory. Here are some of my notes:

- Sub inventory attributes and being category specific

- Settings all over the place - configuration

- What about changes, updates, and flipping categories (after the fact)?

- Possible mapping of categories, sub attributes, etc. Talking about mapping by id numbers and not names or column numbers.

- We need a sub inventory history section. Tables are already built, but they have not been tied in.

- Some of our clients want so much control

- Sub attributes, parent attributes, flex attributes, flex grid tie-ins, and other different levels or layers

- Master list of sub attributes and then repurpose those per category. This could be tied in with the mapping options listed up higher. Either start from the top (master list) and go down (what sub attributes are needed per category) or list out each attribute per category (current model) and then tie and/or map them back to a master type list. We may have to go in both directions. Just some thoughts.

- Kelly likes how parent attributes can be bridged over categories. Having said that, we need to be able to search by sub attributes, parent attributes, and flex attributes.

- Certain clients want to pull data without the category specific reliance. Basically, once we catch the data, we have to be able to let it be searched, pulled, filtered, shown, and exported. It's all part of the puzzle. Being able to get at and use the data. That's a huge key. Just being silly - ADILAS - all data is live and searchable

- Maybe upping the permission level to add/edit sub inventory or sub inventory templates or sub attributes. Once again, we need some histories of who is doing what in the system.

- Steve was talking about - 1. Capturing the data. 2. Then being able to get it back out (in any form - CSV, Excel, PDF, printable, web). and 3. Being able to play in bulk and deal with automation options. Those are some of the goals (small summary).

- We have people who are wanting to add certain sub attributes on the fly, as part of a sub process or sub phase. This gets into sub locations, sub phases, and sub processes and/or steps. Currently, we only show the subs at certain steps and make them go back to certain places to add/edit or update that data. There is a lot of manual work involved. How cool would it be if we could help them and let them setup their own processes, phases, and sub processes. Mini concepts of the data assembly line.

- There is a need for bulk update tools, easy flow processes, and being able to setup their own data flow based off of the subs or steps within a process.

- The use of templates to help control other actions, defaults, rules, and assignments. Having that example and/or template really helps answer a number of questions.

- We went back to the main need of being able to pull data out of the system (quickly and easily) - all data is live and searchable - We really need this and keep going with what we already have.

- Kelly and Steve working on advanced reporting and moving beyond a band-aid. What about going back and correcting the plumbing from the get go. Planning for the future.

- Need for more controls, handrails, and ability to scale.

- Build and break, build and break. Well, it's time to fix it again! it's breaking!

- What if we re-imagined it??? What would it look like? What things do we need to consider if we were to rebuild this out?

- Kelly was recommending that we get into a real life system to see the challenges. We made some plans to meet with Kelly again see the tools that she uses, how she uses them, and what is still lacking and/or needed.

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

This is more for me, but what are the next steps in the planning process for new phases, data assembly line stuff, and where do we want this to go? Help lead and guide it! Keep pushing for more bulk tools, bulk options, and bulk tools to add, edit, update, change, pull data in, pull data out, etc. We can do a bunch of things on a one-by-one basis, let's keep pushing that to the next level. Yee haw!

Cory and I going over projects and assignments. Sub inventory reporting and getting into system wide aggregates. We also spent some time talking about supporting our team members.

Cory joined the meeting. She, Steve, and Sean were going over a few different projects. They were talking about combined PDF's (previous uploaded docs per item, per sub, or per PO) to generate delivery manifests and what not. They were talking about all kinds of stuff for an upcoming demo in the next couple of days. After those other guys left, Cor and went over projects and did some project management stuff.

We went over some cross corp mappings for a client. We removed a few mapped items (just the mapping) so that they could redo a small portion. We got onto the server and looked around by pulling queries on the database. We modified three small records and that should be enough to let them redo the section that they want to do.

Next, we started talking about a new project to allow customers to have vehicles added and assigned to them on a one-to-many basis. We have a machanic shop that really needs this and we can see some other applications down the road. We went over what it would take to set this up, build it, script it, add pages, add logic, and general data flow. We also need this info to be available in the shopping cart and show up on invoices and quotes, as needed. We talked about settings and other pieces that would be required. I thought that it was a fun session.

We will treat this new assign vehicles to a customer similar to how we allow for additional customers to be assigned to other customers, invoices, and quotes. We may use that existing functionality as a handrail or guide for where and how this new assign vehicle relationship will show up and function. I can't tell you how important some of these existing handrails are to our developers. Once they latch onto what the older stuff does, they can virtually back track and/or trace the routes and make the modifications to do the next pieces. Good stuff.

We did some other quotes and estimates. After that we jumped over to ecommerce and were looking at the show subs and sell subs settings. Lots of AJAX (asynchronous javascript and xml) and cascading and looking up choices (manipulating the page on the fly based on a prior selection without a page refresh - one-pager stuff).

Lastly, we talked about some other projects that just aren't ready yet (to even get started on). Some of them have to almost simmer for bit before we really know which way to jump and what to do. If you force it (jump before the picture or vision is clear), you may not get what you really want. It can be painful (to wait or put things off), but some of our best stuff has developed slowly over time (simmering) and we've taken small steps along the way that allow for the next step or phase to happen. Nobody can jump from A-Z, however, if we keep taking the next logical steps, it gets easier and closer to making that jump.

Zoom meeting with Cory and Kelly. The whole thing was dealing with inventory reporting and an advanced report builder concepts. Kelly wants to throw-out a wider net and see what we can catch. Instead of going super deep to financials, she wants us just to focus on the invoices and PO's. Basically, an inventory and CRM (customer relationship management) mix. Leave the accounting alone right now (for these reports). Just help our clients get their data in and out quickly. Basically, it's operations stuff.

One of the goals is to show, teach, and allow our clients to use a mix of vendors, customers, invoices, PO's, inventory items, sub inventory, parent attributes, and location information as needed. All of these things interact on both the sales and customer relationship (CRM) levels.

Here are some my notes from the meeting:

- Talking about building a report building engine. This deals with groupings, filters, show/hide columns, sort orders, etc.

- Kelly was talking about getting to the meta data of the database data (going deeper). What is related, how does it work, what can I get out of it - including mixing things that a company and/or individual is looking for? Even things that we can't think of and/or thing about. Extracting those data analytics and details out of the system. Lots of value there.

- Be able to export to CSV, PDF, and web formats (normal HTML or data tables).

- Ideas about display options - Nested groupings, even pulling and storing data in temp tables, data dumps, and then querying that data. ETL - extract, transform, and load - manipulate the data however we need to. Leave the raw data alone, just tweak out other pieces or tables.

- Show all of the tables and their fields. Preset a few things so that the defaults are showing (not everything is checked by default).

- Use the data tables, be able to save the reports, see new reports from the saved favorites, all kinds of advanced report building options.

- Put this new advanced report builder engine under its own new permission.

- Thinking about vertical tabs (for a layout view). The tables or basic system players would be the left most side (left vertical tabs), the right side would show other settings per table. For example: Say the tabs down the left were things like vendors, customers, invoices, PO's, parts/items, etc. Then when you click on the different tabs, it would show which fields belong to what table (on the top of the page) and then the filters and grouping options would be below that. When you are done, you click to view the report. You could also save a new report name, set the sorting or sort order, and who can see it (assigned to who or just a assigned to all option).

- Help educate the users on the database structure. This could be a great side agenda item for this advanced report builder engine.

- Kelly was asking - Is this new advanced report builder a value add-on? How do we monetize it? We decided that for now, we'll just roll it in and try to sell it as a feature of the whole or bigger picture.

- We talked about sub inventory attribute mappings and creating groups (things or attributes that can cross over categories). This is a form of layering for the sub attributes. Basically, each item category can have any number of sub attributes. We then go in and allow a user to setup groups or which sub attributes are buddies or tied to other sub attributes in different item categories. Making small or mini family groups for the sub attributes. Just an idea to help with reporting and consistency.

- We won't build this in yet, but we have to think about things on an enterprise level. If we build this advanced report builder engine on the corporation or basic world level (where we need to start), it won't be long and some of our bigger multiple world level clients will want an enterprise level solution for the advanced report builder engine. We know that is coming!

- Along with the enterprise level, we know that some of our clients really want the business intelligence (BI) level of reporting and aggregation. It's a known need. That's a whole other plan and topic.

- There may be versions and phases of this report builder engine.

- I was asking about big reports and possible timeout issues. We may need to show sample data and then build out the bigger (in needed) reports and then let our clients know that they are done or finished. Some of these reports could potentially be millions and millions of records. As a note, I know that Wayne was working on something similar to this a few months back. I'll check with him on ideas for timing, flow, and notifications.

- We may want to build in options for details (default level) and/or aggregates groups, sums, counts, etc.

- If you are wanting to get more money from people, it really helps if the people that you are dealing with want the same things (that you want). It creates a common want and need.

- In a nutshell, this project would be mixing and blending all (maybe not all) of our existing advanced search features into one bigger master report builder. Because this project could get so big, we may end up playing around and building a mini version and/or a prototype of sorts.

- We talked about timelines and even ways of distracting our clients to buy some time. All of this takes time and resources to plan, build, and deploy.

- As an addition - it would be really cool if we had some presets (pre-maid selections and choices) to help people get started. That would make the building process simpler. We could show some defaults and then let them modify that vs building from scratch every time. This idea came from Aspen (my daughter) who was listening to the meeting while working on other stuff.

Cory, Shari O., and I were talking about budgets, hours, and recording times, and notes. Small meeting about emails and our needs in that area. We have some email compacities but want to improve and refine those processes. We need a strong communication channel, auto emails sent out daily for collecting monies on accounts receivables, sending invoices, sending quotes, sending statements, etc. We also use emails tons out in ecommerce land to notify both customers and merchants about new sales.

Making plans and moving forward on our email services. Sadly, our current solutions have been a small thorn in our side. We need to provide an enterprise level communication channel. Some of our bigger clients keep wanting more and more high-level enterprise functions and support. Along those same lines, we talked about new development and being able to copy users and permissions between corporations. Other demands keep coming and piling up. It's hard to keep up and make sure that everything is tight and fully functional. Sometimes we feel like ants trying to serve virtual data giants.

Started out the meeting and John and Cory were talking about the adilas docs and making sure that the adilas style guides and dev checklists were all up to date. That's easier said than done. Things keep evolving and changing. We talked about code review, requirements, sign-off procedures, and merging and pushing up code. Lots of moving pieces. There is a huge need for continuing education and keeping our skills sharp.

Cory and I got into discussion about being able to globally copy users, permissions, and settings from corp to corp (universe or world to world transfers - enterprise level stuff). We can bridge a single user between corporations right now, but all of their permissions and settings have to be setup per corp. We could totally automate that. It just needs to become the goal or a project.

John left and Cory and I started looking over code and reports. We talked about options of bypassing certain prebuilt stop-gaps. Many times, we built in certain stop-gaps to help with flow and dipping into sub routines and sub logic (conditional and nested logic). The last topic of the day was talking pros and cons of showing (show/hide) locations on different inventory exports. That could break things into a one-to-many relationship, depending on how they want to see it, especially for multiple items over multiple locations. Anyways, we went over some options there. Cory took some notes and we may revisit this topic later on. Mostly her notes were dealing with grouping, stacking, or defining output columns - various options.

Cory and I going over different projects. One of the new things that needs to be done is some new code to help with emailing invoices as PDF's. Currently, we send emails with links to web based invoices out in ecommerce. We have a client that has to get their emails as a PDF invoice. Anyways, we talked about needs for that project and being able to automatically email clients who owe us money with the PDF invoice, be able to save it, attach it, and also do a clean-up routine for keeping things tight on the server. We talked about some new settings to make all of that happen.

Along with our conversation, we were talking about being able to do these things asynchronously so that the user doesn't have to wait. Also, as a side note, if we did this, our client would be happy and Shari O. would have an easier time. She does all of our billing stuff.

We flipped over to recipe/builds and a custom report that mixes elements of time, recipe/builds, flex attributes, and inventory planning. We made a small bug fix for the USAePay EMV chip transaction stuff. After that, we spent the rest of our meeting going over custom report requests. It's amazing what people want to search by, group by, and what things they want to mix and blend onto a single report.

As we were talking, Cory had the idea of building a big robust report builder that allowed for all kinds of stuff. Basically, a smorgasbord with options, filters, and such. We then put that power in the hands of our users and let them go at it. In rough terms, it will be let them pick and choose, save it, run it. That would be really cool. We also talked about linking and mapping things internally for sub inventory, kinda like family groups for sub inventory attributes. What are they paired with, how are they related, etc.?

The last subject was dealing with mapping, relationships, groupings, and aggregates. Everybody wants all of the data (details) but they don't want to have to wade through it (sums, counts, maxes, mins, averages, etc.). Those are the aggregates. Everybody wants sales data, inventory, and sub inventory data.

Meeting with Cory. She was checking on projects. We ended up looking at some corp stats for a client. We found a small discrepancy between two different reports. The numbers were the same, but one report had more information, and it would be nice if both had the same values. One is called the history homepage (more values and drill-down links) and the other is called corp stats (no drill-down links and missing things like customers, log entries, customer media/content, employee/user counts, vendor counts, bank counts, etc.). We might need to build that out a bit.

Cory invited Shari O. in and they were helping me to look the data and figure out what is wanted and needed. I did a small data fix for Cory and a client on the data 8 server. It was running kinda slow. Anyways, we got it all fixed and patched up.

From Shari O. - Get w/Brandon about the Insurance needed for Privacy liability, Data Breach and Electronic Data Liability - Need to get this into place by this week, so I can put this to rest, and get info to Nevada Compliancy Board; as Adilas renewal of app is pending METRC app for Nevada Compliancy Board until proof of insurance is submitted.

Recap of the meeting - Spent half an hour with Shari O. talking about insurance. We were using the analogy of a baby going naked to wearing a diaper (just being funny). We are ok taking on some more costs to a certain level. If more is needed, we'll have to pass on those costs to our clients. At least those who need the extra coverage. The main conversation was dealing with CGL (commercial general liability) insurance and going over a quote that we got from a company. We decided to go for it based on the quote.

Cory and I going over projects and quotes. We have a client that wants a few new columns on the advanced PO line item search. We talked about a number of possible options. One was dealing with settings and the other was more involved but what we would really like to do if it was just us deciding. We will pitch it to the client and see what they say. Depending on their interest, we may go either way. If they don't bite, we may put it in the schedule and do what we want to do. Where we want to take it is more of a pick and choose what values and/or columns show up (build your own report) vs just a hardcoded report.

Emails, paying bills, and other small to do list stuff.

Cory had a list of project that she wanted to go over. We both reviewed a small video from Kelly dealing with needs to be able to search sub inventory status and sub inventory availability. Basically, some new filters may need to be added to some of the advanced reports.

Cory and Eric were talking about enterprise level stuff and the new item catalog that they are working on. We then switched over and were talking about a 3rd party API socket connection that has been in place for a couple of years. They had some questions and want us to do some research. We feel like they should pay for it (new maintenance and new development). We looked around in our code repository a bit to see if we could find any changes that happened on our side of the fence.

Wayne joined the meeting and reported on some mandatory Adobe ColdFusion updates (patches) that had to be applied to all production server (security risk stuff). We talked about getting server documentation and helping to transfer that server and backend knowledge to the other developers or whomever might be taking over, once Wayne retires. Wayne has been making some notes and doing some screen recording or screen capture videos.

We then rolled into a discussion on a dedicated testing server. I'll cover more of that in a minute. At the end of the meeting, John was reporting on progress on CSS and look and feel changes. He is working on printable deposits and printable expense/receipts. He is also making some small tweaks to the layouts and where certain dollar figure data is located. Good stuff. Cory and John were talking about plans on the discount engine and making plans.

Going back to the dedicated testing server - We went over a proposal to get a real testing server up and going. We currently have a number of testing bottlenecks. We talked about reverse merging in master code to the working branches, to help keep them up to date. We have had problems when a project takes weeks or months and it has not been kept up with the master code branch. When we go to merge it, sometimes there are huge differences, conflicts, and some of the underlying application structure has changed. That merge process then takes a while to sort out and make sure that everything gets fully tested and verified again. Anyways, it is an issue that we deal with.

////////

We then had a small discussion about pros and cons for getting or having a dedicated testing server. This was all recorded on a google doc, but I'll paste it here for searchability. Here are some of our notes from today:

Group discussion notes

Cory - We’ve tried this before - what would be different this time?

John - No FTP access to the testing server - there are pros and cons to that

Wayne - We need to test one branch at a time

John - He would like to see it (use of the testing server) go in a line (testing schedule or queue) - I’m next, you’re after me, etc.

Wayne - If we need to, we wipe it clean and then start over again. That’s the process and the beauty of it. We test on it, beat it up, and then wipe it clean for the next round.

John - We can get a full copy of a client’s database and then kick the crap out of it. When done, we just flush it. We never mess with live data. We just make a copy and then test and push against that. Much better look (at live data - copied) then our own fake development data.

Wayne - We need a way to turn off outside 3rd party API’s - either mocking it (pretending) or muting it (silent send outs).

Cory - Sometimes we have big issues with Metrc and other outside parties and doing testing that flows into outside 3rd party API sockets and feeds.

Cory - Currently we are using the Herbo server for some testing. We have been having problems with that. What is going on?

Wayne was commenting on the Herbo server - We are mixing branches, there is still FTP access, it is pointed to a non-master branch, and we have certain things that we can’t change for demos or other needs. Basically, we are using a live server, we have live clients on it, and we are trying to test on it. Too many mix and blend variables... Hard to manage.

Wayne - Would like to see some project scheduling - project A on this day, project B on this day, etc. Keep it tight (ish).

Cory - Con of having just Wayne and John having access to the testing servers. The scenario is, if we find an error, we can fix it right away (whoever the developer or testers are) but then we have to contact either John or Wayne to help that new code get pushed up and deployed. That becomes another bottleneck.

Wayne - We could change the timeframe or auto deploy time cycle to make it faster.

Cory - What about data 5? That is an option, but we would have to make a full copy of the database and all of the corp specific files (images, PDF’s, csv files, etc.). We could then order a new hard drive or put those files somewhere on the current hard drive that we could get back to if needed.

John - Talking about paying bills (meaning our clients)… If a client doesn’t pay, we should be able to just shut them off.

Cory - Question - How much does it cost to put things in cold storage? How much does it cost to bring it back up live?

John and Cory - Talking about costs. John was saying that we need to build in this cost ($400-$600 per month) as an operating cost. We are a software company. We kind of need this. Just like being a foundation company and not having access to a cement truck. It creates a problem.

There are ways to lower the cost, if needed. We could lower CPU’s, RAM, etc. We could also spin things up/down as needed.

Wayne - Rough cost to spin up a server is 2+ hours (somewhere in that neighborhood)

Cory - Really liked the video idea of Wayne recording what he does as future training things and visual assets. Good idea. We just need to be careful of who gets those… This is the whole backend access zone stuff. We just need to keep it tight.

John - He has some server docs and would like to get that put into a private repo that only has access to Wayne, Brandon, and John. Small group.

Cory - Figuring out a way to force some of these clients to pay for cold storage and reanimation or redeployment of the servers. It comes down to if you don’t pay your bills, we get full control of what happens. We need to do what we said that we will do. Forcing the hand by making them pay for the backup data.

John - We just need to have our plans and procedures in place. We need something to stand on.

Brandon - We could do some cold storage on the same servers. Either with a different drive or a partitioned area where we could store things. As a group, we were talking about other possible storage options within the same box. We could make copies of ColdFusion files, client files, and SQL data dumps. Put them all out of reach but on the same server. Then if needed, we could restore things as needed.

John and Cory - If we need to reanimate or redeploy - here are the params and timelines and costs - Part of the plan. Some of these values may change in the future as well.

John - If the crap hits the fan… He doesn’t want to be in the spray zone of that fan. We need to protect ourselves.

Prep work and checking out a reported bug/issue on the time-picker. It actually wasn't a bug, it was just forcing the users to play clear out to the minutes and seconds, based on some settings.

Cory joined and we spent some time catching up and talking about projects and issues. We talked about it and we will take off the time-picker for most of the pages that allow for user time inputs (files like add new timecard, clock in/out for users, edit timecards, customer logs, follow-ups, and both main and sub entries for elements of time). We did a search and it only looked like a few (20+) pages that need to be edited.

As we were talking, Cory gave me a few other small projects that need to be done and finished. She will send me some emails with more details, but it sounds like a data clean-up for a client that had the wrong cost of goods based on manual changes. There is also a request to add a few new search filters to a sub inventory PO based advanced search. We went over a few other projects and requests as well. Cory and I finished up around 11:30 am.

I then started working on the project to remove the time-picker from certain files. I uploaded new code to all servers and let Cory and Shari O. know about the update. Small work session.

Just Cory and I were on this meeting. I was reporting on projects and timelines. I showed her my progress on the duplicate recipe project.

Cory was checking in on projects, bugs, and what not. She had a list, and we went through things. We talked about some quotes and numbers for a client dashboard. We need to get to the duplicate recipe project for Kelly. We set a date for the 15th of this month to be finished with that project. We scheduled some time and now we just need to do it.

We spent some time looking at a client's data. Small little fix and trying to help a client with their financials. They had some bad costs of goods sold that didn't have a real backing (they plugged the numbers) and thus it was throwing off the balance sheet.

At the end, Cory was saying that she is trying to help support me and the other developers on our projects and time lines. That is awesome. Sometimes (often) we need the help.

Back to the main index for the master adilas plan

Master Adilas Plan - Jellyfish Model

Brainstorming Ideas and Topics:

- How big do you want to be? – See also the internal questionnaire responses and survey - tons of good info there - almost a mini plan by itself. Also, question 7 on the survey has a whole write up on the adilas jellyfish or jelly fish model and explains it further.

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

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

Areas, sections, and departments in more detail:

** for me - go deeper into each section **

1. adilas.biz

• Are we going to stay the same entity? Are we the same or are we different entities? Are we rebranding? Are we piggybacking?
• What version are we on?
• Adilas.biz or adilas lite? Branding? Marketing? etc.
• The thing that keeps us all together is the reoccurring monthly services subscription for the main adilas.biz system. It has been the glue that keeps us together.
• Offering upgrades from ship A (current adilas) to ship B (fracture or adilas lite)
• What are our goals for ship A? What are our goals for ship B? Are we building it up to sell it? Are we going to be replacing ship A? How do you transition between the two.
• We want to make our current product better. It then grew into a full or bigger rewrite. It seems to be changing more and more. Originally, it was pretty small changes.
• Timelines to get things done? What will it take?
• Ship A will be great salespeople for ship B, once ready.
• If people change from ship A to ship B, there needs to be an increase or at least a re-evaluation of monthly fees and services.
• Ship B, we are planning for tiered pricing and dynamic billing based on functions, sizes, usage, storage, and preset packages.
• Ship B, they can toggle on/off different settings, include other features, and change what they want. All of this will reflect on dynamic billing options.
• Talking about future plans - selling it, royalties, secession, retirement, etc.

2. Admin

• The admin's role is to manage the budget, make decisions as to the direction that we need to go, do HR type functions, payroll, manage the different groups and departments, communication channels, general running of the day to day business.
• This could be one person, multiple people, a board, a council, etc. Somebody or some entity needs to be in control.
• Co-owners, Co-Founders, CEO's, presidents, vice-presidents, board members, etc. We can figure that out.
• If we do one person, we need to have VP's or managers in the other departments.
• One of our problems is that none of us (on the current team) want to be that person or take on this whole responsibility.

3. Monthly Reoccurring Service - aka Billing (new name)

• This is billing, invoicing, receiving, dealing with monies coming in and reaching out to our clients.
• Accounts receivables
• This could be tied in with admin roles
• Debt collection, bad debt, accounting, financials, etc.
• Setting up new corps (currently) and sending welcome emails and collecting business contact info.
• Bank reconciliation, paying bills, prep the budget info, etc.
• We could automate some of this, in the future.

4. Sales & Marketing

• We like that they are together. This is anything to generate and keep new clients to keep coming in and paying for our services. This could be publicity, knowledge about the system, get new demos, entice our clients to buy and keep buying from us. Serving their needs.
• Currently, the main method of marketing is word of mouth and referrals.
• We have used sales reps, consultants, and light networking. Steve and Kelly have been some of our biggest sales type people.
• We want to listen to what feedback they are bringing back. Currently, the sales people and the developers almost live in two different places.
• Sales should have a good pulse on what is working, what is not working, and what people and our clients are asking for. We tend to get lots of good ideas from clients. Sometimes, what that takes or the priority, that can get tricky.
• How big do we want to be? Get everybody or get enough (sufficient)? Keep pushing into other markets or be content with good ROI?
• Helping with market research, looking around and checking out markets, and what do we need to do to penetrate those markets?
• We almost feel like being in no man's land - too big for just a few people to push on it, not quite big enough to really have the team that we need to push it. Do we push and go bigger? Or do we trim down and keep it like it is (not really coasting but strategically developing as we can)? There are associated questions about speed, reliability, and uptime.
• Along with sales and marketing, there are expectations that are set and keep changing (trends and expectations).
• We need to know who we are servicing. Currently, we are kind of all over the place. We have little accounts, medium accounts, and some big accounts. We could go any direction. We just need to decide. Where is the sweet spot?
• If we want to be big and grand, we will need some major funding and thus major sales and marketing. Or do we figure out the sweet spot and really refine and focus in on things.
• Making things more stable and more reliable. Keep improving.
• We have a lot to offer - no one has even heard of us.
• The new and upcoming business owners are going to be fully connected and have certain expectations. If you want to get those guys/gals, you're going to have to revamp things.
• Our current mix is very developer heavy. We really need to switch that focus and get things that people want. Easy, Powerful, and Pretty!
• We need this department to really keep us in the know on what is going on. Currently, we don't have anyone fully dedicated or assigned to this department. We've been missing this piece.

5. Setup & Training

• Originally, we didn't charge for any of this. We just wanted people to get on our system. We are now charging for this and even trying to presale some of the training, deployment, and setup stuff. We are finding and have found, that people who get setup correctly and have the correct amount of training stay longer on our system. It has a learning curve, and that proper setup and training goes a long way.
• Currently, one of our system admin persons has to go in and create the corp, do a bunch of the settings, assign the master users, setup the logos and colors, and get them going. Most of that requires someone from our team to hold their hand along that process.
• Futuristically, we really want to help automate a bunch of that. Have them setup their own corp, let them pick what industries they want to play into, help them with their settings (wizard style), and then even help them pull in their data (without any other involvement). Let them create a test account or a free version, play around, and then either upgrade or get some help.
• Offer services to help our clients. Also have a number of self-help tools and features to let them do it themselves.
• We would love to develop a number of preset packages and industry specific skins.
• We would like the setup and training to be coupled with education and the adilas university side of things. They are very related.
• Getting products, customers, vendors, and other info into the system easily. Currently, we have to do a bunch of that (data imports) on a one-by-one basis. We need to make that more global and self-help level.
• Provide a good starting point to help them succeed. Show them the benefits and advantages of doing it our way or how we help them succeed.
• This department or division could include the adilas university, training, tech support, setup, and training.
• Easy access to get help and direction if needed.
• We see a lot of user error type problems. Figure out ways of helping them stay in their lane better or put up guardrails or bumpers to keep them on track.
• It has only been recently that we have added more focus on the setup, deployment, and training.
• This department could also include on-going training and retention. That is huge. Things constantly keep changing and we keep adding on new features.

6. Tech Support

• Currently, we allow people to email or call for tech support. It's free but often bleeds over into full on training, not tech support.
• We could build out a report a bug or open up a ticket or an issue. Make it easier to get support.
• We could provide better help files, tips, how-to's, videos, tutorials, and in-person training events.
• Everybody uses the system so differently, that makes it kind of tough. It would be nice if we have tech support stuff that was industry specific or catered to a specific industry.
• Tech support really should be part of the training, setup, and deployment stuff.
• Tech support could be a small carrot for deeper training and/or offering other paid services.
• Helping to show the value of deeper training and education.
• Having a standard way of getting to training and even industry specific training.
• Offer some adilas university training courses - covering various subjects on scheduled dates/times.
• Really helping to push the training and education stuff. Tech support should be quick, temporary, and non reoccurring. Show them the benefits of getting properly trained.
• As we move forward, we are planning on simplifying things. That should help with the training needs and the tech support stuff. Helping them figure it out on their own.
• If people (our clients) really want more tech support, we could offer more robust or advanced support packages.

7. Design

• This could be websites, forms, reports, interfaces, dashboards, UI/UX (user interfaces and user experience). This is the pretty and easy part of it. The powerful may be from a feature or backend process.
• Most of our current guys are developers, not designers.
• We don't charge enough, as such, we tend to skimp on the design phases and processes. This tends to get skipped or minimalized.
• We tend to do function over form - however, most clients say that they want function over form, but really, they want form over function - they want it to work and look pretty.
• Our project management tends to be a simple one liner. Do such and such. No other plans, requirements, mock-ups, or fixed specs exist.
• Mock-ups, prototypes, samples, wireframes, flow charts, graphics, videos, etc. We want to show the plan, air it out, and then build to the specs.
• Modern look and feel and user experience keeps changing. We need someone to keep watching and keeping up with trends, expectations, and options. This needs to be monitored and maintained regularly.
• Figuring out and sticking to a style guide. We do have a section called the "adilas docs". We have been working on it, but it has not been fully adopted yet. We need to set those standards and then stick to it. This is our style guide, and we are sticking to it.
• Doing some test cases and getting user/client feedback. How did their experience work out and what did we learn from that?
• Planning in maintenance and upkeep.
• Our clients squawk at things not being consistent. I don't mind change but I don't like some change and other things not being consistent. We could also introduce settings.
• We could allow the users, or corporations, to choose their default layouts. Horizontal forms, vertical forms, stacked forms, or auto formatted. We also want to store those settings and allow them to change it on the fly on per user basis.
• We need some consistency - this deals with who the designer is, what we are designing and outputting, people's preferences and opinions, and where we are heading. We can all be different, but we need to be consistent.
• Allow people to try things out and/or fully switch over.
• There is a point when we need to keep moving forward so we don't have to keep supporting all of the older styles and themes. Help make that as smooth as possible.
• We have some needs for design work out in ecommerce, customer facing sites, portals, and even business websites or web presence stuff.
• We need designers to help with marketing and social media stuff. Once again, consistency, specific plans, strategic campaigns, etc.

8. Custom Code

• This is one of the things that really sets us apart from other systems. We love it and even encourage it.
• We currently have tons of black box options. That was a solution at the time. There are some great concepts there (black box stuff) but we did run into problems.
• The code base keeps changing. We have had people ask for things, we build it custom for them and then wrap back and make it standard. The ones who got the custom version are now off on their own vs being fully integrated into the main codebase.
• We offer a lot of this. Having said that, we don't charge enough.
• We would like to move as much as possible to data driven settings and permissions.
• One of our current issues in maintainability. If it was on the side (like a black box page) it got left behind. The main pages always got updated but anything custom was harder to test, and harder to main it.
• If we do custom code, we need to build in some maintenance costs to help maintain that.
• We could do a community type approach - who ever helps build it out, gets a commission or a usage fee for others using it. Kinda like a sponsorship or something. We just need to get enough to plan it out, build it out, test it, market it, and then do some sort of kickback or reoccurring usage fee. There may be different levels  - one-time, reoccurring, built in, full one-off custom code, settings, combined projects (we pay, they pay, we then get to use it).
• Custom code should be by our internal developers and internal development team. We need to make sure that it works and doesn't affect something else.
• We have had some maintenance issues. Who made it, what does it do, how does it work, what does it touch, what else does it touch up/down stream, where does it live, how can you get to it, and was there any planning or testing done to the custom code? Tons of potential far reaching questions.
• If we build something... we really need to get an ROI and market those pieces.
• We could do some pay as you go build outs. Monthly fees that get added to their bill. They could pay upfront and then get a payment plan, or set it up on a reoccurring basis, or whatever.
• We need to charge enough. We often shoot ourselves in the foot. We charge pennies to build on top of multi-million dollar platforms and applications.
• We need good planning, good project management, good estimates, and then good developing.
• Estimates - take what you think it will take and double it. Then double that. It's almost a 4x ratio. By the time you add the work to get the work, the work before the work, the work, the work in between the work, the work after the work. It all plays in.
• Paying for both quality and speed.
• On the estimates, we also need to think about opportunity costs and what are we not working on, while doing custom code work.
• Approving custom code. Just because someone wants it... doesn't mean we should build it out. How does it fit with our mission statement, goals, and overarching plans and rollouts?

9. Consulting

• Byproduct of the main reoccurring business services. Once we are in, the system starts generating byproducts and people need to know what is next, how to do certain things, where they could go, options, next steps, phases, etc.
• We haven't really tapped into this yet. We do it, but we could do it so much more.
• This could be tied into the training, setup, and education stuff. Teaching our clients the best way to use the system to get the most out of the system or platform.
• You start getting into paying for knowledge and experience and expertise.
• We have seen many of our power-users become consultants. They know the system, they know how to make it run, sing, dance, and play. That provides a value to others. Those people then offer their expertise and know how to help others.
• Currently, some of this is done on the side. Adilas has no part in it, and no kickback exits. We would love to bring this more inside but that takes money to keep those people on call or on staff.
• This could be a great thing to add to the adilas marketplace.
• We may allow some outside stuff to go on, but we need some rules. We could configure this any way we want, we just need some rules.
• This could be part of the adilas cafe scenario - our clients seeking out a professional to help them out.
• Do we want to manage this internally? What would that look like? Once again, we may need some rules here.

10. R&D

• Research and Development - You have to spend time here to move the ball forward. If you aren't going to move forward, nothing will happen, you will live and die. You have to keep up, especially with tech stuff.
• Exploring different avenues - there are costs for exploring.
• Cutting edge, bleeding edge, sweet spot, new ish, or older/classic?
• How much does it cost to be on that cutting edge?
• Vision, plans, and looking to the future. Where are we/you heading? Plans, how are you going to get there?
• It really comes down to where do you want to play (on the spectrum)?
• Training what is new.
• Maintenance for what was or has been developed. Technical debt.
• Stable and known or less stable and new - How quick will the older pieces change and/or be deprecated? If it's so new, it may not even stick.
• We make things and then it sits on a shelf. That hurts. There could be difference between development that didn't get fully funded vs totally new prototyping and experimenting.
• Is this something we should do? On not? Figuring out what it takes to make something happen.
• Looking into speed, efficiency, demand, cost analysis, needs analysis, scope, scale, and reality of doing certain things.
• Beta testing, prototypes, experiments, testing, pushing boundaries.
• Currently some of our R&D is mixed in with our code. We try things to see if it works. Without being consistent with other pages and code. We often have good intentions (prepping for the future - mini stubs or prepping for stuff) but then get pulled on to other projects. We do a lot of experimenting within our projects. Almost a revolving door or revolving code set. Basically, a fully working, living prototype.
• We are seeing a mix between custom code, R&D, and project management.
• Back tracing or reverse engineering things. Sometimes if you know what you want, you can then figure out a way to get there, that might be easier or better.
• Being aware of what's out there? How could I use some of that in my projects?

11. Project Management

• We have really been missing this piece. We do a ton of just in time project management. We are not very good at doing a more full design, plan, or architecture type layout.
• We do a lot of this one-on-one right now. One project and one developer.
• The project manager can and does act as the shield between the client and the developer. Buying some time or deflecting decisions.
• They help with quotes, estimates, and project specs, scope, costs, timelines, and details. Lots of potential back and forth communication is needed.
• We have spent a ton of time and money going back and fixing things that should have been planned out originally. We have also spent money where a developer makes a decision and just does something and doesn't ask or doesn't get any clarification.
• Teams - authority, accountability, and responsibilities - setting up clear expectations. We have played around here a bit. We need to refine things here a bit, based on our needs. We had some people who were so worried about how to do scrum that it didn't actually happen. We also had some problems with free riders. We want to use some small teams, but still need to get it refined a bit better.
• Dealing with teams, we were trying to do some training... and we didn't really have it all defined. Wasted time in meetings, talking about code, and what is needed. We then fall down based on assumptions or just verbal communication. It needs to be just a little bit deeper and more consistent.
• Team sizes and dynamics.
• As a project manager, not assigning yourself to a required task. Actually, make an assignment to do the project management.
• Someone needs to be available and be the virtual babysitter. Getting rid of hurdles and what is expected of them. Helping them stay on task/track. The project manager's job to help other people succeed.
• Slowdown
• We build and build and build... we need to slow down and test it, train on it, market it, and push it.
• Being able to plan it out so that we can reuse as much code as possible. Giving the developers guidelines, handrails, samples, and good instructions. If it's too tight, they don't want to do it (it takes out the fun of figuring it out). Figure out what developer needs what (how detailed) and then play accordingly. Developers need to accomplish something. Not just follow A-Z and you're done. It is a mix and a spectrum.

12. Internal Development & Maintenance

• This internally funded by adilas to work on adilas. This comes from revenue and budgets to keep the system up and running.
• Bug fixes, maintenance, changes, next steps, phases, testing, documentation, code review, etc.
• This needs to be tied into project management and custom code.
• This is the most defined area that we have inside of adilas.
• We get a plan from project management, we then build it out, test it, deploy it, and make sure that it works.
• We have had problems with guys following style guides. Everybody has their own ideas on what a good style guide is. This could be whitespace in code, tabs, naming conventions, etc. It also happens on the look and feel part of page or report.
• Alan had the idea of having a way of helping to force or standardize the output. Almost a forced style guide or validator of sorts. It all has to comply to a certain standard. Whitespace, naming conventions, comments, indents, variable names, components, etc.
• Keeping things separated - backend, database, objects, services, views, logic, functions, classes, etc.
• In object-oriented programming, you need good encapsulation (only contains what is needed) and low coupling (lower number of steps as possible).
• There is some great value in teams and getting different points of view. A better solution because we worked on it as a team. More well-rounded.

13. Adilas University

• This goes hand in hand with the training and deployment section. This is the training arm of the system. It may also tie in with tech support or consulting. We could combine some of this as needed. Similar type people and knowledge resources.
• General topics for training - One, how do you use the system? Two, how do you run your business? Consulting is a part of this as well - what are the best business practices and how to get the most out of the system.
• There could be standard stuff, custom stuff, and internal stuff.
• Each page would have how to videos, quick videos, and options for more or deeper training.
• We also need to offer some custom or live training events.
• For fracture, we experimented with a thing called the education mode. You could turn it on/off and the system would hide or show more options and information. You could turn it on from any page and all of sudden it would react differently. We have some great screenshots on this from Jonathan Wells. Along with this, the help files could be shown, side-by-side with the page that they are referencing. There were also options to toggle into the actual adilas university site as a tab withing the side-by-side help window.
• There is a known missing gap here on the education and training side of things.
• There could be free levels, basic stuff, and deeper more paid type levels of training and consulting.
• There could also be certification levels, requirements, status, and other testing and certification stuff.
• We are hoping that the adilas lite and fracture project will make it even easier to help train the users and because they can tweak everything, there will actually be less of a need for certain pieces of the education and training. They will still be there, just hidden as needed.
• This could be a whole other business entity, if needed.
• A new user really wants to be guided through - holding their hand. An advanced user may not want any of that stuff in their way, just let them do it quickly.
• Link to this from the adilas cafe.
• If we do certifications, maybe show or allow some of that basic info to show to other users, if they are seeking trained professionals to help them out.
• If we have trained users, those become a value to others who are looking for help or pros on those topics.
• Adilas University could be a stand-alone product, or it could be interwoven with the entire site. Both have the same content, they just either have a standalone navigation system or we help navigate for them based on what page the users are on (context stuff).
• There could be levels to the training... Think of a triangle - simple, basic, intermediate, advanced, and deep or backend logic or design level stuff.
• There may be both external and internal training pieces. Along with that, we may have to have permissions or something that open/closes those training modules for certain people or parties.

14. Adilas Marketplace

• Part of the adilas cafe. People could sell their products and services, buy products and services. Including adilas skills and other professional skills.
• Adilas creates lots of byproducts. This is a way to help harness and gather up those byproducts. 
• Options for 3rd party solutions, white labeling, advertising, marketing, etc.
• Online mini marketplace for adilas products and/or our users could sell their products and services on a mini Amazon or eBay type level (mini consignment type shop built for our users and companies that use our products).
• Possible payment solutions with interest, fees, commissions, and other small kickbacks for using the marketplace.
• Limitless potential for other byproducts and additional services that could be added on to this piece of the puzzle.
• This may need a separate team to help run, manage, and administer this piece of the puzzle. Automate as much as possible.
• Here is a rough draft - Russell did - way back - don't get stuck here... It could be so much more. Adilas Market

15. Adilas Cafe & Community - Adilas World

• A landing spot outside of any corporation or entity.
• A corp selector - where can I go (have permissions or access)?
• Get to the marketplace type stuff.
• Get to the adilas university stuff.
• Forum type stuff - ask Q&A type stuff. This could be answered by staff and/or other users. This would need a moderator or forum manager.
• Let people show that they have the skills that others (businesses and/or individuals) could be looking for. This may include direct messaging or some other way of communicating.
• White labeling options.
• Standardized portal - single sign in be able to jump between servers and corporations.
• Dynamic billing and making payments.
• Mini marketplace for adilas products.
• Sales and creation of new accounts - tiered pricing and auto setup options
• News and updates - configure news feed as needed.
• Interface with other companies and corporations. Get assigned, hub type model.
• Work, play (demo sites), buy, sell, training, social stuff, and participate.

16. Databases, Networks, Servers, & IT

• This is the whole backend of the application or hardware side of things.
• Load management, reliability, up time, speed, redundancy, backups, storage, orchestration, etc.
• Lots of security needs and requirements. They will also be majorly involved in implementation of security.
• Code interacts with these things, but they are separate entities or divisions.
• We will need our own documentation, permissions, training, etc.
• Maintenance and upkeep, prototyping, standardizing, testing, databases, servers, hardware, clusters, network, security, IT stuff.
• Patches, updates, protection, hacker prevention stuff.
• Email servers, text or communication servers, web servers, database servers, backend logic servers (ColdFusion or whatever).
• Monitoring services, requests, traffic, load balancing, stats, specs, remote access, database indexing, automation scripts, tons of IT type stuff.
• Migration stuff, off-hour updates and maintenance, backups, restores, and other tasks.
• Move data around, put things into and out of cold storage, special bulk data manipulation stuff, zip and archiving things, etc.
• Future proofing things.
• Offloading bigger or longer processes.
• API sockets, API endpoints, and being able to load balance traffic, requests, deal with sessions, server config, clustering, and managing small microservices.
• We need a way to get rid or purge some of the pieces. The current system builds and builds. It never really releases or virtually poops (dumps).
• We would love to get a full data dictionary to allow our new frontend to be more data driven.
• This could be multiple people - DBA, IT/Server guys, etc. They could cross over, but these are high level skills and high level people or teams.
• Everything on the hosting side of things. This gets deep but just think - what do we need for hosting? - SSL's, domain names, hard drive space, spinning up servers just in time, pointer records, DNS, DSN, puppet, orchestration, bit bucket, code repositories, ColdFusion Administrator, Fusion Reactor, Papertrail, Nagios, tons of outside services and tools.
• Servers - hard drive sizes, backups, RAM, CPU's, configs, and the list goes on.
• This could go deep and deeper... Etc.

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

- Alan and I were playing with a mini version or what that might look like (see attached for a mini mock-up of the smaller mini model):

Adilas.biz - admin, monthly billing, and day to day running the company. They could do their own R&D (progress, speed, what the clients are wanting).

Sales & marketing - They could do their own R&D (advertising, pricing, features, marketing materials, etc.).

Consulting, tech support, setup & training, and retention. This could also be part of the adilas university (similar folk). They could do their own R&D (tied into sales, marketing, training, etc.).

Development stuff - project management, custom code, internal development, maintenance, & design. They could do their own R&D (code, frameworks, layouts, look and feel, etc.).

IT stuff - Databases, servers, hardware, hosting, etc. They could do their own R&D (speed, load balancing, redundancy, monitoring, etc.).

Marketplace and adilas cafe - This could be their own little piece or small team. They could do their own R&D (product research, options, pricing, hardware options, services, etc.).

We would love to see each of these sections or divisions (departments) be able to meet and interact with each other on a consistent basis (at least monthly or semi-monthly). Nobody is left on an island by themselves. Communication is huge.

Meeting with Cory. Small bugs and small fixes. Working on quotes, projects, and general project management stuff. Cory had a list of things to go over. She has been out of pocket for a few weeks (vacation). Shari O. joined and we had a quick chat about numbers, budgets, and personnel.

Wayne, Cory, John, and I jumped on the server meeting. We were reporting on updates and what has happened since last week. Cory had some questions about being able to move corporations around. That lead to a discussion about future goals of being able to move to a fully clustered environment. Talking about plans and where we are headed. We also went over a few of the prep steps that we need to do in order to get there. Light talks about the datasource project. That is part of an overarching world building project that we are working on and chipping away at. It keeps coming up. We really want to push it forward, as we are able.

Wayne was explaining clustering to Cory. I was mostly just listening to them talk back and forth. We did talk about maybe doing a small prototype or demo project to do a proof of concept. Next, we talked about building up a data dictionary. At some point we want to document the whole database, tables, relationships, primary keys, foreign keys, data types, and other data definitions. As a fund side note, inside of the adilas shop corporation's site, we have a number of documents that Brandon has worked on over the years - the beginning of the data definitions and data dictionary stuff. To find those, do an advanced media/content search and add the keyword "database" to the file name or path field to get the results. Some of the original work was done back in 2014 and then added onto later on.

As we were talking about data dictionaries and definitions, we talked about getting everything in one spot where all of us could see it and contribute to the document. We have it stored inside of adilas, but it isn't really setup for quick contributions like a google doc or something like that.

Lastly, both Wayne and John got into some deep talks about Java memory stuff. John and Cory were also talking about look and feel pages and upcoming projects as we ended the meeting.

Two different sections. Steve and I got on a quick meeting to talk about yearend stuff and 1099's. We were talking specifically about different parties and individuals. After that, Cory and I were talking about how we can help Steve and take some things off of his plate. Nobody likes that, but sometimes if you don't remove some of the weight, it sinks the ship and/or makes the skipper make bad decisions.

Cory had a list and we started going though projects and updates. We went over 5 different client projects and where they are at. We looked in the code at a possible bug on inventory usage. We talked about new requested features and reports. It just keeps going!

At the very end, Cory and I were talking about the concept of being supported or feeling like you are supported (loved and cared about).

Chat and work session with Shari O. We were talking about 1099's, both federal and state liability, ethics, values, and right (subjective) vs correct decisions. Good session.

Cory and John were talking about GUI interfaces and UI/UX client experiences. That seems to be where everything is heading. John had a great idea of adding in a new setting to allow our clients to keep progressing and seeing our more modern changes or virtually flip back to what it is right now (a mix between classic and the snow owl theme). Great idea. We chatted about pros and cons for some time. Good stuff!

We are going to be calling the new setting - default page view for snow owl theme or default page view for short. The choices will be snow owl - modern or snow owl - classic. We talked about getting user feedback, outside opinions, and customer/client critiques. These new settings will be at a user level. The main theme is higher, at the corporation or world level. The new display or default page view settings will be a lower or user level, so that each person or user can set their own preferences.

We switched gears and Cory and I spent some time going over projects and updates. We looked into some code on PO's and how they relate to parent item costs and cost updates. We talked about new corp-wide settings for allowing cost changes or locking things down, on the PO level for tracking cost changes. After the meeting, I spent a little bit of time testing some of the GoToMeeting video settings and flow. They recently changed some things around.

Page layout stuff with John and Cory. Getting good feedback from our clients. The hard part is listening and then implementing changes. Cory and I then went over a number of projects. We have a request for a custom (bigger) image for printable invoices. New payroll settings with show/hide options and new custom alias names and other settings. We also talked about charging for training. We fail at that sometimes.

We got into default corp-wide settings and wishes for the future. It is amazing how quick our clients want things, but at the same time, and in the same breath, they want sub settings, micro control, and sub level permissions. It's a very interesting mix.Cory had a list and we went down the list and chatted about projects, updates, and other things that are coming down the pipeline. Cory had to leave and John and I flipped back over to look and feel and layout stuff.

John is reworking the bank pages, deposits, and other financial documents and pages. We talked about responsive web stuff and also flipping it over to printer friendly. We haven't had to worry about printing much, we just made web pages and people printed them if they wanted to. Things change with certain responsive websites. You have to almost treat pages as three separate layouts and designs. You have desktop (full web but on a bigger screen), mobile (phones or tablets), and then print. You have to address all three. That adds a challenge, especially with thousands of pages.

Towards the end of the meeting, John and I were talking about graphical homepages and some of our ideas and goals there. I told John that we had been dreaming about graphical homepages for years. We would love to add in a consistent look and feel, graphs, charts, and other eye candy stuff. Just really make it fun and pop. It feels like the time is coming. As a funny or silly side note, John and I were talking about how we have been virtually hiding for years, building, beefing things up, and doing tons of prep work. It's time to flip the switch and start showing what we can do. Hopefully all the prep will pay off and we can stay ahead of the curve (demand and scaling efforts).

John and I were looking into a possible bank transfer bug with Cory. We found it, but we are not sure that it is a bug. It may be that the user is using it to do something that it wasn't designed to do. That happens more than we know. We then did a critique and review of some of John's new look and feel pages. All in all, I'd say that it is looking good. We talked about how much scrolling is needed and maybe adding in a quick summary section to help get people to the meat of the page as quick as possible.

John is going to be pushing up a number of branches of code here later today. All of them are dealing with deposits, banks, and expense/receipts. After that, we rolled over and started talking about levels of mobile responsive design stuff. We want to get what we can this round, but we also know that we may have to circle back around and pick up that piece at a later date.

Brandon is going to be checking out the parked or other domain names that need to point to adilas.biz. We have like 30+ different domains that point to the main adilas.biz site. Wayne was on the meeting but feeling kinda sick. He will keep working on his tasks that are already assigned. At the end of the meeting, John and I were talking about controlling the printing to make that look good. Sometimes you think that you can just design something and it will work awesome for desktop, mobile, and print. Sadly, not always true. Depending, sometimes you have to design and have code in place for all three versions (desktop, mobile, and print).

Cory and I were working on projects and project management stuff. Shari O. was reporting on the new payroll rules for the state of Colorado. We spent some time talking about the new payroll settings and how to help them handle things. We talked about both fixed values and dynamic values. These new payroll settings will end up being a new project for Bryan and John.

Next, we checked on some custom data for a client. We figured out a few things and sent them an email asking which way that wanted us to fix the data. After that, Shari O. and I got on and did a small session on graphics and editing PDF's. She may need some Adobe Creative Cloud tools to help her out. She it trying to modify existing welcome packets and what not.

Cory and I looking into an inventory disconnect. She was calling it a ghost cost out in inventory. It had a similar feeling to a project that we would like to call internal cost corrections (ICC). Anyways, the error ended up being that the company had duplicate vendors and the code was grouping things based on the vendor's name, thus creating a missing vendor and its data.

The fix is to make sure that the vendors don't have duplicates or redo the code and make it loop over vendor id's vs vendor names. The id's would always be unique. Anyways, we talked about work arounds and ways to fix the data and get the vendors and items fixed and merged together. There already exists a tool for that, we just have to talk the client into to using it.

John was reporting on some new updates on the department homepage. Eric, Cory, and I were looking at gift cards and scenarios with different settings. We had an internal email bug reported to us and we started looking into it. John was the lead and doing most of the debugging today. Bryan joined us as we were checking things out. Sort of a grouped effort. We spent quite a bit of time looking at the email stuff. We pushed up some new code and John will get with Wayne later today to finish things up. We did what we could for current time. It will need more attention later.

Meeting with Cory to go over projects. We talked about the pick ticket stuff with elements of time. Checking on different errors. Auto emails for PDF attachments for invoices. Going over new date-pickers. Reviewing other projects. Talking about transitional invoices and reserving inventory. Mini conversion and laying claims on certain inventory items. Deep production and manufacturing type stuff.

We also got into talks about backorders, cross-corp invoice to PO stuff, and some new sub barcode requirements and settings. After that, John and I spent some time and talked about Adobe XD files and documentation for certain projects. We also talked about some Docker (server) stuff.

Cory and I going over multiple projects. More things are leading to settings. One of the projects was an auto bulk sort on invoice line items by part category. They add the items to the cart as they need to. Then after the fact, they need the invoice line items sorted differently for easier fulfillment. Once again, this would be a setting. Not everybody wants this.

On a different project, we talked about using the external alternate id field to hold special outside id numbers. This option already exits, just some people haven't used it and/or don't know about it. Technically, each of the 12 main players have a field already in the database tables called external alternate id that is setup for external id numbers or tracking purposes. One of the clients may have a special need for us to help generate and store some longer external id numbers (including special formulas and custom build out for functionality).

Props to Cory! She is really learning and growing as a project coordinator. She has a lot of traffic control and directing traffic (requests, quotes, bids, projects, promises, billing, scheduling, budgets, etc.). I've been impressed. She is doing great!

Both Steve and Cory did some planning and scheduling of things. Crazy times, right now. Things (all kinds of stuff) are going on all around us. Cory and I then jumped in and checked on some new logging and backend (hidden) histories and update logs. We were also talking about some advanced shipping options for a client. We could build out some crazy API socket stuff, do custom code, or maybe help them with a small workaround using my cart favorite buttons and custom shipping to known (repeat) areas. This is for a manufacturing company that distributes to the same customers over and over again. Anyways, we also discussed our internal deliver options and maybe building that out a bit more or connecting to outside 3rd party solutions as needed. Other project management stuff.

2/15/23 Edit pages:

- top_secret/secure/statement_home.cfm

- top_secret/secure/add_edit_statement.cfm - step 2 - select statement date range (2 of them)

- top_secret/secure/add_edit_statement.cfm - step 3 - set the dates (4 of them)

- top_secret/secure/bulk_receipt_verify.cfm - top form and looping over the results

- top_secret/secure/bulk_deposit_verify.cfm - top form and looping over the results

1/26 check and pushed final pages with Brandon.  Basic project complete.

1/23/23 checked and pushed 600 pages with Brandon.

1/18/23 checked and pushed 300 pages with Brandon.

1/13/23 updated more datepicker code on pages.

12/21/22 updated more datepicker code on pages (see below). Will connect with Dustin on testing:

12/6/22 Consolidated the Time code that Brandon and Charles did, and met with Brandon to check the code.  Two news and update pages have already been created for this project "Elements of Time Homepage Will Have a New Look" and  "New Look for Working With Time". Next we plan to have Wayne point the data 5 server to the branch (project-2260combine) so that the code can be tested on data 5. 12/5/22 met with Brandon on what we wanted to do with time:

    Date picker:

1. We want:
2. 1. put in 1/1/2 (characters)
3. 2. get 1999 when we put in 99 (not 2099)
4. 3. truncate correctly: 1999 goes to 1999 not 19
5. 4. if I supply a date in the past on the first click I want to go to that first (not how it is currently functioning going to todays date).
6. 5. create documentation in help file and in Adilas docs (update).
7. 6. update to all datetime instances. Check for date validation and go backwards (if I am validating a date I am putting a date in). (search for 'datepicker', '_date', 'date_', '
8. from_date', 'to_date', -form fields are what we are mostly looking for)
9. 7. on the times be able to put in a one digit (1 PM not 1:00 PM)
10. 8. put the datepicker on the content server.
11. 9. roll it out in small batches (10 or so pages instead of all at once)
12. 10. leave Bear100 code alone.
13. 11. communicate with Cory and John.

12/2/22 Spoke with Cory and John about the project.  John said there is a bug with the new picker that needs to be resolved. He said there is some information in the Adilas Docs that may be helpful (Adilas Docs>hamburger link>Adilas Core>components (top links)>date picker (left side dropdown, 'here' link - If you need more information on flatpickr for some reason you can find the documention for the plug-in here ).

Next, all of the datepickers in the system need to be updated to the new datepicker.  Brandon sent an email regarding what needs to be done to update all of the datepickers as follows:

 I found a page that shows some simple date picker stuff. Here is the page: top_secret/secure/add_bulk_flex_grid.cfm – if you search for “picker” it will take you to the different options that are needed. Here is a quick rundown.

• 1st include is set right before the include for basic_css.cfm it looks like this:

 

 

• Then any new date field will need the date-picker class. For example:

 

        on input fields --- the key is the class=”date-picker” part or css class stuff

 

• The last include is set right before the ending body tag. It looks like this:

 

Anyways, there are 3 basic parts… the top include, the new class on form fields, and the bottom include. This is true for any page that is a full page (no black box options). If it does have black box options, it is slightly different. Anyways, just wanted to get you some information. I don’t have a list of files right now, but we want to spread it (the new date picker) across the whole site. If you want, we can meet and build a list or if you want to poke around and fix things, that would be great as well.

The only page that I know we don’t want the new date pickers on is some of the bear 100 custom files. They get dates entered in via special formats and the date picker screws things up. Everything else needs to be updated (to my knowledge).

Project management stuff. Cory and Steve were going over projects, custom labels, and progress in those areas. We jumped into talking about server issues, email issues, and where are we heading. That lead to a conversation about the lack of education and training. Things keep changing so fast, it makes it hard to keep on education and training aspects of the system.

All three of us started talking about permissions and new permissions. We have a need to help secure up or tighten up who has access to certain settings. We decided that we needed a new master page level setting to help control those page settings. As we talked, we decided that eventually, we may need other settings or be able to assign sub permissions to a user based on their higher up settings. Similar to what we do with the manager's time clock settings. It has to be turned on and then we have a whole other page where an administrator turns on certain departments for the manager. We can see the need for similar type things in a settings admin or master settings mode. Basically, a person gets a main permission (part of the permission list) and then we/they configure what underlying access the users get. This becomes somewhat nested, but really opens up options and granular control of who has access to what and who can do certain things but not do other things. More ways the system is breaking or fracturing into subs or smaller and smaller controllable pieces.

We are getting really close on the gift card stuff for the system. Making plans and trying to see if we can push that new feature out before Thanksgiving. We have wanted this for years and years now. It's kinda fun that it is almost there and within a couple of days of being fully launched.

Training session between Russell and Brandon. We met over a Zoom meeting and talked about all kinds of project management styles and techniques. Russell was showing me stuff on his Notion app, how he organizes things, and all of the cool drag and drop type styles for his to do lists and project boards. Lots of linking back and forth and dynamics. We talked about IT structures and how to best manage teams. We talked about scrum, agile, sprint (if you know what to do) and kanban (one project at a time from start to finish).

It comes down to what are your resources, timelines, and talent pool. Do you know what you want to get done or is it more open? The dev team does the story points. Not everybody can do virtual (meaning the work environment). Some people really need some handholding and someone to watch over them. Those are harder to manage virtually. The virtual guys/gals need to be somewhat self-driven and self-motivated. Are the developers full stack (able to do the whole thing - start to finish) or are they limited and/or specialized (just a few of the tasks are suitable for them)? Lots of questions and different styles.

One thing that I was shocked with was how many different tools Russell has to use to keep all of his things going and flowing. Tons of different software and web apps like: Jira, notion, Git, Toggle, Google Drive, all of their internals, and tons of others. We do some of that as well, but Russell had a bunch more. Just me speaking, but no thank you. I've got plenty plus a few.

We flipped back to talking about sprints and getting into a grove. Other topics included owning a task and that is just the starting point, a task is never the end all be all. Helping to share understanding. Also getting help and helping to complete certain tasks. Somewhat of a shared workload vs just owning a certain task and being done with it.

People see things differently. Kinda like the telephone game, what you hear and pass on may not be the actual thing that you are trying to do and/or achieve. It is more of a process of growing and becoming vs just being or having (all at once).

Russell was sharing some of the stuff that he goes over with his guys in the interview process. His interviews are like 3.5 hours long and pretty brutal, testing all kinds of different levels and personality type stuff. We talked about documentation. Other things like dependency injection and how testable are things with dynamics vs hardcoded or static values. We got into testing, mocking data, logic test, integration test, etc. It got pretty deep. Russell is trying to mix all kinds of data and tools to get the testing coverage that he wants. He was even getting numbers and test results (scores) back on some of his processes. He was then using those scores to keep refining until he had less crappy code and in theory, better results.

Spent some time talking about breaking things up into smaller pieces. Using flow charts, wireframes, and other schematic type design tools to show the overview of what the functions and/or processes do or could do. I liked that. He had some new big words for me - I didn't fully understand them. Just being silly, but one of the things he was talking about was "Cyclomatic Complexity" and other things. I thought that it was kinda funny and it made me laugh. I kept thinking, if I don't know that... how am I supposed to teach that or expect it from my guys. Just having fun. I did grab a few screenshots with some of his memes and graphics. See attached. Nothing too special.

Work session between Brandon, Shari O., and Bryan. The goal was to do some training on the settings for online client facing scheduling and the new ecommerce settings that Bryan has been working on. We recorded a good part of the meeting. Shari O. has the video recording. If I were sum it up, I would say, it all comes down to the setup (planning and then executing that plan). See attached for a small Word document that we were working on to help us with reminders. If I can get the video from Shari O., I'll add it here.

Cory and I going over projects. Talking about a custom data export and the amount of data that will be exported. We talked about reaching out to our clients and trying to help them with their needs and possible pain points. As we kept going, one of the projects that we talked about was a request for documentation for the adilas API sockets (public access). I sent Cory three links that have some good info on the adilas API sockets. I'll list them below. The last topic was dealing with different parties and companies trying to control certain space or certain aspects of a business. Talked about some pros and cons there.

Here are the API socket documentation links:
- adilas API socket homepage and visual testing tool
- adilas API socket samples and documentation
- adilas API socket help file

Good conversation between Steve, Sean, Cory, and Brandon. We were going over ideas for sales, eye candy, graphs, charts, and system-wide aggregates. Here are some of our notes:

- We would like to create a MVP - minimal viable plan (product, person, whatever) - focusing on the plan part of it for fracture (future adilas project).

- Brandon pitched the value add-on core model with 5 levels – 1. Internal core (transactions), 2. Industry specific skins and functionality, 3. Custom code, 4. BI – Business Intelligence (aggregates), and 5. Enterprise level (multi corps and multi worlds). Part of our upcomming plan is to work on level 4 - BI or business intelligence (eye candy, graphs, charts, stats, counts, totals, etc.). Make it look good and be quick and easy to get to. Bury the transactional core a couple levels deep, so it is still there, just feeding quick information off of the upper levels (aggregates) vs all of the transactional pieces and records.

- We really want to work on the look and feel of the cart - less is more on the display on the cart

- For graphs and charts, we could use cfchart (code tags) or JSCharts (javascript charts).

- The reports homepage could use some loving

- Surface stuff to help with demos and sales

- Capture the daily, location, and category levels – basically, per day, per location, and per category (on the P&L and BS). As a note, we already have this info... we just need to grab and hold it. Also, we could go backwards on this one... there is already something that exists. We could pull it all in going backwards. There is already a path and a pattern.

- ETL – extract, transform, and load – this is how you get the aggregates = Brandon would be happy to build in this aggregate table or whatever -Steve would like us to talk and work with Eric about the backend triggers and deeper database stuff.

- Lots of talk about database triggers vs smaller microservices - pros, cons, visible, not visible, who has permissions, and best practices.

- We need to remember the API sockets and other ways of getting data both in and out. This needs to be part of our process.

- We tend to get pulled off of a project due to custom code, customer requests, and budgets (time, money, resources).

Cory jumped on the meeting. She had some questions about servers and new changes. If everything goes smooth, she is really happy. If it has any hiccups or goes badly, she seems to get the brunt of the deal. That's no fun. Anyways, she is just being cautious and trying to make sure that new development and deployment goes as smooth as possible. I'm really grateful for that.

She was going through emails and going through a virtual to do list. We touched base on projects, new permissions, verbage changes, and small possible bugs. We also went over some new and upcoming news and updates as well as techy talk for deeper how to's. Other topics that we went over were internal scheduling settings, client data export (custom work), and looking at sales reports and associated drill-down links - trying to make sure that everything matched up and we were getting consistent data back.

Both Cory and Steve were on the meeting. Cory was going over things with me and Steve would chime in when asked about certain projects. He was working on custom label stuff behind the scenes. We were talking about numerous projects. Coordinating flow on the Herbo server for what is up for testing and when that code (branch) would be available and being tracked. As a fun side note, some of the bigger projects that have been out for a while are getting done. It's creating a small traffic jam for testing and deployment.

Cory has a new project for an anti-permission (negative permission). This will be a permission that only allows the adding of a new invoice. No bulk look-ups, reports, or edit capabilities. Talking about pros, cons, and details of that permission project. It will be on my development ticket in a couple of days.

Thumbs up to Cory, she is doing great and coordinating projects between Steve and I and who is going to do what. That is much needed sometimes. More talk about settings and permissions. We also talked about prepping for possible rollback while or after testing, if we needed to. Basically, being ready in case we had to rollback code quickly. This is not something that we do all the time, but it depends on the project and what it touches and/or affects.

Cory and I going over different projects. We talked about 710 Labs, Hoodie Analytics, and copying chart of accounts between different corporations. We got into a small working session and looked at some live scenarios transferring the chart of accounts between accounts. As part of this work session, we talked about deep mappings and maintaining relationships. We had to work backwards from what we wanted to what we have.

We talked about deferring to people with more knowledge. That is huge and a great way to get things done. We spent the rest of the time following a small bug and talking about what might be needed. It was dealing with daily sales and invoices that were paid or not paid.

Sean, Steve, Bryan, Cory, and I talking about reaching out to a client, here in the Logan/Smithfield, UT, area. Talking about what we can offer and who is going to do what. We also were talking about options for mobile payments and getting some new hardware configured for demos and testing.

After all of the others left, it was just Cory and I left on the meeting. I was reporting to her about the conference and things that I learned. Going over projects and talking about a huge upcoming custom data export for a client that has tons of data (lots of CRM stuff). They have flex grid, additional contacts, customers, log notes, and tons of media/content. They would like an export of all of that data. That's going to be a big custom project. Lots of one-to-many relationships. We are also storing close to 500GB of data for them. That could make it interesting.

Cory and I looked at the schedule and booked some time to work with John on finishing up the discount engine project and get all of the backend stuff all wired up. After that, we spent some time talking about value and the value of clean data. That is huge. We went over a number of other projects for Bryan, Eric, Chuck, and John. Our goal is to break things down into smaller and smaller pieces.

Talking about automating aggregates and getting that data to start surfacing and being spread around the site. That is a big goal of mine, for the coming months/years. I want to get it out to the business intelligence levels (BI).

Other topics that we covered were dealing with database triggers, email servers, building in a cost plus - mark-up system, lifespan of software and systems, and other known and upcoming projects.

10/10/22 checked and pushed code with Brandon.

Code edited:

classic/view_cart_body.cfm

classic/view_cart_bottom.cfm

secure/custom_cart_5.cfm

Client paying for modal and settings to allow view of sub attributes when not enough stock is available upon adding to the cart or flipping a transitional invoice to a customer invoice.

Meeting with Cory to go over projects. Cory was asking all kinds of questions from her little list and from email chains that have been going back and forth between herself and our clients. We then moved on to some new projects and getting numbers, estimates, and quotes. One of them, a client wants a bunch of data out of the system. As we talked about it, they are wanting huge one-to-many relationships exported into a CSV file (comma separated values). We spent some time and talked about relationships and where CSV files work great and where JSON (JavaScript Object Notation) files work much better, especially if you have multiple deeper or more complex relationships.

We spent some time talking about the client facing scheduling and where we are heading. We have determined that we will end up with three different types (for now). The three types will be listed below. The main variables that we are watching for and tracking are: What is the date or date/time combo (when)? What product are they wanting (in case there are multiple options - what)? And how many people are participating (quantity, seats, participants)? Those are are three main variables we are watching - when, what, how many.

Plans for different types of online bookings:

1. Daily/weekly reoccurring with multiple participants. This deals with known and pre-set dates and times. We already have the rough schedule and just need to see who will be participating in each preset event. This is a normal one-to-many relationship with time being the one and the participants being the many. For example: like a shuttle service or ongoing event - pretend that we are going to offer a shuttle from point A to point B twice a day. We can hold 35 people per trip. This is a perfect example of the daily/weekly reoccurring with multiple participants. Think of selling seats or counts per event.

2. The next one is very similar but instead of being a daily/weekly reoccurring event, it is more of a special event or unique event. This will still allow for the same one-to-many relationships, but the dates are not as constant. That factor, the frequency of the date/times makes each event be unique. For example: Say you had one trip to a certain destination with multiple people going on the special trip or something like that. Because we have already plowed the path for the reoccurring one-to-many (listed above), this one should be pretty easy. Think of booking seats or counts for a special event (non-reoccurring or reoccurring but with special date/times).

3. The third option for scheduling time will be the one-to-one relationship. This is more of an open calendar and setting up what time slots are available. For example: Say a person wanting to schedule an appointment or get a haircut. The company or users would setup a basic template of allowed time slots and then allow for those time slots to be filled. The one-to-one relationship comes with one element of time holding info for a single client or customer. Basically, the quantity is assumed at one. This type of online scheduling could be used for campgrounds, doctor's offices, hair or nail salons, consulting services, etc.

After we discussed these options, in some detail, we talked about settings, next steps, and plans. Good meeting.

Cory and I were touching base and checking in on a number of different projects. Talking about working through failures. Lot of talks about permissions, settings, and sub permissions or sub functions within the bigger permission. It gets deep or could get deep. Some people don't care a lick. Others want to control things at the smallest granular levels. Interesting, how different people's agendas are.

We also got into settings and sub settings. More quotes on new and upcoming projects. Planning and figuring out next steps on existing projects. Small update from John on his discount engine code.

Started out with Cory and I going over projects. We touched base on multiple projects. We even spent some time going over existing code and how it worked and functioned (logic questions on customer terms and invoice due dates). We talked quite a bit about merchant processing and both existing options and future development options.

Cory wanted us to look into some code on one of the homepages that showed the top 15 customer/clients based on invoice counts. We looked for a good while but didn't see anything. I took some notes down and wrote them in my digital scratch file. We may have to circle back on that one.

After Cory left, I stayed on the meeting for a bit. I ended up calling the bank and requesting that our daily limit for expenses on our bank card get permanently increased to handle some of our expenses to the hosting company that we use. We spend thousands and thousands a month on hosting fees. Lastly, Chuck and I jumped on the GoToMeeting and I helped him out with a small bug fix on his local development environment. Busy morning!

Cory had a list of questions and things that she wanted to go over. She asked about how the top 15 customers were figured out on the some of the dispensary homepages. We went into the code and looked around. We went over invoice due dates, how to allow customer/client terms to show up on invoices, and other projects.

The next major topic was parent attributes and parent attribute sorts. We talked a lot about reworking all of the sub inventory pages and our virtual wish list with regards to sub inventory and parent attributes. It is super flexible and very needed. It currently works but could use some enhancements, polishing, and refinement. Never ending process.

Along those line, there has been requests for better bulk tools for both parent attributes and sub attributes, better reports and advanced searches, and ways to speed things up and make it even smoother.

Cory and I went over some quotes and talking about the need for better project management for our internal projects. We are really good at doing just in time project management but some of our project really need some more base level requirement and expectations out of the gates. Sometimes we hand our developers a simple one liner and then they take off. They just need a little bit more instruction and direction in writing vs just talking and verbal. If good notes weren't taken, things fall through the cracks.

Meeting with Bryan and going over the flex grid tie-in portion of chaining elements of time and flex grid assignments together. This is how we are virtually claiming seats or availability on the bike shuttle project. After the meeting, I finished up some code to help do a bulk update of the budget numbers that were tied to the flex grid record counts. Currently, this file is not part of the master branch but Brandon has it on his computer, if ever needed again.

Steve and Cory were talking about looking up projects in bit bucket (code repository stuff). Being able to check on commits and branches. They were then talking about different industries and how they are financing some of their developments. Lots of games that people play and how do we fit into that mix. While Steve was still on with us, Cory was reporting in on some meetings that she had had with Kelly dealing with the adilas label builder and sub inventory attributes. Both of those subjects seem to be heating up a bit.

Our current goal is to focus and try to get some small victories (projects being done and across the finish line). Cory and I spent some time going over projects. We talked about the need to test everything. Even small stuff. We have had it bite us before. Next, Cory and I looked into a possible bug in some settings. We looked and looked and couldn't see anything quickly. We may have to jump in deeper, when we get a chance.

Shari O. popped in and had some questions about getting a new internal email server. Our current solution has been giving us some problems lately. We don't change any code on our side and it works great, all of the sudden it will be down, and without any changes on our side, it all of the sudden starts working again. Kinda crazy. Shari O. calls it the gremlins or email gremlins. As a side note, later in the meeting she popped back in to let us know that it was working again. Random.

Wayne joined the meeting and got Cory and I up to speed on a few things that he is trying to work on. Performance tweaks.

Cory and I then started going over her list of possible projects, quotes, and estimates.

- Need quotes for inputting sub attribute data all at one time upon PO creation (start with build page)
- Bulk update sub attributes interface
- Mapping of EOT (elements of time) data to sub attributes (settings for cultivation and manufacturing)

Along the way, we were talking about options and settings that relate to the concepts of the data assembly line, recipe/builds, showing subs in the packaging and production pages, and managing recipe/build output better. Lot of talk about bulk edit tools for sub inventory attributes, batches, phasing, sub locations, and moving subs along a known path or virtual assembly line.

Dealing with the data assembly line concepts, I was telling Cory how we setup both rules and assignments for smart group buttons (tiered pricing buttons). I was mentioning that we could use something similar to help setup and do the mapping between elements of time, sub phases, sub locations, sub groups, and monitoring the progress of certain things. We need the rules (what or how to do things) and the assignments (who or what to connect or monitor). Using the two pieces in combo (rules and assignments) we could then have the computer and/or system help us monitor progression and progress. They are good at that, they just need instructions and the who, what, when, how, and why and they can do those jobs over and over again.

As we keep rolling more and more towards the concept of fracture (future adilas project) I would really like to keep working on the data assembly line concepts and using rules and assignments to get the correct flow and mapping in place. I see that as important as we keep going forward.

Meeting with Chuck and going over layout and display options for the "working with time" page (part of the elements of time section). That page has tons of dynamics and was built as a mini prototype for what we want fracture to do and be. Basically, the page uses templates and then either hides, shows, uses dynamic naming, aliases, incorporates settings, permissions, and even eventually sort order and display order. This "working with time" page was built in 2011 but has pieces that we want to do and use throughout the whole system once we move to the fracture level. Ask Brandon for more info on the subject.

Chuck and I were going over design options. We brought up the current page in a simple mode, a medium mode (settings and data), and then in an advanced mode (more settings, more data, and more dynamics). We were drawing pictures and running things through fake mock-up ideas. The page has to be able to handle all of the different possible combinations of settings, templates, defaults, subs of time, flex grid tie-ins, and other dynamics. Each section will end up being in a container of sorts to help with web ready responsive design (mobile friendly). Lots of talk about nav, standards, and where we are heading. The other major variable is how much data is tied to a single element of time. It is just a quick virtual post-it note, an appointment, a project, a timecard, a vacation booking, or clear down to a dispatch level event? Elements of time are very diverse. The amount of data could be huge or super small per element of time, based on the template and the settings and the amounts of sub info or subs attached to the main element of time.

At the end of the meeting (last 10 minutes) we flipped and talked about a small bug that was found and reported to Chuck and also his new promo video for the adilas label builder.

Steve and Cory were talking about pages, packages, and sub inventory. Shari O. popped in and we ended up having some light budget talks. The four of us talked briefly about the state of adilas and where we are going. Lots of good things going but we do need to be careful. On a different note, many things are changing all around us - including code changes, settings, clients, needs, expectations, etc. It's a moving target.

Light talk about what is an MVP (minimal viable product) for what we are doing? Even though we have so much functionality, do we have all of the required pieces? There are still some things that we need, even for an MVP - although it be a large MVP.

Cory was asking questions about projects and what not.

Cory and I going over projects. We talked about custom uploads for bulk expenses, referral tracking (promotion codes), merchant processing (working with the Datacap company), and automating emails. We also got into some talks about SMS and phone stuff. Basically, companies are wanting more and more communication options and even extending that out into marketing realms. Lots of requests and wishes for tools along those communications and marketing channels. We also talked about 3rd party solutions, pros and cons, and doing our own internal enhancements.

Talking with Cory about tips and how to handle that scenario. We talked about just running the payments higher and then dealing with the tip (negative cash out). We looked at it all the way through to the P&L and balance sheet. That seems to be the best way to do it.

Back on the custom label builder app. We are going through things and making plans. We are wanting to do more mock-ups on the label builder and then pitch those to the client who may want to fund things. Talking a lot about flow, promises, and pitching the pitch. More plans and then physically looking a the code. We didn't get all the way through it but making progress. We fixed some session scope locking issues.

At the end of the meeting, we spent some time and were going over some other projects and touching base on things.

Meeting and going over projects, updates, follow-ups, and small quotes. Kelly had made a request to up the size of the additional customer contact notes. Cory was doing other things and I busted it out while we were on the meeting. We had to do a database update, check validation, make a few layout changes, test, merge, and update a help file. We got it all tested and pushed up to all servers.

Working with Cory on projects. Our main goal was to get back to the review of the adilas custom label builder. We spent the first few minutes going over other small issues and errors. Once that was done, we rolled back into our review of the label builder. We took a ton of new notes. We also came up with the idea of making a custom label homepage, where everything could be based out of. That was a huge step that was missing and really helped to springboard our conversations.

See attached for our notes. Also, towards the end of the session, we started into making some quick mock-ups. Originally it was just to show Cory how you could do it... not necessarily professional level stuff. As we got deeper into it, we decided to save it. They are very rough, but we are making progress. Not production level, but making headway. See attached for those images as well. Just for fun.

Small work session with Cory to go over the customer label builder app. This was session number two (of many). Lots of note taking, watching, trying things, and making notes. Towards the end of the session, we went back and read through some of our notes and started to organize topics and sections. It still needs some work but making progress. Pushed up new notes file on element of time # 1455 in the main adilas site. Good work session.

Cory and I going over projects and doing small quotes. We talked quite a bit about settings and different levels of settings (at least 4 known levels - corp, group, page, and user levels). Sometimes adilas is so diverse that we either forget about certain functionality or we never knew that it already did something. It's a blessing and curse - at the same time.

Lots of new smaller projects and some that are more around the $2K to $10K level (medium sized). We spent quite a bit of time talking about options for push notification. Lots of our time was spent talking about a super small mini app that could be installed on mobile devices (apple and android phones). The little mini app would just check for things and let the person know (notifications). Then the user would have to either click or login to the ecommerce page or client portal section. Super simple with minimal functionality. Just use the mini app as a communication channel. All of the rest of the activity would run over existing pieces. Anyways, just going over ideas, options, and drawing out possible solutions. Light brainstorming session.

John popped in towards the end. He and Cory chatted for a bit.

Work session on Calvin's custom label builder. I took a bunch of notes. Cory and I were doing a virtual tool beat-up drill and pushing on the adilas label builder - prototype. John was in the background working on his own projects. At the end, he and I talked a little bit about the code and what kind of backend needs will come into play as we dive in deeper on this project. We have spent over $20,000 on this project but it still needs a little bit more. Trying to figure out what it does and what we want it to do. Good session.

Meeting with Cory. We were talking about projects for Eric. We also want to get back to Calvin's label builder (review and make a plan). Other tech support stuff.

Long meeting between Steve, Cory, and I. Cory was reporting on tons of different projects and getting our input and suggestions. We covered tons of different topics. Here are some of my notes (from 10 pages of post-it notes - didn't know it/we would cover so much). The original meeting was only setup for an hour. It went a wee bit over... :)

- Talking about tons of custom label options. More talks about what to do with Calvin's custom label builder. We've spent a lot of money there and want to really get a return on that investment.

- We talked about bringing projects more internally with our guys and breaking things into smaller and smaller pieces.

- On labels, we had a request to be able to do serialized labels (up or modify counts and counters based on batches or packages).

- Using tons of our existing tools and refining those pieces. We have a ton of tools in the shed (virtually).

- Lots and lots of talks about breaking up the bigger projects into multiple smaller pieces. Along with that, we need to be able to charge money for bigger estimates. Everything takes time and effort. Either that or be able to recoup the amount within the bid or estimate.

- If we are doing real custom work, we need to charge for that. Often, we end up taking a hit.

- The trend seems to be (globally) transactions and details going into aggregates and summaries. We have had so many 3rd party analytical companies wanting to use our API sockets to harvest and use our great data sets. We would like to do a bunch of that analytical work inhouse vs farming it out to a 3rd party. All of these 3rd parties are just working for individual companies, but you can see the trend happening. Our clients are really wanting to get to the business intelligence level (BI) for viewing their data, snapshots, counts, summaries, and other aggregated data or stats.

- We went over some pros and cons of using the adilas API sockets. Back and forth on monetizing those channels and also making sure that they don't get abused or flooded.

- Lots of talks about the item catalog and the image catalog. As we use more and more API sockets, we could really use bigger and bigger bulk tools to help with data standardization and speed of deployment. Lots of positives. We, as a company, could also sell more systems if we brought in the enterprise level (way up - cascading info down to lower systems). Good stuff.

- More bulk standard tools. This just adds to the votes for building out the value add-on core model with different levels. Just as a recap - the value add-on core model deals with 5 known levels. They are: 1. Transaction core (current adilas system), 2. Industry specific skin, tools, and features. 3. Any custom code on top of the main system. 4. BI - Business Intelligence levels (stats, sums, counts, averages, mins, maxes, aggregates), and 5. Enterprise levels - connecting multiple worlds in a hierarchical type system (roll ups, roll downs, transaction corps/worlds, aggregates and sum corps/worlds - also dealing with permissions and access). We really want this type of a system for our future fracture project. We already have a number of pieces to this project (all kinds of prototypes spread all around the system), it just isn't all put together. That would be so awesome, clean, powerful, and hopefully pretty!

- We spent some time talking about our clients. Sometimes they get pretty creative. That is both good and bad. If they get creative, and find errors or break things, we just fix them and keep going. Other times, they totally use certain tools in ways we never would have imagined and/or foreseen. That can get interesting.

- There have been some requests for bulk tools for updating sub attributes and bulk sub inventory tools.

- Cory kept asking - Who are we? We tend to build generally but then we have all of these industry specific demands that keep coming at us. It makes it really hard to know where to focus. We really need to decide who we are and then hopefully that or those choices will help guide us.

- Dealing with Metrc (state compliance systems), we've had the request to build out more individual user type functions. This is dealing with more employee/user type permissions and settings. Currently, most of our Metrc transactions are done on a corporation or world level. The new requests are to do the exact same things but break it down on a per person basis. That sounds awesome, but that could be hundreds of thousands of dollars in development. We would have to create the one-to-many relationship, make sure that they were valid, then sync up users and permissions between systems in order to play. Then, to further make it kinda crazy, you would have to check user permissions (remotely) then attempt the connection, then if it failed, figure out if there was a global (higher up) option that you could do so that it wouldn't break all of our code and processes. It could be a huge project. Lots of unknowns. As part of this project, we would also have to add more history tables, who did what, who changed what, who has permission to do what, and making sure that each individual keeps their keys and tokens updated. It sounds like a small nightmare.

- We seem to build in general and then use it specifically as needed. Custom code on top of our own standard package, tool, or feature.

- Going over the cost of building and building. One you have to build it, then you have to maintain it, and upgrade and support it. The costs keep increasing. This topic lead us back to questions about who are we and where should we be focusing?

- There is a growing need to use asynchronous type loading like AJAX or some way of breaking huge datasets into smaller pieces. It is totally common for us to need to show or export 10,000+ or even 100,000+ records at a time. The current process tries to take that whole thing as a single bite or single attempt. It's just too large and slows things down.

- Some time was spent talking about loyalty points and keeping track of the total liability. More talk about other reports that show sums, grouped values, look-back capable reports, and using ACV (actual cash value) for recording loyalty points. We do a bunch of that, just refining the process and making it even smoother.

- Need for messaging or using the message marketing features that we have already built. There is a growing need for push notification and two-way communications outside of the main app or website. The client portal is growing in needs and options. More mobile ready or full mobile pieces are going to be coming down the pipeline. Everything seems to be trending in that direction.

- Question - do we fill in the gaps on functionality or try to update the look and feel? It sure would be awesome if we could virtually turn things on/off based on the UI (user interface) and settings. We would love to set things up super simply and then let the users add on or take away from our smaller base level. A new mini version of the shopping cart is in great need of these fracture type level settings. Start small and simple and then let the users build on or configure things as needed. Hide anything that we can unless asked for. Then when it is done (using the tool or feature), it can be hidden again. Every page needs show/hide options on a per page or per section level. Totally customized.

- Along with the show/hide options talked about above, it would be so cool to show all of the options and then say - what do you want? You tell us. More fracture stuff (where we are headed). Mountains and iceberg analogy stuff (it still needs to be there, but what is shown and/or exposed).

- We talked about extra costs and prices for some of the other add-on tools and functions. Some of our stuff (tools and features) takes a major amount of work and effort. We would love to sell more training, consulting, automation, and other professional services.

- News and updates and the importance of keeping our users up to date and informed. This seems to be a constant need and keeps evolving. Content and making and creating new content (creation and maintenance).

- Lots of talks about prioritizing efforts for different persons (parties). Diving out responsibilities and sharing info across departments and across people (users).

- Using videos - the value of education and training. Selling our other services. Scheduling and setting up ongoing training efforts. We would love to make lots of polished smaller videos. Laying it all out for our clients (on demand education or just in time education). We could really use our website to toot our stuff for different business verticals. For example: Revamping our manufacturing site and pages. We can handle... (fill in the blank) for manufacturing or whatever. That is a deep pool (manufacturing and production type businesses). The trend seems to be leading us more in that direction.

Meeting with Cory. Talking about new settings and being able to get those new settings fully tested. We talked about getting some of our clients to help with some of the testing (things that they had asked for). We covered a number of other topics in our meeting as well. Here is a short list.

- Slow pages and how the inventory quantity/count snapshot (mini aggregate) should really help with some of those pages.

- Looking into possible negative loyalty points. We ended up finding that there was a gap between when we did a face lift on the add cart payment page and when the bug was reported. The actual bug got fixed very quickly, but there was a couple of months that it went undetected. The bug was not showing an error, but was not running the full validation on the loyalty payments and amounts. During that time period, the system would not run the validation routine on the submit cart buttons (either enable/disable) based on the logic. The bug happened due to us adding a new button, for connivence, but the underlying JavaScript would no longer work because there were two buttons now, both with the same name/id. All of the logic up to that point was fine, it was just the final check before submitting the cart that had broken. Anyways, there are ways of manually adjusting things, it is just unfortunate that the hole was open for so long. We will also be building a new report that shows sums per person to help find possible problems.

- Cory and I were talking about the change in the adilas corporation structure. We have been going more towards an MMLLC (multi member LLC). We talked about the options of having both the MMLLC and normal 1099ers and possible employer/employees. We may end up with a hybrid type model. Along with this topic, we were also discussing possible liabilities that may be coming, based on different scenarios and decisions. Some of the pieces of this topic can get very sticky and emotions can run deep (pros and cons - for and against - certain models and structures).

- We also spent some time talking about picking our battles and how to best help users, owners, clients, etc. - while still keeping things moving and within budgets.

Working with Cory on project management and going over a number of quotes for new projects. She had a big list of projects and client requests. We also spent some time and looked at a couple of small bugs, random things, and small fixes.

Meeting with Cory and going over projects, doing some quotes, and talking about small tech support issues. We looked into a duplicate permission issue on one of the servers. Cory was also reporting in on certain user requests and feedback that she has been getting. I'm glad that she is helping people and then passing along the info. Towards the end of the meeting, we were going over some budget type talks and stuff.

All four of the admin team were on the budget meeting. Good stuff. We flowed between topics and looked at banks, numbers, financials, and P&L (profit and loss statements). We did some budgeting, talked about current projects, and went over a number of other topics. Brandon was taking notes and sent those around via email after the meeting. As a side note, we are really going to be pitching our other professional services as that is a great way to add monies to the reoccurring model that we already use and play along with.

Cory and I were talking about projects and who was assigned to what. Small recap and checking in on different projects and small progress reports per project. After that, I worked on merging in some new code for Eric and the 2D barcode scanner code. I had to fix a merge conflict and then push new files up to all servers.

On with Steve and Cory talking about dynamic data fields and custom software development. Lots of needs for sub phases, sub locations, and data assembly line stuff. We need to know the data points, the flow, and the processes. That also means we need to know the pain points and other important pieces of the puzzle. Instead of guessing, we need real communication and a working knowledge of what they want their workflow to be like. Basically, where, when, and what to do or grab.

We talked about checks and balances, virtual stops, actual stops, and other critical data or checkpoints. More needs for that data assembly line type environment. As a follow-up, we will be looking at setting up some client meetings before we quote anything and/or make any promises.

Eric and Cory were talking about the inventory snapshot project. After that, Cory and I were looking into a small bug on the loyalty payments. Cory was asking for a progress report on the bike shuttle project. We booked some time to work on that the next couple of days. Too many other little things that pull us away from the bigger projects. We spent the rest of the time checking on other project and schedules.

Meeting with Steve and Cory to go over projects. We talked about a couple of projects for Eric. We talked about gift cards, other special account projects (in-store credit, vendor credits, punch cards, coupons, and gift certificates or gift cards). Another one is the mini aggregate project to handle inventory quantities per location. The other possible project for Eric is getting back to the enterprise item catalog project. All of those have value and would be great add-on's.

The next major subject was projects that Alan is either working on and could work on. He is one of our top developers and is in demand, because he can do so many things. One of the projects that Cory really wants him to work on is the transition invoices out in ecommerce land. They already exits out there, they just need a little bit of loving. He could also help Steve out with some BioTrack production stuff.

Lots of talk about other developers and what they are working on. It is a challenge to coordinate projects and developers. Lots of moving pieces. We also talked briefly about some projects for Bryan. We are still trying to help our clients transition from billing in the old independent way to dealing with Adilas as a team or an entity.

Another subject that came up was the number of hours spent in a training and tech support with our clients. It takes a lot of time and effort. One of the benefits is that we learn a lot along the way. The more we help our clients, the more we learn, and can adapt the tools and features that we have to get the desired outcome. Along those lines, sometimes we (internally) need to be reminded of certain processes and tools that exist that we may not remember or are new to us. For example, all of Steve's new backorder stuff that he developed and managing quotes, orders, PO's, and backorders.

Cory was kinda putting her virtual foot down on certain projects. We are trying to retain our clients but sometimes they get out of line. We talked about preventative maintenance type stuff with our existing clients and helping them along the way. We, as a company, are offering more and more internal service offerings. We used to sub it all out to outside independent sub-contractors. We are trying to make those same offerings, but do it all internally now and helping out in new ways. It makes for a better product and better retention.

Budget meeting with the admin crew. Steve wasn't able to make it, but Cory, Shari O. and I were there. We talked about the need for ice-down dates (per section) and how cool that would be. The ice down dates are part of our wish list for fracture (or whenever we can). It has been a goal and dream since 2008/2009 ish. Sometimes things take awhile to get back around to.

We went over budgets and did some calculations and look-ups to get actual values. We spent quite a bit of time talking about next projects for some of the guys. We also did a session dealing with naming conventions for expense types and how we want to classify thing on the P&L. This is mostly dealing with guaranteed payments and tracking how we are paying owners.

Part of the conversation went into some wish list items for Shari O. and ways that we could help her in accounts receivable (A/R's) and chasing down monies and payments. Brandon has both nots and spreadsheet documents from the meeting.

After the meeting was over, John jumped on and had some questions about timecards and timeclocks. We went over ideas, expectations, and where we are headed.

Dustin joined us and he and Cory were going over some live testing issues and the need to roll back a project. We did so and got it all merged back in and pushed back up to the servers. As a side note, they were talking about the cost of a bug. It takes extra tech support, causes stress, emergency development, code sign-off and re-deployment, and it frustrates our clients. There is always a cost for pushing up bugs.

This is just for fun, but Cory was saying - No pushing new code up on Friday! That's a bad idea.

Dustin and John left and just Cory and I were left on the meeting. We started going over a list of projects and questions that Cory had. We went over my cart favorite buttons and how they play with subs (child inventory). Next, we talked about 3rd party solutions and hardware.  They are both needed, but sometimes give us a black eye. We can't control those pieces very easily. We went over a question about active and inactive users, editing relationships, and possible solutions for resetting things and hiding inactive users. This already happens most times, but there are certain scenarios where both active and inactive users are needed. Say like a salesperson that is assigned to a customer. If an old assignment was put in place, they don't just automatically clear themselves if someone gets fired or made inactive. Those are still real relationships that need to be updated and reassigned. It can get tricky.

Cory and I going over a list of questions. About halfway through, Steve and Chuck joined us. I think that they were going to meet and work on some look and feel, but Cory and I were on the meeting. Anyways, the question got brought up about doing down payments on stock/units and how to book that and keep everything straight. The real answer is using transitional invoices. Having said that, we went round and round talking about possible options. Towards the end, Chuck was saying that when we redo our fracture stuff, we may need to make it part of the system that a prepaid invoice, deposit on merchandise, in-store credit, and other things be put in place and education and training made available.

For the record, here is how you would do it right now... using a transitional invoice.

1. Stock in the item, even if you don't have it in stock. If it is in stock, use that item. Anything that is unknown, just make a note of that. For example: a serial number or VIN number - maybe use the customer's phone number or email address.
2. Go to the stock/unit and go through the invoice/sale process. Make sure and set it to a transitional invoice (that wording is dynamic - layaway, prepaid, etc.).
3. Do the sale for the full amount and then take the amount that is either pre-paid or deposited. That will start the journey of the stock/unit and the payments received. All of these transactions will auto flow over to the balance sheet (already built-in) if using a transitional invoice.
4. Keep the invoice in the transitional state until it comes in, gets delivered, or whatever. If needed, additional payments (deposits on merchandise) may be made along the journey.
5. When ready, flip the transition invoice over to a real customer invoice and finish out the rest of the info. Once flipped, it will show up for sales taxes, on the P&L, accounts receivable (if money is still owed), and will count against inventory values. Prior to that, the whole thing is held on the balance sheet as the work in progress, pre-paid invoice, layaway, deposit on merchandise, etc. (dynamic naming).

Anyways, the takeaway is for fracture, we really want to have a way to show our people how to do certain tasks (searchable education mode). We also want to have some of the special account stuff like in-store credit, vendor credits, gift certificates, coupons, punch cards, etc. all done and part of the system. Those features may be built-in prior but need to be there. As a note, a lot of those will be sub sections of what we call special accounts, just like the current loyalty points stuff.

Cory jumped on with us. She had a few things to run past us. We briefly went over the pick ticket for manufacturing. Questions for Steve and I on different projects and we are at, progress wise. Cory was reporting on some client training that she was doing and the client was really getting it and very grateful. She was really excited and called it enjoyable training. If you have a good student/learner, it makes it fun and enjoyable.

Steve and Cory got into some of the gram controllers and settings. Steve was showing Cory some of the options, advanced techniques, and settings. He is even interconnecting different pages and settings. It does get deep, but if you know what it is doing, you can do some really cool things. As a take away, the real value comes with good training and good setup. The importance of good education.

As Steve and Cory were talking, there is a real value in having everything in one system. Less dead ends, less need to maintain duplicate lists of data (items, customers, vendors, etc.), less having to switch between systems. We were also talking about speed, automation, and quicker setups and getting our clients up and going with minimal effort.

Brandon, Steve, Kelly, Cory and Charles... if Brandon isn't working today we can record and ask any questions later.

Cory joined and Chuck was already on with me. We talked about going with components and trying to focus on a new single date picker vs a dual spanning or preset date one (all ideas from Chuck). We will just get the first one done first and then move on.

After Chuck left, just Cory and I were on the meeting. We switched gears and talked about API sockets (request from a client). We ended up doing some code stuff and took off some navigation links off of printable invoices and mini invoices. After that, I did a small demo on the High Valley Bike Shuttle stuff and where the bulk flex grid tools are at, in the development cycle. Cory is trying to keep track of where time is being spent, just for our records.

Small admin meeting with just Brandon, Steve, Cory, and Shair O. - going over the meeting we had with Bob and the rest of the team. Our next major step is getting things in place and doing some prep work before we take it to an attorney to get all of the verbage and wording correctly. Lots of good stuff and future options. Tons of potential and exciting things ahead. Just for fun - Steve said, "I feel like I'm on a big plateau, looking around, and don't see a fence in sight." Kinda fun!

Meeting with our CPA, Bob Hamby. We had 12 people on the meeting with us. Bob was speaking and answering questions, Stee was helping run the meeting, and I was recording notes and chiming in. After the meeting, we did have a small internal Q and A session, with those who were still on. Great participation. We did record the whole things as well. Brandon has a copy of this if needed. See attached for the notes.

Great team meeting. We had 12 of our team on the meeting. We did record it and Brandon has a copy of the recording. The whole meeting was dealing with the adilas.biz company restructure. We are moving from independent sub-contractors to partial owners within adilas. Cool stuff. The meeting went the whole 2 hours. I (Brandon) was mostly presenting and going over a small agenda. Lots of drawings and trying to pitch the pitch. We also had great participation from others on the meeting. I have attached the notes and the agenda from the meeting. Most of the first part of the meeting was talking about items on the Word document. See attached.

Both Steve and Cory were on the meeting. Touching base on projects. I gave an update on my projects and Steve gave us an update on his projects. Light budget talks. We talked about having to front load the initial setup, configuration, and any analysis of what is needed. We then got into client expectations and trying to get those expectations under control. Almost a conditional setup and need for education or step-by-step setup stuff. Ideally the goal is helping to automate things and coming up with wizards, handrails, and step-by-step setup processes.

Cory had some questions on MMLLC and percentage stuff. Checking on invoices and A/R's (account receivables) and getting payments. The subject switched over to pain and how that helps to lead and guide decisions. If we are calling ourselves a custom software solution and then charging accordingly. We need to play accordingly.

Spent the last 15-20 minutes paying bills and doing clean-up from the day.

On a meeting with Steve and Cory. Talking about projects for Eric. Steve will be meeting with him today to go over projects and ideas for ownership in the adilas multi member LLC corporation. Light report on what Dustin is working on. Cory had a list of questions, and we spent some time going over those pieces and questions. Looking into a part look-up problem for a client. The problem ended up being a huge part number (lots of alpha/numeric and special characters) and whether or not it was being URL encoded for certain actions or functions. That little fix will take some more time and we could end up flipping things to an id look-up vs using the text-based searches that exist right now. It's only for a certain method, but it gets used 20+ times.

Spent some time with John looking into deep nested loops and sub filtering data. This is on the discount engine project. Lots of string manipulation and escaping certain strings and characters. Once again, rouge and random client data. It is a challenge to allow flexibility and still keep a level of control on what a user can enter into certain fields, lists, and values. All part of the game.

Meeting with Cory, Steve, and I to go over budgets and corporate structure changes. Shari O. wasn't able to make the first part of the meeting so we recorded it. Brandon has the video footage at his house on his computer. We didn't want to post it as it contains some budget type info. Anyways, we went through the meeting and I was taking some notes, we were drawing and going through some scenarios. Shari O. was able to join us about half way through the meeting. I sent the meeting notes around after we finished. The meeting notes are mostly about the corporate structure changes that we are trying to make. See attached.

Cory and I jumped on and looked over a bunch of projects. John was still on and showed Cory progress on the state choices and new payroll messages. I took some time and showed Cory some of the features of the new copy select chart of accounts tool - copying things between corporations. We also looked at some upcoming projects. I'll be working on some verbage for refund policies, privacy policies, and other terms and conditions. We need to add these pieces to our ecommerce site. After that, my next major project will be planning out an MVP (minimal viable product) for client facing scheduling and booking.

Steve joined and he and Cory were going over a number of custom label and other projects. Steve and Cory were also talking about some merchant processing options. We have some required updates that are coming up and we don't have very many people using that feature. As a business decision, we may need to get with those folks and see if they are willing to transfer over to a different merchant account. The more you have, the more you have to maintain. We are looking to consolidate on some of those options and available features. Finally, we went over next steps for each of us and then bailed out to work on our own projects.

Cory has been on vacation for a week or so. She got back and a bunch of the folks on the morning meeting wanted to talk to her. She coordinated times to get back with Sean, Marisa, and John. After that we went over projects and progress reports. Lots of touching base on small happenings, projects, and updates. We decided to assign a few tasks to some of the developers who could help take things off of my plate.

We talked about state taxes, state payroll and withholdings. We have two new states that are needed. Sometimes, that takes time, research, and then ongoing maintenance (year after year). We talked about new clients and managing expectations. For our new clients, we need to figure out what they will be needing? We may need to pad the setup and activation fee to help with light customizations. Almost every client needs it, but they don't want to pay for that. We can't do it for free. We may need to add some of that flex coverage to the initial activation fee. Thinking about a fee of $1,500 for a brand new client and a smaller activation fee for existing clients that just need a new corporation or system. Something more like $500 vs $1,500 as we won't know what is really needed with a brand new client.

The last topic of the day was 3rd party solutions and some of the settings that we have and how they play in. Light talk about the API sockets and key connections that outside 3rd parties need to make. 

Follow-up with USAePay and getting more info on merchant processing stuff. On the phone with Steve talking about all kinds of stuff. Mostly about the multi member LLC and percentage ownership stuff. Steve and I were on the phone for well over an hour and a half. Here are some of my notes... all over the place.

- Trying to get our guys and gals to focus on one thing and getting it all the way finished. From top to bottom. We have a lot of stuff that feels 50-75% done. We want to get it all the way across the finish line. Our goal is to give them a single project so that they can get it all the way finished before moving on. We are hoping that if we extend them some ownership in the company that it will help to motivate them to play the game.

- Need for more news and updates. We also thought that it would be good to do some internal news and updates for our internal staff. That idea came from Steve.

- We need someone who is able to get into some deep JavaScript stuff and really help out there. We have a number of projects that are very heavy in that area and need some loving.

- We chatted about different developers and their skill levels. As a side note, the deeper we get, the more things start breaking down into smaller and smaller pieces. So many interweaving and interlocking pieces. Lots of dependencies and requirements.

- Kelly seems to follow trends very well. It's almost one of her skill sets. In the book, "Who Moved My Cheese", there are two mouse like characters. One is Sniff and the other is Scurry. Kelly seems to have those type of instincts.

- Divesting possible ownership and management options to an outside company. Just playing with options.

- For our internal team, we have been talking about a price of $1,000 per percent of adilas. That is about 1/100 of its actual value. On the open market, 1% would be somewhere between $50,000 to $100,000 at a $10 million dollar valuation.

- Steve was mentioning options for an operating company, a holding company, a management company, and maybe a retirement company. Just talking possible options, down the road.

- There seems to be a huge gap between sales and demos. If we get the demo and get to talk to people and show them what we have, we shine, and they want it. If we can't make it that far, it doesn't go very fast. Kinda interesting but logical.

- We are trying to stir the pot on the sales side of things. We talked about doing a sales sprint, daily sales standup meeting, and getting some of our guys really going and focused there. We really want to manage it properly as well. It is one thing to say go, it is another thing to have a plan, accountability, and be able to measure efforts. We really want to lean on the manage it properly type level.

- As far as sales and travel. We were talking that if they log their miles, we could pay $0.25 per mile. That covers gas and some light wear and tear on the vechiles. We would have them log those miles inside of adilas. Ideally, we would tie that into a general budget for what they are charging us or what we are budgeting for their help.

- We would like our salespeople to stay as local as possible so we don't burn up tons of travel costs. This is at least true for getting started out and getting things up and running.

- One of the goals would be to help the guys and gals be more accountable. Along with that, dealing with sales, we need them to log the contacts, touches, and daily standup meetings. Ideally, we want to record these notes as real-time as possible, while they are fresh in your minds.

- Sales is a game of numbers. The numbers should tell the story.

- I'm going to reach out to Shawn and get his instructions for his sales and contacts that need to be logged into adilas, in the CRM (customer relationship management) section of the site. See attached.

- Both Steve and Sean would be the main contacts for the sales guys. The main adilas morning meeting would have a small standup for sales everyday.

- For me, keep pushing out gift cards as we get them - perks for the guys and gals.

- Steve and I went over some percentages and who was going to be selling what percentages. We made a list on a spreadsheet. Our initial internal offering is going to be 5% from Steve and 5% from Brandon. These will be sales made to us as individuals - checks made out to Brandon or to Steve vs adilas llc. We will come up with a promissory note of sorts to document the sales of those percentages.

- There is huge value in getting in there, out there, doing it and learning from your mistakes and successes. We build and break, we build and break. Don't overthink it! Just keep going!

- When we present our offer to the guys and gals, Steve wants it to be pretty simple. This is the deal. If you want to play, great. If not, here are the options. Keep it as simple as possible.

- In closing, Steve was making some comments on having sufficient money to play and make other plans. Hinting at some other fun things to come... It just keeps going!

Both Cory and Chuck joined the meeting. Cory helped us follow-up on two tech support items from over the weekend. From what we could see, both issues were resolved, and we couldn't find the bug or issue. We like that kind of stuff (self-fixing bugs).

We looked into some timeclock formatting and other questions. We didn't see anything on that side of the fence as well. We spent some time and were talking about the aggregate quantity project to help speed up some of our inventory searches. Lots of drawing and explaining where we are headed. We also went over the upcoming client facing scheduling and ecommerce based bookings stuff. Chuck will be starting to do some mock-ups there. More chatting and talking with both Chuck and Cory on small little things.

Budget meeting for the SBA loan that we were able to get. Looking into sales, commissions, future automation, existing loan payments, and clearing out payables. See spreadsheets on Brandon's computer is more info is needed. Steve, Brandon, Cory, and Shari O. were in attendance at the meeting. Notes and copies of the budget spreadsheets were sent to each person.

Budget meeting with the adilas admin core team. Steve, Cory, Shari O., and I were there. I was taking notes and we got great input and comments from all parties. We followed up on some old business, then rolled into some new business. We chatted about maintenance, education, looked at budgets (spreadsheet work), and talked about some future and upcoming projects. Brandon has notes and spreadsheets on his local computer. Notes and spreadsheets were also sent out to all parties after the meeting was over. Making progress.