On the morning meeting, Marisa was showing us some sub inventory issues that need to be smoothed out dealing with sub inventory attributes and template settings. I was doing some emails. A question was brought up about New Mexico state payroll and state withholding. We used to have that state, we just need to circle back around and make sure that everything is updated and good to go.

Shari O. and I spent some time going over progress with USAePay and getting information from them. We have both made multiple calls to our contacts at Newtek and haven't really gotten the information that we need yet. Kinda frustrating, we just want info on account types and how to help our clients sign-up for what they need. If we can't the info that we need, we talked about going in a different direction. Both of us will keep trying, for the time being.

Switching subjects, Shari O. and I spent quite a bit of time talking about our transition from full 1099's for all of our guys and gals to the multi member LLC (partners and ownership) options. Eventually, we may need a hybrid type solution that allows for owners, 1099 folks, and even employees and W-2 folks. Still trying to figure things out there. As a note, Shari O. is recommending that we slowdown a bit and make sure that we have watched budgets, gotten documentation, and standard procedures in place before we jump too quickly. I showed her the adilas docs section, inside the adilas site, and she had never been there. If we do build out more internal flow and owner type handbooks, that is where it will go. It will be called our standard operating agreement or something to that nature.

Shari O. and I talked about budgets, watching and tweaking those budgets, and then making some decisions. Lots of talk about timelines and timeframes for some of the upcoming changes. Good stuff. I'm super glad that she cares and is willing to ask hard questions.

Got invited to a Zoom session with Sean, Marisa, and Steve. We looked into a small issue with the enterprise vendors and setting default chart of accounts. The chart of accounts are corp specific and don't transfer when copying over vendors from corp to corp (enterprise level stuff). I helped them fix it and got them going in the right direction. I sent an email off to Alan explaining what we found and some small suggestions.

Calling Newtek about USAePay options. I was on hold for quite a while and wasn't able to leave a message. Called back again and at least left a message. While I was on hold, I read an article that Steve passed me over dealing with guaranteed payments for partners and some of the gotchas in that realm. Lots of tax laws and moving pieces. We will definitely need some help from a CPA and an attorney, when we are ready.

Working on the copy selected chart of accounts between corporations. Testing and working on the main groupings section. The page will end up having copy options for the main groupings, sub groups, and actual chart of accounts (deposit types, expense types, and balance sheet types).

Steve and I were on a meeting, recording notes, and going over budgets and other spreadsheet for planning purposes. Good meeting on the options of making some of our guys and gals into partners and partial owners (small percentages) of the adilas entity. See attached for some of our notes (towards the bottom of the doc). Trying to keep a bunch of the notes in the same place.

Tuesday morning sales meeting was going on this morning. The meeting took the whole hour. Lots of different subjects being covered. They went over their email campaigns, possibility of Eric (one of the developers) doing some sales and networking, touching base on the enterprise level systems and their existing functionality. We may want to go back and spend some time doing some small tweaks on some of the functionality and flow. Just some small tweaks and quirky things that need a little bit of loving.

Sean was asking about travel expenses. Steve recommended that gas, mileage, and drive time expenses be passed on to the client. That seems fair, in my mind. Next, they switched over to some corp-specific tables and settings. As a wish list item, they would like to see more wizard type setup processes that walk you through the setup process to help with choices, defaults, and other settings.

Steve helped Marisa with some cannabis level settings for a new client. That lead into looking at options for custom labels and barcode stuff. The need for custom labels is a huge deal and seems to keep growing. We have some pieces in place that help fill the gap, but there is still a huge need for a super powerful, user maintained, custom label and barcoding or QR coding engine. We have some pieces to the barcode and label solution, but they still need some help. We have that on our to do list, but it is not currently the highest priority. Hopefully soon!

Wayne, John, and I were on the server meeting. We checked in on data 5 and some of the server monitoring that the guys are doing. Our goal there is to glean insight and info on slow queries, huge usage patterns, and see where we could speed things up. After that, we were touching base on other projects and going over our semi-on-going list of server things.

Ideally, communication will improve as often things get done and changed and no one knows about it. Almost like certain information tidbits reside with single users or developers and no one else knows what is going on. Super common.

We also talked about getting Dustin involved more with the servers and helping John and Wayne out in that area. They would like to get him all setup and trained on some of the Docker stuff and start the training from there. I gave them a time Id number to track their time and efforts.

Recording notes and rereading notes from some of our meetings this morning and yesterday. Things keep moving, it doesn't seem to stop. That is both good and bad... :)

Follow-up with USAePay and getting more info on merchant processing stuff. On the phone with Steve talking about all kinds of stuff. Mostly about the multi member LLC and percentage ownership stuff. Steve and I were on the phone for well over an hour and a half. Here are some of my notes... all over the place.

- Trying to get our guys and gals to focus on one thing and getting it all the way finished. From top to bottom. We have a lot of stuff that feels 50-75% done. We want to get it all the way across the finish line. Our goal is to give them a single project so that they can get it all the way finished before moving on. We are hoping that if we extend them some ownership in the company that it will help to motivate them to play the game.

- Need for more news and updates. We also thought that it would be good to do some internal news and updates for our internal staff. That idea came from Steve.

- We need someone who is able to get into some deep JavaScript stuff and really help out there. We have a number of projects that are very heavy in that area and need some loving.

- We chatted about different developers and their skill levels. As a side note, the deeper we get, the more things start breaking down into smaller and smaller pieces. So many interweaving and interlocking pieces. Lots of dependencies and requirements.

- Kelly seems to follow trends very well. It's almost one of her skill sets. In the book, "Who Moved My Cheese", there are two mouse like characters. One is Sniff and the other is Scurry. Kelly seems to have those type of instincts.

- Divesting possible ownership and management options to an outside company. Just playing with options.

- For our internal team, we have been talking about a price of $1,000 per percent of adilas. That is about 1/100 of its actual value. On the open market, 1% would be somewhere between $50,000 to $100,000 at a $10 million dollar valuation.

- Steve was mentioning options for an operating company, a holding company, a management company, and maybe a retirement company. Just talking possible options, down the road.

- There seems to be a huge gap between sales and demos. If we get the demo and get to talk to people and show them what we have, we shine, and they want it. If we can't make it that far, it doesn't go very fast. Kinda interesting but logical.

- We are trying to stir the pot on the sales side of things. We talked about doing a sales sprint, daily sales standup meeting, and getting some of our guys really going and focused there. We really want to manage it properly as well. It is one thing to say go, it is another thing to have a plan, accountability, and be able to measure efforts. We really want to lean on the manage it properly type level.

