Positioning & Messaging
Positioning is not a tagline. It is not a marketing exercise you do after the product is built. Positioning is a strategic decision about where your product fits in the market — who it is for, what problem it solves, and why someone should choose you over every alternative. Get positioning wrong and your product is invisible. Get it right and the product sells itself.
What Positioning Actually Is
April Dunford's "Obviously Awesome" framework is the most practical approach to positioning. She defines positioning as the act of deliberately defining how your product is best in the world at providing something a well-defined set of customers cares a lot about.
Positioning answers five questions in order:
1. Competitive alternatives: What would customers use if your product did not exist?
2. Unique attributes: What do you have that alternatives do not?
3. Value: What value do those attributes create for customers?
4. Target customers: Who cares most about that value?
5. Market category: What market context makes your value obvious?
The order matters. Most companies start with the market category ("we are a CRM") and work backward. Dunford argues you should start with competitive alternatives and work forward. Your positioning is relative to what else exists, not absolute.
Competitive Alternatives
Competitive alternatives are not just direct competitors. They include:
Types of competitive alternatives:
Direct competitors: Products that solve the same problem the same way
Indirect competitors: Products that solve the same problem differently
Do-nothing: The customer just lives with the problem
Manual workaround: Spreadsheets, email, pen and paper
Internal tools: Custom solutions built in-house
For many products, the biggest competitor is not another product — it is the status quo. A project management tool does not just compete with Asana and Monday. It competes with the spreadsheet the team has been using for three years and is perfectly comfortable with.
Understanding competitive alternatives tells you what you are really selling against. If most of your target users currently use spreadsheets, your messaging should not focus on features that beat Asana. It should focus on why a purpose-built tool is worth the switching cost from a spreadsheet.
Unique Attributes & Value
Unique attributes are facts about your product. Value is what those facts mean for customers. The distinction matters.
Attribute vs value:
Attribute: "Our database uses columnar storage."
Value: "Your analytical queries run 100x faster."
Attribute: "We integrate with 200+ tools."
Value: "Your team can keep using the tools they already know."
Attribute: "Our platform is SOC 2 Type II certified."
Value: "You pass your enterprise security reviews without custom work."
Customers do not buy attributes. They buy value. But the attributes make the value credible. "Your queries run 100x faster" is a bold claim. "Your queries run 100x faster because we use columnar storage" is a credible claim.
Mapping Attributes to Value
List every attribute that differentiates you from the most common competitive alternatives. For each attribute, ask: "So what? Why does the customer care?" Keep asking "so what?" until you reach something the customer would pay money for.
Attribute: End-to-end encryption
So what? Customer data is secure
So what? Customers can store sensitive data without compliance risk
Value: Use one tool for all your data, including regulated data
Attribute: Open-source core
So what? Customers can inspect the code
So what? No vendor lock-in, community extensions
Value: Build on a platform you control, not one that controls you
Target Customers
Positioning is not for everyone. The tighter your target, the stronger your positioning. "We are for everyone" means "we are for no one" because your messaging cannot resonate with everyone simultaneously.
Segmentation That Actually Works
Demographics (company size, industry, geography) are a starting point but not sufficient. The best segmentation is based on the problem the customer has and how acutely they feel it.
Weak segmentation: "Mid-market SaaS companies"
Strong segmentation: "Engineering teams at mid-market SaaS companies that
have outgrown their monitoring setup and are losing
engineering hours to incident response"
The strong segmentation describes a customer who has a specific, acute problem. They know they have it. They are actively looking for a solution. Your product is obviously the right choice for them because your positioning speaks directly to their pain.
The Bowling Pin Strategy
Geoffrey Moore's "Crossing the Chasm" suggests starting with a narrow beachhead segment and expanding outward. Think of market segments as bowling pins. Knock over the first pin (your beachhead) and use that momentum to reach adjacent segments.
Beachhead: DevOps teams at Series B startups (50-200 engineers)
Adjacent 1: Platform teams at Series C-D companies
Adjacent 2: Enterprise infrastructure teams
Adjacent 3: Regulated industries (fintech, healthcare)
Each segment requires slightly different positioning. The core product is the same, but the emphasis shifts. DevOps teams at startups care about speed and simplicity. Enterprise teams care about compliance and scalability. Positioning adapts to the segment without changing the product.
Market Category
The market category is the context that makes your value obvious. It is the frame the customer uses to evaluate you.
Category choices for a collaboration tool:
"Project management" -> Compared against Asana, Monday, Jira
"Team communication" -> Compared against Slack, Teams
"Work management" -> Broader, less clear competition
"Operating system for teams" -> New category, you define it
Category choice has massive implications. It determines:
- Who you are compared against
- What features customers expect
- How customers find you
- What budget the purchase comes from
Category Strategies
Existing category, differentiated position. You compete in a known market but claim a distinct position. Example: Figma entered the "design tools" category but positioned as "collaborative design" — differentiating against Sketch's local-file model.
Sub-category. You create a more specific version of an existing category. Example: "Conversational AI platform" is a sub-category of "AI" and "customer support tools." The sub-category inherits familiarity while narrowing the competitive set.
New category. You define a market that did not exist before. Example: HubSpot coined "inbound marketing" as a category. This is powerful but expensive — you have to educate the market on why the category exists before you can sell your product.
Testing Your Positioning
Positioning is a hypothesis. Test it.
The 10-Second Test
Show your homepage or one-sentence pitch to someone in your target audience. After 10 seconds, ask:
- What does this product do?
- Who is it for?
- How is it different from X (their current solution)?
If they cannot answer these questions clearly, your positioning is not working. The fix is not a better tagline. It is sharper positioning that translates into clearer communication.
The Sales Conversation Test
Listen to sales calls. When prospects immediately understand the value proposition and the conversation moves to pricing and implementation, positioning is working. When prospects keep asking "but what exactly do you do?" or "how is this different from X?", positioning needs work.
The Support Ticket Test
Read support tickets. If customers are trying to use your product for a use case it was not designed for, your positioning may be attracting the wrong audience. If customers consistently do not discover your most differentiated features, your messaging is not highlighting the right value.
From Positioning to Messaging
Positioning is the strategic foundation. Messaging is how you express it. Good messaging flows directly from positioning.
Positioning statement:
For [target customers] who [have this problem],
[product name] is a [market category] that [key differentiator].
Unlike [competitive alternatives], we [unique value].
Example:
For engineering teams that waste hours on incident response,
PagerDuty is an incident management platform that automates
alerting and coordination. Unlike monitoring tools with basic
alerting, PagerDuty reduces response time by orchestrating
the entire incident lifecycle.
Messaging Hierarchy
Build a messaging hierarchy from your positioning:
Level 1: One-sentence pitch (elevator pitch)
"We help engineering teams resolve incidents 3x faster."
Level 2: Three key messages (landing page)
"Automated alerting that reaches the right person."
"Coordinated response that reduces chaos."
"Post-incident learning that prevents recurrence."
Level 3: Supporting proof points (sales deck, case studies)
- Specific metrics from customer stories
- Product features that enable each key message
- Competitive comparisons on each dimension
Messaging by Audience
Different audiences need different messaging even for the same product:
For the IC engineer:
"Stop getting woken up for alerts that are not yours."
For the engineering manager:
"Reduce MTTR and protect your team from burnout."
For the VP of Engineering:
"Turn incident response from a cost center into a learning system."
For the CFO:
"Reduce downtime costs by 60%."
Same product, same positioning, different emphasis based on what each audience cares about.
Real-World Examples
Basecamp: Anti-Positioning
Basecamp positioned itself not by claiming to be better than project management tools, but by rejecting the category's assumptions. "We do not believe in Gantt charts, resource allocation, or time tracking." This attracted customers who were frustrated with the complexity of traditional tools. The positioning was as much about what Basecamp was not as what it was.
Notion: Category Creation
Notion's early positioning was confusing: "all-in-one workspace" could mean anything. As they refined it, they created a sub-category: "connected workspace" that combined docs, databases, and project management. The category made sense because each component was familiar, and the connection between them was the differentiator.
Linear: Opinionated Positioning
Linear positioned itself against Jira by being opinionated: "The issue tracker built for software teams that care about quality." They did not try to be everything for everyone. They explicitly targeted engineering teams frustrated with Jira's complexity, and their messaging reflected that frustration directly.
Common Pitfalls
- Positioning by feature — listing features is not positioning. Customers do not buy features. They buy solutions to problems.
- Trying to appeal to everyone — broad positioning resonates with no one. Pick a target segment and own it.
- Copying competitor positioning — if your positioning sounds like your competitor's with different adjectives, you have not done the work. Positioning must be differentiated.
- Confusing positioning with branding — a new logo and color scheme do not fix a positioning problem. Branding expresses positioning; it does not replace it.
- Setting positioning once and forgetting it — markets change, competitors emerge, your product evolves. Revisit positioning at least annually.
- Letting positioning be a committee exercise — positioning by consensus produces mush. One person should own the positioning decision, informed by input from many.
Key Takeaways
- Positioning is strategic: who is it for, what problem does it solve, why you over alternatives. Messaging is how you express that strategy.
- Start with competitive alternatives, not your market category. Understand what you are really competing against, including the status quo.
- Map attributes to value. Customers do not buy features. They buy outcomes that features enable.
- Target narrowly. A tight beachhead segment with acute pain is better than a broad market with mild interest.
- Test positioning with real users: the 10-second test, sales conversation analysis, and support ticket patterns all reveal whether positioning is working.
- Revisit positioning regularly. It is a living strategy, not a one-time exercise.