Category of one positioning

Purpose

A business that looks like one of a shelf of near-identical options gets compared on price. This skill changes the frame, so buyers stop comparing rates and start asking for the business by name. The output is a positioning package built from the business's own words, not from generic marketing copy.

When to use

• Buyers compare the business on price, or describe it in the same words as its competitors.
• An expertise-led business is winning on rates rather than on authority.
• A founder needs a reframed problem and category language, not a messaging house.

Route elsewhere when:

• The question is a full messaging framework. Use positioning-messaging-designer.
• The question is a scan of what competitors claim. Use competitive-white-space.

Inputs

• The business's own description: website, service pages, headlines, and profile text.
• The closest competitors' descriptions, to build the shared-language list.
• The ICP, named concretely by the user. If it is not available, ask for it.
• An interview answer for each pain point: what is broken, why it is broken, and the business's own solution.
• The process the business runs to get its results, in order.
• Confirmed proof points and results. Nothing is written without them.

Procedure

1. Diagnose interchangeability. List the words the business and its competitors share. Mark those as banned from the final package. Capture the business's own phrasing word for word, without polishing it.
2. Narrow the ICP. Name buyer types with an industry, stage, or revenue band. If the ICP cannot be found, ask and wait. Do not invent it.
3. Interview for each pain point. Ask three questions and keep the answers verbatim: what is broken in the industry, why it is broken, and what the solution is. Do not answer for the user.
4. Frame the problem as old way against new way. Build directly from the interview answers. Each side is one line: the old way, why it quietly fails, and what the new way replaces it with.
5. Map the new way as a process before naming the result. Use the business's real steps, in order.
6. Package the expertise as a named system. Use steps, a framework, or a method, built from real engagements and proprietary data rather than generic tooling.
7. Build category language. Give the problem, the mechanism, and the outcome a name the market can attribute to the business. Start from the business's own phrasing and keep it where it is already sharp. Draft five to ten candidates.
8. Get approval on the reframe. Stop here until the user approves it. Everything downstream inherits it.
9. Assemble and pressure-test. Check that no phrase from the shared-language list survives, and that every claim traces to something the user has confirmed.

Output

• The old-way against new-way reframe.
• The process map, in order.
• The category language, five to ten candidates, with the one the user prefers marked.
• The named system, with its steps.
• A one-line positioning statement and a headline built from them.
• The pressure-test result: shared phrases found (expected none), and any claim without a confirmed source.

Quality bar

The package is built from the business's own words. The reframe is approved before any language or named system is built on it. No phrase from the shared-language list survives. No proof, result, or client name appears unless the user has confirmed it. Watch for a reframe written without the interview, language polished into generic copy, and a position set against a named competitor.

Rules

• Interview for each pain point before writing the reframe.
• Never invent the ICP, proof, results, or client names.
• Keep the user's own phrasing. Do not sand it into generic marketing language.
• Process before result.
• Position against the old way, not against a named competitor.
• Get approval on the reframe before building on it.