A Voicify "Competitor A or Competitor B" dental AI battlecard library does not fail in the writing. It fails in the rollout. Enablement spends a quarter building thirty artifacts, drops them in a shared drive, runs a one-hour all-hands, and expects reps to open the right artifact before the right conversation. Three weeks later, half the team cannot find the battlecard, managers have not absorbed it into 1:1s, the field intel inbox is empty, and the next deal-critical call goes out on the old talk track. The library is launched on paper and dead in practice. The rollout playbook is the 30-day operational sequence — plus the 90-day stickiness gate — that prevents that outcome. It turns launch from an event into a system, and it is what separates a library that gets used from a folder reps forget about by month two.
TL;DR
Five preconditions. One launch week. Four weekly checkpoints. One 90-day gate. The Voicify A-or-B dental AI battlecard rollout playbook treats launch as a 30-day sequence, not an event. Before launch: owners assigned, governance SOP published, certification path ready, manager cadence updated, intake inbox live. Launch week: role-specific orientation Monday through Friday — kickoff, AE training, SDR training, manager calibration, certification opens. Weeks 2-4: certification completion, intake volume, deal-note reference rate, manager coaching scorecard data. Day 90 stickiness gate: refresh on schedule, intake still flowing, references still visible, new-hire certification holding. Pass the gate, the library is adopted. Miss it, the library is a folder reps quietly stopped opening.
Why Rollout Is the Real Failure Point
The Voicify A-or-B library is rarely undertooled. Between the primary battlecard, the comparison matrix, the objection handling map, the demo script, and the operational and connective artifacts that surround them, a competitive AI sales org launching one of these libraries has more written material than a rep can absorb in a quarter. The failure mode at launch is not absence of content. The failure mode is treating launch as the moment the content exists rather than the moment the surrounding operating system absorbs it.
The pattern across dental AI receptionist sales orgs that have shipped these libraries is consistent. The artifacts are good. The training session is fine. Adoption peaks at week one and decays from there. By week six, the intake inbox is empty. By week ten, the first scheduled refresh has slipped. By month four, the library is a folder the new hires get pointed to during onboarding and the tenured reps stopped opening. The library is not used because the rollout did not install the behaviors that would have made using it routine. The playbook below is the install procedure.
The Five Preconditions Before Launch Week
Launching into a vacuum is the most expensive mistake in battlecard rollout. If the operating layer around the library is not in place when launch week starts, no amount of training-day energy will hold. Five conditions must be true before launch week kicks off.
| Precondition | What "ready" looks like | Owner |
|---|---|---|
| Tier 1 owners assigned | Every combat artifact has one named owner and a version stamp in the header | Competitive intelligence lead |
| Governance SOP published | Three-tier sort, refresh cadence, intake path, deprecation rule all written and accessible | Enablement lead |
| Certification path ready | At least one mock-call scenario per rep tier; certification rubric published | Sales enablement |
| Manager cadence updated | 1:1 template and pipeline review template reference battlecard usage as a coachable behavior | Sales operations |
| Intake inbox live | Single inbox owned by competitive intelligence lead; biweekly review scheduled | Competitive intelligence lead |
The governance SOP is load-bearing because it makes ownership and cadence legible to reps and managers from day one. The rep certification path is load-bearing because it converts "we trained you" into "you demonstrated competence on a real scenario." Without all five preconditions, launch week produces enthusiasm but not adoption.
Launch Week: Day-by-Day
The point of launch week is not to certify every rep by Friday. It is to give every consumer of the library — AEs, SDRs, first-line managers, CS — a role-specific orientation so that week two starts as execution rather than orientation. Five days, five lanes.
- Monday — All-hands kickoff. Leadership opens with why this library matters now. Competitive intelligence lead walks the library structure and the governance SOP. Every rep leaves with the library index bookmarked, the certification due date on their calendar, and one assigned reading: the primary battlecard before Tuesday.
- Tuesday — AE deep dive. Tier 1 combat artifacts walked in detail. Two live deal applications: take a current pipeline deal, identify which artifact would have changed the last conversation, role-play the next one with the artifact open. Pre-call prep introduced as the routine that ties artifacts to live calls.
- Wednesday — SDR training. The outbound sequence and the discovery brief walked with concrete prospect examples. Objection map drilled live on the patterns SDRs hear most. Handoff to AE practiced.
- Thursday — Manager calibration. First-line managers walk through how they will reference the library in next Monday's 1:1s and Tuesday's pipeline reviews. Coaching cadence updates rolled out. Managers commit publicly to one battlecard-coaching moment per rep per week through end of month.
- Friday — Certification window opens. Field intel intake inbox announced. Competitive intelligence lead opens office hours. First field intel submissions encouraged from reps with active deals.
The Friday handoff matters most. If launch week ends with the certification window open, the intake inbox live, and at least one field intel submission posted publicly by Friday afternoon, the rest of the rollout has surface to run on. If Friday ends with applause and no behavioral handoff, the library is in trouble already.
Weeks 2-4: The Four Adoption Checkpoints
Adoption does not happen because reps are inspired. It happens because the surrounding system makes using the library the path of least resistance. Four weekly checkpoints surface whether that is happening in time to correct.
Week 2 — Certification completion rate
Target: 100 percent of in-seat reps certified by end of week 2. Track in a published dashboard. Reps who have not started by Wednesday get a manager prompt; reps who have not completed by Friday escalate. Certification is not a soft commitment — uncertified reps are coached out of deal-critical conversations until they clear the bar.
Week 3 — Field intel intake volume
Target: at least one submission per AE per week, with heavier patches contributing more. Track in the competitive intelligence inbox dashboard. Empty inboxes are not "no signal" — they are "reps do not yet trust the intake path." If volume is below threshold, the competitive intelligence lead seeds one submission per day for week three from observed deals to model the behavior.
Week 4 — Battlecard reference rate in deal notes
Sample CRM deal notes from deal-critical interactions during the week. Target: visible reference to one or more library artifacts in 60 percent of sampled notes. The reference does not need to be a citation — a phrased decision ("opened with discovery brief", "ran objection X from the map") is enough. Notes with zero artifact references are surfaced to first-line managers as coaching signals.
Week 4 — Manager coaching scorecard data
The coaching scorecard for the month must show every first-line manager has referenced the library in at least one 1:1 per rep and one pipeline review per patch. Manager silence is the single biggest predictor of adoption failure; surfacing it weekly is what prevents it.
The 90-Day Stickiness Gate
A library can clear week four cleanly and still be dead by day ninety. The stickiness gate is the published checkpoint that decides whether the rollout actually installed the behaviors or just papered over them for a month. Four conditions must hold at day ninety.
- First quarterly refresh shipped on schedule. Tier 1 artifacts have a fresh version stamp dated within the last week. The quarterly refresh meeting happened with full owner attendance.
- Field intel intake still flowing. Weekly submission volume in week twelve is within 25 percent of week four. A drop greater than that means the intake mechanism is decaying.
- Deal-note references still visible. Sampled deal notes in week twelve show artifact references at a rate within 10 percentage points of week four.
- New-hire certification holding. Reps onboarded since launch have completed certification at the same bar as the launch-week cohort. No two-tier rep population.
If three of four hold, the rollout passes the gate and moves into steady-state governance. If two or fewer hold, the rollout failed and the next 30 days are remediation, not new content. Remediation almost always means re-engaging managers — the failure modes that kill adoption all route through manager silence in one form or another.
The Five Adoption Killers and How the Playbook Catches Them
Across dental AI receptionist sales orgs that have rolled these libraries out, five recurring failure modes account for nearly every rollout that quietly fails. The playbook is designed to make each visible early.
- Manager silence. First-line managers do not reference the library in 1:1s or pipeline reviews. Caught at week four by the coaching scorecard checkpoint.
- Refresh slip. The first scheduled quarterly refresh slips two weeks, version stamps go stale, reps notice. Caught at the 90-day gate.
- Intake silence. The field intel inbox runs empty for six weeks. Caught at week three checkpoint.
- Certification leak. New hires post-launch are not held to the same bar. Caught at the 90-day gate.
- Out-of-cycle abuse. Every anecdote becomes an out-of-cycle update, the library thrashes, reps stop trusting current versions. Caught by the governance SOP intake disposition lanes.
What the Playbook Does Not Do
The playbook is a launch sequence, not a content guarantee. If the underlying artifacts are weak — a thin objection map, a battlecard that overpromises — no rollout cadence will hold the library together. Quality lives in the QA checklist at refresh time, not in the rollout playbook.
The playbook also does not replace the governance SOP. The SOP is the steady-state operating layer that keeps the library alive month over month. The playbook is the 30-day procedure that hands the library off into that steady state. Both are required. The SOP without a rollout produces a library no one knows how to use; the rollout without an SOP produces a library that adopts well and decays in two quarters.