From Feature List to Category Dominance: Rebuilding B2B Positioning with Dunford's 5-Step Framework

Marketing Academy · Field Work●Marketing Fundamentals

CoreRebuild· 45 minutes

Freshworks

Objective: Apply April Dunford's five-component positioning framework (competitive alternatives, unique attributes, customer value, target segment, and market category) to reposition a crowded B2B software product, formulating an airtight 'Only' statement and a defensibility audit.

You are the product marketing lead at Freshworks (FRSH) during the early expansion of Freshdesk. The customer service software market is fiercely competitive: Zendesk dominates mid-market tech companies, Salesforce Service Cloud dominates legacy enterprise, and hundreds of SMBs still manage support out of a shared Gmail inbox. Sales reps report prospects asking 'how are you different from Zendesk?', and your homepage is slipping into generic feature-comparison territory.

Rebuild Freshworks' core customer-support positioning from the ground up using the lesson's three-step positioning process and Dunford's 5-part framework. Map competitive alternatives (including 'doing nothing / shared inbox'), isolate the single authentic point of difference, define the ideal customer profile, choose the winning frame of reference, and validate defensibility against the 'Only' test.

Before you start

What you'll need

Free path (everything below is enough to finish)

Notion

FreemiumDraft the 5-component Dunford framework and synthesize the Only Test statement

Structured document templates with version comparison

Google Sheets(optional)

FreeConduct the competitor defensibility and moat audit

Tabular evaluation of incumbent constraints and unit economics

The process

4 steps

Step 01 of 04

Choose Your Frame of Reference

The lesson's Step 1 establishes that your market category (frame of reference) dictates who your competitors are, what price you can charge, and which features matter. Slack succeeded by framing against email rather than enterprise chat.

What frame of reference allows Freshdesk to avoid a direct head-on slugfest with heavyweight enterprise suites while standing miles above shared email inboxes?

Notion— Positioning workspace table -> Section 1: Frame of Reference & Competitive Alternatives

Procedure

List the primary competitive alternatives prospects use when they do not buy your product: (1) Shared Gmail/Outlook inbox, (2) Heavy enterprise suites like Salesforce/ServiceNow, (3) Complex mid-market helpdesks like Zendesk.
Identify what baggage and pricing expectations each frame carries for a 20-person support team.
Define the category frame that highlights fast time-to-value and low administrative overhead rather than endless enterprise customization.

Sample output

Frame Analysis:
- Alternative A: Shared Gmail/Outlook (Free, zero setup, but chaotic, collisions, no ticket routing)
- Alternative B: Salesforce Service Cloud (Enterprise, $150+/agent/mo, requires full-time admin and 6-month rollout)
- Target Frame: 'Modern, setup-in-minutes customer support software for fast-growing teams who refuse enterprise bloat'

Healthy

Category frame immediately positions the product against both chaotic inboxes and bloated enterprise tools.

Unhealthy

Selecting 'Enterprise Customer Relationship Management Platform', forcing direct RFP comparisons with Salesforce on enterprise feature checkboxes.

What this means

Your category frame must make your strengths obvious and your competitors' strengths irrelevant for your chosen segment.

So what do I do about it?

Symptom	Action	Effort
Prospects compare your product to $50k enterprise platforms	Refocus the category frame on 'frictionless setup and lightweight agility'	30 min

YouYou can do this yourself, no engineering access required.

Step 02 of 04

Find Your Point of Difference

Step 2 requires identifying the single point of difference that delivers distinct customer value. April Dunford's framework links unique attributes directly to business outcomes for the customer, not a feature list.

Which unique capability translates into the single highest-value business outcome for high-velocity support teams?

Notion— Positioning workspace table -> Section 2: Attribute-to-Value Mapping

Procedure

List 3 candidate features (e.g., intuitive multi-channel ticketing UI, built-in phone channel, transparent per-agent pricing with zero setup fee).
Convert each feature input into a tangible customer outcome (e.g., agents onboard in 15 minutes without certification; team saves 60% on total cost of ownership).
Select the single primary point of difference that competitors cannot claim without undermining their own enterprise business model.

Sample output

Feature: Zero-configuration omnichannel inbox with transparent self-serve pricing.
Outcome: Support teams launch full ticketing, chat, and phone in under one day with zero IT assistance, cutting response time by 45%.
Point of Difference: 'The only omnichannel helpdesk that delivers instant agent productivity without implementation consultants or multi-month contracts.'

Healthy

Point of difference names one clear, demonstrable customer outcome tied directly to product design.

Unhealthy

Listing 10 generic features ('AI, reporting, macros, integrations') as the differentiator.

What this means

If your point of difference requires a bulleted list, you have not isolated your core strategic advantage.

So what do I do about it?

Symptom	Action	Effort
Sales deck lists 15 bullet points on the 'Why Choose Us' slide	Consolidate to the one core outcome that addresses the customer's primary frustration	30 min

YouYou can do this yourself, no engineering access required.

