Talking with Steve about simple part counts and baby aggregation tables. Making a plan for how to play through the next couple of levels. Sometimes, we can only see so far ahead. We have to do what we know and then reevaluate the next steps.

We spent some time talking about the pros and cons of database triggers. Eric was making some great comments. Yes, the triggers do fire whenever a table is hit or modified, but they are also totally hidden pieces of the business logic. We talked about ways of creating our own triggers that are more visible and in full view.

We also got into some discussions about selling what we have and our interactions with different 3rd party discussions. So, when dealing with the 3rd party solutions, we get the best bang for the buck if we can tell you when something happens and they you record it. If not, they (the 3rd parties) keep asking (traffic back and forth) for data - push technology vs get or pull requests. The ideal is make it all activity based.

One of our biggest problems is that our clients don't even know what is built, available, and even already included in their monthly fees. Somehow letting our clients know what we have. That would be awesome.