Understanding Positioning, Messaging and Category Design

Why positioning is a managerial decision, not a copywriting task

RelayOps's homepage says "modern incident management for engineering teams." Maya Chen, the CEO, likes the phrase. Jordan Park, the CTO, hates it because three lost deals cited "we already have PagerDuty." The argument is not about fonts. It is about whether prospects understand what RelayOps replaces, why switching is rational, and which budget line funds the purchase.

Positioning is the set of choices that answer a buyer's silent question: What is this, and why should I care now? When positioning is weak, every downstream function pays a tax. Sales spends extra calls explaining category basics. Marketing buys broad keywords that attract unqualified demos. Product builds features that impress the wrong buyer. Investors hear a TAM (total addressable market, revenue if you captured 100% of a broad category) story without proof of repeatable wins in a narrow segment.

From Unit 1, RelayOps chose a beachhead: U.S. Series B SaaS (software-as-a-service, software sold on subscription) companies with 80 to 300 engineers. The company reports $920K ARR (annual recurring revenue, subscription revenue recognized over a year), 21 customers, and roughly $44K ACV (average contract value, mean revenue per customer contract). Beachhead discipline tells RelayOps who to pursue. Positioning tells RelayOps what story those accounts should hear. This lesson introduces positioning, messaging (the words and proof that express positioning), and category design (whether you compete inside an existing market label or define a new one).

Managers who treat positioning as a marketing polish step often discover the mistake in win/loss reviews. Prospects say "interesting tool" but never advance. Champions love the demo but cannot explain the purchase to a CFO (chief financial officer). That pattern usually means positioning failed before copywriting began.

Positioning in the April Dunford tradition

April Dunford's positioning work gives early B2B (business-to-business, selling to other companies) teams a repeatable sequence. Dunford argues that positioning is context setting: you cannot communicate value until the buyer knows what you are being compared against. The sequence matters because teams instinctively start with taglines. Dunford starts with competitive alternatives.

Competitive alternatives are what customers would do if your product did not exist. This is not your feature comparison chart against named rivals. It includes spreadsheets, manual phone trees, Slack channels, and "do nothing." For RelayOps's beachhead, alternatives often include PagerDuty (a widely used incident alerting platform), ad hoc Slack war rooms, and overloaded on-call rotations documented in Google Docs.

After alternatives come unique attributes: capabilities your product has that alternatives lack. RelayOps might claim Slack-native escalation paths, automatic role-based paging rules tuned for mid-size SaaS teams, and faster mean time to acknowledge in the first 30 days. Attributes are not benefits yet. They are facts that must map to customer outcomes.

Value translates attributes into outcomes buyers fund. RelayOps might promise fewer false pages per engineer per week and faster executive visibility during Sev-1 incidents (severity level 1, highest urgency outages). Value requires proof: customer metrics, pilot results, screenshots, or references.

Target market characteristics describe who cares most about that value. RelayOps's beachhead ICP (ideal customer profile, written description of best-fit accounts) from Unit 1 is the input here: Series B U.S. SaaS, Datadog monitoring, Slack collaboration, weekly incident pain.

Finally, market category is the label buyers use to file your product mentally. Category choice affects budget source, competitive set, and sales cycle length. Is RelayOps "incident management," "on-call operations," or a new category like "incident response orchestration"? The label is not cosmetic. It sets expectations.

Dunford's insight for managers: positioning is a business strategy choice, not a sentence workshop. Changing category changes which competitors you invite into the evaluation. Changing alternatives changes which value proof matters. RelayOps cannot position well without agreeing on alternatives first.

Value propositions versus positioning

Founders often conflate value proposition (the promised economic and operational payoff for a specific buyer) with positioning (the full context that makes the promise believable). The value proposition is one layer in a messaging hierarchy (structured levels of language from company story down to field phrases).

At the top sits company narrative: why RelayOps exists in one paragraph. Example direction: "Engineering teams outgrow alert tools before they outgrow accountability for uptime." The narrative links beachhead pain to mission without listing features.

Below that is category statement: what bucket the product occupies. "On-call operations platform for mid-size SaaS engineering organizations."

Then value proposition for the economic buyer and champion: "Reduce on-call burden and speed incident acknowledgement without a six-month PagerDuty reimplementation." The proposition must name outcomes and implicit cost of alternatives.

Proof points support the proposition: "Northwind SaaS cut false pages 38% in 21 days." Proof must be segment-relevant. A hospital reference weakens credibility in a SaaS beachhead.

