Steve and I touching base on different things happening over the weekend. Steve and Sean then jumped into some labels, custom invoices, and gram tracking options. Steve is really trying hard to build out more settings to help automate different pieces and processes.

John was showing us some of his work and progress on the discount engine. He gave us a small demo and showed us what is still remaining, things that still need some work.

The conversation switched over to getting things pushed up and out for testing and live usage. We are really trying to focus on doing lots of tiny or micro releases vs big huge releases. Along with this topic, we started talking about possible projects and helping out Wayne with some of his bigger projects. If anyone gets too big of a project, they tend to virtually stall out and lose some productivity. We talked about the datasource project (world building), flex attributes for other system player groups (in-line database extensions), and client facing scheduling stuff.

Prep work and planning for a team meeting. Working on a small agenda and opening and prepping files.

Great team meeting. We had 12 of our team on the meeting. We did record it and Brandon has a copy of the recording. The whole meeting was dealing with the adilas.biz company restructure. We are moving from independent sub-contractors to partial owners within adilas. Cool stuff. The meeting went the whole 2 hours. I (Brandon) was mostly presenting and going over a small agenda. Lots of drawings and trying to pitch the pitch. We also had great participation from others on the meeting. I have attached the notes and the agenda from the meeting. Most of the first part of the meeting was talking about items on the Word document. See attached.

Uploading and converting the video recording from the earlier meeting. Sending out emails to the team members.

Small sales meeting this morning. We started out and Maris was showing us a new ad for a magazine that she is working on. Chuck and I talked with here a little bit about print specific stuff. Basically, print and web are treated differently, from color options to dpi or lpi (dots per inch or lines per inch). Print is, and/or can be, much more technical. You have to be careful.

Marisa and Sean were asking about the High Valley Bike Shuttle and progress there. I requested that Marisa help me reach out and get them all trained up and going. The conversation ended up with a marketing twist and what else we need to do and to help push these things along.

Esperanza (Hope) joined and wanted to do more person-to-person events and network marketing. She was pitching ideas and Steve and Sean were fielding questions back and forth. She seems to have a lot of energy and wants to get out and about more. It seems like she wants to be a promoter type person and help with events, meetings, and social type interactions and marketing. She, Steve, and Sean will get together and talk about ideas, budgets, and expectations. The goal is to get more demos.

Wayne, Cory, and Shari O. were going over server questions. One of the big topics was the clean-up of the data 0 database and servers. We talked about lists and ways to get a standard list of what is good and what needs to go. Wayne also reported in on his settings project. We told him that we would like Bryan to work with him on getting things tested and getting things finished. Wayne was excited to get another set of eyes on the code and help push the project forward.

Cory was asking Wayne about some background syncing between the adilas servers and Metrc (state of Colorado cannabis tracking system). We wanted to make sure that certain background clean-up processes were in place and working as expected.

Towards the end of the meeting, Cory and I were speaking with John. He had some questions from our meeting yesterday and we were talking about buy in and owner and percentages stuff. Sometimes communication and expectations are the hardest things to get figured out. We'll keep pushing things forward and figure it out, maybe even on the fly.

As a side note, we are all trying to do good. If someone isn't happy with what we are doing, it can deflate us. It's like a kick in the side. It hurts when someone doubts you or questions your capabilities or priorities. Just speaking in general. I for one, feel pretty fragile sometimes. Other times, I can take some pressure and heat. It all depends.

Jumped on a GoToMeeting with Chuck. We reviewed his progress on a mini calendar app inside of adilas. He is still working on some of the pieces, but we will most likely push up what he has and then go from there.

After Chuck left, I tried to spend some time and update the developer's notebook from the past couple of days. When things are happening, it is super hard to perfectly keep up with things. Especially if you flip flop from meeting to meeting or task to task without anything in between. I have found that a quick post-it note goes miles. I can scribble down a thought, and then go back and fill in the details later on. If I don't do the initial scribble, while it happens, I lose it. The information and happenings are still there, I just can't recall what the different topics were. I'm a big advocate for writing things down.

Meeting with our CPA, Bob Hamby. We had 12 people on the meeting with us. Bob was speaking and answering questions, Stee was helping run the meeting, and I was recording notes and chiming in. After the meeting, we did have a small internal Q and A session, with those who were still on. Great participation. We did record the whole things as well. Brandon has a copy of this if needed. See attached for the notes.

Small admin meeting with just Brandon, Steve, Cory, and Shair O. - going over the meeting we had with Bob and the rest of the team. Our next major step is getting things in place and doing some prep work before we take it to an attorney to get all of the verbage and wording correctly. Lots of good stuff and future options. Tons of potential and exciting things ahead. Just for fun - Steve said, "I feel like I'm on a big plateau, looking around, and don't see a fence in sight." Kinda fun!

Reviewing the video from this afternoon (meeting with our CPA) and uploading files to the server.

Both Marisa and Sean joined the morning meeting. They were touching base and checking on vendors and active parent items for certain vendors, for a client. We talked about some of our plans for the High Valley Bike Shuttle and where we are headed. John joined us as well. We then talked a little bit about adilas percentages.  We will just keep pushing things forward. Kinda like making an arrowhead out of flint (rock). You just keep doing a little chip here and a little chip there. That seems to be about as fast as we can go. Just keep going!

Sean and Marisa left and just John and I were left on the meeting. We went over some ideas, and I tried to answer some of his questions dealing with the company restructure and what we are planning. Nice little chat.

Meeting with Chuck and going over the mini calendar pages. I had to bail out to go pick-up my daughter. We got back together after I got home and pushed up the mini calendar. We did some testing. Actual times were 10:00 to 10:15 and then 10:45 to 11:15 am - total of 45 minutes - with the break in between.

On a different note, I'm excited to see where Chuck goes with some of his other designs and web components that he is working on. He is working on a possible web component to make a custom date picker, that we could use, even for other projects like fracture. Ideally, the more we create our own little custom web components, the better. Less outside libraries and dependencies. We'll figure out a good mix. Good stuff.

Cory joined and Chuck was already on with me. We talked about going with components and trying to focus on a new single date picker vs a dual spanning or preset date one (all ideas from Chuck). We will just get the first one done first and then move on.

After Chuck left, just Cory and I were on the meeting. We switched gears and talked about API sockets (request from a client). We ended up doing some code stuff and took off some navigation links off of printable invoices and mini invoices. After that, I did a small demo on the High Valley Bike Shuttle stuff and where the bulk flex grid tools are at, in the development cycle. Cory is trying to keep track of where time is being spent, just for our records.

Bryan and I looking at code and checking some default flow on application variables and setting up specific services. We made some good progress but ended up deciding to get with either Wayne or Alan on the different pieces. Lots of moving parts and pieces. We were feeling like there was an order of operations error, with something being called before it was fully setup and instantiated. Lots of functions calling other functions and some functions extending from other functions (code inheritance stuff).

On a training meeting with Drew and Lanette from High Valley Bike Shuttle. We also had Sean and Marisa, from the adilas side on the meeting with us. We were going to be doing some merchant processing stuff and setting up API sockets and API keys, but they didn't have the correct login access. That became a small issue and stopped the progress there. I told Drew that I would check with the vendor/representative from Newtek to make sure that they got the correct login access.

We flipped over to showing them other custom code that had been added since our last meeting. We have made a few tweaks to the bulk flex grid tools as well as some small tweaks to the limited flex grid options. We did some light training and even checked a few things that they had done on their own.

The last thing that we covered was getting them, the bike shuttle company, hooked up with Sean and Marisa to do some inventory management training (PO's, parts, items, categories, invoices, and shopping cart stuff). We also briefly talked about ecommerce and other things that will be needed later on. We had them exchange some contact info.

Emails, text messages, and other follow-ups. Recording notes. Installing some new tools from Calvin Chipman. He has a new image converter and a file renaming tool. Got those installed and ran some tests. Calvin is the tool guy. He loves making his own little tools to make things go faster and faster.

Got on a GoToMeeting session meeting with Shari O. to over our existing options for USAePay and getting re-familiar with the USAePay virtual terminal for credit cards, refunds, batches, and other transaction look-ups. We took a couple of screenshots and will be sending some emails to Newtek tomorrow to help get things going in the right direction.

This is just for fun, but earlier today I heard Cory say - "We the bananas from so and so (a client)". It made me laugh. The term "bananas" is what Shari O. uses instead of saying money. I told Shari O. that she is rubbing off on us... :)

Steve and Sean were going over the differences between Medical and recreational gram controllers. Steve was reporting on an older contact that he knew from almost 10 years ago. The guy used to use adilas back in the day, he now has a new business and will be starting up and getting back into it.

We talked about merchant processing and maybe looking into being a possible vendor or reseller. We've been having some issues with our current contacts or sales rep for the merchant accounts.

Emails and follow-ups with Newtek about our accounts with USAePay. We are trying to help one of our clients get all hooked up. It has been a hassle. Not on the USAePay side, but on the side of our vendor representative. Anyways, sent out some email with some screenshots and what not. Recording notes and uploading files and other notes for documentation. Also posted a bunch of things inside the media/content section (files and links) in the shop to document the adilas company restructure stuff.

Recording notes from this week and the end of last week. Rereading some of the files and other notes. Lots of moving pieces.

Recording notes and getting all caught-up. I always feel so much better when everything is sort of caught up. Boy, can I burn through piles of post-it notes. It is satisfying for me to record the notes, add to them, and then throw away the post-it notes. It is almost as satisfying as putting a checkmark on a big to do list.

On the phone with a couple different people from USAePay. Trying to figure out what it would take to become a reseller of their gateway and merchant services. Due to time, they will be recalling me on Monday, at some time.

Brandon, Steve, Kelly, Cory and Charles... if Brandon isn't working today we can record and ask any questions later.

Pretty quite this morning. Shari O., Sean, and John were all checking in. Nothing major. Steve joined and he and Sean were touching base on some prospects and contacts. Steve had some questions on his smart gram controller settings, able to switch, between medical and recreational licenses. After that, Steve and Shari O. were going over pricing and some new accounts.

Cory jumped on with us. She had a few things to run past us. We briefly went over the pick ticket for manufacturing. Questions for Steve and I on different projects and we are at, progress wise. Cory was reporting on some client training that she was doing and the client was really getting it and very grateful. She was really excited and called it enjoyable training. If you have a good student/learner, it makes it fun and enjoyable.

Steve and Cory got into some of the gram controllers and settings. Steve was showing Cory some of the options, advanced techniques, and settings. He is even interconnecting different pages and settings. It does get deep, but if you know what it is doing, you can do some really cool things. As a take away, the real value comes with good training and good setup. The importance of good education.

As Steve and Cory were talking, there is a real value in having everything in one system. Less dead ends, less need to maintain duplicate lists of data (items, customers, vendors, etc.), less having to switch between systems. We were also talking about speed, automation, and quicker setups and getting our clients up and going with minimal effort.

On a quick meeting with Chuck. We looked over some code and merged and pushed up some changes. This was on the parts usage page. These were some requests from Kelly and Cory. After that we looked at some of his other projects that he is working on. Small little session.

Shari O. jumped on the meeting and just needed a verbal consent for the bank to use a debit card for a foreign transaction for one of our vendors.

Tweak Invoice payment API to send in store orders to METRC

Follow-ups with some banks and merchant account stuff.

Prep stuff for sending out emails, promissory notes, and owner percentages stuff. I sent out emails and individual documents to each person on my list for becoming part owners in the adilas.biz company. Small follow-up stuff via text messages.

Steve and Sean were going over sales, options, and new settings. Sean and Steve were than talking about buying percentages of adilas and creating an asset (user-maintained balance sheet item) and how to track the whole purchase of that asset. Emails and reviewing a reseller agreement for merchant processing with USAePay and NMI.

Steve, Sean, and John started talking about LLC's, trusts, MMLLC's and ways of structuring companies and liability shields (virtually). I showed Steve some of the reseller agreement documents and he wanted me to ask a couple of questions. I have a meeting with a guy later today to talk about reseller options. The last thing we talked about this morning was custom forms out in ecommerce to help get and gather data for certain clients. Steve was talking custom options, using flex attributes, and being able to upload scans, images, and other documents. Full custom ecommerce client portal type stuff.

Wayne was reporting on a question about data syncs on some of the servers. From everything that he can see, the pages and special sync functions are firing on those servers. He also reported that he has transferred the corp-wide setting project over to Bryan and he and Bryan are testing and going through things. This project will eventually allow us to limit how many columns are used for corp-wide settings in a couple huge tables. The goal is to break those tables down into smaller, more manageable pieces.

He is also working on some of the extra domain names and making sure that they resolve to the correct www.adilas.biz site. We briefly touched base on the sales tax aggregate project and Cory will be following up with that one.

Next, we covered plans for the data clean-up stuff on the different servers. That lead us into some discussions on data storage and different options. Depending on how deep and how long the storage needs are, we have a number of different options. We talked about costs vs value and what it would cost to reset or restore older data into live access and live activity. There may be fees for code updates, database updates, etc. Adilas doesn't just sit still, it keeps going and if someone goes into deep storage, they are not getting all of the new updates and system maintenance. Cory and Wayne were talking costs and values to restore systems, if needed.

Before we go live with big system wide updates, we need to plan things out, communicate, and make sure that everybody gets the virtual memo. Wayne and Bryan are working on some big changes, and we want to make sure that everything rolls out smoothly.

Towards the end of the server call, we talked about some other projects that need dependencies on outside libraries and outside files. We briefly talked about some pros and cons and light security stuff.

Wayne left and then Cory and John touched base on some projects. John gave us a small demo of where he is at on the discount engine stuff. As a side note, we have had quite a few clients request a smart cart type logic, especially based around discounts, by one get one, and other complex logic and processes. After Cory left, John and I talked about some training stuff and helping each other stay up to date on new techniques.

On a Microsoft Teams meeting with Eric from USAePay and NMI. He was also representing Trinity Payments and we were talking merchant processing stuff. He was looking at reseller pricing with me, paperwork, giving me some ideas, and helping me to define certain terms and processes. We chatted about a couple of different scenarios and I gave him a demo of the adilas software system. He offered a number of possible relationship options and we'll be looking into some of those. He would also like to see what we are doing for our (adilas's) credit card statement. He would be interested in comparing rate and checking things out. Good meeting.

Bryan came over to my house and we chatted for a bit. He is buying a small percentage of Adilas, LLC in our restructure process. We chatted about some projects and then just talked about all kinds of stuff. Just for fun, I was showing him some stuff on an older project called "Learn To Freeride (LTF)". I did a small demo of that product and we talked about some lessons learned. Kind of a blast from the past. Some fun memories. The cool thing was to look at the timelines and see some divine direction and divine design stuff going on.

On a GoToMeeting session with Dustin. We were looking over code and pulling information out of JSON object for AJAX calls. We briefly talked about adding in even more asynchronous loading and data lookups, throughout the site. Dustin is getting into deeper JavaScript functions and dynamically reusing things. That is awesome and will save time and energy down the road.

Emails, research, and odds and ends. Met up with Drew from High Valley Bike Shuttle to setup his USAePay gateway and API keys. We got it all setup and did a practice transaction. After that, we did some light training and looking around his site. I'm excited to help them out and get them going.

Pretty quiet this morning. Emails, checking in the guys, training them on some financial flow calculator stuff - great training ground for showing the cause and effect between the P&L and the balance sheet. Paying bills and recording some notes.

Chuck and I going over things. We were talking about some of our leadership experiences and how the variables of the group can really change things up. We touched base on some projects and then switched gears again. We ended up talking about taxes, government programs, people being left behind, advancing technology, career changes, and ways of working together. If you make it free, people tend to keep expecting free stuff. We've even seen this with some of our adilas clients. There are some challenges there. Always in search of that balance. Affordable yet reachable.

Recording notes from yesterday and today. Phone calls with credit card companies - they want us to run our servers and other expenses through them for deals and discounts. Other small to do list stuff.

Emails, tech support, and paying bills.

Working on the bulk flex grid tools for High Valley Bike Shuttle. Part way through, I jumped on a meeting with Bryan to look over a small bug with the CFC's that he is working on. Those are dealing with a project that both Wayne and Bryan have been working on for helping to swap out some of the corp-wide settings. After Bryan and I finished, I spent the rest of the time back working on the action page for the add bulk flex grid tie-ins. Making progress.

Steve and Sean talking about other connections (people) and different networking angles. Steve would really like to see if we could find some adilas power users that are looking for some work. Marisa joined and they started talking more sales and marketing. As a side note, both Sean and Marisa are doing a great job with deployment. Steve would like them to circle back around and help make sure that our other clients are being taken care of (reselling or re-pitching our older clients - reengaging them).

They were talking about news and updates and helping to get the word out and about. They were talking about getting some of the new flyers in a standard spot and making those available to any of our guys/gals who need them. Marisa has been revamping some of the flyers recently. The goal is to help our clients stay up to date and also inform new or potential clients of what we are doing and what we offer.

Those who were on the meeting, we touched base on other projects. I was reviewing a number of documents and looking at a website for a possible merchant processing vendor. I have a meeting later today with a guy from USAePay and NMI. The guy also represents a company called Trinity Payments that actually does the merchant processing. The other two companies are called gateways.

Towards the end of the meeting, Eric jumped on and we pushed up some code to the Herbo server. He needed to push up a file for some live testing.

Readign the reseller document (contract) for USAePay and Trinity Payments. Lots of legal mumbo-jumbo stuff.

On with Eric from USAePay and Trinity Payments. We met and went over some of the documents and contract stuff. We met for about 15 minutes. This was a small follow-up meeting. After that, I went back and read more of the documents. I have two main documents, each multiple pages (7-12 pages each), all legal stuff.

I also got a call from Bill at Harris Computer Solutions. We talked and I explained to him our SaaS model and where we are headed.

Cory and I going over a list of questions. About halfway through, Steve and Chuck joined us. I think that they were going to meet and work on some look and feel, but Cory and I were on the meeting. Anyways, the question got brought up about doing down payments on stock/units and how to book that and keep everything straight. The real answer is using transitional invoices. Having said that, we went round and round talking about possible options. Towards the end, Chuck was saying that when we redo our fracture stuff, we may need to make it part of the system that a prepaid invoice, deposit on merchandise, in-store credit, and other things be put in place and education and training made available.

