Meeting with Charlie Spickert from Touchstone. Good meeting. He said that he was going to send me some more information and such. Going through the tools and where we are heading. Getting insider information to a specific business vertical and then building out to that level (industry specific skins or business vertical skins). Where are we headed? Helping to get people to buy into that vision.

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.

Emails and feedback to Chuck on some adilas pricing stuff. He sent us an email saying that some new pricing stuff was live and online. Small page review and sent him a few small changes to make.

 Meeting with Russell and Abby. Russell is working on building a web app. He was showing us a small demo of his camera photo picture to budgeting app. They are still working on it (he and Chuck). We got off into some general world topics. As an ideal, the world would be awesome if we all just helped each other. That would take quite a bit to get there. Talking about some general sharing and community type concepts.

Switched over to working on the deeper documentation options for the presentation gallery. This will end up being the backend behind the presentation gallery. Imagine the meat and potatoes with tons of documentation, screenshots, step-by-steps, and small context related videos. It should be super cool. Anyways, we started with a small review. We were going over moving from the initial plan, to AI prompts, to AI code building, to small manual changes, to GitHub storage, to making updates and having them be tracked in GitHub. It takes quite a bit. Watching his screen and going back and forth through iterations. We liked certain changes and we didn't like other ones. A little bit of picking and choosing. Watching a series of manual tests (at this level, based on the AI changes). We were getting into deep linking and URL routing for pages and sub sections. When it is all done, it should be really cool!

Multiple sessions working with ChatGPT on adilas pricing structures and such. Getting help with prices, plans, add-on's, and other options. Shannon and I started the session earlier this morning. I then did multiple other sessions throughout the evening to finish up. We had left out activations, setups, 3rd party solutions, and other industry specific stuff. We also added in some notes to help us account for upcoming changes to the adilas value add-on core model, adilas marketplace, and the adilas cafe. All part of the new future and where we are headed.

Steve challenged me to work with ChatGPT to actually build out small samples and pages. We went through three different versions. Once we finished, I sent an email out to Chuck (designer) with the temp files and instructions. ChatGPT was very helpful. Recording some notes from the day.

Here is the full chat link of our session - 5-6 hours in total - https://chatgpt.com/share/69a0a070-3778-8007-a998-ebf29c864809

Emails, brainstorming, and light research. I'm planning on doing a small intro video. Basically, who am I, what do I like, where did I come from, why do I like what I do, etc. Be real.

- Maybe move the presentation gallery over to ColdFusion. Currently, it is on a WordPress site and we can change it, but it does not have backend or database capabilities. That could be huge for us, in order to add searching, dynamics, etc. I would also like to build out the details or the full next level. Right now, you can view it, browse around, and get a good general idea. We have had multiple people ask us for more meat (show me, don't just tell me). I was thinking about using a detailed format that I saw on a site that Russell helped me find. It's a help section on the VS Code (code editor or IDE).

- On the pricing page - I was thinking about showing some pricing categories. Things like fixed costs, percentage costs, annual with discounts, and even family or lifetime costs or prices with discounts. On the family or lifetime, help them figure out their price/cost per month and then do that price/cost for ten years. Add a 20% discount and then give them lifetime access. Just a thought. I would like to help build this mini calculator and mini app/widget and then let Chuck put it up on the main adilas website. The goal is to get a ballpark cost/price and then have them contact us to really set the price. We can use it, the calculator, for us and for them. We still want to talk to them. Every business is so different.

- Work more on the 3-part pitch - intro, current offerings, and future offerings

- Focus on what we are building - the community - the buy in will come as we show people what we are doing

- This is for me... Sit down and plan it out on paper... - mix the presentation gallery, some old PDF's and flyers, and the partially done steps to success documents. We started working on those documents years ago. We keep getting pulled off. I want to put it all together in one document or website. Basically, the presentation gallery mixed with the steps to success. Get it all finished up, with walk throughs, step-by-steps, and videos. Make it cool! Really help our users get the quick high-level stuff and also be able to get to the meat and potatoes and how it really works.

- Along with the plan it out stuff, I really want to bring all of the PDF's together in a single page. I also want to do the same things with all of the videos. Basically, a special page for PDF's, flyers, and docs. Also, a special page for all of the small vision videos. That would be really cool. We have so many good things already. I really want to bring them all together in a single place.

Emails and requesting a few main website changes from Chuck. I wanted a few new link options from the main header, under the adilas world menu option. I wanted to add the presentation gallery, fracture - adilas lite plans, investment opportunities, and a link to the adilas API. Quick phone call with Bryan. He found a couple of pages that needed some CSS updates. Small quick code changes on the classic cart. Working on the form field CSS stuff for the classic cart. Ended up going through each of the cart options to help with look and feel. Pushed up the new changes.

Emails, paying bills, reviewing notes from over the weekend. Planning for a meeting with Steve. Reread some great poems that have a great message. Click this link to see the poems (on a different entry from a couple of years ago). Pushing up videos to a new folder inside of google drive.

Translating from post-it notes on 1/11/26

- Sunday morning - I was shaving, getting ready for church. I had a flood of ideas come into my head.

- We go for it on 4th down (football analogy)

- Reinforce the team - goal 1

- Goal 2 - We make sure that keeps working (meaning goal 1)

- Morning meeting at 9:30 am (get some communication stuff going on)

- Let people (our team) run... minimal on the micromanagement

- We focus on people... there will always be more projects and features

- CSS on forms for classic looking forms in the snow owl theme

- Look and feel to snow owl - help fix internal and existing pages look good

- Training - could be internal training, AI training, or external training

- Presentation Gallery - Keep pushing on that project

- Images for the adilas lite plan and the investment opportunities

- Abby - Talk to Steve about getting her involved

- Work with the design team - Chuck, Piper, Sarah

- Move key videos to Google Drive vs on the content server. It just can't serve them up quick enough.

- On the AI Agent - Use what we have - Set it up so that it tells people "I'm good at nav" - Polish the 350 existing prompts and tools.

- Suzi - Step-by-steps - small documents with information and instructions. She is really good at that.

- Sean and Cory - General Training

- Prepare for 100+ new accounts - What would that take?

- Open things up!!!

- If needed, we have others who can help - Dustin, Eric, and John. There are others as well.

- Shannon - She has been such a great helper to me

- Let Alan lead out - Help him succeed. He can do so much more than code.

- Get out of the way

- Leverage debt - put all of the adilas shop or adilas lite stuff into adilas as real payables - bring it out of hiding - true costs and costing

- Co-owner Advocate - possible new title, if needed

- Mini bank accounts for each person and/or department - help the team feel safe, supported, and funded

- Be in someone's corner - believe in them

- Overcoming fear - Satan wants us to run and hide

- Simple 1-pagers (one-pagers) - at a glance

Working with Russell. Talking with Chuck for a few minutes and catching up. They, Russell and Chuck, were on a previous meeting. After Chuck left, Russell and I did a little flashback and were talking about CSS and modern tech. Sometimes it is hard to try to keep up with all of the changes. The old basics are still super important. A developer needs html, JavaScript, CSS, SQL, and some kind of backend technology.

As we were working today, we were talking about exposure, in development, leads to some new ideas and knowing what is possible. Not all exposure is good, but certain kinds of exposure can really help you imagine what is possible. Once you know that, it isn't super hard to then go try to figure it out. Granted, the term "isn't super hard" is relative...

We did some training on the VS code interface, some speed tips, some Git tips (code repository and branching stuff), and then spent some time tweaking a little bit of adilas code. We changed some older hardcoded values (in the CSS) to use flex box instead of older direct positioning. Good little training session.

Email to Wayne about streaming videos. We would love to be able to do that easier from the adilas content server. Then a semi-lengthy email to Chuck and others about the shopping cart and updates to my cart favorites. Phone call with Bryan to go over a page that does an upload from a CSV file and allows for dynamic mappings to be used. He would like to help some clients with possible EDI (electronic data interchange or transfer) type stuff for buying and receiving inventory.

Here are the two videos that I sent to Chuck about the shopping cart.

internal_shopping_cart_r1.mp4 - on Google Drive - small future cart demo

cart_touch_and_discount_options.mp4 - on Google Drive - current cart demo with my cart favorites

Phone call with Chuck to go over a standalone style guide and CSS template. We would like to help out the guys that are going to be creating a white label option, based off of the adilas styles. We talked about some other projects and did some catch-up. He will be code reviewing some of Piper's work (another adilas designer) and then on to the standalone style guide. After the phone call with Chuck, I paid myself and recorded extra time (overflow) values in the shop from last week.

Meeting with Steve. Looking into ecommerce changes and settings. We pulled up a branch that Chuck was working on. We made a few tweaks and wired things up. We got it all up and live and did some testing. After the meeting, I made a few more small tweaks. I also sent an email out to Wayne to ask about caching issues (web file being cached and not updated) and how to help overcome some of those things.

Meeting with Bryan Dayton and his brother Charles Dayton. Charles owns a company called ActionStrategy and they do consulting, project management, and planning for companies. We looked at his software and what it does. We then had some fun conversations about how it might look if we merged both companies together to offer more options and features for their/our users. Lot of fun, just playing around with ideas.

We, Bryan and I, then gave Charles a fun mini demo of adilas and how we use it and have used it. We put a bunch of links through the chat window for him to look at. see list below.

Web link - help.cfm?id=381&pwd=time - elements of time - general

Web link - help.cfm?id=383&pwd=template - time templates

Web link - help.cfm?id=391&pwd=sub - subs of time

Web link - sales-gallery/bf-calendar.html - calendar and scheduling overview

Web link - sales-gallery/cc-vision.html - where are we headed

Web link - help.cfm?id=323&pwd=flex - flex grid options - custom out of the box

Towards the end, we did a small mini consulting session with Charles. He was telling us what he has and what would be required. We took some notes and then showed him how we could do that inside of adilas. Lots of talking and drawing and even jumping into certain parts of the system to show him what the existing interface looks like. Fun little brainstorming session.

Meeting with both Russell and Chuck. They were recommending sub districts (maybe for enterprise level grouping) for multiple locations (corporations). Good work session with both guys. That wasn't the original plan, but it worked out pretty well. We spent some time going over the pdf dashboard mock-up from Chuck for Yogen Fruz (see attached).

After Chuck left, I was talking with Russell about showing and selling subs out in ecommerce land. We may have to reverse out the structure. He also recommended that we abstract the process to use the same code for each option (show and sell parents, show parents and sell subs, show subs and sell subs). Ideally, we will setup the ecommerce so that it can use any of these selling types, and the data all gets passed to the cart correctly. Basically, format it all to go down one pipe... with possible branching logic. Russell did some fun drawings that helped me see what he was pitching (see image).

We then jumped into Affinity Photo and played around with some of the tools. Kind of a show and tell lesson on some of his favorite tools. Recorded some notes and pushed up the supporting files to document things.

Yogen Fruz website meeting - There were 9 of us on the call. They had questions about the main YF website for Chuck. We talked about online orders, merch (small items or merchandise), there will be a test with new hardware from us and another competitor. We spent some time talking about hardware. They were talking about needs and wants for their website. There were some questions about quality control and who does what on the hardware setup. Talking about content and showing videos on their menu boards. Currently the company that does their menu boards change both the video and content. They are also responsible for changes to prices, based on Excel spreadsheets, per location/region. She, Moran, wants to get the videos that they use on the menu board on their social media accounts. They want to control the full backend. They currently don't own the content. More talking about hardware, media, and controlling the backend content. Good meeting.

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!

Various meetings, throughout the day.

On a Zoom meeting with Cory. Looking over some gram control settings.

On a meeting with Cody. He got a few things tweaked for the check write stuff. Looking at pagination on the label builder. He was also showing me some work that he was doing on the infinite scroll (scroll, get more results, scroll, get more results, repeat until finished).

Working with Steve. Debugging things. Found problem with list contains vs list find functions. Pushed up the new file.

Emails and reading over a response from Chuck about a custom website.

Paying bills. Meeting with Cody and Chuck. Light introductions and then some back and forth. Cody was showing Chuck some of the label builder pieces. We also showed Chuck some of Cody's other projects that he has been working on. Towards the end of the meeting, we got into some Yogen Fruz tools and needs. We even talked about bigger dashboard, visualization tools, and prediction type stuff. Chuck likes to build out a list of requirements and then make a plan. He wants me to send some things his way.

Meeting with Steve and Cody. We were talking about current needs for the adilas system. Here are some of my notes:

- Going over forms, accordions, modals (popup windows), client-side validation, ease of use, dashboards, custom homepages, buttons, containers, canvases and pallets (like an artist with paint - a pallet or possible colors and tools), asynchronous loading, preset pages that load certain things, sizing things, moving things around, etc.

- New custom homes... Imagine using the new drag and drop interface (what Cody is working on) and then be able to swap out our homepages (existing homepages) with new custom home pages (built by the users or as an industry specific skin or white label). Eventually you could do lower-level pages as well. Think full custom... for the whole system.

- Getting Chuck involved, right off the bat. Chuck is the frontend designer. Responsive design (phones, tablets, and other devices).

- Where we are heading... not just a new label builder, we are building packaging, designs, full layouts, etc. Steve was saying that if we offer a custom and internal solution, we could potentially help with overcoming minimums on custom design layouts and print projects. Almost like a print shop. Making dynamic graphics. Making packaging with the correct information right on it, just making as many as needed. Basically, you could skip the full packaging and then adding a label on top of that. If people want to print other things... then let's talk about it. This could be making gift cards, employee cards, custom packaging, 3D printing, etc. Not just for labels, it could be for more.

- Light looking at sheets and sheet labels. We want to launch an MVP (minimal viable product) and then sort of tease them (our clients) going forward. help them catch and see the vision. If you can give our clients a vision of one, they can see the possibilities of doing thousands.

- It's all about efficiency, ease of use, helping them get into the correct direction. We talked about galleries and ways to add the data (whatever that is) to the different things or places. Almost a bunch of options and pick and choose what you want and how you want to organize your data.

- I will have the responsibility of hooking up both Chuck and Cody. Letting them get together to go over some gui (ui/ux) stuff (graphical user interface or user experience stuff).

- Steve was talking about how so many people have tons and tons of photos and helping them organize them (in bulk). This was just an idea. It's just data and some management type things. Maybe some bulk galleries with notes, flags, tags, and ways to organize things. It's all just data... print it, organize it, share it, etc. More talk on flagging and tagging items.

I thought that it was a great meeting. Steve and Cody were having fun and doing some great brainstorming stuff. I was chiming in every once in a while, but it was mostly Steve and Cody. Super fun!

Meeting and working with Bryan on the vertical time view (showing time slots per person on a vertical axis vs a horizontal axis). I added a screenshot from a branch that Chuck was working on. It shows a nice view of where we are headed (rough idea). We were also talking about my old notes on element of time # 11333. This was dealing with some planning for the Lucky Puppy folks (potential client).

Meeting with Cody and Alan over a GoToMeeting session. Alan had to join us by phone. We were talking about teams, budgets, and vision. Here are some of my notes:

- Frankenstein computer project. Mixing and blending different styles and such.

- Specialists and filling in the gaps (in our teams). The ideal would be working in Parrell vs just one person on a single project.

- We would love having a known frontend designer. We do have a guy, Chuck and Piper, but both are only doing less than 10 hours a week. We need someone full time.

- Small teams of two

- We spent some time talking about timing, when to push and when to chill.

- A real need for direction (a goal and vision). All going together towards that goal.

- Eye candy, graphs, charts, buttons, containers, widgets, and such. Helping people to get more info graphs and quick summary information (dashboards).

- Sometimes, cool isn't useful... to certain people. Cool can help sell things.

- Cody was talking about adding graphs and charts to the custom homepage builder. That would be super cool.

- Finding out what would be beneficial to our users. Fill in the gaps. Ease of use to help train people. Seeing information, counts, and summaries quickly.

- Talking about visual homepages for all of the main players.

- From Alan - eventually using web sockets to show real time data and changes.

- Ideas on new homepages... we could take all of the old ones and turn them into an old or basic home, add new graphical homes, and maybe the last 15 entries of the data for some super simple home pages.

- Focusing on manager type tools. Top paying customers, group counts, bestselling products, busiest times, etc.

- There always seems to be some stress over money and budgets.

- Cody was grateful for the time to meet with Alan.

Alan had to drop off, we (Cody and I) then switched over to the adilas label builder and talking about direction and eye candy options. We are going to try to help focus on some tools and visuals for manager's and help them save time or feel like adilas gives them some time savers... One of our main goals is helping people out.

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)

