All insights

CRM

The three-pipeline problem: when your CRM has more stages than deals

CRM · Jul 6, 20264 min read

Open most small-business CRMs and the same pattern appears: three pipelines, each half-configured, none of them trusted. The deals that matter live in a spreadsheet on the side, because nobody believes the tool reflects reality.

Stages should match the close

A pipeline is only useful if its stages mirror how the business actually wins work. When the stages are aspirational, copied from a template instead of drawn from the real motion, deals get stuck between steps that don’t describe anything and the reporting on top is fiction.

The repair starts by throwing away the extra pipelines and drawing one that matches the close. Routing, follow-up, and reporting are then built on that single source, so the number at the top of the month is real instead of reconstructed on Fridays.

Automation comes last

Automation layered on a broken pipeline just moves bad data faster. Architecture comes first, and then the automation earns its place: a trigger, a few deterministic steps, and a check. That order is what makes the CRM trustworthy again.

Start

Start with what’s broken.

Send the situation in a paragraph. Strygon comes back with a read on what’s likely wrong and what it would take to fix, before anyone talks about price.

Most builds start withleads dying in an inbox., three half-finished pipelines., follow-up nobody owns., numbers that never agree., four vendors blaming each other.

What to send
A paragraph. What broke, and where it shows up.
What comes back
A read on what is likely wrong and what fixing it takes.
Price
The last conversation, not the first