Quite a few folks checking in from over the weekend. There were six of us on the morning meeting, to start out. After they checked in, they would bail out and do their own work in the background. Cory had a few questions for the group. She and Shari O. bailed out to chat about other things. John had a few questions about some older code that Steve had written. They touched base and exchanged some emails back and forth. Steve and Sean were touching base and setting up individual sales meeting calls. I was chiming in here and there and doing emails and recording notes.

Cory and I going over projects and doing small quotes. We talked quite a bit about settings and different levels of settings (at least 4 known levels - corp, group, page, and user levels). Sometimes adilas is so diverse that we either forget about certain functionality or we never knew that it already did something. It's a blessing and curse - at the same time.

Lots of new smaller projects and some that are more around the $2K to $10K level (medium sized). We spent quite a bit of time talking about options for push notification. Lots of our time was spent talking about a super small mini app that could be installed on mobile devices (apple and android phones). The little mini app would just check for things and let the person know (notifications). Then the user would have to either click or login to the ecommerce page or client portal section. Super simple with minimal functionality. Just use the mini app as a communication channel. All of the rest of the activity would run over existing pieces. Anyways, just going over ideas, options, and drawing out possible solutions. Light brainstorming session.

John popped in towards the end. He and Cory chatted for a bit.

We never ended up meeting. Eric got delayed on a phone call and we just texted back and forth a bit. No actual meeting took place.

Recording notes. Talking with Eric about data driven content and code. We chatted on the phone for a bit. As part of our conversation, we talked about pros and cons of how many servers we have and how we act and interact with them. Certain things have a dependency and other things, on purpose, are completely independent of the other servers. We are trying to create a good mix of convenience and independence or autonomy for each server and/or its supporting functions.

Merged in some code for Eric. Had to do a small local bug fix in order to help it go live. Added in some light error handling (try/catch) on a couple of the DAO's (data access objects).

Small work session with Cory to go over the customer label builder app. This was session number two (of many). Lots of note taking, watching, trying things, and making notes. Towards the end of the session, we went back and read through some of our notes and started to organize topics and sections. It still needs some work but making progress. Pushed up new notes file on element of time # 1455 in the main adilas site. Good work session.

Steve and Sean were going over some pain points from a client who is using the BioTrack API system. We don't know if the pain is on our side or on their side. The client was trying to do something that we allow (combine two products into a new product) but the BioTrack API was giving them fits. Anyways, they are going to look deeper to see if it is a setting, an order of operations thing (what comes first - chicken or the egg), or just not allowed with that outside connection. Light tech support.

After that, Steve was asking me some code questions and how to loop over things and strip out duplicates. We went over some ideas and options. I showed him some other files that do the same (similar) things and maybe he could go pull some of that code in as a sample.

Cory and Steve ended up talking about a discount report and how best to filter it and group it - by item, by discount campaign, by location, by salesperson, by category, etc. Sometimes it is hard to guess what an end user is looking for. They are going to present what they have and then try to get some feedback vs just guessing what is wanted.

Cory and Wayne were going over the new settings. They launched some code earlier today and just cleaning things up a bit. Minor stuff. The changes went pretty smooth. There was some conversation about helping the developers to use the adilas docs and making sure that we update those assets and pieces. We also went over some code that hit in between switching between an old way of doing things and a new way of doing it. We need to keep pushing the internal communication channels. That is always a struggle.

Wayne has plans to switch the MySQL database engine from MyISAM to InnoDB. Some of that already exists, but he is looking to make a full switch over in the next couple of days. We were trying to pare down a couple of bigger tables in order to get the whole database in the InnoDB table engines. The old tables were too big to fit into the newer engine type. Growing pains. Most of these changes will be dealing with table conversions and code that creates new database tables. Anyways, I think that we are finally getting ready for that switch. That will be good and will open up some options.

I've got a custom report and data export that is needed by a client for an outside 3rd party analytics service. I'll be working on that in the next couple of days.

Wayne and John are going to be implementing an internal monitoring service. We currently use a number of dedicated monitoring services. With Wayne and John's new code, we should be able to drop some of those other services. We spent a lot of time talking about security - both internal and external security threats. Wayne took some notes and will be implementing some new features to what they were planning. Good stuff. Lot of talk about encryption and secure database storage and clean-up routines.

Bryan and I were looking into his new changes for the automated emails and corp email settings. he is making progress on that section. He will do some clean-up and then circle back around for a final code sign-off. We are getting closer. He has been working with Shari O. on this project. That is awesome. I also asked Bryan to start helping me with client side or client facing scheduling. That is one of the next big things on my tick list.

Recording notes from today, yesterday, and last week. Trying to get caught up. Sometimes the meetings happen so quickly, or you have to jump from meeting to meeting or topic to topic, you just can't switch fast enough or keep up. Anyways, trying to clean off my desk a little bit.

Back on the bulk edit flex grid tools. Got back in and started to test and ran into problems with being behind the master branch. Spent the rest of the evening trying to get my branch up to speed with master. I was 450+ commits behind. It's amazing how fast things happen and move. This branch was only about 2 months old, but it was way behind the main master branch. The problem that I ran into was dealing with how the corp-wide settings were handled and the new structure that is in place on the live production servers.

Sean and Shari O. were coordinating on some client training that they both are doing. Basically, an I'll do this and you do that, type of coordination. They both bailed out and I was just doing emails, recording notes, and jumping back into my bulk edit flex grid tools project.

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

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

