Qualification: Fit, Intent, Process, Commitments

When a “great discovery call” turns into a dead deal

A founder finishes what felt like a strong first call. The buyer had real pain, asked smart questions, and even said, “This looks promising.” The founder sends a recap deck and waits. A week later: silence. When they finally reconnect, the buyer says, “We’re still evaluating options,” and can’t name who else is involved, what criteria matter, or what needs to happen internally to approve anything.

That stall isn’t a follow-up problem—it’s a qualification problem. You learned “they have pain,” but you didn’t learn whether this opportunity is real, winnable, and tractable inside the buyer’s organization.

This lesson gives you a qualification system that matches the way advanced discovery works. If discovery creates decision-grade clarity, qualification tells you what to do with that clarity: advance, recycle, or disqualify without guessing or hoping.

Qualification as proof: Fit, Intent, Process, and Commitments

Qualification is often taught as “ask about budget and authority.” At intermediate level, that’s too blunt to be reliable. Better qualification treats the sales motion as a series of tests: can this buyer succeed with you (fit), do they actually plan to act (intent), do they have a viable path to a decision (process), and will they make the small agreements that prove momentum (commitments).

Here are the core definitions you’ll use:

• Fit: Your ability to solve the right problem for this buyer under their real constraints (use case, integrations, security, timeline, team capacity, change tolerance).

• Intent: Evidence they prioritize solving it now (urgency drivers, internal sponsorship, cost of inaction, willingness to mobilize).

• Process: The actual decision path (stakeholders, evaluation steps, approvals, procurement/legal/security gates, timeline reality).

• Commitments: Specific, mutual next actions that create forward motion (introductions, data access, pilot agreement, security review kickoff, meeting cadence).

The key principle: qualification is not interrogation; it’s alignment plus evidence. You’re not trying to “catch” the buyer. You’re trying to prevent the most expensive failure mode from the previous lesson: discovery that sounds busy but produces no usable decision data. Qualification is where you convert that decision data into a clear go/no-go stance and a mutually understood plan.

A helpful analogy is the medical consult from advanced discovery: discovery diagnoses; qualification determines the treatment plan and whether the patient will follow it. A correct diagnosis with no adherence still fails. In sales terms, the buyer might be in pain but unwilling to change, unable to navigate approvals, or not serious enough to invest the effort required to buy and implement.

Fit: can you solve it here, with these constraints?

Fit is not “they match our ICP on a slide.” Fit is the intersection of problem narrative + constraints + your actual solution boundaries. If you leave a call saying “they need our category,” you haven’t qualified fit; you’ve only categorized the problem. Decision-grade fit requires you to test whether the outcome they want is achievable in their environment.

Start by anchoring fit in the buyer’s problem narrative and the impact you quantified. If the buyer says they lose 18–22% of inbound demos due to slow follow-up and you can reduce response time with automation, that’s promising—but only if you can operate within their tooling, permissions, and ownership model. Fit questions become sharper when tied to mechanisms: “Where does lead assignment happen today?” “What system is the source of truth?” “What happens when a rep doesn’t follow the process?” Those questions connect directly to the root-cause mindset from advanced discovery.

Best practice is to qualify fit by explicitly checking constraints early, even when it feels “later-stage.” Security review lead times, data residency needs, integration requirements, and admin ownership routinely kill deals late if you avoid them now. Fit also includes organizational capacity: do they have someone who will own rollout, definitions, and change management? If the buyer wants a “fix” that requires RevOps, IT, and the frontline team to adopt new behaviors—and none of those teams are reachable—you may have a theoretical fit but a practical mismatch.

Common pitfalls show up in two directions. One pitfall is happy-ears fit: you interpret enthusiasm as feasibility and skip hard checks (like “can we integrate?” or “who maintains definitions?”). Another pitfall is over-disqualifying based on surface constraints (“they use a different CRM, so no fit”) without exploring workable paths (middleware, phased rollout, scoped use case). A typical misconception is that fit is purely product capability; in reality, fit is also implementation reality, and implementation reality is shaped by decision dynamics, resource availability, and constraints you only learn through structured questioning.

Intent: are they willing to act—or just interested?

Intent is evidence that the buyer will mobilize to change their current state. Plenty of buyers have pain and curiosity; fewer are ready to pay the switching costs: time, political capital, vendor evaluation work, and internal disruption. Your job is to replace “they seem excited” with observable signals that action is likely.

Strong intent usually has a trigger and a consequence. Triggers include board pressure, renewal timelines, seasonal peaks, a competitor move, headcount changes, or a public miss that leadership now tracks weekly. Consequences are what happens if they do nothing: revenue loss, churn risk, compliance exposure, or leadership credibility damage. This connects directly to the advanced discovery emphasis on converting vague pain into measurable impact. If the buyer can articulate impact but shrugs at timelines, you probably have relevance, not intent.

