Working with Shannon. I was talking and she was taking notes. Lots of things have been going on. My son Tanner passed away, I haven't been working for almost a month, things were left with some uncertainty, etc. Pretty crazy time. Anyways, I was talking and speaking, and Shannon was catching what I was saying and talking about. See attached for some of the notes.

After our meeting, I printed out the notes and reread them. What a help to have here take such good notes. I was literally just talking and she was catching all of that.

Meeting with Russell. These are some of my quick notes from our meeting:

- Talking about testing and testing coverage.

- Doing mock-ups and putting yourself in the right thought pattern (not pixel perfect mock-ups).

- Experimenting, looking at layouts, looking at distractions, questioning everything, etc. Quick mock-ups and throwing things around to see what looks good. All of this in Adobe XD. Bouncing between the project (CSS theme) and then pulling out small reference pieces.

- Managing the attention of the user (visual layout and visual priorities).

- Make the mock-up so mouthwatering you just say yes - powerful, easy, and beautiful.

- Dream it up and then build it and make it happen.

- Crafting an experience takes time.

- Building out mock-ups to catch all of their desires.

- Even asking for non-refundable percentages to do a more detailed estimate or price quote.

- If you tell me what you want... I can sell it to you (sell you a solution to fit your needs).

- Russell, helps other people build their dreams and then tells them how much it would cost.

- Just for fun... I sent him a copy of the horse graphic (client asking could you do it any cheaper?). See attached.

Working with Shannon. Touching on the adilas value add-on core model and the adilas university overviews for the adilas lite and fracture projects. We also spent some time working on the adilas marketplace project overview. Good work session. We then added the overviews to the web pages where they belonged. See attached for our documents and progress.

Links to the project overviews:

- adilas jelly fish model

- adilas value add-on core model

- adilas university

- adilas marketplace

Phone call with Steve. Going over ideas, what's happening (I've been out for almost a month with the passing of my son), talking about new projects, job costing ideas, merchant processing, managing people, talking about investors, and creating a pitch deck. Steve had the idea of creating revenue caps and repaying things based on values that exceed a certain revenue cap or amount. Other different ways of financing things. Good conversation.

Lunch meeting with Chad Jeppsen. Talked about different companies that Chad has worked with or for. Their cultures, management styles, perks, and stable vs more open models. We talked about getting multiple tasks piled on top of you without removing other already assigned tasks or responsibilities.  That can really add stress to your load. We also spent some time going over work environments and level of control where you work. Those are big factors.

Daylight savings time changes on all servers. As a note, data 5 was missing the main logo. May need to check that out (fixed it on 3/14/24).

Meeting with Steve. We had a great little brainstorming session. We were looking at the database, checking out tables, and planning out options for using elements of time for perfect job costing. See attached notes for some of our plans.

Great meeting with Shannon. We were going over ideas for an adilas pitch deck for selling shares (percentages of ownership) for adilas. I was talking and going over some of my notes and ideas and Shannon was taking notes about what I was talking about. See attached. After we got done talking about plans there, we switched gears and did some more planning on the project overviews for the adilas cafe. Once again, see attached for our progress.

Letter of recommendation for Bryan. Also, cutting a personal check out for Shannon and work done helping me with Ship B stuff.

Looking over plans for the pitch deck (notes from session with Shannon and I from this afternoon). Rereading some of the notes and plans.

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.

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.

Working with Shannon on project overviews. We did some work on the adilas cafe overview and then on to the adilas lite and fracture overviews. We made a few website changes and Shannon attached the documents that we are working on. See attached.

Phone call with Bryan. He had some questions about merchant processing and internal scheduling. Recording notes from the past couple of weeks (3/5/24-3/14/24). It's been a little bit crazy.

Meeting with Bryan. Going over golf club (image a country club) type business options and how to use adilas to help with certain tasks. Things like scheduling tee times, tons of restaurant type needs, etc. Bryan was asking all kinds of questions. We have all of the tools, they just need to be tweaked a bit. Eventually, our meeting got into a who knows what type conversation. For example: So and so knows about this part, and so and so knows about this other part, etc. No one knows all of it. I was telling Bryan about some custom work we did for a Mexican Burrito place and how we were using ecommerce to help them place their orders with certain choices. I know that Sean and Dustin know about tons of other stuff. Alan has helped with other setups and custom code. Steve, Shari O., and Cory all know other things.

We talked about normal cart stuff, delivery, fulfillment stuff, custom webpages, and setting up custom skins or custom flow processes. I ended up doing some consulting, talking to Bryan about custom skins, and setting up a demo site. It takes effort to configure the tools. Once set up, the flow is much easier. Ideally, we would like to gather up all of the knowledge and put it in one place for use by others who want or need it.

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.

