SPACED methodology

What is the SPACED methodology?

SPACED is a six-letter B2B sales qualification framework — Situation, Problem, Articulation, Cause, Effect, Decision. It was developed for technical and consultative selling contexts where BANT and MEDDPICC are used for qualification but don't adequately capture the diagnostic depth needed to understand complex problems before prescribing solutions.

The framework is less widely taught than MEDDPICC or SPICED but is used in industries like enterprise software, cybersecurity, data infrastructure, and professional services where the prospect's problem has multiple symptoms, requires root-cause identification, and where the wrong diagnosis means selling the wrong solution. SPACED forces the rep to articulate — out loud, in the call — the causal chain from root cause to business effect before moving to Decision.

For a technical AE selling complex infrastructure or security solutions, SPACED adds a layer of diagnostic rigor that BANT misses entirely and that MEDDPICC handles only implicitly through the Identify Pain letter. The Cause and Effect letters, in particular, are SPACED's differentiating feature: they require the rep to understand not just what the problem is but why it exists and what it costs.

The six SPACED letters

• Situation — the prospect's current operating context: team structure, tools, processes, scale. Same as SPICED's Situation and SPIN's Situation questions. Keep brief — capture, confirm, move on.
• Problem — the specific issue the prospect is experiencing. More precise than 'challenge': a named, observed problem with a frequency and a visible effect.
• Articulation — the rep explicitly restates the problem back to the prospect in precise language and gets confirmation. 'So the problem is that your fraud models retrain weekly but your transaction volume requires daily retraining — and that lag is causing false positive rates above your SLA threshold. Is that right?' This lock-in step prevents the discovery from being based on misinterpretation.
• Cause — why the problem exists. Root cause, not symptom. 'The lag exists because your current vendor's retraining pipeline doesn't support the throughput at your transaction volume.' Without Cause, the solution risks addressing a symptom and missing the root.
• Effect — the quantified business impact of the problem going unresolved. Dollar cost, operational cost, strategic risk. Same as SPICED's Impact and MEDDPICC's Metrics.
• Decision — the decision process, timeline, stakeholders, and constraints. Same as MEDDPICC's Decision Process and SPICED's Decision fields.

When to use SPACED vs MEDDPICC vs SPICED

SPACED is most useful when the selling motion requires technical diagnosis before prescription — complex data, security, infrastructure, and professional services sales. The Articulation and Cause steps are SPACED's differentiators: forcing the rep to restate the problem precisely and identify root cause ensures the proposal is solving the right thing.

For qualification-focused enterprise sales ($100K+ ACV, committee buying, long procurement), MEDDPICC's eight letters cover more ground on the commercial side. For modern SaaS mid-market deals ($10–100K ACV), SPICED is faster. SPACED sits in the overlap — best when discovery accuracy is as important as qualification rigor. Some technical AE teams run SPICED for qualification and SPACED for discovery depth simultaneously.

How to run a SPACED discovery

1. Situation — confirm the operating context in 3–5 questions. Don't learn from scratch; confirm your pre-call hypothesis.

2. Problem — 'Where does the current setup break down most?' Surface the named problem with frequency. 'How often does this happen?'

3. Articulation — stop and restate. 'So what I'm hearing is [precise restatement of problem]. Is that an accurate description?' Get a verbal yes. Fix misinterpretation now, not in the proposal.

4. Cause — 'Why does this happen?' Drill the root cause. Don't accept 'it's a technology limitation' — ask what specifically causes it. The rep who understands Cause sells the right solution; the rep who skips it sells the wrong one.

5. Effect — quantify the cost. 'What does this cost you in dollars or hours per month?' Lock in the number.

6. Decision — map the process. 'Walk me through how you'd make a decision on this.' Capture names, steps, timeline.

Common mistakes with SPACED

1. Skipping Articulation because it feels awkward. Restating the problem sounds obvious but catches misinterpretations that would otherwise only surface in the proposal. The 60-second awkwardness saves 3 weeks of rework.

2. Accepting surface-level Cause. 'It's a data quality issue' is not Cause. 'The data quality issue exists because your ingestion pipeline doesn't validate against your master record at the time of ingest' is Cause. Push.

3. Running SPACED on non-technical deals. For straightforward SaaS sales where the problem is well-understood, SPACED's depth is overkill. Use SPICED or MEDDPICC.

How Gangly supports SPACED-style discovery

Gangly's Call Prep Engine generates a SPACED-calibrated discovery guide when the deal is flagged as technical or infrastructure. During the call, Live Call Coach watches for the Articulation moment — when the rep should restate and confirm — and prompts it if the rep moves past Problem without pausing to confirm.

Post-Call Notes captures the Cause and Effect fields verbatim from the transcript so the proposal team has root-cause language that matches what the prospect actually said, not a paraphrase.

See how Call Prep Engine works →

Frequently asked questions