Reviewing code and pages on the edit bulk flex grid tools. Switching branches and rereading things.

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

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

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

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

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

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

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

Clean-up from this morning. Uploaded some notes and a screenshot from our client facing scheduling discussion. Checking emails, recording notes, and back on the bulk flex grid tools project.

Working with Cory on projects. Our main goal was to get back to the review of the adilas custom label builder. We spent the first few minutes going over other small issues and errors. Once that was done, we rolled back into our review of the label builder. We took a ton of new notes. We also came up with the idea of making a custom label homepage, where everything could be based out of. That was a huge step that was missing and really helped to springboard our conversations.

See attached for our notes. Also, towards the end of the session, we started into making some quick mock-ups. Originally it was just to show Cory how you could do it... not necessarily professional level stuff. As we got deeper into it, we decided to save it. They are very rough, but we are making progress. Not production level, but making headway. See attached for those images as well. Just for fun.

Sean was asking about payment solutions and trying to get an easy mobile ready solution in place. He, Steve, and I chatted about some ideas and options. We like the direction, we just don't have any firm plans in that area yet (key word - yet).

Steve and Sean were talking about sales and making plans. They are meeting with different individuals and making each meeting totally keyed or scoped to the individual that they are meeting with.

I was listening in, reading emails, and paying bills in the background.

Meeting and going over projects, updates, follow-ups, and small quotes. Kelly had made a request to up the size of the additional customer contact notes. Cory was doing other things and I busted it out while we were on the meeting. We had to do a database update, check validation, make a few layout changes, test, merge, and update a help file. We got it all tested and pushed up to all servers.

Bryan and Cory were touching base on the invoice due date project and different aspects of that project. Lots of talk about the auto email and email history portion of the project. Things are coming along nicely.

Cory left and Bryan and I started looking into some code for a payment card solution (Deb) that he was working on. We looked over the code and pushed up just the database update portion of the code. We then went to each server, ran the updates, synced up master database tables, and flushed the application variables. Running updates on each server.

Bryan and I tried to reconnect to finish pushing up some code for his card payment solution (Deb). We were having Internet issues and issues with both GoToMeeting and Zoom. We finally resorted to the phone and doing texts to let each other know when things were done. Merged in new code and pushed it up to data 0 for testing.

emails and recording notes. Moved some appointments around on my calendar. Looks like a busy week.

Meeting with Steve, Sean, and Michael - going over an onsite visit that Michael did with Pete down in Prescott, AZ (gun store and shooting range). As we were talking, I was taking notes. See attached for the notes. Some of the biggest requests were dealing with driver license scans, faster credit card and chip reading, and cleaning up inventory (duplicate stock/units). See attached for a couple pages of notes.

Cory and Wayne were talking about having to roll back a small code set that was scheduled for testing. It got crossed with another branch of code that was only partially done. Light talks about testing and ability to reverse things out or back code changes out (roll-back).

We spent some time looking at an error out in ecommerce. Wayne is going to work on it later today or early tomorrow morning. We talked about how cool and amazing technology is when it works and what a major pain it is when it doesn't. We looked into some other errors that Cory had in a small bug review list. As a side note, when reporting the bugs or error pages, we need as much info as possible. Just an error message doesn't give us much to go on. We need a server, a page URL, and any other relevant data. It all plays into the mix, either based on settings, permissions, data, etc. Lots of moving parts and pieces.

John was showing up some of his new stuff on the discount engine. He is working on DAO's, services, and automated testing. That is awesome. We also talked about some new AJAX pieces and being able to test that code. There was also lots of talk about using the services and putting those code pieces into the application scope so that we could us the discount engine stuff all over the system (internal cart, ecommerce, reports, after the fact invoice line item changes, and external API sockets). Basically, code once and then use many.

We ended the meeting with Wayne and John were coordinating on when to get back together to do some more training and even cross training based on their responsibilities. That makes me happy. Good stuff!

Meeting with some of the guys from PayPod and CPI payment solutions. We had three of their guys on with both Cory and I. We got to talk with Mike from the UK, Murray, and Curtis. Good meeting. Here are some of my notes:

- They have built out a web-based management function and basic admin tool. This used to be on us to build out. It is pretty simple, but very powerful. This changes the whole project and takes off close to 75% of the load that was there prior. Great enhancement.

- If we do an integration with them, they would provide all of the new tools, pieces, new code samples, simulators, and also assign us to an integration person to work with us.

- In their new web-based interface, they have included some user role-based permissions.

- We got a quick demo from Mike (based in the UK) and he showed us samples of integrating with a standalone windows app, web-based, API sockets, and an external source. Pretty cool - everything interacted with a window's service (virtual server).

- We will start small and then add on - if we decide to do this integration.

- On our side, we will have to do some OAuth2 integrations with security tokens and certificates. We will also be responsible for normal development, error handling, and basic interactions with the PayPod unit. They will handle most of the basic admin features through their new web interface.

- If we do this, it would be a joint funded partnership. They pay X and we pay Y - ideally matching funds.

- If we needed to get paid back for the integration, we could charge a possible license fee for the cash handling or cash payment solution. We could also do some sort of community funded project for those who are looking for this type of solution.

- Their new PayPod unit has an onboard chip and mini computer built into the unit. This opens up options to be able to share devices through a network or ethernet type interface.

- If we get people to buy their product, they will service all of the hardware. Our clients would be responsible for any prep type stuff - they called it mill work - such as network upgrades, wiring, electrical, and countertop or woodwork.

