Two Field Guides.

Part III · Sell, Deliver, and Compete — Chapter 14

Selling is diagnosis and risk reduction

The Complete Masterbook · pages 48–51

A sale is not won when the buyer likes the product. It is won when the buyer has enough evidence to make a good decision—and you have enough evidence to deserve the buyer.

Imagine a founder leaving a demo with compliments, three requests for slides, and no next meeting. He calls it a promising opportunity. It is not yet an opportunity. Nobody has confirmed a costly problem, named a priority, exposed a decision process, or committed to an action. Warm words have been mistaken for commercial evidence.

Selling begins by refusing that mistake. Its proper job is to help a person with a real problem decide well, with less uncertainty than before. Sometimes the right decision is to buy from you. Sometimes it is to wait, solve the problem internally, choose another provider, or do nothing. If you would hide the last four possibilities because your fee depends on the first, you are no longer diagnosing. You are applying pressure.

The first competitor is the status quo

Before a buyer changes, four beliefs usually have to become credible:

1. Problem: something important is not working well enough. 2. Priority: solving it now deserves scarce money and attention. 3. Approach: a proposed kind of solution can improve the situation. 4. Provider: this particular provider can deliver with acceptable risk.

Builders tend to start at belief three because the product is what they know. Buyers often remain at belief one or two. They may agree that your product is clever and still decide that migration, approval, learning, or disruption costs more than the present pain. The status quo does not need to be excellent. It only needs to feel safer than change.

That makes honest selling a form of risk reduction. You clarify the present cost, show what would change, make assumptions visible, bound the first commitment, and explain what can go wrong. You do not manufacture urgency. A real trigger—a contract renewal, a capacity limit, an audit, a launch, a recurring failure—can create a buying window. A fake deadline merely borrows trust from the future.

Aim before you approach

An ideal customer profile, or ICP, is not a fantasy description of anyone who could use the product. It is a working hypothesis about the customer most likely to buy, succeed, stay, and refer. Write it in observable terms:

  • • type of organization and operating model;
  • • scale or complexity at which the problem appears;
  • • current process, tool, or workaround;
  • • trigger that makes the problem timely;
  • • person who feels the pain and person who controls the money;
  • • conditions that make delivery safe and successful;
  • • conditions that make the account a bad fit.

“Bengaluru startups” is not an ICP. “Independent recruitment firms running high-volume screening through spreadsheets, after adding a second delivery team, with an operations leader who owns turnaround time” is closer. It gives you somewhere to look and something to disprove.

Prospecting then becomes hypothesis testing. Look for problem signals, not merely names: a new location, a hiring pattern, a public service failure, a new compliance burden, an expiring vendor contract, or a workflow described in the customer’s own material. A researched approach can be short: the observed signal, a cautious problem hypothesis, relevant proof, and a small request. Do not claim to know the buyer’s problem before the buyer confirms it.

Qualify the account and the decision

In a small purchase, one person may discover, approve, use, and pay. In a larger sale, those roles split.

RoleWhat mattersEvidence to seek
Economic buyerControls funds and accepts the business caseAccess, stated criteria, or a credible route to approval
Process ownerLives with the operational problemA reconstructed workflow and owned consequence
UserMust adopt the changeUse-case fit, effort, training, and failure concerns
Technical or risk reviewerCan veto on feasibility, security, legal, or compliance groundsRequirements and review path surfaced early
ChampionWants the change, has influence, and will work internallyA concrete act: meeting secured, data shared, plan advanced
Procurement or financeControls paper, vendor onboarding, and termsKnown steps, owners, documents, and timing

Do not turn this into political theatre. It is simply a map of whose work, money, or reputation the decision affects. A friendly contact is not automatically a champion. Test the relationship with a reasonable action: ask for the process owner, the approval criteria, a sanitized workflow, or a jointly prepared business case. Enthusiasm produces praise. A champion produces movement.

Single-threaded deals are fragile. Your contact may change roles, lose priority, or discover a veto late. Multithreading means earning appropriate access across the decision group while protecting your contact’s position. Ask as service: “Finance will probably question how the savings are calculated. Would it be useful to involve them now, or should I prepare a one-page case you can take to them?” Never go around a contact by surprise. For a founder-led sale, a light qualification scorecard is enough. Confirm:

  • • the problem and its owner;
  • • impact in the buyer’s measures;
  • • the desired outcome and success test;
  • • the economic buyer or approval route;
  • • decision criteria and competing alternatives, including no change;
  • • decision and paper process;
  • • a real timing condition;
  • • delivery fit and unacceptable risks.

Unknown is an acceptable answer. Pretending it is known is not. Qualification is not a pass/fail interrogation; it shows what must be learned next and whether the deal deserves another hour.

Let evidence move the stage

A pipeline becomes fiction when a seller advances deals because calls felt good. Give each stage a buyer- owned exit condition.

StageJobEvidence required to advance
TargetChoose where to spend attentionICP fit plus a plausible trigger
ConversationEarn permission to diagnoseMeeting with a relevant role
DiscoveryEstablish present state, impact, and processBuyer confirms the problem, consequence, and decision path
ProofReduce solution and provider riskBuyer tests relevant proof against agreed criteria
Business caseMake the internal decision legibleAssumptions checked; champion can explain value and risk
CommercialResolve scope, price, terms, and paperOpen issues owned and traded, not ignored
DecisionObtain an answerSigned agreement, explicit no, or a dated buyer action
Delivery and expansionProduce what was soldValue verified; renewal, expansion, or exit decided honestly

The labels can change. The discipline cannot. A stage records what the buyer has done, not how confident the seller feels. “Send information” is not an advance unless the information serves a named decision and a next action is agreed. “Reconnect later” needs a real trigger and date or it belongs outside the active forecast.

Disqualification protects both sides. Leave when there is no meaningful problem, no owned priority, no path to a decision, no safe delivery fit, or no economics that can work. Say it plainly: “From what I have heard, changing now may cost more than the problem. I suggest we close this for the moment. If the volume or deadline changes, we can reassess.” Mean it. A graceful no preserves time and reputation; a bad-fit yes mortgages both.

· SALES pp. 2–13 · ASC pp. 85–87 · GE ch. 13. Frameworks are adapted as decision aids; unsupported conversion percentages and universal thresholds are omitted.