There were quite a few people on the morning meeting this morning. We had Steve, Dustin, Wayne, Shari O., and myself. We started out and Wayne wanted to get a standard spot to report and handle issues and bugs for the transition to the AWS stuff. We setup an element of time and will be using the sub comments and notes to record any issues and/or bugs.

After that, Steve and Dustin wanted to go over the cannabis cultivation homepage and figure out where we could speed things up. See attached for some notes. The main take away from the meeting was user designed, single pagers, let users control the flow of data based on clicks and events, and use AJAX (asynchronous JavaScript and XML) type interfaces. The conversation turned lightly to aggerated data (pre-summed up data) vs transactional data (individual details). We would really love to keep heading more and more in this direction.

Shari O. was talking about some communication issues between our clients and the reps that support them. We had an issue last night when we had to turn a client's system off. We had contacted the client and they were over 3 months behind on monthly payments. We shut them off (the companies system) and then crap hit the fan. The client was open 24 hours a day. Anyways, we had a rep that got on the phone and was ripping our tech support people a new one. We had some talks about how we need to use the system to be the bad guy. We have a project planned that will show prompts in the page headers and will let them know that they will be shut off if they get past a certain date. We need to get back to that. If we could get this project done, it would save a lot of headaches.

Shari O. was talking about some team work and playing as a team. We have some great people who help and participate and some that don't do much. We have a spectrum of different people all around.

This is both funny and sad, but sometimes we really feel like the little red hen - who wants bread? Me, pick me. Ok, who wants to help me plant it? Not me, not me. Ok, who wants to help me harvest this stuff? Not me, not me. Ok, who wants to help me with (fill in the blank)? Not me, not me. Ok, I guess that I'll just do it my self. Suddenly, we get the bread done, and everybody wants it. There is some truth to that.

Steve was expressing some concerns that he is getting behind on his email stuff. We had some light talks about what needs to happen there and how best to structure our team. At a certain point, you almost give up and/or can't keep up. The mountain keeps growing and doesn't seem to stop.

Back on team building stuff... we are trying to help and train our guys and gals to work as independently as possible. There are constant needs that just keep coming. It gets pretty crazy. Back on the email stuff, maybe we need to use more of a standard like "support@adilas.biz" or "info@adilas.biz" and then let it get filtered out before it hits all of us. Steve really wants us to use technology to play this game. More automation and more ideas and options. Lots of tag team stuff. We are also learning along the way. Lots of new lessons being learned and hopefully applied.

Steve was talking about dependables and who is playing with what and who is doing what. We have a very independent model. That is awesome but does have some challenges as well. Steve would like his sales focus to be more on the white label type arena.

Alan joined the meeting and gave us an update with USAePay and there EMV chip reading and chip processing. We may end up having to integrate with FirstData as a merchant processing account (more gateways). We currently offer some chip reading options, but it still kinda random and small ball of strings. There is a growing need on the merchant processing and gateway stuff (credit card processing and chip reading technology stuff). This is way out there... but maybe at some point adilas will be their own merchant processing gateway (some sort of internal solution). Alan volunteered for this project (just kidding).

Towards the end of the session, Eric jumped on and needed some help with some queries of queries, complex data, and getting some data tables setup for his custom reports. We also scheduled some other time next week to work on sub inventory and API socket documentation stuff.