Checklist: SPICED Sales
-p-1600.avif)
"With Weflow, we’re now capturing all relevant activities and have full transparency into the performance of each sales rep. It’s a game changer."
%201.svg)
"Weflow gives us better visibility and predictability of our business."
"Weflow eliminated the need for our VP to ask, ‘Did you follow up with that deal?’. It tracks customer interactions automatically, creating a framework that drives accountability across the team."
"None of the other tools gave us a solution like Weflow. From the beginning, we had a really smooth process."
.webp)
"I had a first introductory call with Weflow. I think I was sold after 15 minutes. There’s no question that the people at Weflow understood the problems that we were trying to solve."
"I’ve worked with Gong before, but Weflow’s simplicity and real-time sync are game-changing."
.webp)
"We use Weflow to auto-capture activity data, run deal reviews, and analyze our pipeline to inform our forecast. Being able to spot deal risks early has improved win rates and pipeline health."
.svg){kind=icon}
.svg){kind=icon}
.svg){kind=icon}
.svg){kind=icon}
.svg){kind=icon}
What's Inside
Discovery qualification inputs
- Situation prompts that capture team footprint, office headcount, and current sales stack before pain discovery begins
- How to pair firmographic context with operational detail to qualify accounts against your ICP in the first call
- A repeatable top-of-funnel structure that replaces unstructured rep notes with consistent qualification data across the team
Pain and impact mapping
- Pain questions that surface team-level challenges around onboarding, ramp, and the gaps in current sales enablement workflows
- Impact prompts that connect slow rep ramp directly to missed revenue targets and quota attainment risk
- Downstream consequence probes covering recruiting visibility, remote collaboration, and the operational cost of doing nothing
Buying process signals
- Critical Event questions that force reps to document the deadline driving urgency and the cost of missing it
- Decision questions that uncover prior purchases of similar products and map the internal buying process end to end
- Stakeholder prompts that pull Legal, Security, and IT into the deal early instead of late-stage surprises
Daniel Schemmert
Daniel Schemmert is the Head of Growth at Weflow, where he's built the GTM engine from scratch. He spends valuable time talking to RevOps leaders about how they run pipeline, forecasting, and Salesforce. He's also the co-founder of RevOps Chat, the Slack community where 1,000+ RevOps practitioners share what's actually working inside their revenue orgs.
Go Deeper
SPICED Sales Methodology: Discovery Questions and Prompts by Stage
#88 Rolling Out SPICED across a 750-Person Sales Org
Sales Methodology Guide & Checklists
Frequently asked questions
What is SPICED and how is it different from MEDDIC or BANT?
SPICED is a discovery and qualification framework built around five stages: Situation, Pain, Impact, Critical Event, and Decision. Where BANT focuses heavily on budget and authority upfront, and MEDDIC leans into economic buyers and decision criteria, SPICED puts deliberate emphasis on Impact and Critical Event — meaning you're building a business case and surfacing urgency in the same motion. It's particularly well-suited for SaaS sales cycles where the "why now" is as important as the "why us."
Do I need a specific CRM or sales tool to run SPICED, or can I use this with whatever my team already has?
SPICED is methodology-first — it's a set of questions and a mental model, not a software dependency. You can run it in Salesforce, HubSpot, a Google Doc, or a paper notepad. The checklist maps cleanly to deal stages or opportunity fields in most CRMs if you want to formalize it, but that's optional.
Which of the five SPICED stages do most sales reps skip or rush through, and should I prioritize those in coaching?
Impact and Critical Event are the two most commonly glossed over. Reps tend to move from Pain straight to pitching, skipping the step where you quantify what fixing the problem is actually worth to the prospect. Critical Event gets skipped because asking "what happens if you don't have a solution by that date?" feels confrontational — but it's the question that separates real pipeline from wishful pipeline.
What information should a rep have before walking into a discovery call if they want to use this checklist effectively?
At minimum, know the prospect's team size and current sales stack before the call — the Situation questions ("How many sales reps work in your office?" and "What sales tools are you using?") land better as confirmations than cold asks. A quick LinkedIn and website scan gets you 80% of the way there. Going in blind wastes the first five minutes of every call on basics you could have already known.
How do I know if a rep is actually running SPICED well versus just checking boxes?
The tell is whether they can articulate the prospect's Critical Event and its consequence in their own words after the call. If a rep can't answer "what happens if they don't buy by X date," they didn't get there — they just moved on. Review call recordings against the Impact and Critical Event questions specifically; those two stages are where qualification depth shows up most clearly.
How often should my team revisit SPICED qualification on an active deal, or is it a one-time discovery exercise?
Treat it as a living document on each deal, not a one-time intake form. Critical Event timelines shift, decision processes change when new stakeholders get involved, and the Impact framing often needs to be re-anchored as you get deeper into Legal or Security conversations. A quick SPICED review at each stage gate — especially before a proposal goes out — catches deals that have quietly gone sideways.
-p-1600.avif)
-p-1600.avif)