Close
Close starts once a lead has passed qualification and is a deal on the board. SPICED is why the customer would buy, and it stays on the deal. Closing a deal refers to moving that deal through the stages below until a purchase order is received.
A deal is 100% only at PO received.
Why use stages?
The stage is the shared record of how far a deal has got. The percentage on it is the chance of close used in a weighted pipeline. Two people looking at the board should see the same progress, because the stage matches what has happened, not how the last meeting felt.
Each week in the pipeline review, confirm SPICED still holds — especially the impact number and the critical event date. A passed date with no replacement, or an impact figure that was never made specific, comes off the board.
Stages
Record the stage on the deal in Pipedrive.
| Stage | Chance of close | What is true |
|---|---|---|
| Qualified Opportunity | 10% | The lead has passed qualification and the deal is on the board. SPICED is filled in. |
| Business Case Development | 20% | Someone on the customer or partner side is actively working on the business case with us. |
| Solution Validation | 40% | A proof of concept or evaluation is underway, against written decision criteria. |
| Commercial Proposal Sent | 50% | A commercial proposal has been sent, the person who signs is named, and the steps toward the critical event are known. |
| Procurement & Contracting | 80% | Procurement, legal, or security review has started, and we know how long it takes. |
| Signature Pending | 90% | The terms and required approvals are agreed, and the contract is awaiting signature. |
| PO received | 100% | A purchase order has been received. The deal leaves the open pipeline and its deal value counts as new ARR. |
Shifting stage
In the weekly pipeline review, move the deal to the stage that matches what has happened. Leave it where it is until that is true.
Qualified Opportunity
Move here when the lead has passed qualification and the deal is on the board. SPICED must be filled in.
Business Case Development
Move here when someone is working on the business case with us. A demo can support that work. On a partner deal, that someone can be the partner.
Solution Validation
Move here when a hands-on evaluation is underway. Before it moves, write the decision criteria: what a yes has to satisfy. Coverage evidence, a saving, architect time returned, or surviving a consultancy review are the usual answers.
Ask:
- "What does a yes have to satisfy?"
This is the one fact SPICED does not capture at registration. It is required for this stage, not before the deal is on the board. Record it in the Decision Criteria field on the deal.
Commercial Proposal Sent
Move here when a commercial proposal has been sent, the person who signs is named — Simon the CISO, or the CIO or CFO who owns the budget — and the steps from here to the critical event are known. The champion can find that name and test the case internally. A meeting between us and the signer can come later.
If the steps take longer than the critical event allows, say so in the review and leave the deal at Solution Validation.
Procurement & Contracting
Move here when procurement, legal, or security review has started. Paige the Procurement Officer's path needs durations, and those durations need to fit the critical event.
Signature Pending
Move here when the terms and required approvals are agreed, and the contract is awaiting signature. The deal is still open at 90%.
PO received
Move here when a purchase order has been received. The deal is then 100%, and its deal value counts as new ARR.
Recording it in Pipedrive
The stage on the deal is the record. SPICED fields are already on the deal from qualification. Add one more field, on the deal only, in Company settings → Data fields:
| Field label | Field type | What goes in it |
|---|---|---|
Decision criteria | Large text | What a yes has to satisfy. Required before the deal moves to Solution Validation. |

