Talking about creating a smaller sub theme in adilas and called it "fracture". This would end up being an adilas fracture account. We would like to rebuild things from the virtual ground up and add in all of the subs of subs and database field level control. This would be a full on internal white label and/or internal theme that goes down to the micro level. This deals with database field names, settings, permissions, and all of the sub settings and sub permissions that are needed. It could also deal and use smaller getters and setters as well as individual databases, custom API access levels, etc.

This is kind of a dream, but it would be so cool if we took the time to virtually rebuild the entire thing from the ground up and use and apply all of the ideas and lessons that we have learned getting to this point. That would be really exciting. It would really be cool if we had the money, funding, plan, and people and talent assets ready to play the game as well. That would be a huge but awesome project. Just an idea and/or a dream at this point in the game.

Talking about scalability and how to manage up and down swings without shooting ourselves in the foot. We were talking about load balancing and monitoring usage, storage, and bandwidth.

We have been seeing some light push back on price from the consultants. Basically, they are charging a certain amount and then promising that our services are and/or will be a certain rate for life.

We are also seeing that some of our clients are growing as they come on to our systems. That is hard to know what is going to happen when they first start up.

Technology keeps changing and pushing things forward. This is a crazy world and we need to build on the dynamic changing environments that happen all the time. This is not a static model.

Traditionally, software companies build versions and then release that version. They then build in the background and make the next version and then plan the release of the next version. Our model is literally build and deploy on a daily, weekly basis. Alan was saying that our clients are paying for what the current adilas system does and can do... they are not paying for the future developments. However, some of the client demands are almost all speed, bulk, and future related.

Tons of cause and effect relationships, pros and cons, and maintenance things... lots of talk about concepts, styles, and preferences.

After our discussions, we all went back and worked on our own projects. I was working on adding in the customer type id filter for sales tax reports and advanced invoice searches. Steve and Dustin were working on Metrc API pieces and bulk QR code labels. We also had both Wayne, Alan, and Calvin pop in and help with different questions and projects. Busy work section. Also some light phone calls and tech support stuff.