Getting Amber signed up with an adilas account. Showing her how to login and record her hours. She is helping me to organize some printed copies of the developer's notebook entries.

Emails, small edits, and merged in some code for Chuck on the PO photos page - new snow owl theme stuff. Recording notes.

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.

Code review on Chuck's changes to the advanced time sub search results pages (like 6 new report formats). Merged in code to the master branch. Registered for the Adobe ColdFusion Summit event this fall, in Las Vegas.

Working with Chuck. Talking about preparedness stuff. Looking at the subs of time advanced search report and all of the exports. He needed some directions, where to turn things on/off, settings, and how to load in the data. We bounced through a few of them (different sub reports) and got things going in a good direction. He will go back and fix the pieces that he didn't know how to get to, and we'll go from there. Good stuff.

Phone calls with Steve and Bryan. Talked with Steve about some manufacturing stuff and new default vendors and default customer settings. We talked about options and ways to help take out steps and automate things. More and more settings. We also talked about other deployments and clients and upcoming projects. Light talks about staff and even a new guy (Cody - developer) and Piper (designer working with Chuck). Trying to make things happen.

Bryan had some questions about more QuickBooks API stuff and other projects that he is working on. He's got a lot of stuff going on as well.

Phone call with Eric. Texts back and forth with Steve (small update). Merged in some code for Chuck and his snow owl changes for the add/edit payee and permissions pages. Switching branches and pushing up some database updates for Eric. Ran updates on all servers for cross-corp gift card rules. Recording some notes from the day.

Meeting with Chuck. Code review and going over a number of to do list items on the add/edit payees and permissions page. Small work session.

Working with Russell. We were working on some AJAX and jQuery on the cart groupings. CSS changes with Chuck on the presentation gallery. Working more with Russell on AJAX stuff. Mostly prep work. Consolidating and simplifying it. Light testing.

Emails. Looking at Chuck's vertical time slot view page and a new code branch for showing the vertical time stuff. Playing with some of the values on the mock-up page, just getting to know it (small experiments). On the phone with Bryan going over some ideas. Also talking about raises and time available to help with code, projects, and prospecting.

Meeting with Chuck, Suzi, and Steve to go over the vertical time view page. We were talking about MVP options (minimal viable product). Looking at some other software options (things that the client is currently using - likes and dislikes). Good meeting and came away with some small to do list items.

After the meeting, Chuck helped me get signed into the WordPress site and setup the two-factor authentication (2FA) stuff. Recording notes.

Meeting with Chuck to talk about a vertical time view for appointments and elements of time (calendar events). We setup a new page template for his new page. Talked about how we did the horizontal time view page for beaver mountain. We also talked about a number of possible options and how to show the correct vertical appointment blocks. We even looked at some dynamic CSS and doing custom height calculations on the fly. Making progress.

Getting organized. Texts with chuck on scheduling. Prep work and planning for working with my daughter Abby. Figuring out a number of things that need to be done. Getting a list together.

Email to Chuck about main website and navigation issues. He is going to check into it. I then spent a little bit of time undoing some of the new cart stuff that I was working on last night. I decided to go in a different direction. Working on the new mini scan cart and the new split cart stuff. Adding new settings and playing with a new modern split cart including variables for which sides and sizes to use the split cart. Should be pretty fun. Making good progress.

Meeting with Shannon. She took a bunch of notes about what we were talking about today. See attached. We started talking about my daughter Abby and what she could bring to the mix. We then talked about Russell and some of the fun things that he brought to the mix (inside adilas, look and feel, ecommerce, AFB, photo galleries, other projects). He has been a great asset. We spent a lot of time talking about being our own style. That's really important. That's who we are.

We then spent a ton of time looking around the presentation gallery and expanding things. We'd like to build that out and let it go deeper, if someone wants to go deeper. Keep it really simple on the top level and then they can go deeper if wanted or needed. We may have to get access from Chuck to work on the presentation gallery. He built the WordPress site. We would love to add photos, videos, modals, and other things to that site. It could be really cool.

