Agiled Docs
Guides

Build a Sales Pipeline

Track leads, deals, stages, and follow-up work.

Use this guide to set up a simple sales process in Agiled.

Start with a pipeline your team will actually maintain. A simple pipeline with clear next tasks is more useful than a complex pipeline that sales users avoid.

Goal

A clean sales pipeline should show where every opportunity sits, who owns the next step, what value is at stake, and which deals need attention. Keep the process simple enough that the sales team updates it every day.

Steps

  1. Create or import contacts and accounts.
  2. Configure CRM pipeline stages in settings.
  3. Create a deal linked to the contact or account.
  4. Add deal value, owner, expected close date, and next task.
  5. Move the deal as the opportunity progresses.
  6. Review pipeline reports and dashboard widgets.
  7. Use workflows for repeatable follow-ups when the process is stable.

Good Pipeline Stages

Use stages that describe real progress, such as new lead, qualified, proposal sent, negotiation, won, and lost.

Avoid stages that describe internal feelings, such as "maybe" or "hot lead". Stages should tell the team what happened and what should happen next.

Define Exit Criteria

For every stage, write what must be true before a deal moves forward. For example, a deal should leave Qualified only after the budget, need, decision maker, and next meeting are clear.

Exit criteria keep reports useful because everyone moves deals for the same reason.

Start with one default pipeline:

  • New lead: contact exists but has not been qualified.
  • Qualified: the opportunity fits your service and budget range.
  • Discovery booked: a call or meeting is scheduled.
  • Proposal sent: an estimate, proposal, or document has been shared.
  • Negotiation: terms, scope, or timing are being discussed.
  • Won: the customer accepted and delivery can start.
  • Lost: the opportunity is closed without a sale.

Add a second pipeline only when the sales process is truly different, such as one pipeline for service retainers and one for productized checkout offers.

Daily Operating Habit

At the end of each day, review open deals and confirm every deal has:

  • A current stage.
  • A deal owner.
  • A value or expected revenue.
  • A next task or follow-up date.
  • A linked contact or account.
  • Notes explaining the latest customer context.

If a deal has no next task, it is not really being worked. Add a task or close the deal as won/lost so the pipeline reflects reality.

Weekly Pipeline Review

Each week:

  1. Review deals without next tasks.
  2. Check stale stages.
  3. Confirm high-value expected close dates.
  4. Move accepted deals to won and rejected deals to lost.
  5. Create follow-up tasks for active opportunities.
  6. Review reports after cleanup, not before.

Reporting

Use CRM reports and dashboard widgets to review pipeline value, stalled deals, won/lost outcomes, and owner workload. If reports look wrong, check that deals are linked to the correct pipeline and that users are moving deals to won or lost instead of leaving them in active stages.

First Pipeline Review

After building the pipeline, add a small set of real or test deals and run one review with the sales owner. Confirm every stage has clear exit criteria, each deal has an owner and next task, and stale deals have a cleanup path.

If the team cannot decide where a deal belongs, adjust the stage names before importing or creating more deals.

On this page