Demo with Mark at Vivio

Started working on new discount engine and smart cart logic. Sort of an advanced discount with tiered pricing and automatic discounts based on certain rules. Going over my quick post-it note scribbles and translating them into a digital list of things to think about and check.

Switched over to working on the edit cart line item page. Started making changes and ran into a JavaScript error. Ended up backing things out. I think that I need to take a different approach. It started getting messy. Rolled back the code locally.

Recording notes from 10/24/24 to 10/25/24.

Meeting with Cody. Going over the adilas check write app changes. He has the main bank check settings, the print individual checks interface, and the logic done. It is getting close. We ended up adding eight new columns to the check specs table to allow users to move some of the placeholders around on the check. These placeholders are things like logos, bank info, corp info, and check number fields.

We also looked at the adilas label builder, and I showed him my progress on doing the final code review on that project. We are going to tweak a few things with the builder layout but it is also making great progress. I really want to get these tools out to our users so that they can start being used and we can get some feedback. That's important.

Backing up files. Exported each table from my local database. There were over 360 tables and millions of records, just on my local box. Burned a CD back-up copy. Pretty crazy!

Meeting with Hamid. He needed some help with his budget tool project. We spent time deleting budget items from his little app and then being able to edit items and entry transactions. We worked through the process and lightly finished things up. It still needs some loving, but it at least works. Great little training session and mini project for him. I think that he learned a lot. Good stuff.

He's going to send me over a copy of the code and a small dump of the database files for our records. It's not ready for live production, and would need some major work, but it was a great training app.

Back working on the label builder and retrofitting the old labels to be able to work with both the v2 and v3 code. Had to work some with the old label builder to help show links to the new label homepage and make sure that older versions still had active links and navigation.

Meeting with Alan and going over an update on the discounts and smart cart logic. We talked through a few things. He showed me what he is working on (mini cart display version) and we talked about discounts, showing things, and helping show the customers the total savings. All current projects and shopping cart stuff.

Code review on the adilas label builder. Trying to help out the older v2 labels come up to speed. Small database update and then cascading those pieces through the system.

Meeting with a buddy for lunch and talking about business and what we are doing and learning. Fun lunch appointment. We would like to get back together and chat once I get back from an upcoming business trip. I'd like to see if we, adilas, could help him out.

Phone call with cory to go over item imports for a client. We actually called back and forth a couple of time to make sure we were on the same page. This is basically, a custom data upload for a client. This new upload will load an enterprise system and then the enterprise system will push content down to smaller transactional corporations on the same server. Conditioning and setting up a new custom upload page. Did some local testing and then pushed up live. Sent an email with some instructions.

Code review on Cody's v3 adilas label builder. Going over changes and flow.

Filling out passport information and setting up an appointment to meet with a person in Denver, CO, next Monday to get my passport. I am going to Canada to help with a system deployment for a client. Had to go into town to get some passport pictures taken. Other crazy running around and checking stuff.

Recording notes from 10/22/24 and 10/23/24.

On a GoToMeeting with Bryan. We went over some settings and made a few changes on a demo site to add more navigation. They (prior users) had it way too tight and had removed some major navigation buttons. We went over some basic flow and talked about other avenues to help with custom web code, customer facing websites, and other services that we can offer.

Phone call with Steve. Talked about deep topics and really taking a look at what we are doing - business wise and adilas wise. We had a good hour plus long conversation. We made some plans, went in circles a few times, and feel like we have a plan moving forward. It's not perfect but great progress. Good stuff!

Code review on Cody's version 3 of the adilas label builder. Light research, pulled down the code, and started going through things. Poking around a little bit. Ended up getting pulled off of it for a phone call with Steve.

Brainstorming about smart cart logic, tiered pricing, rules, and assignments. Made a couple of post-it notes full of questions and ideas. Phone call with Steve going over ideas and flow stuff. Talked about the special tiered pricing discounts that are needed for a client.

Phone call with Bryan. Going over questions from a demo. He/They had questions about a private local install and having that sync up to a remote install of adilas. Talks back and forth about what that would take. Only possible with a private local and a private remote at this point. Any shared or semi-dedicated options would have database issues (primary keys and id numbers).

Meeting with the local tech college and their web development advisory board. Went into Logan for a semi-annual meeting. They fed us lunch and we had a good time and some good conversations. 30 miles.

Meeting with Alan. We went over projects and assignments. Alan is acting more in an admin type role. We also talked about budgets, other developers, and levels of commitment. Stress levels are high right now in different areas.

Reading over some of the presentation gallery slides. Read over the vision and future page. Writing new content for the sub modals and popups.

Emails, phone calls with Bryan - helping him get his local all setup, paying bills, and other general stuff. Meeting with Cody to go over his changes on the adilas check write settings for banks and check printing. It is looking good. We touched base on some other projects, and I told him that I would be doing some code review on the adilas label builder this week.

Back working on the database exploration project. Started a big spreadsheet with all 300+ tables listed out. Checking for corp_id numbers and how easily we could mix corps and databases at will. We can add more corps (it was built that way) but we may not be able to mix records between databases (meaning mixing new records with older records from other databases or servers). It gets into primary id conflicts. Techy stuff.

Anyways, that is what we are looking at, this go around. There is a future need to be able to do that (mix and blend and move corps around at will). Long story made short... we are great at adding on, we can handle removing things, and we can even move things (once). We can't move data or mix data, over and over again, as needed. We get one shot at it if moving corporations around. We want to get to that next level, but that's honestly a whole other level.

Paying bills, emails, looking into the adilas database tables and columns. Trying to figure out how many of the tables can be easily moved from server to server based on the primary key and/or combo keys (unique combo of sub keys to make a virtual primary key).

There are over 300+ tables in our database. Our most complex relationship may be payees - they can bridge corps and have a number of sub relationships (who did what inside the system or who is assigned to what - tons of subs).

Meeting with Abby. She had a number of new information modal popups with some content and verbiage. We worked on the core concepts section and the vision and future page and the systems page.

Recording notes from last week. Meeting with Cody, Wayne, and Alan. Going over progress and new interfaces ideas and options. We then let Alan and Cody talk about API sockets and how to set them up and use them. Tech talk stuff. They got into some deep topics and Cody was asking for some samples. Both Wayne and Alan were chiming in and giving him tips and pointers.

