When to Name Voicify and When to Anonymize as "Competitor A" or "Competitor B"

The "Competitor A" / "Competitor B" label is not a stylistic choice. It is a content-governance decision that determines whether a dental AI battlecard can leave a sales-enablement library safely, how much legal review it needs, and how much of its SEO and field-clarity value it gives up in exchange for portability. Teams that default to anonymizing Voicify everywhere lose brand-keyword traffic and slow their reps down. Teams that default to naming Voicify everywhere create legal exposure the moment a deck leaves the building. The right answer is a naming-convention rulebook — a small set of context-dependent rules that decide, per artifact, whether Voicify gets named directly or sits under a "Competitor A" or "Competitor B" label. This post is that rulebook.

The Three Contexts That Decide the Label

Every dental AI battlecard lives in one of three contexts, and the context decides whether Voicify gets named or hidden behind a placeholder. The first context is the internal, rep-only card — the artifact a sales rep opens five minutes before a call. Recognition speed matters most here, and the audience cannot redistribute. Name Voicify directly. The second context is the externally distributed template — a card that ships to channel partners, prospects, or analysts. The publisher has no control over redistribution and limited control over how claims are excerpted. Anonymize Voicify as Competitor A or B. The third context is the public SEO asset — a blog post or comparison page intended to capture branded search traffic. Naming is required for SEO to function, but every claim has to clear a higher accuracy bar because the page is indexed and quotable. Name Voicify, and route the draft through legal before publication.

The Legal Frame: Nominative Fair Use Allows Naming, Substance Drives Risk

Direct naming of Voicify in a competitive battlecard is permitted in the United States under the nominative fair use doctrine, which allows the use of a competitor's trademark to identify that competitor for comparison purposes. The Lanham Act creates risk not from the act of naming but from the substance of the claims. A statement that "Voicify charges $X per practice per month" must be defensible against Voicify's actual published pricing. A statement that "Voicify cannot integrate with Dentrix" must be defensible against Voicify's actual integration coverage. Field-intelligence claims — "Voicify's implementation typically takes 90 days, not 30 as quoted" — are the highest-risk category because they cannot be cited to a vendor-published source, even when reps know they are true from multiple deployments. The rule of thumb most healthcare-tech legal teams use is straightforward: name Voicify when the claim is cite-able to Voicify's own collateral, anonymize Voicify when the claim is sourced to your own customers, deployments, or field observations.

The SEO Trade-Off: Brand-Keyword Capture vs Template Portability

Naming Voicify directly on a public page is the only way to capture brand-keyword search traffic. A page titled "Voicify vs Arini Dental AI Battlecard" ranks for the exact phrase practice managers type into Google when they are comparing the two platforms. A page titled "Competitor A vs Competitor B Dental AI Battlecard" only ranks for the abstract comparison query, which has lower search volume and lower commercial intent — the people typing it are usually sales-enablement professionals researching the format, not buyers researching a purchase. The trade-off is that the anonymized version travels further. It can be repurposed for multiple deals, redistributed by partners without rework, and updated when one vendor changes posture without touching every related artifact. The clean way to resolve the trade-off is to publish both: a named SEO version for traffic capture, and an anonymized template version for the sales-enablement library. The named version lives in the blog. The anonymized version lives in the sales-enablement system. They share an underlying claim set. Our companion piece on slotting Voicify into the A or B position covers which posture the anonymized template takes, and the decoder for reading anonymized competitor battlecards covers what buyers do with the unnamed version once it reaches them.

The Field-Clarity Test: Will a Tired Rep Get It Right?

Sales-enablement leaders underweight this test and pay for it in deal cycles. A rep opening a battlecard at 7:55 am before an 8 am call needs to identify the vendor and the slot in under five seconds. Internal cards that anonymize Voicify as Competitor B fail the field-clarity test because the rep has to remember which letter maps to which vendor in this library — and the answer differs across libraries that the rep has worked in over their career. Direct naming on internal cards is the right call almost every time, even when the same content is being anonymized for external distribution. The two versions are not in conflict. They are two outputs from the same source data, optimized for two different audiences. The internal version uses "Voicify" because the rep is the audience and recognition speed wins. The external version uses "Competitor A" because the legal department is the audience and risk reduction wins.

The Disclosure Layer: What Every External Anonymized Card Needs

When an anonymized "Competitor A vs Competitor B" battlecard ships externally, three disclosures meet most legal-review bars and reduce the chance the artifact becomes a problem six months later. First, a footer note clarifying that the placeholder labels map to identifiable vendors and that the publisher can disclose the mapping on reasonable request. This defeats the appearance of a hidden agenda. Second, a per-row data-source notation indicating whether each comparison claim is sourced to public vendor documentation, customer reports, or analyst data. This blocks the most common deceptive-comparison challenge: that the publisher is presenting field intel as if it were vendor-confirmed fact. Third, a "last reviewed" date with a 90-day freshness window. Dental AI feature sets, pricing, and integration coverage shift quickly enough that an aged anonymized card invites a fact-based challenge from the named-but-unnamed vendor when they eventually identify themselves in it. Reviewing on a 90-day cadence keeps the artifact defensible and signals to readers that the comparison is current. For teams running this discipline across a battlecard library, our working battlecard template and the 60-minute sprint workshop show the production cadence end to end.

The Decision Tree, Compressed

The summary rule is that the label follows the audience and the source of the claim, not the artifact's title. Internal-and-cite-able stays named. External-or-field-sourced gets anonymized. The teams that run this discipline correctly maintain two production lines for the same competitive intelligence — a fast, named internal track for reps, and a careful, anonymized external track for everything else — and they review the boundary every quarter to catch artifacts that drifted from one track to the other.