- They were encouraging a kiosks or self-checkout type model.

- If the partnership flourishes, we could talk about referral fees, commissions, and other sales options.

- Cory was asking about some feedback from other clients. The biggest feedback was dealing with security, accuracy, and more time with the customers vs just chasing and monitoring the cash.

After the CPI guys left, Cory and I jumped on a phone call. We went over ideas, costs, scenarios, options, and what plans would need to be in the works, if we go forward with this. We also touched base on a couple of other projects. If we do this integration, we were thinking that John might the best candidate for this one.

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

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

Emails and research for a meeting with the Hoodie Analytics guys.

Meeting with the Hoodie guys. They wanted a 60-day lookback in order to get any of the changes and modifications. Currently, we were giving them a single day snapshot. The problem is/was that the company they are pulling data from is using transitional invoices, and thus doing work after the fact or while things are a virtual work in progress. Along with the 60-day lookback, they also wanted a last modified date/time stamp.

They asked about API sockets and we showed them what we have. Next, we switched gears and talked about real-time inventory counts and values. All of the data that they are getting currently is sales-based data.

Making changes to the custom data export report for a client. I got a phone call and jumped on with Eric for half an hour. We were going over the inventory snapshot (mini aggregate project for item quantities). We talked about ways of building it out and even adding in switches so that we could do some live testing when needed. After the called with Eric, I jumped back on the custom data export project. Made the changes, pushed up new files and let all parties know about the new changes and update.

Cleaning up from the day and recording notes.

Some of the entries, I was recording here in the shop and then flipping over to the main adilas account and recording small summaries in the sub dates and times for the projects. Steve is really wanting to have us all record our time on certain projects inside of adilas. Trying to see what it really takes and helping Cory to know who is doing what.

Jumped on the morning meeting and Sean and I had a second to catch-up and talk about quotes, follow-up emails, and plans. John joined the meeting and had a few questions. We ended up doing a small session and going over adilas financials with both he and Sean. Just a small update and looking around at real numbers.

John made a suggestion for the sub dates and times and how they are sorted. We flipped things around and now the newest entries are at the top vs the bottom (sort order stuff). Tested and pushed the file live.

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

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

Phone call with Eric talking about possible outside work and options. It is a client that uses adilas but also has other needs. I recommended that he run it past Steve as well. Just touching base.

Phone call with Drew and the bike shuttle/coffee shop stuff. He was asking some questions and we went over a bunch of different items and topics. Here are some of my notes:

- eCommerce and client facing scheduling. He is really wanting to know a timeline on when that is going to be done and finished. He is spending tons of time right now on the phone and doing everything manually.

- Tips - He wanted to know how to do tips. We talked about techy talk and credit card stuff (normal sales vs pre-auths). We talked about unlimited line items, over payments, after the fact values or relationships, etc. Lots of ideas. Not sure where to go with it. I'll check with Steve and Shari O.

- EMV/Chip reader - they have some hardware and want to get someone over there to help them out.

- They would really like some sort of mobile checkout and mobile payment option. They are out of the shop and people just want to pay them right there vs going back inside and what not. Sort of a quick sales (all mobile).

- They would really like the bulk edit on flex grid tie-ins. The page is prepped but not fully online yet. Currently, they have to edit individual lines at a time.

- They also want to get some custom stuff done with monitoring availability on shuttle rides (virtual seats that are available - we are using budget settings inside of elements of time - expected and actuals).

Phone calls with Eric about the USAePay and EMV/chip readers. He is going to check in with the bike shuttle guys to make sure all is well. On the phone with Shari O. going over a plan. We talked about the new USAePay account, EMV/chip reader stuff, and options for handling tips on invoices. After that, I spent the rest of the time working on the Trinity Payment stuff and getting setup on the new USAePay account. I ended up doing a lot of emails back and forth and on a tech support call to try to get things ironed out.

Talking with Cory about tips and how to handle that scenario. We talked about just running the payments higher and then dealing with the tip (negative cash out). We looked at it all the way through to the P&L and balance sheet. That seems to be the best way to do it.

Back on the custom label builder app. We are going through things and making plans. We are wanting to do more mock-ups on the label builder and then pitch those to the client who may want to fund things. Talking a lot about flow, promises, and pitching the pitch. More plans and then physically looking a the code. We didn't get all the way through it but making progress. We fixed some session scope locking issues.

At the end of the meeting, we spent some time and were going over some other projects and touching base on things.

I got on a little late, I was helping my son out. Steve was on a meeting with Kelly. When I jumped on, John was on there. We touched base on a couple of things and then just worked on our own. I was recording notes and going through emails. He was working on his own projects.

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

Anyways, here are some of my notes:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Meeting with George from Datacap. He was referred to us by Matt from Solvent, a different card processor and middleware type business. Basically, they were pitching that they have one API socket integration set and it is integrated with tons of backend processors or merchant vendor systems. Anyways, we have a client who wants to interface with some software and hardware and we don't want to deal with interacting with each and every gateway independently. So, this Datacap company has done the gateway interactions and integrations for tons of gateways and merchant processors. So, if we do the 3rd party integration with them, then we could virtually hook into all of their possible gateway and processor connections. It adds another layer, but it also makes our job so much easier vs having to code to every hardware device and every merchant processing gateway. This could be a great option for us. Anyways, we'll check it out.

After the meeting, Cory and I got on the phone and chatted about possible options. We think that Eric could be a great fit for this project as a full stack developer from the adilas side of things.

