Can I use SPICED, MEDDIC, or BANT inside Spiky?

If your team already runs SPICED, MEDDIC, MEDDPICC, BANT, or your own internal framework, you do not want another tool trying to replace it.

In Spiky, your methodology becomes the intelligence layer behind real-time sales coaching, playbook execution, and deal visibility. You keep your CRM stages. You keep your language. You keep your exit criteria.

Here is exactly how Spiky sales methodology support works in practice.

Let’s define how Spiky thinks about sales methodologies

Before we talk about setup, we need a shared definition.

SPICED, MEDDIC, MEDDPICC, BANT, and custom frameworks are structured ways to:

• Run discovery
• Qualify opportunities
• Advance deals through stages
• Improve forecast accuracy

Spiky treats methodologies as a flexible playbook layer, not a rigid process engine.

Important distinctions:

• Methodology = how you sell
• CRM stages = where the deal sits in the pipeline
• Playbooks in Spiky = how your methodology is operationalized during live calls

Spiky is methodology-agnostic. It observes behavior, guides conversations, and tracks completion against whatever framework you choose.

You do not need to abandon SPICED or MEDDIC to use Spiky. In fact, Spiky is designed to make your existing framework more actionable in real time.

Here’s how Spiky supports SPICED, MEDDIC, BANT, and your own custom framework

Inside Spiky, any sales methodology becomes three connected layers:

1. Real-time playbooks on calls

During a live Zoom, Teams, or Google Meet call, Spiky displays your active playbook in a sidebar. That playbook can be:

• SPICED Discovery
• MEDDPICC Enterprise Qualification
• BANT First Call
• A fully custom internal framework

Reps see prompts and checkpoints tied to your methodology.

2. Structured inputs and notes

Each methodology element becomes:

• A field
• A checklist item
• A required input
• Or a short free-text summary

For example:

• Champion Identified
• Critical Event Date
• Economic Buyer Confirmed
• Budget Range

You define the language. Spiky mirrors it.

3. Deal and pipeline analytics

Spiky then analyzes:

• Methodology coverage across calls
• Which elements are consistently skipped
• Correlation between coverage and win rate

Many Spiky customers run:

• MEDDPICC for enterprise
• SPICED for mid-market
• BANT for inbound SDR qualification
• Hybrid frameworks unique to their company

You can even support multiple methodologies across teams in the same Spiky instance.

How do I set up my methodology in Spiky step by step?

Setting up SPICED in Spiky or configuring MEDDIC in Spiky is straightforward.

Step 1: Define your framework clearly

List:

• Each methodology element
• The key questions reps should ask
• The fields required in CRM
• Exit criteria for stage movement

For example:

• MEDDPICC → Metrics, Economic Buyer, Decision Criteria, Decision Process, Paper Process, Identify Pain, Champion, Competition
• SPICED → Situation, Pain, Impact, Critical Event, Decision

Step 2: Create or edit a Playbook in Spiky

In Spiky’s Playbook section:

• Create a new playbook
• Name it clearly, such as “Enterprise Discovery - MEDDPICC”
• Add each methodology element as a section

Each section can include:

• Live prompts
• Coaching reminders
• Completion checkboxes

Step 3: Configure input fields

Define fields for reps to fill:

• Dropdown for Economic Buyer Identified
• Text field for Critical Event
• Toggle for Budget Confirmed

These can be completed during or right after the call.

Step 4: Map fields to your CRM

Using Spiky’s CRM field mapping:

• Map MEDDPICC fields to Salesforce or HubSpot fields
• Ensure no duplicate data structure
• Keep reporting clean

Spiky does not create a parallel process. It enhances your existing one.

Step 5: Test and iterate

Run Spiky on 2 to 3 real calls.

Then review:

• Which prompts were useful
• Which elements were skipped
• What should be simplified

You can iterate on your playbook quickly without disrupting historical data.

Here’s what a SPICED playbook looks like in a live Spiky call

Alt text examples:

• Spiky SPICED playbook sidebar during live sales call
• SPICED checklist active inside Spiky real-time coaching interface
• Real-time prompt reminding rep to quantify impact in SPICED framework

SPICED stands for:

• Situation
• Pain
• Impact
• Critical Event
• Decision

Inside Spiky:

• The Active Playbook shows “SPICED Discovery.”
• Each element appears as a live checklist section
• Prompts guide the rep naturally

Example real-time nudges:

• “Impact not yet quantified in this call.”
• “No Critical Event identified so far.”

Reps can:

