vercel-labs/positioning
Use when working out what a product is, who it's for, and what it competes with: the market alternatives, the ideal customer, the differentiators worth claiming, and the positioning statement that follows.
npx skills add https://github.com/vercel-labs/marketing-team-eve-template --skill positioning
Positioning is not a tagline. It's a decision about which market you're in and who you're beating, and the words come last. Work it in order, because each step constrains the next.
Get 1, 2, and 4 right and the statement writes itself. Skip to the statement and you get something true of every product in the category.
The alternative determines everything downstream, and picking the wrong one is the most expensive error available. Positioning against a well-funded incumbent when your customers actually arrive from a spreadsheet means your messaging answers questions nobody is asking.
Ask the user directly what the last few customers used before, and take the most common answer over the most flattering one.
A differentiator survives three tests. It has to be true, provable, and hard to copy. Fail any one and it isn't yours to claim.
Things that feel like differentiators and aren't: being easy to use, caring about customers, being fast, having a modern interface, being AI-powered. Every competitor claims all of these, so claiming them positions you nowhere. If a competitor's site would say the same sentence, delete it.
A segment is useful when its members share a problem, a budget, and a way of finding you. "Mid-market" is a size, not a segment. "Series B companies whose finance team still closes the books in spreadsheets" is a segment, because it predicts the problem, the buyer, and the search.
Pick the narrowest segment that can still support the business. Broad positioning feels safer and converts worse, because a message addressed to everyone sounds addressed to no one.
One paragraph, internal, written to be checked rather than published:
> For [segment] who [situation and problem], [product] is a [category] that [key benefit]. Unlike [the real alternative], it [the differentiator, with proof].
Then test it. Would a competitor's marketing team write the same sentence? Could a customer disagree with it? Does it name something you can prove? If any answer is wrong, the problem is upstream in the five questions, not in the wording.
references/frameworks.md has the fuller worked structure, a positioning-map format for handing back a competitive picture, and the failure patterns worth recognizing.
Sometimes the honest output is that the positioning isn't settled: the differentiator is unproven, or two segments are pulling in different directions. Say that. Write the options and what evidence would decide between them, rather than picking one and presenting it as concluded. The team can work with a stated question; it can't recover from confident guessing.
Take vercel-labs/positioning from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.