“How big a job is this?” is usually the first question when a CRM needs fixing or replacing, and it’s hard to answer without a rough sense of how much is involved. This calculator gives you one. For each of seven questions you pick the closest range: connected systems, contacts in the CRM, active workflows or flows, pipelines or distinct sales processes, custom or middleware integrations (Zapier, Make, n8n or direct API work), teams, brands or regions using the system, and whether the current setup is documented. It then places your setup in one of four bands and lists the answers pushing it up.
It’s deliberately simple. Counts are a reasonable proxy for complexity, but they miss things, which is why documentation is one of the questions: ten well-documented workflows can be easier to work with than three that only their builder understood. Even so, one badly built integration can cause more trouble than five good ones, and no range picker will catch that. The calculator doesn’t give prices; scope depends on what you need done, not only on what exists.
Run the calculator
What each band means
Your result is one of four bands: Contained, Moderate, Complex or Highly complex. Below the band, a What drives it list names each question where you picked one of the two higher ranges. Here’s what each band usually means for an audit or implementation.
Contained. One main system, a modest number of records, a handful of workflows and a single team. An audit can usually review everything rather than sampling, and most implementation work happens inside the CRM itself.
Moderate. Several connected tools, more than one pipeline, or two or more teams with different needs. Scope starts to depend on interfaces: how data moves between systems, and whether teams agree on definitions. Expect time spent on lifecycle and ownership rules as well as configuration.
Complex. Many integrations, large record volumes, dozens of active workflows or several teams. A review at this level usually samples workflows and traces specific journeys from start to finish rather than checking every item. Data quality and documentation become a significant part of the work.
Highly complex. Multiple core systems, high data volumes, many teams and integrations with custom logic. Work is normally phased: diagnose first, agree priorities, then implement in stages with validation between them. Requirements documentation becomes essential, not optional.
Some answers weigh more than others. Workflows, connected systems and integrations count for more than raw contact volume, because each one adds definitions to agree and failure points to test. A business with half a million records and one team can be simpler to work on than one with 20,000 records shared by sales, support and three regional marketing teams.
The band describes the size of the system, not its health. A highly complex CRM can be in good shape, and a contained one can be a mess. For health, use the CRM Health Check.
Using the result
If you’re preparing for an audit, the band is a useful thing to share at the start of the conversation. Our CRM Audit and CRM Implementation pages explain what each engagement covers, and published starting prices are on the pricing page. For larger setups, writing the requirements down first, as described in CRM requirements documentation, usually saves more time than it takes.