What is product category positioning?
Product category positioning is the decision about which market your product belongs to in the buyer's head. The category does a lot of silent work: it tells a visitor what the product roughly does, who else they should compare it to, what it probably costs and which budget pays for it, all before they read your second sentence.
April Dunford's positioning work, which many SaaS teams use, treats the market category as a frame of reference: you pick the frame that makes your strengths obvious. Pick a frame buyers already understand and they fill in the blanks for you. Pick one they've never heard of and they fill in nothing, so every claim on the page has to carry its own context. That's why category is a positioning decision first and a copy decision second. If you're still separating the two, our guide to positioning vs messaging covers which comes first, and the wider SaaS website copywriting guide shows where category language sits on each page.
Should a startup create a new category or position in an existing one?
Most startups should position in an existing category or carve out a sub-category of one. Creating a new category is a valid strategy, but it's the most expensive one: you have to teach the market a problem, a name and a solution at the same time, usually with a small team and a short runway.
There are really three options, not two, and the middle one is the one founders skip.
Strategy | What the hero says | Works when | Main risk |
|---|---|---|---|
Existing category | "Project management software for agencies" | Buyers already search for and budget for the category | You look like one of many and compete on features |
Sub-category | "Project management built for client approvals" | A known category exists but one segment is badly served | Too narrow a slice to grow into |
New category | "The first client delivery platform" | Current terms genuinely don't describe the problem | Visitors don't know what you are or whether they need it |
A sub-category keeps the buyer's frame of reference (they know what project management software is) while giving you a reason to exist (you're the one built for approvals). You get most of the differentiation of a new category with a fraction of the education cost. For most seed and Series A teams, that's the right default.
How do you test whether new category language will confuse buyers?
Test new category language by asking whether a cold visitor could explain what you do after reading only the hero. If they can't, the category name is costing you conversions, no matter how good it sounds in the pitch deck. Run these five questions before you commit.
Can buyers name what they use today?
Ask five recent prospects what they used before you. If they all name the same type of tool, that's your existing category, and you're competing in it whether you like it or not.
Do buyers search for the old term or the new one?
Check whether anyone searches for your category name. If nobody does, you'll need content and SEO for the problem instead, which our guide to keyword research for a new product category walks through.
Is there a budget line for it?
Ask who pays and from which budget. A product that fits an existing budget line closes faster than one that needs a new line created.
Can you explain the difference in one sentence?
Write "Unlike [existing category], we [difference]." If that sentence is clear and true, a sub-category will probably do the job.
Does the sales call start with ten minutes of explaining?
If your team has to define the category before every demo, the website is failing at the same point. That's a signal to anchor the language, not to add more of it.
Score it honestly. If buyers name an existing tool, search for the old term and pay from an existing budget, you're in an existing category with a twist. That's good news. It means the market already exists.
When does category design actually make sense?
Category design makes sense when the old category frame actively hides your value, so being compared on its terms means losing. If buyers keep judging you against a checklist that misses the point, a new frame can be worth the cost of building it.
- The old frame misprices you. Buyers compare you to a cheap utility when you replace a team or a process.
- The problem is new. A technology shift created a job that no existing tool category covers yet.
- You can fund the education. Content, events, analyst relations and sales enablement for several years, not one launch.
- You have proof. Customers already describe the problem in your terms without being prompted, which you can check with voice of customer research.
If only one of these is true, you probably don't need a new category. You need a sharper sub-category and better proof. New category marketing is a long game played mostly outside the website: the homepage can't create a category on its own, it can only reflect one that's already forming.
How should a category name appear on the homepage?
A category name on the homepage should appear next to a term buyers already understand, never alone. The hero's job is to make a stranger understand what you are in a few seconds, and an unfamiliar label only helps once it's anchored to something familiar.
Three patterns work, in rough order of safety:
- Known category plus a qualifier. "Payroll for remote teams in 40 countries." The category is instantly clear and the qualifier does the positioning.
- New name, anchored. An eyebrow with the new category name, then an H1 that describes the outcome in plain words and a subhead that names what it replaces.
- Analogy bridge. "Like a CRM, but for partnerships." Fast to grasp, though it borrows a frame you don't own. Our piece on X for Y positioning covers when that backfires.
Whichever you choose, the subhead and the first section below the hero should answer "what is this, and who is it for?" in plain language. Our SaaS homepage guide goes section by section, and if the product is genuinely hard to grasp, explaining a complex product has the techniques for showing rather than naming.
For example, suppose a startup builds AI review tooling for contracts
Hypothetical example: the founders call it "Contract Intelligence" and want that as the H1. Running the five questions, prospects say they use a contract lifecycle management tool plus manual review, nobody searches for "contract intelligence" and legal ops already has a budget for CLM software.
The better hero keeps the familiar frame and adds the difference: an eyebrow reading "Contract intelligence", an H1 like "Review vendor contracts in minutes, not days" and a subhead that says it works alongside the CLM they already have. The new term is present, so the team can build it over time, but the page doesn't depend on it.
How does category positioning shape the rest of your messaging?
Your category choice decides who you're compared against, so it shapes which proof, features and objections appear on every page. Change the category and you change the comparison set, which changes almost everything below the hero.
In an existing category, buyers already know the checklist, so your page should show quickly that you meet it and then spend its space on the difference. In a sub-category, the page should name the segment early and use proof from that segment. In a new category, the page has to sell the problem before the product, which means more space for the before-and-after and less for feature grids.
Write this down once so every page and every writer uses it the same way. A messaging framework is the right place: category, competitive alternatives, the one-line difference and the proof for each claim. Then the value proposition on the hero becomes a summary of decisions you've already made, not a fresh argument every time someone edits the page.
Which category positioning approach should you choose?
Choose the cheapest frame that still makes your difference obvious. For most startups that's a sub-category: a known term plus a qualifier that names the buyer or the job you're best at. It gives cold visitors instant context and still gives you something to own.