Meeting with Chuck to go over the horizontal time view stuff for appointments and scheduling. Sent him a link to the video for Beaver Mountain and how they use the horizontal time view and scheduling for ski school stuff. Also, a couple of screenshots and some other notes and references (notebook entries id #'s 8004 and 10914) dealing with time, settings, and where we want to go.

Working with Steve and Suzi. They are planning a demo site for a dog care (nails, baths, grooming services) business. Going over processes, routes, settings, processes, etc. It ended up being a small planning and consulting type session. Suzi does a great job and is very organized. Once we figure out the flow, we plan on passing that info over to Chuck (designer) to let him work his magic to help design a custom skin or mock-up.

One of the things that we may end up doing is adding a button to the element of time to allow a pet to be assigned. We are handling all of the one-to-many pet to owner details in flex grid tie ins. That's working pretty slick. We just need to populate that data around a bit more to help it show up correctly.

Another thing that we may need to do is a popup builder to show services that can be added to an invoice and also pushed over to an element of time to help the attendants to know what is scheduled, needed, and what was done per appointment. We went over some options.

After Suzi left, Steve and I jumped back in and went over other stuff. We talked about merchant processing. We went over some database updates that Steve is working on for invoicing time and sub timecards (job costing stuff). As a side note, Steve was mentioning that adilas is starting to sell some bookkeeping services along with the main system or main product. That's awesome. All part of what we want the adilas marketplace to do, speaking towards the future.

Steve also requested that we start working on the known issues report to help Mike out. This is a list of things that we have identified where things could go off the rails. Things like duplicates, certain dates that are out of order, mismatch between main and line items, sub inventory issues, etc. We have a page called known issues where we are listing all of these possible gotchas (data problems). It would be really cool to start working on some small reports to show those pieces that may have issues.

Meeting with Chuck and Russell. Touching base with Chuck. It's been a while. Working with Russell on some CSS tweaks for the adilas lite site (mobile ready). Then back to working on our dashboard mock-up project with Adobe XD and AJAX stuff. Russell was prepping things and building out his own components. While working in Adobe XD, get close but not pixel perfect. Just enough to get going. Everything will be dynamic (data wise) later on. Building out custom components and zooming in/out to make sure that we get the visual ranking correct (what is the most important). We also talked about not being limited by the template (CSS theme or template). It's okay to go custom if needed. Asking lots of questions. What do we want to show, why, where, what is the most important part of it? Balancing out the visuals, the user experience, and gently leading the user to what to do and what is important. As a light goal... is the user experience good enough that they could use it without training? The design determines the architecture (what is needed). Good session.

Emails, code review, merged and pushed up some code for Bryan. Started looking into some code changes that Chuck had made. Asked him to make a small change and then I'll recheck it again. Recording notes from 12/11 - 12/12.

Jumped on with Cory and Shari O. to show them some progress on my bulk clear loyalty points project. Small show and tell. We merged in a small branch for Chuck and then talked about some clean-up on pagination on certain pages that is needed (go to the next page - pagination). We talked about yearend stuff and getting the known pieces done before the end of the year. That one, yearend tax stuff, comes up every year. We have to update 1099's, W-2's, and other reports. We also have to add new tax withholding tables and update values. Maintenance stuff.

Small hot fix for the add/edit customer page. Got the hot fix from Chuck. It was missing a button.

Met up with Chuck after hours to do some code review on the add/edit customers page. We did some catching up and I showed him around some of the adilas financials. He has been doing some after hours work and light moonlighting work for us here lately.

Emails and helping Chuck with some questions. Getting him going in a good direction.

Jumped on the GoToMeeting with Chuck. He needs to get his local environment all setup again. He wiped a hard drive and lost his older local box and coding environment. We talked about options of the older classic way or getting with Wayne to try the Docker container way. I got him enough info that he can do it either way. We then talked about the new shopping cart that I'm working on. He was watching and providing some light feedback.

Online meeting with Chuck. He was helping me with some CSS stuff and some Bootstrap stuff for the Bear 100 mobile app. We did some training and Chuck helped me make a few changes. He's a good frontend guy and has skills that I don't have. Good session. Pushed up new code to the repository when we finished.

working on the Bear 100 mobile app. Added in some new code that Chuck sent to me for the top runners. Working on layout, logic, and making the page dynamic. Chuck's code was static (hardcoded - prep stuff). I was adding real data to it. See attached for a couple of screenshots. Sent an email to the race director to show him progress.

New transition today. I popped onto the morning meeting because that is what I normally did. I let the guys know that I wasn't going to be doing that any more. Sean was on the meeting and we chatted for a bit. By way of an update, he is doing great working with the dynamic adilas label builder. He is also willing to do some checking out of what our competitors are doing and providing me some competitive research. Nothing too huge.

John joined the meeting, and we were looking at some mock-ups. We would like to allow our users to interact with options to setup their own space, look and feel, etc. We would also like to do some early prototyping. Get it out and in their hands. Even things like settings for click vs hoover and other simple choices that affect their space (what they do and use - their space, their flow). We already have a bunch that we have paid for and haven't been able to use it yet. We have a ton of R&D stuff that Jonathan Wells did in Adobe XD for fracture, adilas cafe, and a new shopping cart.

A picture is worth a thousand words. Dramatize it, push up XD docs from Chuck on the content server. We have done tons of really good R&D. Let's use that. This is how we are going to get fracture up and going and off the ground.

John and I talked about trying to centralize all of the data and assets. I have a bunch of it. We have pushed up a bunch to the adilas content server. We also still have quite a few assets and raw authoring files with the guys/gals who made them - Jonathan Wells, Chuck, Russell, Marisa, etc.

As part of our discussion, John was showing me some of the projects that he worked on for school. He's got business design docs, pitches, proposals, flow charts, etc. I'd like to tap into some of those planning and system scope documents. Not necessarily for his project, but more for what we could do for our projects. Once again, show them don't tell them. That is huge and reoccurring theme. Show them, don't tell them.

Here are some other notes from our meeting:

- We could make some awesome customizable dashboards

- Realtime data on what is going on (tables, graphs, charts, and quick aggregates), help them see everything without overwhelming them. Full visibility.

- "Show them" and then do it over and over again.

- Talking about dream salaries between John and I. Where would you like to be, salary wise?

- Keep idea farming - that's what we do

- Shari O. joined the meeting. She loves to do some gaming. I'd love for her to come up with some ideas on how to turn adilas and the daily work into a game of sorts (the game of business). Shari O. said that she could do some light research and maybe come up with some ideas. As we were talking, she said that she changes games based on moods. That's good information. We may want to come up with something similar - what mood are you in? Ok, let's play that way. This is just a dream right now. I'd like to see where it goes.

- Keep gathering things together. Eventually, we will make our own world.

- More ideas for the application and/or system - education mode, game mode, nuts and bolts mode (just get it done - speed mode).

- More talks with Shari O. about Facebook groups, other social groups, having meetings, setting up schedules, and giving people power to run what they want to do. Make the whole thing a team effort.

WordPress was down and this caused our main website to be down. I contacted Chuck via text, then a phone call. Sent emails to Wayne with some instructions and suggestions from Chuck. Trying to get things figured out. Luckily, you could bypass the main website and do a direct login by changing the URL (web path) to the login page.

Jumped on the GoToMeeting session and was having audio problems. Cory had some questions about the adilas label builder and getting images pulled in. Kelly needs some sub inventory reports. Some of that gets pretty dynamic and pretty deep. After that, John and I talked about our WordPress site and getting our stuff off of an outside content management software package, WordPress. We couldn't get ahold of either Wayne or Chuck to get help. We need to get some documentation from both or have John help with that documentation. Our eventual goal is working towards standardizing and using best practices for all of our developers. Constant processing of pivoting, updating, and changing to fit and fill our needs.

Chuck was able to meet with me and I jumped back on the GoToMeeting session. John jumped back on as well. We were trying to fix the WordPress stuff for our site. Chuck was helping John try to navigate to a certain file folder and make some changes. We kept running into issues. Cory jumped on and we made a quick fix for her on a cross corp invoice to PO transaction (special cross corp page). Once we finished that up, back on with John going over plans and what not.

Met with Chuck over a GoToMeeting session. We were going over changes and requests from the Bear 100 folks. We worked on new tooltips, runner counts, and a new leader board. Due to time, we had to put in some fake data, but we will go back and reformat things and populate it with real data. Good meeting.

Working through a number of notes from a client meeting. Work session on the requests for the custom code on the Bear 100 mobile app and the internal code. Spent most of the session getting back into the project. Read my notebook notes, looked around, tried a few things, and sent a text message to Chuck to see if he could help me out.

Steve and I touching base on things. Meeting with Bryan. Merged in 10 new files for elements of time. The new code came from Chuck. John helped us push it up to data 0 for testing. Looking over Bryan's progress on his migration of the custom Beaver Mountain horizontal time view to a more generic and public accessible horizontal time view page. Bryan is also working on pulling across the add additional user/payee assignments page. Once again, custom code that only Beaver Mountain had access to and now we are reverse merging in that new code so that other clients could use that type of functionality.

code review session with Bryan. He is helping me out by combining about 5 branches of code that Chuck did into one single branch. We reviewed some of the code and he will be coordinating with both Cory and Wayne to get things tested. Once tested, we will merge the new files into the master branch and push things up live on all servers. The 5 or so branches were dealing with new changes to elements of time. New time homepage look and feel, new working with time page, new printable time page, and some tweaks on the add/edit main time pages and time history pages. Good stuff. Looking good.

Bryan has really been a key helper in getting these projects off of my desk and getting them making progress and being pushed forward. I'm super grateful for that.

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).

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

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

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

- Helping people know what is possible

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

- YouTube is another option

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

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

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

- Global communities

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

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

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

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

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

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

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

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

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

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

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

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

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

- Talking about invoice reminders, online payments, etc.

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

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

- Steve was pitching ongoing training courses for our clients.

- Wayne has a degree in curriculum and training

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

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

- Just in time online courses

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

- Keeping up with the constant changes

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

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

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

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

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

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

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

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

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

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

- Train the world

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

Good meeting this morning. Lots of talk about trends, needs, and client wants. Steve, Sean, John, and I were on the meeting. We were talking about software needs, trends, expectations and how those things keep changing. Steve was pitching the idea of a full white label type approach. This would be something like where we would license our software to a company, help them setup a standalone server(s), give them raw code and let them build and deploy whatever they want to do. This would be similar to open source in that we would give them a full copy, provide them updates, and let them tweak and use whatever they want to. Basically, let independent companies build out their own software solution based on our base code. In reality, that is still quite a ways out, but fun conversations.

Everything keeps changing, daily. Maybe let them (our clients) have it and do their own upkeep for their own systems. We could keep evolving the master branch and allow our clients to pull in new code, if they want it. It just needs to keep perpetually evolving. As a direct quote from John - "Our clients eat with their eyes." We need to keep working on a better look and feel. Also, this look and feel needs to keep changing every few years to keep it up to speed and up to snuff. If you want it to look modern, you need to have an update plan in place to keep it up.

Lots of talk about our competition and what level they are playing with. Because the whole world uses stuff like Amazon, eBay, and other giants, we are virtually competing with those entities and the expectations are similar because we play in the giant web world. Every has a smart phone and get to use mobile apps, nice interfaces, and other cool things every day. That is the expectation. That is really hard to keep up with and/or even play the game. Our users are expecting eye candy, graphs, charts, quick aggregates, slide in/out drawers, show/hide options, drop-down, slide-up, modal pop-ups, and cool one-pager type apps.

We just need to keep going. Eventually, even if it looks pretty, people really need functionality. However, if they can choose pretty and easy, they always will until it bites them due to lack of functionality. The old adage of form and function - which one do you or do our client value? It keeps changing as well.

Steve was talking with John about some future projects dealing with the look and feel. John is going to be taking over the adilas docs now that Chuck had to take another job. We talked about the use of a global style guide and keeping that up. Once again, every couple (2-4) years, we will need to keep upgrading the look and feel. It is part of the game.

As a side note, some of these things are good info for our future project of moving over to a project called fracture. Along those same lines, fracture may end up being a morphing process (using the old and making it become something new) vs a full re-build from the ground up. Both ways take a lot of work and there are pros and cons to both. Until we get more funding, our current goal is to capture the info, ideas, and data. We will then keep chipping away at the current infrastructure and virtually morph into the fracture model vs a full re-build. We would like to re-build, but that may not be practical. It all depends on needs, funds, timing, and goals.

Meeting with Chuck and talking about the vertical time views. We wrote some ideas down inside of the notes inside of the time homepage (code view). Lots of math. Going over ideas on how to wire up the page and work the CSS. We even got into fractions within div tags (CSS stuff). Making other plans. Chuck is almost done with the changes for the time homepage.

Before Steve and Sean left, I asked Chuck to show them what is coming for the time homepage. They really liked what they were seeing. After they left, Chuck and I started talking about owning and starting a business. We talked about problems, successes, inflation, the state of the economy, and how society is forcing almost all homes to choose between money (dual income) or more family time (traditional family roles).

Switched over to looking at code and going over the time homepage changes. Chuck had a to do list and we were going through items on the list and finishing them up and removing the to do list flags. Lots of work with date/time logic, buttons, links, and if statements. We used to have a function called the jump to date. It was only on one section or part of the page. Chuck wanted to expand it so that it could be used more generally. Adding some new code.

Chuck and I were talking about 3D printing and how he is hoping to do more commercial stuff with his printers. He showed me a few Udemy courses and we talked about web design, CSS, and normal JavaScript stuff. We were talking about how, in our line of work (web and code stuff), you have to virtually sharpen your tools (continuing education).

We switched gears and started looking at the time homepage redo project. Chuck was trying to help me learn about CSS grids, flex boxes, and expanding flex in both horizontal and vertical directions. Eventually, we run out of room. Chuck suggested that if we develop for mobile, we may need to drop some data or use modals to show more info (screen real estate). Light work session. We setup some more time for tomorrow to get back in there on the time homepage project.

