Good conversation between Steve, Sean, Cory, and Brandon. We were going over ideas for sales, eye candy, graphs, charts, and system-wide aggregates. Here are some of our notes:

- We would like to create a MVP - minimal viable plan (product, person, whatever) - focusing on the plan part of it for fracture (future adilas project).

- Brandon pitched the value add-on core model with 5 levels – 1. Internal core (transactions), 2. Industry specific skins and functionality, 3. Custom code, 4. BI – Business Intelligence (aggregates), and 5. Enterprise level (multi corps and multi worlds). Part of our upcomming plan is to work on level 4 - BI or business intelligence (eye candy, graphs, charts, stats, counts, totals, etc.). Make it look good and be quick and easy to get to. Bury the transactional core a couple levels deep, so it is still there, just feeding quick information off of the upper levels (aggregates) vs all of the transactional pieces and records.

- We really want to work on the look and feel of the cart - less is more on the display on the cart

- For graphs and charts, we could use cfchart (code tags) or JSCharts (javascript charts).

- The reports homepage could use some loving

- Surface stuff to help with demos and sales

- Capture the daily, location, and category levels – basically, per day, per location, and per category (on the P&L and BS). As a note, we already have this info... we just need to grab and hold it. Also, we could go backwards on this one... there is already something that exists. We could pull it all in going backwards. There is already a path and a pattern.

- ETL – extract, transform, and load – this is how you get the aggregates = Brandon would be happy to build in this aggregate table or whatever -Steve would like us to talk and work with Eric about the backend triggers and deeper database stuff.

- Lots of talk about database triggers vs smaller microservices - pros, cons, visible, not visible, who has permissions, and best practices.

- We need to remember the API sockets and other ways of getting data both in and out. This needs to be part of our process.

- We tend to get pulled off of a project due to custom code, customer requests, and budgets (time, money, resources).