Emails, recording notes from earlier this week and today. Phone call with Eric going over ideas for gift cards and pushing that project forward. Eric and I also chatted and talked about doing research and project analysis and if a client needs that, that we could charge for that as well. Basically, breaking up estimates and quotes into project analysis and code development (two parts to the whole). He's got a lot of stuff going on right now. Busy, busy!

Admin meeting. We were going to do some budgeting but ended up getting pulled into other topics of discussion. Lots of talk about 3rd party solutions and our love/hate type relationships. Sometimes, those relationships can be challenging. We also talked about some possible rules for bigger clients and helping them get transferred over to semi-dedicated or full dedicated serves vs staying on the shared environment.

We chatted about a number of up-and-coming projects and ran through some pros and cons with each of them. A number of them are dealing with outside 3rd parties and have some good things but also have some teeth (virtually).

For outside custom work, we are heading towards full pre-payment or getting something upfront and then billing along the way. We have been skunked a few times and had to run things out to bad debt (uncollectable invoices). along those lines, permission was given to Cory to help wheel and deal as needed for certain projects.

At the end of the meeting, Steve was doing some training for Shari O. and myself on his new timeclock and timecards for our internal co-owners and what they are working on. Good meeting. I sent around notes to all of the key admin team members.

Logging into the new USAePay account and looking around. The new one is backed by a processor called Trinity Payment Solutions. Our old one was backed by Newtek as the processor. We are changing some things up. If we go with Trinity, they have given us options to make some passive revenue based on fees and commissions. We are going to try it out and see what we come up with. Good stuff.

Steve and Sean were touching base on sales. Steve had a few code questions for me dealing with queries and flow. John joined the called and was asking Steve and Sean about prices and options for clients (pricing structure stuff). Eric joined and was asking questions about gift cards and going over different ideas.

This may or may not help, but I went in and found a bunch of older files that we were had started and worked on dealing with special accounts, loyalty points, gift cards, customer in-store credit, vendor discounts, and other special account stuff. See attached.

Working and setting up the new USAePay gateway and merchant account settings for our (adilas) merchant accounts. Ran a few small tests from both inside the secure cart and from outside in the online ecommerce bill pay section. Everything went through great.

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

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

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

Work session with Bryan. Checking out code for the auto email project. Looking over code and going over the project flow. The branch is showing multiple merge conflicts, so we will have to do a manual merge (that takes a little bit longer). We also hit a snag on one of the include files (send email action pages). It is called from outside in the public folder but it resides inside the top secret/secure folder. That folder is protected and requires a valid login and session. The code worked great during testing but as soon as it goes live, it will be called via an automated schedule vs a logged in user. Basically, the validation on the secure page will block it from being used due to a missing login. We will have to restructure some code and put a standalone file out in the public folder to help do the same process.

Towards the end of the meeting, we flipped over and were going to look at some of the AJAX stuff that Bryan has been working on with John and Dustin. We were having conflicts while switching branches. We will reschedule a time to look deeper into this. Making progress.

Shari O. and I met on the GoToMeeting session and went over new USAePay accounts, settings, and logins. Part way through I got a call from Calvin and we chatted for a bit. Shari O. and I jumped back in and were looking at more settings and playing around. As part of the meeting, she was showing me what she does to track and correctly process the reoccurring invoices that done inside of adilas. There are a lot of places that we could help her out (automation). We may have to circle back to that.

As part of our meeting, we also went in and looked around on some of the new Trinity Payment stuff as well. Basically, a small look-y-peek into their backend card processing interface. It looks good.

Wayne and Steve were checking in on servers and server-based projects. Wayne was reporting in and giving some light estimates as to timelines and possible rollouts. After that, Steve and I worked on some code for a page that he is working on to help push up some outside client data into the system (customer data import). We worked through some code and logic dealing with lists within lists and how to pull the correct data out. We ended up rewriting some of the code and doing some testing. We got it all figured out and moving forward.

We all jumped on the server meeting. Wayne was showing me his new monitoring services (watching for form submissions and URL values for internal pages per user per server). We went over some of the custom stuff, encryption, and ended up doing a huge asynchronous database update using AJAX and JavaScript. The update did a series of loops and reported back as things were happening. We are switching our database table engine from MyISAM tables to Innodb tables inside of the MySQL database. That was kinda a big internal switch.

Wayne spent some time and showed me around and went through the code with me. I know that we can use some of those same asynchronous techniques to speed up some of our long running reports or processes. Pretty cool.

Wayne was pretty creative how he blended session values, ColdFusion, method calls, AJAX, JavaScript, database updates, and reporting all into one small page flow. It was cool to see the pieces and then watch them work in real time. I enjoyed it.

After that, Steve has some questions with his VPN connection (VPN = virtual private network). Wayne helped him uninstall and reinstall the VPN software. They got it working again. Steve uses his VPN to push up code via FTP to all of the servers. We use that all of the time. If we don't FTP the files, we have to redeploy and pull master code branches on the different servers. Sometimes, the FTP route is much faster, and we can target single servers if we have to do some live testing that relies on certain data or certain sets of settings (data and configuration stuff).

