In short
- Capabilities are what your product lets a buyer do in their own work, said in the buyer's terms: the middle step between the feature you built and the result they get.
- In session 2 we map every capability, the pain it solves for your segment and the features behind it.
- We rank them by how much the problem hurts and the wow factor, and the top three become your USPs.
- The rest stay on the map, ready for the product page, the demo and the sales calls.
Ask a founder to describe the product and the answer usually lands in one of two places. Either it's the roadmap, module by module, or it's the big result: more pipeline, less time, lower costs.
Both are true, and both leave out the part a buyer needs in order to picture it: what they'll be able to do next week that they can't do today. That part is the capability.
What a capability is
A capability is something your product lets the buyer do, said as an action in their own world. A shared approval queue is a feature; the capability it gives is that a finance manager can sign off on every vendor invoice from one screen, and the result the buyer is after is closing the month days sooner.
Features describe what you built, results describe the change the buyer is after, and capabilities connect the two, so a buyer can see how the result happens. The USP page goes deeper on all three.
Why the middle step matters
Features on their own talk to the engineers who built them, and big results on their own could sit on any site in the category. The capability is the part that shows the buyer how the result happens.
Capabilities are what the buyer recognizes from their own week. When someone asks an AI tool for a product that does a specific job, it can only name you if your pages say plainly what the product lets the buyer do (more on the AEO page).
None of this replaces the value proposition. It still starts from the outcome the buyer wants. The capabilities underneath it are what make that outcome believable.
Mapping them
In session 2 we map all the capabilities of the product, with the founders and the heads of sales, product and customer success, because each of them sees the product from a different angle. For every capability we write down three things:
- The pain. Which problem, exactly, does this solve for the segment we chose in session 1? If it doesn't hurt that buyer, it's not part of the story.
- The features behind it. Which parts of the product make it work, so every claim has something real under it.
- The value. What it's worth to this buyer next to what they do today, their competitive alternative.
We leave with a detailed list: every capability, the features that support it, and what it means to the audience.
From the map to three USPs
With the map on the table, every capability gets two scores: the pain (how badly the problem it solves hurts this buyer right now) and the wow factor (how much it excites them compared with their current way of working). The three with the highest scores become your USPs.
When I ran Yalla Marketing through my own Positioning Builder, the capability it ranked first was giving every AI tool the company's context. The alternative it found was a founder doing marketing alone with generic AI tools that keep no company context, and none of the competitors it researched offered it, so it scored high on both pain and wow.
The same capability, different segments
A capability only has value for a specific buyer. A reporting feature can save one segment hours a week and mean nothing to another, because the second one doesn't report on that at all.
That's why the map comes after the segment. Map capabilities before you've chosen who you're for, and every one of them looks important, because somewhere there's a buyer who needs it. Map them for one segment, and the ranking gets much easier.
Where the rest go
Only three capabilities make it into the USPs, and the others are just as real. They stay on the map and show up later in the buying process: on the product page, in the demo script and in your objection handling. A capability that was cut from the homepage can be the exact answer to "but can it do X?" on a sales call.
When a new capability changes who you're best for, the positioning needs another look. The repositioning page covers what that means.
Capabilities in the sprint
Before session 1, my Builder reads your questionnaire, the competitor research and your demo and prospect call recordings. The demo shows what the product does, and the calls show which pains buyers name in their own words. In session 2 everyone who decides goes through the capability map together, scores it, and picks the three USPs, then sets the value proposition, the KPIs and your tone of voice. The full map goes into the messaging doc and your marketing brain, so every page and every AI tool works from the same list.
How does your own homepage score? Get a free homepage audit: your homepage scored on the same 7 dimensions of positioning, with a line from your own page behind each score. Free, private, never published.