A good discussion between Steve and Sean talking about gift cards and options for training, pitching, and selling just that small feature. Sean has been reaching out to some of our existing clients to see if they need any help setting those things up. I'm hoping to help them out by building a special little page to help new clients just use gift cards. Basically, a mini homepage for quick gift card actions.

Cory joined and was asking about recipe/builds and maybe making some sort of placeholder (variable) recipe/build process. We ended up talking about options to duplicate recipes. At first, we were just talking about the main recipe details and such. It then turned into a full-on duplicate recipe option with options for both main ingredients, outputs, line items, and the main recipe details. Basically, a bulk edit tool for recipes and recipe line items.

Cory and Steve then switched over and were talking about enterprise systems and flow of data from top down and what pieces are done and what ones are not yet done or finished. We are heading in that direction. After that, Cory and Sean were talking about helping out corporations that are doing more and more manufacturing.

Recording notes from the last few days (2/23 to 2/28). Helping Sean with some recipe, build and sell, training with hidden line items and what not.

Bryan and I looking over his rostering settings for elements of time and the horizontal time view page. He's really close to getting all of the advanced rostering stuff (shifts - day, swing, and grave) finished up. We will most likely finalize things tomorrow and push it up. While he was fixing a few things, I was doing some prep work for a meeting later today. We are going to have a potential adilas intern build us a small sub website for a topic of interest. Eventually, that sub web site will point people to the main adilas.biz website. That's the plan right now.

Meeting with Hamid Karbasi, new adilas intern. He will be building a small web site on the topic of the "business zipper" and how we came up with that analogy. Hamid was referred to us by Russell Moore. They had worked together as student and teacher at Bridgerland, in the web development department. Anyways, we got on a Zoom meeting and started going over things. We did a small get to know you session. We then switched over to a small about us and where we came from orientation. I did a light intro into adilas.

We then talked about a small assignment to build a billboard site for the business zipper domain (businesszipper.com). As of right now (3/1/23) it is pointed to the main adilas.biz website. Our goal is to create a new mini site or billboard site (think of a billboard or sign as you are driving down the road that pointed you to something else). In Hamid's words, "all roads lead to adilas". I thought that was good and fun.

We have a number of other domains that we may work on in the future. All of them will be billboard sites or mini sites that point to adilas.biz or a feature or concept within the adilas network/family. We made a small plan and then I gave Hamid a number of resources, info, links, and such. We will get back together in the next couple of weeks to see how things are going.

Talking about data uploads and combing data and other prep work for clients. Steve and Sean have some data uploads that need to be done here in the next few days/weeks. Looking over the chooser pages that John is working on (new look and feel stuff).

Wayne joined the meeting and we did a couple hour work session together. He was showing me some stuff on the Google Workspace and email settings. We were going over SMTP, relay services, and app passwords. We changed the payment options for the Google Workspace account. We then flipped over to a number of other topics. Here are some of my other notes.

- We looked at session values and setting up both application and session values and variables on the server. We talked about a session object manager of sorts. This also includes the main adilas.biz website, shop (ecommerce), web (API sockets), and other public sites. We were thinking of having one session manager object and then passing in special flags based on what section(s) the user/client is using. It may vary or may include a number of different things, at the same time. We talked about sub classes within the session scope or session manager.

- Looking at SQL table joins and going over some options for inner joins, syntax, and converting our older code into different formats. Our goal is to make some of the joins tighter, yet still maintain the agile or flexible interface that we currently have. This is part of the datasource project (splitting up the databases and also being able to combine the databases, if needed).

- We talked a lot about UUID's and how this sometimes slows things down. As a thought, we may just use this (UUID's) on the payee/vendor tables. We spent some time talking about the global id numbers for payees (users and vendors). This lead to a discussion on off coding (altering our current code) to use a combo primary key vs a single auto generated primary key. We went over a number of scenarios and talked through things. We are putting the datasource project at $30K-$60K based on what we are seeing.