Multiple different phone calls. On the phone with Steve going over education, certification, and getting a quick ROI (return on investment) from new development. Steve has been talking with Kelly about some ideas and options. She has been a great resource. I was also on a phone call with Chuck. Sadly, he is going to be moving on to greener pastures. He got an offer for over double what he was getting plus benefits. It's a no brainer. Anyways, we talked and chatted, and we'll still pass him over projects as he is able to fit them in. Emails and other text messages.

Recording notes and to do list stuff. Meeting with Chuck and touching base on projects. Most of the time was spent reviewing notes in the shop and putting summaries inside of projects in the adilas side.

Small work session with Chuck. He is working on the time homepage for elements of time. We are doing a full new look and feel to the page. Our session today was spent looking over progress, talking about changes, and doing a little bit of wishing and dreaming (what it could be). We talked about making the date jumper a more static piece of the page (older feature to jump dates by hours, days, weeks, or months). Say we were on 10/13/22 and a doctor said come back in two weeks. We could put in a 2, select the weeks option, and hit go. It would move us ahead in the calendar to that time period (days, weeks, or months). Chuck is planning a slight change to make it simpler going forward. Making good progress.

Work session with Chuck and the new look and feel for some pages inside of elements of time. Working on the working with time page and the printable time page. They looked great. We made a few small tweaks and merged two different branches together. We sent a note to Wayne and Cory about testing and pushing the code to all servers. We are waiting for them before taking it to the next step.

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.

Chuck and I talking about automation and tech for the Bear 100. Making it cost effective and still high tech. Looking at mock-ups for the time homepage. See attached for a first round mock-up of the time homepage.

Chuck and I working on the printable time page. Going over JavaScript stuff, bootstrap 5, and new stuff. Talking about investments.

Talking with Sean and showing him some stuff with the Bear 100. Looking into Chuck's event code for the events page. Demo and showing Steve and Sean the new events stuff. Small brainstorming on sales ideas and trying to do more special events and such.

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!

Chuck has been feeling under the weather for the last couple of days. We spent most of our time going over the new code on the working with time (elements of time) page. It is looking good. He had a number of to do list items and we were going through them. Making some decisions and helping him test some of the data driven code options. As a side note, some of the pages are getting really big with the new display code mixed in with the older classic theme. This page is over 8,000+ lines of code just for the working with time page. That's getting pretty big, for just one page.

Light talk about the Bear 100 page and using the mobile ready version this year for the public facing race stuff. We need to get the events page up and going.

Quick GoToMeeting with Chuck to go over assigning flex attributes to elements of time and how all of that stuff works. Text messages to developers helping and pointing them in a good direction.

Meeting with both Bryan and Chuck and going over the progress on the ecommerce side for client facing scheduling. Bryan is further along than I thought. That's awesome and we'll be hitting this project harder in the next few days.

Chuck joined the meeting. Cory was still on from the last meeting. She quickly reported to Chuck about the video for the adilas label builder that he had done. Cory had showed it to kelly and had gotten some good feedback.

After that, Chuck and I talked briefly about 3D printing and building in supports for more complex projects. This was just for fun.

We got into a small session and talked about financials and available hours, based on projects and budgets. We hopped into the system and looked around. After that, Chuck and I spent some time looking at his new code for the working with time page for elements of time. Lots of layout and UI (user interface) changes. It is looking good. Big lift and Chuck is adding tons of new code to help with the layout and such. He is somewhat experimenting with different layouts and formatting options. I thought that it was looking good.

The last topic of the session was dealing with maintenance costs going between the older classic code and the newer snow owl look and feel theme. Some of our pages are doubling due to the amount of code to handle both versions and/or themes. Once again, a maintenance deal - hidden costs.

Phone call with a client. Passing on some updates and information. Spent some time looking into a bug that Cory reported. Found the bug and pushed up new code. Emailed both Cory and Steve about what I found with the bug. It ended up being a date sync thing. One of the custom pages had a date sync option tied to the settings. Every day, the sync would check the stored date to see if it had the latest info. It would resave the settings and thus refresh itself. The auto process was saving most of the old settings but setting some of them to a default value vs holding the older settings. That was the problem.

Took the rest of the time and worked on pushing up Chuck's new code to expand the time - sub date/time notes field. It was limited to 255 characters. We expanded it and allowed for HTML in the new text field (65,000 character limit). Ran the database update on all servers and pushed up code and did some testing.

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

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

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.

Reviewing a small promo video from Chuck dealing with the adilas label builder. The video is about 5 minutes long and pitches the adilas label builder project and what we want to do with it.

https://vimeo.com/744675016

Chuck's label demo went for about 45 minutes, then we rolled into a meeting with Wayne and then right into a second meeting with just Steve and I. Here are a few notes.

- Chuck was going over the new adilas label builder or label maker design. He was doing both a verbal and visual walkthrough of the prototypes screens. Light back and forth on feedback and ideas. It's looking good. He will be doing a final video here in the next couple of days.

- Wayne had some questions on parts, parent/child items, getting part quantity counts, and part status fields. Going over code and database stuff for a project that he is working on to get rid of duplicate parts or items.

- Steve and I talking about budgets, direction, maintenance, and priorities. We were brainstorming on ideas such as meeting with the guys every week for an hour to help them out and get an idea where they are at. Getting things done. Sometimes our guys get distracted. We know what to do but we aren't doing it. If our guys need help, they need to get ahold of us. As we delegate, we then need to inspect what we expect. Small chat about managing techniques.

Small session with Chuck going over the adilas label builder and his new prototypes and mock-ups. Light back and forth on ideas and suggestions. We talked about doing a video and mini campaign to help raise funds for the adilas label builder. Other talks about internal and external fund raising. Putting the power in their hands (our clients). This could be funding options, tools, create, update, modify, delete, and use as needed. The more tools that we provide and let the users use them, the better our product becomes.

We talked about doing an internal pitch and pitching our ideas to Steve as well. If we get his buy in, that helps the whole project fly and it gains access to other networking and funding options.

Lastly we went through some ecommerce stuff to help Chuck with his project to help with the client facing scheduling project. We are making progress on all fronts. Good stuff.

Light research on some business info from Jonathan Johnson at Epic Enterprises. I want to pass on the info to Sean so that he can review it. Wayne and I spent some time going over indexes and possible code wrappers and helpers. Then we flipped over and worked on some new corp stuff (adding and editing corporations inside the system).

We have a couple of new projects that are somewhat mixing. We have the change from MyISAM tables to InnoDB tables (database engines inside of MySQL database). We also have a project called the monitoring system that has some cool things that are coming. We have to mix and blend all of the pieces together.

Chuck jumped on and we chatted about 3D printers and building things that we need. Wayne and I finished up our meeting by going over parts, find and replace functions and code snippets. Wayne is going to do some backend clean-up on some of the servers and will end up either using the find and replace stuff and/or pointing users there if duplicates are found. Either way, planning some light clean-up on the databases and servers.

Text messages and touching base with a business consultant that we worked with previously. Switched gears and working on code for Chuck's changes to sub dates and times for elements of time. Steve had requested those notes to be expanded and to allow for HTML if needed.

Helping Chuck with some ecommerce settings inside of his development environment. Cutting a check for Aspen. She is working on some training to help with HTML and CSS stuff. Other follow-ups with our internal guys and gals. On the phone with Eric going over projects and getting a verbal update on things that he is doing.

Meeting with Cory, Chuck, and I going over the label builder. We went over all of the notes that Chuck had on the opening page. We looked at visuals and made some decisions. Good starting place.

Most of the meeting was going over the notes, mock-ups, walk throughs, and coming up with specifics. Somewhat of a detail work session.

Meeting with Bryan and Chuck on the client facing scheduling project. Touching base on where each of the guys are at. Chuck is working on design and Bryan is working on the backend. Bryan showed me some scratch files stuff. We made some plans and then talked about options on both the frontend and the backend. Chuck bailed out and just Bryan stayed on the call.

Bryan and I decided to go full custom (hardcoded values vs variables) for this first round. He and I spent the rest of the time going over steps and options.

Emails and tech support. Checking on internal email processes. The email stuff was struggling. I was then working on merging in code for Chuck. I ended up doing 5 branches of code that were dealing with a new date-picker.

I also had a quick meeting with Bryan going over automated emails and new code. After that, I jumped back on the date-picker pages and got everything merged in for Chuck. Hundreds of files had been updated. Good stuff!

Recording notes, both here in the shop and some subs of time out in the main adilas.biz account. We are trying to track time from all of our guys and gals and put it in one place. I have more freedom out here in the shop world vs inside of adilas. I'll keep recording things out here as part of the developer's notebook and then put some summaries into the main adilas world (system). working on the last couple of days. It is amazing to see how much changes just in a few days. The whole thing (app and/or system) can flip and roll and move, faster than we can even keep up with it. It's pretty crazy!

Spent half an hour doing emails and reviewing mock-ups from Chuck. His new mock-ups are prototypes for the new adilas label builder app.

Meeting with Chuck on the client facing scheduling stuff. We went over ideas for the MVP (minimal viable product). Talking about flow and structure. I took a number of screenshots (see attached). We also talked about how to deal with custom shuttles (unscheduled elements of time). After that, we rolled into what might come after the MVP rollout.

We spent a little bit of time looking into the label builder and Chuck's new layout and prototypes. We got into some JavaScript stuff and looking at custom code to control a JavaScript canvas. We also looked into a mock-up of the custom label homepage that Chuck is working on.

Bryan joined us and we switched back over to the client facing scheduling stuff and gave him a small walkthrough.

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

Anyways, here are some of my notes:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Small group discussion about the Discord server and using that for our daily meetings instead of GoToMeeting or Zoom. Light talks about pros and cons. Eric, Chuck, John, and I were on the small group meeting.

After that, Chuck and I spent the rest of the time merging in code branches and checking as many pages as possible. Pushed up about 50 new date-picker files.

Chuck and I met to go over progress on the client facing scheduling. We talked about the date-picker project and how big it is getting. After that, Chuck and I talked about new settings for ecommerce time templates. Chuck had some basic visual mock-ups and we talked about pros and cons of what we are thinking and seeing. Lots of talk about doing an MVP (minimal viable product) and also a bigger granddaddy (full blown product or dreaming the dream) - with more look and feel options, functions, settings, and options.

We talked about doing some other prototypes and scenarios. He is going to build out the bike shuttle stuff and then do some rentals or a booking for something - date/times, just a single date (no time), and a date range (multiple dates). Making progress. See attached for a couple small screenshots.

Five of us met and did some brainstorming on the client facing scheduling. At first, we even had Steve on with us and then it rolled into Chuck, Bryan, Sean, and I. See attached for our notes. We decide that there will be two different flavors of client facing scheduling. We will have the single - add new appointment/booking option as one of the flavors. The other flavor will deal more with an event (calendar event or element of time) is already setup and outside parties may participate or join those existing events. We are calling this one the multiple or multi sign-up flavor.

We are still working on all of the tech settings, but we got a good idea of roughly what we are looking for. Great input by all of those guys who were on the meeting. See attached for our notes.

Steve, Sean, John, and I were on the morning meeting. Each of us took a turn and checked in and touched base on what we were doing. Steve and Sean were going over some Cannapages stuff (one of our 3rd party solutions) and what they are doing and offering to some of our clients.