Steve and I jumped on a GoToMeetign session. We rand a database update for Dustin and some new code that he had made. We merged in the new code to master. We then spent some time talking about other needed database changes. Wayne has been proposing a datasource update. That is one of the needed steps. We also discussed other database changes that are needed on the actual database and some of the primary keys. We need to switch out the auto number primary keys with unique combo primary keys. That will allow us to move databases and corporations (worlds) around more easily. Bulk and mass migration needs for some of our clients. Including bulk copy of certain pieces and sections within the system (items, buttons, photos, settings, logic, discounts, etc.). Talking over things and ideas. We will have to take the time and figure out tasks and processes.

Emails, writing to Wayne about possible changes to the adilas database and changing some of the primary keys. He was proposing a datasource project, which would be awesome. If we combined his datasource project with the new primary keys, it would be super awesome and just what we need. Also did some testing on the new part reference number code for PO's. Sent an update email to our people, letting them know about the changes, that everything was finished on that project and live on all servers.

Finishing up the part reference field on the PO's (new column). Did some testing and pushed up new files. Recording notes in adilas.

Meeting with Hamid. Working on edit and delete functions for his mini budget tool. Mostly a work session with some training.

Working on adding the part reference numbers to PO's (new column). Going through multiple pages to make sure that the part reference field can show up if needed on the different PO pages - pages - PO line items, bulk edit PO lines, and printable PO.

