I recently helped a customer create a very cool QuickBase to manage service contracts throughout their Fortune 500 organization. The current system was being managed with a combination spreadsheet and file cabinet. As a result, the Company estimated that they had lost over $4 million in the past year alone in missed "details” (terms, renewals, etc.).
So the customer created a very powerful QuickBase that could manage the approval process including:
This whole process to manage hundreds of contracts included dozens of users across a variety of business functions. Using a combination of custom notifications and roles, the QuickBase was developed to notify the right people of the right information, at the right time. The amazing part was that this QuickBase was a single table application. When I finally saw it just before the customer was going to roll it out live, I was shocked that a process this complicated could be managed through a single table, roles, and notifications.
I know that often as I’m developing my own applications I find myself making things way too complicated with too many tables and relationships to keep track of. There is definitely a time and place for multi-table QuickBases but sometimes simple really is better.