DHM hard-to-copy test
BiddleA differentiator a rival can copy next quarter is a feature, not positioning. Frame the underlying need as a JTBD job-story.
Positioning · Launch · Enterprise sales
Default positioning happens to you; deliberate positioning is built. Start from what the customer uses if you don't exist — including doing nothing — and work forward to the category that makes your value obvious.
Competitive alternatives
What the customer uses if you don't exist. Include "do nothing" — usually your #1 competitor.
Unique attributes
Capabilities only you have vs. those alternatives.
Value
What those attributes let the customer do — reach it with the "so what?" test.
Target market
The segment that cares most — best-fit, not all-addressable.
Market category
The frame of reference that makes the value obvious.
Dunford, Obviously Awesome · derive the 5 components in order
Above the fold
Derive positioning in order.
Competitive alternatives (incl. "do nothing") → unique attributes → value → target market → market category. Each component feeds the next; you can't skip to the category.
The enemy is indecision, not a rival.
40–60% of B2B deals end in no-decision (JOLT — Dixon & McKenna, not Dunford). Judge the indecision, recommend, limit options, take risk off the table.
Launch is risk reduction, not a date.
Prove it's valuable, adoptable and viable before committing. Any one unproven → the launch is theater, however coordinated the press hit.
Positioning · Dunford (Obviously Awesome)
Reach Value with the "so what?" test: ask "so what?" of each attribute until you land on a value worth paying for. Then check the differentiator holds and the statement survives a real customer.
A differentiator a rival can copy next quarter is a feature, not positioning. Frame the underlying need as a JTBD job-story.
When buyer ≠ user you may need two positioning statements — one for the end-user (adoption), one for the economic buyer (purchase).
Formal positioning can be premature pre-PMF — treat the statement as a living hypothesis to test in sales calls, not a fixed artifact.
Validation battery · three falsification tests
Test
Does a real customer describe the value the way you wrote it?
Pass
Their words echo yours — the value lands unaided.
Test
Swap your name for a competitor's — does the statement still read true?
Pass
If it still reads true, it isn't differentiated — rewrite until only you can claim it.
Test
Will it survive the next 2–3 competitor moves?
Pass
The claim holds even after rivals react — not a position you'll lose next release.
Attribution warning · JOLT ≠ Dunford
"40–60% of B2B deals end in no-decision" is the JOLT Effect — Dixon & McKenna, not Dunford. The enemy is customer indecision / FOMU (fear of messing up), not a rival: judge the indecision, offer a recommendation, limit the options, take risk off the table. Position against the status quo, not only competitors.
Pick the category · 3 market-frame strategies
Lowest ambiguity
Dominate a sub-segment
Highest cost
Sell what's on the truck
Position the product you ship today, not the roadmap. AI capability is increasingly table stakes; in positioning, ignore future/competitor moves and frame on shipped value — address them on the roadmap, not in the pitch.
Launch · Perri
Is it valuable (solves a real problem), adoptable (users find it and succeed with it), viable (you can support and sustain it)? Any one unproven → the launch is theater.
Release behind a flag to a small cohort, watch real failure modes, then widen. No big-bang.
Ship related changes as one coherent story, not a dribble of half-features — the launch should land as a narrative, not noise.
Cadence · directional
Pre
~8–12 wk
Beta, enablement, pricing + positioning locked, success metrics defined.
Launch
The moment
Coordinated product / mktg / sales / support; internal + external comms.
Post
~4–8 wk
Adoption metrics, iterate, retro.
Optics-velocity trap
Ship-count and launch velocity are vanity. A launch nobody adopts moved no outcome; measure adoption and retained value, not the press hit.
Enterprise / sales integration · B2B
Moore positioning statement · the one-line output of the Dunford work
When sales promises a feature to close a deal, gate on (1) strategy fit, (2) how many other customers need it, (3) true cost incl. maintenance — separate "customer-funded" builds from the roadmap.
Enterprise-readiness / security posture isn't just for the deal on the table — it's an Opportunity-Enablement lever that unblocks a whole future cohort. Weight it as future revenue unlocked, not one-off cost.
When the CRO escalates, make opportunity cost visible: "Here's what we'd deprioritize to do this; want that trade?" Score one-off-vs-generalizable × deal value vs. maintenance/opp-cost × reversibility → build / yes-with-conditions / no-with-alternative.
Ownership split + monthly sync
PM owns positioning (what it IS, for whom), Marketing owns messaging (how to say it), Sales owns the narrative (how to tell it in context) — keep all three aligned. Run a monthly PM↔Sales sync: Sales brings top-5 loss reasons + top-5 customer requests; PM shares upcoming releases + positioning guidance. This prevents drift.
Try it
The Dunford positioning builder, live: fill the five components in order, then run the substitutability test — swap a rival's name in and see if it still reads true.
The positioning builder needs JavaScript to run. Run it on the Tools page.