Feature, Capability, Outcome, Metric [43]

Show notes

Your SEs are great at explaining what a feature does and terrible at answering 'so what?' A simple four-word tool that drags a team out of feature-dumping.

What Nate and Ava discuss

  • Feature to Capability to Outcome to Metric, and why the value is all the way right
  • Why the metric must come from the customer, never the template
  • Leading with the outcome before you click, so the demo becomes a series of payoffs

The move

Make feature-capability-outcome-metric a required step of demo prep — but populate the metric from the customer's own numbers. Discovery first, framework second.


🔗 Resources & Links: paths.to/presales

📅 Book a Discovery Call: calendly.com/serockstars-tim/discovery-call

New comment

Your name or nickname, will be shown publicly
At least 10 characters long
By submitting your comment you agree that the content of the field "Name or nickname" will be stored and shown publicly next to your comment. Using your real name is optional.