Founder-led sales: lead with the buyer’s outcome

Show buyers how your product could improve their work. Lead with the outcomes they care about and the evidence they can assess, not a tour of every feature.

Adapted by the EWOR Team from Sean Gallagher’s article (opens in a new tab)2 min read

Start with the buyer’s objective

A buyer can understand your technology and still have no reason to purchase it. Sean Gallagher's sales-coaching approach starts with the customer's objective: show how the work gets done today and what your product could change. Decide which outcome matters most to the buyer before choosing which feature to demonstrate.

Translate capabilities into outcomes

Before preparing your pitch, identify what this particular buyer is responsible for improving. The relevant outcome might involve revenue, costs, cash flow, time, risk, employee productivity or customer experience.

Don't assume an outcome matters simply because your product could influence it. Ask how the organisation handles the work today, what the buyer finds unsatisfactory and how they would recognise an improvement.

Next, connect each proposed outcome to a specific product capability. If the link depends on several unsupported assumptions, the claim is not ready for a sales conversation. Group related benefits and lead with the few that address the buyer's stated priorities. Keep other capabilities available for a technical evaluation rather than crowding them into your opening pitch.

Show the before and after

Build a simple before-and-after account of the buyer's actual workflow. Explain who does the work today, where delays or errors occur and what would change with your product. Distinguish what you have observed from what you have estimated and what still needs testing.

Your demonstration should then focus on the relevant step rather than walking through the entire interface.

Ask whether the difference matters enough to influence a purchasing decision and what evidence the organisation would need to see. You might find that your favourite feature matters less to the buyer than an outcome you barely mentioned. Adapt your pitch based on what you learn. Your before-and-after account is a proposition to test, not proof that the promised result will materialise.

Be careful with risk and compliance claims

If the proposed benefit relates to compliance or risk, explain exactly which part of the workflow your product supports. Validate the claim, and do not promise that using the product guarantees compliance or eliminates risk.

Source: EWOR article by Sean Gallagher (opens in a new tab)

Get the next signal before everyone else.

Frameworks and contrarian theses for outlier founders, straight to your inbox. No fluff, no recycled advice, weekly.

The EWOR Signals newsletter