From Enquiry to Handover: Designing Your Pipeline

Most pipelines fail before the first lead arrives, because the stages were copied from a template that describes someone else's business. The team then works around the pipeline instead of through it — leads pile up in a stage called "Follow-up", reports say nothing, and within a quarter the CRM is a contact list with opinions. Designing stages that mirror your real process is the single highest-leverage hour you will spend in any CRM.

Start from the journey, not the software

Before touching settings, write down what actually happens between an enquiry and a completed sale or admission in your business. Interview the people who do the work, not only the manager. You are listening for the moments where something real changes: a conversation happened, a document arrived, money moved, a site was visited. Those moments — not activities — become your stages.

Rules that keep stages honest

• Name stages after completed events, not ongoing work: "Site visit done", not "Following up". An activity is a task; a stage is a state.
• Give every stage an exit criterion everyone can state in one sentence. If two counsellors would classify the same lead differently, the stage is ambiguous.
• Keep it to five to eight stages. Fewer hides the process; more invents distinctions nobody maintains.
• Do not create parking stages. "On hold" and "Follow-up" are where leads go to die. Use a scheduled next task instead, and record lost leads with a reason, separately from the pipeline.

Two worked examples

An education pipeline might run: Enquiry, Contacted, Counselled, Application submitted, Fee paid, Enrolled. Each step is a verifiable event, and the later ones can be self-served — with ASH's applicant portal, a student sees their own stage and fee status through a secure link, which removes a whole category of "what is my status" calls. A real estate pipeline runs differently: Enquiry, Qualified, Site visit scheduled, Site visit done, Negotiation, Booking, Handover. Notice that the site visit appears twice — scheduled and done are different states with very different drop-off, and collapsing them hides your most important number. The real estate module and the education module ship with stage patterns suited to each.

Make the pipeline drive the work

A pipeline earns its keep when stage changes trigger action. In ASH's workflow builder, a lead entering "Site visit scheduled" can automatically create a reminder task and notify the owner; a lead going quiet for a week can trigger a follow-up task or, on the Enterprise plan, enrol into an email sequence or send a DLT-registered SMS template. The stages become rails the process runs on, rather than labels applied after the fact.

Revisit quarterly

Watch stage-to-stage conversion in your reports. A stage that passes nearly everything through is decoration — delete it. A stage where most leads stall is either your real bottleneck or a badly defined state; both are worth a design conversation. Your pipeline is a model of your business, and models earn trust by being revised.