Yes, if you want the build to fix the problem you actually have. A discovery phase looks at how work moves through your business before anyone configures anything, so the system you pay for is aimed at the right thing. The only time to skip it is when you already know exactly what needs building, and why.
At Centralise this stage is Assess: a top-down view of your whole revenue engine, from where leads come from to where quotes go. This article covers what goes wrong without it, when you can safely go straight to the build, and what you should walk away with either way.
Most go wrong at the brief, long before the build. A partner configures what they're asked for. If the request is "set up a seven-stage pipeline and automate the handover to delivery", that is what gets built. Whether seven stages reflects how your team really sells, or whether the handover was ever the real issue, rarely gets asked, because nobody was paid to ask it.
The real problem usually sits between people. Sales considers a deal done when the contract is signed. Delivery considers it started when the kickoff call is booked. Nobody owns the fortnight in between, so the client's first experience of you is three people asking them the same questions. No CRM setting resolves that on its own, and if you configure the tool before you agree who owns that gap, you end up with a well-built system wrapped around a broken handover.
The same three patterns come up again and again.
Pipeline stages nobody uses. The stages were designed in a workshop with leadership and reflect how the sales director thinks deals should move. The reps sell differently. Within a few weeks deals jump straight from the second stage to closed won, and the pipeline report stops telling you anything.
A handover automated exactly as it was. Before, sales emailed the account manager, who asked for three missing details and then chased finance for the purchase order. After, a workflow sends the same incomplete information automatically. The chasing still happens. It just starts with a notification now.
A migration that copies the mess across. Duplicate companies, contacts owned by people who left two years ago, a lifecycle stage field with eleven values and four meanings. Move that into a new portal without deciding what clean looks like and you have paid to relocate the problem. It also gets harder to untangle later, once new data has been built on top.
When you already know what needs building and you are right about why. That might be a specific integration feeding a process that already works, a new team joining a portal that is already well governed, or process work you have done yourself, written down and agreed with the people who do the work.
In those cases a good partner should tell you to go straight to the build. We do. Paying to be told what you already know is a poor use of anyone's budget.
A simple test: could you write down, on one page, how a lead becomes a customer and then a renewal, who owns each step, and where it breaks? And would the people doing that work agree with what you wrote? If the answer to both is yes, skip it. If you hesitated on the second question, that hesitation is the reason to do it.
Real records and the people doing the work, not just leadership. Leadership can describe how the process is meant to run. The records show what happens: deals that sat in the proposal stage for months, quotes created and never sent, contacts with no owner. The people doing the work explain why. They know which field everyone skips because it doesn't apply to half the deals, and which spreadsheet finance keeps because the CRM figure is never quite right.
It should also look across the whole revenue engine rather than one team. Problems tend to show up in one place and start in another. A renewal goes badly because the original scope was never recorded at the point of sale, and no amount of work on the renewal process will find that.
Two more things separate a useful assessment from a box-ticking one. Findings should be marked as confirmed or hypothesis, so you know which ones to act on now and which to test first. And the recommendations should include fixes that need no technology at all, such as agreeing who owns a follow-up or removing a step nobody needs. If every recommendation involves configuring something, ask why.
By the end you should be able to decide four things: where the biggest gaps are, which changes matter most, what you can fix with what you already have, and where further investment is justified. All of it in writing, so you can act on it with or without the partner who produced it.
That last point matters more than it sounds. Before you sign, ask whether you keep the outputs if you don't go ahead with the build. If the answer is no, or vague, you are looking at a sales exercise with a fee attached. With Assess you keep every output, whether or not you work with us afterwards.
Not sure whether you need a portal audit or a full assessment? [LINK: Article 2] explains the difference and the right order for both.
Assess takes three weeks and costs £4,000, excluding VAT, for every company regardless of size. It produces four outputs, in this order:
Assess ends at the Roadmap. Any build is separate work, scoped from what Assess found, so if you do go ahead with us it starts from what has already been agreed.
Assess runs for a fixed three weeks. Your team's involvement is concentrated in a small number of working sessions and reviews, mostly while the Landscape is being built.
You can, if someone has the time and enough distance from the process. Distance is the hard part, because people inside a business tend to describe the process as they believe it works. If you do it in-house, start from records rather than opinions, talk to the people doing the work, and write every finding down with the evidence behind it.
It can be. Two checks will tell you: whether you keep the outputs if you walk away, and whether the recommendations include fixes that need no new technology. Assess passes both.
You keep the Brief, the Landscape, the Report and the Roadmap. Use them to make the changes in-house, or take them to another partner.
The free revenue audit asks how your revenue engine works today and gives you a report on where it is under strain. If you go on to Assess, your answers become the starting point for the Brief.
Start the free revenue audit or find out more about Assess.