How to Use the SPICED Methodology? [Sample Scripts Included]

Akash Bansal
June 29, 2026
Table Of Contents

Every salesperson has a humbling rejection story. Mine involves a complex B2B proposal, months of planning, a seemingly flawless presentation, and then… radio silence. Emails bounced, calls went unanswered, and finally, a rejection without explanation (We all know the pain).

Weeks later, I ran into an old colleague who knew someone on the inside. Turns out, a decision-maker I missed, torpedoed the deal with concerns about complexity. My solution, finely tuned for everyone else, hit a wall I didn't even know existed. 

But hey, every misstep's a lesson, and this one led me to discover a powerful framework that could have saved the day: SPICED.

What Is the SPICED Selling Methodology?

SPICED is a sales methodology created by “Winning by Design,” a sales consulting and services company. SPICED stands for Situation, Pain, Impact, Critical Event, and Decision — it is a framework designed to understand: 

  • a prospect’s current circumstance, 
  • the challenges that brought them to you, 
  • the impact your business may have on them
  • deadline to achieve that impact, and
  • procedure or committee involved in the decision-making process

SPICED Sales Framework: Step-by-Step Breakdown

Let’s see what each letter in the SPICED acronym means in detail.

1. Situation (Understanding Your Prospect's Landscape)

  • Goal: Gather comprehensive information about your prospect's company and its current situation.
  • Action Steps: Don't solely rely on their website and LinkedIn. Focus areas:
    • Strategic Moves: Track recent announcements, press releases, and event participation to understand their focus and goals.
    • Fresh Developments: Analyze news, blogs, and social media for product launches, partnerships, or leadership changes.
    • Potential Hurdles: Identify potential challenges by looking at industry trends, customer feedback, and competitor strategies. Consider what gaps your prospect might be trying to fill.
  • Challenge:  Information overload! Prioritize the most relevant insights and weave them into your conversations naturally.
  • Example Script: "I noticed your recent announcement regarding expansion into [mention new market].  Considering industry trends in [mention relevant industry trend], how does this expansion align with your overall growth strategy?"

2. Pain (Uncovering Your Prospect's Struggles)

  • Goal: Identify the specific challenges hindering your prospect's success.
  • Action Steps:
    • Active listening: Pay close attention to their concerns during conversations.
    • Open-ended questions: Ask questions that go beyond "yes" or "no" answers, like "What are your biggest frustrations with [current process]?"
    • Situational probing: Use information from the Situation step to ask targeted questions, like "Given your expansion plans, how is [current pain point] impacting your resource allocation?"
  • Challenge: Prospects might downplay their problems. Ask follow-up questions to get to the root cause of their pain.
  • Example Script: "During our conversation about scaling your team, you mentioned challenges with onboarding new hires. Can you elaborate on the specific bottlenecks you're experiencing?"

3. Impact (Demonstrating the Value You Deliver)

  • Goal: Show how your solution directly addresses their pain points and creates positive outcomes.
  • Action Steps:
    • Quantify the impact: Translate the resolution of their pain into concrete benefits. Use metrics, case studies, or industry benchmarks.
    • Focus on outcomes, not features: Explain how your solution helps them achieve their desired results, not just the functionalities it offers.
  • Challenge: Avoid generic claims. Tailor your impact statement to their specific situation and pain.
  • Example Script: "By streamlining your onboarding process with our platform, we've helped similar companies reduce time-to-productivity by 20%. This translates to faster project execution and time to value."

4. Critical Event (Identifying the Urgency for Change)

  • Goal: Uncover the deadline or event that drives their need for a solution. Here’s a graph depicting how critical events carry over time.

Graph showing how critical event carries over time
Source
  • Action Steps:
    • Ask urgency-driven questions: "When do you expect these onboarding delays to become a critical business issue?" or "Is there a specific deadline for achieving your expansion goals?"
    • Listen for urgency cues: Pay attention to phrases like "as soon as possible" or "we need a solution in place by [date]."
  • Challenge: Don't push for a forced deadline. Focus on understanding their genuine sense of urgency.
  • Example Script: ""You mentioned wanting to improve team collaboration on client projects.  Is there a specific upcoming project launch with tight deadlines that could benefit from a more streamlined communication and workflow process?"

5. Decision (Understanding the Buying Process)

  • Goal: Gain insight into the decision-making process and key stakeholders involved.
  • Action Steps:
    • Identify decision-makers: Ask questions like "Who will be involved in evaluating potential solutions?" or "Who ultimately signs off on these types of purchases?"
    • Understand the buying process: Learn about their typical timeline, evaluation criteria, and potential approval hurdles.
  • Challenge: Navigating complex buying committees. Be prepared to cater your communication and presentations to different stakeholders.
  • Example Script: "To ensure we deliver a solution that aligns with everyone's needs, can you walk me through the typical process for evaluating new vendors in your company?"
  • Pro tip: Build relationships with internal champions who can be advocates for your solution.

Who Can Use SPICED?

The SPICED Sales Methodology is for any sales team looking to improve their understanding of customer needs and close more deals.  It can be particularly useful for teams that practice solution selling or needs-based selling.

Here's a breakdown of who can benefit from SPICED:

  • Sales reps:  SPICED equips reps with a framework to ask the right questions, uncover prospect challenges, and tailor solutions for maximum impact.
  • Sales managers:  The framework  provides a common language for communication  across teams and helps managers coach reps more effectively.
  • Marketing teams: By understanding the Situation, Pain, and Impact aspects of SPICED, marketing can craft messaging that resonates with target audiences.
  • Customer success teams:  SPICED can aid customer success teams in understanding the original reasons a customer bought the product and ensure they continue to receive that value.

What Makes SPICED Different From Other Sales Methodologies? 

Here’s what makes SPICED unique: 

1. SPICED Promotes Alignment Across GTM

Most sales methodologies are restrictive to one subset of the sales team like BANT for SDRs and MEDDIC for AEs. 

SPICED requires your sales, marketing, and customer success to be on the same page and follow the same process. It also enables revenue teams to be more customer-centric and drive sales by having customers “own” the conversations.

2. SPICED Is Customer-Centric

SPICED is more focused on understanding and achieving the customer's desired impact and maintaining a relationship around that impact.

“I implemented the SPICED framework into my calls, and it's enabled me to understand my clients without sounding 'salesy',” says Alesia Venuto,

Enterprise Customer Success Manager, Asana.

Limitations of the SPICED Framework

While SPICED has its many advantages, not all sales teams can implement and benefit from it. Here are some of its limitations: 

1. Information Dependency 

SPICED relies heavily on accurate and available information about the prospect. Unwillingness to share or lack of self-awareness from the prospect can hinder its effectiveness.

2. Adaptability Changes

While SPICED provides structure, it's crucial to be flexible. Sticking rigidly to the framework without considering the individual nuances of each prospect might lead to missed opportunities.

3. Time and Resource Sensitive

Noel from DarwinBox says, “The SPICED process calls for sales professionals to engage time and effort in completing research, having in-depth conversations, and analyzing data. This could be difficult when working with many prospects or tight deadlines.”

Storylane x SPICED: The Winning Combination

As we saw above, SPICED requires extensive research and an in-depth understanding of your customer and their behavior. Storylane uncovers silent signals, allowing you to ask better questions and tailor your solutions. 

For example, a prospect might explore your Storylane demo and spend extra time on a specific feature. This dwell time reveals a hidden pain point, a concern they might not have mentioned in a call. By addressing this upfront, you demonstrate proactive problem-solving and position yourself as a trusted advisor, ready to tackle their specific concerns with your solution.

See Storylane in action. Start a free trial today!

FAQs

1. What is the difference between MEDDIC and SPICED?

MEDDIC is primarily process-centric, focusing on the progression of sales through an organization. Whereas SPICED is more customer-centric and uses strategic questions to uncover prospect pain points. 

2. What is the main purpose of the SPICED framework? 

The SPICED framework helps salespeople diagnose a prospect's situation and tailor their approach to address their specific needs and urgency, ultimately increasing sales success.

3. What are some benefits of using SPICED?

SPICED benefits you by:

  • Focusing conversations: You target your approach to their specific needs.
  • Building trust: You show genuine understanding of their situation.
  • Closing more deals: You address their pain points with relevant solutions.

Killer demos for every stage

Build demos and agents that turn curious buyers to closed won
Book a demo

Related Articles

Read All Articles
Research
July 3, 2026
6 min read

68,000 deals, 3 findings: Measuring the ROI of interactive demos

This report analyzes ~68,000 deals (~50,000 of them closed) across 20+ anonymized B2B SaaS pipelines to measure what interactive demos actually do for pipeline metrics..
Ranga Kaliyur

This report analyzes ~68,000 deals (~50,000 of them closed) across 20+ anonymized B2B SaaS pipelines to measure what interactive demos actually do to pipeline metrics. Most demo benchmarks stop at engagement rates and time on page. I wanted the part that matters: do deals where buyers use a demo do better than deals where they don't?

My approach is simple. Using aggregated, anonymized Deal Intelligence data, I connected demo activity to real CRM outcomes, then compared deals with Storylane demos against deals without, inside each pipeline.

In summary

When buyers use an interactive demo, deals tend to...

  • Win 20% more often (38% vs 46% win rate), and it climbs the more they engage.
  • Reach 60% more of the buying committee (more stakeholders on the deal).
  • Land 2.75x bigger specifically in enterprise motions (flat in SMB and mid-market).

Methodology

  1. Using Storylane's Deal Intelligence, I connected demo engagement to CRM deal records (HubSpot and Salesforce) across 20+ anonymized pipelines: ~68,000 deals, nearly 50,000 closed.
  2. For each deal, I compared two groups: buyers who engaged with a demo (at least one demo session tied to the deal) and buyers who didn't. I measured win rate, deal size, and number of stakeholders.
  3. I report the median within each pipeline, then across pipelines, so a handful of large accounts don't skew the average (Simpson’s Paradox). The findings come from the 20 pipelines where the demo-to-deal link was clean enough to compare.

One caveat worth stating up front: this is a pattern, not proof of causation. Reps demo the deals worth demoing, so demo use partly reflects deal quality. Read these as strong, repeatable signals.

1. Conversion Lift: Buyers that engage with interactive demos close 20% more often

This is the big one: deals where the buyer engaged with an interactive demo won 46% of the time, versus 38% for deals with no demo  (about 20% more often), and it held in 14 of 20 pipelines analyzed.

The most interesting part is that the impact compounds with every session. The more a buyer returned to the demo, the higher the win rate. In our own pipeline the climb was steady: 87% (no demo) → 90% (1 session) → 91% (2–3) → 96% (4+ sessions). 

Across the dataset, deals with 4+ sessions won more often than zero-session deals in 71% of pipelines analyzed. A single view nudges the odds; repeat engagement moves them.

The logic is intuitive: a buyer who keeps coming back to a demo is a buyer building conviction. A static page can tell someone your product is good; a demo lets them prove it to themselves, and repeat visits usually mean they're selling it internally too.

🥡 Takeaway: Treat repeat demo use as a buying signal. When an account keeps coming back, get Sales in early.

2. Stakeholder Reach: Demos bring 60% more people into the deal

Deals with an interactive demo carried about 60% more stakeholders: a median of 1.6 contacts per deal vs 1.0 without, and more stakeholders in 15 of 17 pipelines. The gap was widest in enterprise pipelines, where one averaged 4.6 stakeholders per interactive demo-influenced deal vs 2.7 without, and another 5.2 vs 3.8.

Here's why it matters: B2B software isn't bought by one person anymore, it's bought by a committee. A demo is the rare sales asset that's easy to forward and relevant across functions, so it travels. One champion shares it, and suddenly the economic buyer, a security reviewer, and two end users have all seen the product for themselves. Deals that reach more of the committee are the deals that close.

🥡 Takeaway: Multi-thread on purpose. Send shareable, role-specific demos so the whole committee sees the product firsthand, not just your champion's secondhand pitch.

3. ACV Lift: In enterprise, deals with a demo are 2.75x bigger

Demos don't inflate every deal, and that's the honest part. The deal-size effect depends entirely on who you sell to.

  • Enterprise motions (large, complex, multi-team deals like GRC/compliance and enterprise healthcare): deals with a demo were 2.75x bigger at the median, and larger in 4 of 5 such pipelines. In one, median deal size went from roughly $16k without a demo to $127k with one; in another, from about $170k to $468k.
  • SMB and mid-market: no size difference. Demos there still won more deals and reached more people, they just didn't make deals bigger.

This tracks with how big deals actually get done. The larger and more complex the purchase, the more people and the more scrutiny involved, and the more room a demo has to do the explaining across stakeholders, functions, and weeks of evaluation. In a quick self-serve motion there's simply less for it to move.

🥡 Takeaway: if you sell enterprise, use demos as a late-stage lever, not just a top-of-funnel asset. That's where they move deal size.

How to read this report

The honest question is cause versus correlation. Demos land on the deals worth demoing, so some of this reflects deal quality alongside demo impact. To me that's what makes it worth taking seriously: across dozens of independent pipelines, the same three patterns keep showing up next to the deals that win, spread, and grow.

A few caveats. This is a first look at a subset of pipelines, deal values span multiple currencies, and a handful of accounts run against each trend. I've held an industry-by-industry breakdown for the next version, once there's enough data per vertical to say something solid.

What's next

A larger, cleaner dataset and a proper apples-to-apples comparison of similar deals with and without a demo, to turn these patterns into measurable lift, with industry and company-size cuts.

Guides
June 29, 2026
6 min read

Five ways B2B teams are using interactive demos that nobody talks about

What a conference booth in London, an EHR rollout for a differently-abled community, and a fintech triage system have in common — and what it tells us about where demo automation is actually going.
Ranga Kaliyur

What a conference booth in London, an EHR rollout for a differently-abled community, and a fintech triage system have in common — and what it tells us about where demo automation is actually going.

The standard demo automation playbook is predictable: marketing website tour, sales leave-behind, email nurture embed. That is what most companies start with.

But spend time in actual customer conversations and you see something different: teams using demos to solve problems the standard playbook never imagined.

This week, we reviewed a working session with an engineer at a large cloud computing company preparing for a technology summit in London. Her problem: she needed a product demo to play on a loop at her conference booth (no clicks, no one to navigate it, just a screen running in the background while conversations happened around it.)

Nobody markets demo automation as a conference booth tool. But that's exactly what she needed it for. And it wasn't the only unexpected use case this week.

1. Trade show and conference booth displays

The conference loop use case has specific requirements: autoplay enabled, 4-6 second transitions on title cards and pause slides, video clips set to 1.5-2x playback speed for longer recordings, and the entire thing downloaded onto the device. Conference WiFi is unreliable. You need the offline version ready before you walk in the door.

The structural formula that worked: technology stack slide (static) -> 4-second pause slide (blank) -> demo 1 with title card framing the problem ("Can I detect performance issues before they cause outages?") -> demo 2 -> repeat on loop. The problem-framing title cards are what make this work at a booth — a passerby reads a question they recognize and stops.

2. Staff onboarding for organizations with diverse accessibility requirements

A director of organizational performance at a nonprofit came to us mid-EHR transition. Her organization (200-plus staff, statewide) was moving to a new electronic health records platform and needed tutorials for everyone from clinicians to program administrators. Complicating factor: their staff includes a deaf and hard-of-hearing community.

Her requirements were specific: self-paced clicking rather than auto-advancing video, AI voiceover as an optional layer, and demos organized by function and embedded in SharePoint so staff could browse by department and role.

The training-center use case of interactive demos replacing annotated PDFs  is not new. The accessibility angle is. When a demo is self-paced, the viewer controls the speed versus video. That's a meaningful accommodation for populations that need more time, and it requires zero additional effort from the team building the content.

3. Multi-system integration demos

"We get asked all the time: what do these integrations actually look like?" said a co-founder at an early-stage health tech company. They had been answering that question in live demos, switching between systems in real-time and hoping nothing broke.

What they discovered: you can capture from multiple platforms in a single demo session. Finish recording in system one, click "add to existing demo," then capture from system two. The viewer moves between platforms seamlessly — without any live switching, without any risk of a broken environment. 

Live integration demos are high-risk, tedious (from a data management pov) and unrepeatable. Captured integration demos are neither. For a company whose primary sales objection is "show me exactly how the integration works," this is not a minor workflow change; it's a competitive differentiator.

4.Inside sales automation for long-tail accounts

An inside sales leader at a fintech company described a problem his team lives with daily: they manage accounts "where we're seeing very less revenue and more effort going from an account manager's point of view." His team's solution was a self-serve portal paired with interactive demos that replace human demos entirely for lower-priority accounts. Reps focus on the accounts with revenue potential; the demo handles the education and qualification for everyone else.

He had used this approach at a previous company and was replicating it here. The key insight: he was not evaluating demo automation as a way to improve existing demos; He was using it as a triage mechanism for a coverage problem. Interactive demos let you maintain a presence in accounts that don't justify a rep's time. That's a fundamentally different value proposition than "make your demos better," and it's one that VP of Sales audiences will understand immediately.

5. Localized demos for non-English-speaking markets

An inside sales team at a fintech company with a large India-based sales operation had one specific question: how many languages does the AI voiceover support? The answer, over 30, prompted an immediate workflow: build the demo once in English, then translate and duplicate into regional languages.

In markets where English-language demos create friction in the sales process, this is not a nice-to-have. It is a conversion rate issue. Prospects engage more deeply with content in their first language. The ability to generate a localized demo without re-recording or hiring a voice actor changes the economics of localization for inside sales teams that are already stretched thin.

Research
June 29, 2026
6 min read

Interactive demos vs. product videos: why revenue teams are switching over

Should you use interactive demos or product videos for sales? Compare creation time, maintenance, personalization, and analytics to decide.
Ranga Kaliyur

When sharing async product demos, sales teams have traditionally reached for a couple of options: quick and dirty screen recordings (think Loom, Vidyard, etc.) and high-end video productions (think Camtasia, Consensus, etc.). While there’s a time and place for both; AEs, SEs, and PMMs are increasingly adopting a third format — interactive demos — as a “better than both worlds” alternative. Here's why:

Interactive Demos vs Video: Feature Comparison
Compare Interactive demos
(Storylane)
Screen recordings
(Loom, Vidyard)
Video productions
(Camtasia, Consensus)
Time to create ✅ Fast, capture and creation often completed in minutes ✅ Fast but requires narration, timing, retakes, etc. ❌ Slow, can take weeks to script, shoot, and edit
Editing ✅ Self-serve, easy: replace screens, tweak text, reorder steps; no re-recording ❌ Limited scope: re-recording, trimming, stitching clips, fixing audio ❌ Technical dependency: needs expertise in pro editing software
Polish and branding ✅ Professional, consistent themes built-in; no editing software needed ❌ Low production value. Harder to maintain consistency; requires design/video tools ✅ Cinematic quality but requires video editing expertise
Publishing ✅ One-click publish; instantly updates everywhere ❌ Requires re-uploading and re-sharing new versions ❌ Requires re-uploading and re-sharing new versions
Maintenance & Updates ✅ Replace screens and content in minutes, auto-update instantly ❌ Requires re-recording entire sections/full-video ❌ Requires re-producing entire sections/full-video
Personalization ✅ Personalize at scale with dynamic tokens ❌ Hard to scale: Requires re-recording ❌ Impossible to scale: Requires re-production
Analytics ✅ Granular: Track views, interests, completion, and time-spent per step ❌ Limited to views, no actionable analytics or Opinions ❌ Limited to views, no actionable analytics or Opinions
Buyer experience ✅ Interactive, two-way experience ❌ Passive, one-way experience ❌ Passive, one-way experience
Ideal for… Across the board Ad-hoc touches, quick Q&A Top-of-funnel brand awareness campaigns

Why revenue teams are adopting interactive demos

Since our inception, we've noticed revenue teams of all sizes, from early-stage startups to Fortune 500 enterprises, switch over from videos to interactive demos. Here are the most common reasons we hear from customers.

Reason #1 - Speed without sacrificing quality

Screen recordings are quick and easy to produce but lack the polish and quality needed for high-value deals. On the other hand, producing polished video demos means days of planning, hours of environment prep, multiple recording attempts, and extensive editing. Interactive demos eliminate this friction entirely, especially now with AI, to instantly generate product-specific content (Guides, voiceovers, etc) from captured screens — no need for multiple takes. 

"Video is really strong at capturing people's attention and welcoming them into your story. But the thing that video can't do is provide a “click-through experience” allowing users to actually get their hands on the product — to feel it, to see it, to understand what the actual day in and day out of working with your tool is going to be like. Especially with its AI and automation, Storylane allowed us to build demos in such a quick amount of time."
- Michael DeMarco, PMM, Phenom

Reason #2 - Asset maintenance and scalability

Traditional videos are like baked cakes — once ingredients (product screens, click path, narrative) are combined into a video, it’s difficult to swap individual components. When your product UI changes six months from now, you face full reproduction from scratch.

Interactive demos keep these elements separate. Update a screen in minutes without touching the narrative. Adjust messaging without re-recording. Reorder workflows without starting over. This durability enables demos to stay current as your product evolves.

Further, creating persona-specific, industry-tailored, or localized video content means producing multiple versions of each asset — a multiplication problem that quickly becomes unmanageable. Storylane's AI editor recontextualizes entire demos for different personas or industries in seconds. Dynamic tokens automatically swap prospect information without creating separate versions. One base demo adapts to dozens of scenarios without manual overhead.

Reason #3 - Modern buying preferences 

Interactive demos respect buyer time by letting them jump to relevant sections, skip familiar concepts, and control their pace. Video forces a fixed timeline — even if viewers only care about one feature, they must scrub through the entire recording to find it. This level of control and self-serve flexibility reflects the preference of modern buyers, who'd rather click around a product tour for themselves than rely on a passive, one-way video.

"Nobody wants to watch a 5-minute video anymore. So my team sends a Storylane demo and the prospect sees the demo in 5 clicks."
- Jon Dolan, Sales Director, Cognism

The difference in analytics is equally striking. Video platforms show watch time and opens. Interactive demos reveal which features prospects explored, where they spent time, which stakeholders engaged, and where they dropped off. These step-level Opinions enable targeted follow-up conversations that video simply can't support.

Make buying easy with Storylane