Bryan checking into the morning meeting with a question or two. We will have to get with him later to get it all figured out. It wasn't a simple fix. Michael and Sean were talking sales and gift card stuff. Cory jumped on and we were talking about scenarios on reports for showing new columns. If we just add them, not all of our clients like that. If we don't add them, other clients want them. You almost can't win.

Our solution will end up being a mix between show/hide checkboxes and saved settings where they could set their own defaults and then still be able to change things on the fly if they want something different. Anyways, we may end up with a mix between normal filters and options and pre-saved settings to help speed things up.

This is our bad, but we have a small lack of communication to our clients. Here's the tricky part, even if we put something out there, they usually don't read it. However, if we do something and don't let them know, they get mad at us as well. Cory and Kelly requested some changes, now we are dealing with the backlash. Some like it, some don't. Sounds like we need more settings.

Shari O. had a question about the adilas phones stuff. We looked at the page and there was some code that tried to show a sub or outside website that was not in a secured SSL (https) site. We made some tweaks and pushed up the code. Kind of a temporary quick fix.

Wayne, John, Cory, Shari O., and I were on the meeting. They were talking about a client and their servers needs. They (our client) may be closing some of their locations down but want to keep other ones active. Light back and forth on whether or not any server specs needed to be changed on that server. There was also a conversation about the need for more tech support. Both on our side and on the server side (the hosting company). Often we don't need help, but when we do, it is kind of painful.

Cory had a list and was checking on different projects. Good dialog and good back and forth. Wayne may be moving on and working less in the next few months. He is wanting to be more of a part time or fully retired. We need to get plans in place to figure out who is going to be taking over that role and what documentation and knowledge needs to be transferred over. We talked briefly about Dustin maybe wanting to help with servers and also looking at existing knowledge levels. Do we want to bring up one of our own guys and/or hire it out to someone else with more knowledge? Great questions.

Wayne was talking about options for virtually building a new ship. This has been a discussion and topic for years. Do we keep building and tweaking what we have or do we rewrite things and try to go all new (code, architecture, design, etc.). There are pros and cons to both approaches. Due to current budgets, we have to stay with fixing what we have vs building all new. That can be painful as well and takes a lot of time. Wayne was talking about doing a sample project and seeing what kind of time it might take to move the existing adilas structure over or under a new standard framework. There are a number of unknowns, but worth looking into.

Towards the end, John and Cory were talking about look and feel stuff. Also, Wayne and John will continue to work on some outlines and plans for the system architecture stuff. Making progress on most fonts. We'll take it!

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

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

Bryan and I making some changes on the KPI (key performance indicators) dashboard. Small work session. Pushed up some new code and dis some live testing on one of the servers.

Kickoff meeting with Datacap. We will be doing an integration with the DC Direct options for card present and card not present. There will be two different integrations. As part of the meeting, they had a number of key players on the meeting and Eric and I were on from the adilas side. They spent some time going over an onboarding questionnaire (in-take kits) and answering some questions. We are looking for one tool to help standardize things.

Like most merchant processors and gateways, they have a number of different terms and things that they were throwing around (even though Eric and I didn't really know what they were). We are excited to get a good one-to-many integration with multiple hardware devices and multiple standard merchant processing gateways. We already have a number of merchant processing gateways and integrations setup, clear since 2009. We are hoping that this one will be our last one and will help us standardize things into something that is more maintainable and easier to work with.

After the call, Eric and I jumped on a quick phone call to do some follow-up and talk between ourselves after the Datacap folks had left the meeting. We just wanted to make sure that we were both on the same page. Making plans and going over the meeting and conversation. They are going to be getting us a quote for some new testing hardware and the certification/testing stuff.

Emails and recording notes from 4/5/23.

Bryan and I working on some of the new online scheduling. Talking a look at what we have and what else is still needed? Looking for the next logical step. We talked about a number of options and did some drawing and planning.

As a side note, after the meeting, I sent him a few text messages with some ideas about setting up the master time templates, then creating a new element of time that could work or server as a fully filled in sample record (a real element of time using existing manual tools). We could then pull data and values from the sample and hold them in the background. We could then collect the new data or things that need to change and use both the new data (just the things that changed) and the old sample data (old existing record) and make a new record from the mix of the old and new data. Anyways, it seemed like a good idea and possible option. We may expand more on this later.