Scanning and signing some promissory notes for adilas percentage changes. Paying bills and doing emails.

Distributing some adilas percentages to other co-owners as a thank you gesture. Did 10 of them. New promissory notes. printed them out and sent them out via email as well.

A couple of smaller work sessions throughout the day. Spent some time reading over plans for the vendor credit project. Making tons of progress. Checking off things that were done and seeing what is still needed for this project. As of right now, we still need help files, code for voids (deleting expenses), showing vendor credits per payee/vendor (edit modes and printable pages), and all of the balance sheet stuff. Most of the other pieces are done or at least at a good level. I've been working on this project for about a month now.

Sent a couple of hours adding vendor credits to pages that show vendor/payee information. Did this for both normal vendors and employee/users (any payee per corporation).

Back working on vendor credits and being able show proper payments. Added in some JavaScript and a helper field to show the math calculations if using a vendor credit. That should help with showing what will be happening once a payment page is submitted. Added to payment pages for splits, reimbursements, and payments on PO's. Testing different scenarios.

Recording notes from the past couple of days.

Work session with Shannon. Working on BI level verbiage and content. This is part of the Adilas value add-on core model stuff. We didn't get all the way through it and will have to pick it back up next Tuesday. Making progress.

Working on paying for PO's with both vendor credits and normal payments. Added new code and did some testing. Even though this is dealing with PO's, it still follows the normal expense/receipt payment structure.

Emails and then watching a video from Bryan and one of his clients. Going over needs for parent attributes and how best to see and process those pieces. Bryan Dayton sent me a video, and the lady had all kinds of parent attributes for her snack food business. She wants to put all of this info inside of adilas and be able to search and filter things accordingly. Currently, she is just using a bunch of spreadsheets to keep track of everything. Bryan and Sean, in the video, were helping her see some of the cool things that a data table could do with sorting by columns, local searches, exports, etc.

Meeting with the Benning construction company to help with their golf tournament. Touching base, showing a quick demo, and asking some questions. Bryan and Suzi were the main adilas contacts. A lady by the name of Jessica will be the contact on their side. Bryan sent them an email with information requests. We setup a meeting for next week to touch base. They need some of it done by mid-July and then the remainder of the site done by September.

Added vendor credits to the pay reimbursement page. It has logic to allow normal re-payments, apply a vendor credit, and mix (both) payment types.

Meeting with Bryan and talking about searching parent attributes. He is working with a client who is taking parent attributes to the next level and needs some supporting options for running and filtering data accordingly. When I say taking it to a new level, imagine someone who has hundreds of possible options that they want to track. She, the client, does healthy snacks and wants to track all kinds of nutrition facts, allergy stuff, texture stuff, sugar content, carbs, and everything else that is needed for her business. Pretty deep. I only saw a minute of a video, but I could tell that she needs some better tools, for what she is trying to do. We chatted about some options.

Back working on the vendor credit project. Tightening up the logic on applying a vendor credit from some of the payables payment forms and sub forms. Made it so that the logic could switch between normal payments and vendor credits of a mixed payment. Mostly logic type stuff.

Recording notes from yesterday and this morning.

Added the mini question mark icon for the settings dialog box to the mini scan cart. Sent an email out to the others. This was requested by Steve and Cory in our earlier meeting today.

Meeting with Cory and Steve. Going over progress on the vendor credit project. Cory is trying to help and is managing expectations with the clients. That really helps. We flipped over to some needs on the shopping cart side. Steve is working on a number of new settings. He is working on some new ecommerce settings. After the meeting, I started looking into adding standard settings into the new shopping cart.

Working with Bryan and looking at ways to quickly verify expense/receipts. We already have bulk tools, but this was basically a shortcut for users who wanted to use the plaid API (external bank stuff). We want to add the receipts and mark them as verified (two steps for the price of one) at the same time. This could potentially save our users a few steps. This is just me, but I'm kinda torn... If we add this external bank help... it may speed things up for some of our clients. It also teaches the users bad habits. Instead of putting in the expenses as they happen (ideal), they wait and try to have the system put it all in for them (automated after the fact). They, our users, are back to batching things vs running on real-time values. You lose some details. Anyways a small bittersweet.

We merged in the code, and it will go live tomorrow morning.

Working with Russell. Talking about life and best to navigate things. We talked for quite a while about these topics. We then jumped into changing code and looking at our chart and graph project. Here are some of my notes - somewhat all over the place.

- We were looking at code and samples on the chart JS site.

- Building in training time. That really helps and keeps things sharp.

- Small changes moving forward. Those small changes can really add up over time. Like small drips in a bucket.

- You have to sacrifice something to make changes (talking about time and priorities).

- I enjoy enabling and helping others. We talked about boundaries and how to manage those. Sometimes, by not managing those things, I feel like I get taken advantage of. I'm not very good at setting some of those boundaries for myself.

- Questions - How do I run, what motivates me, how does that affect me?

- For me, I get worried about not doing certain things. Instead of fully removing things that I enjoy, maybe just opening it up a certain amount. Being able to adjust within certain parameters.

- You have to have sanity checks and find that maintainable pace. Otherwise, a pile of "goo" doesn't do very much (if you over do it, you can feel like goo or a puddle of something).

- Bloom and prosper where you are planted.

- You have to adjust within the bounds that are set to what you can. Fighting for that high ground and safety spot.

