Start with the pipeline you actually run
A minimum viable CRM is not a toy — it is the smallest shape of record and stage that matches how your team really wins, loses, and re-opens work. If your stages are a fiction from a template (everyone drags to Qualified in week one, then fights in a spreadsheet after), the tool is a data-entry tax before it is a system of record.
Start by naming the stages a deal or job actually passes through from first touch to won, lost, and nurture. Fewer, honest stages beat a beautiful diagram nobody follows. Book a free systems review if you want a second pair of eyes on the truth in your data before you shop for another app — our offers include process audit when the map is messy, build when a thin custom layer is the right move, and ongoing system care once the hub is in daily use.
Fields, stages, and the report that stops arguments
Ownership is non-negotiable on day one: one named owner per open opportunity, and a rule for handoff to delivery or support when the deal flips. Without that, the CRM is a broadcast channel, not a forecast.
Fields should start embarrassingly small — the ones you would actually filter and report on in a Tuesday meeting, not a wish list. Typical first cuts: source, value band or range, next step date, and why lost when it closes. Everything else is optional until a repeated we need that on every call from the people who will keep it up.
One report leadership trusts — often a pipeline by close date and stage plus new vs slipped week on week. If the report does not match reality in the room, fix behaviour and definitions before you add a fourth dashboard nobody opens.
| Keep it this lean | Defer or kill |
|---|---|
| Stages that match a real huddle, not a default template | Custom objects that one person in finance asked for in year one |
| Mandatory next action and owner on every open line | Nice to have fields the team re-types from email every week |
| A weekly refresh habit (15 minutes) in the tool | A perfect automation matrix before anyone owns data quality |
When to add complexity
Good triggers to spend more: you have a repeated, measured same wrong thing twice that automation would fix, or a second system of truth re-keying into the CRM and you are ready to own the integration. Bad triggers — the vendor suite upsell, or AI for a list nobody is cleaning.
If the CRM is already a rescue story — inherited mess, works for no one — a platform swap is rarely step one. Sometimes the win is a process audit, a cut-down model, and training; sometimes it is a rescue and rebuild on a build that was never right for the team. We will say which out loud, not the one with the best referral fee.
Local and remote: we work with Teesside and the North East and further afield when the fit is right. Book a systems review to get pipeline hygiene unstuck, or browse our offers for audit, build, and care.