Skip to content

Sales & CRM Systems

Pipeline automation: a stage is a promise

“Quote” should mean the same thing to everyone who reads the pipeline: the site visit is done, the scope is clear and you know who signs. Pipeline automation checks what must be true before an opportunity moves, turns anything missing into a task for its owner, and starts the next stage's work the moment it's entered.
Discuss your systemSee every stage defined ↓
leadsite visitquotedecisionwonheld · 1 missingopenOP-712 · K.L.new furnaceTo enter quoteMeasurementsattached TuePhotos6 attachedWho signsmissingWho signsboth ownersTask · E2 · confirm who signs · due Thu✓ E2 confirmed Wed 16:10: both owners signOn entering quoteQuote draft started from the visit notesOwner stays E2Follow-up set: 2 days after sendingStall alert at 7 days in this stage

Stages that mean different things to different people

In most pipelines a stage is whatever the last person to drag the card thought it meant. One estimator moves a job to “quote” after the call, another after the visit, a third once the quote is written. The forecast adds them up as if they were the same, and the follow-up that should start when a quote goes out starts at random.

Pipeline automation writes each stage down as rules: what has to be true to enter it, what has to happen before it's left, and what starts the moment it's entered. Every move, by a person or by the system, is checked against them. Anything missing becomes a task for the owner rather than a silent gap, and every move is recorded with who made it and why.

Every stage, defined

LeadContact and need recordedOwner assigned; first call due within an hour
Site visitMeasurements, photos, and who signsReminder to the customer the day before
QuoteThe quote is sentDraft started from the visit notes
DecisionSigned or declinedFollow-up cadence; stall alert at 7 days
WonThe job is createdJob and deposit invoice; handed to scheduling
LostA reason is recorded“Not now” goes to nurture

Five rules for stages that mean something

  1. 01

    Every stage has a meaning

    Written down once

    Each stage says what's true when an opportunity is in it, so a report of “in quote” means one thing.

  2. 02

    Exits are checked, not hoped for

    Every move, every time

    A move by a person or by the system is checked against the same conditions.

  3. 03

    Missing facts become tasks

    Held, not blocked

    An opportunity that can't move yet gets a task for its owner, with what's missing and a due date.

  4. 04

    Stalls are noticed

    A clock per stage

    Each stage has a time limit; past it, the owner hears first, then the manager.

  5. 05

    Every move is recorded

    Who, when and why

    Moves, overrides and the reasons for them are kept, so the history of a deal can be read later.

What pipeline automation hands off

In

Opportunity
stage, fields, owner
Stage definitions
enters, exits, on entry
Activity
calls, visits, emails
Stage rules
check → move → act

Out

Moves
only when the conditions are true
Tasks
for what's missing, with owners
Alerts
stalls, to the owner then the manager

Worth building when the pipeline has to mean something

Good fit

  • More than one person moves opportunities through the pipeline.
  • The forecast or the follow-up depends on what stage a deal is in.
  • Deals sit in a stage for weeks without anyone noticing.

Not the right fit

  • One person sells and keeps the pipeline in their head.
  • The stages themselves haven't been agreed. Start with CRM architecture.

Where it's built in

Next to pipeline automation

Questions about pipeline automation

Can people still move deals by hand?

Yes. A move by hand is checked the same way. If something's missing, they're asked for it, or they can override with a reason, which is recorded.

Does it work with our CRM?

Most CRMs with stage fields and an API can hold the rules, such as HubSpot, Pipedrive or Salesforce, with the checks running in the CRM or beside it. These are starting candidates, not requirements.

What if a rule turns out to be wrong?

Rules are configuration, not code. Changing one is a small reviewed change, and the history shows which rule applied to each past move.

Won't this slow the sales team down?

Only when something they'd need later is missing, which is exactly when it should. Everything else moves as before, and the busywork on entry is done for them.