Wayne left and Steve and John started going over timeclocks and internal timecards. Steve gave John a number of new permissions to be able to look around inside of adilas to check and look at numbers. John then gave Steve and I a small walk-through demo on the discount engine. Steve and John spent a bit of time talking about graphs, charts, and adding in eye candy to the system. Currently, it doesn't have much eye cand or sweet visuals to help show the data that we are holding. If truth be known, we are holding tons and tons of super awesome data, it is just hidden and only shown in a tabular format right now. Also, the users have to ask for the data right now, there is nothing that is pushing the important things up to the surface (push technology or using dashboard type utilities). It could really do some cool things if we got the right charts, graphs, sums, counts, and other business intelligence (BI) stats and values. That's where we are heading.

Steve and John were talking about the future fracture project and how each page will end up getting its own page level settings. Things like: What to show? What to hide? What tabs or sub sections will be displayed and what interfaces will be the default per person? More talk about settings, dashboards, and making the data sing and talk vs just holding it all. We really want to get it out into the business intelligence (BI) level. That will be so cool!

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

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

Switched branches and started to get back into the bulk flex grid tools for the bike shuttle company. Didn't get much done but at least got flipped over to that project again. Hopefully more progress tomorrow.

Meeting with Sean over the GoToMeeting channel. He gave Steve and I a new expanded elevator pitch. We went over that new pitch and made some suggestions and ideas. We also spent a bunch of time talking about merchant processing and how things are organized. I showed him the datacap website and I was pitching their ideas and how they connect to multiple gateways and use multiple pieces of hardware to make that happen. I'm excited to see if that will work out. Eventually, we want to either use what they are doing and/or create our own process along those same lines. Good discussion.

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

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

This is an expanded elevator pitch - submitted by Sean Carlton on 8/17/22

Adilas is a complete business solution for business-minded companies. We handle all of your operations, such as Point of Sale, E-Commerce, and Inventory Control, and tie them directly to your Financials, such as Time Clock and Payroll, Accounts Payable and Receivable, Profit and Loss Statements, and your Balance Sheet. We operate in high-compliance industries, such as Cannabis, Firearm Sales, and Liquor Stores, as well as high-value Unit sales, like Car and Trailer Dealerships. No company is too big or too small, with complete systems, starting at $97 per month. As great as Adilas is, "out of the box", we also offer very affordable customization to fit your flow and processes, instead of making you adapt to ours.

Just pushing it up for the record. Good stuff!

Meeting with Bryan. We were moving his code from top secret out to the public folder. This is just so that the system can do some automation for automated emails and invoice due dates.

Working on adding in date-pickers to the normal adilas code. Popping from page to page and fixing things on the fly. I also met with Bryan and we pushed up about 17 files that had new code and/or changes dealing with the automated email stuff. Back on the date-picker stuff after helping Brayn. Merged in all of the changes that I had, so that the ball keeps advancing.

Spent another 45 minutes working on adding in new date-pickers throughout the system on older code pages. Ran into a few errors and let Alan know about them via email.

Steve, Sean, and I were going over progress and ideas on merchant processing. We got a report from a client that they are using one of our gateway integrations and it has been going very good. We talked about progression and how the first one we did for a gateway, nobody knew about it. We then did a second integration for the same gateway using newer tech. That is the one that is going great. We may end up having to convert the company that is using the older integration to the code that is using the newer tech. Sometimes things get lost in the shuffle.

Steve was talking about interactions with 3rd party solutions and making sure that we have money and agreements done up front. We have had too many use us and/or stiff us. We need to cover ourselves.

We were talking about how quickly things change. We tend to build something or make an advancement and go right on to the next thing instead of trying to pitch it, market it, or get a return on our investment. part of that is personality, and part of that is just pressure (we need the next thing), and part of that is the lack of communication (what is new and cool and how do we get that word out?). Anyways, we are aware of it, we will need to keep working on it. Sometimes, we literally have golden nuggets and we just bury them or they get buried because so many other cool things are happening.

Both Steve and Sean are really trying to focus in on merchant processing and figure out a way to get something put together that is as easy as Square (simple POS system with integrated hardware and software - able to take credit cards on the fly) but as powerful as adilas. Just for fun, they were calling it the Square Crusher (aka a similar or competing product). Just being silly.

Cory joined the meeting and had a number of questions from some of our clients. She was asking both Steve and I about our takes on certain things. One of the email requests was dealing with discount campaign tracking and ways of using and tracking promotion codes. Cory and I will talk more about this next week. I have done a ton of this, with my other company, back in the day, but we don't have this built out for adilas or adilas clients yet.

One of the places that we are weak or not as strong is in the marketing and marketing tools for our clients. I'm forecasting, but I'll bet that we will see more of this type of promotion code tracking, flagging and tagging, and tag management stuff come across our plates in the next few months. It is important and seems to be heating up. We will build it out and make it part of our internal and ecommerce offerings. Plus, we'll try to market it ourselves... push it out there for others to use and see. We've got to start doing more of that kind of stuff.

The last major topic of the morning meeting was using API sockets. We tend to build API sockets for other outside parties to use (pull technology - they pull the data that they want based on settings and permissions). We also talked about using other 3rd party API sockets and being able to push updates and records as they happen (push technology - just in time and being able to control how much data is being pushed). We may have to find a mix of both options, but we need to remember that both options exist. We tend to see just one side.

Along with that, we have some clients that are getting bigger and bigger datasets. That becomes a problem. Say we design it so that an elephant could be moved from place to place. Without telling us, our clients move on from elephants, which are already huge, into whales that are four times as big as elephants (just an analogy of sorts). Anyways, there is a constant need to keep making the channels and pipelines bigger and bigger and faster and faster. If we exceed our limits, sometimes we have to keep modifying things and keep pushing our limits in order to get into the game. Hardly ever does it just sit still. Constantly moving targets.

