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, 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

Reviewing the document that Suzi made for some simple step-by-step instructions. Looks great! See attached for the file. Switched over to doing more documentation of the AI quick search prompts, keywords, and options.

Documentation and recording notes for keywords, options, and prompts for the AI quick search. Got a small PDF from Suzi with some step-by-step instructions. I briefly went through it and sent her back some quick feedback. Great start, just need to tweak a few things. Jumped back to filling in information on the AI quick search prompts page. Pushed up new files. It is rough, but we got small descriptions on all AI quick search prompts.

Working with Bryan on AI keywords, options, and prompts. Bryan reached out to Suzi and we checked in with her. Lots of planning. We want Suzi to help do some step-by-step guides to help us show user scenarios inside of the adilas POS (point of sale system). We wanted her to do at least 10 scenarios from super easy to more complex.

Working with Shannon and Suzi. Started out with Shannon. We were reviewing some progress on the AI quick search. We did some testing and made a few small changes. Talking about the need for documentation. Suzi popped in and we went over some instructions and direction for a project she will be helping with. She is going to be making some screenshots and documentation on how to run simple POS (point of sale) functions inside of adilas. After Suzi left, Shannon and I went back to working on rough content for adilas lite - fracture plans.

Suzi jumped on with Shannon and I around 12:30 pm vs 11:30 am. I probably wrote it wrong in the email. We got it all figured out.

Text messages, reaching out to a client, then typing up some directions for Suzi to help us build some scenarios and user stories for the AI agent to follow some directions and instructions. Other emails and trying to do some follow-ups. Lots of moving pieces.

Work session for the Benning construction site. Added a new top header logo. They provided a nice flyer. Took a bunch of the images off of the flyer to rework the header graphic. Working on the custom code to help with the donations page. Had to open up the pricing field. Meeting with the construction company and Bryan and Suzi from the adilas team. Quick meeting. We are getting closer. After the meeting, then working on a small to do list of items. Small cosmetic stuff.

Meeting and follow-up with the Benning Construction company. They are going to be using adilas to run a golf tournament later this Fall. We went over progress and made a few small assignments. Making progress. Good stuff.

After the meeting, Suzi, Bryan, and I talk about plans and went over assignments.

Meeting with the Benning construction company to help with their golf tournament. Touching base, showing a quick demo, and asking some questions. Bryan and Suzi were the main adilas contacts. A lady by the name of Jessica will be the contact on their side. Bryan sent them an email with information requests. We setup a meeting for next week to touch base. They need some of it done by mid-July and then the remainder of the site done by September.

Recording notes and looking over a PowerPoint slide show that Suzi sent to me. We really need to spend some time, money, and efforts on marketing and creating simple visuals and screenshots of what we are doing and offering. People are interested in what we are doing but they need to see it to really help them figure things out.

HOA (homeowners association) demo with Suzi. It was just the two of us. We had a few other people pop in/out pretty quickly. Anyways, Suzi gave me the demo and we went through a bunch of things. Kinda a practice run of sorts. Suzi had everything prepped. She covered ecommerce, paying dues, requesting services, and getting to links and paperwork. We then jumped inside of adilas and looked at reoccurring billing, tracking expenses, PO's and inventory, payroll for any employees, financials, etc. We talked about scheduling and how to help these people track their different needs (rentals, home visits, work projects, etc.).

As we were talking, we wanted to make a note about adding in a public facing calendar. We have a great internal calendar. We just need to push it out as a mini version for our clients to use as a client facing calendar view. This would be some new development. We know that the need is there as it has been requested a few times.

Suzi and I then got into a small PowerPoint presentation that she had made. See attached. We jumped into the presentation gallery and clicked around. I showed her some cool new features and what not. We have been making some changes there. We need more pictures and ways to show off what we do (a good mix of visual eye candy and light education). We would love to make it so intuitive that people could virtually follow the picture story. People really seem to respond well to good pictures and screenshots. Good little meeting.

On a Zoom call (demo) with Bryan and Suzi and HollyJo from Richmond city (Utah). Suzi was doing the demo. She had some open tabs to help speed up the demo. She started in on payroll options. She was showing user profiles, templates, permissions, and such. Talking about clocking in/out and how to do that on their phones, using a small mini app. Next, she jumped into different reports and how to navigate around. After that, she switched over to showing some scheduling for parks, practice fields, pavilions, and library reading times. HollyJo has a number of needs for project time tracking. We went over a few options there. Quick but a good demo.

