API and platform companies do not lose because the product is worse. They lose because the buyer files them under an existing line item and compares them on price. Category design gives your product a name, a problem, and a reason to exist that the old category cannot answer.
The Problem
Your API gets compared inside a category your competitor defined
When a developer evaluates you, the first thing they do is decide what bucket you belong in – payments, observability, auth, messaging. Whoever named that bucket wrote the evaluation criteria, and those criteria favor them. You end up answering a feature checklist built around the incumbent's roadmap, defending why you lack a capability that only matters because they decided it should. The fight is rigged before the first call, and discounting is the only lever left.
The problem you solve has no name, so nobody budgets for it
Platform companies frequently solve a problem the buyer has not formally recognized yet – a new failure mode, a new integration surface, a cost that used to be invisible. If there is no name for that problem, there is no line in the budget, no internal champion who can requisition spend, and no urgency. Developers may love the product in a side project, but the purchase stalls because the buyer cannot explain upward why this category needs to exist. You win the demo and lose the budget cycle.
Your messaging describes the product instead of reframing the market
Most API companies write copy that lists endpoints, SDKs, and latency numbers. That is useful once a buyer is already convinced the category matters, but it does nothing to convince them it does. Without a point of view about why the old way is now broken, you are a better mousetrap in a market that does not believe it has a rat problem. Technical buyers are persuaded by a sharper model of their own world, not by your changelog, and feature-level messaging leaves that persuasion on the table.
Analysts and the ecosystem keep slotting you into the wrong quadrant
In the API economy, where you sit in an analyst grid, a marketplace taxonomy, or a partner directory shapes who finds you and how they judge you. When you let others categorize you, you inherit a comparison set that drags your differentiation into the noise. Integration partners describe you in their terms, marketplaces tag you under a saturated keyword, and inbound arrives expecting the wrong thing. You spend every sales cycle re-explaining what you actually are instead of selling the value of being the one company that owns a category.
How We Help
We start by interrogating the problem, not the product. In the first 30 days we interview your power users, your lost deals, and the developers who churned, and we map the language they use to describe the pain – not the language your marketing uses to describe the feature. We look at how the current category was framed, who framed it, and where its model of the world breaks down for the workloads you serve best.
Strategy is where we name the thing. We define the category – the problem space you intend to own – and write the point of view that makes the old approach look obsolete rather than merely worse. That point of view has to survive a technical audience, so it is grounded in real architectural shifts: a new primitive, a new integration model, a new cost curve.
Execution embeds us with your team to install the category across every surface a buyer touches. We rewrite the homepage and docs intro to lead with the problem and the new model before the endpoint list. We arm your developer relations and sales teams with the same frame so a conference talk, a sandbox tutorial, and a procurement deck all reinforce one story.
Measurement proves the category is taking hold, which is different from proving a campaign worked. We track whether inbound starts using your language unprompted, whether deals reference the new problem in their justification, whether analysts and the ecosystem start tagging you under your name instead of the incumbent's. We watch win rates against the old comparison set and the share of pipeline that arrives already framed your way.
Throughout, we keep the work honest by tying it back to revenue motion. A category that wins panels but does not move pipeline is a vanity exercise, and we treat it as one. We pressure-test the frame against actual sales conversations every two weeks and cut anything that sounds clever but does not change how a technical buyer reasons about their stack.
What we deliver
- Category thesis – the named problem space, the point of view, and the technical shift that makes the old category obsolete
- Buyer and developer language audit mapping the words real users use to the frame you will own
- Narrative install across homepage, docs intro, sandbox, and sales deck so every surface tells one story
- Developer relations and sales enablement so DevRel talks and procurement decks reinforce the same category
- Category-traction dashboard tracking unprompted language adoption, win rate shift, and analyst placement
In the API economy you do not get to choose whether your product gets categorized – only whether you do it or your competitor does. Category design is claiming the right to write the evaluation criteria before the buyer does.
Our Methodology
Our category design work runs as a 90-day sprint built for technical buyers, not a brand exercise. Phase one is excavation. We interview power users, churned developers, and lost deals to surface the real problem language and find the fracture in the incumbent's category model – the workload, cost, or integration pattern its story cannot account for.
Phase two is the thesis. We name the category, write the point of view, and stress-test it against a technical audience so it rests on a genuine architectural shift rather than a marketing claim. We translate the thesis into the concrete decisions it has to govern: how the docs open, how the sandbox introduces the product, how pricing is packaged, and what the sales team says in the first call.
Phase three installs the category across every buyer surface and measures whether it is taking hold. Unlike a brand agency that hands you a manifesto and leaves, we embed until your homepage, your DevRel motion, and your sales deck all tell the same story, and we track unprompted language adoption and win-rate shift to prove the category is doing real work in the pipeline.
How We Work
Initial engagements run 3 to 6 months because category design only proves out once the new frame survives real sales cycles. The first 30 days are excavation – power-user and lost-deal interviews, a language audit, and a teardown of the existing category and its blind spots. Days 31 to 60 produce the category thesis and point of view and pressure-test it against your sales team and a sample of technical buyers. Days 61 to 90 install the narrative across homepage, docs, sandbox, and sales materials and arm DevRel and sales to carry it.
Our team includes a category strategist who owns the thesis, a technical narrative lead who can write for a developer audience without dumbing it down, and an operator who installs the frame across product, docs, and sales surfaces. From your side we need access to power users and recent lost deals for interviews, a product or DevRel contact who controls the docs and sandbox experience, and your founder or head of product in the room for the thesis decisions, because category design is a strategy choice they have to own.
Weekly working sessions pressure-test the frame against live deals and refine the language. Monthly reviews track whether inbound and deals are adopting your category language, how win rates against the old comparison set are moving, and where analysts and ecosystem partners place you. Most platform companies see their own teams using the new frame within 30 days, inbound starting to echo it within 60, and a measurable shift in how deals are justified by 90 once the category has run through a full sales cycle.
- A named category the company owns instead of competing inside a rival's definition
- Higher win rate against the incumbent comparison set
- Inbound and deals that arrive pre-framed in your language
- Cleaner analyst and ecosystem placement under your category, not the incumbent's
If your api & platform companies company needs category design leadership, we should talk.
Expand your marketing team output with our experts
Let us take a custom approach to your growth goals by assembling and leading the best-in-class marketing team to support your next stage.
Frequently asked questions
How much does a category design engagement cost for an API or platform company?
Category design engagements typically run between $20K and $45K per month depending on how much excavation research the thesis requires and how many buyer surfaces need to be rebuilt around the new frame. A single-product company with a clean docs site sits at the lower end, while a platform with multiple developer surfaces and an existing analyst footprint sits higher.
How long before category design shows up in the pipeline?
Your own team usually adopts the new frame within the first 30 days, which is the precondition for everything downstream. Inbound starts echoing your category language within about 60 days as the narrative lands across the homepage, docs, and DevRel content.
How does the category design team integrate with our product, DevRel, and sales teams?
We embed rather than hand off a deck. The thesis is built with your founder and head of product in the room because it governs real decisions about packaging and roadmap.
What makes Winston Francois different from a brand or positioning agency?
A brand agency hands you a manifesto and a color palette and leaves the hard part – making the category true across the product – to you. We are operators who install the category into the surfaces a technical buyer actually touches: the docs intro, the sandbox first-run, the procurement deck, the DevRel talk.
How do you measure ROI from a category design engagement?
We measure whether the market adopts your frame and whether that frame moves money. Concretely: unprompted use of your category language in inbound and deal notes, win rate against the incumbent comparison set, share of pipeline that arrives already framed your way, and how analysts and ecosystem partners place you.
What type of API or platform company is the right fit for category design?
Companies that solve a genuinely new problem – a new primitive, a new integration surface, a cost the old category hid – but keep getting compared inside an existing bucket and losing on price. You need real product differentiation rooted in architecture, not just a nicer dashboard, because category design amplifies a true shift and cannot manufacture one.
