Positioning Canvas
Adapted from April Dunford — one page, one product.
For Series B SaaS growth leads managing 3-6 experimenters who currently use spreadsheets, generic project tools, hiring a consultant, we are a Experimentation platform for growth teams that delivers ship 5x more experiments without adding headcount, because purpose-built for growth teams, shared creative library, one-click variants.
Why it works▾
One page, one product: the Positioning Canvas wins in 2026 when Clay, PostHog, and Claude make positioning measurable instead of mystical.
When to use▾
Use this framework when a 2026 operator needs to reposition a single product fast, without hiring a strategy layer or building a 40-slide deck. It is best for seed to Series C teams, category entrants, or a product that keeps getting “interesting” feedback but weak conversion. If you cannot point to 1 primary ICP, 1 enemy, and 1 buying trigger, use this canvas before spending on creative, outbound, or a site rebuild in Framer + Relume.
Steps in detail▾
1. Define the customer problem in one sentence
Start with a single problem statement that names 1 buyer, 1 pain, and 1 urgency trigger. In 2026, do not workshop this in a doc for 3 weeks; pull 50 call transcripts into Common Room, score them with Clay, then use Claude 4.5 Sonnet to cluster the language by urgency and intent. Example: “RevOps teams cannot reconcile product-qualified leads before pipeline leakage kills Q2 forecast accuracy.”
2. Identify the best-fit market and exclude the rest
A Positioning Canvas works only if it says who is not the buyer. Use Clay enrichment plus Default signals to rank accounts by headcount, tech stack, and hiring velocity, then use Apollo AI or Keyplay to exclude low-fit segments. Example: a developer-tool company learns via PostHog and Common Room that mid-market SaaS with 2+ PMMs converts 3x better than agencies, so agencies become an explicit non-target.
3. Map the category and your enemy
Name the category your buyer already understands, then name the old way you are replacing. In 2026, the winning move is usually “leaving Salesforce” or “migrating off HubSpot workflows,” not inventing a new noun. Example: an AI SDR vendor uses 11x plus Clay to show that “manual outbound” is the enemy, because 1 operator with an agent workflow outperforms 5 SDRs on reply quality and speed.
4. Prove the unique value with evidence
List 3 proof points that make the claim believable, and make each one observable in product or revenue data. PostHog can show activation lift, Northbeam or Triple Whale can show channel contribution, and Claude Code can analyse session replays or win/loss notes for patterns. Example: a Framer-based landing page says “cut time-to-launch by 72%,” backed by PostHog funnels and 20 Clay-enriched customer interviews.
5. Turn the canvas into a messaging system
Convert the canvas into 1 homepage headline, 3 use-case pages, 5 outbound angles, and 1 demo script. In 2026, do not hand this to a generic copywriter; feed the canvas into an OpenAI Agents SDK workflow with n8n, then generate variants for 11x, Regie.ai, and AdCreative.ai. Example: the same core position becomes a homepage in Framer, a Clay-segmented outbound sequence, and a Claude-generated objection-handling script.
Pitfalls▾
- 01Trying to support 4 ICPs in 1 canvas; decision rule: if it needs 2 audience rows, it is already too broad.
- 02Writing category language before customer language; rule: 20 customer quotes first, then 1 category label.
- 03Using vanity proof like traffic or impressions; rule: only metrics tied to pipeline, activation, or retention count.
- 04Treating the canvas as a static doc; rule: rerun it after every 30 Clay-enriched losses or 30 PostHog activation events.
- 05Copying April Dunford as theory; rule: every box must connect to a 2026 system like Clay, PostHog, Attio, or 11x.
Get one interactive framework in your inbox each week
Every Monday. No fluff.