title: Positioning → Messaging Framework Reference source: "Positioning methodology + Use Case Messaging Canvas" category: Oracle-Knowledge-Base tags:
- positioning
- messaging-framework
- copy-strategy
- icp
- spiced
- use-case-canvas
- gtm status: published
Positioning → Messaging Framework Reference
The Core Problem: The Copy Skip
Most companies follow this broken path:
- ICP → (skip) → Copy
- Result: constant rewriting. Copy becomes decoration, not strategy.
The missing piece: Positioning + Messaging Framework.
The Chain: ICP → Messaging → Copy
| Stage | Input | Output | Purpose |
|---|---|---|---|
| ICP + SPICED | Market research, interviews | WHO they are, WHAT they feel | Audience definition |
| Positioning | ICP + competitive context | WHERE you stand in their mind | Market perception |
| Messaging Framework | Positioning + Use Case Canvas | WHAT to say (structured, reusable) | Source of truth |
| Copy | Messaging Framework | Every channel (LinkedIn, web, email, sales) | Execution |
Key insight: Skip the messaging framework, and copy becomes decoration. Build it right, and copy becomes inevitable.
1. Positioning: 12 Elements to Consider
Positioning is not a tagline. It's the structure that makes your solution visible in a crowded market.
Primary Positioning Elements
These answer the immediate question: "Why should I choose you?"
| Element | Definition | Example (B2B GTM) |
|---|---|---|
| Category | What market do you play in? | "Marketing strategy & execution platform" |
| Alternative | What do they compare you to? | "Hiring freelancers or big agencies" |
| Differentiation | What makes you meaningfully different? | "No-code, repeatable workflows -- vs. ad-hoc work" |
| Capabilities | What can they DO with you that they can't elsewhere? | "Launch 10 campaigns a week without hiring" |
| Benefits | What results do they get? | "Faster go-to-market, lower cost per acquisition" |
| Features | What powers those capabilities? | "Pre-built templates, workflow automation, analytics" |
Secondary Positioning Elements
These add specificity and defensibility.
| Element | Definition | Relevance |
|---|---|---|
| Personas | Who specifically benefits most? | Narrows focus (e.g., "CMOs at B2B SaaS") |
| Use Case | What job are they hiring you for? | "Building repeatable GTM processes" |
| Overarching Problem | What big-picture struggle ties it all together? | "Marketing can't scale without hiring" |
| Sub-Problems (1, 2, 3) | What specific blockers do they face? | Inconsistent messaging across campaigns; Long launch cycles; Campaign quality relies on individuals |
2. Functional Description Formula: 6 Types of Positioning
Use one of these as your single, repeatable positioning line. Buyers recognize it fast. It works across proposals, LinkedIn, and sales calls.
1. Problem/Outcome-led
Structure: "We help [who] reduce [pain] so they achieve [result]."
Example: "We help B2B SaaS CMOs reduce campaign launch time by 70% so they ship GTM campaigns faster than competitors."
When to use: Your main value is solving a pain that's costly or time-consuming.
2. Job-to-be-Done
Structure: "When you need to [job], use [us] instead of [old way]."
Example: "When you need to build repeatable GTM playbooks, use our platform instead of hiring new marketers."
When to use: The job is clear and well-defined; you're the obvious alternative.
3. Category + Competitor
Structure: "Unlike [alternative], we're [difference]."
Example: "Unlike hiring freelancers, we give you repeatable, team-owned processes."
When to use: You're competing for budget/mindshare against a specific rival.
4. Segment/Niche-led
Structure: "[Category/product] built for [niche], not generic [everyone]."
Example: "GTM strategy platform built for B2B SaaS teams, not generic marketing departments."
When to use: You own a specific niche and don't try to appeal to everyone.
5. Primary Value Vector
Structure: "The most [value angle] way for [who] to [result]."
Example: "The fastest way for B2B SaaS marketers to go from strategy to execution."
When to use: Your primary differentiator is speed, cost, simplicity, or scale.
6. Strategic Archetype
Structure: "The [archetype] in [category] for [who] who need [job]."
Example: "The operating system for B2B SaaS GTM teams who need to ship campaigns at scale."
When to use: You're positioning as a foundational platform or system, not a tool.
Pick ONE. Make it repeatable. Back it with proof. Keep it consistent across all channels.
3. The Use Case Messaging Canvas
The canvas has two sides: The OLD Way (what they do now) and The NEW Way (what becomes possible with you), connected by a central Use Case and Persona.
Canvas Structure
+-----------------------------------------------------------------------------+
| CURRENT WAY (LEFT) |
+-----------------------------------------------------------------------------+
| |
| OVERARCHING PROBLEM USE CASE |
| (Big Picture Struggle) (What they are trying to do) |
| In their words, from interviews. The job/outcome, clearly defined. |
| |
| PROBLEM (3 Specific Pains) PERSONA |
| Word-for-word from interviews. Who specifically benefits most. |
| (This is the "P" in SPICED) Names, titles, behaviors. |
| |
| LIMITATION OF CURRENT WAY NEW WAY (RIGHT SIDE BEGINS HERE) --+ |
| (Anti-Feature) (Product Capability) | |
| What's broken about how they What becomes possible. | |
| do it now. (Opposite of left). | |
| | |
| CURRENT WAY PRODUCT FEATURE | |
| (Anti-Capability) (What powers the ability) | |
| What they actually do today. Features serve capabilities, | |
| (This is the "C" in SPICED) don't lead with them. | |
| | |
| BENEFIT | |
| (Result of using the ability) | |
| Directly answers a Pain. | |
| | |
| DESIRED OUTCOME | |
| (Main goal) | |
| The aspirational end state. | |
| | |
+-----------------------------------------------------------------------------+
Left Side: The Current Way (Their Reality)
Overarching Problem (Big Picture Struggle)
- The market-level pain, in their words
- From interviews and SPICED analysis
- Example: "Marketing teams can't scale GTM without hiring more people."
Problem (3 Specific Blockers)
- Pain 1: from SPICED interviews (exact language)
- Pain 2: from SPICED interviews (exact language)
- Pain 3: from SPICED interviews (exact language)
- These are the "P" in SPICED; use their exact words
Limitation of Current Way (Anti-Feature)
- What's broken about how they do it now
- Example: "Campaign launches take weeks because each one is custom-built."
Current Way (Anti-Capability)
- What they actually do today (often manual, time-consuming, fragile)
- This is the "C" in SPICED
- Example: "Build campaigns from scratch each time, relying on individual expertise."
Center: The Job & Persona
Use Case (What they are trying to do)
- The specific job or outcome
- Example: "Build repeatable GTM playbooks that the team can execute without hiring."
Persona (Who specifically)
- Name, title, behaviors, context
- Example: "Sarah, VP Marketing at a B2B SaaS company with $5-50M ARR"
Right Side: The New Way (Your Solution)
New Way (Product Capability)
- Each capability is the OPPOSITE of a Current Way step
- What becomes possible
- Example: "Use pre-built, customizable campaign templates that launch in days."
Product Feature (What powers the ability)
- The specific technical or product lever
- Features serve capabilities; don't lead with features
- Example: "Drag-and-drop workflow builder with 50+ pre-built campaign templates"
Benefit (Result of using the ability)
- Directly solves a Pain from the left side
- Example: "Save 3 weeks per campaign launch"
Desired Outcome (Main goal)
- The aspirational end state
- Example: "Ship 10 GTM campaigns a quarter without hiring"
4. The Opposites Method
The secret: Every New Way element is the OPPOSITE of an Old Way element.
This is how the canvas writes your messaging for you.
| Current Way (Left) | → Opposite → | New Way (Right) |
|---|---|---|
| "Campaign launches take weeks" | → | "Launch campaigns in days" |
| "Relies on one expert's knowledge" | → | "Repeatable for anyone on the team" |
| "Each campaign is custom-built" | → | "Use proven templates and workflows" |
| "Time is the blocker" | → | "Speed is the advantage" |
| "Cost goes up with volume" | → | "Cost stays flat as you scale" |
How to Fill the Canvas
Start with SPICED Analysis
- Interview customers, map their world
- Capture exact language: Problems (P), Critical Events (C), Ideal state (I), etc.
Fill the Left Side First
- This is THEIR reality, not your narrative
- Use their words from interviews
- If it doesn't come from SPICED, it's not positioning -- it's fiction
Flip Each Row to the Right
- Problem → Benefit (the benefit directly solves the pain)
- Anti-feature → Product Feature (what was broken → what's now possible)
- Anti-capability → Capability (what they did manually → what the system does)
The Opposites Write Your Messaging
- You don't invent messaging
- You extract it from the contrast between Old and New
5. From Framework to Copy
The messaging framework is NOT a document you write once and file away. It's the operating system for everything your team says.
Your messaging appears in:
- LinkedIn posts and articles
- Website copy (homepage, product pages, case studies)
- Sales decks and pitches
- Email campaigns
- Customer calls
- Proposal templates
Three tools working together:
| Tool | Purpose | Feeds Into |
|---|---|---|
| SPICED | WHAT to say (the substance) | Use Case Canvas |
| Use Case Canvas | WHERE to put it (structure) | Copy outlines |
| Opposites | HOW to say it (the contrast) | Every headline, email, post |
Result: One canvas. One source of truth. Copy writes itself.
6. Story Building: The Weekly GTM Sequence
A practical 3-day workflow to build positioning and messaging from real customer evidence.
Tuesday: ICP + Personas
Goal: Map your best-fit customer from real deal evidence
Activities:
- Pull last 5 closed deals (biggest deals, happiest customers)
- For each deal: Extract company size, role, industry, approval chain
- SPICED ICP creation: Interview or review notes
- Situation: Where do they work? What do they do?
- Pain: What's keeping them up at night?
- Ideal state: What would "solved" look like?
- Critical event: What triggered the search for a solution?
- Economic buyer: Who owns the budget?
- Decision criteria: How do they evaluate options?
Output: Ideal Customer Profile + 2-3 key personas with names, titles, and SPICED attributes
Wednesday: Position Yourself
Goal: Map positioning from best-customer language and competitive context
Activities:
- From Tuesday's ICP: Extract category, alternative, differentiation
- Interview customers: "What were you comparing us to?"
- Fill in Primary Positioning Elements (category, alternative, diff, capabilities, benefits, features)
- Write ONE positioning line (use the 6 formulas above)
- Test it: Does it resonate with your best customers? Can sales say it naturally?
Output: Single positioning line + defensible rationale, backed by customer language
Thursday: Messaging
Goal: Map messaging from SPICED ICP + positioning. Validate through content, calls, outreach.
Activities:
- From Tuesday's SPICED: Fill the LEFT SIDE of the Use Case Canvas (their reality)
- From Wednesday's positioning: Fill the RIGHT SIDE (your solution)
- Use the Opposites method to ensure every new way element counters an old way pain
- Test messaging: Use it in 3 outreach emails or calls -- listen for resonance
- The two sides of a messaging framework become content: "Old Way vs. New Way" posts are high-engagement
Output: Complete Use Case Canvas + first 5 pieces of messaging-backed content
7. Worked Example: Filled Use Case Canvas
Context
Company: RevOps Platform for Enterprise SaaS Customer SPICED context: Interviewed 5 customers at $50M+ ARR companies. Common theme: pipeline visibility and forecast accuracy degrading as they scale; current processes rely on Excel and manual reconciliation across 3+ CRMs.
Completed Canvas
OVERARCHING PROBLEM USE CASE
"We can't forecast revenue anymore. "Build a single source of truth for pipeline
Our pipeline data lives in 3 systems and revenue visibility that doesn't require
and nobody trusts the numbers." 15 emails to close."
PROBLEM (3 specific blockers) PERSONA
"Forecast is always wrong by Sarah, VP RevOps at $50M SaaS
$2-5M; nobody knows which forecast (5 years in role, 3 systems managed)
to trust" "I spend 20 hours a month on
reconciliation, not strategy"
"Deals get stuck in the pipeline;
we have no visibility into where
they're really at"
"Every process change means
updates to Excel and scripts"
LIMITATION OF CURRENT WAY NEW WAY
"Reconciling pipeline takes 20 hours "Get real-time visibility into pipeline
a month; we're always 3 days behind across all CRMs in one dashboard"
on actuals"
CURRENT WAY PRODUCT FEATURE
"Pull data from 3 CRMs, map deal "Multi-CRM connector; automated
stages, reconcile in Excel, reconciliation engine running 6x
distribute to reps via email" daily with conflict resolution"
BENEFIT
"Save 16 hours a month on
reconciliation; forecast accuracy
within 5%"
DESIRED OUTCOME
"Close deals faster because RevOps
catches stuck deals in the pipeline
within 24 hours"
What This Canvas Produces
Positioning line (Problem/Outcome formula): "We help VP RevOps at enterprise SaaS companies eliminate spreadsheet reconciliation so they can build accurate forecasts in under 5 minutes."
LinkedIn messaging (Old vs New): "Most RevOps teams spend 20 hours a month reconciling pipeline data across 3 CRMs. They chase data instead of chasing revenue. We built RevOps Platform to give you real-time visibility instead. Same deal data, zero reconciliation."
Sales email opener: "Sarah, I noticed Acme just launched 3 new products in parallel. I'd guess forecast accuracy is getting harder, not easier, especially when pipeline lives in both Salesforce and HubSpot. That's the exact problem we solve for VP RevOps at companies your size. Want to see how in 15 min?"
Website headline: "Unified pipeline intelligence across your entire CRM stack: no reconciliation required."
All of these speak the language of the customer's reality (SPICED left side) and contrast it directly with the new way. The canvas makes the messaging inevitable.
8. Usage Guide
When to Use This Reference
- AFTER building the ICP (see icp-builder skill)
- BEFORE writing any sales collateral, website copy, or content calendar
- DURING launch planning and competitive positioning discussions
How to Use Each Section
| Section | Use Case | Who |
|---|---|---|
| 6 Positioning Formulas | Write your LinkedIn headline, one-liner for proposals, elevator pitch | Founders, marketing lead |
| Use Case Canvas | Structure customer deliverables (enablement, case studies); source of truth for messaging | GTM team, copywriter |
| Opposites Method | Generate LinkedIn content (high engagement); ensure consistency across channels | Content creator, social team |
| Primary Positioning Elements | Brief sales team and ensure shared language | Sales manager, marketing |
| Weekly GTM Sequence | Run recurring positioning workshops; build messaging artifacts | Growth lead, full team |
Common Mistakes to Avoid
- Writing positioning before SPICED → Guessing instead of listening
- Filling the right side before the left → Your narrative overwrites their reality
- Using "nice" words instead of customer words → Messaging doesn't resonate
- Forgetting the Opposites → New way doesn't clearly contrast with old way
- Creating a document instead of a system → Canvas collects dust; copy doesn't improve
Appendix: Blank Use Case Canvas Template
Use this template to build messaging for any use case.
OVERARCHING PROBLEM USE CASE
[Big picture struggle, in their words] [Job/outcome being done]
PROBLEM (3 specific blockers) PERSONA
[Pain 1 - from interviews] [Name, title, context]
[Pain 2 - from interviews]
[Pain 3 - from interviews]
LIMITATION OF CURRENT WAY NEW WAY
[What's broken] [What becomes possible]
[Opposite of limitation]
CURRENT WAY PRODUCT FEATURE
[What they actually do today] [What powers the ability]
[Opposite of current way]
BENEFIT
[Result of using ability]
[Solves a pain from left]
DESIRED OUTCOME
[Aspirational end state]
Version: 1.0 Last Updated: 2026-03-06