building-positioning-messaging

Use when messaging is inconsistent across sales and marketing, homepage conversion is low, buyers cannot articulate what makes you different, or positioning was never formally defined. Use when entering a new category, responding to competitive repositioning, launching a major product, or when customer research reveals a gap between how customers describe you and how you describe yourself.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "building-positioning-messaging" with this command: npx skills add amogha-dalvi/marketing_gtm/amogha-dalvi-marketing-gtm-building-positioning-messaging

Positioning & Messaging Framework

Overview

Positioning is the strategic decision of how you exist in your buyer's mind. Messaging is the language system that communicates that position. At $1M-5M ARR, nailing positioning is often the difference between efficient growth and expensive chaos.

When to Use

  • Messaging is inconsistent (reps say different things, website doesn't match sales pitch)
  • Homepage or landing page conversion rates are low
  • Buyers cannot articulate what makes you different
  • Positioning was never formally defined beyond founder intuition
  • Entering or creating a new product category
  • Competitors are actively repositioning you
  • Customers describe you better than your marketing team does
  • Launching a major product or entering a new segment
  • AI search engines are mischaracterizing what you do

Don't use when: You have a validated messaging framework from the last 12 months, conversion rates are strong, and sales pitch consistency is above 80%.

Quick Reference

PhaseDurationOutput
Positioning inputs assemblyDay 1Inputs Brief
Positioning strategyDay 2-3Category Decision, Positioning Matrix, Value Props
Messaging architectureDay 4-5Messaging Hierarchy by persona and stage
Messaging document buildDay 6Master Messaging Guide
Message testing & validationWeek 2-3Tested messaging with performance data

Core Deliverables

  • Positioning Statement -- Internal-facing strategic position: category, target, key benefit, differentiator
  • Value Proposition Architecture -- Primary value prop plus 3 supporting pillars mapped to JTBD and differentiators
  • Master Messaging Guide -- Elevator pitch, boilerplate, headlines, pillar messages, persona and competitive messaging, proof points, objection responses
  • Messaging by Persona -- Tailored pain, outcome, proof, and objection handling per buyer role
  • Messaging by Funnel Stage -- Awareness-appropriate language from unaware through most-aware

Common Mistakes

  • Positioning by features instead of outcomes
  • Using internal jargon customers never use (Customer Voice Library is the source of truth)
  • Trying to be everything to everyone ("all-in-one platform for everyone" = nothing for nobody)
  • Copying competitor positioning (same position = price competition)
  • Skipping testing (conference-room messaging often fails in market)
  • Changing positioning quarterly (positioning is long-term; messaging can evolve)
  • Letting features drive positioning instead of customer problems

Integration

Feeds into: designing-gtm-strategy, developing-brand-strategy, running-content-engine, optimizing-geo-visibility, creating-sales-enablement, executing-launch-playbook, reducing-cac

Refresh: Positioning review annually. Messaging document update quarterly. Message testing continuous. Persona messaging refresh every 6 months. Proof points update monthly.

See workflow.md for detailed phase-by-phase execution, messaging hierarchy templates, persona messaging matrices, testing methods, and integration point diagrams.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Web3

defining-icp-segmentation

No summary provided by upstream source.

Repository SourceNeeds Review
General

reducing-cac

No summary provided by upstream source.

Repository SourceNeeds Review
General

running-content-engine

No summary provided by upstream source.

Repository SourceNeeds Review
General

planning-marketing-budget

No summary provided by upstream source.

Repository SourceNeeds Review