- As far as sales and travel. We were talking that if they log their miles, we could pay $0.25 per mile. That covers gas and some light wear and tear on the vechiles. We would have them log those miles inside of adilas. Ideally, we would tie that into a general budget for what they are charging us or what we are budgeting for their help.

- We would like our salespeople to stay as local as possible so we don't burn up tons of travel costs. This is at least true for getting started out and getting things up and running.

- One of the goals would be to help the guys and gals be more accountable. Along with that, dealing with sales, we need them to log the contacts, touches, and daily standup meetings. Ideally, we want to record these notes as real-time as possible, while they are fresh in your minds.

- Sales is a game of numbers. The numbers should tell the story.

- I'm going to reach out to Shawn and get his instructions for his sales and contacts that need to be logged into adilas, in the CRM (customer relationship management) section of the site. See attached.

- Both Steve and Sean would be the main contacts for the sales guys. The main adilas morning meeting would have a small standup for sales everyday.

- For me, keep pushing out gift cards as we get them - perks for the guys and gals.

- Steve and I went over some percentages and who was going to be selling what percentages. We made a list on a spreadsheet. Our initial internal offering is going to be 5% from Steve and 5% from Brandon. These will be sales made to us as individuals - checks made out to Brandon or to Steve vs adilas llc. We will come up with a promissory note of sorts to document the sales of those percentages.

- There is huge value in getting in there, out there, doing it and learning from your mistakes and successes. We build and break, we build and break. Don't overthink it! Just keep going!

- When we present our offer to the guys and gals, Steve wants it to be pretty simple. This is the deal. If you want to play, great. If not, here are the options. Keep it as simple as possible.

- In closing, Steve was making some comments on having sufficient money to play and make other plans. Hinting at some other fun things to come... It just keeps going!

Recording notes, doing emails, and making some follow-ups. General to do list stuff.

Marisa and Sean were on the morning meeting. Marisa wanted to get some information on the PO line item rounding project and how that affected recipe/builds and internal build PO's. We went through a number of scenarios, and I showed her and Sean what the new force to $0 buttons and the line item rounding function does. We talked, drew some flow and training things (online meeting and drawing tools), and spent a good 25 minutes going over all of the ins and outs of that feature.

Next, I asked both Marisa and Sean if they had heard anything about the possible switch to a multi member LLC. Both of them said no, so we went into a good 45-minute crash course. We covered K-1's, 1099's, W-2's, etc. Lots of other ideas and concepts, dealing with our move to a multi member LLC with more owners and splitting up some percentages. I was having fun explaining things and I hope that they were enjoying it as well. We were looking at reports, getting numbers, drawing, linking things together and hopefully making sense. Anyways, good meeting and we went over a lot of ground and territory. When we finished, Chuck had joined us as well.

Chuck joined Sean and Marisa on the last little bit of the other meeting. We were going over financials, accounts payable, and accounts receivable. Lots of fun showing numbers and some of their trends. Lots of drawing on the screen.

Both Sean and Marisa had to bail out and so just Chuck and I kept going. We switched gears and talked about the add/edit media/content pages that Chuck is working on (small page level facelift on certain pages). We also briefly talked about maybe using a JS framework (JavaScript) for the next version of adilas. Eventually, we really want to allocate some time, funds, energy, and resources to work on the fracture project. We are hoping that that could be part of our plans going forward. Even if it is a little bit here and there, we would take it and run with it. One of our first main goals is to create a plan and then be able to pitch the pitch. No new code, just mock-ups, requirements, prototypes, and proof of concept stuff. We really want a great plan and then to be able to do and build what we are hoping and dreaming about.

