Disclosure: The Pipedrive link here is a plain official-product link, not an affiliate tracking link. See our affiliate disclosure for details.
For agency client work, define Pipedrive stages around observable progress: a booked discovery call, completed scope, delivered proposal, client review, and contract preparation. Pipedrive describes a customizable pipeline on its official product page, accessed September 6, 2026. The stage names below are an editorial example to adapt to your sales process, not a claim about Pipedrive’s default stages.
Why agency sales don’t fit a product pipeline
Selling client services can involve a discovery or scoping phase without a product-demo equivalent, a custom proposal, and a separate client approval process. A useful pipeline distinguishes work your team must finish from decisions the client must make. Stage names alone are insufficient unless everyone agrees what evidence permits a move.
A deal-stage set built for agency client work
Start with Inquiry, Discovery Call Booked, Scoping, Proposal Sent, Client Review, and Contract Sent as a proposed working sequence. Agree separately how the team records completed and unsuccessful opportunities. Use the following evidence rules to test whether the stages describe your actual work.
| Proposed stage | Evidence needed to enter | Next action to record |
|---|---|---|
| Inquiry | A specific request for services has arrived | Assign someone to check fit and arrange discovery |
| Discovery Call Booked | The prospect has agreed to a meeting time | Prepare questions about scope, budget, and decision process |
| Scoping | Discovery has supplied enough information to draft an engagement | Assign the outstanding scope or estimate work |
| Proposal Sent | The proposal was delivered to a named contact | Confirm receipt and agree a review date |
| Client Review | The client confirms the proposal is being reviewed | Record the reviewer and agreed next contact date |
| Contract Sent | The contract was delivered for approval or signature | Record who must respond and any remaining questions |
A proposal sent on Tuesday does not automatically become Client Review on Friday. Without confirmation, keep the last evidenced stage and record the unanswered follow-up separately. If the client requests a revised scope, assign that work explicitly instead of leaving the deal labeled as waiting entirely on the client.
Custom fields that matter for agency deals
Consider engagement type, estimated project start date, and referral source as custom fields. Keep start date separate from the expected close date. These are suggested fields, not mandatory product requirements. Pipedrive’s spreadsheet import guide, accessed September 6, 2026, says to create custom fields before import when existing fields do not match your data.
Automations worth evaluating after the manual workflow works
First test two routines manually: schedule the agreed follow-up when a client starts reviewing a proposal, and notify the delivery owner when an engagement is confirmed. Pipedrive’s official product page describes workflow automation, but verify the available triggers, actions, and plan requirements in your account before relying on either routine as an automation. A timed reminder should prompt a review; it should not imply that the client has made progress.
Reporting for an agency sales manager
In the weekly review, separate deals waiting on your scoping or proposal work from deals awaiting a client response. For each stalled opportunity, check its evidence, owner, and next action. Use that review to decide whether you need more delivery input, a clearer proposal, or a follow-up, rather than treating every aging deal as the same problem.
Rolling this out to the team
Test the proposed definitions against five existing opportunities before changing the live pipeline. Have two teammates classify the same deals independently; disagreements reveal unclear entry rules. Resolve those rules before importing or remapping records. If importing a spreadsheet, review field mapping and the preview, including linked contacts, as described in the official import guide, accessed September 6, 2026.
The bottom line for agency pipelines
A shared spreadsheet and calendar are enough when one owner can reliably maintain stage evidence and follow-up dates. Consider a paid CRM when multiple teammates need a shared pipeline, contact history, and coordinated activities. Test these stage rules with a small sample in Pipedrive, then confirm the plan includes the features your team actually needs before paying. Use the new-rep onboarding checklist to teach the agreed definitions.
Related reading: Pipedrive vs HubSpot for a Small Sales Team: Which Fits 5-15 Reps? and Pipedrive Onboarding Checklist for New Sales Reps on a Small Team.
Leave a Reply