What is a battlecard intake brief for Voicify A-or-B dental AI sales?

A battlecard intake brief is the seven-field gate every proposed Voicify A-or-B battlecard or comparison matrix entry must clear before a product marketer is authorized to spend hours writing it. The brief is filled out by the requester — usually a rep, a sales manager, or the competitive intel lead — and reviewed in a fifteen-minute weekly intake meeting. It exists because battlecard libraries die of one of two failures: they ship cards no one needs because no one asked the requester to define the use case, or they ship the same card three times under three names because no one checked the library before writing. The brief forces a use case, a target deal pattern, a hypothesized rep behavior change, an existing-card audit, an attribution plan, an owner, and a kill criterion. Cards that cannot answer all seven fields are not written. The brief is the upstream control on what enters the library and the single largest source of dead-weight prevention in a Voicify A-or-B competitive program.

What are the seven fields on the intake brief?

One — the triggering deal pattern, a description of the specific Voicify A-or-B deal shape this card is meant to help reps win, including segment, slot tag, and the competitor scenario. Two — the rep behavior change, a sentence that completes the form 'after reading this card the rep will say or do X differently in the next live call.' Three — the existing-card audit, a list of any battlecard already in the library that touches the same use case, with a one-line explanation of why a new card is needed instead of an edit to an existing one. Four — the attribution plan, the specific deal-stage advance or won-deal pattern the card is hypothesized to correlate with, so the analytics dashboard knows what to track. Five — the named owner, a single person — usually a product marketer — accountable for the card from publish through every quarterly refresh. Six — the kill criterion, the floor on the analytics dashboard the card must clear within two quarters or it is archived. Seven — the field-test plan, the two or three reps who will read the draft and give a thumbs-up or thumbs-down before publication. Cards missing any field are returned to the requester, not written.

Who fills out the brief and who approves it?

The requester fills out the brief — most commonly a rep or sales manager surfacing a specific live-deal pattern, occasionally the competitive intel lead surfacing a new Voicify A-or-B competitor move, and occasionally a customer success manager surfacing a renewal or expansion pattern. The competitive intel lead approves the brief in a fifteen-minute standing weekly intake meeting with the product marketing manager and one rotating sales manager. Approvals are binary — green-lit for writing, returned for more detail, or declined outright. Declined briefs are documented with a one-line reason, so a future requester does not re-submit the same scope. Approved briefs are assigned to a named product marketer with a publication target date and a kill criterion already baked into the assignment, so the writer knows on day one what the card will be measured against and when it gets archived if it fails.

How does the intake brief connect to the rest of the Voicify A-or-B cluster?

The intake brief feeds every downstream artifact in the cluster. The triggering deal pattern field feeds into the slot tagging used by the analytics dashboard for held-within attribution. The attribution plan field is what the dashboard uses to determine whether the card is in the working library after two quarters. The kill criterion field is enforced by the governance SOP as the hard archival rule. The named-owner field feeds the quarterly refresh meeting agenda, so refreshes are assigned to a specific person not a vague team. The field-test plan feeds the rep certification cycle, so the reps who tested the draft become the first certified readers. The result is that every card in the library carries its own measurement contract from day one, and the library stops accumulating cards no one can explain the reason for two quarters later when the original requester has rotated off the team.

Voicify "Competitor A or B" Dental AI: Battlecard Intake Brief

Q: Why is the intake brief separate from the battlecard governance SOP?

The governance SOP runs after a card exists — it covers review cadence, refresh ownership, version control, and archival rules. The intake brief runs before a card exists — it is the gate that decides whether a card should be written at all. The two are complementary but the intake brief carries the heavier load on library quality, because it is much cheaper to refuse to write a redundant or unattributable card than to ship one and then argue about archiving it three quarters later. Separating intake from governance also separates the decision rights: the competitive intel lead approves intakes, the product marketing manager owns governance, and the sales VP signs off on archival exceptions. Without a separate intake brief, requests pile up in the governance forum and the meeting becomes triage instead of strategy. With the brief in place, the governance meeting only sees cards that have already cleared the seven-field gate, and the conversation can move to refresh and archival decisions instead of scope debates.

Every Voicify "Competitor A or Competitor B" battlecard library that goes dead at quarter six dies of one of two failures upstream. Either the library ships cards no one needs because no one asked the requester to define the live-deal pattern the card was meant to help reps win, or the library ships the same card three times under three names because no one checked what was already there before writing. Both failures happen in the same place — in the gap between a sales manager saying "we need a card on X" and a product marketer opening a blank doc to write it. The battlecard intake brief is what fills that gap. It is the seven-field gate every proposed card or comparison matrix entry must clear before a product marketer is authorized to spend forty hours writing it, and it is the single largest source of dead-weight prevention in any disciplined Voicify A-or-B competitive program.

TL;DR

Seven fields. One weekly meeting. No card gets written that cannot answer all seven. The Voicify A-or-B battlecard intake brief forces the requester to name the triggering deal pattern, the specific rep behavior the card will change, any existing card that already touches the use case, the attribution plan the analytics dashboard will read, the named owner, the kill criterion, and the field-test reps. Cards missing any field are returned, not written. The competitive intel lead approves in a fifteen-minute weekly intake meeting alongside the product marketing manager and a rotating sales manager. The brief sits upstream of the governance SOP, the analytics dashboard, the quarterly refresh, and the rep certification cycle — every downstream artifact reads from the intake fields. The result is a library where every card carries its own measurement contract from day one and the library stops growing by accident.

Why the Brief Lives Upstream of Governance

The battlecard governance SOP runs after a card exists. It covers review cadence, refresh ownership, version control, and archival. It is necessary but it is not sufficient, because by the time governance is reviewing a card the writing cost has already been paid and the political cost of archival has already accrued. The intake brief runs before the writing cost is paid. It is much cheaper to refuse to write a redundant or unattributable card than to ship one and then argue about archiving it three quarters later when the requester has moved on and a new sales manager wants to defend a card she did not commission.

Separating intake from governance also separates the decision rights, which is the second reason the brief is its own document. The competitive intel lead approves intakes. The product marketing manager owns governance. The sales VP signs off on archival exceptions. Without the brief, all three conversations happen in the same forum, the meeting becomes triage instead of strategy, and the rep-facing library suffers because the people responsible for it are too busy debating scope to look at the analytics dashboard.

The Seven Fields

Every brief carries the same seven fields. The fields are not negotiable. A brief missing one is returned to the requester with a one-line note explaining what is missing. The requester resubmits or drops the request. There is no compromise tier where a brief gets approved with four fields and a hand-wave on the rest — that path is how libraries get dead weight.

#	Field	What it forces the requester to commit to
1	Triggering deal pattern	The segment, slot tag, and competitor scenario this card is meant to help reps win
2	Rep behavior change	A sentence completing "after reading this, the rep will say or do X differently on the next live call"
3	Existing-card audit	A list of cards already in the library that touch the same use case, with a reason the edit path was rejected
4	Attribution plan	The specific stage advance or won-deal pattern the card is hypothesized to correlate with
5	Named owner	One person accountable for the card through every quarterly refresh, not a team alias
6	Kill criterion	The dashboard floor the card must clear within two quarters or it is archived
7	Field-test plan	The two or three reps who will read the draft and give a thumbs-up before publication

Field 1 — the triggering deal pattern

Every card is built for a specific shape of deal. "Hundred-location DSO weighing Voicify against Competitor A in a head-to-head with IT on the call" is a triggering pattern. "Sales reps need a way to handle pricing pushback" is not — it does not name segment, does not name slot, does not name the competitor scenario, and is therefore unwritable in a way that produces a measurably useful card. The triggering pattern field feeds directly into the slot tagging used by the analytics dashboard for held-within attribution.

Field 2 — the rep behavior change

If the card cannot finish the sentence "after reading this, the rep will say or do X differently on the next live call," it is not a battlecard. It is a wiki page, and wiki pages do not belong in a battlecard library. This field exists because most rejected briefs fail here — the requester knows there is a problem but cannot articulate what the rep would do differently after reading, which means the card has no clear shape and would be written as an unfocused information dump.

Field 3 — the existing-card audit

The requester must search the library and list any card that touches the same use case. If a card already exists, the default is to edit it. A new card is justified only if the existing card is scoped differently in a way the requester can articulate. This is the field that prevents a library of thirty cards from becoming a library of forty-two cards where the marginal twelve are minor remixes of the original thirty.

Field 4 — the attribution plan

The card must declare what the analytics dashboard should look for. "Reps who read this card before a DSO discovery-to-demo advance" is a plan. "Generally helps reps close more deals" is not. The attribution plan field is what the dashboard uses to determine whether the card is in the working library or the dead-weight quadrant after two quarters.

Field 5 — the named owner

One person, not a team. The owner is on the hook for every quarterly refresh, every dashboard review, every customer-conversation update that affects the card. Team-alias ownership produces orphan cards within two rotations.

Field 6 — the kill criterion

The owner declares, at intake, what dashboard floor the card must clear within two quarters or it is archived. Writing the kill criterion at intake is uncomfortable, which is the point — it forces the requester and owner to admit the card might fail, and to specify the failure mode in advance. The governance SOP enforces this field.

Field 7 — the field-test plan

Two or three named reps read the draft before publication and give a thumbs-up or thumbs-down. The thumbs-down reps are the most useful — their objections become the second draft. Field-test reps become the first certified readers in the rep certification cycle, so the field-test plan and the certification plan share a roster.

The Weekly Intake Meeting

Fifteen minutes, standing slot, three attendees — the competitive intel lead, the product marketing manager, and one rotating sales manager. The agenda is the queue of briefs submitted in the prior seven days. Each brief gets a binary outcome: green-lit for writing, returned for more detail, or declined outright. Declined briefs are documented with a one-line reason in a running log, so a future requester does not resubmit the same scope and waste another meeting cycle. Approved briefs are assigned to a named product marketer with a publication target date and a kill criterion already baked into the assignment, so the writer knows on day one what the card will be measured against.

The rotating sales manager seat matters more than it looks. The intel lead and the product marketing manager will, given time, develop blind spots around what reps actually struggle with on live calls. A rotating manager seat keeps the intake meeting honest by putting someone in the room who heard the latest objection on a deal yesterday afternoon.

How the Brief Feeds the Cluster Downstream

Every downstream artifact in the Voicify A-or-B cluster reads from the intake brief. The triggering deal pattern feeds the comparison matrix tagging. The attribution plan feeds the analytics dashboard. The kill criterion feeds the governance SOP. The named owner feeds the quarterly refresh agenda. The field-test plan feeds the rep certification cycle. The result is that every card in the library carries its own measurement contract from the day intake is approved, and a card that fails has a documented kill criterion already signed off by its own owner — no political fight, no rescue committee, just the archive folder.

The brief is the unsexy upstream control that does more to keep a battlecard library alive than any analytics dashboard or governance SOP downstream. It costs fifteen minutes a week. It saves four to six unpublished cards per quarter that would otherwise have shipped, sat unopened for two quarters, and consumed the political energy of an archival debate. For Voicify A-or-B dental AI sales orgs running fifteen to thirty reps and a library of twenty-plus cards, the intake brief is the gate that decides whether the library stays a working tool or drifts into a museum.

Voicify "Competitor A or Competitor B" in Dental AI: Battlecard Intake Brief