Had to postpone the demo. She got pulled into another city project/meeting. Bryan let Suzi and I know about the change in plans before the demo.

Emails, light tech support, and meeting with Shannon. Also working with Wayne (briefly) and looking over some automatic email code. He jumped on the GoToMeeting session with Shannon and I for a bit. Once we were done, Shannon and I went back to working on things. We made a plan for Thursday. Light tech support and changing some settings for Suzi.

Light plan for working on the presentation gallery. We have 4 main topics, about 50 slides (pages), and we want to work on each section, one thing at a time to make sure that the site seems cohesive and works as a group.

Presentation Gallery
link - https://news.adilas.biz/sales-gallery/adilas-advert-index.html

Business Functions
- Solid bullets - Make sure that the bullet points are good and solid
- Top Level Modals - Make sure that every page has a top level popup modal description
- Sub Level Modals - When ready, make sure that each bullet point has its own popup modal description and images (or videos)
- Images and Refine - Go back through things and make it look really nice, tight, and fine-tooth combing of the data and content.

Application Players
- Solid bullets - See above
- Top Level Modals
- Sub Level Modals
- Images and Refine

Attributes
- Solid bullets - See above
- Top Level Modals
- Sub Level Modals
- Images and Refine

Core Concepts
- Solid bullets - See above
- Top Level Modals
- Sub Level Modals
- Images and Refine

Starting on Thursday we want to go back through each one at the top level. Review the bullets we have done (business functions and core concepts) and look to what needs to happen for the Attributes and Application Players.

Emails and recording notes. A quick phone call with Suzi to talk about POS cashdrawers and settings.

Meeting with Bryan and Suzi. Dealing with Lucky Puppy stuff (planning and figuring out where we are at). They really want options for docking (virtual copy and paste board for their appointments), drag-and-drop, multiple relationships (owner to pets, pets to rooms, pets to other assistants), popups and rollovers (showing sub details), splitting tips, etc. Suzi showed us some log info under the customer log that she had added. I was really glad that she did that. I had forgotten a few things. She had log notes, screenshots, files, documents, and other stuff. Bryan and I will get together and do some planning and then we will circle back around after the first of the year.

Talking with Bryan - I was asked what are our most popular business functions - these are my top three functions - where I think people like to use our products - POS & inventory tracking, CRM (customer relationship management), and scheduling. Here are some fun links: POS, CRM, and Scheduling.

Switched over to the QuickBooks API stuff. We kept getting an error and didn't know why. We had to make some live edits and then do some live testing. We found some large negative numbers and it looks like the client is maybe using some values and tools in the wrong way (updating inventory counts using huge negative invoices vs using an update inventory count PO - normal way). It sounds like a training issue. We will get with the rep and show him so that the client can do it correctly. Hopefully that will fix the API issue.

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)

Up helping with the Yogen Fruz deployment with Sean up in Tronto, Canada.

Here are some notes and recap:

Sunday - 10/27/24 - Drove to Colorado. Needed to get a passport and Utah didn't have a passport agency place.

Monday - 10/28/24 - Spent the day in Denver getting my passport. Had to go back to the passport agency a couple of times. One for the initial appointment and another time to pick it up and verify information. While waiting, did some research on my cart favorite buttons, smart groups, tiered pricing and rules and assignments for the smart group buttons. Met up with my brother for dinner.

Tuesday - 10/29/24 - Went to the Denver temple in the morning. Spent some time playing around with Affinity Designer and learning how to control color and saturation levels. Graphic stuff. Drove to Salida, CO. Met up with Steve at his house. We chatted about some upcoming projects and challenges. I really liked his house. He had redone some rooms, cabinets, counters, rest rooms, and such. Super cool! Craig came over and gave me a bunch of adilas checks. We talked about goals and ideas for the Canada trip and venture. After that, I met up with Mrs. Shari O. up in Buena Vista, Colorado and we had dinner together. Great time and fun chatting. I then got to go see Shari O.'s house and dogs. Super cute. Visited my friend Andy Maupin and then drove up to Denver.

Wednesday - 10/30/24 - Slept in my car in the airport parking garage - fun! Flew up to Canada and Sean picked me up in Tronto. We went to the hotel, got settled in and got some dinner. After dinner, we went and found a store to get some snacks and other food for the week.