Chuck and his sister Penny joined the meeting. Steve was talking to Chuck and Penny about possible content writing for production and manufacturing. Steve is wanting to focus some efforts there. They were talking about different forms of content (digital, web, print, blogs, flyers, etc.). As they get things going, they will review and make suggestions and then link everything up and make it available. This was mostly a first meet and greet type meeting.

As a side note, it sure takes someone from outside our little family quite a bit to become up to speed and know what we can and cannot do. They, Steve, Sean, and Chuck were talking about using existing clients, adilas power users, and others who can help get the new parties up to speed and following along with our vision. It does take quite a bit of work to get someone fully up to speed.

Emails. Back and forth between Dustin and Chuck. Dustin was doing some testing on some new code changes.

Spent most of the work session working on the bulk flex grid tools. Got into some local testing with some JavaScript to keep track of which fields were modified. Nothing too crazy. Getting back into the project.

Chuck and I were working on the date-picker code. He had another 30+ files that had been updated. We did some local testing and merged and pushed the files up to data 0. We ended up sending an email to Dustin to help us test some of the cannabis specific pages, as Chuck and I didn't have the correct settings or access levels.

We did a quick reimbursement in the system for font awesome (icons). I also invited Chuck to help with the client facing scheduling project that is coming up. He is excited to help there.

Chuck, John, and I chatting and going over upcoming projects. After Chuck left, just John and I spent some time talking about projects (current and up coming) and certain code choices that we are making.

Chuck and I spent some time checking code and merging in the first round of code for a new date-picker and new time-pickers. Good stuff. We pushed up just shy of 30 new files with more to go in the next few rounds.

Helping Chuck with his local development environment. Light debugging. He ended up having a setting on his local database too tight, dealing with group by limitations. We didn't get it all solved, but got him going in a good direction.

Met with Chuck to go over options for a new date picker and time picker. We made a small plan and then started to work through splitting things up into different pages (smaller include files). We did some light testing and then started working through the process. Good little work session. Chuck has all of the new code on his computer.

Small work session with Chuck. The primary topic was code review, testing, and deploying the subs of time page. That is the latest page that Chuck has been working on. We made a few small tweaks and pushed the new file up to all servers.

Sean, Chuck, Cory, Shari O., and I were on a meeting. Shari O. came in a little bit later after the rest of us had started. The goal was to talk about and look at options for creating some industry specific tables and logic to hold bowling ball drilling specs (important pieces for the bowling industry). I was taking notes and the others were chiming in with questions, feedback, and ideas. Good little brainstorming meeting.

Here are a couple of topics of discussion:

- We have some really old screenshots of some bowling specific software that looks like it was developed in the 1980's or 1990's - looks like old windows stuff.

- Talking about options by using flex attributes - (real in-line database extensions). Those are fairly new and are unlimited, but they are only currently developed as a one-to-one relationship (you only get one set of unlimited data points) vs a one-to-many relationship where you could have one customer and they could have many balls or different drill patterns. We would also have to go in and setup these flex attributes per corporation. We went over some other pros and cons there.

- We could use flex grid tie-ins or even limited flex grid tie-ins, but we cap out at 30 custom fields. They can be used as one-to-many relationships and already have a ton of flexibility and features built in. Possible option.

- Currently, one of our bowling customers is using an old school paper type model. They print out a form, fill it in, and then scan and upload and attach it to a specific customer. They can upload as many new images as needed. They could also use PDF, Word docs, Excel files, etc. - using media/content vs photo uploads. These options exist right now at no additional cost, just some training. The downside here is that each photo or scan is not searchable. It exists but you can't search for patterns or combine things.

- We talked about a budget of between $2,000 and $4,000 ish to get a custom project up and running. This would include onsite research, planning, designing, development, and even some reporting. Just guessing without more info at this point.

- We have a number of resources (people in the bowling industry) that could help and guide us. That is huge. We just haven't really tapped into it yet.

- Chuck had some great questions about other service type industries and how they track their repairs and custom jobs - ski shops, bike shops, etc. Maybe look at what it would take to do and/or extend things out to other industries. Good insight.

We closed the meeting and both Cory and Sean are going to poke around with some of our contacts and see what we come up with. As it develops, we may setup other meetings to keep pushing the project forward.

Working with Chuck on the add/edit time (elements of time stuff) page. He did a whole new revamp and added a new look and feel to the main add/edit time page. We spent some time working on both the date pickers and time pickers. We tweaked some settings and added a time picker that could either do just hours and minutes or one that can do hours, minutes, and seconds. Small tweaks and checks (logic) to make the right one show up at the correct time. We merged in the new code and pushed it up to all servers.

After we pushed the code and Chuck left the meeting, I went back and cleaned up and removed a custom black box page for the adilas shop that had some custom code for the add/edit time page. That's a good feeling to remove or get rid of a black box page. They play a role, but sometimes also create an additional maintenance burden. Good stuff.

Worked on a new tool (backend admin tool) for restoring a user's prior permissions. Got on a meeting with Chuck and went over some time formatting and general questions. He is working on the add/edit elements of time page.

Chuck and I jumped on a GoToMeeting session and were looking at a new date picker and time picker that works with SummerNote (web-based HTML editor for custom HTML enabled notes and comments). Good stuff and looking over documentation and making a few tweaks. Light feedback on progress and direction. Trying to standardize things.

Chuck is currently working on the add/edit elements of time page. It is pretty big and pretty dynamic with lots of possible combos and show/hide scenarios based on time template settings. He is doing a snow owl (theme) facelift on the page. We also talked about a number of other fun topics.

- Chuck recommended, for fracture, what about preset color pallets vs full custom colors. We may need both options (presets and build your own custom look and feel color pallets). See a screenshot for a picture to see what WordPress does for preset color pallets. Trying to get ideas.

- As a side note, we currently are revamping things to show different visual displays for the snow owl and classic themes. Lots and lots of extra code and it may eventually effect load and run times. On average, Chuck was saying that we end up with almost triple the amount of code, going from an older original file (just classic) to showing both classic and snow owl theme options. That also translates to more code to maintain and keep updated. Lots of moving parts. When we do the fracture project, we want to make it standalone product. Basically, the old code will support classic and snow owl themes but fracture will only support the new fracture options. Simplify the code that needs to be maintained.

- We talked about using more content and page loaders - using asynchronous loading and asynchronous processes. We also talked about big reports and either using in-line asynchronous loading or doing some kind of build report to file type process. Especially for big or huge files (over 500+ records at a time - say 1,000, 10,000, or up into the 100,000+ records - we have some reports that could output millions of records). If we do a asynchronous process or build to file, we will also need notifiers, emails, text messages, or some other type of push/pull type communication. This may be a nice feature for fracture and future development.

- Going along with the huge reports and data tables, mentioned above - for fracture, we may want to build in the BI (business intelligence) levels and have sums, averages, counts, and other aggregate values right from the start. Sometimes we have users pull 10,000+ records, just to get counts and totals. Let's help that data (the BI level) rise to the top and be available so that we don't have to output and show all 10,000+ records. They may only want the aggregate values anyway. If they want more info, we could allow stepped drill-downs by month, week, day, items, categories, or some other grouping. That will help the record counts be much smaller unless they really want to see all of that data. Once again, we could do the asynchronous or build report to file type process for super huge reports.

- As long as we are talking counts, sums, averages, maxes, mins, and other aggregates for fracture - we really need to think about adding in visual homepages or graphical homepages with dashboards and other quick data references. The details are great, but that is only one of many possible views. We could use calendar views, timeslots views, horizontal grids, vertical grids, grouped reports, details, and other fun dashboard type interfaces. This could include charts, graphs, quick counts, trends, etc. Once again, at the BI level (business intelligence) on showing the data. Allow for drill-downs, filtering, exporting, saving reports, or refining a search if something different is needed. Quick access to the data.

- Push and pull communications - push notification is we (the system) pushed the notification out to the user or group of users (text, email, phone call, browser message or prompt). Pull notification is, you, as a user, requests or pulls certain types of information. Currently, our most common form of communication is pull notifications. When building out fracture, we would really like to be able to define more options for push and pull notification and communication channels.

- We circled back around and were talking about survey's, market research, and asking for feedback before we build the fracture project. As a side note, there really needs to be a plan and then help everybody build towards that plan.

- As part of the plan for fracture, we really want to build out a style guide and get the primary elements in place before anybody else builds the other pieces of the plan. We want it to be consistent, all the way through the build and deployment process. Everybody who then works on the fracture project would be expected to follow suite and follow those plans, guidelines, and style guides.

- Chuck and I talked about checking out competitors and their pricing and then building some marketing based on that research. As we were looking around, some of the other products out there have a smaller starting price but then you have to add on tons of modules or multiple by locations and by seats (active users). We want to pitch the whole thing as a package and then make it so configurable that it could appear small, medium, large, or extra-large. It's all done by settings, permissions, and configurations. Anyways, we really could use some more market information and data before building out fracture.

- Eventually, the fracture part of adilas will need to be its own mini app (fully mobile ready). We may have to scale things back, down, or allow custom configuration options. A full on adilas mini app would be super cool.

- One of our last topics for the day was dealing with costs. We will provide different levels and/or packages that all work and blend together (integrated solutions). If something else if wanted, it will cost and be built out as custom. We love custom and it's part of model. We need to keep that in mind for fracture. With custom, also needs to come cost. Just for fun, Chuck was saying... "I could hand out gold bars on the corner and still get complaints. If they want us to round it out, stamp it, or trim it to make it lighter - we get to keep the gold dust or shavings". We were just being silly but... it's real - custom needs to cost accordingly. That's important. I think that we are getting better at that and really trying to pass on costs and other services to our clients. It has been a learning process. We need our business to make enough money to keep it going. We offer some really great stuff. Our prices need to reflect that.

Great little discussion on fracture (future project - redoing the adilas interfaces and system). I had a bunch of post-it notes with notes on it after the meeting. Chuck really has some good ideas and is forming a vision of what he would like to see the fracture project become. He is great asset. I'm excited to see where it goes!

Meeting with Chuck to go over some time questions (elements of time section). We talked about some formatting issues, how special flags and tags work, and other time questions (as a general topic - time - one of the 12 main player groups). We looked at his current project to redo the advanced time search page and other verbage and layout type questions. Small tweaks to code and pages.

Good meeting - Going over the advanced time search page. Chuck is reworking that page. It is a huge form and has multiple smaller search forms all on one page. He is rearranging them into vertical tabs to show each one separately. That will really help. Here are some of my other notes.

- Chuck would really like to use drop-downs or predictive text drop-down selectors vs open text entry fields.

- Elements of time - very powerful but almost overkill - sooooo much data and sooooo many settings. How can we narrow that down? We talked about a couple of different analogies - cover the walls (imagine all the plumbing and wiring being shown vs a nice looking wall that is pained and has pictures on it), a hood covering the car's engine (style on top and complex and even dangerous below the surface), icebergs vs mountains (how much are you seeing at a time).

- Being able to pull data as needed using things like AJAX (asynchronous data being pulled in just in time, based on user inputs and requests).

- Sort of big and confusing - what does this do? How about that? How can we educate our users without making it look complicated?

- Make the whole thing (elements of time) more consumable - plans for fracture - break it down - Ask our clients and users, how do you use it? Offer preset settings or feature packages - such as: basic calendar, appointments, rentals, bookings, project time tracking, etc. Keep it small and tiny and lead the users along to get it setup correctly and not be intimidated by the number of options.

- Simple interfaces that are to the point and optimized for smart phones, mobile, and responsive layouts.

- Do some market research on how people use it and what they want.