Feature pillars explain how delivery happens: escalation policies, Slack workflows, Datadog integration. Features are not the lead message in early GTM (go-to-market, choices about who you sell to and how). They answer "how" after the buyer accepts "why."

Field language is what account executives and founders say on calls: questions, stories, objection handlers. Field language should sound like customers, not like website adjectives.

A manager tests messaging hierarchy coherence with a simple drill. Read only the headline. Can you predict the proof points? Read only the proof. Can you infer the competitive alternative? If not, the hierarchy is inconsistent. RelayOps's old headline "modern incident management" failed the drill because it could describe PagerDuty, Opsgenie, or a consulting firm.

Category design versus competing in an existing category

Category design means defining a new market label you want buyers, analysts, and competitors to adopt. Category competition means accepting an existing label and fighting for share inside it. Both paths are valid. Both carry costs.

Competing in an existing category (for example, "incident management") gives buyers instant comprehension. The budget line may already exist. Procurement knows how to evaluate vendors. The downside is incumbent gravity. PagerDuty owns default mental availability. RelayOps gets compared feature-by-feature against a mature product with integrations buyers already installed.

Designing a category (for example, "on-call operations platform") lets RelayOps reframe the comparison set. Buyers might evaluate RelayOps against broken Slack workflows instead of against PagerDuty's enterprise bundle. The downside is education cost. You must teach the category before you can sell the product. Early marketing spend and sales cycles lengthen while language spreads.

RelayOps's numbers sharpen the tradeoff. At $920K ARR and 21 customers, the company cannot fund a multi-year category education campaign like a mature vendor. Yet winning a feature bake-off against PagerDuty in every deal is also expensive. Positioning strategy must match stage and capacity.

Managers should document the category choice in writing alongside the beachhead ICP. If sales, marketing, and product use different category labels, prospects receive mixed signals. One RelayOps account executive calling the product "incident management" while the website says "on-call operations" revives the PagerDuty comparison before discovery begins.

Competitive alternatives and the PagerDuty comparison trap

The most common RelayOps positioning error is defining alternatives as "PagerDuty" alone. PagerDuty is a vendor, not a full alternative picture. Buyers rarely choose between two vendors in a vacuum. They choose between staying with current workflow plus PagerDuty alerts versus adopting RelayOps orchestration layered on or replacing parts of the stack.

A complete alternative map for RelayOps's beachhead includes:

Status quo plus alerting: PagerDuty pages engineers; coordination happens in Slack threads; runbooks live in Notion; postmortems are manual. Pain is familiar, switching cost feels high.

Manual escalation: On-call phone tree in a spreadsheet. Cheap, brittle, embarrassing during customer-facing outages.

Build internal tooling: A platform team scripts paging in-house. Flexible, diverts engineering from product roadmap.

Do nothing until incident: Hero culture absorbs pain until burnout or a major outage forces change.

RelayOps wins when the cost of status quo is visible: false pages, slow acknowledgement, missing executive timeline during incidents. RelayOps loses when prospects wanted a cheaper PagerDuty license, not workflow change.

Positioning must therefore name the struggling moment (JTBD, jobs-to-be-done vocabulary from Unit 1: the recurring situation when pain spikes). For RelayOps: "Weekly Sev-1 where Slack threads exceed 200 messages before the right engineer acknowledges." Features matter after that moment is vivid.

RelayOps versus PagerDuty is not "we are better software." It is "when your team already pages through PagerDuty but still loses minutes in Slack chaos, RelayOps owns the escalation layer PagerDuty was not built to optimize." That sentence may or may not be final copy. It shows alternative clarity.

Maya and Jordan run a positioning working session before rewriting the website. They use Dunford's sequence and forbid taglines until step five is complete.

Part A: Fact pattern

Win/loss notes show a pattern: losses said "PagerDuty is good enough." Wins said "PagerDuty pages us but coordination is a mess."

Part B: Dunford sequence applied

Step 1: Competitive alternatives (status quo first)

Step 2: Unique attributes

• Slack-native escalation with role-based rules tuned for 10-25 engineer on-call rotations
• Datadog alert ingestion with deduplication rules for noisy monitors
• Executive incident timeline view without admin training burden

Step 3: Value (with proof targets)

Step 4: Target market characteristics

Series B U.S. SaaS; VP Engineering or Head of Platform owns uptime; Datadog + Slack; 4+ Sev-1/month; on-call rotation covers 15+ engineers.