Thursday - 10/31/24 - Trick or treat... We got tricked... :) We went to headquarters and met with some of their team. We got there at 9:30 am in the morning. We didn't leave until after 12:30 am, that night. Super long and stressful day. Tons of hardware issues. They wanted us to fully configure the old FranPOS units (7 year old Android tables with a locked software system installed). We were attempting to run adilas (web-based system on that unit). The browser part worked great (normal adilas stuff). The ability to interface with the peripherals and hardware were crazy tough. We couldn't get anything to work. Totally beating our heads against the wall. Trying all kinds of stuff. We did have some help from one of their team members (Harsha) and that was about it. At one point, it looked like that was the end... The main boss on their team was saying, it doesn't look like we will be able to deploy this software. Sean and I asked for leave to go to the computer store and purchase some things that we knew would work (new hardware). We were also somewhat waiting on another one of their team members who hadn't come in yet. He was a tech savvy guy who had been able to hack the locked code on the FranPOS on the last visit from Suzi from the adilas team. Without going into crazy details. We got some new hardware and started setting it up. We were also blessed and the other IT guy (George) from their company came and was able to get some things going through on the older hardware. Pretty stressful day.

Friday - 11/1/24 - Went to the mall (Square One mall in Tronto) to help get the system up live for the client. We were needing some help from the IT guy. He was a little bit late, we had it mostly running before he came. He put the icing on the cake and made it work. In the meantime, I ended up recoding some of the my cart favorite buttons, making them bigger, and styling the mini invoice (customer receipt) format. Sean was doing some training and by mid way through the day, it was going super smooth. If it wasn't for the hardware issues, we could have been in and out in just a few hours. Anyways, good day and they seemed to like the system. Answering random questions here and there. By the end of the day, they had done over 150 invoices (sales tickets) through the system.

Saturday - 11/2/24 - Went back to the store (Square One) to help out and see if they had any questions. Had lunch with the owner (Eric), great guy. I spent most of the day fixing small little things to help with flow and settings. Fixed a few information messages and added a new setting to control the auto print option for the mini invoice. Good day.

Sunday - 11/3/24 - Woke up early to update all of the time zones on the servers (daylight savings stuff). Sean and I went to church and then did some site seeing (Niagra Falls and such).

Monday - 11/4/24 - Back to headquarters. Worked on uploading customers. Sean was helping and doing some training. We spent some time and put together a small email with a list of to do items. We then had a meeting with some of their team to go over the email and to do list. That was really good. I met with a couple of people and setup some new accounts for some of the accounting people. Towards the end of the day, I got a chance to chat with the main operations boss (Phillip). I enjoyed that. Trying to show him what we do and how we do things. He has a lot of things going on.

Tuesday - 11/5/24 - Sean dropped me off at headquarters and I worked there all day. He took the rental car back and flew home. I spent most of the morning working on loyalty points and getting data entered into the system. Various questions, different sessions, etc. Towards the end of the day, I did some group training for four of the main people (Phillip, Rex, George, and Harsha). I thought it went good, hopefully they enjoyed it. There is a lot to cover. At the end of the day, I found a good spot to stop and did some light planning. One of the guys gave me a ride home (Rex). He was pretty cool! Just being silly but I got back to the hotel and said, "I'm alive!". I was super happy. We still have some things flapping in the wind but nothing that we can't tie up and/or fix. All in all, I was pretty happy.

Wednesday - 11/6/24 - Took a cab to the airport and got all checked in. I spent some time going over emails and what not. I hadn't checked them too much for the past week or so. Somewhat behind. Flew home and drove from Denver to Grand Junction, Colorado.

Thursday - 11/7/24 - Drove home from Grand Junction, Colorado to Logan, Utah. Stopped along the way and had a 2 hour phone call meeting with the adilas team (Steve, Alan, Cory, Sean, and I). Had a little car trouble but got home safe. What a trip!

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

- Colors - new dogs, bite risk, etc.

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

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

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

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

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

- Vaccination records - tracking that info

- Vet info - doctor info and such

- Dashboards

- Conversational text messages and using a huge texting tool

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

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

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

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

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

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

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

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

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

- They would love integrated financials - in the end

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

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

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

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

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

1/13/25 Bryan and Brandon meeting 

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

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

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

    a. Populate Charles' layout

    b. Already have a time slot view.

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

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

3. Tip splitting. (20hrs)

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

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

    c. create a tips page.

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

    a. Garrett/Calvin created apis with Twillio.

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

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

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

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

*** could be used for multiple Adilas projects.

Emails and tech support. Simple cart stuff, new cart ideas, button settings, and label requests. Suzi was passing along some notes from a meeting that she was in with a client. Also did some adilas API socket settings for a trailer dealer with some samples.