• Mark sections complete
• Add short notes
• Sync to CRM instantly

Managers later see:

• Percentage of calls covering Impact
• How often is a Critical Event captured
• Conversion rates when SPICED is fully executed

This is how SPICED in Spiky becomes operational, not theoretical.

Here’s how MEDDIC and MEDDPICC teams usually configure Spiky

Alt text examples:

• Spiky real-time MEDDPICC playbook sidebar on a sales call
• Dashboard highlighting skipped authority topics in MEDDPICC
• Pipeline view filtered by methodology completion percentage

Enterprise teams running MEDDIC or MEDDPICC often treat it as their deal operating system.

In Spiky, this becomes:

Active Playbook sections:

• Metrics
• Economic Buyer
• Decision Criteria
• Decision Process
• Paper Process
• Identify Pain
• Champion
• Competition

Spiky can flag insights like:

• 70 percent of meetings skip authority topics
• 20 percent of meetings skip legal matters

This visibility is powerful for leaders.

Managers can:

• Filter pipeline by MEDDPICC completeness
• Prioritize deals with low coverage
• Coach reps specifically on multi-threading or budget conversations

Spiky recommendations can link to training content, reinforcing MEDDPICC skills across the team.

What about BANT and lighter qualification frameworks?

BANT stands for:

• Budget
• Authority
• Need
• Timing

For SMB or SDR teams, simplicity matters.

Inside Spiky, you can create:

Playbook: First Call - BANT Qual

Each element becomes a natural conversation reminder:

• “Have you confirmed budget range?”
• “Have you identified decision authority?”

Spiky can highlight patterns like:

• Budget avoided in 40 percent of calls
• Authority not discussed in early-stage conversations

Managers can then correlate BANT completeness with:

• Demo-to-opportunity conversion
• No-show rates
• Close rates

You can even combine frameworks:

• BANT for first call
• SPICED for deeper discovery
• MEDDPICC for enterprise stages

Spiky supports all of them simultaneously.

Here’s how Spiky keeps your CRM stages and reports clean

RevOps leaders often ask:

“Will using SPICED or MEDDIC in Spiky break our reporting?”

The answer is no.

Spiky:

• Does not replace CRM stages
• Does not redefine pipeline logic
• Does not override exit criteria

Instead, it augments them.

Field mapping ensures:

• Methodology fields sync directly to CRM
• Forecasting logic remains intact
• Reporting stays consistent

Example deal view:

• CRM Stage: Discovery
• Methodology Completion: 45 percent
• Missing: Economic Buyer, Paper Process

This adds context without disrupting governance.

Role-based permissions allow ops teams to:

• Define mandatory fields
• Control edit access
• Restrict visibility where needed

How should I roll this out to my sales team inside Spiky?

Best practice rollout plan:

1. Start small

Pilot with:

• 3 to 5 reps
• One methodology
• One clearly defined playbook

2. Run a focused enablement session

Show:

• Live call with playbook sidebar
• How prompts reduce mental load
• How CRM sync removes manual note-taking

3. Track 1 to 2 simple metrics

Examples:

• Percent of calls capturing Budget
• Percent of calls identifying Decision Process

4. Use Spiky coaching insights

Instead of manual call reviews, use:

• Coverage dashboards
• Skill-based recommendations
• Real-time coaching nudges

Reps keep their style. Spiky supports behavior change without scripting.

FAQ: Can I mix methods, change later, or use different frameworks by team?

Yes, you can run multiple methodologies in parallel.

Examples:

• SPICED for mid-market AEs
• MEDDPICC for enterprise
• BANT for SDR teams

You can edit or evolve your methodology over time without breaking CRM sync or losing historical insights.

Playbooks can be assigned by:

• Team
• Territory
• Segment
• Product line

Changes can be phased gradually. Start simple, then layer complexity.

Spiky support and Help Center resources guide you through playbook design and CRM mapping.

Next steps: Try your methodology live in Spiky

The best way to answer “Can I use SPICED or BANT in Spiky?” is to see it live.

Book a demo and we will:

• Configure your current methodology before the session
• Map your CRM fields in real time
• Show live prompts during a sample call

Suggested experiment:

Run Spiky on 5 discovery calls and compare:

• Methodology coverage
• Deal progression
• Coaching insights
• Close rates

Spiky customers have reported measurable gains such as a 7 percent lift in closures after improving playbook execution.

👉 Talk to our team about your methodology setup

Bring your field list and exit criteria.

We will map your framework live.

Spiky is not a new methodology.

It is the real-time execution layer for the one you already use.