- We jumped backed more into session stuff and looking at errors that are undefined in session scope (variables that are used in heads and tops but don't exist in certain situations. We would like to create a master list of all session variables and what their defaults are. If we do this, we will be able to code against things better and really be able to push heavily on the know values. As a side note, we do have some pages that only create session values if a certain task or button is clicked. The code there will need to be changes to check for some other value (is it valid or not). If we do this, it should make our code more simple and more usable and more reliable. That will help.

- Consistency, and always setting things to a known state. Creating that central one-to-many type object.

- Dealing with session values, new rules, and new functions - we don't have to do everything in one swipe. We could do one variable, one page, one function at a time. Once we get it lined out (basically outlining the logic, flow, and template type mentality), we could hand it over to one of our other developers who likes to do processes over and over again. Basically, using our super skilled folk to build it out, then have our lower skilled folks help us push it to all pages and sections. We then would need to oversee things and delegate the tasks to our guys and gals.

Good meeting, making progress!

Work session with Bryan. Standardizing payroll settings. He is going to do some clean-up at Cory's request. We then switched over to advanced rostering and horizontal time view changes and settings. Merged in code and resolved a few conflicts. Testing and working on the demo sites.

Great phone call with Steve. We were talking about direction, options, and how to push the ball to the next level. We talked sales, staff, developers, projects, MVP, plans, adilas jellyfish model, value add-on core model, adilas cafe, adilas marketplace, and adilas university. Tons of different topics. We talked about raising prices, raising funds, selling percentage shares of adilas, and how to help make things smoother and smoother. Who is going to manage what and how to best define certain roles, jobs, and tasks. Great conversation and making progress.

Here are some other random notes:

- Client acquisition costs - Where are they at? Do we fully know or does it change from client to client?

- Increasing development or decreasing development?

- MVP's - minimal viable products and minimal viable plans and minimal viable persons

- Possibly selling up to 51% of adilas percentages and then reinvesting strategically in projects and pieces that we want and/or really need. Plan it all out and then push on what we want.

- As a side note, we went in a number of circles - ok, let's do this... ok, maybe we should do this..., no, let's do this... - next thing you know, you are back where you started. We did this over and over again. The funny thing is, we didn't come up with the same exact plans every time. That means that there is more than one option out there.

- Trying to work the long plan and long play

Aspen got with me and was pitching her ideas on a presentation for world building and trying to get buy in on that subject and topic. She showed me a small PowerPoint slide show (just roughed in) but it had some good stuff. It still needs a lot of work but getting there. We also talked about co-ownership inside of adilas and options there for her as we go throughout this year.

Sean was reporting to Steve about a client meeting and how they (the clients) weren't wanting to do things (prep work or setup). They just wanted it to read their minds and just do it (whatever the task was). Silly, silly. Along those lines, you can see how AI (artificial intelligence) and easy presets would really help things out. You still have to play the game, but maybe helping to make it easier.

Going along with the topic above, they were hoping that it would do multiple tasks at once. For example, bring in inventory, price it, track it, and sell it back out to a single client in one quick process vs the normal processes or tasks. We can do some of that, we just need to know that that is the goal.

Steve and Sean were talking about trailer rentals and tracking those through the system. They are going to get with Shari O. and go over things. While they were talking, I was reading emails and trying to fix a small bug on some formatted dates and times for a custom report.

Shari O. joined the meeting and her and I and Sean did a small training session on using a built-in percentage mark-up tool. We did mark-ups, saleprices, and percentage fees in the cart. We did some light training on existing tools and features. We have a client that needs to charge a credit card processing fee (be able to pass it on to the customer). I showed them the percentage calculators and tools on the add item to cart button. It totally calculates a percentage based on the cart or other given amount. We went through a few examples.

Some of our customers really fight against doing the work that is required to really make things great and really make things work. The tools are there, but the chainsaw doesn't cut the wood by itself.

Cory was checking in on projects, bugs, and what not. She had a list, and we went through things. We talked about some quotes and numbers for a client dashboard. We need to get to the duplicate recipe project for Kelly. We set a date for the 15th of this month to be finished with that project. We scheduled some time and now we just need to do it.

We spent some time looking at a client's data. Small little fix and trying to help a client with their financials. They had some bad costs of goods sold that didn't have a real backing (they plugged the numbers) and thus it was throwing off the balance sheet.

At the end, Cory was saying that she is trying to help support me and the other developers on our projects and time lines. That is awesome. Sometimes (often) we need the help.

Meeting with Bryan and going over some quick fixes that we had to do this morning on some date/time formatting. Small review. Next, he had done some clean-up on the employee and employer withholding settings for payroll that were launched a few days ago. We pushed up the new code and Bryan ran some update scripts to update the new settings for all corporations.

While Bryan was running the update scripts, I was doing some emails. We then pushed up some new code for Bryan's project management stuff. This is a small custom page that he runs all of his stuff (projects) on.

We spent the last hour looking at time, scheduling, and web availability settings. We did some light review and planned another meeting for tomorrow. Planning the next steps to help with scheduling, rentals, and making internal and online reservations.

Emails, research, and recording notes for entries between 3/1/23 and 3/6/23.