Working with Shannon. We finished up the adilas lite (fracture) project overviews. We then pushed up the overviews to the correct pages. That is awesome, we've been working hard on some of these overviews. Here's a list of projects. They are not done yet (as of right now) but we are making progress and getting things planned out.

Adilas Lite - Main Homepage
# 1 - The company structure - adilas jelly fish model
# 2 - The overall structure of the adilas platform or system - adilas value add-on core
# 3 - The education and training needs - adilas university
# 4 - The marketplace for the adilas community - adilas marketplace
# 5 - The virtual portal or primary landing spot for the community - adilas cafe and community
# 6 - Deeper dive into the adilas platform or system - adilas lite or fracture
# 7 - The budgets, finances, marketing, and sales plans - other business plans
# 8 - Come take a look!!! - adilas lite videos and research

Meeting with Bryan. Working on some demo flow options. Tons of stuff for the golf club demo site. We went over new carts, ways to track tables (say like in a restaurant), custom buttons, and other topics. Here are a couple of topics that need their own line.

- We would like to set it up to be able to setup and/or pass through flex grid items from the shopping cart to either customers, invoices, quotes, or elements of time. That would be so cool. Currently, you have to get out of the shopping cart before you can deal with flex grid tie ins (custom fields or custom one-to-many relationships). We talked about ways to do this and make it happen. Brainstorming.

- Putting multiple people on a single element of time. We already do this for places like Beaver Mountain (ski school lessons) and High Valley Bike (bike shuttle services). We just need ways to make it easier to do for other companies. You can already set it up, but you kinda have to know what to do and how to do it to make it really work. Also, some of those other businesses, we've helped them out by creating a custom set of buttons to jump into their specific flows. That really makes it easy for them. Basically, ways to speed things up and make it not so custom but a generic, yet configurable, toolset. Behind the scenes, we use a thing called limited flex grid to make the forms look super simple and easy to use.

- Bryan and I went over lots of options for splitting tickets or bills. Here's the scenario. Say a guy wants to set up a tee time (golfing) for he and three other friends. We need to schedule the tee time (calendar event or element of time). We also need to bill each person or put it on their tab. We can do that right now but we would have to do one of the following. 1. Create four invoices, one for each person and put it on account (they will pay later or their tab). Or 2. We make one invoice for the full amount and then let them, each person, make a payment towards the full ticket. You can do that right now but it doesn't put it on account for each one. It would just be an invoice with multiple payments. Anyways, we talked about some bulk tools for the shopping cart or ways of saying... duplicate this invoice for these people (bulk tools). Then it, the system, goes out and does it.

Just some ideas and discussion topics. Good stuff! Bryan is doing a great job asking questions and what not. Lots of fun ideas and getting him some training on the system.

Helping Bryan with some questions and setting up a merchant account on data 7 for a company. Recording notes and making a small fix on the developer's notebook pages.

Working with Russell on the dashboard mock-ups. We ended up getting lost in the details (micro tweaks on fonts, colors, sizes, etc.). We talked about style guides and trying to get to a good style guide level (ish). Constantly moving target, in some ways. As a reminder, who's the audience for each thing? Keep that in mind. It makes a difference. We spent some time adding in charts and graphs to help with the layout and display of the data. It was fun to watch him build things up from wireframe to actual mock-up. Going through the refinement process. From placeholders to mocked data and elements. This is just a practice project to go from design to full output.

Recording notes from weeks past. Trying to catch up (1/23/24 to 1/25/24).

Working with Shannon. We were going over our ideas for the adilas pitch deck. We had some notes from back on 3/12/24. I was reading the notes and expounding on some of the ideas. We talked about all kinds of stuff. Tons of side tracks and trying to get clarification. We had the idea to use the adilas interactive map and adilas core to show how things came about. That could be pretty fun. We will also try to use the graphics to build up what we have. When ready, I'd really like to link to the presentation gallery and use that for some our pitch deck stuff. I really want to use that resource (presentation gallery) as well as other graphics. See attached for our notes and changes to the original notes. Shannon will also be adding her notes from our meeting.

Recording notes from today and yesterday. Also, went back and filled in some older notes starting on 1/25/24 to 2/1/24. I got behind and then my son Tanner passed away. That really put me behind. Doing some catch up work. Lots of moving pieces.

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.

Phone call with Bryan. Talking about needs for Golf Clubs (resorts) or Tennis Clubs and how they need software for Tee times (scheduling), pro shops (retail), memberships, dining, etc. Multifaceted needs. We talked about options to help draw or create custom visual interfaces for dining rooms, restaurants, and bars. We talked about how we have custom label builders that allow for buttons, input, and then setting up rules and data connections to each field or barcode on the custom labels. Setting up a dinning layout could be similar to the custom label builder (in theory).

We may need someone to help plan things out. Maybe work on layout and flow as well as processes and options. There seems to be a growing need for a project manager/designer.