Along those same lines, Chuck was talking about making sure that our application has multiple layers. The database level (dao's - database access objects), the middle layer (business logic, models, and services - object oriented pieces), we then need an interchangeable display or show level (visual wrapper, themes, custom, or even white label options). If we build it out that way, the 2 lower levels could be almost untouched, even if we had to redo the upper or display level. Sometimes that is called the view level. It goes deeper than this, but an older acronym is MVC (model, view, controller). There are more modern versions of that now, but that is all that would come to my mind as I was recording this. Long story made short, keep the data, logic, and display levels as separate pieces and you are heading in a good direction.

Emails, tech support, and met up with both Sean and Wayne on the GoToMeeting session for a bit. Responding to emails and checking on a loan repayment (big check that cleared the bank today). So many little things to do. They take up tons of time.

Research and re-activation of the New Mexico Payroll

Recording notes, doing emails, and checking out some new code from one of our 3rd party solutions.

I woke up this morning dreaming about adilas and what value it brings to the table. I went downstairs to record a couple of thoughts and ended up staying down there for a quite a bit of time, just recording ideas as they came to me. I then took a small notepad of post-it notes upstairs and kept coming up with different ideas. These could be expanded upon, it was just a quick, record what thoughts are coming to your mind, type of thing. I had all of these little one-liners written on about 9 pages of post-it notes. Kinda funny.

- 20 years of experience

- 250 customers

- Working model

- Trained team

- Data like crazy - tons of it

- Usage patterns

- Able to handle multi-industries (business verticals)

- People use it - daily

- Success stories from some of our clients

- Database model and database schema (what rows, columns, tables, indexes, data types, records, values, etc.)

- Code repository (huge code base)

- 10 full versions with back-ups of each version (over time)

- Documentation (things written, recorded, and organized)

- Commercial product

- Developer's notebook - full story and all that we have learned

- Able to do custom out of the box

- All of the custom code (as an asset)

- Plans for fracture (upcoming and future project)

- Established billing and revenue

- R&D and prototyping

- Graphics, visuals, and other artwork (even sketches)

- Presentation gallery - Full presentation ready gallery for business functions, attributes, key players, and core concepts

- Concepts - these are worth more than our code

- Pioneering paths and ideas

- Over 6.5 million in sales

- Willing to push the limits and try new things

- We know the pit falls, the costs, the good, and the bad - we've been playing in this arena for quite some time

- No one else is doing what we are doing and how we do it. Our approach to bring operations and accounting together is unique.

- Our story is fully recorded

- Reoccurring model and reoccurring revenue

- Support a team of 15-20 individuals and their families

- Thousands of users that use it every day

- Refinement and bug fixes

- We've built and maintained this application - we know what it takes

- We are doing it - following a dream

- Tons of video recordings and trainings

- Knowledge and experience

- Minimal debt

- Generating revenue right now

- Plans and vision for the future

- 40+ servers

- Ok with being who we are right now

- We don't have to have every client - Ok with serving those who like what we do

- Relationships with clients, vendors, 3rd party solutions, users, and team members

- Tons of intangibles

- Ecosystem

- 12 main players, 12 business functions, 12 core concepts

- Data assembly line

- 3D World building concepts

- The concepts are worth more than the code - We are one of millions of possible options vs everybody will go down the main primary path that leads to what we are doing and trying to do. If they (any other company or software system) choose to follow us, they will come down the core paths that we have found and are exploring. These are the core concepts that we are built on. There is tons of room down here (like exploring a giant cavern with tons of off shooting tunnels and shoots).

- We keep taking the next little step and keeping linking things together

- The depth of what we do and what we cover

- High-end software as a service (online SaaS model), we cover anything to do with operations and accounting, we have a standard package and can built out custom on top of that.

Marisa and Sean jumped on the meeting. We started out by talking about special driver license scanning options and possible state specific formats and options. Next we switched over and talked about a 3rd party solution and possible security issues. We came up with a couple of suggestions and Sean will relay those ideas back to the 3rd party folks.

Next we went through a number of scenarios on discount engine stuff, custom discounts for employees, and cost plus tax options for owners. We got deep into the discount engine and also using the advanced add/edit to cart feature. Pretty cool.

Tons of dynamic setting and setting up options for barcode quick carts and other speed and ease of use options and settings. Sometimes a new user may feel overwhelmed with too many settings. We can help them run their way without getting overwhelmed via a setup and deployment person on our side who helps guide them through the processes and sets things up for them, based on what they know or have been asked to do. Futuristically, we would love to have a series or wizard type walk-throughs or bigger global user types where we could quickly configure settings on a corporation, business industry level, and even a page level - based on known needs and patterns.

Cory has been on vacation for a week or so. She got back and a bunch of the folks on the morning meeting wanted to talk to her. She coordinated times to get back with Sean, Marisa, and John. After that we went over projects and progress reports. Lots of touching base on small happenings, projects, and updates. We decided to assign a few tasks to some of the developers who could help take things off of my plate.

We talked about state taxes, state payroll and withholdings. We have two new states that are needed. Sometimes, that takes time, research, and then ongoing maintenance (year after year). We talked about new clients and managing expectations. For our new clients, we need to figure out what they will be needing? We may need to pad the setup and activation fee to help with light customizations. Almost every client needs it, but they don't want to pay for that. We can't do it for free. We may need to add some of that flex coverage to the initial activation fee. Thinking about a fee of $1,500 for a brand new client and a smaller activation fee for existing clients that just need a new corporation or system. Something more like $500 vs $1,500 as we won't know what is really needed with a brand new client.

The last topic of the day was 3rd party solutions and some of the settings that we have and how they play in. Light talk about the API sockets and key connections that outside 3rd parties need to make. 

Recording notes from earlier meetings and brainstorming sessions. Recorded a number of quick list items for what brings value to our company. This is not an exhausted list, but a good start. I was already able to think of a bunch more.

Budget meeting with Steve, Shari O., Cory, and I. Most of the meeting was done using spreadsheets and Word document that we have been adding to for the ideas and concepts of the multi member LLC that we are trying to get fully setup.

- Steve and I talking about the cost of getting a client on the system. Often, they have huge demands, totally ridiculous. Often, there are even times that they have huge expectations, almost expecting perfectly wrapped, signed, sealed, and delivered products. Steve and I were talking about the expectations and ROI on those clients.

- Levels of activation and setting a price tag accordingly. Setting the expectations and assessing their (our clients) needs. Seeing how deep we need to go and what we are dealing with.

- As is or are we doing extras?

- Steve was reporting on talking with Eric and maybe letting him take a crack at doing sales. Cory has some small development projects for him as well.

- Doing a better assessment of what it will take for them (each new client) to be fully on and up and going. It may be a 5-10K dollar rollout vs a $500 activation.

- Differentiate between training, setup, deployment, customization, consulting, and tech support.

At the end of the meeting, Shari O. and I touched base on ecommerce terms and refund policies. We need to create a general page that covers different privacy policies, refund policies, and other terms and such for ecommerce. We have a client that needs that in place before the merchant processing company will release their merchant account. After that, Cory and I quickly touched base on some other projects that we are working on. I showed her a demo of the copy selected chart of accounts between corporations and we went over the next steps.

Emails, internal tech support stuff, and then back working on my projects. Working on the copy selected chart of accounts between corporations. In our terms, chart of accounts are expense types, deposit types, and balance sheet types.

Finished up the special copy between corporations for chart of accounts (expense types, deposit types, and balance sheet item types). Pushed the new file up to all servers and sent Cory an email as she is the one that needed this tool for a special migration project that she was helping out with.

Recording notes from Thursday and Friday. Just trying to stay caught up.

A bunch of the guys were checking in this morning. Eric needed some info and direction on a driver license scan project. Alan checked in on the enterprise level parts categories and category images. Chuck and I did a small code review and merged and pushed up a file for adding media/content (files). After that, John and I looked over some small payroll changes for states and allowing for timecards without fully allowing for full payroll options. Mostly a small work session this morning.

Cory and I jumped on and looked over a bunch of projects. John was still on and showed Cory progress on the state choices and new payroll messages. I took some time and showed Cory some of the features of the new copy select chart of accounts tool - copying things between corporations. We also looked at some upcoming projects. I'll be working on some verbage for refund policies, privacy policies, and other terms and conditions. We need to add these pieces to our ecommerce site. After that, my next major project will be planning out an MVP (minimal viable product) for client facing scheduling and booking.

Steve joined and he and Cory were going over a number of custom label and other projects. Steve and Cory were also talking about some merchant processing options. We have some required updates that are coming up and we don't have very many people using that feature. As a business decision, we may need to get with those folks and see if they are willing to transfer over to a different merchant account. The more you have, the more you have to maintain. We are looking to consolidate on some of those options and available features. Finally, we went over next steps for each of us and then bailed out to work on our own projects.

Recording notes from this morning and getting going on a new page for verbage on terms and conditions, privacy policy, and refund policies. Required for ecommerce stuff. Got the first round verbage done and posted online. Click here if you want to read the generic terms and policies. Sent some emails around to get some feedback.

When I joined, they were going over some sales stuff. Steve, Sean, and Cory were going over specific examples and how BioTrack calculates units and grams. Crazy stuff. I joined later today. I had a dentist appointment.

As the meeting progressed, we were talking about client acquisition costs and how to manage expectations. We are really trying to get a good ROI (return on investment) from what we are doing. We can't charge for all of it and that is where it hurts a bit. It gets really crazy if there are a lot of unknowns or unfamiliar territory. An example in my mind is I start saying "I'm not sure" if I see too many revolving doors (variables) and the maintenance load is somewhat unknown (they keep changing things). Those are the scary ones.

With some of the BioTrack stuff, we are seeing lots of crazy tracking needs. Some per item, per patient/client, and some per tax category. It sounded like possible crazy taxing stuff based on items and customer types. Not impossible, but for sure deep and complicated.

These talks about crazy custom code levels lead into some talks about charging for custom work or what is expected of the software. That lead to talks about clients covering travel time and other deployment and reimbursement costs. Each door we open has a number of new options, possibilities and variables. We also talked about costs of deploying in different states and special code that is required per state. For example: state level payroll for all 50 states or driver license scanning and auto populating for customer searches. Each state may be very different. If we add them, we then have to support and maintain those things as well. It's not just a one-time cost, it keeps going, as long as we have clients in those states, using our products. You have to look down the road a little bit.

Wayne jumped on and was reporting on a number of server issues and projects. Just this morning, he did a clean-up on the data 3 database and removed some older data (we call them skeletons - dead data). They will be sweeping the floor on the data 20 box next week. Just some backend clean-up and maintenance. Wayne also touched base on a number of other projects that were on his list. Good report.

After the server meeting, Steve had some questions on the bulk printing of cart and PO labels. We got into the logic and other settings. Looking over code.

Cory, Steve, and I talking about merchant processing with both Elavon and USAePay gateways. Trying to figure out the best approach for those two solutions. We already have active code and implementations with both gateways, we are just trying to figure out which one to sort of lean on and favor (business decisions). Both seem pretty good, just weighing options.

Steve, Sean, and I jumped on a small fix it project for the complex labels (QR code and normal barcodes). We got in there and made a number of changes and pushed up some files. As we were talking about labels, we brought up Calvin's dynamic labels and the need to get back in there and work out kinks from his dynamic label builder. Marisa joined and had some label questions. That shot us over to the barcode custom labels and using the complex label generator to store sub packages, fixed quantities, and fixed costs, all tied to a single barcode value. Kind of interesting that the custom labels came up multiple times this morning alone. Pretty crazy!

Somewhat of a mix of different things. Reviewing and planning an MVP (minimal viable product) for the client facing scheduling app for ecommerce. Doing some research and reading inside of pass elements of time in the developer's notebook. One of the items was some new time template settings on element of time # 8004. The other was some notes on the bike shuttle scheduling for a client on element of time # 8137.

Sending some emails over to the merchant processing folks to get some approvals on terms and policies for a client. This was required for underwriting for their merchant account.

Jumped on a GoToMeeting with Steve to go over some code for bulk printing custom labels. Steve also reported that he spoke more with Alan on the options for multi member LLC and the adilas trust options for a new corporation and entity structure. Good stuff.

I then jumped back into the research and planning for the client facing scheduling stuff for ecommerce and elements of time.

Recording notes from today and this morning. Reviewing notes, scans, and plans.

It was Steve's day off today, but he was still in there pushing on things. He was checking in and uploading new custom labels to data 16. After that, he and Dustin were going over some new CSS (display) changes for some of the pages. We helped Dusitn figure out some stuff with the CSS and data table switches. Cory and Shari O. were touching base on some small tech support issues. Eric joined and was reporting in on the driver license scanning project. He is looking into our code and comparing it to a 2D barcode library that he found on git hub.

Eric and I ended up talking about other API sockets and functionality. He was saying that he likes to categorize things as - must haves and nice to haves. I thought that it was a fun way of saying needs and wants. Good stuff. Spent the rest of the time working on emails.

Chuck and I were talking about using setup wizards and easy setup steps to virtually walk people through complex or involved processes. We covered a bunch of different topics today. One of them was MVC or model view controllers and how splitting things into different levels allows for more modular code. The thing that changes the most is the view model (display). The other pieces tend to stay fairly similar without huge changes between versions. Chuck would like me to speak with his wife about some of those different levels and some tips and tricks on keeping them separate. She worked with a client that does government work and they were setup with really good deafferentation between data layers, business logic layers, and view or display layers. She is also familiar with a number of different frameworks and possible options there.

As we were talking, Chuck said that one of his goals is going to be working on layouts, use of whitespace, and number of clicks to get something done and finished. Those sounded like good goals to look into and work on for adilas projects. Next, we chatted about navigation, layouts, and the concept of an artist with a pallet and being able to change the layout and control your space (work environment). Sometimes the word space is too deep for people to grasp. They think of stars and constellations. We are currently talking more about personal space and configuring your own environment or working space (homepages, nav options, preferences, dashboards, etc.). Chuck would love to help develop some really cool dashboards and such. That would be awesome.

More talk about wizards and easy bulk setup options. We would love to configure some almost hands-free setup options. Think of what a cost saving this would be. Basically, if we could make the setup easier, we could eliminate some large costs and time savings by letting the users set it up themselves. That is still a long way out, but a great goal. Along those lines, we were talking about how both settings and permissions really need to dictate displays, options, and work spaces. If we did it well enough, we could even offer a free trial or something along those lines. Right now, it takes too much to setup it all up and get someone trained. We can't do it for free because it takes someone who know the system to setup it up, configure it, and get the people trained on it.

If we could get things done in bulk or through simple handholding wizards, that would really help the process. Those handrails or wizards turn mountains into smaller icebergs (perception of what is there to take in or acknowledge). We talked about some possible mini apps or standalone modules for the current adilas platform. Timeclocks, timecards, uers, payroll, expense tracking, point of sale, CRM (customer relationship management), ecommerce, etc. All of the main 12 business functions. Fun little meeting and some good ideas. We would like to include and even start working on the fracture project with some of these ideas. That is and has been a big goal and driving force for what we are doing. What is the next step and how can we get there?

Meeting with Cory, Eric, and I to go over the reoccurring expense/receipts and how they play with balance sheet items. I was showing my screen and drawing and talking with Eric. We went over the basics and then went in and did an actual example. Cory had to leave, so she and Eric switched over to a project dealing with an outside 3rd party solution and a full API socket setup. They will be starting from scratch (basically) and building from there. We have an API socket and API endpoints and they have an API socket with endpoints. We just need to figure out who is pushing and who is pulling data. Somewhat of a discovery process and taking things step by step with an end goal in mind.

After Cory left, Eric and I jumped in deeper and got into specifics on the bump up/down project for expenses and balance sheet items. We looked at code, made suggestions, and talked about a rough plan of attack. Eric should have some direction and will report back if he gets stuck. We are pretty good at doing just in time project management and getting things assigned out to our guys and gals. Good meeting.

Checking emails and then on a phone call with Drew from the High Valley Bike Shuttle corporation. We chatted and touched base. We also setup some times to do some training and progress reports. Here is our rough plan.

- Get in there and setup categories, items, images, descriptions, flex grid tie-ins, time templates, and general processes.

- Do some training on the general processes and get them using the system with current tools - somewhat of the manual or non-automated processes. We will record the training and make sure that they are good to go. This will get them going.

- We will keep building on the automation and client facing scheduling portions that are needed. Release things as soon as we are able as an MVP deployment (minimal viable product).

Emails, client logs, and scheduling follow-ups. Recording notes from earlier today. Tons of notes. The ball keeps rolling! What a game!

Steve and Sean were talking about custom gram controllers and ways to setup certain settings to make it super flexible. As they were talking, I was thinking, yes, it can do it but we will need to train our people on how to use that. Often with complexity comes the need for more education. They seem to go hand in hand.

I was reviewing notes from a meeting with an unemployment auditor about employees and general employer stuff. We are trying to make some changes in how our business is structured. Good stuff, but also a challenge.

Cory and Steve were going over 3rd party solutions and dealing with them. It is kind of a bitter sweet relationship. They keep popping up all over the place and some of them expect us to virtually carry them. It can be a challenge.

On a different note, we keep circling back around and talking about Stripe and ways to possibly integrate with them. They seem to be a very good and valid merchant solution. Marisa and Sean were going over Metrc invoice syncing and tips and tricks to make things sync up.

After that, Chuck and I worked on media/content files and code review. We tweaked a few files and pushed them up to the adilas content server. Chuck and I started chatting about rules for 1099's and sub-contractors. We reviewed some of my notes from the meeting with the unemployment auditor. Just for fun, Chuck was say, why don't you move where the business is based out of to a more tax friendly state. I never would have thought of that. We don't plan on moving, but it was an interesting angle. Almost a business decision based on tax friendliness - kinda interesting.

Emails and then hopped on a GoToMeeting with Bryan. He wanted to look at some ecommerce gram controllers. We got it as far as we could. I recommended that he talk to Steve about some of the new settings. We jumped off and then jumped back on again for another issue. We needed to get Bryan's local environment up to speed and updated with master code repository stuff. Crazy to see how much changes, even in just a couple of weeks to a month. Every day something is different. It moves that fast sometimes.

I made some calls to a funding company, just checking on final payoffs and wrapping things up. It feels good to get all of that stuff done and fully taken care of.

Planning and researching some changes that are needed on the use limited flex grid tie-in pages. Currently only Beaver Mountain Ski School uses the special limited flex grid pages. We would like to roll that out to all clients and let them configure things and how things get setup and shown. Even though in the background it is doing flips and twists, make it look super simple on the frontend. It makes a difference. Imagine around 40+ fields to handle a single flex grid tie-in. What if you could get that down to 4 or 5 key fields. Wouldn't that look so much simpler. Anyways, we have it, but it fully custom and only tied to one corporation. We are looking at rolling that out to all clients. It will be pretty cool.

Meeting with Cory, Steve, and I to go over budgets and corporate structure changes. Shari O. wasn't able to make the first part of the meeting so we recorded it. Brandon has the video footage at his house on his computer. We didn't want to post it as it contains some budget type info. Anyways, we went through the meeting and I was taking some notes, we were drawing and going through some scenarios. Shari O. was able to join us about half way through the meeting. I sent the meeting notes around after we finished. The meeting notes are mostly about the corporate structure changes that we are trying to make. See attached.

Emails and playing with numbers for a retirement type program for adilas, co-founders, and co-owners. I was asking my wife and kids for some ideas and suggestions. I then was playing with some small calculations and seeing how things would look and/or work out. I also did some research and reading up on ternary operators in JavaScript. This is a shortcut for setting a single variable with either a true or false type logic (normal if statement stuff) without writing out the full if statement and setting the variables in the main if or the else clause.

Here is a sample: I got this online on one of the sites that I was looking at and it made sense to me. "variable = (condition) ? true-value : false-value;"

Working on the limited flex grid tie-ins page and section. Finished up the advanced settings for the flex grid fields. Looking at the add limited flex grid page and the normal add/edit or fully expanded add/edit flex grid page. Going though both pages from top to bottom in order to compare what they do and see if we could combine any code or logic. Pretty deep dive. I will add my notes and scans to this element of time. Looking to build out the add limited flex grid tie-ins to make it a global tool. Currently, only one company can use it as it was developed as custom code, back in 2016-2017. It has a lot of power and really makes the custom flex grid fields seem much more digestible and easier to manage. See attached.

Building out the ability to look-up settings and be able to flip flop between the add limited flex grid tie-ins and the fully expanded add/edit flex grid tie-ins page. Started coding some of the elements of time pages to allow for the flexible choice of doing limited or fully expanded modes in add mode. Making progress.

Recording notes from meeting and work sessions from the past couple of days. Sometimes it is fun to go back and review your progress and see what you are accomplishing. It all adds up over time.

Steve and Sean were going over tired pricing out in ecommerce and how to set things up. I got to show a small demo of my progress on the limited flex grid stuff. Steve and Sean jumped back on going over some other new things that have come up and/or being developed. Both Sean and Marisa are helping with training and deployment and are doing a great job. As they are out in the field, they keep bringing things back that need a little bit of loving, small tweaks, and other ideas and feedback. Good stuff! That information is super valuable and even critical to our survival and success.

The more we do, the more we are trying to improve our internal connections. Steve and I were talking about ideas for an operating agreement and some sort of option for doing a retirement or special savings account of sorts. I scanned some scratch paper and I was asking him for some ideas and feedback. He recommended that the column for quality could be called position or position level. How critical or important is the role that the person is playing in the mix? We couldn't think of a good name. We were thinking value, quality, rating, or level. I like position level better. Just playing with ideas.

On a meeting with Steve and Cory. Talking about projects for Eric. Steve will be meeting with him today to go over projects and ideas for ownership in the adilas multi member LLC corporation. Light report on what Dustin is working on. Cory had a list of questions, and we spent some time going over those pieces and questions. Looking into a part look-up problem for a client. The problem ended up being a huge part number (lots of alpha/numeric and special characters) and whether or not it was being URL encoded for certain actions or functions. That little fix will take some more time and we could end up flipping things to an id look-up vs using the text-based searches that exist right now. It's only for a certain method, but it gets used 20+ times.

Spent some time with John looking into deep nested loops and sub filtering data. This is on the discount engine project. Lots of string manipulation and escaping certain strings and characters. Once again, rouge and random client data. It is a challenge to allow flexibility and still keep a level of control on what a user can enter into certain fields, lists, and values. All part of the game.

Working on an inventory look-up project to help avoid bad user input and data. Switched a key look-up from a user-defined text look-up into a more controlled id look-up. We had to leave the flexible look-up for certain things and create a switch that allowed for both text and id look-ups on the same method. We've done this tons of times, we just had to do it and then follow all of the connecting paths and figure out which value to pass and base things off of. Cascaded the changes, tested, merged in code, and pushed it up to all of the servers.

Emails, reading up on a payroll audit and ideas on creating a MMLLC (multi member LLC) for the adilas company. Back on the limited flex grid project and cascading some of those pieces and changes around the site.

Morning sales meeting. They were checking in on email campaigns. They were looking at getting better calls and follow-ups. Steve was saying that we keep testing things, going through phases, and trying different things. Basically, small or little experiments on sales and promotions.

Chuck and I talking about 3D printers. Chuck and I going over the media/content multi upload page.

Cory, Wayne, John, and I on the server meeting. John was reporting on the discount engine and his progress there. He has a visual model that he was showing us for the demo. Wayne has been cleaning up some of the database servers and actual databases (data on the servers). Cory and Marisa are trying to make us look good by working on better communication stuff. We also were touching base on other server-based projects. Small meeting.

Working with Chuck to get the multi file upload page live and online. Added the spinning loader gif to the page to help show activity. Pushed up files live on all servers.

Working with Bryan on some try, catches, if statements, and API socket payments. Emails and other to do list stuff.

Research and planning what is next with Drew and the High Valley Bike Shuttle. Called drew and setup some training for Friday at 2 pm. Going over the plan with him and talking about options.

Back on the limited flex grid project and cascading those new links and settings to all 12 of the main system or application players. Part of the process of distributing that code to where it needs to go.

Up early and couldn't sleep. Spent the time brainstorming on scenarios, ideas, and trying to push things forward with adilas switching from just Steve and I being owners into a bigger MMLLC (multi member LLC). These are just ideas - not polished or complete, but at least a start. See attached for some scans. As a funny note, I woke up and had a few ideas floating around in my head, I started recording them and pretty soon, a huge tidal wave of ideas started breaking out. My original goal was just to record a couple of things. Two hours later, I went back to bed. Kinda funny.

Multiple folks checking in this morning. Cory had some questions about payables and a company that reported that one of the payables wasn't showing up in their system. We briefly looked into it. Showed Sean and Marisa some of the progress on the limited flex grid tie-in stuff. Small mini demo for them. Reviewing notes on the adilas trust and ideas for the changes in company structure.

Chuck and I pushed up some changes. We then talked about investments. Lots of talk about annual returns on accounts, actively managing the monies and possible investments. Basically, what are the benefits of having another special account for retirement or savings? We talked about possible withdrawal rules such as any amount that is greater than or equal to $1,000. Basically, if we had another account, if you have $20K in that account, you could grab what you wanted, but you could do something like $100. It would have to be greater than or equal to $1,000 minimum ($amount to withdrawal needs to be >= $1,000).

If there was a bunch of money, you could do all kinds of stuff. Our current goal is to create and capture small drops based off of the reoccurring revenue model. We could open up other options later on down the road. We also talked about who may want to help manage and help monitor this account or business entity.

Looking into a data issue on an expense/receipt on data 20 that wasn't showing up in the correct accounts payables section. It ended up being a vendor data problem. Got it fixed. Back working more on the limited flex grid tie-ins and distributing the links to all of the main application player groups (12 main player groups - deposits, invoices, PO's, expense/receipts, balance sheet items, stock/units, customers, vendors, employee/users, parts, elements of time, and quotes). Lots of local testing and coding. Going down the list, started with deposits and going from there.

More work on cascading the limited flex grid tie-ins to other system player groups. Worked on vendors, employee/users, parts, and quotes.

Finished up and merged in code for the limited flex grid tie-in stuff. Close to 50 pages that got altered and updated. Pushed up files to all servers.

Small demo about the new global features for limited flex grid for both Steve and Sean. This feature used to be exclusive for the Ski School up at Beaver Mountain. We pushed it out to the whole adilas system earlier this week. It should be a great tool for those who are doing combos with flex grid tie-ins. Steve asked about the plan for the bike shuttle company. I told him that we are planning on doing 3 basic steps - prep, train on existing pieces, work on automation.

Hope (Experanza) reported in and wanted to do more marketing with a specific company. She has good connections in her industry. She and Sean are trying to get some advertising into magazines and in front of different parties. As a small side note, it was fun to listen in from the background. You could tell that she was a power user of adilas and those people tend to be our best salespeople or representatives. They have lived it.

Just for fun, Steve would love to go back through and figure out who else we could grab that were adilas power users. There is an untapped resource there - who has the skills and who has done what over time? Another idea was, if we can get the adilas cafe all setup, these power users could offer their own skills and services. That would be totally awesome! Also, if you take a power user and then teach them something else that they don't know (different section of adilas), they tend to pick things up really fast. They are able to build off of a good knowledge and skill base. They eat it up and see the potential.

We talked about other possible marketing stuff, events, swag, banners, the works. Steve and Sean were talking about options and marketing efforts.

Next, we switched gears and Steve and I started working on pulling in custom labels into auto print from the cart. We kinda got lost and couldn't figure it out until we saw that his browser (just a setting) was blocking what we were trying to do. We got it figured out but it had us stumped for a little while. After that, we talked briefly about the MMLLC (multi member LLC) stuff and where we are heading. We also talked about the upcoming scheduling stuff that is coming down the pipeline. As it gets developed, we will need to make sure and get the training and education stuff out there to help our users and trainers.

Going over numbers, calculations, scenarios, and ideas for buying and selling internal ownership percentages of adilas. Trying to get our ducks in a line.

A number of different activities. Watched some videos online about retirement plans, options, and rules. Just trying to get familiar with options for altering the adilas business structure into more of a multi member LLC with multiple owners. Prep work for the bike shuttle company. Planning and working on pieces, doing images, descriptions, ecommerce stuff, and helping to setup the system. Some small code tweaks to help with flow on some of the pages.

Small tweak to the photo and scan upload options inside of adilas. We upped the quality and made some code changes to help with display. Pushed up the new files and did some live testing with some ecommerce images for the bike shuttle company.

Prep work for the training session with High Valley Bike shuttle later today. Working on customer settings, setting up limited flex grid settings, and light ecommerce prep work. I came up with a number of scenarios, some planning, and light code tweaks to help with flow. I also started into some custom work for them. I'm excited to get them some training.

Demo and training session with High Valley Bike Shuttle. They had Drew, Jim, and Lanette on the call. We had Chuck, Sean, Marisa, and me from adilas. Good call. It went about an hour and 45 minutes. Lots of information to cover. We did record most of it, see attached if you are interested in seeing where things are at currently. Lots of other pieces are planned and in the development stages. Once the meeting ended, I wrote down a couple of ideas and pushed up the video. 

Recording notes from last week. What a variety, from last week. We did stuff for corporation and business structure stuff, brainstorming, custom development, bug fixes, meetings, and advancing the ball in other ways. Busy week.

Steve and Sean were on talking about possible advertising in trade magazines and possible budgets and marketing decisions. Sean and Steve were also talking about how Sean had done a lot of marketing previously (back in college and what he was going into - his major). They talked about changes and other possible options. Steve and I touched base on the demo that I did on Friday. We talked about the limited flex grid and upcoming client facing scheduling. Small report on where we are at there.

Eric joined and he and Steve were talking about options for the 2D barcode and digital scans of customer driver licenses. Eric wanted to know which way to head and where we are going. We talked about bigger options and chasing bigger fish but ended up coming back to an MVP (minimal viable product) type approach and direction. That's all that we can afford at this time.

Recording notes from last week, busy week. Fixing a small image width issue on big photo gallery pages and photo/scan drill-down links. Emails and other small catch-up stuff.