Recording notes and light research on some other solutions that are out there. Uploading Adobe ColdFusion Summit 2024 notes into an element of time (19 pages of notes - see time # 11331). Spent some time reviewing some of my notes.

Meeting with Dustin to help point him in good ways on the ecommerce stuff. We talked photos, paths, options, black box take overs (custom pages), and where to look and how to help build some custom pages. Short but good meeting.

Meeting with media3 web hosting. Microsoft Teams meeting. They had Steve Rodden and Bob Hayes on the call. Bryan and I were on from adilas. We talked about our two stories and how we came to be (adilas and media3). Lots of similarities. They are in the hosting realm and we are in the SaaS (software as a service) realm. We chatted about options, hosting, support, migration, and potential marketplace options. We had a good talk, and it was an enjoyable meeting.

One of my takeaways was distribution channels and getting our product out to multiple people at once. After the meeting, quick follow up phone call with Bryan talking about distribution channels and how to get adilas setup in those veins or avenues. We have to get more people to see us and start checking us out. It's a scale thing.

We also talked about free trial versions of adilas and how to get things setup and spun up quickly - full turnkey solutions. We are learning and making progress.

Meeting with Bryan and a guy from Ortus Solutions. Kind of a get to know you type meeting. We met with their marketing and sales guy - Cristobal Escobar who lives in Spain. We did a small demo of what we do in adilas and then talked about Ortus Solutions and what they do. They were interested in CMS (content management systems) as they have a similar product and solution for that. We also talked about team augmentation, training, flexibility, and offering lots of different services. Cristobal gave us a few links to checkout some of their products and solutions. Follow up phone call with Bryan after the meeting.

https://www.ortussolutions.com/ - main website

https://www.ortussolutions.com/contentbox - content box - cms solution

https://boxlang.io - their new language - multiple parser for other languages

Emails, texts, and recording notes from the day.

Ship B meeting with Bryan. Touching base. Went over some prior discussions and did some more restaurant industry planning (what we need to service that industry). Bryan was taking notes, and we were going over ideas and scenarios. As part of that, we did some planning on flex attributes for quotes, carts, and invoices. We also touched base and did some planning for upcoming meetings tomorrow. Bryan has three client meetings tomorrow that he has lined up.

Meeting with Alan and going over budget stuff. Projects for me... check write bug and reference number on PO's. We then went over some API structure stuff and how that all plays into the mix. Small meeting.

Meeting with Cody. Going over a small bug in the check write settings. We ended up spending quite a bit of time there and making a pretty good plan. As we were talking, Cody was saying "Being clear in communication makes a lot of difference." He helped me format my notes better so that it wasn't assuming things, they were clearer, and it was all spelled out so that anyone could have read it.

After we finished up with our plans on the check write bug, we switched over and started talking about custom responsive web pages and a custom interface and navigation builder. That sent us off to talking about good visuals, eye candy, graphs, charts, and custom components. We then spent some time talking about API's and how to connect to the API sockets internally. Basically, getting the data from the database and mixing both server-side and client-side languages (code). I'm going to set up a small meeting with Wayne and Alan to make sure that we are all on the same page.

From Cody - If you provide good visuals and have good structure, that is good story telling (meaning, we can help tell the client and user stories better by having in those visuals and correct formats). I liked how he tied it into story telling or digital story telling. That's where we are headed.

Working on the adilas lite pages and adding content to the different accordion drop-down sections. Here are a couple of pages that I was working on:

Adilas investment opportunities
Adilas jellyfish model
Adilas value add-on core model (still working on this one).

Recording notes.

Quick meeting and helping Dustin get started with custom web page settings for doing client facing websites for adilas clients. Good meeting. We also chatted and talked about some other projects and things. He showed me some of his photography (new macros) and other beautiful shots. Fun meeting.

Recording notes, phone calls, and texts. Bryan is trying to get some sales meetings setup with other companies. After that, I rolled over and started working more on some adilas lite pages (prep work, planning, content, and filling in needed verbiage). I would like to finish up some of that planning stuff.

Affinity designer training stuff. Going through some training videos. Trying to up my skills on graphic stuff.

On the phone with Steve. Talking about developers, projects, sales, and direction. We talked about who is doing what, changes that we have made, and direction going forward. We also talked about other sellable projects such as graphical eye candy like charts, graphs, and dashboards. We talked about custom build your own interfaces and light fracture stuff (code for adilas lite - new framework and interface). Lots of topics.

After that, we also talked about sales, marketing, and getting some market penetration and how best to go about doing that. Lots of ideas and discussion points. We will touch base again at the end of the week and go from there.

Looking into custom web pages built by one of our developers back in 2023. These custom pages are for our clients out in the shop area or public web presence area (client portal area or ecommerce area). Pages like home, about us, etc. Sent out some emails to both Will and Dustin (developers) to make sure we were all on the same page.

Paying bills and recording expenses. Going through emails.

Phone call with Alan, recording notes, and doing some follow ups. Sent an email to Alan with a small list of MVP projects. Here is what I sent in my email.

-------

Here is a small list of projects that I feel need to be done to help with an MVP. There will always be more, but here is a good start.

- In-store credits
- Coupons
- Tips and being able to split tips
- Adilas label builder - version 3
- Stable and standardized chip reading and merchant processing - retail and ecommerce
- Revamp of the shopping cart (mostly done)
- Time and scheduling - vertical time view - scheduling from out in ecommerce land
- Discount engine (rework)
- Smart cart engine and logic (overarching cart logic to handle discounts, coupons, and tiered pricing)
- Rework sub inventory
- Consistent look and feel
- Text messaging and push notifications and reminders
- Database changes - allow for either clustering and/or being able to move corps around at the db level
- Customizable homepage or build your own interface (not really required but I think that it would really help)

Anyways, that's a quick list of some of the things that I think would really be helpful. We are getting closer and closer. I know that people can use it right now and have for years, but these are some of the things that have been asking for. I hope that helps.

Paying bills. Jumped on a meeting with Cody. We talked about the adilas label builder. We are going to work on it on Wednesday to see if we can get it ready to push up to let people start playing with it. We then looked into some other projects. We looked at a check printing bug. Cody is going to look into that.

Next, we then looked into what it might take to build a create your own interface type model. Lots of drawings and talking about options and plans. I sent him the link for where we are headed, based on the some of the adilas lite videos. See this page for some videos: https://data0.adilas.biz/lite/adilas_lite_videos.cfm

Meeting with Bryan. Going over his code for flex attributes for stock/units. Code review stuff. We had to fix some merge conflicts. We pushed up some code and did some live testing. We found a few small errors and spent some time pushing up fixes.

Small to do list stuff. Emails and tech support. Small check for the bear 100 on a CSV export. They were wondering about a special format. Looking over code and reporting back to them.

Emails and pitching custom code to clients. Billing for other custom code projects that are completed. Scanning receipts from the coding conference. Paying bills.

Tons of emails, catching up from the trip to Las Vegas for the Adobe ColdFusion Summit Conference, notes, phone calls, texts, etc. Phone call with Steve going over plans, options with the developers, custom web sites, projects, and updates on where other things are at. He's got a lot of things cooking.

Just for fun... he and I were talking about the developers and how to handle billing and commissions - almost a commission developer of sorts. We talked about a 75/25 split. If they are doing the work, they get 75% and adilas gets 25%. If they sell some adilas time, the ratio switches - meaning 75% adilas and 25% them (they still make a little bit for selling our time). Everybody gets covered. Cool ideas. We will give it a try.

Phone call with Cory. Going over projects, priorities, updates, and a couple of small bugs.

Bryan Dayton, another adilas developer, and I went down to this Adobe ColdFusion conference in Las Vegas, NV. We had a great time, talking, driving, attending the conference, and playing with friends. Not only did we attend the conference, we had tons of fun along the way. We got to go hiking in Red Rocks one of the mornings. We also got to go mountain biking and climbing in St. George, UT with my brother in-law. Great trip. See attached for my notes from the conference. This conference, more than others, I had some personal breakthroughs in non techy subjects. Good stuff!

Recording notes from 9/26/24 and 9/27/24. Up early checking on the progress of the Bear 100 mile race. Wanted to make sure that the new finish line code worked correctly (live).

New code for the Bear 100 CSV exports. Had to do both the DNS (did not start) and the DNF (did not finish) exports. They used to be very similar. They now have different fields and logic. Small change to the bulk start page. More work on the new CSV (comma separated values) export format. Tons of monitoring the site and fielding a few phone calls, texts, and emails. The new code was being used today on the Bear 100 tracking and runner portal site. Just for fun, here is a link to the news and update that goes along with how adilas helps the Bear 100 mile running event. It has been fun.

Bear 100 - final adjustments to bear 100 runner list. Removed 4 runners, add 3 new ones, and updated a few details. Got the final list from the race director.

Meeting with Hamid. We looked at his code for a bit. He has made some good progress. He has been working on a small little budget tool. Just to help clean things up, we ended up going back to the database and tightening things up a bit. We changed some tables and column names to help it be more self-explanatory. We then went through each page and made sure that each database query was correct and functioning (with the new changes). That helped a ton. Towards the end of the session, we were populating a results table based on jQuery and AJAX stuff. It looked great. He is going to keep playing with it and we'll meet next week to see what he has done.

Code review with Bryan. Looking over flex attributes for stock/units. We are close. Just need to refine some of the dynamic searches and then we should be good to go. We will hit it again tomorrow with fresh minds and brains. Sometimes, you just get to a spot or point and you can't really think very good.

Emails and checking on some funding. Working on the Bear 100 and doing some testing and reading through logic flow.

Developer meeting - We were calling it our "pause and pivot" meeting. I started out and we talked about some of the new development that we have done. There are some cool pieces and projects that have been pushed out recently. We then rolled into an MVP wish list for ship A (small project list that we would like to get done). We then talked about the crunch that we are in (financial and cash flow stuff). It's not super bad but we are struggling a bit. We have spent huge amounts on client acquisition stuff. Trying to make people happy. It gets super expensive.

Alan did a small slide show and presented on some things. Alan did a great job. We had some open question and answer stuff. Dustin had some questions about maintenance budgets. See attached for Alan's PowerPoint. He started out with the 4D's, where we fail or fall short. We then talked about some cycles and how we plan on breaking those cycles.

Steve talked to the guys for a bit and then we wrapped it up. Quote from Steve "What you think about, you bring about." Not sure where he got it, but I liked it.

Basically, the plan is to pause and pivot, meaning, we will stop development projects for a bit until we can get caught up. The developers will do direct client work and custom code so as to relieve the burden from adilas. We are going to help them get projects and also help them with oversite, consulting, project management, and code sign-off. Another big goal that we have is to define ourselves a little bit more vs just going wherever the wind blow. This is both in people, roles, expectations, and development efforts.

Looking over some loan documents and possible line of credit stuff for adilas. I spent well over an hour reading super technical legal contract stuff. My eyes hurt... too much legal talk.

Multiple sessions throughout the day working on the new Bear 100 mile race changes. Going through internal and external pages to show the new dates of the event and the new inbound CSV uploads (new format). Quite a bit of time spent conditioning the pages to handle the new import format and style. Light testing. Uploaded 350+ new runners. Prep work to help the new pages go live tomorrow morning.

Emails and recording notes from yesterday.

Bear 100 data team meeting. We had multiple people on the call with us. Good turnout. We spent some time and explained some of the new changes and how that will benefit all of the people involved. The Bear 100 has worked with the local Ham radio club and has built a small runner logging tool (small piece of software). It will help speed things up, help standardize the input on site and pass adilas good data. One of the new benefits is incremental pushes vs full or whole pushes every time of the runner data.

Switched gears and went internal to adilas and the custom interface pages inside of adilas. We spent some time going over the radio homepage interface. I explained all of the buttons and features. Some of the folks have been with us for years and some were new. Good overview and review. I thought that it was a good meeting.

Prepping some bank statements and calling on getting some funding setup. We need to cover some expenses that we occurred in our last big development push.

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

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

- Help protect our clients...

- Set some caps on how much our developers can charge

- Communication back to the clients - weekly reports and billing

- Billing - weekly

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

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

- Possible kickback - commission to adilas

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

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

- Consultation document or a checklist type doc

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

- Setting up boundaries and being firm on that

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

- Selling what we have

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

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

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

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

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

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

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

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

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

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

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

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

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

Touching base with Abby. She has been sick. We will meet up again on Thursday. Pretty quick meeting today.

Jumped over to more work on the Bear 100 mile race and the new import and export formats that are needed for the 2024 race. The race is this coming weekend. Pushed up a new scratch file and sent out a few emails to key data team players.

New changes for the Bear 100 mile race code and runner logging stuff. Looking over emails and new files and samples. They provided tons of new samples, documentation, etc. Almost too much (45 minutes - just reading through things).

Started looking into the test csv upload file for external attempts (non-destructive playground or scratch file). Started making some changes.

Meeting with Cody to go over the changes for the adilas label builder. Going over the JavaScript drawing functions. Tons of them for lines, boxes, corners, rotation handles, basic text fields, text boxes (multi line), images, etc. We also went over his dynamic search and view functions (actually showing the labels). We ended up talking about the image search functionality stuff and light debugging there. He is making progress. His JavaScript stuff is really tight and great. We just need to spend some time on the ColdFusion and database side of things to really make it smooth and flow within our application. Looking good.

To do list stuff. Reaching out to director from the Bear 100. Emails. Checking on bills. Quick phone calls to a number of our guys to touch base. Recording notes from 9/18/24 to 9/20/24. Paying bills.

Emails. Paying bills, recording notes from 9/17/24, and other prep work stuff.

Brainstorming on documentation for the pause and pivot proposal. Prep work and recording notes.

Meeting with Steve and Alan. Going over some rough budgets. Alan had done some prep work there on the budgets. The budgets were in two categories - per people and per area/department (with some flex). The extra portion on the budgets will help each department with R&D (research and development) stuff for their department.

I was pitching some things and we had some good back and forth (conversations and discussions). I took some notes from our meeting. Steve was reporting on meetings with Mike and other possible investors. Here are some other notes that were recorded as part of the meeting:

- Inside look (efficiency) - using modern tech to solve those problems.

- -Problems with bids (hard to figure out actual costs).

- Our developers doing custom client work. What would that look like?

- Steve was saying that is really helps playing both sides of the fence (developer and a user).

- Our clients eat with their eyes. They are looking for the pretty or shinny type tools.

- Sometimes we oversell ourselves. We start offering custom without having them try things first.

- Let's talk and make a plan (talking about interactions with clients). Some clients like to help fund development and others just want it all the way done and then pay.

- We talked about an approach like this: Just try it out, if we need to change something, let's talk, but give it a try for 3 months.

- Steve was talking about sales. He was saying, just talk to people about what we do and offer. There are lots of people (potential clients) who have needs.

Towards the end, Alan and I talked about swapping out some training stuff (adilas stuff and code stuff). Quick phone call with Steve to go over a few things. He had to drop off early due to his laptop running out of power.

Working with Hamid on his budget tool. Lots of training and review on both ColdFusion and JavaScript debugging. He is trying to tackle a bunch, all at once. We are slowly making progress. Mostly a work session tonight.

Working on a proposal for Steve and Alan. Looking at a number of pages and pieces from earlier this year and end of year last year. Reviewing, planning, looking at numbers, and doing prep work for the proposal.

Quick meeting with Bryan. He had some questions on flex attributes for stock/units. We also talked briefly about restaurants and he showed me the "no" and "extra" functions for his line description modifiers. Say you are selling hamburgers. The "no" and "extra" options could help for things like: no pickle, no onions, extra ketchup, extra cheese, etc. These line description modifiers have to be turned on (a setting) and then added and maintained on a per item basis.

Work session with Abby and Shannon. We worked on two pages in the presentation gallery this morning. We worked on some sub pop-ups (modals) for the maintenance page and some new information on the vision and future page. Our plans are to circle back around and fill in more plans for the vision and future stuff. That will be fun. Anyways, that's where we are headed.

Met with Alan again. We were working on some plans and rules and expectations. We logged into adilas and did some looking at budget numbers, revenue, and expenses. Good session, trying to figure out a plan and what processes and/or rules to put in place. The further we go, the more set some of these processes need to be. We are making good progress.

Meeting with Cody for code review on the version 3 adilas label builder. Introduced Cody to Alan and let them talk for a bit. Going through the pages and finding bugs and going over code. Deep code review of his project. We went through a bunch of pages for both ColdFusion and JavaScript pages. Looking good.

Phone call with Alan talking about budgets, structure, plans, and how to get control of the development and planning. Setting up guide rails, processes, and procedures. Switched over to GoToMeeting and did some planning. Lots of talk about budgets, departments, and processes.

Phone call with Cory about the deli style barcodes and tightening it up a bit. Making a few small changes to help out with the actual client and what they are doing and how they are using it. Pushed up code. Recording notes from yesterday and today (9/16-9/17). Fixing some internal shopping cart messages. trying to make the style match for the new mini scan cart.

Phone call with Steve. We covered a lot of topics. We talked about people, ideas, plans, and where we are heading. We talked about payables, who we owe, who owes us, funding, revenue, etc. We were throwing ideas back and forth. I pitched a few ideas to Steve that Shannon and I were talking about earlier this morning (see EOT # 11405).

We may end up trying some things including investing in peoples (strategic personalities and skills) and also allowing our developers to do some side work or subcontract work (to keep them going). We tried bringing them fully under the adilas umbrella but that is a huge financial burden. They all used to be independent contractors. We are thinking of going back (in some ways) to that type of model. It's that or we have to let some of them go.

We talked about sales, projects, features, education, marketing, communications, etc. We may look at trying to get some more on the SBA loan and use it all (ish) to fund people filling specific roles. The list of projects is unending... we may have to leave that as is right now. That ball will keep rolling. In the mean time, we need to let the developers pick up the paid client work and setup some rules to help us all play along.

Working with Shannon. Showing her the new deli style barcode stuff. Small demo. Talking about debt and plans. That lead to a discussion on a number of topics. Here are some random notes... (not all tied together but what we were talking about):

- What if we set limits on how much we do for a new client. We can still invest in them but there are limits. Finding a good middle ground. We get in trouble with "it should" (expectations). We can't really fully stop this - meaning investing in our clients.

- Coding actually takes a lot of both time and money. Awareness is a great place to start.

- It might be hard for the builders to be the sellers (all we see is what needs to be done - meaning the developers). Possible disconnects.

- Still do what we do but put some boundaries on it. Say, spend $10K and show them what we are doing for that vs just an open ticket.

- Setting up checkpoints... to help us and the clients to move along. Healthier steps vs just plunging in.

- We have done a great job with what we have to work with.

- We were talking about different personalities and roles.

- Some transitions are coming. Along those lines, transitions take time.

- Our guys have been very willing to try to play into different roles (code vs sales).

- Sometimes there are painful talks and meetings.

- Some of our solutions come from our experiences... that is both good and bad.

- Our greatest weaknesses are overused strengths. There is more overlap in our strengths and weaknesses than we know. Sometimes we get so good at things we don't mix and blend, we just push on what we are good at. Flipsides - gains and losses. Patterns and phases.

- We totally switched gears and talked about plugging money into people vs code or sales. We've tried those other things before. Just a thought, maybe focus on people and key positions (stable pieces or needed pieces of the puzzle).

- Back to limits and checkpoints - communication and expectations and requirements.

- Talking about the working genius and how each of us plays into that mix.

- Hiring to our needs vs forcing in people who are already on the team.

- In some ways, okay, a lot of ways, we like the random... Random vs super strict order and organization. We need someone or something that will allow for some randomness and still provide structure. Setting up light boundaries. We have created some awesome things from the chaos... We can also see that full chaos will drive people insane.

- This is a question - Are we helpable? - Are we doing things a different way (like a welfare situation - helping people and they just go back to what they were doing). We don't want someone to come in and put us in a straitjacket... What can we do to help ourselves to create new mixed processes. We might need to find good matches (personalities and traits and skills and costs).

- If we invested in people, we would have to help them define their roles and help them in their pieces and processes. It could help us develop our underlying structure. That would be awesome!

Checking on the code for the complex deli style barcodes. Finished up and did some testing on the page. Looking over the page flow. Fixed a few error messages. On the error messages, I changed them to show them in a new format to match the new mini scan cart style.

Recording notes from the day. Emails, including a note to the ladies at lucky puppy about having to cancel the meeting for tomorrow. Just ran out of time.

Working with Eric. Going over some AJAX Json parsing errors. Lots of back and forth and trying different things. Couldn't find the error or figure out if the page was refreshing itself or somehow routing differently. Kind of a weird error. He may need to get with Alan (other developer) to see if they could figure things out. I helped where I could and was a second set of eyes, but it was kinda getting over my head.

Meeting with Bryan. Going over flex attributes for stock/units. Switched over to invoice aging and receivable reports. Small layout tweaks and added more options to see tip amounts on some of the reporting. Looked over some other code on aging for on account payments.

Meeting with Cody. Going over progress on the adilas label builder page. He has got it quite a ways along. We need to do some major code review, but it is looking good (ish) - just needs a little bit of loving. We will meet again on Wednesday for a multi-hour long code review. If we need more, we'll book more time.

Emails and paying bills.

Working on the complex deli style barcode logic. Lots of nested if statements and figuring out reverse math based on prices, quantities, and extended totals. Small work session. It's pretty deep with a lot of moving parts and pieces.

Working on the logic to help with tying in the complex deli style barcodes to the parts homepage. Deep in barcode land. I'm trying to tie in the logic as high as I can so that I can use other existing pieces without duplicating tons of code. It's pretty tricky.

Prep work and looking around on the deli style barcodes. Making a plan.

Meeting with Bryan to go over some code. Going over projects and light review on some code and small bugs on accounts receivable reports. He is going to fix one more thing before we push those new changes up. We then flipped over to a different project and looked at some new code on Bryan's QuickBooks API stuff for invoices on account. He is making tons of progress there. His new code pushes up on account invoices and then records the external alternate id behind the scenes. Then, when that invoice gets paid off, internally, he used that external alternate id and pushed up payments to the correct invoice inside of QuickBooks using their API sockets. He is getting good at using that API route.

Sent a small email and error message to Calvin on an FTP error.

Meeting with Hamid. He has been working on his budget tool project. He had a couple of different solutions (options that he was working on). We went through some jQuery code and built a dynamic drop-down, that when clicked or changed, populated a sub drop-down dynamically. Lots of training and testing along the way. Going through things line by line. Good session and good learning on both parts (his and mine).

Recording notes from 9/11/24.

Working with Shannon and Abby on the presentation gallery. Shannon had a few new definitions and Abby showed us a graphic that she is working on for the 12 main player groups. Pretty short meeting today. We will hit it again next Tuesday. Shannon is getting close to having her baby (any time).

Back on the complex barcode settings for the mini scan cart. Working on the logic and action pages for the new settings. Also tied them into the session scope from the login process clear out to changing corporations. There are 7 new secondary barcode scan settings that are playing through.

Quick phone call with Bryan going over on account invoices and possible updates to the QuickBooks API. We may have to tie things in tighter and use the external alternate id fields to keep the relationship tight. Quick phone call with Steve. Touching base. Recording some notes from 9/10/24.

Phone call with Alan. We went over a bunch of topics. We started out talking about mins and maxes (inventory controls). We then moved into a number of other topics. Here are some quick thoughts:

- Life, motivation, and feeling appreciated.

- Upcoming Adobe ColdFusion Summit - Coding conference coming up in the end of September and first of October

- Talking about percentage ownership of adilas and what are goals are

- I've got a new project coming up for the Bear 100 (new CSV uploads and exports). As a fun throwback... Alan and a guy by the name of Nick helped me the first year we did the Bear 100 code for helping to track their runners and such. That was back in 2015. Crazy!

- The value of a buddy to help you get through the mud and the muck. Sometimes changing the focus from the task at hand to helping out a buddy or having a buddy along helps you get through the rough stuff.

- Alan was saying that he feels like we are developing a "Frankenstein type application". Our plan is to make a whole cohesive application but we tend to do sprints, change out an arm or a leg, and then the rest of the application stays as is - Just for fun, imagine an arm made out of metal, a leg out of wood, etc. Sort of this mismatched or hobbled together end product. We have good intentions. We get hamstrung by fires, funding, and talent. It's a constant battle. What you end up with is - a Frankenstein type application. Kinda funny and kinda sad. It is what it is.

- It would really be nice if we could onboard or help people get going easier. That is one of Alan's goals, going forward. It may take a minute to get there, but it is important and hopefully in the near future (next couple of years or sooner).

- We spent some time talking about the cost of chasing clients and client acquisition costs. That scope or value has gone up for us in the past few months. We have to be careful there. It, meaning costs, can get out of control pretty quickly.

- Alan would like to build some standard templates to help people upload things - items, part categories, customers, vendors, expense types, employees, etc. That would help with the onboarding process and put the power more in the users hands vs waiting on us and/or us holding their hands to do actions like that.

- We are going to touch base next week and see where things are at. That will be good for both of us.

Emails and paying bills and recording some line of credit funding stuff.

Working on new complex barcode settings for the mini scan cart.

Emails and paying bills. Switched over to working on the new settings for the deli style barcode stuff (parsing complex barcodes). Working on adding the new settings (seven of them) to the mini scan cart page.

Phone call with Steve. Talking about projects, developers, and payables. We talked about current needs, known upcoming needs, and other possibilities. It just keeps going. We talked about managing things and who is doing what or supposed to do what. That is always a challenge. Steve was saying that he is having someone ask him what is being done and who is working on what. Other people are starting to want to know what we are doing and are somewhat holding our feet to the fire, per say, as to what we are doing and accomplishing. That is both good and bad. Anyways, we will keep going and see what happens. That's about all that we can do, at least that's what it feels like.

Meeting with Shannon and Abby. Touching base. Abby had some new popup modal descriptions for the core concept on the maintenance page. We did those new descriptions and then jumped off to work independently. After that, I did some emails and small to do list stuff.

Tech support for a client. Looking into some of their settings and took some time helping to configure things as needed. Changed some colors on their look and feel, removed some unused locations, had to search the system to make sure that they weren't in use, and spent some time playing with their ecommerce and emailing quote settings. Sent an email to the client with an update.

Emails. quick phone call with Cory. Making changes to some stock/unit API's inside of adilas. Added some new image helper info to the getBulkStockPhotos method. Modified two other stock/unit methods and included some other columns. Pushed up new code for testing and let the client know about the new changes.

Emails and recording notes for 9/6/24. Paying bills.

Meeting with Bryan to look over a test or scratch file to test or play with the data. This is for some changes to the QuickBooks API connections. We have to grab invoice data by date, by corporation, and whether or not the invoices were fully paid or on account. We also needed to track payments and which payments were added after the fact for the on account stuff (accounts receivable).

Switched to a request for an oil, lube, and filter software tie-in. Basically, a one-to-many for customers with one or more vehicles. Went over some requirements and ideas. They need a reverse look-up based on vin number (car or auto id) to customer. They also need a full inventory control system, POS (point of sale) system, payment integration, and preset products and services. We already have a ton of those pieces. We just need to alter the flow a bit. We want to do the same thing with puppy stuff. The big difference is a one-to-many between customers and pets vs customers and vehicles. The whole deal is a multi-relational database with smooth interactions between the different pieces.

Client meeting with an outside developer. He had a number of valid questions about the adilas API sockets. How to turn things on/off, what servers, what corp key id's to use, what API methods, how to check for data, and other settings. They wanted more helps with full location names (not just the location initials), they wanted the additional notes per stock/unit, and they wanted more help on images. They wanted us to build out the full image path for each stock/unit. I told him that I would work on those changes. All valid requests. Good stuff!

Recording notes from earlier this week (9/3/24 to 9/5/24). Then back working on the dynamic placeholder values for the adilas label builder app. See attached for a 6-page document of what some of the dynamic placeholder values look like. Not the easiest reading, but it will help out the developer who is working on the adilas label builder app.

Meeting with Abby and Shannon. Talking about removing friction out of processes and sub processes. Constant work of refinement. We were commenting on how we are trending and creating new settings so that people can configure their own tools that they use. They are not required, but if used, they may be customized. I gave them a small demo on the deli style barcodes and how that works.

We then switched over and started doing a small work session on verbiage and new icons for the business functions in the presentation gallery.

Code review with Bryan. Small fix for the mini scan cart. Pushed up code to data 0 for testing. Going over Bryan's plan for some QuickBooks API socket fixes and changes. We talked about building out a scratch file vs just coding the new changes. It would be nice to check things without having the hassle of doing the full API back and forth stuff.

Back working on the dynamic list of placeholder values for the adilas label builder.

Quick meeting with Cody to see progress and answer some questions. Cody is still learning the system but getting much faster. He was showing me some local filters based on JavaScript stuff for showing certain page results. We talked about next steps for the label builder. I told him that I would get him a list of dynamics (text placeholders) per application type to help with substituting or swapping out dynamics (on the labels) with real data.

Meeting with Steve. Responding to the problems and requests, that's what we do (just in time problem solving). Steve jumped off and I started working on implementing the new deli style barcode (complex barcodes) stuff into the mini scan cart. Before I did that, I spent some time and beefed up the sample deli style barcode tool. I also checked in with Bank of America about some funding options. Reviewing some documents from Cory on deployment practices and light budget numbers.

Emails and then a phone call with Bryan about credit card numbers (reporting - comparing adilas numbers with the gateway numbers). We also went over some changes for the QuickBooks API that are wanted. Our client is wanting AR's and account receivable info sent over via the QuickBooks API. Light feature creep (that project is growing) and talking about setting lines and expectations. We don't mind doing all kinds of custom code, but we have to have it flow in the correct channels and paths. We also need to make sure that people are paying for the custom code work. We kinda struggle there.

Zoom meeting with a client. We had Steve, Cory, Sean, and I on the meeting and two of their people. These are some small notes and request:

- On PO's, they want the part reference number added to the PO creation section (multiple pages). Basically, they want another column on a number of pages so that it flows through the PO or inbound inventory section.

- Mins and maxes per item (single quantities as well as case or box size values). They want these values to help with the ordering and re-ordering process. We talked about possible use of parent attributes. I'm not sure about that. They want those (parent attributes) to play into the mix with rules or then enforce those rules. That's the part that I'm not sure about. They want the mins and maxes (along with case sizes) to help build the PO for them.

- When receiving the PO's - they bulk flip the quantities. That works great. They would like some help with the subs or sub inventory counts on that process. Basically, a bulk flip on the subs as well.

- Remove "on account" options for counter sales - invoices where no customer is assigned.

- We did some training and drawing (scenarios) dealing with dual payments or mixed payments using multiple credit cards, cash, and gift cards - small training.

- Small demo on the deli style barcodes and how that will work. Basically, an on-the-fly barcode that has item numbers and prices encoded into the barcode. We have to split things apart and basically interpret the barcode vs just reading it and matching it up to an item in the database. You break it apart and do some reverse look-ups of sorts.

- On PO's, show current activity (per vendor for a given date range) and/or a show all items button - quick links.

- Talking about other stores going live and some possible timeframes (rough).

- Quick internal talks after the client had left the meeting - who is going to do what - tasks and projects?

- Cory and I stayed on the meeting once everyone else had gone. Going over some existing bulk pricing tools and other upcoming projects.

- One upcoming need is for a client that needs help with the adilas API settings. They are requesting new info, a few new columns to be returned, and easy access to backend data and values.

Back working on the logic for the deli style barcodes and interpreting complex barcodes. Testing and merged it into the master branch.

Meeting with Bryan to go over a few different projects and new code. Light code review. We pushed up some code and even did some live testing. We also got into a small discussion about a couple of bugs that we found. One was a co-dependency on a new touch level setting in the shopping cart. Another one was a column disconnect (report headings vs report data - missing a column heading). The other one was a filter (search by age on a receivables report) but we weren't sure how to use it (just need to look up the logic and then record our findings to help our users).

Working with Steve. Talking about priorities. Started on a scratch file to read complex barcodes (deli style barcodes - the item number and the price are encoded into the barcode). Spent the session working on the new logic and testing via the scratch file.

Quick meeting with Shannon. We touched base and then jumped off to work on our own projects. We will hit it again on Thursday. Emails and paying bills. Phone call with Bryan. Quick code merge for Cory - restoring quotes to cart and helping flip the invoice type. Yesterday was a holiday. Today felt like a Monday, even though it was a Tuesday. Random odds and ends.

Quick phone call with Bryan, going over projects. We then jumped on a GoToMeeting session really quickly. Going over flex attributes for stock/units. We have a client that could really use that feature. I bounced into the pages and refreshed Bryan's memory on what we are looking for (recap of sorts). He has already done similar projects for other application players (time, customers, and PO's). This new one will be for stock/units (another one of the 12 main player groups).

Emails and recording notes for the day.

Going over projects with Cory. Worked on a small fix for restoring quotes to cart. She has a client that wants a small change. We talked about the customer to additional vehicles project. it was on hold (paused), but we need to get it out of mothballs and start it back up. We also talked about tips and credit card transactions. We want to expand that out to other non credit card transactions (really beef it up, including tip splitting between employees/users). Lastly, we went over some ideas on request PO's and how speed up the tie-ins between the PO's, the actual received quantities, and the quantities recorded on the subs. Small work session of sorts.

The client demo got rescheduled. Steve and I used the time to go over things. We went over Bryan's new cart line description modifiers, and I showed Steve a demo of those new features (it will go live tomorrow). We also looked at some other code and projects. We talked about building out aggregates (database level counts, sums, quantities, and quick look-ups). We want to do aggregates for quick quantity numbers for parts and sub inventory. Once that is finished, we have tons of other pieces that we want aggregated as well. We then talked about other upcoming projects and who is working on what. Towards the end, we also set aside some time for some work sessions next week.

Emails and recording notes. Meeting with Bryan to go over some of his projects. He is working on the cart line description modifiers. This is basically a way to setup multiple line descriptions and then click and add or modify the line descriptions as needed. We merged in some code and did some testing. We had to fix a couple of small issues but got it working on the live server.

On with the Bear 100 data and software team. Discussing the new app that they made with smaller csv and incremental sending and exporting of data. I was patched in via phone for the audio and using google meet for the video (screen sharing). We talked about plans and timelines. The Bear 100 is in about 1 month. We are planning on moving forward with the new app.

Meeting with Hamid. He is working on a budget tool. We went through things and tried to get his local files back on track. He had been spinning his wheels a bit and needed some help. Part of that is learning. We spent the whole time going over code and team coding on his little project. I sent him a small sample of some jQuery stuff that I made for Cody. Hopefully it will help. He is going to review it later this week and first part of next week.

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

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

Went up to Bryan's house to take him a label scanner and Dymo label printer. We got it all setup and did some practice prints and what not. I also had him jump onto Cody's label builder branch (new code project) and look around a bit. I'm going to have both Bryan and Cody do some co-coding on that project.

Working with Cody on his label builder project. We jumped on the GoToMeeting session and passed code back and forth (pushing and pulling) to do some local testing. We had to install some Dymo label printer software and play around with that for a bit. We made a few changes and talked about next steps. I'm going to connect Cody and Bryan to work together a bit. That should be a good match.

Helping Amber (my daughter) with some of her organization of the printouts of the adilas developer's notebook stuff - physical printouts of the elements of time with planning, brainstorming, and other notes.

Pushing up some file for the presentation gallery files. Created a new folder for the old or original presentation gallery vs the new one. Recording notes from today.

Recording notes from a client meeting and adding additional details to my original notes. Added the new notes to element of time # 11333 in the shop.

Looking over Bryan's line description modifiers project. It's coming along. I made a few suggestions, and we'll tighten it up a bit and then it should be ready.

Meeting with Shannon. Abby joined us part way through. We were talking about risks and costs and how they correlate and run together. I can't tell you how many times we see repeating patterns. What do you do about that? Great question. We were talking about personalities and strengths and weaknesses. Question - what you value? What you end up getting out of a relationship and/or a business is somewhat of a reflection of you and what and who you are. I really enjoy some of our talks. It's therapeutic for me and hopefully for the girls as well.

Setting up a new schedule for some meeting times. We are going to be changing it up a bit in September. We got into a small work session. Shannon has some new text and verbiage for new modal messages and Abby had a bunch of new icons to add to the pages. Pushed up the new changes.

Emails and then reviewing a video from a client meeting last week. Took my old notes and printed them out. I then went through the video and would pause it as we were talking about different subjects. I made a few updates, changes, and additions to the older notes (eot # 11333 in the shop). I'll translate it into digital and then we should be good to go for at least the overview.

Emails and recording notes from 8/21/24, 8/22/24, & 8/23/24.

Recording notes from 8/15/24 to 8/20/24.

Meeting with Steve. Going over new settings. We have or there is a small communication gap, even within our own team - who is doing what and what is either live or in progress? Crazy how quick things go and change.

We spent some time going over notes from different client meetings... Liberty Machine Works (stock/unit stuff), Lucky Puppy (time and scheduling and texting), etc. Lots of moving pieces.

Went over the new label builder progress. Talking about next steps for American Made (more sub inventory rules and controls, faster PO ordering process, and speeding up steps). We also looked at their deli barcode labels (standalone complex barcode). The scale was purchased from a different vendor, and they just want to use it and have us interpret it (what the barcode means). Talking about building complex labels.

Emails, downloading a Zoom meeting video from yesterday's client meeting. Quick fix for Sean on some decimal formatting. Recording notes from 8/13/24 to 8/14/24.

Emails and pushing up code for Bryan.

Looking into beefing up the logic for the auto open next sub inventory package project (new sub inventory setting). Built a new function to help count unique subs within a cart. Lots of testing and trying things. Sent a message to one of the guys about pushing things live. I just want to make sure we don't interrupt anything (live processes).

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 pasted

- 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 mult-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 neede, 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.

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

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

Emails and text messages. Sean found a bug in what we are doing for opening up the next sub. We are just checking it against the database values. We need to check to see if that same sub is already in the cart (in memory). Most of our other logic is based on existing database values, not cart or memory logic. We need to check against both values (database and memory). We may need to write a function to help look-up any other items in the cart and their quantities.

Switched over and did a little bit of prep for an upcoming client meeting.

Meeting with Shannon. Talking about personalities and styles and some of the variables that go along with that. People can be very interesting and yet also challenging at times. After the meeting with Shannon, we decided to break off and work on our own. I jumped into emails and recording notes. Quick phone call with Sean to explain the new functionality on auto open next sub settings for sub inventory.

Recording notes, emails, and such.

Went up to Preston, Idaho, to work with the folks at the Liberty Machine Works business. We (Bryan Dayton and I) ended up in a multi-hour teaching, training, and consulting session. It was fun. They had some questions and suggestions. That is great. We helped them out with showing them where to find certain things and what not. Here are a couple of my other notes:

- They needed both physical locations and virtual profit centers or business classes or classifications. We ended up changing the corp-wide setting for "location" to "class". It just fit their vocabulary better.

- We went over some flex grid options and I recommended the help file for that section.

- There are different points within the system that they wish that they could put a push notification or some sort of communication prompt. Say when things are added, flipped between statuses, etc. They would love a text or an email that has rules and/or is based on rules and does a push notification with options.

- They wanted to know where the page or setting was to change the stock/unit numbers. By default the system starts at a new stock/unit number of 1 and keeps adding to it. This feature lets you start a new stock/unit number with whatever stock number you wish. Then the system will As a side note, a few days later, Steve helped me find the page. It is called top_secret/secure/new_stock_number.cfm

- On the stock/unit checkout process. There are multiple pages (multi-step process) and they don't use all of them. They would like some settings and be able to customize that flow process. That would save time, brain power (remembering what to do and what to skip), and actual clicks. As a follow-up, Steve showed me some new settings a few days later that eliminate a couple of those pages. I will pass that along to the client. It is called top_secret/secure/settings_stock_units.cfm

- We spent some time going over elements of time, work orders, sub time tracking, and such. They are looking to use elements of time to help them keep track of work orders and internal projects. Tons of potential there. I also recommended that they read the help file for the elements of time section.

- On of the last things that we went over was tying things back and forth with the bank. Basically, helping to bank reconciliation as well as auto entering things to help keep things up to date. This still may take some thought and research but I thought that I would record it. Bryan Dayton from the adilas team is already looking into options here.

Meeting with Steve. We spent some time talking about the current state of things and where things are heading and going. Just for fun, Steve was talking about companies hiring robots and having those robots do a bunch of data entry work to help with the constant flow of data coming in and going out. He was talking about robots being a price or business expense in order get the data that you want and need. People want an intuitive system. They don't want to spend the time or money to get trained. Ideally, they would want to be able to open it up, and it just runs, or you know what to do. Talking about business and divvying up the workload (who plays where and what in the sandbox). If just one person has to do it, the amount of work could virtually crush that person.

We switched over to the new sub inventory settings and had a small work session. We added a new auto clean up subs setting. Built it out and tested it. We then merged it into master.

Once that was finished, we switched over to recipe/builds and added in a whole new search feature to help swap out or replace line items for both ingredients and output items. Basically, a link to another page that helped do the look-up and swapped out the main item for the ingredient or output. You could do this manually before, but you had to know the part id number. We got done what we could and then pushed it up. Steve may alter it and help it out a bit more. Good progress and a good work session.

Emails and tech support (voice messages and texts). Meeting with Bryan and helping him out with some JavaScript tweaks and changes. He is working on the part number line description modifiers. This is a way to quickly change a line item description in the cart based on pre-saved snippets and line description modifiers.

Working on the logic for opening up the next sub. Went in and did some research. Ended up finding the place to add the new logic. Did some conditional statements and looped over the results to help find the next possible sub package. We (Steve and I) made some great progress and even added some code to help open/close the sub if needed. We got to a place where we needed to stop. We'll pick it up tomorrow morning. Brain meltdown... :)

Meeting with Cody to help him out with images on the label builer. We did some light training on using the adilas system and adding images to different places. We had to disable his full group by options inside of MySQL (database engine or database server stuff). That took a little bit. We then worked on some new code to help with the label homepage. I added in a search method and some simple output values. We passed the file back and forth and he got the new code working on his local system. Making progress.

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

Quick meeting with Shannon and Abby. We talked about where we are heading and decided to break off and do some work on our own. I mentioned to them about the need for the presentation gallery, if we ended up having a bigger team. Our goal would be to share the core concepts and the vision of where we are heading. We also spent a little bit of time going over the four phases of team building and how each new team goes through these phases. They are: forming, storming, norming, and performing.