Zoom meeting with the Yogen Fruz folks from Canada. Suzi and Steve were leading out on the meeting. Here are some of my notes... kinda random:

- They (the Yogen Fruz folks) want one stable platform used among all of their brands. Something that will lead them into the future. Reports in real-time, real-time analysis, data mining, deeper and deeper down the rabbit hole (big data wants and needs).

- They want to get a better picture and more control on the inventory control level.

- Accounting and operations (mixed) - they need to track flavors, add-in's, waste, accurate food costs, etc.

- Breaking things down into smaller and smaller pieces - more control and knowing where they are at financially. Basically, empower the users to see what is really happening.

- Being able to pull the data out of the system and support people.

- They had Phillip, Josh, and George on the meeting. Another lady was on for a bit but had to jump off.

- They wanted to see the fruits of their labors - they had given us some instructions and wanted to see where they (we) are at. Phillip was mostly leading the charge and asking the questions. He seemed very sharp and fun.

- They wanted to know about the clover payment integration system - progress, rates, and cash back amounts. Steve was talking about tokenized transactions vs raw data transactions. Also, they were talking about the need for breaking and re-establishing connections every couple of hours (automation stuff). Light history and evolution on some of the old and new payment options (merchant processing).

- Switched over to bulk product labels. They were worried about permission levels. They wanted to possibly have special labels that would dissolve in water. They may look at normal options if the cost is too high or only a certain label printer is able to handle that kind of label.

- They turned the meeting over to Suzi for a bit. She was showing them new settings within the cart. Went over a bunch of new things.

- Taking ideas that work for others and then using those ideas - shameless borrowing of ideas.

- Fulfilment options - fill in based on settings - timing - etc. Steve chimed in and had lots of info. He has helped and built a couple versions of the fulfillment homepage within adilas. That was pretty cool!

- Print and label settings from the cart - speeding things up. We may need to add some more settings to help with less clicks and automation options.

- Reporting - They are really looking for real-time data - top 5 products, top 10 products sold, etc. All at the click of a button.

- BI stuff (business intelligence) - projections and real-time data - even multi corp - enterprise level needs

- Steve was talking about paperless options and pitching other adilas backend office features.

- Steve built a special report for them while they were on the demo. He was talking about favorites and custom reports. So much power already exists.

- Limited time offers - LTO's - they want to track some of those things. It was important to them. We don't fully know what those are but they seemed to think that some of our existing functionality would work great for them. Somewhat unknown to us...

- The searchability of adilas - so many options to help you get a good flavor and taste of what is really going on.

- I got to show a few things - multi-level reporting. I jumped into some existing accounts and did a quick demo of a few things.

- Small talks about hardware and converting things from one system to another - switching things over

- Towards the end, they were talking about next steps - other meetings, changes, live testing on hardware, and SOP's (standard operating procedures).

- After the main meeting, Steve and I were going over some code stuff. Small tech talk stuff. Light re-camp and team meeting with the adilas folks. Suzi and Josh stayed on for a bit after everybody else left. Great meeting.

Meeting with Steve and Suzi and going over the changes in the cart. I showed them both the touch popup for changing the line item quantity in the cart. We also looked into Steve's new drink level PDF labels (what goes in what drink - for the frozen yogurt company). We talked about some other ideas and ways to take steps off of the current process (refinement process). Suzi is sending emails, screenshots, and communicating with the client what things have changed and been updated/altered. Fun to see all of the changes.

Meeting with Suzi and Sean over a GoToMeeting session. We were going over the adilas label builder. We have an existing piece but it needs some major upgrading. Here are some of my notes... It sounds like it's pretty painful from the user side.

- In the current label builder - on step 2... help show the width and height on the label drop-down. Also use smaller decimal.

- On step 4, the label is so small... they would love to see it bigger (zoom to scale)

- When editing, the top 5 fields need to be editable. These are the name of the field, the height, width, the _x and _y positions (where on the canvas the fields starts).

- Be able to see it while you are doing it, be able to save it while you are doing it. Currently, you have to make an edit, switch modes, then save it, then go back.

- When going from page to page, it isn't saving the new changes. You have to almost make a change, go save it, make a change, go save it. If you try to have it do too much at a time, it gets lost.

- She (Suzi) has to go back, go back, go back... very frustrating.

- She is recommending that people don't even use it. The current label creation tool is that bad. They (she and Sean) are building out the labels, showing the people, and not showing them the actual tool. They are taking on the hard part in order to save frustration.