Best practice is to test intent through “skin in the game” behaviors. Are they willing to involve the people who own the problem (RevOps, IT, finance, security)? Will they share baseline data so you can verify ROI ranges? Will they align on success metrics, not just request “a demo”? You don’t need them to commit to purchase; you need them to commit to the work of evaluation and internal alignment. When intent is real, buyers lean into specificity because specificity helps them get approved.

Pitfalls often look like politeness. A buyer says “this is a priority,” but won’t schedule the next meeting, won’t introduce stakeholders, and won’t confirm a decision date. Another pitfall is mistaking urgency for intent: “ASAP” can mean “I’m stressed,” not “we will navigate procurement.” A common misconception is that asking about urgency drivers feels pushy. In practice, it feels professional when you frame it as protecting time: “I want to make sure we match your timeline and don’t create extra work if this isn’t something you’ll tackle this quarter.”

Process: what actually has to happen for a “yes”?

Process qualification is how you prevent the classic stall: “We’re still evaluating.” The goal is not to extract an org chart; it’s to build a reliable map of how decisions get made in this specific organization, with this specific risk profile. This is where the previous lesson’s focus on decision dynamics becomes operational.

A usable process map includes three layers. First, people: who has strong opinions, who signs, who can block (security, IT, finance, legal, procurement). Second, evaluation: what criteria matter (risk reduction, speed, cost control, reporting accuracy) and what evidence they require (pilot results, references, ROI model, security documentation). Third, sequence: the order and timing of gates (demo → technical validation → security questionnaire → procurement → contract redlines). The best way to get truth is to ask about history: “The last time you bought a tool like this, what happened step by step?”

Best practice is to treat process as a joint planning activity, not a hidden interrogation. You can share your intent openly: “If security review typically takes two weeks, we should start it early so it doesn’t become the bottleneck.” This de-risks the deal for the buyer and reduces your own forecasting errors. It also sets up a mutual action plan without forcing the term. When done well, process questions feel like competence, not pressure.

Common pitfalls include relying on a champion’s optimism (“we can move fast”) without verifying gates, and avoiding procurement/legal conversations until after excitement is built. That delay tends to backfire: you create internal momentum around a timeline that wasn’t realistic. A typical misconception is that process belongs later because it “kills the vibe.” In reality, process clarity often increases buyer confidence because it reduces uncertainty and makes the project feel manageable.

Commitments: the micro-agreements that prove momentum

Commitments are the observable proof that fit, intent, and process are real. If qualification is a set of tests, commitments are the pass/fail criteria you can see on the calendar and in the inbox. They are small, specific actions that move the opportunity forward and require the buyer to invest something meaningful.

A good commitment has five qualities: it’s specific, time-bound, owned (named person), mutual (you do work too), and decision-relevant (it reduces uncertainty about fit, intent, or process). “I’ll send you information” is not a commitment; it creates no shared motion and doesn’t reduce decision risk. “We’ll schedule a 45-minute session with RevOps to validate CRM fields and routing rules by Thursday, and you’ll share a sample export beforehand” is a commitment because it produces evidence and surfaces blockers.

Best practice is to earn commitments by summarizing alignment first—just like the strategic summarizing from advanced discovery. You reflect the story: impact, root causes, and constraints, then propose the smallest next step that meaningfully advances the decision. This prevents you from asking for a big “close” when the buyer is still uncertain, and it avoids the opposite mistake of taking tiny, non-decision steps that prolong the cycle.

Pitfalls show up as either overreach or underreach. Overreach is pushing for a pilot or contract step when the process map isn’t clear or stakeholders aren’t involved. Underreach is accepting vague next steps because you fear being “pushy,” which leads to the dead-end “send info” outcome. The common misconception is that commitments are about pressure. They’re actually about mutual integrity: if the buyer won’t make small, reasonable commitments, you’ve learned something important about intent and internal ability to execute.

How the four checks work together

The fastest way to become consistent is to treat Fit, Intent, Process, and Commitments as a single system rather than four separate topics.

Dimension	What you’re proving	Strong signals	Weak signals (risk)	What to do when weak
Fit	You can achieve outcomes within constraints	Clear use case tied to the problem narrative; constraints surfaced early (integrations, security, capacity); realistic scope	“We love it” but no clarity on systems/ownership; hidden security or data constraints; no team to implement	Narrow scope; run technical validation; disqualify if constraints block core value
Intent	They will prioritize action now	Trigger event + consequence; willing to share data; willing to involve stakeholders; timeline has a reason	Vague urgency (“ASAP”) with no driver; slow scheduling; curiosity-only behavior	Re-anchor cost of inaction; ask what happens if nothing changes; recycle if no priority
Process	There is a path to a decision	Named stakeholders; known gates; criteria defined; sequence and timing realistic	“No process”; decisions are “ad hoc”; procurement/security unknown; champion guessing	Map the last similar purchase; propose a simple plan; pause advancement until gates are known
Commitments	Momentum is real and mutual	Calendar holds next step; buyer completes agreed actions; mutual action plan emerges naturally	“Send me something”; missed follow-ups; no introductions; no data access	Reset with a summary + a specific ask; downgrade forecast; exit respectfully if pattern persists

