Position by Subtraction: Verbs and Anti‑Personas
A step‑by‑step guide to position by subtraction using competitor verbs and anti‑personas, with a worked example and a 6‑week validation plan.

For practicing PMs in crowded markets. By the end, you will have a verb-based competitor map, three anti-personas, one clear positioning sentence, three tactical consequences, and a 6‑week validation plan you can run with sales, design, and engineering.
Position by subtraction. Map competitors as verbs your users hire them for. Name three anti-personas you will not serve. Combine both into a single line that guides what you stop building, what you integrate, and who you sell to.
Why subtracting works
Feature parity blurs you. Verbs are what customers actually do. When you chart competitors as verbs, you see overlaps and gaps fast. Anti-personas sharpen trade-offs. They force a choice: who you will turn away so the right users see themselves.
This is useful because it makes trade-offs concrete. You can name what to stop building, what to route to a partner, and who is your ICP for sales. It gives a repeatable template the team can argue over with real outcomes, not slogans.
Tip: Use a value lens like the Value proposition canvas to check that your verbs tie to pains and gains, not just internal ideas.
Steps to position by subtraction
Write 5–7 named competitors your buyers compare you to. Name the 2–3 user groups you serve today.
For each competitor, write 2–4 plain verbs customers hire it for. No features. Verbs like “collect,” “approve,” “reconcile,” “expense.”
Describe who you will not serve and why. Each with segment, trigger, and the verb you will not support.
Combine your verb map and anti-personas into one sentence. Then set three consequences: product scope, pricing/packaging, and GTM focus.
Design small tests: messaging, talk tracks, prototype flows, and partner routes. Decide one feature to hold or to replace with a partner build.
Competitor verbs: a simple template
| Competitor | Primary verbs users hire it for | Secondary verbs you will ignore | Notes |
|---|---|---|---|
| Competitor A | e.g., collect payments, manage subscriptions | e.g., invoice approvals, PO matching | List what you will route to a partner, not build. |
| Competitor B | e.g., reconcile accounts, run reports | e.g., dunning, customer reminders | Call out the verbs that are not your job. |
| Competitor C | e.g., submit expenses, reimburse | e.g., invoice creation, vendor onboarding | Be plain. Keep verbs short and unambiguous. |
Anti-personas sharpen the edges
Write three anti-personas that you will disqualify. Each should be active and specific.
- Segment: who they are (industry, size, workflow).
- Trigger: what event signals they are not for you.
- Excluded verb: the action you choose not to support.
Avoid passive statements like “not our focus right now.” Say what you will route to a partner and why.
Turn it into a sentence and decisions
Your positioning sentence format:
For [ICP] who need to [your primary verbs], we are [category] that helps them [outcome in plain words] — not for [anti-persona 1], [anti-persona 2], or [anti-persona 3].
Then set three consequences:
- Product scope: what you will stop building, what you will double down on, and what you will integrate.
- Pricing and packaging: how you make the value legible to the ICP and unattractive to anti-personas.
- GTM focus: ICP definition, routes to disqualify, and partner paths.
Run a 60‑minute workshop
- 5 min — State the problem and the users.
- 15 min — Draft competitor verbs (silent write, then converge).
- 10 min — Write and vote on three anti-personas.
- 15 min — Draft the one-line positioning.
- 10 min — Choose three consequences and one feature to hold or partner.
- 5 min — Assign owners for the 6‑week plan.
- Competitor-verb map (one table).
- Three anti-personas.
- One positioning sentence.
- Three consequences with owners.
- A single decision: hold a feature or route to a partner build.
Common mistakes to avoid
- Equating verbs with features. “Has dunning” is a feature. “Collect late payments” is a verb.
- Passive anti-personas. “Not enterprise” is vague. Name the trigger and the excluded verb.
- Aspirational positioning. If a prospect cannot verify it from a demo or trial, it is fluff.
- Skipping consequences. If nothing is stopped, you did not position.
- Letting edge cases drive scope. Write them into anti-personas and integrate instead.
Worked example: a mid‑market invoicing app
Context: You compete with Stripe Billing, QuickBooks, and Expensify. You serve B2B services firms that send invoices to clients. You need a clear space.
| Competitor | Primary verbs users hire it for | Secondary verbs you will ignore | Notes |
|---|---|---|---|
| Stripe Billing | manage subscriptions, collect recurring payments | invoice approvals, PO matching | Partner for subscription-heavy prospects. |
| QuickBooks | reconcile accounts, run accounting, produce reports | advanced dunning, client-side approvals | Integrate for ledger and reporting. |
| Expensify | submit expenses, reimburse employees | client invoicing, collections | Out of scope for client billing flows. |
| Your app | create invoices, route for client approval, collect faster | subscriptions, full accounting, employee expenses | Focus on getting invoices approved and paid. |
- SaaS subscription teams (Segment). Trigger: more than 70% of revenue is subscription. Excluded verb: manage subscriptions. Route: Stripe Billing integration.
- Finance-led accounting buyers (Segment). Trigger: RFP lists GL, AP, AR consolidation. Excluded verb: reconcile accounts. Route: QuickBooks integration and referral.
- Travel-expense heavy companies (Segment). Trigger: need card controls and reimbursements. Excluded verb: reimburse employees. Route: Expensify partner.
For mid‑market B2B services teams who need to create invoices, get client approval fast, and collect on time, we are the invoicing app that shortens time‑to‑pay — not for subscription‑heavy SaaS, accounting system replacements, or expense management.
- Product scope: hold the subscription module; invest in approval flows, smart reminders, and ACH collection; build first-class integrations to Stripe Billing and QuickBooks.
- Pricing and packaging: price per paid invoice or per active payer; remove expense-related add-ons; two plans that emphasize faster collection.
- GTM focus: ICP = agencies and consultancies with 20–200 employees; sales disqualifies subscription-first and accounting-first buyers; partner routes for the three anti-personas.
- Week 1: ship a landing page with the new line; measure click-to-trial vs. baseline; add a question to self-qualify anti-personas.
- Week 2: run 10 prospect calls with a new talk track; log reasons for disqualification and objections.
- Week 3: prototype approval and dunning flows; 5 usability sessions with target users; capture whether they recognize their jobs-to-be-done.
- Week 4: partner routing test; when a subscription keyword is detected, offer Stripe path; track accept rate.
- Week 5: pricing smoke test; present per-paid-invoice framing in 5 deals; record response and deal velocity.
- Week 6: review data with sales, design, engineering; decide to keep or adjust line; confirm the held feature or greenlight partner build.
How to use this in meetings
Bring the verb map template. Keep verbs to four words or less. Ask the team to replace feature nouns with action verbs. Read anti-personas out loud and confirm the route for each. End with a single decision: hold one feature or route it to a partner. Add owners and dates to the 6‑week plan before the room breaks.
What you walk away with
- Competitor-verb map you can show on one slide.
- Three anti-personas with triggers and routes.
- One positioning sentence that sales can say and design can draw.
- Three consequences: product scope, pricing/packaging, GTM focus.
- A 6‑week experiment plan to validate or adjust.
Why this is surprising: it flips the default. Instead of adding features to look unique, you subtract audiences and actions to make your space obvious and defendable.