- Keep gathering up the drips and drops (From Russell - that's my life). It takes many strokes to make a masterpiece.

- We were talking about feeling like we are in prison, based on circumstances and such. Russell said - It is only your prison if you make it so. You have options and choices. I needed to hear that.

- Some other one-liner topics that we were talking about. Journey before destination (From the book "Way of Kings" - Brandon Sanderson), moment by moment (getting help from God - He is with us - both with me and by me), Doing unto others and helping along the way.

Meeting with Bryan. Looking over his progress on the Plaid API stuff (external banking API). We did a little bit of work with some of the dates. We like to see dates in a certain format and our code works well with that format. The Plaid API likes the dates passed to it to be in a totally different format. We flipped a few things around and got it pretty close. Bryan is going to go in and try to track things down a bit more and then we will re-meet to push up new changes.

After Bryan left, I did a little bit of clean-up, recording of notes, and paying bills.

Working on new code that allows a user to apply a known vendor credit on splits (payments on account).

Working on the vendor credit project. Did some review and then started working on cascading links and options to other pages. Working through a small tick list of to do items.

Emails and recording notes.

Meeting with Bryan to go over the planning for the upcoming golf tournament that we are going to be running through adilas for a construction company. We went over a bunch of known needs and did some planning and brainstorming. Bryan was taking notes. I was drawing and highlighting different parts and pieces of what we need to do and how we can get those things done. He took a bunch of notes and a few screenshots of our drawings. We also setup some more time next week to touch base and keep pushing the ball forward. Good work and planning session.

Meeting with Hamid. We finished up the intake form for his wife, in Spanish. See attached. This is for a skin care business. Next time we will work on some graphs and charts and get back into developer training stuff. This other project, the intake forms, was somewhat of a side project that we had to do.

Meeting with Bryan and looking at advanced expense/receipt queries and underlying results and values. He was doing some special query stuff to try to work on the Plaid API code (outside banking utility stuff). On his local box, he had an expense/receipt, but we couldn't get it to pull up through the new code. Because he was testing things, he had added in a new vendor and then deleted it. The old record was still tied to that vendor id number. The system couldn't pull that record because the table join was broken, due to him manually removing the vendor (practice stuff). It took us a few minutes to figure out why we couldn't get it to work. One of those days... :)

Working with Russell on custom JavaScript and CSS toggle switches. We are working on the graphical user interfaces for some of the homepages. We were working on getting the page to switch charts (currently using placeholders) when certain buttons are clicked.

Working with Shannon. Spent time working on describing the industry specific skin section of the adilas value add-on core model. See below for some of the content that we came up with.

Industry Specific Skins Level - White Labeling

The next, or second, layer above the core is what we call the industry specific skins. Imagine taking the generic adilas business tool, the adilas core, and then building software specifically for a business vertical. The new software package has exactly what they need, looks like what they want, and caters to their specific business practices or processes.

All of the other pieces are hidden and/or behind the scenes. With an industry specific skin, you can toggle on and off almost anything that you want. Change any of the verbiage, language, steps, and even the flow process. It becomes fully custom.

Every business has such diverse needs, wants, and even flow. For example: Say you were a car or trailer dealership. You would be dealing with stock/units (serialized inventory), floorplans, commissions, paperwork, etc. If you were simple retail, you would be dealing with barcodes, touchscreens, tons of different widget inventory, quick counter sales, and different payment options. A service industry may need scheduling, reoccurring billing, and a focus on customer care or support. You get the idea.

Building industry specific skins help us, as a company, cater to the exact needs of those business verticals. This also helps our clients feel like they have industry specific software that was built just for them. The true secret is the powerful underlying core. That's what allows all of this to really take place per business vertical and allow unlimited possibilities.

The white label option deals with a company wanting to brand and sell one or more of these custom industry specific skins. Each white label will, or could, have a completely different brand, feel, or flavor. For example: Say a specific skin for bowling pro shops, ice cream shops, pet grooming, quick retail, health and wellness, hobby shops, etc. Lots of potential! If you want to learn more about our plans for the white label options, see this page that has some adilas investment opportunities. The white label content is number 4 in the last section, ways to invest in adilas.

Meeting with Sean to go over touch discounts in the new mini scan cart. We jumped on a GoToMeeting session and were able to figure out his question. It ended up being some funky characters in the discount campaign value.

Recording some notes from earlier meetings.

Working with Shannon. Going over content for the transactional core. Showing that the current core is basically a fully integrated system with all of the pieces working together in harmony. See the content on the adilas value add-on core model page for details. Specifically, look for the section titled "Define The Current Core - Transactional Core Level" (the third accordion section).

On the GoToMeeting session with Steve. We were looking at the new mini scan cart and talking about how to get the gram controllers in there, inside the mini scan cart. We looked at some code and talked about options. He was also showing me some other changes that have been made and some new updates on projects, look and feel, and who is doing what.

Emails, recording notes, and paying bills.

Meeting with Bryan. We jumped into the data 11 server and were checking out some merchant processing options. We had to fix one of the merchant accounts and change some settings. We then briefly talked about another project that will be coming down the pipeline. We went ahead and setup some time on Friday to work on that other project.

Recording notes from 6/10/25 to 6/14/25.

Working with Bryan and going over a comic book ecommerce demo and what they are doing. Brian Mowris from FineTech has a few clients that are in the hobby store arena. They are looking for quick ecommerce, full POS, and all of the other fun stuff that adilas could bring to the table. These are smaller customer but there could be a lot of them. We watched a demo and I took a few notes. We then got Brian Mowris on the phone and chatted with him. We feel like we are 85% of the way there, out of the box. We talked about a few funding options and how best to proceed. Good stuff.

Meeting with Shannon and working on content for the adilas value add-on core model. This is somewhat of the master plan and where we are heading. Today we were working on content for defining the core. Here is some of what we came up with... we may still edit some things but it's a start.

New content... - part of the value add-on core

Before defining the current adilas core, we thought that it would be helpful to show what is common or somewhat industry standard as far as matching software to needs.

The current approach that most businesses use is to look around and try to find the best in class pieces of software. Then they try to marry those software pieces together to get a semi-workable system. This commonly ends up being a solution that includes anywhere from 4-10 (or more) different software packages to run their business. Imagine something like this: Best in class inventory tracking, best in class POS (point of sale), best in class ecommerce package, accounting, payroll, timecards, CRM (customer relationship management), project management, scheduling, etc. You get the idea... Does this sound familiar?

This ends up being what is called a "mashup", or mix, of different software packages all trying to be pulled into one workable solution. The pain comes in as each piece dead ends and doesn't fully fit with the other pieces. You end up in somewhat of a time sink as you have to duplicate data or search for data details in or from one software package to the other. Not to mention that you have different accounts, contracts, logins, and are paying for multiple pieces of software.

Inside of adilas, we are demonstrating that it is possible to do all of these critical business functions in a single integrated system. This is what we do at adilas. Imagine being able to do full inventory tracking, fully configurable POS functionality, CRM functionality, scheduling, accounting, payroll, ecommerce, full financials, reporting, exports, and having a virtual paperless office (CMS - content management system). This is just the surface of what is available with adilas, one system, all working together in an integrated solution.

Some of the benefits of having a fully integrated solution are things like: Having everything in one place and it all interconnects (no dead ends). Being able to search and find underlying details of amounts, sums, and counts. Not having to buy all of the other software packages. You are no longer limited to strictly linear processes. You are able to have a virtual three-dimensional (3D) system that allows you to enter data at any level and it will interconnect. Another huge advantage is that you get to use what features you want and don't have to use other features that you don't need. It's all there, if you need or want it.

To describe the adilas transactional core, what already exists, we will start with the word "transactional". This means - details or individual transactions. If you catch every penny in and every penny out, every invoice, every PO, item usage, expenses, deposits, etc., you start getting transactions and data history. This creates multi-relational data stored over time. All of these underlying details and histories become the transactional core. Everyone who uses adilas will need a transactional core. This is what people will purchase as the base model for how they run their business.

If you want more, here is a 50 slide pitch of what we do... have fun... we call this the presentation gallery.

Working with Bryan and going over new code to be able to switch locations out in ecommerce. He also introduced a quick mode that skips certain steps and limits how much editing of customer and profile type information. He is calling it quick shop mode. Light debugging and looking over new code. We made a few changes and then did some code branch management stuff to get everything all good to go. Fixed a merge conflict and got the new branch all merged into the master code branch.

Working with Russell on the graphical homepages. More work on custom CSS and setting up layers to help guide the users to what is most important. Working on leading the eye from one thing to the next in a hierarchy of visual elements. It sounds cool, but it takes some work and planning to really make it happen. He is more skilled than I am with that kind of stuff.

Meeting with FineTech folks. Bryan Dayton and I were on the meeting on the adilas side. We didn't really know what the subject of the meeting was. The FineTech folks had a number of questions about merchant processing, onboarding, custom quotes, and possible white label stuff.

We explained the integration of Clover devices, emphasizing the use of the Cloud Pay Display app for connectivity. We then discussed the technical aspects of merchant processing, device compatibility, and the need for API credentials. Jennifer inquired about onboarding processes, training, and the potential for customization. I provided contact information for key Adilas team members for support and training. The meeting concluded with a discussion on industry targeting and the importance of clear communication for updates and new features.

Back on the vendor credit project. Passing params to help create new vendor credits. Part manual but part automated (what the new credit is tied to - PO's, expense, and vendor id's). Working on the flow process and what is connected to what.

Phone call with Steve going over some sales strategies and ideas. He was on a meeting with a lady who knows Josh from California. She was proposing that we change our onboarding process. Instead of talking to a company and showing them a small demo, basically telling them that we will do a 3 month free trial and help them along the way. She recommended that we find businesses that have multiple locations (say 2-50 locations). We then jump in and show them vs trying to talk them into saying yes.

She was also telling Steve some basic numbers... For example: If you take our total overall revenue and divide it by the number of clients (regardless of what they have paid), you get a simple client value. So, for us, it came out to an average client value of $11,000. So, even if it takes us a couple of thousands of dollars to get the client, they end up being worth $11K ish (average).

She was also recommending that instead of building out a huge demo site and then trying to show the client, we spend that same amount of time helping the actual client do their stuff and run their business. If we do this, we spend the same amount of time and potentially cut the training time and help a client see what we can do, first hand. Interesting ideas.

Here is the quick summary - just for fun - free trial - figure $2k onboarding - worth $11k average - give it away - go after businesses with multiple locations - reallocation of funds - helping businesses succeed.

From Bryan - Check and push Healthy Bite code

Working with Bryan. Looking at session values and switching locations out in ecommerce land. He is calling it the quick shop settings. We spent some time and reworked a query to only pull items per location that have 1 or more in the total quantity per location. Should be some good stuff. He still needs to work on it a little bit, but making great progress.

Small fixes and checks after a meeting with Steve and Cory. Working on the pay PO page and the display for the payables homepage. Showing vendor credits with other totals at the top of the page.

Small internal tech support things with Cory - time card clean-up and helping with payroll and commissions. Talking with Steve about AI integrations and new settings and filters on the fulfillment pages.

Meeting with Steve and Cory. The whole meeting was a little bit over an hour. The first 45 mins were spent reviewing where we are at on partial PO and vendor credits project. I showed them some of the pages and code. We went through a few different scenarios and what not. I took a few notes on places that still need some loving. Making good progress. We should have this vendor credit portion done by the end of June.

Working on adding vendor credit links to the po line items page. Options for viewing existing credits and creating new ones. This is part of the manual creation process for vendor credits.

Working on using vendor payments as part of the payables and payment processes. Did some testing and worked on cascading more code to other pages.

Emails, paying bills, and recording notes.

More cascading of vendor credits and new code around the site. Spent some time on the payables homepage, who needs splits (payments on account), and who needs reimbursements. Those are different payables reports. After that, I started into adding code on the add/edit expense/receipt page. That is where you actually start using a vendor credit as a payment type. I didn't get all the way done but at least got it to the level of being able to run the first vendor credit through and having it auto deduct from the existing vendor credits stored in the special accounts. More testing yet to come.

Light clean-up at the end of the day. Added code to one other page that got missed earlier.

Recording notes and looking over a PowerPoint slide show that Suzi sent to me. We really need to spend some time, money, and efforts on marketing and creating simple visuals and screenshots of what we are doing and offering. People are interested in what we are doing but they need to see it to really help them figure things out.

HOA (homeowners association) demo with Suzi. It was just the two of us. We had a few other people pop in/out pretty quickly. Anyways, Suzi gave me the demo and we went through a bunch of things. Kinda a practice run of sorts. Suzi had everything prepped. She covered ecommerce, paying dues, requesting services, and getting to links and paperwork. We then jumped inside of adilas and looked at reoccurring billing, tracking expenses, PO's and inventory, payroll for any employees, financials, etc. We talked about scheduling and how to help these people track their different needs (rentals, home visits, work projects, etc.).

As we were talking, we wanted to make a note about adding in a public facing calendar. We have a great internal calendar. We just need to push it out as a mini version for our clients to use as a client facing calendar view. This would be some new development. We know that the need is there as it has been requested a few times.

Suzi and I then got into a small PowerPoint presentation that she had made. See attached. We jumped into the presentation gallery and clicked around. I showed her some cool new features and what not. We have been making some changes there. We need more pictures and ways to show off what we do (a good mix of visual eye candy and light education). We would love to make it so intuitive that people could virtually follow the picture story. People really seem to respond well to good pictures and screenshots. Good little meeting.

Working on showing and using vendor credits in the system. Started on the payables homepage. There are multiple views and report formats on that page. Also added in filters and drill-down options from the payables back to the vendor credit transactions. Slowly working through things.

Recording notes from today.

Working on automatic settings when dealing with special accounts and assigning certain key money types. This is a backend process to help with easier setup for corp special accounts. Once I got that finished, I started to work on special look-ups for vendor credits (new special account type). Went over to the payables homepage and started to code that page to handle vendor credit look-ups.

Quick phone call with Bryan to go over options for ecommerce, searching inventory, filtering data, and only showing certain results for different locations. The old code just looked at a single web location. The new code needs to flip locations and just show what is what for that store or location. We briefly talked about a couple of options and ways to apply those filters.

Recording notes. Meeting with Russell. We jumped back on the graphical invoice homepage and making some changes to the CSS and layouts. Our plan was to work on some graphs and such... It has turned into a huge custom CSS lesson and such. We'll still get to the graphs and charts, but we are learning along the way. It is helping me out.

Today we started working with small callout cards and values and adding buttons to show different chart options. The page is not linked up to real charts yet, just the prep and layout stuff.

Meeting with an investor group that helps provide investor leads and contacts. There were two people on the call with me. They were pitching their services to us. There was a nice lady by the name of Sita Chopra who answered a bunch of questions for me. I appreciate that. She was talking about different phases of investments and funding. Often companies will start at the seed stage and get funding there. Then they go to the series A and possibly series B type funding. Often they will use their seed funders to keep moving the ball along. There are certain numbers (annual revenue values) and time in business that determine if you are seed, series A, series B stage, etc.

Sita was saying that you don't want to skip the seed level funding. If you do, other investors may see that as a problem. We, at adilas, are kinda bootstrapping our project and have been for years. That is awesome, but sometimes it doesn't look super good to certain investors. It's kinda like not having a credit rating or credit score. They are looking for previous actions and experience. I thought that was interesting.

The other thing that Sita said was is that they really like to get a full pitch deck vs just a small teaser type document. The teasers are smaller but don't really satisfy the bigger investors. They want to see the whole pitch deck and want to do their research and homework. She mentioned that one of the things that they look at (their services) is how many times a certain pitch deck is opened and viewed and how long the investors sped looking at it. She said, if they are serious, they will open it up multiple times, review it, read it, and even study it. She said that many of the investors really like to read about their options and what to expect. Once again, I thought that was good information.

Working on the vendor credit special account functions. Started refining the vendor/payee search when checking corp level transactions for vendor credits. I then started working on a section to help auto select certain money types that are tied into the special accounts such as gift cards, loyalty points, and vendor credits. Left off part way through this section.

Recording expenses and paying credit card bills. Other general to do stuff.

Was going to be working on the vendor credit special account functions. Got a call from Bryan and he needed some help pushing up some code. Switched over to help him out. He is working on a new 3rd party API socket for the Plaid banking API stuff. Light testing and pushing up new code.

Meeting with Bryan. Looking over the availability to switch the store locations out in ecommerce land. Looking over his code and such. We merged in some new code. We then switched and were looking at a bug on the Plaid API code. Plaid is a bank account extension or a banking API socket option. Looking at error handling and try/catch type processing. Our session turned into a small work and testing session.

Meeting with Jeff Machlin from Wingman Growth Partners. Small meeting to just see what everybody is offering and doing. Pretty simple meeting. Just a get to know you type thing.

Paying bills and adding scans for documentation.

Meeting with Bryan and pushing the Plaid (bank stuff) code up for a new 3rd party solution and bank integration. There were a few merge conflicts in the adilas 3rd party solution pages. Fixed those and pushed up new code. Also looked at his current code for allowing multiple locations outside in ecommerce land. Small chat about other upcoming projects.

Emails and sending a guy a link to the adilas investment options and opportunities.

Working on the vendor credit special account section. This is a sub project of the receive partial PO line items project. Ended up doing some light research on balance sheet watchers and feeders (sub details of a balance sheet item). The ideal goal is to setup a balance sheet item, with custom groupings, mappings, and custom naming. Then we use that balance sheet number as a base where we can show additional details without having to go in and physically add all of those details. We can get the details (of the balance sheet) from other sources.

This is not the only way to use watchers and feeders, but it could be pretty cool. I was doing some research on how we wanted to treat the vendor credits inside of special accounts (overpayments for PO's and expenses or sales tax commissions for early pre-payment). Basically, vendor credits are any monies that are paid to a vendor and we either didn't get anything for it or we overpaid for something and need to reduce some other expense payment to that vendor by that amount.

Spent the rest of the afternoon refining the add manual vendor credit process. Pushed up code into a small side branch for vendor credits. Recorded notes on the partial PO project timecard.

Working on the receiving a partial po project. Started out with adding a new money type called "Vendor Credit" - just on the data 0 to start with. We will cascade it to all servers once other code is ready. Just getting new id numbers.

Working on new database scripts. Adding in a new PO type for the transition PO's. Then started working on the new code to help with vendor credits as a special account. We need this to be done before we can really turn on and fully develop the receiving partial po line items. Prep stuff.

Recording notes and checking email. Spent some time and made a fix for the PDF custom part labels. Sean had sent an email yesterday with a possible problem. It took a bit to find it, but we did some formatting of some prices and costs to get the decimals to show up correctly. This was different than our normal code. We have custom code that allows for up to 5 decimal places, based on settings. We call it the adilas dewy decimal for fun. This new fix was a raw database query that needed to be forced to a certain decimal format. Called Sean and had him test things. Pushed up new code.

General to do list stuff. Recording notes. Quick meeting with Bryan to go over allowing multiple locations to be used out in ecommerce. We jumped on the GoToMeeting session and looked around a bit. Made a small plan. I had to go pick up one of my daughters. We had to wrap it up before we were fully finished. Hopefully it was enough to get started.

Emails and some follow-up.

Went to the Adobe website and signed up to be a presenter in an upcoming conference.

Session Title: Using CF to mix and sell essential business solutions - client success story

Session Description: CF developers know that ColdFusion can do amazing things... would you like to see how CF made our reoccurring revenue SaaS solution possible? In this session, we will show you how we used CF to combine inventory tracking, a full POS (point of sale), CRM (customer relationship management), eCommerce, scheduling, backend accounting, into a full-on ERP solution (enterprise resource planning)? The entire backend is built on Adobe ColdFusion with a MySQL database. Small demo of the product and what it does, open discussion, and plenty of time to ask questions. If you want to see a process, from start to finish, no problem. If you want to dive into code and look under the hood, no problem. Developer and project manager, Brandon Moore, will help you see the power of CF in a real-life client success story.

https://news.adilas.biz/sales-gallery/adilas-advert-index.html - Some slides on what we do at adilas.biz

Recording notes from 5/27/25 to 5/28/25.

Phone call with Bryan to go over some ecommerce questions. He has a client that wants to use multiple locations out in ecommerce land. Normally, we use a setting and then just use that single location/store out in ecommerce land. We talked about what would need to be done to make it all work and how long that may take. We will dig into this tomorrow over a GoToMeeting session.

Working with Russell on the graphical homepages project. Only got about half an hour today. We ran late on an earlier meeting and then I got pulled off because my wife needed me to pick up our daughter. Short meeting today. Working on layout stuff. I got a couple of screenshot graphics from Russell to help with the project. See attached.

Steve and I going over highlights and thoughts from our meeting. Phone call going over plans, vision, and other things that are circling around. We are really trying to educate people that we are working with. It will help them out in the long run.

There were 12 people on the call. 4 from adilas (Steve, Sean, Josh, and I). The rest were from Yogen Fruz. We started out and Sean was giving a demo to their team. He started with clock in/outs. Then he showed some simple carts, checkout options, gift cards and loyalty points, and discounts. Simple POS stuff.

He was able to switch from the demo site out to the live site to show some real values. They, the Yogen Fruz team, got into some questions about the backend and cost of goods. It got into accounting pretty quickly vs just POS stuff. Steve took over and showed some new AI (grok) stuff that he is working on. I took a bunch of other notes. Here they are, no special order:

- They are wanting an offline solution. Adilas is a full web-based solution currently.

- There was a super diverse group, lots of questions from their different sides. Operations, POS, hardware, accounting, managing, etc.

- Steve was talking about adilas and how it is setup as a paperless office. Tons of options to add photos, scans, images, and other media/content or files for documentation. Currently, the YF team is very heavy into tons of spreadsheets and such.

- Talking about backend accounting options. Light show and tell session.

- Ivan - new guy - seemed pretty technical. He has some great questions and tried to keep the meeting on task. It was going all over the place.

- One thing that Steve and Josh were saying was, they could use their phones or any other web connected device, if the Internet went down. They were even talking, say a physical unit goes down (physical failure). They could even use any device until we (they) get them new hardware - different backup options.

- Lots of talk about API socket connections and connecting with delivery options and other possible vendors and 3rd parties. Mixing and blending pieces.

- AI talk... where we are heading - sanitation of data - security and transfer of data.

- Steve was pitching enterprise level mapping for customers and items.

- Aaron (main boss) was saying... we are planning to release these features in stages. Some of the questions were directed to POS, ecommerce, scheduling, payroll, financials, etc. Aaron seems to be catching the vision. I don't know all of the stages, but imagine something like: Stage 1, POS and inventory tracking, stage 2, ecommerce and menu boards, Stage 3, backend accounting, etc.

- Lots of talk about hardware stuff, including menu boards, printers, and POS stuff.

- They wanted someone to fix the Windows settings for multiple displays (2-sided POS station - cashier and customer side). They can do it right now, but they want it to be automated. That is a Windows thing but we will get someone on that.

- Towards the end, there was some talking about pricing and what is included - setup, monthly, ecommerce, support, changes, etc.

- This is just for me... It really seems like they want the moon, but they are trying to talk us down on everything (cost wise). Most of our other clients, we offer something, and they say yes or no. They do a lot on their own and we either train them or setup a plan to get them the help that they need. This one seems like there will be some direct handholding along the way. We just have to make sure that expectations are set before we (or they) commit to something. I have already seen some feature creep for this project (the scope keeps changing). I really hope that we nail down the stages or phases and then stick to that. It could get crazy if that is not followed.

- Good overall meeting. We left it in their court. Steve and Josh will do some follow-up.

Benning golf tournament plan. Meeting with Bryan. Going over deliverables for the golf tournament. He had a document prepped with an outline. We then went through the outline and filled in either questions, assumptions, and/or plans. It went pretty smoothly, as far as a brainstorming process. Bryan has all of the notes.

Phone call with Steve. Touching base on different needs and things that are going on. People are looking for solutions. Talking about some of our new and old connections and contacts. Going over some marketing ideas and who will help us with those marketing efforts. Good catch-up phone call.

Meeting with Steve and Cory. We stared out by doing a recap of our plan and going over a number of scenarios. I got some questions answered. They want us to hyperfocus on the MVP and go from there. Anything extra, needs to sit on the side. We may end up circling back around. We talked about voids and limiting those options (making things go away after other transactions or sub cause and effect processes have taken place). Some of those interconnected processes can get super crazy if too many things start interconnecting and then you void something. We spent some time and went over vendor credits (new project) and how all of that will work out and play through. We had some great conversations, and I got a bunch of questions answered. I'm ready to start building.

Tech support to help Michael with some backend queries. Ran a couple of queries and sent the results to the 3rd party developer for review. Multiple emails and back and forth.

Emails and checking on the help file for the adilas API socket. Lots of old and outdated information. I need to get it updated. Checking out links, videos, and trying to figure things out. Ended up doing some research and trying to find some older files that were missing.

Switched over to some research on web availability and layering for elements of time. I've got some projects coming up that will need those pieces. Also looking into some time based my cart favorite buttons. That would be really cool for selling time or time slots, combining POS and scheduling functionality.

Getting lost in some of the dreams of where we can take this. I love the dreaming part of this... sometimes when it takes 5+ years to circle back around... you almost forget the dreams. It is fun to circle back around some times to remember. :)

Emails and light tech support. Emailing a developer about a couple of inventory method out in API land. Trying to point him in a good direction. Recording notes from yesterday and today.

More planning and looking into how the vendor credits will play out. Writing out a few other scenarios. Scanned and put together a 17-page document to  help show brainstorming notes, ideas, refinements, scenarios, database changes, and plans for some of the mini projects that could be associated with this bigger project. I uploaded the document inside of adilas on project # 2794.

Researching on ways to make new expense/receipts and apply payments for specific vendors. Part of the vendor credit stuff (new special account section).

Back working on the plan for receiving of a partial PO. Working on the payment portion and how that ties into the financials. Started planning out vendor credits (new special accounts option) and how that will play into the mix. Lots of planning on paper. I will scan all of the pages in when I finish up the planning part of the project.

On a Zoom call (demo) with Bryan and Suzi and HollyJo from Richmond city (Utah). Suzi was doing the demo. She had some open tabs to help speed up the demo. She started in on payroll options. She was showing user profiles, templates, permissions, and such. Talking about clocking in/out and how to do that on their phones, using a small mini app. Next, she jumped into different reports and how to navigate around. After that, she switched over to showing some scheduling for parks, practice fields, pavilions, and library reading times. HollyJo has a number of needs for project time tracking. We went over a few options there. Quick but a good demo.

Working on the receiving of a partial PO project. Planning and going through scenarios and mocking up fake data to see what it would look like. Making tons of progress. Good work session.

Emails and recording notes. Had to go in and do some samples API calls to answer one of the emails. It was dealing with finding quantities for sub inventory. Ran API sockets on both data 20 and data 0 to find the answers. Send an email with my findings and recommendations.

Working with Russell. Refining CSS on the graphical invoice homepage. We finished up the main search and compare buttons and the top form. It is now responsive clear down to 450 pixels. We added a number of breakpoints and media queries to help it change and modify itself as we scale down the screen size. Fun session.

Talking about life and business... how they compare and what you learn from different places. We had some fun conversations. I was also asking Russell about some business decisions and where to go with things. We got talking about bidding and doing quotes/estimates for custom jobs. Here are a few of my notes:

- If you know (what something will take to do), you can set an estimate (at least ballpark it).

- If both of you (you and the client) don't know (how much it will take), set a small budget and then jump in and see what you see. Setup an exploratory cushion of sorts.

- Be willing to communicate back with them, especially if it (the project) starts growing or you see that it will be bigger than you thought or had communicated.

- Weighing dreams and focusing on what really counts.

- Who and what do you want to be? Work on that stuff.

- Russell was talking about God, heaven, and helping people along the way.

Recording notes from yesterday and today.

Meeting with the SymLiv guys. They wanted to see what kind of options were available and how best to proceed. We talked about CSS and style guides, API sockets, custom wire-ups, etc. We got pretty techy and were going through code, flow, options, and how things may or may not work.

Prep work for meeting with the SymLiv folks. Prepping for a white label. Started to play with a new theme and how that might roll out. I got into it a little bit, but would need to keep pushing to see what else might happen. Lots of moving pieces. Made a new code branch on my local box.

Work session with Shannon. We spent the entire time working on new content for describing the value add-on core model and what that really means. We really tied to explain that each business, that uses adilas, needs a transactional core. That is where you start. That core is where they capture and record all of the daily transactions and subsequent accounting pieces. We then offer upgrades or value add-on's, to that core, as additional layers or levels that help the core product of what we offer.

Stepped away from my desk to do some planning for the project to partially receive PO line items. Did some reading, research, and planning on paper. That really helps me to step away from the computer. Otherwise, I figure something out and immediately want to go fix that part or piece. Sometimes you need to get the whole plan figured out, on paper, before you start coding. I have also identified a number of smaller pieces or independent mini projects that are part of the whole.

Partway through the planning session, I needed a break. I did a quick fix on the my cart favorite buttons to help add a link to the multi assignments per button to allow for sharing and stacking of buttons. I added the new link, in edit mode, to the add/edit my cart favorite button page. It was already available from the bulk sort my cart favorites page. It was pretty fast.

Phone call with Chuck to go over a standalone style guide and CSS template. We would like to help out the guys that are going to be creating a white label option, based off of the adilas styles. We talked about some other projects and did some catch-up. He will be code reviewing some of Piper's work (another adilas designer) and then on to the standalone style guide. After the phone call with Chuck, I paid myself and recorded extra time (overflow) values in the shop from last week.

Emails, reading a mutual NDA document, signing it, and other emails. Recording notes from yesterday. Paying bills.

Just for fun, we had a person ask us for a list of files (like a directory list) who is wanting to work with us on a white label buildout. Just to be funny, I sent him one of the folders (a scrolling screenshot)... It was a 5 MB file and had over 1,400+ file names, just in one directory. I was just being silly. I told him that I would help him out vs making him go through all of those files.

Phone call with Steve going over plans and small recap of our previous meeting. We also talked about some other projects and how best to proceed. Something is always going on... never a dull moment.

Meeting with the SymLiv folks (Taylor and John). This was the first time that Steve had met these guys. Light intros. They have lots of asks from their clients... can you connect to x, y, z, etc.? They are looking for resort level communities and helping to control access and flow in those resort level communities. We talked about doing a full white label option or options. This was kinda fun, but they were talking about white labels of white labels (multi layering of white label products). We were talking about pricing, wholesale options, and how to proceed. Kind of an intro meeting of sorts for Steve and John.

Working with Sean on buttons and new items for Yogen Fruz. They wanted a new Greek froyo line pushed up for tomorrow. It sounds super easy... 4 sizes, small, regular, large, and pint. Ok, they also have 10 flavors per size. We tag teamed and did items, photos, and buttons for them. doing multi-assignments for the buttons. Mini work session.

Emails and light research.

Work session with Shannon. We were finishing up some content and verbiage for the adilas jellyfish model page (company structure). We were mostly working on the payment and compensation section. Good session and some good conversations. Somewhat off topic, but we also talked about saying yes, saying no, setting boundaries, abusive and positive relationships, and how certain things - if taken too far - actually hurt others around you, unintentionally.

Anyways, I had done some prep work on this section. I had a printed page and half worth of content, and we got it paired down to less than a half a page. Shannon really helps me talk through things and helps keep the content on track and concise.

Emails and recording notes. Clean-up from the day and random to do list items.

Meeting with Taylor James, John Spuhler, and Tim Greenfield from SymLiv. They deal with different gated communities. They were looking at adilas to help them take care of the other internal processes within those gated communities. Things like simple cabin rentals, small retail shops, booking venues, owners or guests putting things on a tab and paying later, other simple ecommerce, POS (point of sale stuff), CRM (customer relationship management stuff), and scheduling options. Good little demo. They wanted to connect with Steve to get some other info and some pricing. I was somewhat pitching them the white label idea and option.

After the meeting, I called and chatted with Steve for 10 or so minutes to give him a recap. I sent the guys his contact info. He will watch for the email and we'll go from there. He was also reporting on other things that are going on with different clients and projects.

Working with Russell. More work with media queries and custom CSS stuff. Lots of testing for responsive web stuff on these new graphical homepages. Just an observation, but there is a lot of trial and error. Fix one thing, check it out. Go fix another thing, then check it out. The one thing you just fixed causes something else to break. This is all custom display stuff. Definitely a learning curve on the custom CSS stuff.

Looking over plans for receiving inventory on the partial po project. More planning on paper. I have to figure it out there first. Started to plan out some new database tables. Still working through ideas and plans. On transition invoices, we went with an acronym of "QTI" which was for quote, transition, invoice. On the transition PO's, we are thinking of going with an acronym of "RTL" which will be for request, transition, live (all states of the PO line items). Anyways, making progress. I'll scan in my notes later on, they are kinda rough right now.

Small fix on some verbiage and content for the adilas jellyfish model (company structure). Ended up rewriting the whole section (payment and compensation section). The ideal is to focus on the people and the teams vs new features for our products and services. I tried to explain the current mode of how we operate and then spin somewhat of a plan for where we are heading and how we will get there. Little by little.

Working with Shannon. We got in and started working on the content for the adilas jellyfish model (company structure). Our goal was to work on the payment and compensation section. We kept getting pulled off into side tangents. Not fully related, but somewhat related to the topic at hand. We ended up talking about a shift from focusing on the next projects (tick list or features) to more of a person and talent type approach. We have been somewhat focused on following the money or following the dollar.

This shift, from features to people, I would love to see that play out. The current focus has always been on the next project or feature. It seems like it was always something like this... if we could just get such and such done, then we could work on this or that, or our customers wouldn't ask for anything else. Sadly, that is not true. The requests and demands just keep going. We have hundreds and thousands of features... We really need a bomber team!

Working on the changes for the mini scan cart and not creating new objects each time we asked or stored data for the shopping cart. Ended up giving Alan a call and he walked me through it (how to make some changes). Spent time cascading code around to help make it happen (creating less objects).

Meeting with Matt Veil from HuskiCRM. We were going to do some back and forth demos. They are doing a white label of GoHighLevel - CRM stuff - call tracking and call recording. Lots of dashboards. Automations and emails and texts. Trying to make all marketing funnel into one location and/or source. We talked about outside parties and integrations.

I then did a demo and showed Matt a ton of things that adilas does. We went over tons of options. I thought it was fun. He seemed to be impressed with how many things we could do. Towards the end, we were talking about marketing ideas and options that we could do. Possible automations, asking for reviews, and setting up some automated emails and/or text messages. Just ideas at this point.

Emails and paying bills. Working on some new changes for the shopping cart and how we call data. Trying to make that process lighter. Going through other pages and cascading new code changes.

Meeting with Wayne. Looking over server memory issues and how the shopping cart was pulling things. We were looking and didn't find anything immediately. We decided that we will rewrite some of the ways that we call for data and see if that helps. I will make the changes and push them up live so that tomorrow morning it should be better. This is plan A, if that helps the memory issues, great. If not, we'll circle back around and see if we can figure something else out. Lots of moving pieces.

Emails and recording notes from 5/8/25 to 5/10/25.

Meeting with Steve and Adilene. We were talking and showing her around adilas. Steve and I were batting things around and feeding off of one another. It was fun. We were bouncing around from server to server, client to client, and showing her all kinds of stuff. Fun little session. We got into some theory, some logic and flow, and even showed her some code. We were chatting and talking for a couple of hours. All kinds of subjects and topics.

Meeting with Hamid. We were working on the Spanish intake forms. Got the second page done for his wife and her skin care business.

Went into town to meet with Matt and Andrew from HostHuski and HuskiCRM. Fielding questions and pitching some vision. They both had some great questions. Good conversation with Andrew about doing custom code and somewhat chasing our tail (focusing on other people's work and projects vs our own).

Jumped in on the partial PO project. Stepped away from the computer and read over the brainstorming document that Steve and I had made. Working on refining the plan. Started to work on the plan with paper and pen first, then I'll go to a digital format.

Recording notes from yesterday. Meeting with Shannon to go over text, verbiage, and content on the adilas master plan stuff. Working on talent and personality types. As we are writing these sections, we are trying to shoot for the ideal, show what is current, and then show where we are heading for our future plans.

Emails and sending out some small video links and an investor packet to Jennifer at Harris.

Meeting with Cory. Quick fix. We had to alter the default expense types for an employee. They had set it to a value that didn't exist and were getting a small error. We made the fix, and they were good to go (simple user error).

Working with Russell. We were tweaking out the CSS and JavaScript for the graphical homepages. Lots of work on CSS media queries for responsive pages and modifying the dynamic CSS as the screen size changes.

Recording notes and paying a credit card bill. Spent a bunch of time adding content to the adilas cafe page inside the adilas lite plan.

Rereading an internal questionnaire on what the adilas team thought was important heading forward (precursor of the adilas business plan). 15-page document. I enjoyed reading over it. Lots of the pieces are still in play and it's kinda fun to see how things are playing out. See attached for a copy of the document.

Here are some of the questions:
1. How big do we want to get?
2. What is our time frame to get there?
3. What do we want to do/have for our company/user culture?
4. What are some of the things you like about what we are doing right now?
5. What are some things you would want us to change?
6. As far as structure, what do you like? Do you like the independent model or would you like it more solid?
7. Do you like the jellyfish model? (Organized with a loose, flowing feeling. Adilas is the overarching umbrella and there are a number of sub departments or subsets.)
8. Would you want to see something different (company structure)?
9. What products and services do you think we should focus on?
10. Do we want to continue to internally fund this or seek outside investments?
11. What do we need on the management side? What do we need in leaders and managers? Traditional managers? Or more of a Board of Trustees or Advisors?
12. Do we want some sort of internal loyalty system or revenue sharing plan?
13. How do you play? What is your time commitment, scheduling, maxes and mins (hours per week/month)?
14. What business verticals are you interested in?
15. Where would you like to focus?
16. What are your thoughts on look and feel for the application interface?
17. Let's talk pricing. What are your thoughts?
18. What about marketing and sales?
19. What about code, databases, automation, testing, deployment, and other techy stuff? Back-ups, redundancy, mirrors, servers, clusters, etc.
20. What are your thoughts on education, training, and add-on services?
21. What about custom and API sockets and integrating with other external products?
22. If we do a trust, what are the other rules or parameters we want to set up? Is it just time, is it time and money, is it investment, what is necessary if you want to buy in? How do we determine who is active and not active? How many virtual family members do we want? Etc.
23. Where do you see us (as a company) in 1 year, 5 years, 10 years?
24. Where do you want to be in 1 year, 5 years, 10 years?
25. Other ideas and thoughts?

Super fun read and some great comments. Sometimes it takes us a while, in the adilas world, but we keep pushing forward. It is exciting to see how many of things are starting to play out and/or are still in our upcoming goals and direction. I really enjoyed re-reading this internal survey summary. Good stuff!

Paying bills and checking emails. Working on the text and verbiage for the investment options for adilas. Grabbed all of the text that we had finished and made it into a PDF document for easy passing around. See attached for the new PDF. The same text is also available online at: https://data0.adilas.biz/lite/adilas_investment_opportunities.cfm

Working with Shannon on refining content for the adilas jellyfish model - pages within the adilas lite (fracture) plan. We didn't quite finish everything up but making good progress. Here is the link to that page - https://data0.adilas.biz/lite/jellyfish_model.cfm

Started reading over brainstorming notes from last Friday. Steve joined the meeting, and we were talking about AI and doing AI data analysis. He was showing me some of his new AI stuff that he is playing with. Very interesting. Going over prompts (what AI needs to do its stuff) and even asking it what a better prompt would be. The key in in the prompts... Steve was asking it (Grok), how to do better prompts and what it is looking for. Great ideas. We spent some time looking around and then talking about where and how to use it, meaning AI options.

Emails and looking at a siteplan for a new website for adilas. See attached. A couple different phone calls with Bryan to go over plans for the golf tournament folks. They got back with the Finetech (3rd party solution that we work with) folks and want to move forward. We gave them a demo a couple of weeks ago. Going over needs and making some small plans. More emails and recording notes.

Working with Steve on receiving the partial PO's project. We spent some time going over the project, talking about scenarios, and looking at different parts of the system. We did some drawings and some brainstorming on ideas. We may also see a need for forecasting and predictive AI type level stuff playing into the mix. See attached for our notes.

Numerous sessions throughout the day. Four hours in the morning and then the rest afternoon.

Adding content to the adilas lite plans and pages (fracture stuff). Filling in some of the gaps. Working on the pages for the value add-on core and the adilas university projects. I would open up Microsoft Word, get to the correct spot in the outline, brainstorm for a minute or two, then use the dictate tool and record my thoughts. I would then go back through the text and modify it so that it becomes more legible and readable. Kinda fun. Also worked on content for the adilas marketplace and defining some of the sub topics and sections.

Working on filling out content for the adilas lite or "fracture" stuff on the existing adilas lite pages. The pages have been live for almost two years. Just trying to fill in the gaps and add some content. We will go back and edit it later, just trying to fill in some holes.

Phone call with Steve. Going over new AI generated web content, updates on possible investors, and talking about projects and budgets. We also briefly talked about other developers, current and upcoming projects, and future plans. Small catch-up and update session.

Working with Shannon. We did a bunch of editing and read through the investment page for adilas. Trying to make it a final edit so that we can move on. Here is the link to the page. Most of the edits were on the bottom section, dealing with ways to invest in adilas. Towards the end of our time, we were planning on what we will tackle next.

Working with Russell. Working on custom CSS and precise placement for form controls, including some media queries, and responsive design. Small work session on a new graphic homepage for invoices.

Three different sessions throughout the day paying bills, emails, and recording notes from 4/28/25 to 4/30/25.

Working with Bryan on merchant processing stuff. Going over settings for Clover and CardPointe and which auth keys go where, in the setup and settings pages. This is the trick, who holds the knowledge... that is hard to track down (meaning which developer built it and what do they know). Making sure that things get put into help files and passed along.

Working with Cory. She had a list of things to go over and check on. Small data clean-up for a client. Checking on a few removed line items (from a PO) and their subs. Looking things up in the database.

Spent the whole last part of the meeting talking about mental challenges (mine) and how to overcome those things. Topics included burnout, more and more projects, unknown finish lines, demands, payments, etc. Small venting and meltdown session. Sorry Cory! :)

Working with Shannon on verbiage for the adilas investment options page. We were working on the last few options. Just an observation, it is so interesting to see how the process goes for smoothing things out (making good content). You almost have to rough cut it, refine, refine, maybe even give it some time, and then circle back around again. It is fun to be part of the process. Good work session today.

Went into town to meet with Andrew from Host Huski (web hosting and website builders and web consultants). We met and talked about websites, common ground buildouts between both of our parties, and options going forward. Here are some of my notes:

- He would like to make a Huski Point of Sale or HuskiPOS white label, using the adilas engine. That would be really fun.

- He made a huge spreadsheet of the different features that adilas has. They came from the presentation gallery pages. He gave me the homework assignment of pairing things down and getting rid of things. There are almost 800 lines (features and points). Along those same lines, he would like me to really spend the time and make it easy for a client or user to both understand and basically see what they get at a glance.

- Along with pairing down the list of features. We want to categorize things into plans and packages. Ranging from free to full enterprise or custom.

- We talked about doing a full website redesign for the main adilas.biz website. We would base this off of the features list that we are going to be creating.

- For me, I like to say we have 12 main functions and 12 main player groups. Maybe get rid of the numbers and say something like: Our essential business functions and key components (parts and pieces... aka the 12 main player groups).

- Andrew asked me about "roll call" and what that meant. As we talked about it, we thought that "lifecycle tracking" may be a better fit.

- ACL (access control list) - and having permissions better organized and even sub divided into better or real groupings. Light conversations about where we could go with that. We already have that, but it could use a little bit of loving.

- Letting clients do their own data imports and importing data. Maybe even doing some automated combing and virtual pre-flight checks on the data (does it pass, without trying to do it).

- Good discussion on moving things around. What is the most important to our clients and potential clients? Put that first, other stuff, either get rid of it, move it to another area, or keep it as is. Helping with organization and flow. The easier things are to do and follow, the less need for tech support, training, and handholding. They can then do it themselves to a certain level.

- Good faith - work on both parts (Andrew and Host Huski and Brandon and adilas).

- Lots of focus on getting organized.

- Easy onboarding

- Going over design principles and the power of 3 (design stuff).

- Andrew is trying to work with SEO guys, marketing, CRM, hosting, payment solutions, and POS guys. He wants to create a super team to help do all of the pieces.

https://data0.adilas.biz/top_secret/secure/invoice_sales_search.cfm

https://data0.adilas.biz/top_secret/custom/sales_reports_home.cfm

Paying bills and checking emails.

Meeting with my sister Kim and her friend. They would like to use adilas to do some simple ecommerce and show off some of my sister's products - handcrafted items and crafts. We did a small session and talked about what is needed and how we could help her out. Her friend will help her with some marketing and social media stuff. We just need to be the web site and backend shopping cart (ecommerce stuff) to help with products, contact us, about us, and photos for some of her items.

Working with Hamid to help his wife with Spanish skin care intake forms. We finished the English version last week. Now we are doing a Spanish version. See attached.

Working with Shannon this morning. We spent the whole time talking about white label options and the five main adilas business entities (main adilas.biz llc, adilas shop, adilas university, adilas marketplace, and the adilas cafe). We were working on new verbiage and content for the investment options page for adilas. Lots of talk about byproducts and how to help service those needs and wants. We also talked about ways of catering to our needs (as humans) and how certain things really make us shine and come alive while other things can drain us and have an emotional cost to them.

We briefly talked about the working genius - a company that helps you know where your working geniuses, working competencies, and working frustrations lie - (WorkingGenius.com). We talked about how things look and behave and how we deal with those things. Talking about pressures, length of time, and demands on our time and energy.

Meeting with Russell. Circling back around on some graphical homepages and working on some graphs and charts. Working on some JavaScript and small tweaks. Playing with CSS, toggles switches, and media queries to help with responsive layouts.

After the meeting, recorded some notes in both the shop and inside of adilas.

Emails and recording notes from yesterday and today (4/21/25 to 4/22/25).

Prep work and then recording a video for touch and discount options for the main shopping cart. I had to re-record the video a few times. I pushed it up online and then sent out an email to some of the folks involved. See attached for the video link. It's about 7 minutes long.

Had to postpone the demo. She got pulled into another city project/meeting. Bryan let Suzi and I know about the change in plans before the demo.

Great session working with Shannon. We spent the whole time working on verbiage and content for the white label options for investors and what that might look like. As part of our meeting, we came up with this nice statement that involves our business functions and what we call our application players. Here is the statement:

"Adilas has the essential business functions and needed pieces to create any digital software system. Your white label mix will become a fully viable and marketable solution. We can help you mix and blend any of these pieces, based on your needs, designs, and input. Let's dream it up and make it!"

Quick meeting with Cory. Touching base on projects and such. We did some backend checking of settings and what pieces control what outcomes. We then did some database look-ups to see if we could see anything in the client's data. They are using adilas to hold and control the data and then using an outside 3rd party to show and display that data (API stuff).

Emails and paying bills. Meeting with Bryan to go over some questions that he has for the Richmond city demo. We talked about a public facing calendar page for our clients. We have a great internal calendar, but nothing that is visible to the public. We have some clients that could use the public calendar feature. We may need to look into that as a tool and/or feature.

Prep work for a small video to show off the new touch discount options. Created an outline and ran through a couple of practice runs.

Tech support. Running API socket connections and raw database queries to check numbers and values for a client.

Working on cascading a new setting for the mini scan cart to all servers. The new setting is for the touch discount popup. Pushed up a new file and ran it on all servers to globally update the settings. Next, I will be working on a small video to show the new settings in action.

Meeting with Steve. Looking into ecommerce changes and settings. We pulled up a branch that Chuck was working on. We made a few tweaks and wired things up. We got it all up and live and did some testing. After the meeting, I made a few more small tweaks. I also sent an email out to Wayne to ask about caching issues (web file being cached and not updated) and how to help overcome some of those things.

Emails and recording notes. There was one longer email that will require some tech support. It's for a guy who is building out an API connection for multiple corporations using our data (client data) to pass to an approved 3rd party solution. They have to sign-up for the other 3rd party solution, but this guy is building the code to bridge the gap and make things quicker. He is going to need some light handholding to make all of this work.

Meeting with Hamid. We finished up the 6-page intake form for his wife and her skin care business. See attached for the form that we are/were working on.

Online demo - with Finetech business solutions (merchant processing) - they wanted a demo for one of their clients that were looking to do a golf tournament and maybe use adilas to help them get reservations, sign-ups, and such for the golf tournament. Lots of talk about ecommerce type stuff, customer info, event info, and custom data tracking. I was giving the demo and showing a bunch of stuff. It went about 45 minutes. Lots of good back and forth questions and answers.

Phone call with Bryan Dayton afterwards to do a small recap and review.