Positioning Divergence Log¶

Purpose¶

This document tracks where the April Dunford analysis (this folder) diverges from the project's current positioning documents in background/. The Dunford analysis represents a sharpened, pressure-tested version of the positioning. The project docs haven't been updated yet.

Use this as a checklist when updating the project-level positioning documents.

Last Updated: 2026-03-21

Document-by-Document Divergences¶

1. Positioning Phase 1 Doc¶

File: background/VoiceNut Positioning Angle Phase 1 - Meeting Prep Only.md

Element	Project Doc Says	Dunford Analysis Says	Impact
Product name	VoiceNut throughout	ClientIQ (decided 2026-03-13)	All copy needs updating
Time claim	"30 seconds" in several places	Standardised to "1 minute"	Minor — align to 1 minute
Positioning layers	3 layers: Time → Growth → Confidence	4 layers: Time → Growth → Confidence + Intelligence as underlying engine	Intelligence is missing entirely from this doc
Competitive context	"While every competitor fights over transcription"	Generic AI tools (ChatGPT, Claude wealth plugin, Copilot) are the new competitive context. Transcription is adjacent, not the comparison point.	Major — the competitive framing is outdated
Zero-effort differentiator	Not mentioned — describes what we do but not how it differs from generic AI	Core differentiator: "prep that happens automatically without prompting" vs. "AI that can help you prep if you do the work"	Major — this is now the primary distinction
Growth story	"Reclaim hours for revenue-generating activities" (generic)	"Meeting prep is step one. Personalised messaging, mobile apps, and client portal are on the roadmap." (backed by product roadmap)	Significant — growth is no longer abstract
"What We Don't Do" section	Don't lead with competitive comparisons, don't position against transcription	Still valid, but should add: "Don't position as 'another AI tool'" and should acknowledge generic AI as a competitive context without leading with comparisons	Moderate

2. Market-Specific Positioning Guide¶

File: background/market-specific-positioning.md

Element	Project Doc Says	Dunford Analysis Says	Impact
Competitive alternatives by market	Not addressed — assumes same alternatives everywhere	USA: generic AI is fastest-growing alternative. SA: admin staff dominant, generic AI slower. UK: compliance checklists + manual.	Moderate — market-specific objection handling needed
Product framing table	USA: "Meeting prep tool → practice growth enabler"	USA: Must explicitly differentiate from generic AI. "Purpose-built" is the key word.	Moderate
Generic AI as alternative	Not mentioned anywhere	Full analysis of generic AI as Alternative #5, with the "Excel as CRM" analogy	Major gap — this is the fastest-growing alternative
Growth framing	"Reclaim hours" / "scale without sacrifice"	"We're building a growth engine — prep is step one, personalised messaging and client portal are coming"	Significant
Layer 4 (Intelligence)	Listed as a layer with sub-bullets	Reframed: not a standalone layer but the underlying engine that powers everything. Surfaces differently by market.	Conceptual shift — same content, different framing
Objection handling	Implicit in the SA section (cheap labour)	Explicit per-market objection handling recommended, including "I already use ChatGPT for that"	New addition needed

3. CLAUDE.md — Positioning Strategy Section¶

Element	Project Doc Says	Dunford Analysis Says	Impact
Four-Layer Angle	Time → Growth → Confidence → Intelligence	Time → Growth → Confidence (Intelligence is the engine, not a layer)	Conceptual — same content, different hierarchy
Key Differentiator	"While every competitor fights over who records meetings best"	The differentiator is now zero-effort vs. generic AI, not us vs. transcription	Outdated framing
Subcategory	Not explicitly stated	Confirmed: "AI Meeting Prep for Financial Advisors" with evolution path to "Client Intelligence Platform"	Should be made explicit
Product roadmap context	Not mentioned in positioning sections	Future modules (personalised messaging, mobile apps, web portal) inform the growth story and validate the platform trajectory	Missing context

Key Strategic Shifts (Summary)¶

1. Competitive landscape has changed¶

Before: "We solve prep, competitors solve transcription — different problem"
After: "Generic AI can do basic prep now. Our moat is zero-effort integration, domain depth, and a platform roadmap."

2. Growth story is now backed by product roadmap¶

Before: "Save time → have more hours → grow" (abstract)
After: "Meeting prep removes the bottleneck. Then: personalised messaging, mobile apps, client portal." (concrete)

3. Intelligence is reframed from layer to engine¶

Before: Layer 4, a supporting proof point
After: The underlying capability that powers everything — prep quality, future modules, and the technical moat against generic AI. Not a customer-facing messaging pillar (customers buy outcomes, not capabilities).

4. Zero-effort is the new core differentiator¶

Before: "We use AI for meeting prep" was differentiating
After: "AI meeting prep" is table stakes. "Prep that happens without you doing anything" is the differentiator. The Excel-as-CRM analogy.

5. Subcategory is confirmed and explicit¶

Before: Implicit category (somewhere between advisor-tech and new category)
After: Explicit subcategory: "AI Meeting Prep for Financial Advisors" (Phase 1) → "AI Meeting Intelligence" (Phase 2) → "Client Intelligence Platform" (Phase 3)

Recommended Update Sequence¶

When ready to update the project-level docs:

First: Update background/VoiceNut Positioning Angle Phase 1 - Meeting Prep Only.md — this is the source doc everything else references. Rename to reflect ClientIQ. Add zero-effort differentiator, generic AI competitive context, expanded growth story, and Intelligence-as-engine framing.
Second: Update background/market-specific-positioning.md — add generic AI as competitive alternative, add per-market objection handling, update product framing table.
Third: Update CLAUDE.md positioning sections — align Key Differentiator, layer descriptions, and add subcategory framing.
Fourth: Review landing page copy and outreach templates against the updated positioning — these are the customer-facing assets that need to reflect the new framing.