Agency operations

Agency Pipeline Design

Most agency pipelines fail in a surprisingly mundane way: nobody agrees what the stages mean. One salesperson moves a promising lead to “proposal”; another waits until a document is actually sent. A dashboard can look precise while the underlying data means different things to different people.

Make every stage prove something happened

A useful pipeline is a state machine for commercial work. “Discovery booked” means there is an appointment. “Proposal sent” means the prospect has received a commercial offer. “Closed lost” means the opportunity is no longer being actively pursued. Those definitions sound obvious, but writing them down removes a great deal of reporting noise.

Systems principle: If two team members can look at the same opportunity and reasonably choose different stages, the stage definition is too vague.

Design backward from the next action

For each stage, decide who owns the record, what the next action is and what must be true before it moves. Keep fields to the information that changes a decision: service interest, likely value, source, decision timing or a genuine qualification constraint. Every extra required field creates admin that somebody eventually learns to bypass.

Watch the edges

Stale opportunities are not harmless. They distort forecasts and hide weak follow-up. Add a clear rule for opportunities with no next action, and review them regularly. The goal is not to keep the pipeline full; it is to keep it truthful.

Audit five records

In the context of agency pipeline design, choose five active opportunities without warning the sales team. For each one, identify the owner, state, next action and last meaningful interaction using only the CRM. Every question you cannot answer exposes either missing process discipline or unnecessary ambiguity in the system.