The Voicify "Competitor A or Competitor B" framing assumes one buyer. Dental AI receptionist deals never have one buyer. A sub-ten-location practice has at minimum the owner-dentist, the office manager, and the billing lead in the room; a DSO adds an operations director, an internal IT lead, and a regional manager. The slot framing — A-slot displacement or B-slot defense — lands differently on each of those personas, and a rep who runs the same battlecard language across all of them loses at least one stakeholder per deal. The stakeholder map is the instrument that fixes the leak. It pairs every persona in a dental buying committee with the right framing, the right artifact, the right objection lane, and the right champion sub-asset so the A-or-B conversation arrives in each person's language without the rep having to improvise.
TL;DR
Six personas. One framing per slot per persona. One artifact per persona per slot. The stakeholder map for the Voicify A-or-B battlecard names the canonical dental buying-committee personas — owner-dentist, office manager, billing lead, IT lead, hygienist or front-desk lead, DSO operations director — and pairs each with the slot-specific framing they hear in their own language, the battlecard artifact that serves them, the objection lane they push hardest on, and the champion enablement sub-asset to leave them with. Reps tag personas during discovery, walk the map before any multi-stakeholder meeting, and update persona-level commitment signals (green, yellow, red) post-call. The pattern of greens and reds across the map predicts deal velocity better than CRM stage. The map routes the whole A-or-B system.
Why the A-or-B Framing Needs a Persona Layer
The A-or-B battlecard tells the rep which conversation to have — the displacement conversation against an installed competitor, or the defense conversation when the rep is the incumbent. What the card does not do — by design, because it would balloon into an unreadable document — is tell the rep how to translate that conversation across the five to six humans who will weigh in on the buying decision. That translation is where the deal is won or lost. An owner-dentist hears "A or B" as a strategic vendor decision; an office manager hears it as a change to her morning huddle; a billing lead hears it as a claims-routing question; an IT person hears it as an integration question. Same words, four buyers, four meanings.
The stakeholder map sits between the battlecard and the buying committee. It does not replace the card — it routes the card. The discovery brief is where the rep records which personas appear in the deal; the map is where the rep records what to do with each. Most lost deals are lost on a persona the rep never met, not on a persona the rep handled badly. The map's first job is making the missing personas visible.
The Six Canonical Personas
Across roughly 95 percent of dental AI receptionist deals, the buying committee resolves to some subset of six personas. Solo practices collapse three of them into one person; DSOs split them out fully and add the sixth. The list:
- Owner-dentist or managing partner. Strategic vendor decision-maker. Cares about category positioning, peer-reference signals, and whether the AI receptionist makes the practice look modern to patients.
- Office manager or practice administrator. Operational owner. Cares about staff workflow disruption, training time, and whether the morning huddle gets harder or easier on day one.
- Billing or insurance lead. Claims-flow owner. Cares about whether the AI handles insurance questions correctly, how denied claims get routed, and whether the integration breaks her current claims process.
- IT lead. External managed service provider for sub-ten-location practices; internal team for DSOs. Cares about integration, security, and who gets the support call at 2am when the AI fails.
- Hygienist or front-desk team lead. User-facing influence. Cares about whether the AI makes the patient-facing side of the practice better or worse, and whether her team gets blamed when the AI fumbles.
- DSO operations director or regional manager. Only present for multi-location buyers. Cares about per-location rollout sequencing, KPI rollup, and whether the AI standardizes across the portfolio or fragments it.
The map's job is naming which of these six are present in any given deal — not all six are always in play — and then routing the right framing to each.
The Map Itself
Each row of the map is one persona. Each persona has four columns: the A-slot framing they hear, the B-slot framing they hear, the leading artifact for that persona, and the objection lane they push hardest. The map is deliberately stable — the columns do not change quarter to quarter — so reps can internalize it across deals.
| Persona | A-slot framing | B-slot framing | Leading artifact | Objection lane |
|---|---|---|---|---|
| Owner-dentist | Category leader vs. category-pure dental AI; peer-reference forward | Continuity of category position; switching risk forward | Executive briefing one-pager | Category and reference |
| Office manager | Staff workflow improvement on week one; training reduction | Workflow stability; what changes if you switch and why it is risky | Demo script walk-through | Workflow disruption |
| Billing lead | Claims routing accuracy; denied-claim handling improvement | Claims integration stability; current routing preserved | Discovery brief addendum with billing scenarios | Claims-flow risk |
| IT lead | Cleaner integration than the incumbent; SOC 2 and HIPAA evidence | Already-deployed integration; switching is the new IT project | IT & integration due-diligence battlecard | Integration and security |
| Hygienist / front-desk lead | Patient-facing experience improvement; less front-desk overflow | Team familiarity preserved; retraining cost of switching | Patient-experience demo segment | Patient and team experience |
| DSO operations director | Per-location rollout sequencing; portfolio-level KPI rollup | Standardization preservation; rollback cost across portfolio | Pilot scorecard with multi-site lens | Rollout risk at portfolio scale |
How A-Slot and B-Slot Change the Map's Posture
The persona list does not change between A-slot and B-slot deals. The framing, the language, and the leading artifact do. In an A-slot displacement conversation the map is offensive — every persona gets the displacement framing customized to their concerns, and the leading artifacts are evidence-forward: the discovery brief, the demo script, the pilot scorecard. In a B-slot defense conversation the map is defensive — every persona gets the defense framing customized to their concerns, and the leading artifacts are stability-forward: the CSM B-slot defense kit, the migration battlecard read as a counter-position, the executive briefing one-pager reframed as a continuity case.
The slot decision is made by the rep before the meeting using the slot decision tree. The map is what the rep does with the slot decision once it is made. Without the map, the slot framing collapses back into generic A-or-B language the moment the rep walks into a room with three different personas in it.
How Reps Use the Map Mid-Deal
Three steps, repeated across the life of the deal.
Step one — persona tagging during discovery. During the first two discovery calls the rep tags which of the six personas have appeared in the conversation, which have been named by the buyer but not yet met, and which are completely missing. The missing column is the most important. A deal where the office manager and billing lead have both been named but not engaged is a deal where two of the four likely vetoes are unaddressed.
Step two — pre-meeting map walk. Before any multi-stakeholder meeting the rep pulls the map and walks through which framing each attending persona should hear and which artifact to leave them with afterward. This step is what the AE pre-call prep covers in detail. The map is the source the prep pulls from.
Step three — post-call commitment signals. The rep updates the map post-call with persona-level commitment signals. Green for explicit support, yellow for neutral, red for active resistance. The pattern across the map — not the count — predicts deal velocity. Five greens and one red on the IT lead is a deal that needs an IT-focused next step. Three yellows in a row is a deal where nobody yet has a reason to advocate, and the next move is finding the green, not converting the red.
How the Map Feeds the Rest of the System
The stakeholder map is the routing layer for the whole A-or-B artifact set. Three connections matter.
First, persona-level commitment signals feed the discovery brief — a yellow on the billing manager raises a flag the next AE pre-call prep needs to address before next call. Second, persona-level objection patterns feed the objection backlog at the quarterly refresh — if the IT lead consistently raises an objection that is not yet in the six-category objection map, that objection gets promoted. Third, the champion enablement kit pulls its sub-assets from the map: each persona has a one-page brief the champion can forward to a peer, and the rep selects which to send based on which personas the champion needs to convert internally.
Two further connections close the loop. The win-loss debrief at deal close reviews the map's final state — which personas were green, which were red, which were never met — and surfaces structural gaps for the field intel capture. The coaching scorecard grades whether the rep updated the map after every multi-stakeholder meeting; persistent failure on that criterion is a coaching signal, not a tool problem.
What the Map Does Not Do
The map is not a substitute for the discovery brief. It does not record the deal's facts — close date, pricing, location count, integration scope. Those live in the brief. The map only records persona-level state. Mixing them creates a bloated document nobody updates.
The map is not a champion-development tool. It identifies which personas need to be converted; it does not coach the champion on how to do that conversion internally. That work lives in the champion enablement kit. The map's job is naming the personas and routing the artifacts; the champion's job is the actual internal selling. Asking the map to do both turns it into a champion-development plan that is too generic to use.
The map is not a forecasting instrument. A green across all six personas does not mean the deal closes — it means every persona is aligned on the framing. The forecast call scorecard still has to grade the deal across slot-tag hygiene, activation cue compliance, override discipline, and signal-to-outcome correlation. The map is one input to the forecast, not the forecast itself.