- She has seen some demos that have really nice label building tools.

- I have a bunch of notes from past brainstorming sessions - dealing with wish lists for the adilas label builder. I also have some document on my local computer from some brainstorming sessions with Cory, talking about next steps on the label builder.

- She has also seen other tools that are really hard to work with for label building (other products). You really need a way to connect the database to the label builders.

- They are wanting full colors, static text, dynamic text, QR codes, barcodes, horizontal text, vertical text, graphics, data driven value, etc.

- Snap to grid... both yes and no options. Along with that... a nudge (using arrow keys) would be super helpful.

- Suzi was talking about how at another company, they used Adobe Illustrator (full on graphics program) to do super custom layouts.

- They need ability to do super small text (font size)

- They may even need round labels, not just square or rectangle labels.

- The current decimal level is way out there... like 10 or 20 decimal points. We just need to format things, for a visual for the end user.

- Some of our competition has some really fancy label builders. No idea on the price tag, but there are some sweet label builders out there.

- Not just simple labels... they are looking for super fancy labels... full color, full gloss, full layout options, etc.

- Suzi has a number of samples of fancy labels, if we need them as samples.

- Sean and Suzi were talking about the cost of labels - pros and cons of going with preprinted logos. It depends on what things change and how often you need the label options.

- Both Sean and Suzi have used it (the current label creation tool) but it is painful.

- The work has to stick... every time. It's way to fidgety.

- Be able to zoom in and out.

- Add a save button on the show grid layout step.

- They want to combine step 4 and 5 - do it all on one page.

- They want to be able to add a custom label size... be able to enter perfect width and height. Currently, you can pick from a bunch of single labels (presets) or a huge list of Avery sheet labels. They would like options to enter custom labels (sizes and dimensions).

- Be able to switch between inches and centimeters.

- Be able to align elements, copy elements, paste elements, etc. Easier for the end users.

- The barcode text needs to be able to scale (font size of the bars) - we need to be able to fit a 24 character barcode on a 2" label.

- Instruction and education (writing and on video) on where to access the labels - for each type - customers, invoices, PO's, and items.

- Be able to work easier with subs (parts) and sub packages (parent/child inventory).

Meeting with Bryan. He is working on being able to set an item as a main item to help with cart line item level grouping (special cart stuff). This will help Suzi with some of her clients. We tweaked the logic and did a little bit of looking around. Small work session to cascade code and logic. We also made a list of to do list items for this project. Anything in the cart quickly multiplies to a handful of pages.

Working on the show cart line item groupings page. This page shows the line summaries based on the groupings. Built the logic, did some testing, and pushed up the files to data 0 for some live testing. Sent an email to Steve, Suzi, and Bryan letting them know with some more information on where things are at (development wise). Other small cart changes.

Emails. Meeting with Bryan. We pushed up some code for the new my cart favorites and being able to stack and multi assign buttons to different groups. Super cool and it will help out Suzi and the frozen yogurt demo site. Being able to reuse a single button or button group in multiple places. We then talked about next steps. Went over some of our priorities. Started to line out some of the other projects. We will meet up tomorrow and see where we are at.

Meeting with Bryan and Suzi. Showing some progress. Then going through a full list of to do items. Setting some priorities. Bryan showed us some progress on the button stacking stuff for my cart favorites. After the meeting we chatted about next steps and setup a meeting time.

Here are the priorities that Suzi has for the mini scan cart...

1. Groupings for the labels

2. Back button - be able to go up the button drill-down chain in split cart mode

3. Button stacking - one-to-many relationship on the buttons

4. Touchscreen quantities

5. Auto numbering based on main items - be able to flag certain items in the system so that they know that they are main items (grouping stuff)

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 Suzi and Steve on the frozen yogurt company. Suzi was going over things and giving us a recap of her live demo up in Canada. We went over the full 8-page document that Suzi wrote up on her findings. We are getting closer and closer to get their needs and wants checked off. I took a few notes and have a good idea where we are heading.

Multiple sessions throughout the day. Started at 6:30 am and ended up finishing up around 7:45 pm. Trying to help out Suzi who was in Canada on a live demo.

Small demo with Suzi and Bryan, early in the morning. Super quick demo. Suzi had a few more suggestions. Bryan and I talked about some stuff for a bit as well. Small change to preselect the auto number option for the groupings. Pushed up some code.

More small tweaks for Suzi. Added code to help with discounts, clear cart options, and a new checkout screen. Pushed up some code. On a phone call with both Steve and Suzi. Recording ideas and needs. Tons of small layout changes. Tons of great ideas and notes. See attached for some notes and to do list items.