Database meeting with Steve, Wayne, Alan, John, and I. The primary topic was splitting up the bus and making motorcycles (datasouce project or world building project). Basically, the current database is big and has both shared tables and corp-specific tables. We want to split things up so that the whole thing will be faster and more nimble. The whole meeting was dealing with ideas, notes, and brainstorming along those lines. See attached for multiple pages of notes from our meeting. Lots of good comments from all parties on the meeting.

Working with Bryan and looking at a bug on the automated emails. We did some live testing and debugging. We had to get rid of a few references to the session scope. This was a switch between test and live. The fully automated process won't be tied to a user logging in and doing an action. It has to run by itself. Small fix and pushed up new code.

Talking with Aspen over lunch. She is working on some HTML and CSS (web design) training. She is wanting to work for Adilas and do different things. We went over some technical stuff from her classes and then rolled into some business logic and Adilas pain points. She may end up helping me with some research and getting projects prepped and ready for the guys. Talking about ideas and options. Aspen is my daughter. She will be attending her first year of college this year and is looking to help out where we need some help.

Working with Bryan on his AJAX (asynchronous transactions). Going over some training and explaining the client facing scheduling project in more detail. We were looking at and working on Bryan's scratch files.

Talking about sales and follow-up calls and emails. Steve, Sean, and I were going over some emails that we got over the weekend. We decided that we would reach out to one of our clients, as another potential client wanted to ask some questions to some of our existing clients. Making plans and getting ideas from each other.

Cory joined the meeting and we broke into a small project overview and question session. She was out of the office most of last week and just had a pile of emails and questions for Steve and I. There were 3rd party solution needs, emails, small bugs, and new requests. It doesn't seem to slow down... and if it does, it isn't for very long.

Cory and Steve were going over the compare Metrc inventory page and talking about ideas to help shorten up that page. We have a client that is getting so many sub packages that it is causing problems (too much data). We talked about other possible bulk tools and ways to help them clean-up there data and/or be able to easily filter their records and results sets. Kinda funny and kinda not, but we build and break, build and break. Our clients keep pushing things to huge extreme levels. All you can do is build and break, build and break, try to respond and look forward as far as you can. It becomes an interesting game.

After that, Cory was bringing forward some new requests to be able to duplicate PO's with sub inventory packages. We have been able to duplicate PO's for years now, but not with sub inventory packages because those are all fully independent and have varying sub attributes and usually it's not a straightforward duplication process. It requires too many other questions, variables, and switches. Anyways, that is heating up and we may have to figure out a way to get that going.

Cory and I going over projects. We talked about custom uploads for bulk expenses, referral tracking (promotion codes), merchant processing (working with the Datacap company), and automating emails. We also got into some talks about SMS and phone stuff. Basically, companies are wanting more and more communication options and even extending that out into marketing realms. Lots of requests and wishes for tools along those communications and marketing channels. We also talked about 3rd party solutions, pros and cons, and doing our own internal enhancements.

Emails, phone calls, and helping Dustin with some code. We ended up having to get Wayne involved to help us figure it out. Basically, Dustin's local branch was old and then when we went to make a new branch, there were updates that he needed that were being required for his new branch. We had to manually updates some database tables and then everything worked fine.

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

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

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

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

Working with Bryan on ideas for the client facing scheduling project. See the attached notes. Lots of talk about doing this first round with hardcoded custom variables vs system-wide dynamics. Too many moving pieces to fit within our timelines. We are trying to take baby steps.

