Set up a Pipedrive pipeline a service team will actually keep updated

By Marcus Webb · A tutorial — setup guidance; Pipedrive plan facts verified October 23, 2026 · Hands-on testing in progress — see note below

Every abandoned CRM died the same death: the pipeline was designed for how the company wishes it sold, not how it does. The team stopped updating in week three, and the forecast became fiction. This setup starts from what a service business actually does — a conversation, a proposal, a signature — and adds nothing Pipedrive does not need.

Step 1: five stages, and no sixth

Create exactly these stages on the default pipeline:

1. Qualified — they have a problem, a budget owner, and a timeline. Nothing enters the pipeline before this is true; "maybe someday" contacts live in contacts, not deals.
2. Scoping — you are working out what the work is. The deal's value is still a guess, and that is fine; update it as you learn.
3. Proposal sent — a document exists, with a price and a date on it.
4. Negotiation — they replied with something other than yes. (If they went silent, it stays here — silence is a negotiation state.)
5. Won / Lost — Pipedrive's built-in endings, plus a mandatory Lost reason (Step 3).

The discipline that keeps this alive: a deal moves the day the evidence exists, not when you feel optimistic. Proposal sent means the email went out, not that you drafted it. We use the same evidence-over-vibes rule throughout our Pipedrive pricing breakdown because it is the difference between a pipeline and a wish list.

Step 2: three fields, not thirty

Pipedrive will happily let you build a forty-field monster; every field is a question your future self must answer to move a card. Add only:

• Lead source (select: Referral / Outbound / Inbound / Repeat) — the one field that tells you where to spend next quarter.
• Expected close (date) — it powers Pipedrive's forecast view; keep it honest even when the honest answer is embarrassing.
• Proposal date (date) — it makes stage 3 measurable: proposals sitting there for 21 days are a different problem from proposals sitting for 5.

Everything else — company size, industry, "temperature" — is a field you will maintain for a fortnight and then resent forever. Delete before you decorate.

Step 3: make Lost reasons mandatory

In pipeline settings, require a lost reason on any lost deal, with four options: Price, Timing, Lost to competitor, No decision. The fourth is the one that pays for the feature: service businesses lose more deals to "no decision" than to competitors, and the only way to see that pattern is to record it. This single setting converts your pipeline from a tracker into next year's strategy.

Step 4: the three automations worth their ops budget

Pipedrive's automation rules are quota-free on the plans we verified, but restraint still applies. Build exactly three:

• Stage entry → task: when a deal enters Proposal sent, create a follow-up task in 5 business days. The silent-deal problem is solved by machinery, not memory.
• Won → project handoff task: create a "kickoff" task assigned to delivery. Sales-to-delivery handoff is where service businesses drop balls; a task is the cheapest possible baton.
• No activity → flag: a deal with no activity for 14 days gets a "stale?" task on the owner. The pipeline audits itself.

Resist automating anything you cannot explain in one sentence. Complex rules fail silently, and a silently wrong pipeline is worse than a manually updated one.

Step 5: the one-per-day rule

Adopt this as team law: update the pipeline once a day, all at once, in five minutes — never continuously, never "when something happens". Batch updating is the only habit that survives a busy month, and the pipeline's value compounds exactly as long as the habit does. If the team cannot keep the rule, the pipeline has too many stages or too many fields; fix the design, not the people.

Plan notes and costs

None of this setup needs anything above Pipedrive's cheapest tier: multiple pipelines, custom fields, lost reasons and automation rules as configured here are within the entry plan's scope, and there is no free plan — the 14-day trial is the evaluation window (plan facts and add-on pricing verified in Pipedrive pricing explained). Seat-count the team honestly before subscribing; the per-seat cost is the whole bill, and the seat rules vendors do not advertise are in seat minimums nobody budgets for. For how this setup compares to staying in Gmail, see Pipedrive vs Streak.

What we cannot verify

The setup above reflects Pipedrive's feature set as publicly documented and our hands-on familiarity with the product's general design; exact menu labels move between releases, so treat step instructions as intent, not pixel paths. We verified plan scope statements (no free plan, 14-day trial, entry-tier features) against Pipedrive's pricing pages on October 23, 2026 — feature availability per tier can change, and regional plans differ. The five-stage and one-per-day prescriptions are our methodology, not vendor guidance. See How We Test.