Working on a modified payment page for faster checkout. Made it more graphical. Only got about halfway through it. Couldn't stop, had to finish at least a small version of it. Pushed up new code.

Quick phone calls with both Steve and Suzi. Talking about ideas, options, needs, and potential clients. Back working on the groupings. Spent some time adding a new method to help store the line sorts and line item level groupings and store those values in the database. I was able to grab some of Bryan's code and just tweak it a little bit. He already had an add new tie-in method built. I just made it into an add/edit (both) method. Started working on the restore to cart from quote to cart. Pulling in the saved sortings and groupings.

Just an idea... On the my cart favorites (custom buttons). If they are stacking buttons (button groups), allow them to create one button and then stack it wherever they need to. Open that up and allow for one-to-many assignments. We may want to look at smart group button assignments (rules and assignments). We may want a similar table or multi-purpose that table to allow for the relationships. Maybe do a sort of just the group buttons and allow for a quick checkbox to say yes, show it here as well. Something like that.

Meeting with Shannon and Abby. Small demo of where are at with the new cart stuff. We even logged in and looked around Suzi's demo site (super cool with all of the buttons). Good stuff. After that, Shannon was presenting on some of her research. We made some plans for next week. Next, Abby was showing us some of her progress on a history of adilas document. We talked about desktop publishing, typography, and making things consistent across a document or a project. I gave her an assignment to checkout some topics and then do a new version. The text is fine, the graphics and feel just need a little bit of help.

Working on saving the new line item level sorting and allowing edits to the sort numbers as needed.

Meeting with Suzi, Steve, Bryan and doing a small demo. Got a little bit of feedback and a few requests on changes that they need and want. It's looking good, just needs a little bit more and then to get it live. After the demo with Suzi, I talked with Steve a bit about some other things that are coming down the pipeline. After the meeting, I talked with Bryan and we did some light planning.

Small side notes...

Wish list stuff. Bryan had a request to get white papers on some of our accounting and how it all works. He has a person who wanted to read up on stuff. Basically, a request for documents and content. That's awesome. I'll try to work with Shannon to get some of that stuff going and done.

On the mini scan cart, we would like to add options for printable notes, non-printing notes, customer PO's, due dates, etc. All of that stuff already exists on the classic cart but not currently on the mini scan cart. We want to be able to change the cart type, the cart date, the salesperson(s), etc. Normal main cart edits.

Request from Suzi, if you click on start cart and the cart already exists... maybe just go to the view cart vs showing an error. not sure?

Emails and then a small change for Suzi and my cart favorites. Took off the quantities on the photo buttons (my cart favorites). Started working on a custom page to help with sorting the line items. Decided to show page stats for the cart and then started working on the bulk sort edit form for the line item groupings. The display was pretty easy. Sorting the line items (in memory) is a little bit harder.

Quick meeting with Suzi. Made a quick change to the split cart buttons (bigger size). Ended up making other button changes to make it easier for people with touch screens (bigger buttons). Touching base on where we are at.

Working with Bryan on the mini scan cart. We showed each other where we were working (progress check). We passed some info back and forth through chat. Bryan is working on his visuals for the groupings. I'm working on the background stuff (session stuff and backend logic). We both started working on our projects and doing prep work.

Meeting with Suzi and giving her a demo of where we are heading. Both Bryan and I showed what we are working on. We spent some time drawing and showing documents, notes, and even code. We showed Suzi how we will be sorting things, based on a small scratch file that allowed for us to move things around in memory. Good interactions.

Multiple sessions throughout the day. Working both alone and with Bryan on and off through the day. Here are some rough notes.

Emails and recording notes. Research on sorting multiple arrays and structures. Meeting with Bryan. Working on sorting memory and complex data objects. Looking into flipping a few small pieces for Suzi for the cart (loyalty points and cart types). Finished up some code and pushed it up to data 0 for testing. Went back to doing a small work session with Bryan to work on sorting memory and complex data structures and arrays. We were playing with a scratch file and trying to make it work on that before going deep into the real code.

Looking into Bryan's code branch for cart line item level groupings. Started going through the code and prepping the cart structure and line items structures with the correct new placeholder fields for both the arguments and session scope variables. More backend prep work stuff.

Meeting with Bryan, Suzi, and Steve on the line item groupings for the cart. We started out and Bryan was giving the demo/show and tell. We ran into a few small bugs. Suzi grabbed the demo and showed us where she is at with her buttons and flow. That was really awesome.

