Help Center
Contacts & leadsAdmin only10 min read

Build your sales pipeline & stages

A pipeline is the path every opportunity walks, from first hello to closed. You design it yourself — name it, build its stages in order, and decide which fields your reps see. This guide is the admin’s side of that: how to set a pipeline up in Settings, and how to keep it healthy as your process changes.

Pipeline, stage, lead

Three words, one idea. A lead is a single opportunity attached to a contact. A pipeline is the ordered set of stages that lead moves through. At any moment a lead sits at exactly one stage, and that stage is how everyone reads where the deal stands.

This guide is about building that pipeline as an admin. For the day-to-day — creating leads, moving them, filtering the table — see Contacts, leads & pipelines.

A stage is just a named step
In Exabloom a stage is deliberately simple: a name and an order. There’s no colour, probability or “type” baked into a stage — which keeps pipelines quick to design and easy to change.
The page

Where to build them

Pipelines live under Settings Pipelines. The page lists every pipeline you’ve built; + New pipeline starts a fresh one. If you’ve never made one, you’ll see a “Create your first pipeline” prompt instead — and the Leads screen will send people here until one exists.

Pipelines
Configure your lead stages and data fields.
+ New pipeline
New enrolments
5 stages · 9 data fields
Renewals
4 stages · 7 data fields
Settings → Pipelines. Each pipeline opens an editor with two tabs: Stages and Data Fields.

Creating or opening a pipeline gives you the same editor: a Pipeline name at the top, then two tabs — Stages and Data Fields. Nothing saves until you hit Save (or Create on a new one), so you can lay out the whole pipeline before committing it.

The Stages tab

Designing your stages

A brand-new pipeline starts with no stages at all — there’s nothing pre-filled. You build the exact steps your business uses. On the Stages tab, Add new stage appends a row; type its name; repeat. Drag the handle to reorder, and the trash icon removes a stage.

Edit pipeline
Pipeline name *
New enrolments
StagesData Fields
Stages (5)
New
Contacted
Trial booked
Enrolled
Lost
Add new stage
The Stages editor. Type each name, drag the handle to reorder, “Add new stage” to extend the list.

Order is everything here, because the order you arrange them in is the pipeline. The very first stage has a special job: it’s where every new lead lands by default. So make stage one your true starting point — “New”, “Enquiry”, “Lead received” — not a step that assumes work has already happened.

NewNew leads land here
Contacted
Trial booked
EnrolledWon outcome
LostLost outcome
Stage one is the default landing spot for new leads. The rest flow left to right toward your outcomes.
Keep it to the steps that change a decision
A stage should mark a real shift in where a deal stands, not every tiny task. Five to seven crisp stages beats fifteen fuzzy ones — reps update them more honestly, and your pipeline view stays readable.
Important

How “won” & “lost” work

Here’s the part that surprises people coming from other CRMs: Exabloom has no separate “Mark as won / lost” button. A lead’s progress is its stage — there’s no second status sitting alongside it in the app. So the way you record an outcome is to make it a stage.

There’s no…
Mark won Mark lost

No separate Won/Lost control in the app.

So instead…
EnrolledLost

End the pipeline with the outcomes you care about, as real stages.

No Won/Lost control exists. Record outcomes by ending your pipeline with explicit closed stages.

End your pipeline with the closes you care about — an Enrolled (or “Won”, “Signed”) stage and a Lost stage. Moving a lead there is what “closing” means in practice, and because the Analytics dashboard counts leads by stage, those outcome stages become your won/lost numbers automatically.

Don’t rely on a hidden “status”
Under the hood a lead does carry an open/won/lost status field, but it isn’t exposed anywhere in the app today — you can’t set it or filter on it. Treat your stages as the single source of truth for outcomes, and don’t design around a status reps can’t actually touch.
The Data Fields tab

Which fields reps see