Step 5: Market category (working choice)

On-call operations platform for mid-size SaaS engineering teams. SEO pages may still mention incident management as search synonym with disciplined footnotes.

Part C: Messaging hierarchy check

Check: 9 losses mapped to alternatives ✓; hierarchy terms trace to same alternative (PagerDuty + Slack chaos) ✓; beachhead ICP unchanged from Unit 1 ✓

Part D: Managerial read

Jordan wants to attack PagerDuty in product marketing. Maya pushes status-quo framing to avoid rip-and-replace objections. The canvas gives a board-answerable decision: compete on workflow pain after the page, not on becoming a full PagerDuty replacement in year one. Product roadmap implications: deepen Slack orchestration before building net-new monitoring. Sales training implication: discovery must document Slack coordination minutes, not only alert volume.

RelayOps receives two inbound demos the same week. Positioning is tested by whether the value proposition differs by persona while staying anchored to the same alternatives.

Part A: Personas

Part B: Proposition mapping

Shared category, shared alternative frame, different proof emphasis. Check: both propositions reference Slack coordination pain, not generic "modern incident management" ✓

Part C: Managerial read

If RelayOps used one generic value proposition for both personas, Sam would hear burnout language (less credible to platform leads) and Alex would hear integration detail (too narrow). Messaging hierarchy discipline at the value proposition layer improves conversion without splintering category choice.

RelayOps reviews a lost deal against BrightLoop, a Series B SaaS competitor using PagerDuty. Discovery notes: 22 engineers on-call, 6 Sev-1 events last month, 180-minute average Slack thread length during incidents, PagerDuty contract renews in 8 months. Champion loved the demo. VP Engineering declined pilot, citing "no budget for another incident tool."

Tasks:

1. Write RelayOps's competitive alternative statement for this account (not only "PagerDuty").
2. Draft a value proposition for the VP Engineering persona using the messaging hierarchy (company narrative not required; include category, value, proof type).
3. Recommend whether RelayOps should compete in "incident management" or push "on-call operations platform" for this deal. Explain why in one paragraph.
4. Show a check that your alternative statement explains the budget objection.

Solution

1. Competitive alternative statement

If RelayOps did not exist, BrightLoop would continue paging through PagerDuty while engineers coordinate in lengthy Slack threads, absorbing roughly three hours of senior engineering time per Sev-1 and delaying executive updates. Switching cost is perceived as adding another incident tool; real pain is workflow chaos after the page.

2. Value proposition draft

• Category: On-call operations platform for mid-size SaaS engineering teams.
• Value: Reduce Slack coordination time during Sev-1 incidents and speed acknowledgement without requiring PagerDuty replacement at contract renewal.
• Proof type: 14-day pilot measuring MTTA and Slack message volume compared to last two incidents, plus reference call with similar Series B SaaS customer still on PagerDuty alerts.

3. Category recommendation

Use on-call operations platform in sales conversations to avoid immediate feature parity with PagerDuty. Mention incident management only as search synonym if procurement requires familiar language. BrightLoop's objection is budget for "another incident tool," which is a category framing problem. Reframing to orchestration layered on existing paging addresses the objection. Competing solely in incident management invites renewal defense tied to PagerDuty's entrenched contract.

4. Check

Budget objection assumed marginal tool cost. Alternative statement names Slack coordination cost (senior engineer hours) that is already being spent inside opex (operating expense, day-to-day spending) through engineering salaries. Pilot proof reframes spend as reallocation, not net-new category budget. Check: alternative → pain in existing opex → pilot metric ties to VP Eng KPI (key performance indicator, measurable success target) ✓

Key takeaways

• Positioning is context: alternatives, attributes, value, target market, and category must be chosen before polished copy.
• Messaging hierarchy translates positioning into narrative, category, value proposition, proof, features, and field language without contradictions.
• Category design reframes competition but costs education; existing categories speed comprehension but invite incumbent comparisons.
• RelayOps should position against PagerDuty-plus-Slack status quo, not against PagerDuty alone.
• Value propositions differ by persona emphasis while sharing the same alternative and category anchor.

1. Pick a B2B product you know. Write its competitive alternatives including status quo and do-nothing, not only named vendors.
2. Explain in your own words why April Dunford starts with alternatives instead of taglines.
3. Continue to Lesson 2: How Positioning, Messaging and Category Design Works in Practice.