Turn capability into an offer

An offer makes a valuable change specific enough to buy, deliver, measure, and price without confusion.

discipA buyer asks, “How much?” The inexperienced seller names a number and begins defending it. The lined seller first confirms what is being bought: the problem, result, scope, timing, success measure, responsibilities, risk boundary, and alternative. Price without an offer is an argument about a number. Price inside a precise offer is a decision about an exchange.

Build the offer before the proposal

A complete offer answers nine questions:

1. Who is the customer and who is the economic buyer? 2. What current event or problem are we addressing? 3. What measurable result will this scope attempt to create? 4. What mechanism and deliverables will we provide?

5. What must the customer provide or decide? 6. What is included, excluded, and change-controlled? 7. What risks remain outside our control? 8. What will be paid, when, and under what acceptance terms? 9. What happens after success, partial success, or failure?

Use plain language:

We help [specific customer] move from [verified current state] to [measured target] through [mechanism and scope] over [time]. Success will be assessed by [measures]. The fee is [price and payment schedule]. The customer provides [inputs]. The work excludes [boundaries].

Promise only what you control. You can commit to process, deliverables, response standards, safeguards, and honest measurement. A customer’s final commercial result may also depend on adoption, data quality, internal decisions, demand, or third parties.

Triangulate the price

No single formula discovers the right price. Use three views:

Delivery viability. The price must support direct cost, support, rework, acquisition, overhead, tax obligations, risk, and enough contribution to keep the promise. Cost creates a floor for a viable scope; it does not prove customer value.

Customer economics. Compare the fee with the verified cost of the problem, the value of the improvement, the risk reduced, and the alternatives. Do not claim all theoretical value. Ask what portion is attributable to your work and what uncertainty remains.

Market evidence. Observe what similar qualified buyers choose among credible alternatives. A competitor’s list price is context, not truth. Your proof, scope, risk, terms, and segment may differ. Price is also a capacity decision. When demand exceeds responsible delivery, a higher price, tighter qualification, narrower scope, or longer lead time may protect quality. When demand is weak, diagnose segment, urgency, trust, offer clarity, and reach before concluding that price alone is wrong.

Measure response with midpoint elasticity

For a discrete price test, calculate percentage changes from the midpoint. Using the starting value as the base produces different elasticity depending on which direction you describe the same move.

Elasticity = [(Q₂ − Q₁) ÷ ((Q₁ + Q₂) ÷ 2)] ÷ [(P₂ − P₁) ÷ ((P₁ + P₂) ÷ 2)]

WORKED ARITHMETIC · ASSUMPTIONS SHOWN Worked example · one bounded price test

Assume a standardized offer moves from ₹10,000 to ₹11,000 across two equally sized, otherwise comparable cohorts of qualified opportunities. Quantity purchased moves from 100 to 92.

Midpoint quantity change = −8 ÷ 96 = −8.33%. Midpoint price change = ₹1,000 ÷ ₹10,500 = 9.52%. Elasticity = −8.33% ÷ 9.52% = approximately −0.88. For this segment, offer, and test period, quantity was less responsive than price in proportional terms. Revenue moved from ₹10,00,000 to ₹10,12,000. If variable cost remained ₹3,000 per sale, contribution before fixed costs moved from ₹7,00,000 to ₹7,36,000. The test supports a local decision. It does not establish permanent demand: seasonality, sample mix, competitor response, renewal behaviour, and longer-term switching can change the result.

Test one meaningful change at a time where practical. Keep the segment, qualification standard, scope, payment terms, seller quality, and measurement window comparable. Follow applicable law and fairness requirements; never vary price using protected characteristics or deception.

Package choice without hiding the trade

Good packages serve genuinely different needs. A useful three-level structure might vary scope, response time, implementation support, risk-sharing, or usage. State the differences clearly and recommend the level that matches the diagnosed need.

Avoid artificial scarcity, unusable low tiers, hidden fees, or an expensive option created solely to manipulate comparison. Anchors influence decisions; use them to clarify the range of legitimate choices, not to conceal value.

A paid pilot should include:

• • one problem, user group, and bounded environment;
• • baseline, success measures, and review date;
• • customer access and responsibilities;
• • privacy, security, safety, and legal boundaries;
• • price, payment, acceptance, and change terms;
• • a decision rule for stop, revise, or expand;
• • separate permission for any logo, testimonial, or case study.

Free work can be rational when it produces a deliberate asset—learning, proof, or public contribution—but “free until they see value” often creates unbounded scope and weak commitment. Name the investment and limit it.

Trade; do not leak

When a buyer asks for a lower number, diagnose the reason. A budget ceiling, a competing scope, procurement target, cash-timing problem, and doubt about value require different responses.

Reduce scope before casually reducing price. If you make a concession, receive a useful commitment in return: prepayment, longer term where appropriate, narrower support, phased delivery, faster decision, reference participation, or a larger standard scope. Put the complete trade in writing.

Never let a discount make responsible delivery impossible. Never invent urgency. Silence after stating the price is not a crisis; it is the customer thinking.

· EF pp. 13–18, 26–27 · SALES pp. 31–32 · TABLE pp. 30–33 · GE ch. 12. Mechanisms paraphrased; midpoint elasticity replaces the source corpus’s simple-base shortcut.