Market Choice, Customer and Economic Case · Lesson 2

Map buying jobs and relative value

11 min read

Lesson objectives

  • Map buying jobs across stakeholders and test a value promise against an incumbent and inaction.
Reading tools

The user, the buyer and the person who can say no

A maintenance team may like scheduling software while a finance manager sees its cost before the time it saves. “The customer” is therefore not always one person. In organizational selling, map the user doing the work, the problem owner accountable for its result, the budget holder and the reviewer who can reject an integration or contract. One person may fill several roles, especially in a small account. The map is not an exercise in collecting names; it exposes different success criteria. A technician wants a clear route, an operations manager fewer cancellations, finance a return worth paying for, and technology a maintainable integration. One vague promise to all four may convince none of them.

Define a customer “job” as the progress someone seeks in a specific situation, not the product feature requested. Strategyzer’s Value Proposition Canvas describes customer jobs, pains and gains, then maps them to the offer’s pain relievers and gain creators. Use it as a hypothesis tool: what must the buyer accomplish, what does the current method cost, what might be lost in switching, and what observed result would make a trial successful? If an operations manager asks for a dashboard, ask what decision they want to make after looking at it. Their job may be preventing double-booked technicians, not obtaining a dashboard for its own sake. The verification test changes when the job changes, even if the product does not.

Establish the comparison baseline. The alternative is not necessarily a commercial competitor. It may be a spreadsheet, another employee or a decision to delay. In a hypothetical case, estimate the current process’s time, duplication and rework, then separate cash cost from value that is difficult to price. An hour saved is not automatically an hour of payroll that can be recovered; the time might become faster service. Nor can one interview support “customers save 20%.” Tie each material claim to its source, denominator and period. If evidence is thin, offer a range and scenarios, or state a promise to be tested rather than a fixed number.

Compare on three layers. First is the buyer’s outcome: do speed, accuracy or a risk they care about improve? Second is switching cost: must they migrate data, train staff or tolerate temporary disruption? Third is proof: what can be measured before and after purchase without letting the vendor alone control the interpretation? A strong value proposition does not list ten features. It selects an important result for a defined segment, explains how the offer could produce it and names the conditions required. If the only difference is a longer feature list, the familiar incumbent may win because its cost and change burden are known. Do not hide a product limitation; it defines accounts you should defer.

Translate value across roles without inflating it

Test the offer through an evidence ladder, not by asking, “Do you like the idea?” Observe the current workflow or inspect a problem log with the customer’s permission. Ask about the last specific incident: when it occurred, who noticed it, what the team tried, and what impact was measured. Show a bounded prototype demonstrating the proposed mechanism, then seek an action that costs the customer something real: assigning a staff hour, sharing appropriately authorized data, or accepting a paid trial. Easy verbal approval signals interest. Practical commitment is stronger purchase evidence, though it is not a contract. If the prospect cannot name a budget owner and decision date, classify the opportunity as discovery rather than a likely close.

Each role needs its own acceptance evidence. A user may complete a task in five steps rather than ten, but that does not answer technology’s question about the data source. Operations may see a shorter wait, while finance needs to know whether it releases cash cost or raises sales. Technology may accept compatibility after a sample transfer, while contract review may need a term that cannot be guaranteed in advance for every jurisdiction. Put criteria on one scorecard: who measures each result, what threshold is acceptable, and what happens if a protection limit fails. Sales then cannot present user satisfaction alone as full organizational acceptance.

A calculation shows the danger of gross “value.” A support team handles 400 cases monthly and spends 15 minutes reentering data for each case: 400×15÷60=100 hours. A tool reduces reentry to nine minutes, freeing 40 hours monthly. Do not multiply 40 by the contribution from an extra case until you know how many cases an hour can handle and whether demand exists. If staffing stays fixed and there is no queue, quality may improve without immediate incremental cash flow. Either outcome matters, but “40 payroll hours saved” is false unless payroll or overtime expense changes. Keep time, cash and customer-experience measures distinct.

Compare offers over a stated horizon. One costs 24,000 yearly plus 8,000 setup; another costs 30,000 yearly without setup. Year-one costs are 32,000 and 30,000 before training and integration. Over two years, assuming unchanged prices and no other costs, they are 56,000 and 60,000. A buyer with a year-one cash constraint may prefer the second, while one planning three years may favor the first. Neither comparison settles the choice without exit probability and switching costs. If future prices cannot be guaranteed, show an increase scenario rather than silently assuming a fixed fee.

Separate a mechanism claim that can be shown now from a result claim that requires testing. “The system sends a weekly order recommendation for manager review” describes an observable mechanism. “It will reduce stockouts by 30%” is an unproven outcome for this account. Even after a trial, its scope matters: a few sites, fast-moving items and eight weeks. Do not transport that result to every item, branch or country without more evidence. This discipline gives sales a credible story and reveals when the product must change before spending more on marketing.

Before asking a buyer about our solution, ask about the last comparable purchase: who joined, what delayed it, and how alternatives were judged. A problem owner may say wasted time is paramount, while procurement notes reveal that lack of one integration killed a cheaper offer. That is an eligibility condition, not merely a price objection. Compare interview claims with actions such as requesting a trial, sharing relevant data or approving a written scope. If behavior differs from words, do not call the buyer dishonest. Organizational risk or switching burden may not have appeared in the hypothetical question. Record an alternative interpretation and test the message or package against another concrete incident.

“The competitor” can differ by role. Users compare speed with a spreadsheet, finance compares spending with another hire, and technology compares integration with its existing stack. Create one comparison sheet describing each alternative’s job, cost and switching risk rather than a feature grid against one commercial rival that ignores doing nothing. If the alternative’s cost is unknown, show the range at which the decision flips instead of inventing a number. When a buyer asks “why now?”, answer with a specific delay cost or opportunity in their operation, not an artificial discount deadline. The proposition is strong when every relevant role can see a sound reason and conditions for change, not only attractive copy.

Lesson summary

A sound promise names stakeholder outcomes against the incumbent with a protection measure.