- More dynamics and allow for the users (or preset settings) to change the naming and make it more dynamic. This would be from the top down - what do you call it? What does it do? What is shown, hidden, defaults, etc.? Allow for dynamic naming, layout configuration, and flow of data. At the highest level, almost the data assembly line type concept. If the preset options don't do enough, allow for a build your own layout system (super configurable).

- I mentioned to Chuck that we had some other plans for time templates and dynamic settings that we want to build into the next level (fracture project). See elements of time # 8004 for more details.

- Timing and budgets - sadly, it may take months and years to get all of this done. We have lots of changes that we would like to do. All in good time. Keep floating, watching timelines, budgets, and available funding. We'll get there.

- For fracture, we talked about some sort of education mode. This could be small popup walk through guides, wizards, tutorial helps, or whatever. Along with this, if we show little popup helpers, keep track of what has been viewed and what had not yet been reviewed. Be able to reset if needed.

- Chuck and I also talked about date pickers and time pickers. We looked at a few samples. Ideally, with the new UI/UX changes, we will be able to add both date pickers and time pickers to all pages that need that type of user input fields or selectors.

- The value of a team. We don't have anybody who can do everything to the fullest level. Plus, that would take way too long. That's where the team comes in. We've got backend guys, frontend guys, designers, database guys, coders/developers, project managers, dreamers, admin, and managers. Good stuff! Keep going in that direction.

chuck and I working on look and feel for the advanced time search. Currently, it has a number of search forms stacked on top of each other. Currently there are seven different searches that you can do from the advanced search page. The new page will use vertical tabs and will show each section in a different section. That should help.

As part of our meeting, Chuck and I went over some small tweaks and small code changes that we have made to some of the new pages over the past couple of days/weeks. Small stuff, just trying to keep Chuck up to speed on any issues and trends. After that, he and I touched base on budgets, hours, and plans. Good little meeting.

Working with Bryan to push up new changes for the invoice due dates and options to use individual customer terms to override the new corp-wide settings. Launched the new code, ran new database updates, and pushed up new files to all servers.

Next, we switched gears and spent the rest of the time planning the next steps and phases of the invoice due date project. Bryan was typing and recording the notes and I was spitting out ideas and requirements. We will end up breaking this next step into smaller and smaller pieces. Just trying to get the main brainstorming and planning out of the way. From what it looks like, the next step will be an email history homepage and new email history table. We already send emails for invoices, PO's, quotes, statements, and custom emails. We will start by logging those and then moving on to automated emails for invoice due dates and collecting monies (being silly, in Chuck's terms - the nagatha - email reminders on monies owed).

I'm grateful for Bryan's help in planning out these projects. He also has time to then go in and work on them, that is huge. Time is a rear commodity and resource. If you just have time but no skills, you are stuck. If you have tons of skills and no time, you can't make it very far. If you have both time and skills, you can get a lot done.

Back recording notes from this week and end of last week. I have a list of post-it notes and I cycle through them to transfer from pen and ink to digital. Part way through I was recording some notes on the add limited flex grid settings page. Chuck was reworking that page. I decided to check it out (the new changes). I ended up doing some light re-tweaking of that page to make it work just a little bit better. Small side trip to tweak some code.

Chuck and I did a small work session. We were working on the limited flex grid settings and moving all of the fields into smaller sections and horizontal tabs. Kind of a small dynamic surgery of sorts. Good work session.

Talking with Steve about limited flex grid, status, and where things are headed. He is excited to expose some of the new tools that we are developing out to the rest of our clients. We are also trying to stay ahead of Chuck and what pages he is redoing and making them look better. That lead us into some discussions on layout and display options such as tabs, accordions, pop-ups, modals, and other modern display and layout styles.

Everything keeps going back to settings. We talked about 4 different level of settings, that we are seeing. They are: 1. Corporation level settings (corp level or world level), 2. Group or player group level settings (12 main players), 3. Page level settings, and 4. User level settings. As a side note, settings are awesome, but they can also make things feel like it is more complicated. You have to play the game of iceberg vs huge mountain. Hide what you can, only show what is needed, but still make it available if needed (like tools in the shed). We see more and more of this type of thing coming as we build out toward fracture and future development.

Another fun thing that we talked about was page views. We happened to be on the time homepage and going over different page views of the same data, but how cool would it be if we could build out reports that show up in calendar view, timeslot view, grouped or aggregated views, or normal details and tabular data type formats. So many options, including charts, graphs, and other layout options. Not to mention, export or save custom report settings. All available, we just need to keep bringing it all together. More stuff for fracture.

The next subject was dealing with getters and setters and how those pieces are so dynamic. Some of our entries have 30-40 fields or choices. We don't want to have to submit all of those pieces, every time, for a simple update. Getters help you get the data in smaller pieces, as needed. Setters help you set or update the data in small bitesize pieces. For example, say you have 30 records of flex grid, each with a possible 40 columns. If you do the math, that one bulk edit page could have over 1,000 fields. What if only 2 pieces of data actually change? Using a simple setter allows you to only alter smaller pieces of the whole without having to carry the whole load. Efficiency!

As we were talking, we can see the value of using small teams to push on projects together. That could really help with resources and giving everybody a buddy to work with. Along those lines, here are some other projects that we may give to Bryan or a small team of developers. Flex attributes for all of the main players (used to be called in-line database extensions), vendor/payee logs (modeled after the customer log section but for vendor/payees), and other projects that already have a small handrail or guide. Anything that has been done before seems to be easier, due to the example or handrail for the developer to follow.

Working with Bryan on updates on the custom shopping carts and adding in the options to record the invoice due dates. Running some tests and merged in some code. We then switched gears and started planning the next steps. See attached for our work document (brainstorming of ideas).

After that, I was texting back and forth with Chuck on setting up limited flex grid stuff.

Back on with Bryan. Checking over code and making changes. Passed him over 10+ files to check. Doing emails and looking over code from Chuck on the add/edit flex grid page. Pushed up Chuck's new files. After that Bryan and I pushed up some code and did some live testing on the invoice due date project. Making progress.

As part of our meeting, I was explaining to Chuck about our invoice due date project. He had a ton of good ideas and we talked about options to combine the invoice due date with automated reminder emails and what not. Great ideas. This is just for fun, but he said that he used a different product and it had automated reminders. He got more responses from the "nag" (automated emails) than he did by asking for money. As we were talking and joking around, he said, we should rename our automated email stuff "The Nagatha" (one-off from the nag). Just being silly.

Once we got back to normal work, we spent some time looking over the flex grid stuff. He is working on the add/edit flex grid tie-in page (rework and page facelift). We also spent some time talking about different questions, ideas, and styles. Those conversations included topics and discussions dealing with taking heat on making changes and adding a more modern look and feel (getting in trouble for making things look better). We have a lot of users who don't like change and we are constantly rolling out new changes, tweaks, and refinements. That's how we roll.

We spent some time talking about things that need to go in the adilas docs (internal snippets and style guide). We also went over some testing and talking about adding in tons of client-side validation (JavaScript) for fracture. We also talked about the value of doing small prototypes and how much we can learn by doing those little mini apps. As a side note, Chuck is really excited about fracture (future project in adilas) and has a number of great ideas and vision. Almost every time we talk, I hear him throw out a ping or a reference for planning and building out fracture. We'll get to it... it just takes time and resources, but the vision and dream are out there. Let's go get it!

On the morning meeting with Steve. We touched base on the discount engine that John is working on. I was with John yesterday for over an hour and half looking at the code. There is a lot going on there. Good stuff and making progress.

Steve wanted a demo of where I was at with the bike shuttle company and some of the custom scheduling and booking tools. I showed him the progress, including the bulk add limited flex grid tools. I showed him where I was at on the bulk edit flex grid tie-ins tool and how cool that will be. We also jumped out in ecommerce and talked about the client facing scheduling options that we want to add in. I've got a few more internal tools to work on and finish and then I'll roll outside in ecommerce and work on the client facing scheduling options. Marisa joined us and expressed that when we get to the planning and design portion of that project that she and Chuck would really like to be involved. As a fun side note, this will end up being a precursor to the WanderWays project (campground, cabins, and other scheduling options).

Part of my role is to help share the vision of where we are heading and how to get there. I've got some of the other guys and gals building it out, I just need to keep helping them see where we are heading. As a fun bonus, they catch the vision and then add more to it. That makes it really fun.

Steve and Marisa were going over some Metrc syncing and Metrc training. There are tons of options built-in to the adilas platform. Pretty cool. After that, they got into a training session on how to deal with samples and how to bring them in, sell them, and account for them. Steve was showing Marisa how to treat them similar to normal inventory items. Next, they got into a small internal training session on using update PO's to help with inventory updates and adjustments. That lead to a conversation about how important dates and date sensitivity is when dealing with inventory tracking. There is value in being in a real time inventory management environment.

The last major topic of the morning was dealing with the value and need for education. We have all kinds of tools and some that are light years ahead of the competition. However, if we don't teach our users how to use them and if they don't know about them, then they can use them. There is a real need to train our internal staff as well as getting our clients trained up and using the correct tools. That is a challenge but also an opportunity. There is real value in a power user, someone who knows adilas backwards and forwards. They are needed and in demand. There is real value there.

Chuck and I looked at code and merged in two small branches. One was for credit card payments (manual or swipe). The other was for date pickers on the main flex grid tie-in homepage. Once we got those things merged in, we chatted about some other stuff. We talked about home office layouts, ergonomics, standing while working, and other hobbies and pastimes.

Chuck and I testing and going over credit card readers and the credit card payment page. Chuck was giving it a new look and feel (small facelift). We did some testing and Chuck is going to make a couple of changes and then we will push it up. We are going through things, one page at a time and trying to upgrade the look and feel to match a more modern theme.

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.

Chuck and I going over things. We were talking about some of our leadership experiences and how the variables of the group can really change things up. We touched base on some projects and then switched gears again. We ended up talking about taxes, government programs, people being left behind, advancing technology, career changes, and ways of working together. If you make it free, people tend to keep expecting free stuff. We've even seen this with some of our adilas clients. There are some challenges there. Always in search of that balance. Affordable yet reachable.

On a quick meeting with Chuck. We looked over some code and merged and pushed up some changes. This was on the parts usage page. These were some requests from Kelly and Cory. After that we looked at some of his other projects that he is working on. Small little session.

Shari O. jumped on the meeting and just needed a verbal consent for the bank to use a debit card for a foreign transaction for one of our vendors.

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.

Meeting with Chuck and going over the mini calendar pages. I had to bail out to go pick-up my daughter. We got back together after I got home and pushed up the mini calendar. We did some testing. Actual times were 10:00 to 10:15 and then 10:45 to 11:15 am - total of 45 minutes - with the break in between.

On a different note, I'm excited to see where Chuck goes with some of his other designs and web components that he is working on. He is working on a possible web component to make a custom date picker, that we could use, even for other projects like fracture. Ideally, the more we create our own little custom web components, the better. Less outside libraries and dependencies. We'll figure out a good mix. Good stuff.

Jumped on a GoToMeeting with Chuck. We reviewed his progress on a mini calendar app inside of adilas. He is still working on some of the pieces, but we will most likely push up what he has and then go from there.

After Chuck left, I tried to spend some time and update the developer's notebook from the past couple of days. When things are happening, it is super hard to perfectly keep up with things. Especially if you flip flop from meeting to meeting or task to task without anything in between. I have found that a quick post-it note goes miles. I can scribble down a thought, and then go back and fill in the details later on. If I don't do the initial scribble, while it happens, I lose it. The information and happenings are still there, I just can't recall what the different topics were. I'm a big advocate for writing things down.

