The Voicify A-or-B primary battlecard was built around a single-practice buying motion. One owner-dentist or one office manager makes the call, deployment is one location, ROI is one phone line, the competitive question is whether AI receptionist coverage is worth twelve hundred dollars a month. That motion is the bulk of the dental AI receptionist market by deal count. But the dental service organization buying motion inverts almost every assumption that primary battlecard rests on — procurement is centralized, IT is centralized, the practice-management system is consolidated across fifty to several hundred locations, ROI is per-location-times-scale-times-rollout-cadence, and the stakeholder list expands from two to seven roles. Running the single-practice battlecard against a DSO buyer signals to the buyer that the rep has not done their homework. The DSO battlecard layer is the supplement that handles the seven dimensions where DSO framing diverges, plugged into the primary library through the governance SOP so reps maintain one set of facts and pull the DSO overlay only when the deal calls for it.
TL;DR
Seven dimensions. One supplement layer. Plugged into the primary, not parallel to it. The Voicify A-or-B DSO buyer battlecard supplements the primary library on the seven dimensions where DSO framing diverges from single-practice — seven-role stakeholder map, per-location ROI with central-overhead and rollout-cadence corrections, three rollout models (central-and-uniform, pilot-then-cascade, federated-by-region), consolidated PMS integration risk, multi-year contract structure with location-tier pricing and expansion clauses, change-management at scale across hundreds of practice managers, and rip-and-replace incumbency dynamics. The layer ships as five one-page supplements attached to the existing stakeholder map, pricing-procurement battlecard, IT integration due-diligence, slot decision tree, and migration battlecard. Tier assignment and refresh cadence follow the governance SOP. One library, one refresh cycle, DSO overlay on demand.
Why the Primary Battlecard Falls Short for DSO Deals
The primary Voicify A-or-B battlecard is engineered around the single-practice buyer. The objections it anticipates — call-coverage gaps, after-hours patient handling, front-desk staffing — are office-level questions. The pricing comparison it carries is monthly-per-location with a single-decision-maker buying motion. The integration story it tells is one PMS instance at one location. None of that translates cleanly to a DSO with seventy-five locations, three regions, a centralized IT function, a CFO who wants per-location unit economics, and a VP of operations who wants to know whether the chosen vendor can roll out at ten locations a month without burning the field training budget.
The failure mode for reps who try to stretch the single-practice battlecard onto a DSO conversation is consistent. Discovery questions feel undersized to the DSO stakeholders. ROI math gets rejected by the CFO inside the first call because the rep multiplied single-practice savings by location count without correcting for rollout cadence or central-overhead. Integration discussion gets shut down by IT because the rep is talking PMS-instance-level when the DSO runs a consolidated PMS at the corporate level. The competitive framing the rep brings sounds like a small-practice framing translated mechanically — and the buyer registers that. The DSO buyer battlecard layer is what prevents that translation failure.
The Seven Dimensions of Divergence
DSO framing diverges from single-practice framing along seven specific dimensions. The battlecard layer addresses each one explicitly, with a one-page supplement keyed back to the primary artifact it extends.
| Dimension | Single-practice framing | DSO framing | Layer supplement |
|---|---|---|---|
| Stakeholders | Owner-dentist or office manager | Seven roles across corporate and regional | DSO stakeholder map supplement |
| ROI math | One phone line, one month | Per-location savings × scale × rollout cadence × central-overhead | Multi-location ROI supplement |
| Rollout model | Single deployment | Central-and-uniform vs. pilot-then-cascade vs. federated-by-region | Three-model rollout supplement |
| PMS integration | One PMS instance at one location | Consolidated PMS instance shared across all locations | Multi-location integration supplement |
| Contract structure | Monthly, one location | Multi-year, location-tier pricing, expansion clauses, renegotiation rights | DSO contract supplement |
| Change management | One practice manager training | Training rolled out across hundreds of practice managers in waves | Wave-rollout training supplement |
| Incumbency | Greenfield, no incumbent | Existing vendor at scale, rip-and-replace | Rip-and-replace migration supplement |
Dimension One — The Seven-Role Stakeholder Map
The single-practice stakeholder map has two roles. The DSO map has seven. VP of operations owns the operating-system fit. CFO owns the per-location unit economics and the multi-year contract. Head of IT owns the consolidated PMS integration risk. Head of revenue cycle owns the downstream impact on collections and accounts receivable. Regional ops directors own the rollout risk in their patch and may hold veto under a federated model. Practice managers in pilot locations carry the day-one-after-deployment experience that determines whether cascade approval lands. Corporate clinical leadership enters if any scope-of-practice question surfaces — what the AI is and is not allowed to triage, document, or recommend.
The supplement names each role, maps Voicify's evidence to that role's primary concern, and prescribes a discovery question per role the rep should land before the deal advances. Skipping a role costs the deal because DSO procurement processes route through every named role at some stage — usually late, when re-framing is expensive.
Dimension Two — Per-Location ROI With the Two Corrections
The math reps reach for first is single-practice savings multiplied by location count. The CFO will reject it in the first ten minutes of the call. Three corrections apply, and the supplement carries each one with a worked example.
- Per-location savings curve is non-linear. Strong locations — high call volume, modern PMS integration, weak after-hours coverage — realize meaningfully more per-location savings than the average. Weak locations realize less. A single-average number understates the strong and overstates the weak.
- Central-overhead savings layer on top. One centralized after-hours coverage model replacing fifty location-level coverage models is a category of savings the per-location summary misses. The supplement carries a one-line central-overhead estimate the rep can ground in the DSO's current model.
- Rollout-cadence sensitivity dominates first-year ROI. Ten locations a month versus three locations a month is the difference between a fraction of steady-state and most of steady-state in year one. The supplement carries a three-variable model — per-location savings range, central-overhead, rollout cadence — that the rep can walk a CFO through in real time.
The supplement explicitly tells the rep not to bring a single-figure ROI number into the CFO conversation. The point is to walk the CFO through the model and let the CFO choose the inputs they trust. Single-figure ROI claims at DSO scale get treated as marketing, not analysis.
Dimension Three — The Three Rollout Models
DSO rollouts run on one of three models. Identifying which one the DSO is operating under is the first thing the rep does after the discovery call, because each model favors a different vendor profile and the framing the rep leads with should track.
Central-and-uniform. Corporate selects one vendor; every location runs it. This model favors the vendor with the strongest enterprise contract terms, deepest consolidated-PMS integration, and most mature multi-location reporting dashboard. Voicify framing in this model leads with the contract structure supplement and the integration supplement.
Pilot-then-cascade. A pilot of three to ten locations runs first, results are evaluated against pre-agreed criteria, then the rollout cascades. This model favors the vendor with the most credible pilot-design support and the cleanest pilot exit criteria. The framing the rep leads with connects directly to the primary library's pilot scorecard — the supplement annotates the scorecard with DSO-specific cascade criteria so the pilot does not end with everyone celebrating and no one knowing what triggers the cascade.
Federated-by-region. Regional ops directors retain veto and the vendor must clear each region. This model favors the vendor with the strongest regional-customization story and the most usable change-management materials at the practice-manager level. The framing leads with the wave-rollout training supplement and the regional-customization narrative.
The supplement is a one-page decision tree — three rollout models, three vendor profiles, three lead-with framings. The rep identifies the model from discovery and reads the right column.
Dimension Four — Consolidated PMS Integration Risk
Single-practice integration risk is low because the blast radius is one location. Consolidated-PMS integration risk is high because a bad integration affects every location simultaneously. The supplement extends the IT integration due-diligence battlecard with three DSO-specific questions: how Voicify and each A-or-B competitor handle a single consolidated PMS instance, what the rollback path looks like for a multi-location deployment that needs to revert, and how patient-data segmentation works when one PMS instance carries data for seventy-five locations under different state regulatory regimes.
The supplement is the artifact head-of-IT reads before greenlighting pilot integration. Skipping it leaves the rep depending on the single-practice version, which the head of IT correctly perceives as undersized.
Dimension Five — Contract Structure
DSO contracts carry multi-year terms, location-tier pricing, expansion clauses for new acquisitions, and renegotiation rights tied to vendor performance metrics. The supplement extends the pricing-procurement battlecard with the DSO contract architecture — what a typical multi-year structure looks like, where Voicify is strongest competitively, and which clauses each A-or-B competitor reliably pushes back on. The CFO reads the contract architecture before signature, and the rep needs to anticipate where each line item lands.
Dimension Six — Change Management at Wave Scale
Training one practice manager is a thirty-minute call. Training the practice manager cohort across seventy-five locations is a wave program — written materials, regional sessions, escalation paths, performance feedback loops. The supplement details the wave structure Voicify ships for DSO buyers and contrasts it with what each A-or-B competitor offers. The artifact is what the VP of operations reads before signing off on rollout scope, and what regional ops directors reference when they audit how their patch is being supported.
Dimension Seven — Rip-and-Replace Incumbency
Many DSOs already run a receptionist, scheduling, or patient-communication vendor at scale. A new vendor deal is a rip-and-replace, not greenfield. The supplement extends the migration battlecard with the DSO-specific migration arc — how data ports across at consolidated-PMS scale, how the rep frames the switching cost case to a CFO who has already capitalized the incumbent integration, and how Voicify and each A-or-B competitor pattern the cutover. Migration risk is higher in a DSO and the upside narrative needs to clear that bar.
How the DSO Layer Plugs Into the Library
The DSO layer ships as five one-page supplements, each attached to a parent artifact in the existing library. The stakeholder map gets the DSO stakeholder supplement. The pricing-procurement battlecard gets the multi-location ROI and contract supplements. The IT integration due-diligence battlecard gets the multi-location integration supplement. The slot decision tree gets the three-rollout-model supplement. The migration battlecard gets the rip-and-replace supplement. The wave-rollout training supplement is the one new connective artifact the layer adds.
Under the governance SOP, each supplement is tiered to match the parent — Tier 1 supplements refresh quarterly with their parent, Tier 2 supplements refresh semiannually. Ownership of the supplement sits with the same person who owns the parent artifact, so the library does not gain ten new owners. The comparison matrix gains a DSO column toggle but not a separate matrix. The discovery brief gains a DSO question bank as an appendix. The result is one library, one refresh cycle, one set of facts, with a DSO overlay reps pull when the deal calls for it. The maintenance load grows by minutes per quarter, not days.
What the DSO Layer Does Not Try to Do
The DSO layer does not replace the primary battlecard. Competitive facts about Voicify and each A-or-B competitor live in the primary, refresh in the primary, and stay singular. The DSO layer adds the buyer-segment overlay only.
The DSO layer does not pretend every DSO is the same. Sixty-location regional DSOs and four-hundred-location private-equity-backed national DSOs differ on rollout cadence, IT maturity, and contract sophistication. The supplements carry segment notes the rep applies based on the DSO's profile — but the supplements stay one page each so the rep is not buried in conditional logic at deal time. The judgment is the rep's; the supplement gives the rep the framing.
The DSO layer does not replace the AE pre-call prep or the discovery brief. It supplements them. The rep still runs pre-call prep with the primary brief and the DSO supplements pulled forward; the discovery brief still anchors the conversation; the supplements give the rep the segment-specific framing once the deal pattern is identified.