---
name: category-positioning-sop
description: How to turn a thin AI wrapper startup into a category leader. Positioning SOP for AI-native startups. Use when the user mentions category positioning, turning an AI wrapper into a category leader, a positioning SOP, category design, or startup positioning.
triggers:
  - "category positioning"
  - "AI wrapper to category leader"
  - "positioning SOP"
  - "category design"
  - "startup positioning"
disable-model-invocation: false
title: category-positioning-sop
canonical_url: https://skilld.dev/gh/salikshah/startup-agent-skills/category-positioning-sop
last_updated: 2026-10-29T10:46:09.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [evals/evals.json](https://skilld.dev/api/skills-raw/salikshah/startup-agent-skills/category-positioning-sop/evals/evals.json).
>
> If the user asked to install this Skill, run `npx skilld install salikshah/startup-agent-skills/category-positioning-sop`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/category-positioning-sop`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/salikshah/startup-agent-skills/category-positioning-sop) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/category-positioning-sop`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/category-positioning-sop --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/category-positioning-sop --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Category Positioning SOP

## Intent
Turn a thin AI wrapper startup into a category leader. Most AI startups sound like wrappers over rented models. This SOP shows how to design a category narrative that makes a product the unavoidable answer in its category.

## Inputs
- Product name and description
- Current positioning (how the company describes itself)
- Top 3 competitors and their positioning
- Target customer (who buys, who uses)
- Unique technical or workflow advantage

## Process (SOP)

1. Run the Wrapper Test and decide whether the product is a wrapper.
2. Find the constraint outside the model: vertical, infrastructure, security, workflow, or data.
3. Design the category narrative: enemy, new category, core idea, and proof.
4. Write the one-liner: target customer, outcome, unique mechanism, proof metric.
5. Build the proof stack with a receipt for every claim.
6. Distribute the narrative through the channels where the audience already gathers.

If the product fails two or more Wrapper Test questions, position it as a feature or workflow layer until the constraint is real. When to stop: do not publish a category claim without at least one verifiable receipt.

### Step 1: The Wrapper Test
Run the 10-minute test:
1. Can a technical user get 80% of the output by pasting the core prompt into a general AI model directly? (If yes, it is a wrapper.)
2. Can a competitor clone the UI in a weekend? (If yes, no moat.)
3. Does a frontier-model vendor shipping the feature next quarter kill the business? (If yes, no defensibility.)

If the product fails 2+ tests, it is a wrapper. That is OK — most start here.

### Step 2: Find the Constraint Outside the Model
Companies that survive pick a narrow surface where they have an unfair edge:
- Vertical: regulated industries (healthcare, legal, finance)
- Infrastructure: agent memory, reward models, cold starts, latency
- Security: securing AI agents
- Workflow: owning the workflow end to end
- Data: proprietary data loops, network effects

### Step 3: Design the Category Narrative
Answer these questions:
- What enemy are you against? (e.g., "AI wrappers with broken onboarding")
- What new category are you creating? (e.g., "DevEx for AI startups")
- What's the one idea that defines you? (e.g., "Developer adoption is the byproduct, not the product")
- What proof do you have? (e.g., "1,000 paid customers, $0 ad spend")

### Step 4: Write the One-Liner
"I help [target customer] [do outcome] by [unique mechanism]. Proof: [metric]."

### Step 5: Build the Proof Stack
Every claim needs a receipt. Typical receipts:
- Adoption → GitHub stars, package downloads, active users
- Revenue → closed proposals, customer logos (with permission)
- Authority → awards, press, original research
- Content → assets produced, publishing cadence, measured reach

### Step 6: Distribute the Narrative
- X (daily): Technical insights, build logs, positioning teardowns
- LinkedIn (weekly): Long-form articles, teardown analyses, and operating notes
- YouTube: Short explainers and demos
- Website: The hub — product pages, proof, and contact

## Outputs
- Category narrative document
- One-liner positioning statement
- Proof stack (receipts for every claim)
- Distribution plan (X, LinkedIn, YouTube, website)
- Competitor positioning map

**Pre-flight checklist:**
- [ ] Wrapper Test completed
- [ ] Constraint outside the model named
- [ ] One-liner includes a proof metric
- [ ] Every claim has a receipt
- [ ] Distribution plan names an owner and cadence

## Evidence
Category design is a well-established positioning discipline: name the enemy, define a new category, and attach a proof stack so the category claim is verifiable. The Wrapper Test operationalizes the common "thin wrapper" critique of AI startups.

## Examples
**Before:** "We use AI to help teams work better." — generic, no category, no proof.
**After:** "We make AI agents safe to deploy in regulated healthcare workflows. 3 enterprise design partners, SOC 2 certified." — names the category, states the constraint, attaches a receipt.

The shift: move from describing capabilities to naming a category and proving you own it.

## Metrics
- Category named (Y/N). Target: one category name used consistently for 90 days.
- One-liner published (Y/N). Target: live on the homepage and in the founder bio.
- Proof stack complete (Y/N). Target: 3+ receipts.
- Distribution channels active (count). Target: 2+ channels with weekly cadence.
- Inbound conversations attributed to positioning (monthly). Target: 3+ per month by day 90.

## Anti-Patterns
- Listing capabilities instead of naming a category — "AI + analytics + automation" is a feature list, not a position
- Leading with company age or team size instead of the customer outcome
- Claiming "interdisciplinary" or "full-stack" without specifying the constraint you own
- Skipping the Wrapper Test — if the product is a wrapper, admit it and fix the constraint before claiming a category
