The most popular advice about building a sales process for B2B is also the most misleading: define your funnel, increase activity, and push prospects toward the close. That's tidy advice for a spreadsheet. It's less useful when your champion wants a demo, finance wants a business case, and security hasn't heard of you.
A better process coordinates the work buyers need to do before they can agree to buy. Your reps still need stages, owners, and targets. But those should measure buyer progress, not how enthusiastically someone clicked “proposal sent.”
The funnel isn't dead as a reporting tool. It's dead as a reliable description of how buyers make decisions. Confusing those purposes is how teams build beautiful dashboards around opportunities that aren't going anywhere.
Gartner's buyer-journey research describes recurring buying jobs: problem identification, solution exploration, requirements building, supplier selection, validation, and consensus creation. The same research reports that 99% of B2B purchases involve organizational change, while 75% of buyers prefer a rep-free experience. Yet buyers using supplier-provided digital tools alongside a representative were 1.8 times more likely to complete a high-quality deal than those using the tools independently.
The lesson isn't to remove salespeople. It's to stop making buyers talk to salespeople for information they should be able to find themselves.
A prospect can select a preferred supplier and then revisit requirements after IT discovers an integration problem. Finance can reopen the business case after a strategic priority changes. Neither event means the buyer has somehow broken your funnel.
Your process should accommodate that movement without disguising it:
Gartner's enterprise buying-group research puts the average group at five to 11 stakeholders across roughly five business functions. That's a coordination problem, not a persuasion problem.
If buyers can't understand your product, improve self-service education. If they understand the product but can't justify changing systems, strengthen discovery and business-case support. Hiring more SDRs to compensate for either problem just creates more conversations your team can't advance.
A meeting is access to a calendar. It isn't necessarily access to a buying decision.
That distinction should influence SDR targets. Meetings booked can remain a useful operational measure, but qualified buying-group access is the more demanding question: did the rep reach the people who can help an account evaluate and approve change?
Don't eliminate structure. Replace the assumption of orderly buyer movement with explicit evidence of readiness.
A useful stage model gives each opportunity a home without pretending every buyer follows the same route. Buyers can revisit earlier work. Reps shouldn't advance the opportunity until they can document the required evidence.
For founder-level context before configuring your CRM, Big Moves Marketing's B2B sales strategy for founders is a companion resource. Translate strategy into enforceable gates rather than another slide deck.
| Stage | Owner | Exit Criteria | CRM Field |
|---|---|---|---|
| ICP and trigger | SDR manager | Target profile and relevant change documented | ICP rationale; trigger |
| Account fit and problem | SDR | Fit verified; buyer confirms an operational problem | Fit evidence; problem statement |
| Stakeholder mapping | Account executive | Relevant roles and access gaps identified | Buying-group map |
| Multi-threaded discovery | Account executive | Impact, priorities, and evaluation requirements confirmed | Impact; decision criteria |
| Validated solution design | Solutions lead | Buyer accepts how the proposed approach meets requirements | Validation evidence; implementation risks |
| Consensus and close | Account executive | Approvals completed, terms agreed, and agreement executed | Approval path; contract status |
An owner is accountable, not solitary. A solutions lead can own validation while an account executive handles commercial coordination. In a smaller company, a founder may hold both responsibilities, but the responsibilities should still be distinct.
Consider a hypothetical workflow-software opportunity at a company changing its customer onboarding process. This is an illustrative deal, not a customer case study.
At ICP and trigger, the SDR documents why the account fits and why the onboarding change matters now. The written question is: Why this account, and why now?
During account fit and problem framing, the SDR checks the environment and asks the operations leader to describe the failure. “Interested in automation” isn't enough. “Customer handoffs lack a clear owner” gives discovery somewhere useful to go.
For stakeholder mapping, the account executive identifies who owns onboarding, who controls spending, and who must evaluate integration and security. The question becomes: Whose approval or cooperation could determine the outcome?
Multi-threaded discovery tests the problem across those roles. Operations may want visibility while IT wants fewer custom integrations. Capture both rather than treating the champion's preferences as company policy.
At validated solution design, the solutions lead demonstrates the relevant workflow and records unresolved dependencies. The buyer should confirm what passed, what failed, and what still needs investigation.
Consensus and close requires an agreed approval path, completed reviews, executable terms, and a clear implementation handoff. A signature shouldn't reveal promises customer success has never heard of.
Configure validation rules around these gates, but allow managers to record justified exceptions. Otherwise, reps will enter nonsense to satisfy mandatory fields, and you'll have automated fiction.
BANT, MEDDPICC, SPICED, CHAMP, GPCT. There's no shortage of acronyms available to decorate a sales kickoff. The useful question is which framework helps a manager expose risk without turning discovery into an interrogation.
My recommendation for a lean SaaS team is SPICED for discovery, with selected MEDDPICC fields for opportunity control. That's an operating preference, not a claim that one acronym universally outperforms another.
| Framework | Where I'd use it | Where I'd be careful |
|---|---|---|
| BANT | Initial triage when spending authority and timing are relatively clear | Treating absent budget as proof there's no worthwhile problem |
| SPICED | Exploring situation, pain, impact, critical events, and decisions | Leaving procurement and approval mechanics insufficiently documented |
| MEDDPICC | Complex evaluations with commercial, technical, and organizational dependencies | Requiring exhaustive answers before a buyer has reason to share them |
For a sub-50-person team, keep the initial workflow light. For a deal above $500K ACV, I wouldn't rely on BANT alone, but that's a proposed decision rule, not a research-backed breakpoint. Approval complexity matters more than a neat contract-value threshold.
Ebsta's 2023 B2B Sales Benchmark Report found that 61% of surveyed users used MEDDPICC or a variation. Completing commonly neglected fields, including metrics, decision criteria, and paper process, was associated with a 206% improvement in win rates. That's an association, not a promised causal uplift.
Make these fields mandatory when they become relevant:
Keep speculative competitor notes and elaborate account narratives optional unless they affect a decision.
Qualification test: If a different rep inherited the account tomorrow, could they distinguish buyer-confirmed facts from the seller's assumptions?
Audit that distinction during deal reviews. “Interested” is a reaction. “Demo completed” is an activity. Neither tells you whether the buyer can justify, approve, or implement the purchase.
A buyer requests a demo after reading your integration documentation. Your form sends a notification to an unattended inbox, the SDR eventually calls without context, and the account executive later asks which integration matters.
You haven't created an omnichannel process. You've made the buyer repeat themselves across channels.
McKinsey's Global B2B Pulse research found that buyers use an average of 10 channels, compared with about five in 2016. It also reports that 71% of B2B companies offer e-commerce, with roughly one-third of revenue among those companies coming through digital channels.
For that integration-focused buyer, build the workflow around continuity:
An InsideSales analysis summarized by Martal covered more than 55 million sales activities and 5.7 million inbound leads across 400-plus companies. Conversion rates were eight times higher when the initial attempt happened within five minutes rather than between five minutes and 24 hours.
Use that response window as a relative benchmark, not a guaranteed outcome. Speed can't rescue poor fit or a thoughtless opening.
Set availability rules, local-time coverage, and SLA breach alerts. Then check whether your calling infrastructure supports the workflow; SnapDial's VoIP solutions for small businesses is a resource to consult while evaluating the phone component.
Use a documented lead-response-time workflow rather than hoping each rep interprets urgency the same way.
The SDR-to-AE handoff should include the problem, relevant trigger, known stakeholders, evaluation concerns, and promised next action. Attach evidence, not a novel-length transcript dump.
Fast outreach gets attention. A coherent handoff prevents the next conversation from wasting it.
Your champion likes the product. That's useful. It isn't permission to forecast the enthusiasm of everyone they haven't spoken to.
Gartner research on buyer enablement puts time spent meeting potential suppliers at about 17% of the buying journey. Your team therefore needs to support decisions made outside meetings it controls.
Build a stakeholder map that records more than names and job titles.
| Role | Outcome to clarify | Evidence to prepare | Access status |
|---|---|---|---|
| Business owner | Operational improvement | Problem statement and success criteria | Direct or champion-mediated |
| Finance | Commercial justification | Buyer-validated assumptions and costs | Confirmed or missing |
| IT | Integration feasibility | Architecture and dependencies | Confirmed or missing |
| Security | Acceptable risk | Accurate security responses | Confirmed or missing |
| Procurement | Executable purchase | Terms and approval requirements | Confirmed or missing |
| End users | Usable workflow | Relevant demonstration and rollout plan | Confirmed or missing |
Treat the entries as hypotheses until the relevant people confirm them. A rep guessing what finance cares about isn't the same as finance agreeing.
Ask the champion to help design the evaluation. Position introductions around reducing their workload, not checking whether they're important enough.
Don't launch parallel outreach to colleagues behind your champion's back. Agree on who gets contacted, why, and what you'll share.
Portability rule: Every useful sales asset should make sense when forwarded internally without the rep there to explain it.
A forwardable business case identifies assumptions. A security answer distinguishes verified capability from planned work. An implementation outline names responsibilities and dependencies.
When access is the bottleneck, increasing outreach volume can create more internal confusion rather than progress. Ask whether the next touch helps a stakeholder make a decision. If it merely reminds everyone that your quarter is ending, keep it in drafts.
I've watched reps ace every interview question and then spend their first month booking meetings with accounts that were never going to buy. Hiring and ramping are different management jobs. A candidate can interview well and still struggle to explain your ICP, diagnose a problem, or recognize when a meeting shouldn't become an opportunity.
As one recruiting option alongside direct hiring and referrals, hireSDRs screens SDR and BDR candidates through skills tests, English assessments, reference checks, and cultural-fit interviews, so managers interview a shortlist rather than a stack of resumes.
Treat this as a working blueprint, not a universal ramp-time benchmark. Extend or compress it based on demonstrated competence and deal complexity.
| Period | Weekly outcome | Certification gate |
|---|---|---|
| Days 1–30 | Week 1: explain the ICP and buyer problem. Week 2: assess account fit. Week 3: practice outreach and discovery. Week 4: complete a supervised handoff. | Correctly qualify a simulated account and record defensible CRM evidence |
| Days 31–60 | Week 5: run a supervised sequence. Week 6: review calls against the qualification rubric. Week 7: handle objections. Week 8: build a stakeholder map. | Manager approves a real qualification decision and follow-up |
| Days 61–90 | Week 9: manage follow-up independently. Week 10: resolve handoff gaps. Week 11: analyze source quality. Week 12: complete an opportunity review, then use remaining days to close coaching gaps. | Demonstrate consistent judgment before full quota ownership |
For SDRs, certify targeting, relevance, initial discovery, and clean handoffs. For account executives, add evaluation planning, commercial discovery, stakeholder coordination, and forecast judgment. The true test is whether the rep can move a buying group through its actual work: confirming the problem, agreeing on evaluation criteria, and getting the right roles into the room. An identical training playlist for both roles certifies neither.
Use call recordings to examine where the rep accepted a vague answer, missed a contradiction, or promised something unverified. Choose a specific moment, agree on a better response, and rehearse it.
A documented sales-rep onboarding plan helps managers apply the same standards without relying on memory.
For a new market, consider a limited staffing pilot before committing permanent headcount. If month-to-month support is available, confirm the terms, management responsibilities, and exit conditions. Flexible staffing still demands a capable coach.
Skip that discipline and the rep costs you a calendar full of supervision.
A swollen pipeline is expensive comfort. Salesforce reports that 57% of sales professionals say their sales cycle is getting longer, which makes unsupported close dates particularly unhelpful.
Run a weekly review around a compact dashboard:
G2's buyer-behavior research reports that nearly two-thirds of software buyers prefer engaging salespeople only later in the journey, a 17-percentage-point increase from the prior year. That makes meeting count an incomplete measure of whether SDRs reach an account while they can still influence evaluation.
Define qualified buying-group access as an ICP-fit account with a buyer-confirmed problem, an identified approval structure, and agreed access to relevant evaluation stakeholders. Record the first verified access date against the buyer-reported shortlist status.
Use an account-level reporting view with source, trigger, problem evidence, engaged roles, missing roles, shortlist status, and next action. Don't count an extra contact because someone accepted a connection request.
Ask what changed, who confirmed it, and which dependency could still prevent the decision. Use a documented sales-forecasting example to make category definitions consistent across managers.
Retire activity volume as a standalone success measure. Keep it for diagnosis: low activity may explain weak coverage, but high activity doesn't excuse poor qualification.
The useful question isn't whether your team looks busy. It's whether buyers are becoming more able to make, approve, and implement a decision.
hireSDR.com offers screened SDR and BDR talent for teams building or expanding their prospecting operation. Visit hireSDR.com with your ICP, qualification gates, and coaching plan, then discuss the staffing support needed to run that process rather than book more meetings.
Cold calling isn't dead. Your approach is. Most “cold calling best practices” posts are recycled wallpaper, a pile of obvious advice dressed up like strategy....
You probably know this scene a little too well. Your CRM says the quarter looks alive. Your SDRs are booking meetings. Your AE says there's...
Your best Account Executive is doing detective work in Apollo, cleaning CSVs, and chasing no-shows instead of closing. Your pipeline has activity, sure, but the...
Tell us who you need. We'll have pre-vetted candidates in your inbox within 72 hours. No commitment until you hire.