Danny, Dustin, Steve, and I were on the morning meeting. Danny had some Git (code repository stuff) questions. Steve and Dustin were working on some bug tracking. We also showed the guys some of Chuck's new layouts for sales. We had a bunch of fun ideas. Some of the ideas were being able to change the backgound images, changing the main presentation settings, and even being able to click on a link and have it automatically switch background images, verbiage, and settings. A simple little URL switch and all of a sudden, you have a customized presentation. Super cool idea.

On this same line of thinking... if we can flip the demos and presentations really easily, we could potentially use the same presentation gallery to do different presentations for different verticals. We just store the settings, verbiage changes, images, and even options, features, tools, and usage models. That would be super cool.

- Maybe using the ice-down date as a transfer between transactional data to aggregated data... That is a great switch and/or trigger. Similar to the water to ice analogy... The transactional data is kinda loose... Once it gets pushed to the aggregated data, we really want that data to be more stable (more like ice). Great idea.

- What if we had some bulk tools on the transactional side to post and/or lock things down. Once that data is locked down, we can then pull that data across to the aggregated system. Steve was talking about a possible two-part effort. They get to set a date (virtual line in the sand) and things behind that date can't be changed without altering the ice-down date. We also allow the users to lock things down on the transactional side of things.

- On a different note, Steve would like to build things out to a trust level... Making a number of adilas players as dependable cofounders. As a side note, we could use the new customer loyalty points to keep track of a virtual club member point system. They, the special accounts, are already setup like mini bank accounts.