Sales process consultants should do more than rename stages or add fields to a CRM. For B2B technology teams, the process must reflect how customers make decisions, what evidence sellers need to advance a deal, and how managers coach execution. The right design gives Heads of Sales, Revenue Operations, and Enablement a shared operating model without turning every opportunity into an administrative exercise. This guide focuses on diagnosing and repairing that operating model in live deals.
What should sales process consultants actually change?
A process is useful when it helps a team make better decisions about real opportunities. A stage label alone does not do that. “Discovery complete” is weak evidence if the seller cannot explain the buyer’s problem, who is affected, and what happens if the problem remains unresolved.
Start by separating the process into three connected layers:
- Buyer decision: What must the customer understand, validate, approve, or change at this point?
- Seller action: What conversation or work can help the buyer make progress?
- Inspection evidence: What can a manager verify from the deal, rather than infer from seller confidence?
For example, a technical validation stage should not advance simply because a demo occurred. The team should know which use case is being tested, who agreed to the success criteria, what the test will prove, and how the result connects to the customer’s decision. This is where a practical B2B sales process design connects stages to customer evidence.
How do you diagnose a process that is not working?
Do not begin with a workshop to rewrite every stage. Inspect a small set of recent wins, losses, and stalled deals. Trace each opportunity from first meeting through decision. Compare what the process said should happen with what the buyer and account team actually did. Use a consistent review sheet: opportunity context, expected stage evidence, evidence actually recorded, buyer action, and the moment progress slowed or stopped.
- Find the recurring failure point. Look for deals that enter technical validation without an agreed business problem, or reach proposal with no clear buying decision or approval path.
- Separate process failure from execution failure. If the stage asks for useful evidence but sellers do not collect it, the issue may be capability or coaching. If the stage does not reflect a customer decision, the design itself needs work.
- Check whether evidence is observable. “Strong relationship” is an opinion. A buyer-confirmed next step involving the people who own the decision is observable.
- Test the language with the field. Ask sellers and managers to apply each stage to the same opportunity. Conflicting interpretations reveal unclear criteria.
Use MEDDIC as a disciplined way to examine deal evidence, not as a checklist that replaces judgment. For instance, a seller may know a technical champion but still lack access to the Economic Buyer or a grounded understanding of the Decision Criteria. The process should make that gap visible early enough to act. Research on sales digitization and sales-process optimization examines how sales enablement platforms relate to stages of the B2B sales process; it reinforces the need to connect tools and process rather than treating software as the design itself (study on sales digitization and sales process optimization).
How should the diagnostic work in practice?
Choose a few opportunities with different outcomes rather than reviewing only a dramatic loss. In one won deal, ask which buyer actions made the decision credible and whether the process captured them. In a stalled deal, identify the earliest point where the seller’s assumptions stopped matching buyer behavior. In a lost deal, distinguish a genuine competitive decision from a late discovery that the buying group lacked agreement or authority.
Then write the problem as a testable statement: “Opportunities enter POV without a buyer-approved test plan.” That statement is more useful than “qualification is weak” because the team can check it against deal records and calls. Keep observations separate from interpretation. “No buyer owner appears in notes” is an observation; “the buyer has no owner” is an inference that needs confirmation.
Which process evidence matters by role?
Shared definitions do not mean every role needs the same view. A Head of Sales needs a usable way to inspect deal health and coach decisions. Revenue Operations needs consistent data definitions and workflow logic. Enablement needs to turn the process into field behavior and usable assets.
| Role | Decision to support | Useful deliverable | Evidence to inspect |
|---|---|---|---|
| Head of Sales | Where should leaders coach or intervene? | Manager inspection guide and deal-review prompts | Buyer-confirmed milestones, risks, and next steps |
| Head of Revenue Operations | How should stages and systems represent progress? | Stage definitions, required fields, and reporting logic | Consistent, decision-relevant CRM evidence |
| Head of Enablement | What must sellers be able to do in the field? | Playbook, call prompts, and role-based practice | Observed use in prospecting and customer conversations |
Keep required CRM fields limited to evidence that informs a decision. If a field is collected but never used in coaching, forecasting, or process improvement, challenge its place in the workflow. For more on turning stages into operating discipline, see this guide to building a scalable sales process.
How can the roles work from one deal without duplicating effort?
Take an opportunity approaching a proof of value. The seller should record the buyer’s use case, agreed test conditions, stakeholders, and next decision. The manager should use that record to coach the next conversation, not ask for a second narrative in a separate document. Revenue Operations should ensure the fields and reports expose the evidence without forcing sellers to enter the same fact twice. Enablement should create the call prompts and test-plan examples that help the seller gather information naturally.
Agree on a shared definition of “buyer-confirmed.” A meeting invite alone may show that a meeting is scheduled, but not that the buyer agreed on its purpose or participants. A useful record says who will attend, what question the meeting will resolve, and how the outcome affects the decision. This precision makes handoffs between seller, manager, and operations more useful.
How should the process guide the work between stages?
A stage map is not enough. Sellers need practical actions that help buyers move forward, and managers need questions that reveal whether those actions worked. Build a small set of assets around the friction points the deal review uncovered.
- Prospecting: Create messages that connect a specific business or technical problem to a reason for a conversation. Coach the seller on actual outreach, not only on a template.
- First meeting: Use prompts to uncover the buyer’s desired change, impact, stakeholders, and decision path. Avoid treating discovery as a list of questions to complete.
- Demonstration: Tie the demo to agreed use cases and buyer criteria. A demo script should guide relevance, not force a rigid monologue.
- Proof of value: Agree on a test plan, owners, measures, and decision implications before work begins. This keeps a technical evaluation connected to the purchase decision.
MEDDIC helps teams ask whether they understand Metrics, the Economic Buyer, Decision Criteria, Decision Process, Identify Pain, and the Champion. The point is not to force every deal into identical conversations. It is to make important unknowns explicit and decide how to resolve them.
Translate those unknowns into useful field tools. A prospecting asset should help a seller test whether the problem matters to the target account. A sales deck should make the customer’s decision and evidence visible, not merely list product capabilities. A demo script should state the buyer question each section is meant to answer. A POV plan should document the hypothesis, environment, owners, success evidence, timeline, and the decision that follows. If the buyer cannot say how a successful test changes the decision, the test may be technically interesting but commercially disconnected.
These tools should be built around role and moment. A technical evaluator may need a clear test protocol; an economic buyer may need the implications, alternatives, and decision path summarized. The process should help the account team share evidence across those conversations instead of making each seller invent a separate story.
What makes an asset usable rather than decorative?
Start with a real piece of work and a specific failure mode. If first meetings end with polite interest but no next action, create a short discovery guide that helps the seller test the business problem, impact, stakeholders, and urgency. If demos wander through features, build an agenda that connects each segment to a buyer question and agreed criterion. If POVs continue without a decision date, use a plan that records owners, checkpoints, evidence, and the decision meeting.
Review each asset with the people who must use it. Ask a seller to apply it to a current account, not a hypothetical ideal customer. Remove prompts that do not change the conversation or improve the evidence. Keep enough structure to support consistency, while allowing the seller to follow the buyer’s answers rather than reading a script aloud.
How can leaders coach the process in live deals?
Training introduces a method; coaching tests whether a seller can use it under real customer conditions. RevCentric’s “Sellers Teaching Sellers” and “Teaching in the Trenches” approach centers proven sales operators and practical work, including live calls where appropriate. That makes it possible to coach the moment: a vague question, an unsupported claim, or a next step that has no buyer commitment.
Before a call, agree on one process objective. It might be to confirm the business impact, clarify who owns a decision criterion, or secure agreement on a test plan. After the call, review what the buyer actually said and identify the next action. Avoid grading the seller on whether they used a particular phrase; assess whether the conversation produced credible evidence and buyer progress.
Keep manager coaching narrow enough to repeat. One useful sequence is: state the deal question, ask the seller what evidence exists, identify the gap, and rehearse the next customer conversation. A closed-loop training approach can help connect skill development with observed field behavior.
Coach prospecting as well as later-stage calls. Review an actual message or call opening, identify the buyer problem it is meant to surface, and practice a more precise question. In a live opportunity, listen for whether the buyer validates the problem, adds stakeholders, corrects an assumption, or commits to a next action. The point is not to script every exchange. It is to build the seller’s ability to recognize evidence and respond well when the conversation takes an unexpected turn.
What should the manager do when evidence is missing?
Do not ask the seller to fill the gap with a confidence rating. First establish whether the missing information is material to the next decision. If the buyer’s approval path is unknown but a proposal is due tomorrow, decide whether the seller can contact the relevant stakeholder, ask the champion to confirm the sequence, or adjust the proposal conversation to resolve the uncertainty. If a metric is not yet verified, mark it as an assumption and plan a buyer conversation to test it.
After that discussion, rehearse one concise question and the likely follow-up. For example: “Who else needs to agree that this test is successful?” If the buyer names another group, ask what that group will need to see and how they will participate. This preparation turns coaching into a specific action rather than a general reminder to “qualify better.” Record the learning so the next manager review can check whether the gap was resolved.
How do you implement changes without disrupting the team?
Make changes in a deliberate sequence. A complete redesign can create confusion if the CRM, training, and manager routines all change at once without a shared definition of success.
- Choose a narrow problem. Select a recurring breakdown with a clear cost to deal quality, such as weak qualification before a technical evaluation.
- Map the buyer decision. Identify what the customer must decide and what information is needed to decide it.
- Define evidence and actions. Set stage exit evidence, seller actions, manager prompts, and the asset that supports each action.
- Test against real opportunities. Walk through current deals with sellers and managers. Remove criteria that cannot be observed or that do not improve a decision.
- Align systems and practice. Update CRM definitions only after the process is clear. Then rehearse the specific conversations and coach them in the field.
- Review and adjust. Ask whether managers can make more consistent decisions and whether sellers can explain the buyer’s next decision more clearly.
Before rollout, test the revised stage language with several roles using the same anonymized opportunity story. Ask each person to classify the stage, explain the evidence, and name the next action. If their answers differ, do not solve the problem with more mandatory fields. Clarify the definition, examples, and manager prompt, then repeat the exercise. This simple calibration prevents a process document from appearing clear while teams apply it differently.
Plan a controlled release. Explain what changes, why it changes, which existing opportunities need translation, and where sellers can find the new assets. Give managers a short set of deal-review questions before asking them to coach the new process. Revenue Operations should map the old and new stage definitions, determine which reports or automations depend on them, and communicate any temporary reporting caveats. Enablement can then practice the buyer conversations tied to the new criteria rather than delivering a generic overview.
How do you know what to change first?
Prioritize a problem using three questions: does it recur across multiple deals, does it block a consequential buyer decision, and can the team influence it through a clearer action or evidence standard? A one-off exception may deserve a deal-specific response, not a redesign. A repeated failure to identify the approval path before proposal may justify changes to discovery prompts, manager review, and CRM evidence together.
Make the pilot small enough to learn from. Apply the revised criteria to a limited set of active opportunities and ask managers to note where the definition helps, where it creates friction, and what evidence remains hard to obtain. Do not treat the pilot as proof of revenue impact. Its immediate purpose is to expose ambiguity and usability problems before broad adoption.
Process indicators should inform learning, not become promises of revenue outcomes. Track whether evidence is present, whether next steps are buyer-confirmed, and where opportunities stall. Interpret those signals alongside deal context; a field-completion rate alone does not prove that the process is working.
RevCentric Partners builds customized, programmatic sales performance programs for B2B technology teams. The company’s founders include Dick Dunkel, who authored MEDDIC at PTC in 1996; its approach connects proven playbooks with practical coaching rather than podium-only theory. Explore sales performance services or learn more about RevCentric’s background.
Frequently Asked Questions
When should a B2B technology company bring in sales process consultants?
Consider outside help when stages mean different things to different teams, deal reviews rely on opinion instead of buyer evidence, or a new process has not translated into field behavior. First define the specific breakdown you need to solve.
Is MEDDIC the sales process?
No. MEDDIC is a qualification framework that helps teams understand important deal elements. A sales process also defines buyer progress, seller actions, stage evidence, and management routines.
Should every stage require CRM fields?
No. Require information only when it helps a seller or leader make a meaningful decision. Keep the evidence observable and avoid fields that are collected without a clear use.
How can leaders tell whether a redesigned process is being adopted?
Review live opportunities and calls, not just training attendance or field completion. Look for consistent interpretation of stages, stronger buyer-confirmed next steps, and coaching that addresses specific evidence gaps.
A sound process makes customer decisions easier to understand and seller execution easier to coach. Begin with a real deal problem, define the evidence that would resolve it, and build only the structure the team can put to work.
