Consulting Sales Pipeline Template
A pipeline for scoped engagements, where the real risks are writing proposals with no budget line and winning work you cannot staff.
The stages
Each stage states what is true about a deal sitting in it, and the one testable thing that has to happen before it moves. If the exit criterion is not met, the deal does not advance, whatever the rep believes.
Opportunity Identified
10% probability7 to 21 daysYou have spotted a reason this organisation might buy: new leadership, a regulatory deadline, a funding round, a programme that visibly failed.
You have named the organisation, the likely executive sponsor, and the specific trigger event, and you have a route to that sponsor through a warm introduction or a direct response.
Exploratory Conversation
20% probability7 to 21 daysA first conversation with the sponsor. You are testing whether the problem is real and whether anyone has money for it.
The sponsor has described the problem in their own words, quantified the cost of leaving it alone, and confirmed there is either an existing budget line or a named route to creating one.
Scoping Workshop
35% probability10 to 30 daysA working session with the sponsor and their team to agree what the engagement would actually cover. This is real consulting value, delivered before the contract.
A written problem statement and success criteria are agreed, a rough order of magnitude fee has been shared verbally, and the sponsor has named a date they want the full proposal by.
Proposal Submitted
50% probability14 to 45 daysA phased proposal with named team members, a delivery approach and a fee structure is with the client.
The proposal has been delivered to both the sponsor and the budget holder, with a phased scope, named consultants, and either day rates or a fixed fee with clear assumptions.
Procurement or Panel Review
65% probability21 to 60 daysPeople who have never met you are comparing you against two other firms on a scoring matrix. Relationships help less here than paperwork.
You are confirmed on the approved supplier list or framework, or the panel has told you that you are in the final shortlist with a decision date.
Negotiation and Terms
80% probability10 to 30 daysFee, payment schedule, IP ownership, liability caps and cancellation terms. Scope tends to shrink here while the fee expectation does not.
Rates, payment milestones, IP terms and the cancellation clause are agreed in writing, and any scope reduction has been repriced rather than absorbed.
Signed and Resourced
100% probability5 to 15 daysThe engagement is won and the delivery team is committed. A win you cannot staff is a reputational cost, not a revenue event.
SOW countersigned, PO number issued, start date agreed, and the named consultants blocked in the resourcing plan for the engagement duration.
Fields worth tracking
Stages tell you where a deal is. These fields tell you whether it is any good. Add them as custom fields on the pipeline, and make the ones that gate a stage required.
Fixed fee, time and materials, or retainer. Each has a different margin profile and a different cash curve, and blending them in one pipeline hides which kind of work is actually profitable.
The deal value is a product of these two, and both move independently during negotiation. Storing them separately shows you whether you lost value on rate or on scope.
Direct award, existing framework, or open tender. The route sets the realistic cycle length far more than deal size does, and it is the field that makes your close dates credible.
Often two different people. Consulting deals stall for months when the proposal has only ever been read by the sponsor, who cannot approve the spend.
The link between sales and delivery. Without it, you win three engagements starting the same Monday and have to tell one of them no.
Automations worth building
A pipeline that only stores data is a spreadsheet with a nicer view. These are the three workflows that make this pipeline maintain itself.
On Proposal Submitted, create a follow-up task for day 3 to the sponsor and day 10 to the budget holder, and notify the partner on the account if the deal has not moved by day 21. Consulting proposals die in silence more than in rejection.
Run a workflow that flags any deal above 60% probability whose required start date falls within three weeks, so delivery can provisionally hold capacity before the signature rather than after it.
When a deal moves to Signed and Resourced, auto-create the delivery record, copy across the scope and success criteria fields, and generate the kickoff and milestone tasks so nothing is retyped between sales and delivery.
Common mistakes with this pipeline
A good consulting proposal costs days of senior time. Producing one for a sponsor who has an interesting problem and no money is the single largest hidden cost in most practices. The exploratory-call exit criteria exists to stop exactly this.
Scoped engagements routinely shrink by 20% to 40% in procurement. If you forecast the number on the proposal, you will consistently miss even on deals you win. Track proposed value and expected value as separate fields.
Sales and delivery running on separate systems means the pipeline has no idea what the bench looks like. Winning work you cannot staff for eight weeks damages the relationship more than losing it would have.