We, as a company, are tying in a flag to the item level (mains and subs all within a single cart). I then grabbed the demo and did some drawings of where we are heading. We talked about ideas of flagging the main parts or items and letting them control the first level groupings. Bryan got the bug fixed and we jumped back to him.

Going forward, I will be working on a new customer search based on settings. Bryan will keep working on the line item level groupings. As a fun side note, we are actually getting some customers who are willing to start paying for demo development (proof of concept). After the meeting, Bryan and I did a little planning and coordinating. Making progress.

Recording notes. Jumped on a meeting and working with Bryan. I gave him a small demo on new cart changes. See attached. After that, I gave a quick demo with Suzi and Steve. When the meeting was over, I lightly reviewed the video.

Demo meeting with Steve and Suzi. They have been meeting with a frozen yogurt company out of Canada. Steve and Suzi have been meeting with this client for a few months. We went over a video of their point of sale (POS) system. We are going to need some groupings and ways to sort things within the line items. Basically, you add a main line item and then you get to choose a number of different options or additional add-on's, tied to that main line item. We need to be able to hold sub selections and be able to edit as a group vs just a single line item. As we were talking, Steve wants us to build out the mini scan cart (new existing cart) and really tweak out the configurable settings. Make it be able to do all kinds of things. Along with that, we also want to build out our own split screen (new settings... right, left, pane sizes, etc.). That should be pretty cool! Exciting!

Phone call and planning with Bryan. Then meeting with Suzi and Bryan to go over cart/invoicing line item groupings and sorting options. Both Bryan and Suzi have some upcoming demos that need invoice line item grouping and sorting. Quick meeting to figure out a plan and talk about timelines. Lots of drawing and just talking about possible options.

Meeting with Suzi. She had a new analogy for me (for the dog care demo site), think of an operating room... patient(s), doctor(s), other assistants, etc. Complex scheduling stuff. Switched over to some questions on a frozen yogurt demo site. Suzi has a need for items and sub item attributes, extras, or modifiers. This would need to be tracked per main item but basically, a pool or preset group of extras that could be hung on or attached to an invoice or cart line item. Imagine, a main item with sub options. These could be called options, extras, sizes, flavors, colors, modifiers, attributes, etc. I'm not sure. We spent some time going over an ice cream store (frozen yogurt) type options and needs.

Suzi and I jumped on a demo meeting with the Puppy Pals folks (potential client). Suzi was doing the demo. They, the Puppy Pals folks, need real time texting (push notification). Suzi was demoing the messaging stuff that we have out in ecommerce. Their clients need a quick way to get logged in, communicate, and even get automated responses. They really need notifications.

We switched to flex grid and showing limited flex grid options (for entering pets and one-to-many relations between clients and pets). Talking about dashboards. We went back to messaging for a bit - they really want real time text messaging. Deeper talks about wanting automatic messaging and responses. Two-way communications are needed (big time). Even batch messages.

Suzi handed over the demo to me and I helped with some scheduling stuff. Lite show and tell. They like the time down the side and people across the top for their horizontal time views. Lots of other notes and requests. Basically, they have a complex scheduling need. Almost a 3D model. They have time, rooms, and attendants. They have to matchup all of the pieces.

Partway through the demo, I started writing things down... this is kinda rough (my notes) but here is what I recorded in a quick notepad doc...

- Booking and re-booking

- Moving appointments around

- 5-6 clients coming in at a time

- 100 appointments a day

- Logistics of what happens each day

- Need a quick overview

- Docking and sliding appointments into the slot - temp copy and paste to move things around - move all of the pieces - all of the extras - maintain relationships

- Complex appointments - and then rebooking those appointments

- KISS (keep it simple silly) - visually formatting things to work with the team

- Be able to move the data around

- POS integration

- Be able to divide the tips

- Be able to take a deposit on upcoming services - pre-pay

- They have both taxable and non-taxable items and services

- Bill for no show

- Payoff accounts

- Customer credits - in-store credit

- Notes for customers, notes for pets, notes for appointments - two or three years of notes

- Calendar and time-slot issues and needs

- Per appointment - show dog name - show client name - breed - color code(s) - size, appointment type, assistance level

- Conflicts and rules - max out levels - how many rooms may be booked at once

- Conflict notices

- Each location is different - they are trying to grow from two locations to 10+

- Biggest challenges - complexity of the appointments and be able to move things around

- Be able to manage things and move things around

