The part of your Salesforce build no consultant can do for you

TL;DR: This month a client and I agreed to move a go-live into the new year. Nothing is broken and the build is largely done — what's missing is a set of commercial decisions, starting with what the opportunity stages should actually be. That's not a delay. It's the project working properly, because a CRM built on undecided definitions has to be built twice.

This month a client and I agreed to push a go-live back to January. Nothing broke. The budget is fine. Most of the system is built and tested. What's missing is something no consultant can supply: the business hasn't yet decided what its opportunity stages should be, or settled exactly what belongs in its renewal pipeline. Until those decisions are made, pushing the system live would mean pushing live a guess.

The conventional view

A CRM project reads as a technical project. There's a scope, a build, a test phase, a go-live date, so when the date moves, the natural assumption is that something went wrong on the technical side. Someone underestimated the work, or the configuration hit a snag.

The challenge

In my experience, the hardest parts of a Salesforce build are not technical at all. They're questions like: when exactly does a deal move from one stage to the next? What counts as a renewal, and is a contract that comes back every five years a renewal, or existing-customer expansion? If two teams are measured on pipeline, whose pipeline does a given opportunity sit in?

Those are commercial questions. Only the business can answer them, and until it does, the honest move is to hold back. On this project we deliberately didn't build certain rules, because if the stages change, those rules would be built on sand. Configuring around an undecided definition isn't progress, it's rework you've scheduled in advance.

The strategic truth

Salesforce only works when it reflects how you actually sell. A stage model isn't a dropdown to populate; it's a decision about how you sell, written into the system. When that decision hasn't genuinely been made, you can tell, because everyone has their own interpretation of what belongs where, and every report comes with a verbal footnote explaining the exceptions.

Here's why the definitions matter more than the dashboards. Imagine £100,000 of revenue up for renewal this month, split across two customers. One renews their £90,000 and adds £10,000 on top. The other churns entirely. Measured on total revenue, you renewed 100%, congratulations all round. In truth, you renewed 90% and grew one account. Whether your reporting can tell those two stories apart is decided long before anyone opens a report builder. A forecast is only as good as the stage definitions underneath it.

And exceptions deserve the same honesty. Every business has the odd deal that doesn't fit the model, the five-year contract, the one-off that behaves like a subscription. The question isn't how to make the exception disappear; it's whether it's genuinely part of the pattern or, as I put it to a client recently, a bit of an anomaly as opposed to an actual truth. Name it, decide where it lives, and your reports stay clean.

Why this matters to your business

Undefined definitions are where confidence goes to die. The first time two leaders bring two different renewal numbers to the same meeting, the argument is never really about the numbers, it's about whose interpretation the system encodes. Settle the interpretation first and the meeting gets shorter.

It also changes what "late" means. A go-live that moves to let the business settle its definitions isn't a failed deadline; it's sequencing. And go-live itself is a milestone, not a finish line: definitions evolve as the business does, which is why someone needs to keep owning them after the launch excitement fades.

What to do about it

Try this before your next build decision. Ask whoever owns Salesforce in your business to state your stage definitions from memory, in sales language rather than system language. Then ask two people who work the pipeline to classify the same three deals: if they disagree, the system can't save you, because it will faithfully automate the disagreement.

Write the definitions down before anyone configures anything. Agree what a renewal is, what expansion is, and where the anomalies live. It's less glamorous than a build plan, and it's worth more than most of one.

Decide first, build once

A system that waits for a real decision will always beat a system built on a guess. The configuration was never the hard part. The hard part is being honest about how you actually sell, and once that's settled, everything downstream gets simpler.

If your reports already come with verbal footnotes and nobody's quite sure whose definition the system encodes, start by establishing what's actually going on. The Salesforce Reset is 60 minutes and £2,500, with written findings that show you where the system and your sales process have parted company. Book a Reset.