Emails and updating an active company and corporation list for Shari O. Switched over to working on some custom code and working on bulk tools for dealing with flex grid tie-ins. Coding and working through things.

Both Steve and Cory were on the meeting. Touching base on projects. I gave an update on my projects and Steve gave us an update on his projects. Light budget talks. We talked about having to front load the initial setup, configuration, and any analysis of what is needed. We then got into client expectations and trying to get those expectations under control. Almost a conditional setup and need for education or step-by-step setup stuff. Ideally the goal is helping to automate things and coming up with wizards, handrails, and step-by-step setup processes.

Cory had some questions on MMLLC and percentage stuff. Checking on invoices and A/R's (account receivables) and getting payments. The subject switched over to pain and how that helps to lead and guide decisions. If we are calling ourselves a custom software solution and then charging accordingly. We need to play accordingly.

Spent the last 15-20 minutes paying bills and doing clean-up from the day.

Steve and Sean were talking about ecommerce and what is needed to keep systems going. Lots of moving pieces. After that, it switched over to a sales meeting. Steve was asking questions about some dealerships and recent contacts that Sean and Marisa were making. We talked about how much custom code is needed per client or per industry vertical.

We got into a conversation about the client facing scheduler and how cool it will be, but also how much code it will take to make it fully functional. The subject then flipped over to automation, wizards, settings, training, and education needs. As things get more complex, there needs to be ways of letting people know what is needed and what needs to be done. If the education is not there, it actually makes it even harder to figure it out. We talked more about ways of helping to speed up the training and onboarding processes. We need a way for our client to figure things out and/or be educated on what is possible and what is needed. Steve was mentioning that we need a balance between sales and new development.

As a side note, in some of our design prototypes for the fracture project, we were working on a better UI/UX as well as a thing called education mode (toggle on/off for extra help and information). The goal was to make it available but hidden. If it was needed, it was there. If it wasn't needed, it was hidden but still avaiable. Also, a good UI/UX will help eliminate some of the education stuff (not all of it).

The final topic of the morning meeting was dealing with advertising and pushing that forward. We also talked about having the best team we have ever had. Good stuff!

Wayne, Cory, John, and I on the server meeting. Wayne was reporting on some progress on different things. Small talks about data 16 and some possible memory issues. Cory and Wayne were talking about some servers and data connections. We will continue to keep scheduling database clean-ups. The next one on the list is a database clean-up for the data 0 box. Cory and John spent some time going over projects.

Cory had to bail out and just Wayne and John were left on the meeting with me. Wayne was showing me the new corp-wide settings and changes that he is making there. We have a huge database table that has over 400+ columns or fields. The goal with his new setting service is to make that table much smaller and build out vertically vs horizontally, meaning adding in new rows with variable/value pairs, vs new columns that make the table huge. He is making great progress and seems to be almost halfway through the current process.

Towards the end of the meeting, we were shooting the bull and talking about a bunch of random things. Wayne likes to play around with hacker type tools. We talked about ways that his little hobby of hacking could actually help us make our stuff more stable, by knowing the common vulnerabilities and gotchas.

Chuck was on the meeting asking about calendars and goals and vision for elements of time. Cory and Bryan jumped on and we checked on a bug with some code that got pushed up earlier today. We got it fixed. I was really happy that we had such a quick reaction and were able to make the changes and push up the fix so quickly.

Cascading records and database tables from data 0 to all other data servers. We call this updating tables. There are about 10 tables that we update per server, to keep them synced up with the ones on data 0. Currently that is a manual process. That process took over an hour and a half. After that, I merged in some files and pushed them up to all serves. This was some new code for a 3rd party solution. Eric has been working on an integration with a company called Weedmaps. I don't really know much more than that.

Admin budget meeting. To start out with, we had all of us on the meeting (Steve, Cory, Shari O., and myself). Steve was having internet issues and ended up dropping off of the meeting. The other three of us kept plowing ahead. After the meeting, I sent notes and budgets to all of the main admin team. I have copies of those files here at my house, if we need them.

Sean and I looking into the older code from the Leafly integration (back in 2019) done by Will Hudson. We were somewhat going through some of the pieces and virtually reverse engineering what we saw (looking at existing code and trying to figure it out). Basically, what was built by Will and what did it do?

John showed me some stuff on his discount engine. We were looking into a CSS (display) issue. We decided to wait for Chuck who would be popping in on the next meeting.

Just recording an idea, but what if we had Bryan help us out with some training and education stuff. We are really lacking there. Bryan could build it and then we could have Chuck make it look nice. Basically, Bryan could help with content and Chuck could help with presentation. There is a huge need for training, flow, processes, SOP's, etc. Also, just another idea... What if we put Bryan on a project to see if we could write a grant for building out fracture and where we would like to take it (huge future project in adilas and revamping the whole system). That might have some merit. We could really use some major funding to push that whole project forward. I know that Bryan has written other articles and/or research papers. Just a thought.

If needed, we could use the adilas developer's notebook to do more research on the whole fracture project. Lots of notes and ideas have been posted and pushed up to the developer's notebook over time. A great resource. A lot of it ties in with the adilas cafe and community that we are trying to build. We also have tons of R&D (research and development) on new UI/UX stuff from Jonathan Wells. Lots of great little ideas and such. Good starting point.