[[flowchart-placeholder]]

Two real-world qualification walk-throughs (founders + sales teams)

Example 1: Founder selling B2B analytics to a VP Sales (forecast accuracy)

The VP Sales says forecasting is “a mess,” and you already uncovered symptoms and causes: inconsistent stage definitions, reps updating CRM late, and leadership making decisions on noisy data. Now qualification turns that diagnosis into decision movement. You start with fit: confirm the environment (CRM, data sources, reporting stack), and test whether your product can realistically improve the specific mechanism—input reliability and definitions—not just add dashboards. You ask who owns stage definitions and enforcement, because without that operational ownership, the product can’t sustain accuracy gains.

Then you test intent by anchoring urgency in a driver. Is this tied to board reporting, a hiring plan, or a miss last quarter? You look for skin in the game: willingness to share a baseline (forecast vs. actual deltas) and to bring in RevOps, because RevOps typically controls the levers. If the VP won’t involve RevOps, that’s not a personality issue—it signals low intent or internal friction you need to name.

Next you qualify process: who besides the VP will weigh in (CFO for board confidence, RevOps for data governance, possibly IT/security if data movement is involved). You ask about the last analytics purchase: did it require security review, procurement quotes, or a pilot? With that map, you propose a commitment that reduces the biggest uncertainty: a working session with RevOps to validate definitions, data sources, and the real path to improving inputs. The impact is you avoid a demo-first cycle that excites people but collapses when ops reality appears. The limitation is that if operational ownership is missing, you may have to narrow to a diagnostic project—or disqualify rather than force a “tool-only” sale.

Example 2: Sales team selling workflow automation to an Ops Director (onboarding delays)

The Ops Director wants to automate onboarding because time-to-first-value is dragging. You already have discovery outputs: handoffs across CS, solutions engineering, and product; fragmented spreadsheets; delays caused by security reviews and unclear approvals. Qualification begins with fit by validating whether your workflow tool can connect to the systems that matter and whether the customer’s process is stable enough to automate. If every segment has a different security path, you may need to phase the rollout or start with a standard segment to prove value.

You then test intent by tying impact to business urgency: delayed onboarding increases support load and churn risk, and leadership is tracking it weekly. The strongest indicator of intent here is the willingness to do the unglamorous work: identify owners for each onboarding step, agree on baseline metrics, and share real examples of “last time it broke.” If the Ops Director can’t get those people in a room, automation will remain a wish, not a project.

Process qualification tends to be the make-or-break. You map who must approve: IT for integrations, security for data handling, finance for spend, procurement for vendor steps. You ask how long security questionnaires typically take and whether procurement requires multiple quotes. With that established, you ask for a concrete commitment: kick off security review early and schedule a scoped pilot planning session with IT and CS, with clear success criteria like reducing time-to-first-value by a defined range. The benefit is predictable momentum and fewer late-stage surprises. The limitation is that if integrations are blocked or ownership is unclear, the most honest outcome may be to pause advancement until prerequisites are met, rather than running demos that inflate expectations.

How to close the call without sounding pushy

Qualification doesn’t end with more questions; it ends with a clear, mutual decision about what happens next. The cleanest way to do that is to summarize and offer a crisp fork in the road. You can keep it natural and human while still being direct.

Use a structure like:

1. Confirm the story (impact + causes + constraints).
2. Name the remaining risks (usually process gates or missing stakeholders).
3. Propose the smallest next commitment that reduces the biggest risk.
4. Offer an out if it’s not a priority.

That last part matters. Counterintuitively, giving permission to pause often increases honesty and trust. It also helps you avoid the “polite yes” that drifts into ghosting.

The qualification mindset you can reuse immediately

Qualification works when you treat it as evidence gathering, not hope management. The four checks reinforce each other: Fit protects outcomes, Intent protects time, Process protects timelines, and Commitments protect momentum.

Key takeaways:

• Fit is feasibility, not just category match: constraints and ownership determine whether value can actually be realized.

• Intent is proven by mobilization: data sharing, stakeholder access, and urgency drivers beat enthusiasm.

• Process prevents stalls: map gates and sequence early using “last time you bought” questions.

• Commitments are your truth serum: specific mutual next steps reveal whether the deal is real.

Next, we'll build on this by exploring Buying Committees & Influence Mapping [25 minutes].