I spent some time brainstorming on the adilas pitch deck and how to build some of the graphics and videos. Lots of ideas about using the adilas core graphic and the adilas interactive map graphic. Maybe even using both of them in combo to help show progress and what happened over time. See attached for a couple of scanned planning note pages (scratch paper).

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.

Meeting with Bryan. Going over needs for the resorts or tennis/golf club type businesses that deal with both scheduling and restaurants. Need for being able to keep track of guests at a table and meal courses (subgrouping of cart, quote, and invoice line items). Thinking about altering the description fields. That could be pretty easy. We already allow that, we would just have to create some easier tools to manipulate that field or value. We could also allow for line item sorting from within the cart. You can do it on an invoice (after the fact) but not in cart mode (line sorting or moving up or down inside the ticket).

We also spent some time talking about options for being able to split the check (split ticket or split check options for a dining bill - who pays for what with multiple people eating together). We need to take into consideration both server (waiters/waitresses) and backend kitchen needs. Bryan was basing some of his needs off of a version of Clover table service software (separate software offered by Clover - outside or external vendor).

Back to the tables in a dining room or bar stuff. We need a visual display option for showing the seats, tables, and restaurant style layouts. We could do it manually but it would be better if we had a dynamic tool that the users could use, manage, and fully control. You would need to know things like how many guests, per table, total occupants, what to call things, defaults, other settings, etc.

We kept switching gears. Back to the possible cart line item grouping option... This is basically a way of organizing or putting a pre-fix on the descriptions or flagging certain line items to be part of a group within the main cart or invoice. Towards the end, we switched to button layouts and building special pages (we may need to design a custom layout or customer homepage with settings).

As a note for myself, what the clients are really asking for is a multi-level carts, line items groupings, line items sorting, custom dynamic interfaces, and advanced scheduling options. Complex items, tracking, relationships, and deep time stuff. Interesting.

Emails and checking out a finance company's website. I got an email asking to meet and chat. I wanted to check it out a bit before replying back. Switched and started working on some notes from a multi-day conference for Rezzimax, back in September of 2023 (see element of time # 10257).

Working with Shannon. Going over all of the different custom code requests (doggie salon, frozen yogurt, golf/tennis clubs and restaurant, POS, and calendar (complex pieces). We had a brainstorming session and Shannon took a bunch of notes. See attached. Unwritten, our business plan has been - chase the $ (money). We talked about the difference between the demo clients vs existing paying clients. As we were talking, we made an analogy of running a race. Imagine the difference between racing and tying shoes vs just flopping along (not tying your shoes). Shannon took some notes (see attached). At different times, we are seeing cycles and patterns. We are trying to learn from that or those cycles and patterns. They are not bad, we just need to keep learning from them.

Went over to Bryan's house to plan some dining things and cart line item level groupings. See Bryan's notes on EOT # 2460 inside of adilas. We ended up doing a planning and brainstorming session. We had multiple handwritten pages in a notebook, tons of free scratch papers (each with different subjects), and a small whiteboard drawing. For scans and photos of our brainstorming session, see EOT 2460 in adilas.

Meeting with Cory. Handing over the torch to Alan to work with the developers. Being wise about how we are spending our development money. She lined me up on a few different projects. Pretty short meeting.

Meeting with Russell. Working on the mini dashboard layout practice project. Russell was working on the project overview layout. On the layout and planning, you have to take into consideration the length of the text (variable lengths). You end up making big ones, small ones, and mid sized ones to see how the layout looks and what is allowed (text and graphics - hit all the variables). Not everything lines up perfectly. We did some masking, locking, and playing with layout ideas, all in Adobe XD.

Wow, the value of a good mock-up is huge. It almost becomes live without being live. Being able to show and play with alternates and design decisions - duplicate, tweak, duplicate, tweak - see what you like. Towards the end of the session, we were working with profile pictures and playing with masks and opacity (alpha transparency). We also talked about showing and designing starting modes, active selections, and watermarks. Lots of playing with our layouts. Good session.

Emails. Gathering up some resources for Steve. Put together a quick page to help show some investment opportunities for adilas. It's really rough, but a start.

Working with Shannon. Talking about sorting and grouping cart, invoice, and quote line items. That's a new and upcoming need. We talked about cutting corners and building on top of that - under pressure. Sometimes it just has to happen but you don't want to make that the norm. At some point, there will be some future clean-up that is needed. As we look forward, the question comes up... who is going to get to it and when? All part of the game. See attached for some of Shannon's notes.

We also spent some time talking about buying a house and what a person would like to know... and how that translates into buying shares of a technology and SaaS (software as a service) company. Good discussion. See attached notes.

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.

Projects for Cory. Did some PDF changes for a client. Changing state withholdings for Colorado. Checking on Oklahoma state withholdings, formulas, and table data. Recording notes from earlier in the week.