The second tab, Data Fields, controls which fields are visible when viewing or editing leads in this pipeline. Fields are grouped under Lead Information and Contact Person Information; flip a toggle to include or drop each one. A running count shows how many are enabled.

Control which fields are visible when viewing or editing leads in this pipeline.
Lead Information
Title
Stage
Owner
Budget range
Subject
Contact Person Information
Phone No.
Email
Preferred language
6 fields enabled
The Data Fields tab. Toggle the lead and contact fields — system and custom — that this pipeline should surface.

This is where your custom fields earn their keep: any lead or contact field you’ve defined shows up in this list, ready to switch on. Two pipelines can show entirely different sets — a renewals pipeline needn’t carry the fields a new-business one needs. See Set up custom fields to create them.

Fields here, layout elsewhere
Data Fields decides which fields a pipeline carries. How they’re arranged in the conversation sidebar is a separate setting — see Customise the Lead Info panel.

Running more than one

You can have as many pipelines as you sell in distinct ways. A tuition centre might run New enrolments and Renewalsside by side; each has its own stages and its own visible fields. The Leads screen shows one pipeline at a time — people switch between them from the dropdown at the top-left of the table.

  • Make a new one when the steps genuinely differ — a different journey, not just a different filter on the same one.
  • Duplicate an existing pipeline to clone its stages and fields as a starting point, then adjust — faster than rebuilding from scratch.
  • Lean on stages and filters instead of a new pipeline when it’s really the same process viewed differently — saved views slice one pipeline cheaply.
Keeping it healthy

Renaming & deleting stages

Pipelines aren’t set in stone. To rename a stage, edit its text and save — leads sitting in it come along under the new name. To reorder, drag the handle. Both are safe and non-destructive.

Deleting a stage is where care is needed. If the stage is empty, it’s removed straight away. If it still holds leads, Exabloom stops and asks what to do with them:

Delete Pipeline Stage

You are about to delete stage “Trial booked” which contains 12 leads.

Action
Move to another stage
Move leads to
Contacted
To confirm this action, type “CONFIRM”
CONFIRM
CancelDelete
Deleting a stage that holds leads forces a choice — and a typed “CONFIRM” — so leads are never silently dropped.
  • Move to another stage — pick where its leads should go, and they’re all reassigned there. This is almost always what you want.
  • Delete leads in this stage — permanently removes every lead sitting in it. Use only when those opportunities truly no longer matter.
The CONFIRM step is your seatbelt
Either way, you must type CONFIRM before the delete runs. If you chose “Delete leads”, that text is the only thing between you and losing those leads for good — read the dialog before you type it.

Pipelines to copy

Starting points you can adapt. Notice each one begins with a clean intake stage and ends with explicit outcomes.

1 · A simple sales pipeline

The default for most teams — a short, honest path from enquiry to close.

NewContactedQualifiedWonLost
2 · Tuition enrolment

A trial in the middle, with enrolment and a lost stage as the two ways it ends.

NewContactedTrial bookedEnrolledLost
3 · Renewals

A second pipeline for existing customers, run alongside new business.

Up for renewalReached outRenewedChurned
4 · Onboarding hand-off

Once a deal is won, track delivery on its own pipeline so sales and onboarding don’t tangle.

SignedKickoffLive

Good to know & pitfalls

  • Pipelines start empty. There are no default stages — build the exact steps your business uses, in order.
  • Stage one is the landing pad. New leads default to the first stage, so make it your genuine starting point.
  • Outcomes are stages. There’s no Won/Lost button — end the pipeline with the closed stages you want to report on.
  • Deleting a busy stage is a decision. You must move its leads or delete them, and type CONFIRM. Moving is the safe default.
  • Data Fields are per-pipeline. Each pipeline chooses its own visible fields, so two can look completely different.
  • One pipeline shows at a time. The Leads table is scoped to the pipeline picked in the dropdown — switch there to see another.

Need a hand?

Our Singapore-based team is one message away — happy to help you get set up.