Deal Qualification
A lead in Pipedrive is a conversation. A deal is a conversation that has passed the qualification bar presented here and has been placed on the deal board. We use SPICED to make that decision. After the deal is on the board, that same diagnosis is what we sell against, and what the weekly pipeline review checks.
Why use a qualification framework?
Left to individual judgment, the deal board fills up with accounts we have spoken to, and risk introducing inconsistency in deal stages and sizings.
A qualification framework is the shared definition of a real opportunity, so registration does not depend on who took the meeting. The output is a short diagnosis the customer would recognise as their own. In the weekly pipeline review, a missing date or a missing cost is visible. "Good meeting" is not.
SPICED does not produce a score, and we do not compare a total against a threshold. Each line is either specific enough to register, or the conversation stays a lead.
What SPICED is
SPICED is the diagnosis we complete before a deal exists. Each letter records a fact about the customer: their estate, the pain, the cost of it, the date that forces a decision, and who decides. What a yes has to satisfy — the decision criteria — is not a sixth letter. It is required later, before a deal moves to Solution Validation, and is covered in Close.
| Letter | What we have to know | In our motion |
|---|---|---|
| Situation | Who they are, and what the estate actually looks like | ICP: $1bn+ / 10,000+ enterprise, dozens to 100+ tools, multi-vendor |
| Pain | The picture they cannot produce | Licensed vs deployed vs in use, overlap, or gaps against NIST, ATT&CK, or their own control set. Could be linked to commercials and renewals or knowledge lost within the organisation |
| Impact | The business consequence, with their number | Security architect hours on renewal decisions, product research, and coverage mappings. Also redundant spend, a renewal they cannot defend, a consultancy invoice, or board/audit exposure |
| Critical Event | The date, and what happens if they miss it | Consultancy review, board or audit, a regulatory deadline, or an estate merge, budget/planning cut-offs. |
| Decision | Who champions it, and who has to sign | A named champion in the security organisation, a hypothesis for who signs, and who owns the contract clock |
Working through Partners
The same five facts apply when the introduction comes through a partner. A partner's lead is not a qualified deal. We still complete SPICED ourselves before it goes on the board.
On a direct deal you hear the facts from the end user. On a partner deal you can hear them from the partner, and a second-hand answer counts, so a meeting with the end user is not required. Where the partner cannot answer yet, the conversation stays a lead and stays off the board.
When to ask, and what has to be true
Ask the questions in this order. You can cover more than one step in a single meeting when the customer is ready. You register the deal only when every step has passed.
1. First conversation — Situation
Do this on the first real conversation. The aim is to learn whether they are the ICP and whether a pain is even present. They stay a lead either way.
Ask:
- "Walk me through the security estate. Roughly how many tools, and who can actually list them?"
- "How do you manage contract renewals and commercials today?"
- "If someone asked today for what you own, what overlaps, and what is missing, what would you hand them?"
- "What frameworks do you use to govern your estate, and how do you map your capabilities against those frameworks?"
- "How do you track commercial agreements and renewals in your security estate?"
Passes when the account is in the ICP and the estate is a multi-vendor portfolio they cannot describe from one system. Record the draft on the lead. Do not create a deal.
Stops here when they are outside the ICP, or the estate is already described and governed. Keep the relationship if it is worth having. It does not go on the board.
2. Discovery — Pain, Impact, Critical Event
Do this in discovery, once Situation has passed. This is the substance of qualification. Most conversations that feel promising and are not deals fail here.
Pain. Ask:
- "When a board, an audit, or a consultancy asks for that picture, what do you have to assemble, and how long does it take?"
- "Where are you paying for two products that do the same job, or for a license that is not in use?"
Passes when they cannot evidence the estate: overlap, gaps, or licensed vs deployed vs in use. The Problem Statement is the test for whether that gap is a reason to buy. "Interested in visibility" or "wants a demo" does not pass.
Impact. Ask only after the pain is specific. Press for the architect time, even when a spend figure is already on the table:
- "How many days are your security architects spending on renewal decisions, on researching products, and on building coverage mappings?"
- "If that stays this ways, what else does it cost? Spend you cannot defend, a renewal about to lapse into auto-renew, a consultancy invoice, or exposure in a board or audit?"
- "What figure is attached to that?"
Passes when there is a consequence with a number — architect hours, spend, or a named exposure. A tool count is Situation, not Impact.
Critical Event. Ask in the same conversation:
- "What date does this have to be answered by?"
- "What happens if that date arrives and the answer is still a spreadsheet?"
- "What deadlines are you operating with for this project?"
Passes when there is a real date and a consequence of missing it. No date means no deal, however strong the pain sounds.
3. Before Registration — Decision
Do this before you convert the lead, at the end of discovery or in a short confirmation. Full access to the signer is not required yet.
Ask:
- "Who owns this day to day and will push for an answer?"
- "Who has to defend the number, or sign the spend?"
- "Who else has to be in the room — architecture, procurement?"
Passes when there is a named champion — usually Harry the Head of Cyber or Sasha the Security Architect — and a hypothesis for who signs: Simon the CISO, or the CIO / CFO who actually owns the budget.
Paige the Procurement Officer owns the contract clock, and may be involved in hands-on discussions around commercials with ESProfiler. She does not have to be in the room yet. Write those names on the lead so the next conversation knows who is missing.
Registration
Register the deal when Situation, Pain, Impact, Critical Event, and Decision are each specific, and you could read them back to the customer and have them agree.
Converting the lead to a deal is putting it on the board. Fill the deal fields in that same action. A deal with a blank line should not be saved into the pipeline. How that deal gets to a signature is Close.
Weekly Pipeline Review
In the weekly pipeline review, read the five fields for each deal. Do not reconstruct the opportunity from the activity feed - the fields should be complete and accurate.
- Update the fields when the customer corrects the pain, the number, the date, or the people.
- If the critical event date has passed and there is no replacement date, take the deal off the board.
- If Impact was a placeholder and later discovery has not made it specific, take the deal off the board.
Taking a deal off the board means moving it out of the pipeline (lost, or back to a lead if the conversation is still alive). The account can return when the five lines are true again.
How a passing deal reads
On the board. A 12,000-person bank. Security cannot show overlap or what is actually in use ahead of a portfolio review. About £6m of renewals sit inside the review window, and a consultancy is already assembling a point-in-time inventory. The readout is in November; if they miss it, renewal leverage is gone. The Head of Cyber owns the recommendation. The CISO has to defend it. Procurement owns the notice dates.
Stays a lead. A security architect at a 2,000-person company asked for a demo after a webinar. There is no review date, no renewal figure, and no one who has to sign.
Recording it in Pipedrive
The system of record is a set of custom fields on the deal. The deal list and the board should show the date and the impact value, so review does not depend on opening every card.
Draft the same fields on the lead while you are still in steps 1–3. Pipedrive does not copy lead custom fields onto the deal when you convert, so you copy the five lines across yourself at registration. After that, the deal fields win. Do not keep a second version only in a note.
Fields
Create these on both Lead and Deal, in a field group named SPICED. In Pipedrive: Company settings → Data fields.
| Field label | Field type | What goes in it |
|---|---|---|
SPICED — Situation | Large text | ICP facts and what the estate looks like |
SPICED — Pain | Large text | The picture they cannot produce, in their words |
SPICED — Impact | Large text | The consequence of leaving it unsolved |
SPICED — Impact value | Monetary | Their figure, in the currency they used to measure the impact |
SPICED — Critical event date | Date | The date that forces a decision |
SPICED — Critical event | Large text | What the date is, and what happens if they miss it |
SPICED — Decision | Large text | Named champion, who signs, and who else is in the room |
Mark the seven deal fields as required, so a new deal cannot be saved with them empty. Backfill any deal already on the board. If a current deal cannot be backfilled, it does not meet the bar and comes off the board.
What to show on the board
On the deal list, show SPICED — Critical event date and SPICED — Impact value as columns. On the pipeline, add those two fields to the deal card.
Who checks
Whoever runs the weekly pipeline review checks the columns first. A blank required field, a date that has passed, or an impact value with no sentence in SPICED — Impact means the deal is not qualified and should be removed in that review.