Steve and Sean going over some deep ins and outs of custom gram trackers. It seems like the state compliance rules keep changing and certain vendors are and are not providing the correct information. Basically, they are trying to do super detailed math and stay within certain limits and rules but the incoming data (much of which we can't control) is missing vital pieces. It becomes really frustrating and makes you wonder why you are spending so much effort, when you can't control all of the variables and pieces.

Steve and I talked briefly about the SBA loan that adilas took out. The first payment is due in a couple of months. Steve got pulled into another call with a guy and then was going to be jumping on a Zoom session with one of our guys. So many moving pieces. I was doing emails and catch-up from yesterday.

Talking with Wayne on the server meeting about master branches vs other deployed code branches (on other or certain servers). The more servers that we have with specific testing or production branches, the harder it is to manage all of that. We have some code that needs to be live but still may be in the testing phases. That can screw up all of the other live production servers. It can get interesting.

We spent quite a bit of time going over the add/edit new corporations code, issues, and errors. Shari O. has been sending a series of emails out to us to let us know about certain problems, once again, we have some servers on one branch and others on another branch. It can get a little bit interesting. There is basically one branch of code that is hanging up the others, we'll get it all smoothed out and going.

Cory and Wayne were going through a number of small issues and small bugs. They were also coordinating and planning some future testing dates and times. One of the things that is coming up is a data capacity and memory issues. We have some of our clients that are getting so much data, it is getting hard to deal with all of it.

John and Wayne were talking about long variables vs normal capacity variables. We may need to expand some of our JavaScript variables into longer length capacity variables. It got pretty techy talking about memory, caching, garbage collection, and efficiency stuff.

Working with Cory to go over our plans and making a proposal for the PayPod folks. Coming up with an estimate and who would do which part of project. Lots of prep work and project management type stuff. Cory has the actual proposal document.

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

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

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

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

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

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

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

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

Working with John on his custom JavaScript on the discount engine. Going over ideas and being a second set of eyes. We went over some options and I recommended that he build a small scratch file to practice some of the pieces before trying to make it go live and be fully integrated.

On a meeting with Bryan. Talking about settings for the client facing scheduling stuff. We talked about adding in photos and descriptions on the main booking page. Looking at layout and display options. We also took some time and setup his local environment with time templates, part categories, items, and flex grid settings. We did some local testing and got him some data to work with.

We went through a number of local scenarios and parts of the manual flow processes. Brief look at his automated email stuff. Talking about other small projects, if he needs some fillers.

I was late getting in, helping my wife out. Sean was checking in and he reported that he just got off of a phone call with Steve as he was traveling up to Denver. Working on emails.

Meeting with Eric and going over settings and priorities on his current projects. We also talked about backend database triggers, ETL (extract, transform, and load options - data warehousing and internal aggregates). After Eric left, Cory and I were going over other projects. Here are some of the things that we were talking to Eric about.

- Gift cards
- Sales tax aggregation
- Possibly pushing data through API to Weedmaps and Leafly
- Inventory snapshot
- Prescott shooting range - driver license scans

One of our clients wanted to see all of the sub inventory attributes on a custom data export. Doing some testing and prep work.

I joined later on. Helping my wife Heather after ankle surgery. When I joined, Cory, Shari O., and Steve were on the meeting. I was pretty quiet for the first part. Mostly just listening. We went over numbers and budgeting stuff. As we were going over some of our projects, Steve was recommending that we include Mike on some of the upcoming features and marketing efforts. There was also some talk about real time sales tax redemption and money transfers. They are (Stev and Mike) are trying to figure out some angles on state compliance systems and using sales tax redemption and tracking as a possible angle. Good ideas.

Cory was recording the budget numbers. We also talked about other projects and bids. Lots of verbal reports. At the end, Cory sent around the budget spreadsheet numbers.

emails and recording notes from the week. Crazy how quick it can get away from you. This isn't bad, but one of the new changes is that Steve wants things recorded inside of the adilas account on the different projects. I'll figure it out, but I'm currently recording some things in the shop (where I record most of my primary notes and such) and also inside of adilas (just as sub notes on a bigger project). Interesting.

Steve and Sean were doing some deep dives into some of the packages and helping to auto clean-up some of the sub packages. It seems like samples are crazy and can really clog up the system. They are given freely and sometimes don't get managed as tight as actual inventory. While they were doing that, I was doing emails and recording notes from last week.

Steve and Cory were talking about pages, packages, and sub inventory. Shari O. popped in and we ended up having some light budget talks. The four of us talked briefly about the state of adilas and where we are going. Lots of good things going but we do need to be careful. On a different note, many things are changing all around us - including code changes, settings, clients, needs, expectations, etc. It's a moving target.

Light talk about what is an MVP (minimal viable product) for what we are doing? Even though we have so much functionality, do we have all of the required pieces? There are still some things that we need, even for an MVP - although it be a large MVP.

Cory was asking questions about projects and what not.

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

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

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

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

Online with Shari O. going over settings on merchant processing. We ended up looping in a tech from Newtek to help us look at the settings. He decided that he would need to make some changes on his side of the fence. We'll go from there once we hear back from them.

Emails, paying bills, and recording notes.

Steve, Sean, and Cory were on the morning meeting when I joined. Cory was only there for a little bit but after she left, Steve and Sean were talking about setting up a rough schedule for some of their sales guys and gals. Our model has been very open - you have work to do, do it when you can, record your hours. What we are finding is some people need more structure and our super open model is causing people to fail due to the lack of structure. For example: I know that I can dictate my own hours but I know that I work from 9 to 5 on certain days. I plan accordingly and thus have a base structure of what I'm shooting for. I can change it at any time, but base structure gives me a starting place. Some of the new folks coming into our model are used to having a set schedule and then having to abide accordingly. With it being so open, they kinda get lost, don't have a plan, a goal, or anything set. As such, they tend to let whatever the day brings dictate their output and schedule. That is great, but sometimes there needs to be a bit more structure.

So, Steve and Sean were talking about helping their guys and gals setup a base schedule and then if they need to modify that, they can, but at least they have a set schedule. Interesting. I love freedom but it can be bad if not structured properly (and to what level - it may vary).

Phone call with Shari O. and a merchant processor company. We were going over accounts and needed options. After that I sent Cory a text message about some client training that needed to be done for one of our clients. Other emails and follow-ups.

Great meeting with Eric going over his progress and questions on the gift cards and gift certificates. This will be part of special accounts inside of the system (tying into existing pieces and sections). We are planning on doing single corporation gift cards for now. Once we get that done, and if someone needs it, we will tackle cross-corp or multi-corp gift cards. That gets more complicated and we could charge for that and/or those options.

Eric was going over a number of scenarios and use-cases. I loved hearing it. I could tell that he had thought about a number of great scenarios, processes, and even logic level decisions. Checks, balances, validation, flow, pages, permissions, etc. Good stuff. I was really proud of him for that. Basically, try to break it and make it stand on its own.

Part way through the meeting I grabbed the screen and we looked at existing database tables, data, and options. We were drawing and brainstorming on additional ideas. We talked about quick search options, checkout options and flow inside the cart, invoices and payments after the fact, ecommerce integration, and other advanced options. Good meeting. He is well on his way and making great progress. All of this will tie-in and be a part of the special accounts section. We already use customer loyalty points in that section of the system. More things will be coming in future months such as: in-store customer credit, vendor discounts, punch cards, lunch cards, retirement packages or accounts, and other virtual or actual special account. Good stuff.

Zoom meeting with a client and a 3rd party marketing and communications company. They wanted to see if they could get a client's data out of the system to help feed their offerings (marketing and promotion stuff). Interestingly enough, this meeting was requested by our client and them wanting to use adilas data and be able to get it out to other (mulitple) 3rd parties. All of it was dealing with marketing efforts, communications, notifications, and promotions. We, as a company, aren't very good at that (the actual marketing part of it), but companies that are good at marketing need the data that we are collecting and holding for companies. Things such as CRM, POS, inventory tracking, histories, etc. We have all of the data. It just isn't organized into marketing avenues and pathways yet. Keyword, yet...

Anyways, we went over things like: opt in/out, loyalty points, capturing and recording digital signatures, transferring data, as well as push and pull type options for data events and actions. Lots of talk about API sockets and RESTful API's.

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

https://vimeo.com/744675016

On a conference call with Shari O. and a rep from Newtek. We were going over specifics for two different clients and their merchant processing needs. Both sides were educating the other side as to flow, processes, and needs. I had to bail out at 1 pm to get on a new meeting but Shari O. was trying to help negotiate rates for a client where they, Newtek, couldn't provide the correct hardware device.

Meeting with Chuck and going over layout and display options for the "working with time" page (part of the elements of time section). That page has tons of dynamics and was built as a mini prototype for what we want fracture to do and be. Basically, the page uses templates and then either hides, shows, uses dynamic naming, aliases, incorporates settings, permissions, and even eventually sort order and display order. This "working with time" page was built in 2011 but has pieces that we want to do and use throughout the whole system once we move to the fracture level. Ask Brandon for more info on the subject.

Chuck and I were going over design options. We brought up the current page in a simple mode, a medium mode (settings and data), and then in an advanced mode (more settings, more data, and more dynamics). We were drawing pictures and running things through fake mock-up ideas. The page has to be able to handle all of the different possible combinations of settings, templates, defaults, subs of time, flex grid tie-ins, and other dynamics. Each section will end up being in a container of sorts to help with web ready responsive design (mobile friendly). Lots of talk about nav, standards, and where we are heading. The other major variable is how much data is tied to a single element of time. It is just a quick virtual post-it note, an appointment, a project, a timecard, a vacation booking, or clear down to a dispatch level event? Elements of time are very diverse. The amount of data could be huge or super small per element of time, based on the template and the settings and the amounts of sub info or subs attached to the main element of time.

At the end of the meeting (last 10 minutes) we flipped and talked about a small bug that was found and reported to Chuck and also his new promo video for the adilas label builder.

Recording notes from the earlier part of the day. Some of the notes are here in the shop and some inside of adilas per project.

Small side note - Transitions... Sometimes we flip between projects hour by hour... that costs money in the transitions. What if we did things day by day vs hour by hour. It sure would wear us (the developers) out far less if we were able manage it. Transitions can be a killer on time, budgets, and moral.

Working on storing and converting complex datasets for a custom client data extract project. Working on a scratch file to make sure that it would work.

We were going to have a server meeting but Wayne was helping someone who needed his help. It was just Cory, John, and I on the meeting. We were giving a number of verbal reports back to Cory on different projects. I was showing her some code and some of the challenges of what is wanted and needed. Making progress.

Cory and I listened to John talk about the discount engine project. We are looking to wrap that project up here in the next short while. It has run on for months. Our current plan is to at least end this phase of the project. It may get turned over to a different developer to finish up the heavy backend wire-up job. John has mostly been working on the frontend GUI (graphical user interface) and getting the main admin discount engine page tuned up for managers and such. There is still more work needed on tying in other pieces, but that will be part of the next phase.

One thing of note, John was talking about having his discount engine code do a database update on application start-up vs a normal scripted updates that gets ran manually. I don't have a problem with that, but I just want to make sure that we don't tax the start-up process too much. Just a thought.

Sean joined the meeting and was asking about a small bug. That conversation lead into a further discussion about other cause and effect errors (change this or that and it affects this or that or whatever). It is amazing how interconnected a system may become.

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

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

I sent Sean an email with a link to some business consulting that was done back in 2019/2020 by Jonathan Johnson from Epic Enterprise. I also sent his a 9 page document that had even more notes, ideas, and brainstorming for our company and where we are heading. Good stuff.

Working on new logic and added custom data extract files into master for a client. We were making enough changes that we needed to start tracking those inside of a branch. Originally, they were just on the side - a one off page. Now they are part of the master file system.

Meeting with Cory to go over the quote line items for the adilas label builder. We made a small Word document and added in all kinds of notes, verbage, and estimates on hours for each section. That document was sent to Cory via email and also uploaded inside of adilas for that label builder project. We also did some training on adding media/content to sub inventory items. Lastly, we went through some older notes and tried to make sure that we have/had all of the MVP requirements. Productive meeting and making good progress.

Phone call with Eric going over questions and flow for the gift card payments and project.

Working on the 710 Labs custom data extract and data export. They wanted all of the sub inventory attributes to be passed back with every sale and line item. Working on the new code and writing new logic.

More work on the code for 710 Labs and the custom data extract that they are wanting with all sub inventory attributes and invoice line item data.