Multi-Database Architecture

Multiple databases, what's the big idea?

The humble beginnings of virtually every business at some point in time used an excel spreadsheet to manage leads, contacts, and various other things. When CRM and Lead management software took to the cloud, they quickly helped businesses work more efficiently and save time with the accessibility of familiar tools in one convenient place. We discovered that many CRM systems are missing a fundamental element that every business needs in a CRM- The ability to build more than one contact database.

‍

The idea of having more than one database is quite simple and very necessary for modern businesses. There are countless use cases, but for a minute, let's think back to using spreadsheets. When you keep your spreadsheets in a folder on your work or personal computer for selling, researching, or viewing your customers, you will typically have more than one. Well, if you said yes, you've probably figured out where we're going with this. You see, each of your spreadsheets is created to hold different business-related information such as a spreadsheet for customers, a spreadsheet for jobs, leads, or something similar. Each of the columns in your spreadsheet probably has different headings, and it's likely you control with whom you will share these in your team.

‍

Typical CRM systems (including market leaders) have excellent solutions. Still, none of these systems allow you to create individual databases for different reasons. That's not to say you can't segment information and setup routing to control who sees what, but this is complex and doesn't give you the flexibility you may need, which is also why so many businesses fail with CRM adoption.