Step 03 of 04

Make It Defensible

Step 3 tests whether the position is anchored in structural advantages—such as business model, distribution, or architecture—that competitors cannot copy in a single quarter.

Why can legacy enterprise incumbents not easily clone this positioning without cannibalizing their core revenue?

Google Sheets— Competitive Moat Matrix -> Defensibility Audit Tab

Procedure

Evaluate the incumbent's revenue model: enterprise vendors rely heavily on professional services fees, multi-year lock-in, and tiered enterprise addons.
Assess the competitor's innovator dilemma: if an enterprise competitor attempts to simplify setup and slash prices, they cannibalize their lucrative implementation partner ecosystem.
Document how Freshworks' self-serve, cloud-native architecture creates a durable structural cost advantage.

Sample output

Defensibility Moat Audit:
- Competitor Constraint: Legacy enterprise vendors earn 20-30% of revenue from professional implementation services.
- Incumbent Dilemma: Sponsoring a 'self-serve 10-minute setup' narrative alienates their partner network.
- Structural Edge: Freshworks' bottom-up trial model and intuitive UI creates viral land-and-expand adoption at a fraction of legacy customer acquisition cost.

Healthy

Position is protected by the incumbent's economic model and organizational inertia.

Unhealthy

Assuming UI cleanliness alone is a permanent moat without business model defensibility.

What this means

The strongest positions leverage the competitor's own business model against them.

So what do I do about it?

Symptom	Action	Effort
Competitor launches a promotional campaign copying your headline	Double down on self-serve product trials where their sales-heavy model cannot follow	half day

YouYou can do this yourself, no engineering access required.

Step 04 of 04

The Only Test

The 'Only' Test forces rigorous positioning discipline: '[Brand] is the only [category] that [point of difference] for [target customer].'

How do you synthesize the frame, differentiator, and target customer into an airtight, defensible positioning statement?

Notion— Positioning Synthesis -> Final One-Sentence Position Statement

Procedure

Fill in all four components: Brand, Category Frame, Point of Difference, and Target Customer.
Run the substitution test: replace 'Freshdesk' with 'Zendesk' or 'Salesforce'—the statement must become false or absurd.
Run the exclusion test: ensure the statement clearly repels massive Fortune 500 legacy RFP procurement buyers who demand 12-month on-prem custom consulting.

Sample output

Positioning Statement:
'Freshdesk is the only customer support platform that provides complete multi-channel ticketing with zero-day setup and transparent pricing for fast-growing companies that need immediate agent productivity without enterprise complexity or consulting overhead.'

Substitution Check: Fails if Zendesk or Salesforce is inserted (neither offers zero-day setup with zero enterprise overhead).
Exclusion Check: Clearly excludes companies seeking customized multi-million dollar on-prem legacy deployments.

Healthy

Statement passes the substitution test and gives sales, marketing, and product a single unifying anchor.

Unhealthy

Writing a fluffy slogan ('The smart way to delight customers') that fails all four 'Only' test blanks.

What this means

An effective positioning statement is an internal strategic compass, not a public tagline.

So what do I do about it?

Symptom	Action	Effort
Marketing copy drifts into generic claims across different landing pages	Benchmark every headline against the core 'Only' statement before publishing	5 min

YouYou can do this yourself, no engineering access required.

Final deliverable

A complete 5-component B2B positioning dossier containing competitive alternative mapping, point of difference breakdown, incumbent defensibility matrix, and a validated 'Only' positioning statement.

See a reference example

Sample output

B2B Product Positioning Dossier (Worked Example: Postman API Platform)

1. Market Category (Frame of Reference):
   API Collaboration Platform (repositioned away from 'simple HTTP testing utility')

2. Competitive Alternatives:
   - cURL scripts and command-line tools (free, but siloed, non-shareable, high friction for non-devs)
   - Heavy API management gateways like Apigee/MuleSoft (enterprise-governed, rigid, disconnected from daily developer workflows)

3. Point of Difference & Customer Value:
   - Unique Attribute: Shared team workspaces with automated mocking, documentation, and live test collections.
   - Core Customer Value: Eliminates cross-team API integration friction, reducing API development lifecycle from weeks to hours.

4. Target Customer:
   Engineering teams and product developers building modular, microservices-driven web and cloud applications.

5. Defensibility Moat:
   Network effects of public/private API workspaces and developer bottom-up adoption; enterprise API gateways cannot replicate grassroots developer workflow affinity.

6. Synthesized 'Only' Statement:
   "Postman is the only collaborative API platform that unites the entire API development lifecycle in shared workspaces for software teams who need to design, test, and ship reliable APIs at high velocity."

Success criteria

You're done when you can:

Identifies real competitive alternatives beyond direct software rivals (including 'doing nothing')
Extracts a single, value-driven point of difference rather than a feature checklist
Evaluates structural competitor constraints to prove positioning defensibility
Passes the 'Only' test with a non-interchangeable position statement
Passes the substitution and exclusion checks