Sales Methodology Guide & Checklists

What's the difference between MEDDIC and SPICED, and how do I know which one to use?

MEDDIC is built for rigorous qualification — it's best when you need to filter out bad-fit deals early and focus rep time on opportunities most likely to close. SPICED is designed with the full customer lifecycle in mind, including post-sale impact and renewal, making it a better fit if your revenue model depends on expansion and retention. If your team is primarily hunting net-new logos in complex enterprise deals, start with MEDDIC. If you're in a SaaS business where CS and sales need to speak the same language across the funnel, SPICED gives you that shared framework.

Do I need a specific CRM or tool like Weflow to operationalize these methodologies, or can I run this in a standard Salesforce or HubSpot setup?

You can implement any of these methodologies in a standard Salesforce or HubSpot setup using custom fields, required field validation at each stage, and workflow automations — no additional tooling required to get started. Where tools like Weflow add real leverage is in auto-populating methodology fields from call recordings and emails, which removes the manual logging burden that kills adoption. If your reps are already resistant to CRM hygiene, that automation layer matters more than the methodology choice itself.

Which of these methodologies works best for a sales team that's mostly made up of newer reps?

BANT/GPCT and SNAP are the most accessible for less experienced reps because they're structured around clear, sequential questions without requiring deep industry expertise to execute. MEDDIC and Challenger both demand a level of deal sophistication and business acumen that newer reps typically haven't built yet — Challenger in particular can backfire badly if a rep doesn't know when to back off. A practical approach is to start newer reps on GPCT for qualification and layer in SPIN question types to build their discovery muscle before introducing more complex frameworks.

What data or prep work does a rep actually need before running a Challenger sales conversation?

A rep needs a thorough understanding of the prospect's industry dynamics, the common assumptions buyers in that space tend to make, and at least one well-researched reframe they can back with data or case evidence — not just an opinion. Without that groundwork, the "Reframe" step collapses into a generic pitch, which is worse than not using Challenger at all. The guide recommends pulling from customer conversations, industry publications, and competitor materials to build that depth before the first call.

How do I know if my team is actually following the methodology and not just checking boxes in the CRM?

The clearest signal is whether methodology field completion correlates with win rate — the guide specifically cites that deals with full MEDDIC fields close at roughly 30% higher rates, so you can run that correlation in your own data. Beyond the numbers, look at pipeline review conversations: if managers are asking methodology-driven questions (e.g., "Have we identified the economic buyer?" or "What's the critical event?") and reps can answer with specifics rather than vague responses, adoption is real. Compliance dashboards tracking the percentage of deals missing key qualification criteria give you the leading indicator before win rate data catches up.

How often should we revisit which methodology we're using, and what would trigger a switch?

A reasonable cadence is a quarterly review tied to your win/loss analysis — specifically looking at whether deals lost had methodology gaps or whether the framework itself wasn't suited to the deal type. The guide is explicit that mixing methodologies is valid: for example, using Sandler for relationship-building and trust-setting early, then layering MEDDIC fields for qualification rigor as the deal progresses. A trigger to reconsider your primary methodology is a sustained drop in conversion at a specific pipeline stage that maps back to a gap the current framework doesn't address — that's a structural problem, not just a coaching problem.