The fastest way for a Voicify "Competitor A or Competitor B" battlecard program to lose its credibility is for a rep to deliver, on a live call, a claim about a named competitor that was true ten months ago and is not true today. The claim was in the comparison matrix. It was in the demo script. It was in the one-pager the AE handed the procurement lead. None of the artifacts pointed back to the same dated row in the evidence library, so when the competitor shipped a feature that closed the gap, the program had no fire alarm — every artifact carrying the claim quietly went stale, the reps kept delivering it, and the buyers who knew the new feature existed quietly moved Voicify out of finalist position. The claim citation standard is the artifact that prevents this. It is the format every named-competitor claim wears, in every artifact, so the program can see staleness coming and pull it before a rep delivers it.
TL;DR
The claim citation standard locks every named-competitor claim in a Voicify A-or-B artifact to a sourced, dated, strength-tiered row in the battlecard evidence library — and fails loudly when the row expires. Every citation carries five fixed fields: library row ID, source descriptor, captured date, strength tier, and expiration trigger. Tier A claims (primary public sources) can be delivered verbatim; tier B (testimonial, analyst, intel) requires attribution framing; tier C (hearsay) is internal-reference only. The citation rides with the claim everywhere a buyer sees it — matrix, demo, talk track, one-pager. When a row expires, every artifact citing it pulls from production and every certified rep recertifies on the new line. The standard does not prevent staleness; it makes staleness visible.
Why the Citation Standard Is a Separate Artifact
The battlecard evidence library and the claim citation standard are often conflated, and that conflation is the source of most of the field failures in a competitive program. The battlecard evidence library is the warehouse — every named-competitor fact about Competitor A or Competitor B lives there as a row, with a source link, a captured date, a strength tier, and an expiration trigger. The citation standard is the format that governs how a claim references that row anywhere else in the program. Library is the warehouse, citation is the bill of lading. Without the citation standard, a comparison matrix bullet, a demo script line, or a one-pager paragraph can drift from its underlying library row across revisions and the rep delivering it has no way to verify provenance in the moment.
The reason the citation rides on the artifact and not just in the library is that the rep does not have time, during a live call, to open the library and look up the row. The rep has to read the citation block next to the claim, judge in five seconds whether it is safe to deliver, and either deliver it, soften it, or skip it. That five-second judgment is what the citation standard exists to support.
The Five Fixed Fields
The citation block is five fields, in order. Every field is required. No optional fields. No variant formats. The format is fixed for the same reason a clinical citation in a regulated marketing piece is fixed — lookup time goes up and the audit trail breaks the moment you allow per-claim formatting.
| Field | Purpose | Example |
|---|---|---|
| Row ID | Pointer back to the evidence library row | EL-2026-A-217 |
| Source descriptor | What kind of source — not the URL inline | Primary public spec sheet |
| Captured date | When the source was logged into the library | 2026-03-14 |
| Strength tier | A (primary public), B (attributed), or C (internal only) | Tier A |
| Expiration trigger | Absolute date or triggered event | Expires on competitor next release or 2026-09-14, whichever is sooner |
The block lives next to the claim, not in a footer the rep has to chase. The format is short enough that it does not bloat the artifact and long enough that the rep can decide what to do with it in real time.
Why Strength Tier Is Load-Bearing
Not every claim is the same caliber. A rep delivering a tier A claim and a rep delivering a tier C claim are running two different playbooks, and the citation block surfaces which one applies before the words leave their mouth.
- Tier A — Primary public source. The competitor's published spec sheet, SEC filing, public clinical study, public pricing page, public release notes. Tier A claims can be delivered verbatim on a buyer-facing call. The rep states the fact as fact. No softening, no attribution required.
- Tier B — Attributed source. Customer testimonial, third-party analyst report, win-loss interview, competitive intel call from a public conference. Tier B claims require attribution framing — the rep says "according to a former [competitor] customer we spoke with" or "the most recent analyst report on the category notes." The fact is delivered with its source named.
- Tier C — Internal reference only. Hearsay, anonymous intel, single-source secondhand reports. Tier C claims are allowed in the matrix and the field intel capture for internal reference and triangulation. They never appear in a buyer-facing artifact, ever.
The tier is determined at capture, by the battlecard governance SOP, and is locked once written. It can be upgraded only by capturing a new corroborating source at a higher tier and re-tagging the row.
Expiration as a Fire Alarm
Every citation block carries an expiration trigger — either an absolute date or a triggered event. Common triggers in the Voicify A-or-B program include a new release from Competitor A or Competitor B, a pricing change announced on the competitor's public page, a feature announcement at a category conference, an SEC filing or earnings call disclosure, or simply a six-month default for facts that do not have an obvious trigger.
When the trigger fires, the battlecard analytics dashboard surfaces every artifact in the program that cites the expired row. The field marketing team pulls those artifacts from production. The library row is reopened for refresh. Every rep certified against any affected artifact is queued for recertification on the new line via the rep certification standard. The discipline does not prevent staleness — staleness is inevitable in a fast-moving competitive market — but it makes staleness visible the moment it happens.
Which Artifacts the Standard Rides On
The citation rides with the claim everywhere a buyer can see it. That includes the comparison matrix, the side-by-side, the demo script, the talk track, the objection-handling card, the one-pager, the SDR outbound sequence, the executive briefing, and any pricing-procurement materials that reference competitor pricing. Internal-only artifacts that do not deliver claims to buyers — the rep certification rubric, the manager coaching cadence, the analytics dashboard, the rollout playbook — reference the citation standard but do not embed full citations because they operate on the artifacts that already carry them.
The QA checklist verifies citation block compliance at every artifact revision — wrong format, missing field, untracked row ID, or unmapped expiration trigger fails the artifact at gate review. The standard is enforceable because it is short, fixed, and machine-checkable.
The Rep's Five-Second Judgment
The whole standard exists to support one moment: the rep, mid-call, looking at a citation block next to a claim and deciding whether to deliver it. The five-second judgment is row ID present, captured date inside the last refresh window, strength tier readable, expiration trigger not yet fired. If all four pass, the rep delivers the claim per the tier's playbook. If any fail, the rep softens, attributes, or skips and flags the artifact for review through the field intel capture workflow. That moment — the five-second judgment, repeated across every named-competitor claim in every call — is the difference between a battlecard program that compounds trust with buyers and one that erodes it.