On the morning meeting with Dustin, Steve, and Alan. We were touching base on all of the things going on. Steve needed a merge into master for his current code branch. We did that and both Alan and Steve have plans to take some of the pages a little bit further. Most of the meeting was just touching base on different projects and who is doing what.

I spent quite a bit of time working on emails and doing some follow-ups with different people.

One of the follow-ups was with Russell. I called him and we chatted and then jumped online for a 2 hour meeting with both Steve and I. Great meeting. See below for a number of ideas, concepts, direction, and notes from our meeting:

- Need to focus on Snow Owl theme settings (overall look and feel of adilas pages, reports, headers, footers, and data tables).

- On the data tables (fancy tables that allow exports, sub filtering and sub searching, and sorting of columns) - we talked about the need to get a better handle on these data tables, make them more standard, and deal with the possible weaknesses and/or bottle necks with going with these new fancy table structures. By way of a note, we have a number of these data tables throughout the entire system. We need more of them and we also need to refine some of them to make things faster and smoother.

- We talked about what would be involved with the process if we created our own data tables, specific for adilas, and our client's needs. We talked about creating our own custom tags, our own we components, and then using that throughout the whole system.

- We spent a good amount of time talking about how the need to show aggregated data could remove some of the existing load from showing transactional data with the data tables. Those data tables are really good at showing smaller number of records vs tables with thousands and thousands of records. They really work better for things in the hundreds of records vs the thousands of records (and up). Aggregated data would be things like quick counts, totals, sums, averages, maxes, mins, groups, and other overview type data and numbers. That would also be great if we could show that data in charts, graphs, quick numbers, easy to use mini dashboards, and even graphical sub homepages or graphical homepages per section (system main player groups and/or subsets of specific tools and features).

- If we start showing graphical homepage and aggregated data, it would virtually allow us to pull back a level and push the transactional data deeper. It still needs to exist, but it may be a better option if we could get them quick details and data and then allow for drill-downs as needed. Quick, easy, simple, and then more details as needed.

- On the data tables, do we know what people/users are using and wanting? Is it the exporting, the sub searching, filtering, sortable columns, or quick pagination?

- Maybe work on and do some concepting and proof of concept on the adilas data tables. Take it to the fracture level.

- Russell is going to get with Brandon to do some training on the existing and current data tables. We plan on recording the training session. The goal is to start standardizing the implementation of those tools and features (data tables) in the system.

- We (Steve and I) are really trying to focus on better project management, planning, and helping everybody get small victories. Some of this may involve virtually protecting our guys so that they don't get pulled in every direction.

- Lots of talk about MVP's (minimal viable product) and shooting for that type of approach.

- Breaking things (projects and processes) into smaller projects and pieces.

- Asynchronous data loading for big record sets.

- API sockets and loading in bite sized pieces, data, and logic as the application backbone (main source of both raw and formatted data).

- Russell was talking about a need for more developer training, requirements, snippets, CSS and code samples, standards, validation, and other dev tools.

- Steve and I would like Russell to lead the way and lead out on what is new and what is going on. Nothing too huge, but basically, what is the next logical step?

- Having Russell and Chuck work together. More coordination and small teams. Getting involved with all of the other players and pieces. Different talks about teams and collaborating with each other.

- Easy, pretty, simple, and powerful

- White labeling our own product on a per business vertical type model.

- Russell would really like something that he could be involved with and have some kind of stake, claim, and or ownership. We talked about both adilas and adilas fracture type options.

- Steve would like to come up with a new business type model - who owns what, a perpetual trust type entity, open invitations, rules, regulations, standards and options. Reformatting our existing business structure.

- The concept of how "fracture" keeps happening. The deeper we look, the deeper it goes. Everything is sub dividing and splitting into smaller and smaller pieces or subs. Along with that, where are we headed? Ok, then let's build that.

- The whole thing keeps unwinding and new ideas keep coming and falling into place. We just keep taking the next logical step forward.

- We are seeing more and more needs and wants to be mobile ready, responsive, and modern design needs. This could be mobile apps, phone ready options, different screen sizes, multiple screens at the same time, virtual environments, and where are things headed? Keep pushing forward. Skate to where the puck is going to be (proactive approach).

- We are really wanting to jump into some other verticals (business entities and business categories).

- Steve used to look for a single rep or consultant. Not marital status, but size wise (just one person at a time). Now, he is trying harder and harder to find super consultants who want a group of like clients, outsourced compliance, oversite, over viewers, and other vertical specific services. He would love to tie into different CPA firms or groups. The goal there is to turn over the training, setup, oversite, and support to these super consultant groups or white label entities. They run with the needs per business vertical.

- Reoccurring revenue models and how to work with it and mange it along the way. SaaS (software as a service) and what and where is that headed? Good stuff.

- Let's make it happen. We can check off the checkboxes. Let's do it.

- We even want to move our leads over to the correct white label suppliers. We will act as the industry specific point of contact until a suitable entity and/or third party white labeler is in place and/or available.

- Let others focus on each vertical, we will focus on the core and our software package and the offerings.

- Even the core keeps fracturing. That sounds bad, but we are really excited about it. This is the new direction, small, multi pointed, configurable, flexible, software options and packages.