06-reference/research

dunford positioning b2b services application failures

2026-09-01·research-brief·source: deep-research·by Ray Data Co (deep-research synthesis)
positioningdunfordservices-firmsproductizationlanding-page

Services Firms Barely Have a Documented Dunford Track Record - and Where They Do, Positioning Stops at the Copy Layer

The question

Verbatim: "How have B2B service firms (consultancies, agencies, dev shops) actually applied April Dunford's Obviously Awesome positioning framework, and what's the common failure pattern?"

Context: feeds the raydata.co landing-page rewrite and the Client Reporting service one-pager. The theory is already in the vault; what was missing is services-specific application evidence and the breakage point.

What we already know (from the vault)

What the web says

Convergences and contradictions

Synthesis for RDCO

The honest headline is that there is no services-firm Dunford case-study literature to borrow from. Her documented clients are software companies, her stated ICP is B2B tech with a sales force, and the two public "we ran the 10 steps" write-ups are both SaaS. Any services firm using this framework is extrapolating. That is not a reason to drop it; it is a reason to stop expecting the framework to do the whole job and to know exactly which step will break.

The break is step 2, unique attributes. A product's attributes are fixed and checkable; a dev shop's are elastic, so the firm truthfully answers "we can build you anything" and the chain from attributes to value to best-fit customer never gets traction. The observable consequence is the Digital Applied pattern: the firm completes the exercise at the copy layer, ships packaged-sounding language, and leaves the commerce unpackaged - no price, no duration, no deliverable list, free-consult CTA. Positioning that a buyer cannot act on without a sales call has not actually been applied. Note that the vault caught this on a competitor before it caught it on RDCO, and raydata.co is currently in the weaker state: no rewrite at all, and a Client Reporting price ($2-5k/mo) that is decided internally but published nowhere.

There is a second break the framework does not have a step for. A product company that repositions changes its pitch; a services firm that repositions has to start declining revenue, and the pipeline goes thin before the new position generates inbound. Dunford's process has no "what work do you now refuse" step, and this is exactly where a solo operator with lumpy pipeline is most exposed. (Inference, not a sourced finding - the services-positioning literature that treats this directly, notably Philip Morgan's work on indie-consultant positioning, was unreachable this session after two failed fetches.)

So the operational move for the rewrite is to run Dunford on the offer, not on the firm. RDCO already has every input for a Client Reporting positioning pass: alternatives (in-house analyst time, Big-4 and specialist consultancies at $150k-$500k, Utsubo-style studios, DIY BI tooling), the qualifier that incumbents cannot match (data teams, one senior operator, artifact handed back), the buyer (mid-market data leader), and the price. Running it on "Ray Data Co" as an entity will reproduce the capability-list failure, because at the firm level the honest answer really is "we can build you anything." Two concrete acceptance tests for the rewritten page and the one-pager, both drawn from the failure pattern rather than from theory: (1) the page publishes a number and a bounded deliverable list, so the buyer can act without a call; (2) the page states what RDCO does not take. If a competitor could paste their logo onto the page and have it still read true, the exercise ran at the copy layer only.

Why this is in the vault

It supplies the failure test for two live artifacts: the raydata.co landing-page rewrite that [[2026-04-19-commoncog-obviously-awesome]] queued in April and has not run, and the Client Reporting one-pager whose $2-5k/mo price is decided in [[2026-06-13-managed-ai-data-services-pricing-models]] but unpublished. It also settles a scoping question for both: run the positioning pass on the productized offer, not on the firm.

Open follow-ups

Related

Sources

Vault:

Web: