A dental AI A-or-B battlecard library does not fail on day one. It fails on day one hundred and eighty. Owners drift to new roles, refresh dates slip, field intel piles up in nobody's inbox, retired artifacts keep getting referenced from current training material, and reps quietly stop opening cards because the last three they checked were six months behind on pricing. By the time anyone notices, the library has moved from competitive asset to dead-weight folder. The governance SOP is the operating layer that prevents that decay. It names one owner per artifact, one refresh cadence per tier, one intake path for field intel, and one deprecation rule for retired material. Without governance, every other Voicify A-or-B artifact in the library is on a clock.
TL;DR
One owner per artifact. Three tiers. Quarterly, semiannual, annual cadence. One intake. One deprecation rule. The Voicify A-or-B battlecard governance SOP assigns one named owner per artifact, sorts every artifact into one of three tiers — combat (quarterly), operational (semiannual), connective (annual) — runs all field intel through a single biweekly inbox dispositioned to four lanes (accept now, accept with confirming-signal monitoring, reject with logged reason, out-of-cycle escalate), and retires artifacts only with a steering decision into an archive folder with header notes preserving inbound links. Out-of-cycle updates are reserved for material competitive events. The SOP is what turns a thirty-artifact folder into a living library reps actually open before deal-critical calls.
Why Governance, Not Content, Is the Failure Point
The Voicify A-or-B library is not undertooled. Between the primary battlecard, the comparison matrix, the objection handling map, the demo script, the discovery brief, and the operational and connective artifacts surrounding them, a sales team running A-or-B deals has more written material than a rep can read in a quarter. The failure mode is not absence of content. The failure mode is governance — who keeps it current, who decides when something needs to change, and who removes things that no longer apply.
The pattern across dental AI sales orgs that have built libraries like this is consistent. Quarter one, the library ships with high energy and clean ownership. Quarter two, owners get pulled into a launch and a few refreshes slip. Quarter three, slipped refreshes accumulate and field intel piles up in a shared Slack channel nobody owns. Quarter four, reps have stopped opening half the cards because the last three they checked were behind on pricing or referenced a feature that shipped two releases ago. By month eighteen, the library is a folder of dead documents the new AEs are confused by during onboarding. The cure is not better content. The cure is a published, enforced governance SOP that names owners, sets cadence, and runs an intake path.
The Three Artifact Tiers
The first decision the SOP makes is sorting every artifact into one of three tiers. Tier assignment determines refresh cadence, owner seniority, and intake priority. The tiers are stable — an artifact does not change tiers without a steering decision — and the assignment is published in the library index so every consumer knows what cadence to expect.
| Tier | Definition | Refresh cadence | Representative artifacts |
|---|---|---|---|
| Tier 1 — Combat | Artifacts reps open before deal-critical conversations | Quarterly | Battlecard, comparison matrix, objection map, demo script, discovery brief |
| Tier 2 — Operational | Instruments that shape how reps and managers run the system | Semiannual | Pilot scorecard, slot decision tree, AE pre-call prep, coaching cadence, forecast scorecard, coaching scorecard |
| Tier 3 — Connective | Routing layers and post-deal artifacts that tie the system together | Annual, with triggered exceptions | Stakeholder map, champion kit, IT integration due-diligence, CSM B-slot defense, sales-to-CSM handoff, win-loss debrief, field intel, quarterly refresh, rep certification, this governance SOP |
Staleness in Tier 1 costs revenue directly — a rep walks into a demo with a six-month-old pricing claim and loses credibility in the first ten minutes. Staleness in Tier 2 costs forecast accuracy and coaching effectiveness. Staleness in Tier 3 costs systemic alignment over time. The cadence reflects the cost: combat artifacts must be current; connective artifacts can run on a longer clock because they encode mechanics that change less often than competitive facts.
One Named Owner Per Artifact
Every artifact has one owner — a person, not a team. The owner's name appears in the artifact header. The library index lists the owner alongside the refresh date. Co-ownership is not allowed because shared ownership is how libraries decay: when two people own a thing, neither does.
Tier 1 owners are senior product marketing or competitive intelligence leads — the people closest to the day-to-day competitive picture. Tier 2 owners are sales-operations or enablement leads — the people who run the operating system the artifacts shape. Tier 3 owners are distributed across CS leadership (handoff, B-slot defense), sales leadership (stakeholder map, champion kit, win-loss debrief), and enablement (certification, this SOP).
The owner does not personally write every word at refresh time. The owner convenes the inputs — field intel, rep feedback, the relevant section of the quarterly refresh meeting — signs off on the proposed changes, and owns the version stamp. The owner is the person who gets paged when the artifact is wrong and the person whose name surfaces in the refresh meeting if the date slips. Accountability sits with one human, and the human is named.
The Field-Intel Intake Path
Field intel is captured at the end of every deal-critical interaction through the standard field intel capture template. The SOP's role is what happens to that intel between capture and library update. Without a published intake path, intel either sits in a shared channel and is forgotten or, worse, becomes a series of anecdotal updates that thrash the library every time a rep loses a deal.
The intake path runs through one inbox owned by the competitive intelligence lead. Inbox review happens biweekly. Each item is dispositioned to one of four lanes.
- Accept now. The signal is corroborated, the implication is clear, and the next refresh of the affected artifact incorporates the change. Owner is notified.
- Accept with monitoring. The signal is plausible but single-source. Inbox notes the item and waits for two more confirming signals before promoting. Prevents anecdote-driven thrash.
- Reject with reason. The signal contradicts established positioning or rests on a misread by the rep. Reason is logged and surfaced back to the submitting rep so the rejection is teachable, not silent.
- Out-of-cycle escalate. The signal represents a material competitive event — a pricing change, a feature release that invalidates a current claim, a regulatory event — that cannot wait for next scheduled refresh. The relevant artifact owner is notified within forty-eight hours and an out-of-cycle update is published with a version-stamp annotation.
Out-of-cycle updates are reserved. The threshold is material competitive change that costs deals if reps run the old card for another six weeks. A new objection pattern reported by two reps in one week is not out-of-cycle; it goes to monitoring. A confirmed competitor price drop is out-of-cycle. Maintaining the discipline of the threshold is what keeps the library stable.
Version Control and Change Logging
Every artifact carries a visible version stamp in its header — version number, last refresh date, owner name. Every refresh updates the version stamp and appends one line to the artifact's change log: date, what changed, and why. The change log lives at the end of each artifact, not in a separate file, so any consumer reading the artifact can see how it has evolved.
Three rules govern the log. First, only material changes are logged — a typo fix does not earn an entry. Second, the why matters more than the what; "added pricing tier 4" is less useful than "added pricing tier 4 in response to Competitor B's enterprise plan launch, signal corroborated across three deals." Third, the log is not rewritten or pruned; it accumulates so future owners can read the artifact's history and understand current state in context.
The Deprecation Rule
Artifacts that are no longer current move to an archive folder with a header note stating retirement date, reason, and the superseding artifact if one exists. They are not deleted. Referenced links from other artifacts, from internal training material, and from rep certification would break silently if retired material were deleted outright. The library index marks retired artifacts with a strikethrough so consumers know not to use them but can still follow inbound links.
Retiring an artifact requires a steering decision documented in the quarterly refresh meeting minutes. Owners cannot retire their own artifacts unilaterally — downstream consumers may depend on the artifact in ways the owner does not see. The rep certification process and the quarterly refresh both check for active references to retired artifacts in live rep workflows; any found triggers remediation. The deprecation rule is what stops the library from becoming a graveyard reps wade through to find current material.
How the SOP Connects to the Rest of the System
The governance SOP is itself a Tier 3 artifact, refreshed annually. Its connections to the rest of the library are bidirectional. The quarterly refresh meeting is where the SOP gets enforced — owner names get verified, slipped refresh dates surface as red items, deprecation decisions get logged. The manager coaching cadence reinforces the SOP at the rep level — reps who never submit field intel get coached on the intake path, and persistent non-submission becomes a certification signal. The coaching scorecard grades whether managers are catching slipped refreshes in their patch. The win-loss debrief feeds patterns into the intake inbox. The stakeholder map, the sales-to-CSM handoff, and every other connective artifact run on the cadence the SOP sets.
The SOP is the operating layer everything else assumes exists. The cluster of A-or-B artifacts can describe what a great battlecard system does on a single deal. Only the governance SOP describes what keeps that system alive across two years.
What the SOP Does Not Do
The SOP does not write content. It schedules, assigns, and routes — the actual writing of a refreshed objection map or pricing battlecard is the owner's job, drawing on the inbox, the win-loss debrief, and the quarterly refresh inputs. Treating the SOP as a content engine pushes work onto a document that has no hands.
The SOP does not enforce quality. A refreshed artifact that lands on time but is poorly written passes the cadence check and fails the rep-usefulness check. Quality is the owner's responsibility, and the quarterly refresh meeting is where quality gets flagged when it slips. The SOP's job is making sure refreshes happen; the meeting's job is making sure they are good.
The SOP does not replace the battlecard QA checklist. The checklist runs at refresh time inside each artifact owner's workflow. The SOP says when the refresh happens and who owns it; the checklist says what the refresh has to clear before it ships. Both are required. The SOP without the checklist produces on-time slop; the checklist without the SOP produces high-quality artifacts that never get refreshed.