Small sales meeting this morning. We started out and Maris was showing us a new ad for a magazine that she is working on. Chuck and I talked with here a little bit about print specific stuff. Basically, print and web are treated differently, from color options to dpi or lpi (dots per inch or lines per inch). Print is, and/or can be, much more technical. You have to be careful.

Marisa and Sean were asking about the High Valley Bike Shuttle and progress there. I requested that Marisa help me reach out and get them all trained up and going. The conversation ended up with a marketing twist and what else we need to do and to help push these things along.

Esperanza (Hope) joined and wanted to do more person-to-person events and network marketing. She was pitching ideas and Steve and Sean were fielding questions back and forth. She seems to have a lot of energy and wants to get out and about more. It seems like she wants to be a promoter type person and help with events, meetings, and social type interactions and marketing. She, Steve, and Sean will get together and talk about ideas, budgets, and expectations. The goal is to get more demos.

Chuck and I going over booking and scheduling ideas and things. He has some Pinterest galleries that have some cool calendar and time view widgets. He is somewhat collecting some samples and organizing a small gallery out on Pinterest to help with some research on date pickers, calendar views, time views, scheduling widgets, and calendar stuff. We talked about a new dynamic date picker that he would be willing to build. If yes, we could cascade it throughout the whole adilas site. That would be really cool. We already have a date picker on some of the pages, but not on all of them (there are a ton of pages that could use some loving).

Sean and I looking into the older code from the Leafly integration (back in 2019) done by Will Hudson. We were somewhat going through some of the pieces and virtually reverse engineering what we saw (looking at existing code and trying to figure it out). Basically, what was built by Will and what did it do?

John showed me some stuff on his discount engine. We were looking into a CSS (display) issue. We decided to wait for Chuck who would be popping in on the next meeting.

Just recording an idea, but what if we had Bryan help us out with some training and education stuff. We are really lacking there. Bryan could build it and then we could have Chuck make it look nice. Basically, Bryan could help with content and Chuck could help with presentation. There is a huge need for training, flow, processes, SOP's, etc. Also, just another idea... What if we put Bryan on a project to see if we could write a grant for building out fracture and where we would like to take it (huge future project in adilas and revamping the whole system). That might have some merit. We could really use some major funding to push that whole project forward. I know that Bryan has written other articles and/or research papers. Just a thought.

If needed, we could use the adilas developer's notebook to do more research on the whole fracture project. Lots of notes and ideas have been posted and pushed up to the developer's notebook over time. A great resource. A lot of it ties in with the adilas cafe and community that we are trying to build. We also have tons of R&D (research and development) on new UI/UX stuff from Jonathan Wells. Lots of great little ideas and such. Good starting point.

Chuck was on the meeting asking about calendars and goals and vision for elements of time. Cory and Bryan jumped on and we checked on a bug with some code that got pushed up earlier today. We got it fixed. I was really happy that we had such a quick reaction and were able to make the changes and push up the fix so quickly.

Demo and training session with High Valley Bike Shuttle. They had Drew, Jim, and Lanette on the call. We had Chuck, Sean, Marisa, and me from adilas. Good call. It went about an hour and 45 minutes. Lots of information to cover. We did record most of it, see attached if you are interested in seeing where things are at currently. Lots of other pieces are planned and in the development stages. Once the meeting ended, I wrote down a couple of ideas and pushed up the video. 

Chuck and I pushed up some changes. We then talked about investments. Lots of talk about annual returns on accounts, actively managing the monies and possible investments. Basically, what are the benefits of having another special account for retirement or savings? We talked about possible withdrawal rules such as any amount that is greater than or equal to $1,000. Basically, if we had another account, if you have $20K in that account, you could grab what you wanted, but you could do something like $100. It would have to be greater than or equal to $1,000 minimum ($amount to withdrawal needs to be >= $1,000).

If there was a bunch of money, you could do all kinds of stuff. Our current goal is to create and capture small drops based off of the reoccurring revenue model. We could open up other options later on down the road. We also talked about who may want to help manage and help monitor this account or business entity.

Working with Chuck to get the multi file upload page live and online. Added the spinning loader gif to the page to help show activity. Pushed up files live on all servers.

Morning sales meeting. They were checking in on email campaigns. They were looking at getting better calls and follow-ups. Steve was saying that we keep testing things, going through phases, and trying different things. Basically, small or little experiments on sales and promotions.

Chuck and I talking about 3D printers. Chuck and I going over the media/content multi upload page.

Steve and Sean were talking about custom gram controllers and ways to setup certain settings to make it super flexible. As they were talking, I was thinking, yes, it can do it but we will need to train our people on how to use that. Often with complexity comes the need for more education. They seem to go hand in hand.

I was reviewing notes from a meeting with an unemployment auditor about employees and general employer stuff. We are trying to make some changes in how our business is structured. Good stuff, but also a challenge.

Cory and Steve were going over 3rd party solutions and dealing with them. It is kind of a bitter sweet relationship. They keep popping up all over the place and some of them expect us to virtually carry them. It can be a challenge.

On a different note, we keep circling back around and talking about Stripe and ways to possibly integrate with them. They seem to be a very good and valid merchant solution. Marisa and Sean were going over Metrc invoice syncing and tips and tricks to make things sync up.

After that, Chuck and I worked on media/content files and code review. We tweaked a few files and pushed them up to the adilas content server. Chuck and I started chatting about rules for 1099's and sub-contractors. We reviewed some of my notes from the meeting with the unemployment auditor. Just for fun, Chuck was say, why don't you move where the business is based out of to a more tax friendly state. I never would have thought of that. We don't plan on moving, but it was an interesting angle. Almost a business decision based on tax friendliness - kinda interesting.

Chuck and I were talking about using setup wizards and easy setup steps to virtually walk people through complex or involved processes. We covered a bunch of different topics today. One of them was MVC or model view controllers and how splitting things into different levels allows for more modular code. The thing that changes the most is the view model (display). The other pieces tend to stay fairly similar without huge changes between versions. Chuck would like me to speak with his wife about some of those different levels and some tips and tricks on keeping them separate. She worked with a client that does government work and they were setup with really good deafferentation between data layers, business logic layers, and view or display layers. She is also familiar with a number of different frameworks and possible options there.

As we were talking, Chuck said that one of his goals is going to be working on layouts, use of whitespace, and number of clicks to get something done and finished. Those sounded like good goals to look into and work on for adilas projects. Next, we chatted about navigation, layouts, and the concept of an artist with a pallet and being able to change the layout and control your space (work environment). Sometimes the word space is too deep for people to grasp. They think of stars and constellations. We are currently talking more about personal space and configuring your own environment or working space (homepages, nav options, preferences, dashboards, etc.). Chuck would love to help develop some really cool dashboards and such. That would be awesome.

More talk about wizards and easy bulk setup options. We would love to configure some almost hands-free setup options. Think of what a cost saving this would be. Basically, if we could make the setup easier, we could eliminate some large costs and time savings by letting the users set it up themselves. That is still a long way out, but a great goal. Along those lines, we were talking about how both settings and permissions really need to dictate displays, options, and work spaces. If we did it well enough, we could even offer a free trial or something along those lines. Right now, it takes too much to setup it all up and get someone trained. We can't do it for free because it takes someone who know the system to setup it up, configure it, and get the people trained on it.

If we could get things done in bulk or through simple handholding wizards, that would really help the process. Those handrails or wizards turn mountains into smaller icebergs (perception of what is there to take in or acknowledge). We talked about some possible mini apps or standalone modules for the current adilas platform. Timeclocks, timecards, uers, payroll, expense tracking, point of sale, CRM (customer relationship management), ecommerce, etc. All of the main 12 business functions. Fun little meeting and some good ideas. We would like to include and even start working on the fracture project with some of these ideas. That is and has been a big goal and driving force for what we are doing. What is the next step and how can we get there?

A bunch of the guys were checking in this morning. Eric needed some info and direction on a driver license scan project. Alan checked in on the enterprise level parts categories and category images. Chuck and I did a small code review and merged and pushed up a file for adding media/content (files). After that, John and I looked over some small payroll changes for states and allowing for timecards without fully allowing for full payroll options. Mostly a small work session this morning.

Chuck joined Sean and Marisa on the last little bit of the other meeting. We were going over financials, accounts payable, and accounts receivable. Lots of fun showing numbers and some of their trends. Lots of drawing on the screen.

Both Sean and Marisa had to bail out and so just Chuck and I kept going. We switched gears and talked about the add/edit media/content pages that Chuck is working on (small page level facelift on certain pages). We also briefly talked about maybe using a JS framework (JavaScript) for the next version of adilas. Eventually, we really want to allocate some time, funds, energy, and resources to work on the fracture project. We are hoping that that could be part of our plans going forward. Even if it is a little bit here and there, we would take it and run with it. One of our first main goals is to create a plan and then be able to pitch the pitch. No new code, just mock-ups, requirements, prototypes, and proof of concept stuff. We really want a great plan and then to be able to do and build what we are hoping and dreaming about.