For the record, here is how you would do it right now... using a transitional invoice.

1. Stock in the item, even if you don't have it in stock. If it is in stock, use that item. Anything that is unknown, just make a note of that. For example: a serial number or VIN number - maybe use the customer's phone number or email address.
2. Go to the stock/unit and go through the invoice/sale process. Make sure and set it to a transitional invoice (that wording is dynamic - layaway, prepaid, etc.).
3. Do the sale for the full amount and then take the amount that is either pre-paid or deposited. That will start the journey of the stock/unit and the payments received. All of these transactions will auto flow over to the balance sheet (already built-in) if using a transitional invoice.
4. Keep the invoice in the transitional state until it comes in, gets delivered, or whatever. If needed, additional payments (deposits on merchandise) may be made along the journey.
5. When ready, flip the transition invoice over to a real customer invoice and finish out the rest of the info. Once flipped, it will show up for sales taxes, on the P&L, accounts receivable (if money is still owed), and will count against inventory values. Prior to that, the whole thing is held on the balance sheet as the work in progress, pre-paid invoice, layaway, deposit on merchandise, etc. (dynamic naming).

Anyways, the takeaway is for fracture, we really want to have a way to show our people how to do certain tasks (searchable education mode). We also want to have some of the special account stuff like in-store credit, vendor credits, gift certificates, coupons, punch cards, etc. all done and part of the system. Those features may be built-in prior but need to be there. As a note, a lot of those will be sub sections of what we call special accounts, just like the current loyalty points stuff.

Admin budget meeting. We had Cory, Shari O., Steve, and I on the meeting. We started out the meeting going over an email that Shari O. had sent with items on accounts receivable, bad debt (uncollectable invoices), expenses, and report on new systems. I was taking notes and we got lots of good back and forth communications and plans. Another key thing that we talked about was the need to get our guys (developers) to enter notes on the projects so that we can track hours and progress. Basically, a way to step up and clean-up some of our internal processes.

Notes were sent out after the meeting to all parties.

Going over notes from yesterday and recording them into the developer's notebook.

Jumping onto the morning meeting. It was just Steve and I to start out with. Steve had a couple of code questions. We then started talking about reseller documents and contracts for USAePay, NMI, and Trinity Payments - all merchant processing stuff. We are considering being a reseller of online merchant accounts. We have had merchant processing built into our system since 2009, we are just now getting to the point that we may want to enter that market space and become a reseller of those services.

Steve asked about the bulk flex grid tools and customer facing scheduling stuff that I was doing the bike shuttle company. He volunteered to help build out some settings when I'm ready for that. He would love to go after some clients in that neighborhood. We also talked about using ecommerce, message marketing, and other client portal type tools to really connect with an end-user or client. Good stuff. Steve has lots of ideas.

Shari O. joined and we talked about banks, deposits, and bank transfers. After that, Steve and Shari O. were going over servers and where to setup and put new clients. They also went over some quotes and prices. The last thing that went on in the morning meeting was Steve and Sean going over sales and options to help out our reps in the field. They are bringing in contacts and leads, just trying to make sure that we take care of those leads as they come in.

Everybody left and I was waiting for my next meeting. Nobody came, so I did some emails and what not. Going through small to do list stuff to get my week started.

Reopened the branch, got back in there and made sure that I knew what was going on. Started to make some code changes and got pulled off on another meeting. I'll get back to it.

On a GoToMeeting session with Bryan. He is trying to help a client out who seems to have a hardware/software type problem, dealing with merchant processing and a 3rd party card reader. We went over some ideas and talked about window's services, add/remove programs, restore points, zip files, and getting the client reverted back to old and old or going forward to new and new (this would require them to purchase a new card reader). Anyways, trying to help figure out the best options and possible approaches.

After Bryan left, I was doing emails and light tech support stuff.

We had a client ask for some info on ecommerce images. This is what I wrote. Just recording it for the record.

Good morning. This is going to be good news for you... The images are under the top_secret folder but there is no way of protecting a .jpg file. We only protect the code and data files. Images are images, if that makes sense.

Each company has a different path or corporation folder. If I were you, I'd do an API call, get the path one time, and then store that folder name as part of that company's record. Here is a sample for two corps – 53 and 54

top_secret/images/corp53_5FC2B3D1C9

top_secret/images/corp54_22C0DEC894

As you can see, the last ten digits are a small hash (mini password) to help protect the images. If I were you, I'd figure that folder name out and just store that part of it. For example – for corp 53 – store this - corp53_5FC2B3D1C9.

Underneath that folder, there are the following other sub folders. thumb, small, and large. These are standard and exist for each corporation.

• The thumbnails are in the thumb folder – really small. 29x22 pixels – file name pattern is "part-[part id]-th.jpg" for example: part-55555-th.jpg


• The smaller images are in the small folder – little bit bigger – width is set to 160 pixels –
  height could be anything – file name pattern is "part-[part id]-[image
  number].jpg" for example: part-55555-1.jpg or part-55555-2.jpg, etc.


• The large images are in the large folder – biggest images that we store – width is usually between 640 (older files) and 760 (newer files) – height could be anything – file name pattern is the same as the small folder. Often people will just use these larger images out in ecommerce.

Here are a couple of sample paths for a large image:

https://data0.adilas.biz/top_secret/images/corp53_5FC2B3D1C9/large/part-225406-1.jpg

https://data0.adilas.biz/top_secret/images/corp53_5FC2B3D1C9/large/part-225406-2.jpg

Hopefully that helps you understand a little bit more about the images and where they are stored and the naming conventions.

Finished up the first round of the bulk add limited flex grid tie-ins page. Pushed it up to the server and sent a text message to Drew, at the bike shuttle to check it out and see what he thinks. Making progress. Here is the help file for that page - so far.

Pretty quiet this morning. Got a text from Steve, Sean was traveling, and John briefly checked in. I was doing emails and then back on the bulk flex grid tools for the bike shuttle.