Chuck and I going over booking and scheduling ideas and things. He has some Pinterest galleries that have some cool calendar and time view widgets. He is somewhat collecting some samples and organizing a small gallery out on Pinterest to help with some research on date pickers, calendar views, time views, scheduling widgets, and calendar stuff. We talked about a new dynamic date picker that he would be willing to build. If yes, we could cascade it throughout the whole adilas site. That would be really cool. We already have a date picker on some of the pages, but not on all of them (there are a ton of pages that could use some loving).

Emails, texts, and recording notes from yesterday and today. Trying to keep up with everything. Every day is different and brings new surprises, challenges, and breakthroughs. Good stuff.

Working on the bulk add flex grid page for the High Valley Bike Shuttle. Lots of custom work. Merged in all that I have done to keep showing progress. It is looking good. Here are a few things that it does.

- By default it shows two records. There is a form at the top that you can change that number from 2 to whatever you need. Once submitted, it will show that many new records. The limit is 100 per page.

- The top row has special JavaScript that helps cascade the current value to all other records (cascading from top down). If any other record needs to be changed, no problem. It is just the top row of data that has the magic cascade down feature.

- If they are filling out the guest's name field, if they use the key word "Guest" it will add a number to the end of each value. Say I wanted three and I put in the key word "Guest". It would show Guest 1, Guest 2, Guest 3.

- It has a sub invoice field, all 30 possible custom fields (based off of the limited settings), and all of the general fields for flex grid. All of them work and have the top level magic cascade downward functions built-in. See this help file for more info on flex grid tie-in fields.

All new files have been pushed up to the data 0 server.

Steve and Sean were going over things when I joined. Sean was reporting on his research on Leafly and Steve was talking sales and prospects with Sean. Both Steve and Sean had to leave and that left just John and I on the meeting. We went over projects, the discount engine, and budgets. Everybody is wishing that we didn't have to worry about budgets and could just build to our hearts content. I often wish the same thing. Sometimes life just has other plans.

I was on the phone and then doing some emails with Newtek. They are working on some merchant accounts for some of our clients. It has been a much harder process than I remember. They keep asking for things, we show them, and they ask for something else. I want to get on a meeting with them so that I can ask my questions vs random email chains and small phone calls. This merchant account is for one of our clients, it isn't even for us. We have others that will need to go through the same process. We've had ours in place since 2009 ish. I'm just venting a little bit.

Emails, paying bills, and back working on the bulk flex grid tie-in tools for the bike shuttle company. Mostly I was doing some prep for submitting the bulk add form for the bulk limited flex grid stuff. Also worked on some new help files.

Talking with Steve over a GoToMeeting session. We went over and covered a number of topics. We started out talking about merchant processing options. We already have a relationship with USAePay. However, we are also looking at NMI, Stripe, and Elavon. As we get more or new clients, they will have more and more merchant processing needs. Trying to stay ahead of the game.

Steve and I were also talking about the different mix of team players that we have. We got into talking about religion, beliefs, controversial topics, cannabis, non-cannabis, developers, sales, and how to balance all of those pieces. Our mix almost creates an interesting culture and a specific need (who else if needed). We don't have very many that can crisscross either based on the beliefs (religion and feelings), which topics that they are assigned to work on, and whether or not they will reach out and talk to people (sales). We have some of our developers that will only work on certain projects (me included) and other ones who don't do sales (they only want to do code). Because the team is so small, it can be a real challenge.

There has to be a balance and we are trying to find and maintain that balance. It feels elusive and slippery at times. Steve was saying or relating what we do to an analogy of people sitting around the fire. Everybody likes the fire, but nobody wants to go out and get more firewood. He really wants to push harder on the sales side of things. Basically, it feels like we are a little bit heavy on the developer's side of things.

Towards the end, we were talking about the ability to take basic building blocks and stack them into small combo packages to get awesome outcomes. It's not that the smaller pieces are super cool, all by themselves, it is just, when they get stacked together, they really become something cool. Taking the basics and stacking them together. Steve is really trying hard to work on bringing in custom controls and dynamics to all of his projects. That is awesome.

Here are some other notes that I took during the meeting. I started out jotting things down on paper, but was getting behind, so I started typing things so that Steve could see where we were and what we had covered. These notes below are from the typed stuff.

- People's willingness to play in different industries - cannabis and non-cannabis

- Personalities and where they feel comfortable and want to spend their time - development (writing code) and sales (getting out, networking, pitching things, and talking to people)

- We may need to cut back dev and push more on sales

- Analogy of cutting firewood vs sitting by the fire

- Balance and being able to keep going

- Have cory focus on clients who want improvements and are willing to make investments - client funded projects

- Wasting money on sales meetings and emails campaigns

- People who are great at what they do but they can't do all of the things to keep the balance - This ends up being a vacuum or a money pit because we have to pay for all of the one-sided stuff

- In cannabis - we can get some of the new accounts, but it is hard to make someone switch

- We are up against a lot of money - big money investments

- We want to stay as small as possible and stay nimble

- Paying someone for sales - somewhat of a headhunter

- Steve would like to see 5-10 new systems per month

- 3rd party solutions - there is a need there and they do help us float down the river

- Maybe looking at pair programming

- Talking about trust levels

- Shari O. has been the back-up for server resets

- Help is only helping if they are helping - we can't hold up a drowning swimmer

- We have had some peace and quiet with letting some of our guys/gals go... We need to get back there

- On the MMLLC - some of our team is worried about liability

- A couple of phases - anybody who wants to stay, needs to jump on the wagon

- Minimum is at 1/10th of a percent

- Don't worry about all of the details

- Get those set who want to and then go forward with the others

- Sort of a faith-based venture - just start, if you don't like it, we'll buy it back (talking about the company restructure stuff - buying and selling percentages)

- We have enjoyed working with Dustin

- Bryan has been a great work horse

- Steve would like to check in with industrial supply places and see what we can do there - find a vertical and then service it

- Maybe try some email campaigns for some of these smaller verticals

- Trying to expose more and more of the system - fewer black boxes and make it available for everyone

- Getting to a stable location (lifestyle)

Clean-up from the day. Also planning and writing a pretty long email proposal for moving the company into an expanded MMLLC for adilas. The email basically covered where we are heading and how things are going to work going forward. Dealing with percentages, ownership, switching from 1099 and independent sub-contractors to co-owners and getting K-1's at the end of the year. The email covered a number of other things as well. Mostly dealing with the restructure of the company.

We had a training call planned, but Drew was unable to make it. No meeting happened. Just some texts back and forth.