- Everything happens within 15 minutes... they come in, they get serviced, and they get checked out (payment), and maybe get re-booked

- Future dashboard options - financials, scheduling, inventory, etc.

- We want to help you further that (what you are doing)

- These are "dog" (pet) people

- Pare it down... make it look easy... (frontend)

A lot of that we already have. I was just writing down what they were saying so that I had a record of it. One of the ladies on the call was very sharp. Her name was Jen. You could tell that she had some software and development level background. Great questions, responses, and just knew her stuff. I was impressed.

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 Steve and Suzi. Looking at a dog care software package. It was actually a human salon software system that they are using for the dog care company. Looking at options and seeing what we can do, using adilas to help them out. Lots of talking, planning, and even building out some flex grid pieces in the demo site. Steve had to drop off due to bad Internet. Suzi and I spent the rest of the time planning things out and talking about what already exists and what would need to be custom. Great session.

Suzi is quite sharp. She is willing to get in there and figure things out. Self-taught.

As a fun idea, Suzi thought that it could be really cool if you could tie a picture to a piece of flex grid. That would be pretty cool. Great idea.

Just for the record. Some of the pain points for the dog care people were things like their software system only allows one person per appointment. Sometimes they need multiple people if they need to restrain and/or assist with the appointment. Each client needs a one-to-many relationship with their pets. When a tip is given, they need to be able to split it based on who was working the appointment. Currently, all of their notes just run together. There isn't a any type of log notes or custom fields.

Suzi and I were having fun planning things out and being able to come up with ways that we could solve all of those problems, almost right out of the box. We will have to do some custom stuff, but it isn't too big of a lift, and we could easily reuse it over and over again. Fun project.

Meeting with Suzi and her team from iAnthus. We were checking on progress on a custom report that Steve had built for them. Suzi put it through the paces and everything looked great. We talked about a number of other requests and projects - virtual wish list. Towards the end of the meeting, John from adilas showed some design concepts for some cultivation and industry specific tables and reports that we are looking into building. It is amazing how much people love the flexibility of adilas, but eventually, they want things really pared down and customized to their processes - speed and efficiency - very interesting.

After we got done with the client meeting, we all met back over on the adilas GoToMeeting account. We were going over ideas, processes, and plans. One of the things that we want to keep pitching is hope, a big part of what we offer is potential, vision, and hope. That is part of our marketing plan.

- There was an original email dated back in July - Cultivation report for Ianthus

- Suzi and Philip from Ianthus were on the call - there were quite a few adilas folks on the call.

- Cultivation mapping - done by Dustin

- When a plat it changed from one phase to other phase, you auto populate those fields.

- They have some custom fields (sub inventory attributes) that they want auto filled when certain actions happen - changes of specific phases

- Maybe setting up which sub inventory attributes show up based on what phase. Also, does one or more of them have (sub attributes) a mapping from other data that is being entered up higher. It may take some more mapping. We may want to show/hide certain sub attributes based on the phases. That means we need to go through the process and really detail out what is shown and what is hidden. Along those same lines, they would love to set it up so that if a sub attribute is being shown, it can get a value or its data from one or more spots (other user entered form values). 

- Currently, some of the info that they are wanting to catch (automatically) is dealing with dates and sub dates.

- As a side note, because we allow each corporation build their own sub attributes, we then have to be able to show/hide and map out these pieces as they go through the different phases. The eventually need all of this data, but we are showing so many fields, it makes it more difficult. We are catching all of the data right now, it just isn't organized (visual report or visual form) to make it easy.

- Another thing that they were talking about was getting to those sub attributes later on - other reports  and passing that data along to other places.

- Just an idea... what if we build a phase builder type app - these would be settings, user controlled, and allow you to setup a single phase, what data to gather (maybe a point and click interface to setup what will show up), then the ability to setup defaults, show/hide fields, what to default things to, other data mappings, etc.

- There were some talks about back filling the data - separate tasks going backwards. Along with that, if we back fill things (update the data), we also need to build it going forward so it becomes an automated process.

- Eventually, they were getting into the nitty gritty details of each phase. The start of one phase sets certain values, the end of a phase closes things down (other actions) and also starts the next phase. We need to detail out each phase. I'm just dreaming here, but virtually a way to setup pods or sections of a virtual data assembly line process.

- The first phase would be a backfill type report - able to do things in bulk. They were talking about being able to select a PO date range and then applying specific dates to all line items on the PO. There were also talks about a PO number range.

- Light talks about required sub attributes and optional sub attributes.