Wayne, John, Bryan, Cory, and I were on the server meeting. We went over a number of projects throughout the meeting. We need to spin up a couple more boxes and the guys were working on a quote and a time estimate for one of our clients. This was really cool, but Cory asked Wayne what it would take to get this project done. Wayne flipped it on its head and was talking about working the whole thing backwards. Basically, you start with what they want (that wasn't super clear) and then you figure out what things you will need to do to get there. Wayne's approach quickly started to focus on what was wanted vs what could we do (the sky is the limit). I've known that and even used it, but it was fun to see it play out in the meeting. I really enjoyed it.

We went over options and questions that we could take back to the client. Are they looking for access to raw data, summarized data, a webpage or web-based report, a spreadsheet, or even open API socket access points? That makes a huge difference as to where you go and what you do. We also talked about certain projects and possible code that has already been written for other clients and how we could tweak that if needed. Wayne was recommending that we get with the client, open up a blank spreadsheet and see what data they were looking for (basically doing some consulting - instead of just quoting something). I took it as a form of listening and even helping to educate our clients. That method or process, of talking with our clients, will actually help our clients be even more happy and really get what they want.

We have so many possible options, sometimes it takes some time to figure out what is really wanted and/or needed. There is a big difference between value and cost. We were talking about that. Ideally, we focus more on the value vs the costs. As we were talking about this, I was thinking about some of the ideas of the value add-on core model that we have been dreaming up for fracture. Here is a rough recap that I grabbed from an older element of time.

The concept of the value add-on core model - with different rings to denote the other levels of add-on value pieces. We have determined at least 5 levels as of right now. Starting from the middle. 1. Core (adilas core - everything that exists right now - image the), 2. Business vertical or industry specific, 3. Custom level, 4. BI or Business Intelligence level, and 5. Enterprise or multiple corp(s) level. Each of those value rings has to be purchased and serviced. You have to have the transactional data core to get it started, but anything beyond that, is extra or a value add-on piece. Very configurable.

Eventually, everyone will want some of the (BI) Business Intelligence stuff. This will take the underlying transactional data and will help to summarize it, aggregate it, count it, condense it, and display it in a way that is easy to digest and fun to look at (aka eye candy but also eye candy with a purpose). I'm really excited to get to that part of the project. I want to make sure, when we build out the fracture project, that we include this Business Intelligence (BI) level into the main application.

As far as history, when we started, we didn't have clear picture of where we were going. The further we go along the path, you can see how the other pieces play into the mix. I'm excited to keep working on them prior to getting to fracture, but I really want to make sure we include them in the next round. In a way, it's like what Wayne was saying, work the project backwards - what do you want, then make sure that it fits and fills those needs. Make the plan.

Chuck and I testing and going over credit card readers and the credit card payment page. Chuck was giving it a new look and feel (small facelift). We did some testing and Chuck is going to make a couple of changes and then we will push it up. We are going through things, one page at a time and trying to upgrade the look and feel to match a more modern theme.

Meeting with Bryan and going over the invoice due date project. We did record part of our meeting. See attached, if you want to see it. At the end of the meeting, we did a light progress report and showing the progression of certain projects over time. We keep chipping away at things.

Shari O. jumped on this morning with a few questions. She was setting up a client on an Authorize.net account for merchant processing. We looked at a help file and got her going in a good direction. After that, John checked in and setup a meeting for later today. Shari O. jumped back on a little bit later and had a few more questions. We did some drawings and diagrams and got her all set. She just had some questions on how things work with internal merchant processing vs external or 3rd party solutions and standalone merchant processing. I also did some emails and other small things.

Chuck and I looked at code and merged in two small branches. One was for credit card payments (manual or swipe). The other was for date pickers on the main flex grid tie-in homepage. Once we got those things merged in, we chatted about some other stuff. We talked about home office layouts, ergonomics, standing while working, and other hobbies and pastimes.

On a meeting with Bryan and Alan. We were looking over the code that Wayne and Bryan were working on for moving the corp-wide settings out of the big huge corporations table and moving it into a smaller settings table. Our goal is to break up that huge table. As a fun history note, our first dabble into corp-wide settings was back in 2009 and we added in six new settings. Now that same table has grown to over 400+ columns. We will be taking about 350 or more of those settings and putting them into smaller tables that are able to be maintained and prepped for future growth. Good stuff.

By way of a note, we are seeing settings in a number of different areas. Starting way up high, we see corp-wide settings or world level settings. We see group or section level settings (any of the 12 main player groups). Next we are seeing page level settings come more into play. This is somewhat newer. And finally, we are seeing user or individual settings coming more into play. The foundation of adilas is built on permissions and settings. That is how you make everything so dynamic.

Anyways, back to our meeting, Alan will be looking over the branch of code and giving his thumbs up and approval. Once we get Alan's approval, we'll work with Cory to schedule a live or production deployment. This project, changing out the corp-wide settings, touches hundreds of pages. Anyways, we are testing things right now and will merge and deploy in the next week or so.

Reading reseller docs for Trinity Payments, NMI, and USAePay. Lots of legal stuff. I also met with Eric from USAePay over a Microsoft Teams meeting. He sent me some other forms to fill out. Signing and doing paperwork and contract stuff. Sent an email out to Steve, Cory, Craig, and Shari O. to let them know that new documents have been signed and are in the process.

Code review with John on his new changes to the discount engine. We went pretty deep and I think that it was really good. Lots of mixing and blending of technologies, code languages, tools, data, and general tech. Lots of crossing of both Adobe ColdFusion and JavaScript. Sometimes those two technologies can be hard to mix (server-side and client-side languages). Anyways, looking over code and talking about what and why we (mostly John) are doing what we are doing. Great discussion and lots of back and forth. We went over some JQuery, Dom manipulation, AJAX, date stuff, nulls, escaping characters, sanitizing data, JSON objects, crazy string manipulation, and even looking deeper at possible integrations with hardware or underlying Java code. We went pretty deep.

We also talked about what a project takes as far as planning, research, R&D, proposals, mock-ups, design, code, testing, review, project management, and deployment. There are lots of steps. You also have to look both forwards and backwards to make sure that things are prepped and ready for the future as well as smoothly integrated with the past or legacy code. What John is really making is a 1-pager type interface for the discount engine. Big upgrade from what we currently have. He has some big plans for it. The current project includes things like the 1-pager design, modals, pop-ups, custom CSS, tabs, data tables, exports, tool tips, helper windows, and dynamic pop-up sub forms. Lots of moving pieces. Good meeting.

On the morning meeting with Steve. We touched base on the discount engine that John is working on. I was with John yesterday for over an hour and half looking at the code. There is a lot going on there. Good stuff and making progress.

Steve wanted a demo of where I was at with the bike shuttle company and some of the custom scheduling and booking tools. I showed him the progress, including the bulk add limited flex grid tools. I showed him where I was at on the bulk edit flex grid tie-ins tool and how cool that will be. We also jumped out in ecommerce and talked about the client facing scheduling options that we want to add in. I've got a few more internal tools to work on and finish and then I'll roll outside in ecommerce and work on the client facing scheduling options. Marisa joined us and expressed that when we get to the planning and design portion of that project that she and Chuck would really like to be involved. As a fun side note, this will end up being a precursor to the WanderWays project (campground, cabins, and other scheduling options).

Part of my role is to help share the vision of where we are heading and how to get there. I've got some of the other guys and gals building it out, I just need to keep helping them see where we are heading. As a fun bonus, they catch the vision and then add more to it. That makes it really fun.

Steve and Marisa were going over some Metrc syncing and Metrc training. There are tons of options built-in to the adilas platform. Pretty cool. After that, they got into a training session on how to deal with samples and how to bring them in, sell them, and account for them. Steve was showing Marisa how to treat them similar to normal inventory items. Next, they got into a small internal training session on using update PO's to help with inventory updates and adjustments. That lead to a conversation about how important dates and date sensitivity is when dealing with inventory tracking. There is value in being in a real time inventory management environment.

The last major topic of the morning was dealing with the value and need for education. We have all kinds of tools and some that are light years ahead of the competition. However, if we don't teach our users how to use them and if they don't know about them, then they can use them. There is a real need to train our internal staff as well as getting our clients trained up and using the correct tools. That is a challenge but also an opportunity. There is real value in a power user, someone who knows adilas backwards and forwards. They are needed and in demand. There is real value there.

Recording notes from the past couple of days. It is amazing to see how much happens in a single day or a single week. Lots of moving pieces. We keep chipping away at things every day.

Recording notes from yesterday. Working on the edit bulk flex grid tools for the bike shuttle company. Making good progress. Other email stuff.

Finished up the first round of the bulk edit flex grid tools for the bike shuttle. Pushed up the files. It still needs some more loving, but I wanted to push up the progress, based on the page. Good stopping point. It doesn't work yet, but you get the idea of what it is trying to do.

I got an email from our tech support girls, and they were saying that we were getting some batches blocked on a syncing process that had the word "AppleTurnover" in it. The real cause was the keyword "Applet" which is an older way that things used to be hacked (XSS or cross site scripting). We went through and removed all of the restrictions on the word applet (a mini program or baby app). Pushed up the new code.

Emails, recording notes, and checking banks.

For the first part of the meeting, I was on with Wayne, Cory, and some outside clients on a Google meet meeting to go over an outside data analytics service that was being requested for one of our clients. It was mostly a brainstorming session about possible options and direction. We pitched a proposal for direct data access, showing real data, mirrored over to a new instance, but on an independent accessible database. One of the topics that came up was the data dictionary and the education on the database schema, rows, tables, columns, and relationships (what is what, inside the database). The term that was being flipped around between the parties was the data dictionary (written eduction on the database stuff).

I jumped on the GoToMeeting after we were done. Not much going on there this morning. I was doing emails and texting back and forth with Steve. He was on another meeting with Mike and the state of Mississippi. Steve had some questions about some timecard calculations and wanted to see if we were storing any of the calculated values. I told him that we do store calculated values for employee timeclocks and timecards but do not store calculated values on sub dates and times for elements of time. That may be something that we want to do in the future. It would help save time and speed things up. Steve was saying, when it's time, we'll go for the MVP (minimal viable product) type release. In the meantime, we'll just calculate things on the fly.

Eric and I jumped on and looked at this. Because Sean wasn't around to do some testing, we decided to wait. We flipped over to his other project.

Eric and I worked on his other project for the balance sheet bump value for both reoccurring expenses and duplicate expenses. We went over some existing code, made some tweaks, then made some more tweaks. We ended up settling on a more simple approach and recoded to that version. It was a process - somewhat a internal Q and A. If we do it this way, what will happen? If we tweak this, what does that affect? Etc. Anyways, we got the code done, did some testing, merged it in and pushed it up to all servers.

We also went over some JavaScript memory issues. Working through things.

Dustin and I looking over a possible code problem. Doing some live testing. Ended up finding the error and it was a client's data and them missing something on their side (Metrc rooms) for an API socket connection. Made a few other changes and pushed up code.

Working with Bryan and getting him some of the older files for the invoice due date project. We ended up making my computer go back in time (like 3 years ago) to pick up some of the older code files. Small journey back into the past.

Helping Bryan get some more older files for the invoice due date project. I ended up making a full back-up so that I didn't have to keep going backwards.

New files for Bryan for his invoice due date project. Also helped Dustin and merged in some code. We repeated the process a couple of times, each with small changes. Lots of back and forth.

Steve had some code questions this morning. We went over some math on his running age in hours for sub dates and times, part of an elements of time report. We were also catching up and talking about sales and other options. I was asking Steve about some of the different meetings that he had been on over the past couple of days. Nothing sits still. Finished out the morning doing emails and what not.

Wayne,  Shari O., Cory, John, and I were on the server meeting. Shari O. stayed for the first little bit and then had to bail out. We were talking about a client and some of the needs and/or even their potential needs. One of our clients was sold to another owner and the new owners are going in a different direction. We were talking costs and prices of what it takes to open and close systems. We talked about normal storage where a client still has access to a system with minimal traffic vs full cold storage where it gets stored away and totally inaccessible unless a major system restore is done or made. We talked about costs to do some of those activities. You end up with costs both coming and going. We would have to pass those values over to our client, depending on which way they want to go.

Along those lines, of setting costs and values, I let Cory and Shari O. know that they have my full permission to set those prices as they see fit. After that, we rolled into a number of other server type questions. We went over possible options of doing some custom work and linking up the adilas database with a different service on the Amazon cloud. This would be specific for a bigger client with multiple systems. They are wanting to hire out a data analyst team to pull some deeper queries and get some aggregated data flowing into certain reports.

One small takeaway from our meeting - Wayne was pitching the concept of spending some time on doing a proof of concept before either fully committing or giving an estimate. Sometimes you have to jump in and swim for a bit before you really know what it will take. That is kinda scary sometimes.

Wayne left and it was just Cory, John, and I on the meeting. John was showing us a small demo of his newest version of the discount engine and new updates and changes. It is live, but hidden. We encouraged him to keep pushing things up to that spot (hidden but live) so that we could follow along with progress.

Dustin joined us and he and Cory were going over some live testing issues and the need to roll back a project. We did so and got it all merged back in and pushed back up to the servers. As a side note, they were talking about the cost of a bug. It takes extra tech support, causes stress, emergency development, code sign-off and re-deployment, and it frustrates our clients. There is always a cost for pushing up bugs.

This is just for fun, but Cory was saying - No pushing new code up on Friday! That's a bad idea.

Dustin and John left and just Cory and I were left on the meeting. We started going over a list of projects and questions that Cory had. We went over my cart favorite buttons and how they play with subs (child inventory). Next, we talked about 3rd party solutions and hardware.  They are both needed, but sometimes give us a black eye. We can't control those pieces very easily. We went over a question about active and inactive users, editing relationships, and possible solutions for resetting things and hiding inactive users. This already happens most times, but there are certain scenarios where both active and inactive users are needed. Say like a salesperson that is assigned to a customer. If an old assignment was put in place, they don't just automatically clear themselves if someone gets fired or made inactive. Those are still real relationships that need to be updated and reassigned. It can get tricky.

Checking emails, sending Bryan some older files, and recording notes from earlier today.

Working with Bryan on the invoice due date project. We checked on some code questions, added a few things, and pushed up the database update portion of the project. Started running the database updates on each server. That is a lot of clicking. After I stopped, Bryan was going to continue on and do the rest of the servers.

Got caught up in my notes. Finished recording notes from yesterday and today. Filling in the gaps.

Helping Steve with a report for his super adilas power users. He is looking for users who have done over 5,000 invoices that are no longer working for companies. Basically, a way of searching the system for power users. We did a small recap of other updates and happenings. Bryan and I were looking at code on the invoice due date project.

As part of our meeting, I was explaining to Chuck about our invoice due date project. He had a ton of good ideas and we talked about options to combine the invoice due date with automated reminder emails and what not. Great ideas. This is just for fun, but he said that he used a different product and it had automated reminders. He got more responses from the "nag" (automated emails) than he did by asking for money. As we were talking and joking around, he said, we should rename our automated email stuff "The Nagatha" (one-off from the nag). Just being silly.

Once we got back to normal work, we spent some time looking over the flex grid stuff. He is working on the add/edit flex grid tie-in page (rework and page facelift). We also spent some time talking about different questions, ideas, and styles. Those conversations included topics and discussions dealing with taking heat on making changes and adding a more modern look and feel (getting in trouble for making things look better). We have a lot of users who don't like change and we are constantly rolling out new changes, tweaks, and refinements. That's how we roll.

We spent some time talking about things that need to go in the adilas docs (internal snippets and style guide). We also went over some testing and talking about adding in tons of client-side validation (JavaScript) for fracture. We also talked about the value of doing small prototypes and how much we can learn by doing those little mini apps. As a side note, Chuck is really excited about fracture (future project in adilas) and has a number of great ideas and vision. Almost every time we talk, I hear him throw out a ping or a reference for planning and building out fracture. We'll get to it... it just takes time and resources, but the vision and dream are out there. Let's go get it!

Working with Bryan on a code review and clean-up on the invoice due date project. Code sign-off and live testing on the Herbo server. Small tweaks along the way.

Back on with Bryan. Checking over code and making changes. Passed him over 10+ files to check. Doing emails and looking over code from Chuck on the add/edit flex grid page. Pushed up Chuck's new files. After that Bryan and I pushed up some code and did some live testing on the invoice due date project. Making progress.

Emails and adding in Alan as a co-founder and part owner in the Adilas, LLC. Good stuff!

Fixing a few small bugs with invoice due dates, validation, and one page that was showing an error. Most everything went pretty well. The new invoice due date code hit all of the serves this morning. It was just one page that was struggling. I joined the morning meeting and was telling Steve that we launched new code. I was pretty excited and letting him know that we had some new toys to play with. Cory joined and said that a client was having some issues and problems. That lead into almost a 2-hour bug hunt. I was working and pushing up changes and then right on to the next one. The good thing was it was only not working for a couple of clients. Everybody else was doing fine. I ended up getting Alan on with me to look over things. Some of the deeper DAO's and services. Anyways, we got it figured out.

Working with Bryan on updates on the custom shopping carts and adding in the options to record the invoice due dates. Running some tests and merged in some code. We then switched gears and started planning the next steps. See attached for our work document (brainstorming of ideas).

After that, I was texting back and forth with Chuck on setting up limited flex grid stuff.

Budget meeting with the admin crew. Steve wasn't able to make it, but Cory, Shari O. and I were there. We talked about the need for ice-down dates (per section) and how cool that would be. The ice down dates are part of our wish list for fracture (or whenever we can). It has been a goal and dream since 2008/2009 ish. Sometimes things take awhile to get back around to.

We went over budgets and did some calculations and look-ups to get actual values. We spent quite a bit of time talking about next projects for some of the guys. We also did a session dealing with naming conventions for expense types and how we want to classify thing on the P&L. This is mostly dealing with guaranteed payments and tracking how we are paying owners.

Part of the conversation went into some wish list items for Shari O. and ways that we could help her in accounts receivable (A/R's) and chasing down monies and payments. Brandon has both nots and spreadsheet documents from the meeting.

After the meeting was over, John jumped on and had some questions about timecards and timeclocks. We went over ideas, expectations, and where we are headed.

Today is Memorial Day but we forgot to tell anybody that nothing was going on. So, I jumped on the morning meeting and just did some simple emails, documenting stuff, and general light clean-up. Sean popped in but other than that it was pretty quiet.

Talking with Steve about limited flex grid, status, and where things are headed. He is excited to expose some of the new tools that we are developing out to the rest of our clients. We are also trying to stay ahead of Chuck and what pages he is redoing and making them look better. That lead us into some discussions on layout and display options such as tabs, accordions, pop-ups, modals, and other modern display and layout styles.

Everything keeps going back to settings. We talked about 4 different level of settings, that we are seeing. They are: 1. Corporation level settings (corp level or world level), 2. Group or player group level settings (12 main players), 3. Page level settings, and 4. User level settings. As a side note, settings are awesome, but they can also make things feel like it is more complicated. You have to play the game of iceberg vs huge mountain. Hide what you can, only show what is needed, but still make it available if needed (like tools in the shed). We see more and more of this type of thing coming as we build out toward fracture and future development.

Another fun thing that we talked about was page views. We happened to be on the time homepage and going over different page views of the same data, but how cool would it be if we could build out reports that show up in calendar view, timeslot view, grouped or aggregated views, or normal details and tabular data type formats. So many options, including charts, graphs, and other layout options. Not to mention, export or save custom report settings. All available, we just need to keep bringing it all together. More stuff for fracture.

The next subject was dealing with getters and setters and how those pieces are so dynamic. Some of our entries have 30-40 fields or choices. We don't want to have to submit all of those pieces, every time, for a simple update. Getters help you get the data in smaller pieces, as needed. Setters help you set or update the data in small bitesize pieces. For example, say you have 30 records of flex grid, each with a possible 40 columns. If you do the math, that one bulk edit page could have over 1,000 fields. What if only 2 pieces of data actually change? Using a simple setter allows you to only alter smaller pieces of the whole without having to carry the whole load. Efficiency!

As we were talking, we can see the value of using small teams to push on projects together. That could really help with resources and giving everybody a buddy to work with. Along those lines, here are some other projects that we may give to Bryan or a small team of developers. Flex attributes for all of the main players (used to be called in-line database extensions), vendor/payee logs (modeled after the customer log section but for vendor/payees), and other projects that already have a small handrail or guide. Anything that has been done before seems to be easier, due to the example or handrail for the developer to follow.

Cory was asking for reports on different projects. Wayne joined and we jumped into the server stuff. He was requesting more specific errors to be reported via email. If the error reports are too generic (server 6 is down), that doesn't give him much to go off of. It would be better to say something like, server 6 is denying login access or something like that so he knows where to start. Anyways, he was requesting more details when reporting problems and server errors.

We talked about the database clean-up for data 0. Next, we got into looking over errors and slow pages and slow queries. The main problem child queries are all dealing with corporations with tons and tons of inventory, invoices, and sub inventory. There is just a lot of data there.

At the end, John gave a small report to us. He has been working with Dustin to help get Dustin up to speed with server stuff and pieces.

Meeting with Steve and Cory to go over projects. We talked about a couple of projects for Eric. We talked about gift cards, other special account projects (in-store credit, vendor credits, punch cards, coupons, and gift certificates or gift cards). Another one is the mini aggregate project to handle inventory quantities per location. The other possible project for Eric is getting back to the enterprise item catalog project. All of those have value and would be great add-on's.

The next major subject was projects that Alan is either working on and could work on. He is one of our top developers and is in demand, because he can do so many things. One of the projects that Cory really wants him to work on is the transition invoices out in ecommerce land. They already exits out there, they just need a little bit of loving. He could also help Steve out with some BioTrack production stuff.

Lots of talk about other developers and what they are working on. It is a challenge to coordinate projects and developers. Lots of moving pieces. We also talked briefly about some projects for Bryan. We are still trying to help our clients transition from billing in the old independent way to dealing with Adilas as a team or an entity.

Another subject that came up was the number of hours spent in a training and tech support with our clients. It takes a lot of time and effort. One of the benefits is that we learn a lot along the way. The more we help our clients, the more we learn, and can adapt the tools and features that we have to get the desired outcome. Along those lines, sometimes we (internally) need to be reminded of certain processes and tools that exist that we may not remember or are new to us. For example, all of Steve's new backorder stuff that he developed and managing quotes, orders, PO's, and backorders.

Cory was kinda putting her virtual foot down on certain projects. We are trying to retain our clients but sometimes they get out of line. We talked about preventative maintenance type stuff with our existing clients and helping them along the way. We, as a company, are offering more and more internal service offerings. We used to sub it all out to outside independent sub-contractors. We are trying to make those same offerings, but do it all internally now and helping out in new ways. It makes for a better product and better retention.

Bryan and I met up to go over ideas and brainstorming ideas for the invoice due date project and taking it to the next level. See attached for some of our notes.

Meeting with Rich, Jennifer, and Eric from Trinity Payment Solutions. Small intro, defining some terms, and talking about some options. I asked them to setup another meeting with other key players from the adilas team. The next meeting will be next week and the goal is to get everybody pointed in the right direction. Their plans include two parts - 1. New MID's (new merchant accounts) and 2. A marketing effort to all of our existing Adilas clients (offer merchant processing to our existing clients).

Just for fun, here were some of the terms that I wrote down that they were going over: Var sheet (reseller parameter sheets - information for new accounts), interchange fees, discount rate, no price increases, termination fees, etc. Every industry has its own vocabulary.

Emails, text messages, and recording notes.

Bryan and I jumped back on to do some more planning on the next steps and phases for the invoice due date project. We spent a lot of time talking about settings and automating some email options that would tie-in well with the invoice due date stuff. Currently, we have three main areas that need to be tied together. We have some new corp-wide settings, we have the email settings, and we have the individual customer terms that may play into the invoice due date stuff. Our current goal is mixing and blending those three things together to make a cohesive product and flow.

Bryan was given the challenge of breaking the project up and into smaller and smaller pieces. Basically, taking a bigger project and figuring out the bitesize pieces that we could do in order to get the bigger project done, finished, and across the finish line. If we don't break it down, it becomes too big and too hard to work with.

I got an email about an Adobe ColdFusion conference coming up in October. As part of the email, they were requesting people who wanted to speak and/or present. I decided to put my name into the mix. I would really like to be able to pitch the concepts of world building and the concepts of the data assembly line. I sent them links to our website and also a link to an adilas origins - core concepts document that Shannon and I worked on at the beginning of the year.