Along those same lines, Chuck was talking about making sure that our application has multiple layers. The database level (dao's - database access objects), the middle layer (business logic, models, and services - object oriented pieces), we then need an interchangeable display or show level (visual wrapper, themes, custom, or even white label options). If we build it out that way, the 2 lower levels could be almost untouched, even if we had to redo the upper or display level. Sometimes that is called the view level. It goes deeper than this, but an older acronym is MVC (model, view, controller). There are more modern versions of that now, but that is all that would come to my mind as I was recording this. Long story made short, keep the data, logic, and display levels as separate pieces and you are heading in a good direction.

Marisa and Sean were on the morning meeting. Marisa wanted to get some information on the PO line item rounding project and how that affected recipe/builds and internal build PO's. We went through a number of scenarios, and I showed her and Sean what the new force to $0 buttons and the line item rounding function does. We talked, drew some flow and training things (online meeting and drawing tools), and spent a good 25 minutes going over all of the ins and outs of that feature.

Next, I asked both Marisa and Sean if they had heard anything about the possible switch to a multi member LLC. Both of them said no, so we went into a good 45-minute crash course. We covered K-1's, 1099's, W-2's, etc. Lots of other ideas and concepts, dealing with our move to a multi member LLC with more owners and splitting up some percentages. I was having fun explaining things and I hope that they were enjoying it as well. We were looking at reports, getting numbers, drawing, linking things together and hopefully making sense. Anyways, good meeting and we went over a lot of ground and territory. When we finished, Chuck had joined us as well.

Working with Marisa on parts and part category images. She is going to get with Alan later on. Small to do list stuff. Emails and recording notes from this morning. Lots of notes from a meeting between Steve, Chuck, and I earlier today. Back working on the copy chart of accounts project for Cory.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

- Our model is built on a reoccurring revenue model.

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

- Possible bonuses based on profits

- Birthdays and extra flex time - just having fun

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

- There has to be accountability of each person

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

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

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

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

- Huge team effort - communications - community effort

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

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

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

- Sufficient for our needs

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

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

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

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

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

Chuck, Steve, and Sean were on when I joined. They were going over a number of different things. Sean and Steve started going over some of the BioTrack API and small issues. Marisa, Alan, and I started working on the parts categories and the upload for images and photos for ecommerce. Alan was able to find the error and got it fixed. After that, Steve and Alan were going over more of the BioTrack API socket endpoints. Marisa jumped back on and we made one more small fix for her on the part category stuff.

Next, Chuck and I got into some questions on the add/edit media/content pages. He is working on a revamp for that page and section. He was working on the add mode, but his question was actually part of the edit mode. I got him pointed in the right direction.

Emails and reading an article on a 30 hour work week. Chuck gave me the article to read.

Looking over code and visual stuff with Chuck on the upload media/content pages. Small work session and going over a question and answer stuff dealing with layouts, logic, and backend code. We then looked into the new system error messages and custom error page. We did some testing on a live server to make sure that the ColdFusion mapping for the image path was working. We tested in multiple file/folder combinations.

After that, we switched gears and started talking about multi member LLC's and options to go along with that. Chuck had some great ideas and comments. He has done some of this kind of stuff before with some of his other businesses that he has had. I was taking some notes as we were talking. Here are a few of my rough notes:

- On hours per week, maybe get a range between x and y vs a hard fast number like 40. For example: 5, 10, 15, 20, 25, 30, 35, 40, 45, etc. A range might be between 25 and 30 or between 30 and 40 or whatever. The range gives some flex but also sort of sets a min and a max. There may be weeks that they win and weeks that we could win (how many hours worked).

- We need our guys and gals to report back and let us know how many hours they are working. It would help with budgeting and could be tied to bonuses and games.

- Chuck was saying that per month, the average is 2 days off or 16-20 hours a month of vacation or sick time. Just talking some rough numbers.

- We chatted about bonuses and other perks.

- If giving out ownership percentages, we could have a virtual sign in/out option on those percentages. This is a way of freely trading the percentages without getting into all kinds of buy it back, pay it out, figure it out stuff. Set it up where we could assign a certain amount of ownership on a contingent type basis, then if all goes well, they keep it or it gets added on to. If it doesn't work out, we could get it back without any other trading or negotiating. Almost like ownership on loan until fully given. Just ideas.

- We talked pros and cons of a 30 hour work week. See this online article that covers a few of the ideas and concepts of the 30 hour work week. Just playing with ideas.

- Conversations about burnout and reasons for burnout

- Reporting back on hours per week or per month. Just for fun, we were talking about a goal per week and then setting maxes and mins per month to allow for some flexibility.

- What about overages - people who work extra hours? Maybe goes into extra vacation time or flex time. That would not alter any budgets as they would get a specific salary but may be able to add up some other bonus or perk. The other option was to pay a rate of x for any overages. We talked quite a bit about rewarding or awarding the over workers. That is not really the goal. Ideally, we would have our guys work less, be sharp, and want to play along.

- We talked about flex time and flex time usage. Allowing things to stack up and then use it later. We would need a way to record and keep track of that. Kinda like tracking paid vacation time in normal companies. For us, we could use something over in special accounts (section within the site). Just a thought.

- Chuck's dream is a 30 hour work week but being paid on the 40 hour rate.

- Setting expectations

- The cost of moral for our team - what does it take - what do we want to do (culture wise)?

- It would be great to setup a meeting with our CPA or accountant and get some training and education on tax implications, write offs, rules, tips, tricks, etc. Educate us as owners, sub-contractors, etc. Along those same lines, if there were write offs, would they be against adilas (as a company) or against our own companies or businesses?

- What about ongoing contract work for 1099 folks with an official business of their own? We would like to explore these options more. Instead of ownership, just straight sub-contractor work and what not.

- Advice from Chuck - hire a good accountant and then listen to them!

- Light talks about normal 1099 guys or 1099's to a company. Where do you get more possible write offs?

- What about forcing new comers to do a trial period via a 1099 company? Also, maybe a renewal period on the 1099 contracts? If we like what we see, we could offer or move that person or company to more of an ownership type relationship, as we see fit.

For the record, Chuck has a bunch of good ideas on taxes, businesses, and business structure. I was impressed. I sent Steve a text and told him that we may want to chat with Chuck about more options and ideas for our move to change the company structure. Good stuff!

Marisa, Chuck, John, Sean, Steve, Shari O., and I were on the sales meeting. They were talking about their email campaign and making follow-up calls. Steve wants to get a ballpark figure as to how much that email campaign is costing. We would love to get a rough idea on the client acquisition costs for different industries that we serve. Chuck and Marisa were reporting on how they go in and search for contacts, numbers, emails, and build their own lists. Once we do that for a bit, we'd like to try buying a list of contacts and see which one is more effective. Basically, we are stirring the pot and virtually going on a fishing trip. What is out there?

During the meeting, the question was brought up about current sales rep type persons. Checking in on different names, people, and who is doing what. Sean had some good info on some of the folks.

After the sales meeting, Steve was asking John about some of his projects. Trying to help our guys focus where possible. After that, Steve and Sean were talking about a live system deployment where Sean is going to be going onsite to help with the full setup and deployment. The client has pre-paid for 20 hours of training and will be covering all costs to pay for Sean to be onsite for a couple of days including airfare, lodging, etc. That is awesome! We are really trying to recoup our costs with some of our new clients. On average, it costs us about $2,000 to get a new client on and going on the system.

Steve and Sean were going over ideas on text message marketing and some possible marketing options. We are going to be trying to market more and more of our own professional services such as training, setup, data entry, deployment, maintenance, and consulting. We are really excited about that. One of the missing pieces is who is coordinating things and helping to orchestrate the sale and the deployment.

Switching gears to merchant processing, we really want to figure out a standard procedure there and help get our clients setup with great rates and excellent service. We have tons of options, but we really want to focus in and offer a standard package. Part of our missing link right now is info from the merchant processors as to what kind of accounts and services are available.

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.

Chuck and I going over the custom error page that he is working on. We also talked about fracture and options of building new vs morphing existing into what we want. There are pros and cons of both choices. Just for fun, Chuck and I were saying that is would be really fun to get a small prototype team like Chuck, Russell, and I or something like that and let us work on fracture while others kept up the other system. Dreaming... :)

We also spent some time talking about different page views and where we are heading with scheduling, booking, rentals, and reservations. We really want to circle back and update elements of time to handle the things that we will need going forward. This entire section seems to be heating up and we want to stay on top of that. Good stuff. Dealing with views: We want to improve calendar views, horizontal time views, vertical time views, and other display views that will be fun and useful tools for people who schedule or deal with time as a resource (billing, selling, or booking time).

Chuck and I spent some time going over some code and making some small fixes and tracking down a small bug. Chuck had a nice fix all done and ready, but I didn't know about it (miscommunication). We did his little fix, checked a few other things, and got it pushed up to all servers. Much easier than what I originally thought that it was going to take.

After that, we did some talking about the adilas UI (user interface) and some pros and cons of what we have to work with. We also got pretty deep into the calendar interface and dealing with elements of time. That project was originally done back in 2011 and is heating back up again (needs some new features and functionality and a newer look). We chatted and talked about some calendar and scheduling options. Along with that, we also talked a little bit about estimates and guesses on time/money that it would take to revamp certain sections. Just chatting (for now).

Our little conversion went into budgeting and how we often overshoot, or the projects get under bid, and we overshoot things by miles. That ends up translating to adilas taking the extra costs on the chin and having to shoulder those loads. Chuck was expressing that he thinks that our clients sometimes take advantage of us, and we get the short end of the stick. We also went over a small list of future projects and what else is coming down the pipeline. Lots of moving pieces.

John and I were touching base on his scratch payroll page that he is working on. He is finishing things up and will be moving all of that code over into the live code pages. Good review.

Cory joined the meeting and wanted to show me a bug. We looked into it and ended up trying to compare files for what worked and what did not work. We found a few small issues but we weren't a hundred percent sure how to fix them. We made some notes and recorded line numbers and that's about as far as we made it. Chuck joined the meeting and Cory had to leave, so Chuck and I took it from there.

The Tuesday morning sales meeting was going on this morning. Marisa and Chuck were both presenting and sharing. They were talking about the scheduling side of adilas and how that would be cool to keep building that out. See this link for some other ideas on both horizontal views and vertical views for scheduling and elements of time. That link also has access to a small 2.5 minute demo video showing elements of time and some custom work that we did for Beaver Mountain (ski area and their snowsports school lessons).

Chuck and Marisa were also reviewing some recent email campaigns for trailer dealerships. They were looking at stats and how many emails had been opened and viewed. They were also talking about other places to advertise and connect with business to business software people and clients. Just looking for ways to advertise what we have to offer.

After the meeting, Steve and I were briefly talking about ecommerce and how it is going to be super important that our clients can sell all of their products and services. This includes normal inventory items, different services, and time (bookings and appointments). They all need to be able to be sold from the same ecommerce interface. You can tell that some of that is really heating up and there is a demand out there for it.

Alan and Dustin joined the meeting and we were going over units of measure and a possible variable casting error. John chimed in and recommended an Adobe ColdFusion update that might fix the problem. They spent some time looking into that.

Tuesday morning sales meeting. Marisa, Steve, Sean, and Chuck were on the meeting. Shari O. joined a little bit later on. They were going over email campaigns and planning some follow-up calls. They are just starting that email campaign for trailer dealers and dealerships. They were going over some planning and logistics. Lots of talk about using the existing adilas tools to help them track touches, contacts, quotes, invoices, and billing for time for deployment and other time-based services. Good stuff.

I saw some great communication between different team members and all being on the same page. They will be doing some internal training on elements of time, billing, and what not to make sure that they are good to go.

The last topic for the sales meeting was Marisa asking Steve, Shari O., and I about the floorplan application. Originally, we built that section of the site back in the Morning Stat Automotive days. We were reviewing some things and giving Marisa and Sean a general overview. They are going to be setting up some other internal training sessions to fully get their heads around it.

After the sales meeting was over, Marisa had some questions for Steve and Sean about custom gram controls and other logistics for a demo later today. We also went over some inventory controls and being able to update inventory counts and inventory management tools (update PO's, delayed scanning, etc.).

Chuck and I talked and went over budgets. We talked about global CSS changes and pros and cons of that approach. Ideally, we'd love to almost start over from scratch and build it up like we would like to, with a plan, a design guide, a style guide, and a bigger vision of the whole. Almost to the fracture level, when possible. Currently, we have a system that has been rewritten multiple times and we keep adding on to it. That isn't bad, it just could really use some more master architecting or bigger overarching planning and style guide type approach stuff. It would make it more cohesive as a whole. Build with the end in mind. We can see so much further down the road than we could when we started. We would love to translate some of that vision, pain, needs, and goals into what we build going forward. It's been quite the journey.

We looked at code and went over some feedback from users on the other branches that are still out and needing to be finished. We still have the parts homepage, the advanced parts search, the customer queue, the customer homepage, and other small pieces still hanging out there. Good discussion on raising monies and other ideas. Merged in some code and pushed it live. More email stuff at the end of the meeting.

Small fixes on a custom report for a client. Merging in some code for Chuck on the view parts page. Small fixes for RFID tags and sub attributes on the view parts page and the sub inventory tab. Started working on a fix for Marisa on ecommerce images and setting up default logic based on actual images, item defaults, and category default images.

Tuesday morning sales meeting. Marisa, Sean, Steve, Chuck, and I on the call. They were reporting on email campaigns and coming up with a deployment check list. They are getting pretty deep on the checklist and Marisa is sort of heading that up. They also brought up the presentation gallery and some of the new dealership themes that Chuck added in. That should really help. If you get to the presentation gallery, you get to the custom themes (custom backgrounds) by clicking the menu in the top right corner.

We got into flyers and wanting to revamp things. That would be really cool. The next subject was dealing with merchant processing. Tons and tons of discussions around that subject. Towards the end of the meeting, they switched over and Steve and Sean were going over Metrc stuff.