When does the executive briefing one-pager fire?

The battlecard trigger map fires the executive one-pager on two signals. Signal one: a new executive enters the buying committee who was not in the original discovery brief — typically because the deal escalated above the original sponsor's authority or because a procurement gate inserted finance or clinical leadership. Signal two: an existing executive in the committee raises a question that escalates the deal outside the AE's working scope — pricing beyond the AE's discount ceiling, multi-year commercial terms, or a clinical risk question the AE is not credentialed to answer. In both cases, the override is logged to the slot-flip and signal log, and a net-new meeting is inserted before the next previously scheduled rep touch. Firing the one-pager without inserting the meeting is the most common failure mode — the exec gets the document, the deal does not get the executive sponsor.

What is on the one-pager — and what is deliberately not on it?

On it: the four-line situation summary (where the deal is, what the buying committee converged on, who the new exec is, what the AE is asking for); three slot-weighted proof points anchored to production data from comparable accounts; the explicit one risk the AE wants the exec to weigh; the decision the AE wants the exec to make at the next meeting and the alternative if the exec is not ready. Not on it: a competitive matrix, a feature comparison grid, trap-setters, objection-handling scripts, pricing tables. Those artifacts exist in the library — comparison matrix, side-by-side, objection handling, pricing/procurement battlecard — and the AE cites them only if asked. The one-pager is a ratification document, not a sales document. Executives who receive a document that reads like sales material disengage; executives who receive a document that reads like an internal recommendation memo read it.

How is the A-slot variant different from the B-slot variant?

The A-slot variant — for executives evaluating Voicify against a horizontal voice-AI platform — leads with platform consolidation risk, governance over a multi-vertical vendor, PMS write-back depth and the cost of integration brittleness, and the typical CFO question of whether vertical-specialist software earns its premium against a generalist platform. The B-slot variant — for executives evaluating Voicify against a dental-pure AI receptionist — leads with after-hours coverage uptime data, booking conversion versus the dental-pure incumbent, clinical safety guardrails (especially relevant to a clinical director new to the deal), and the typical clinical-director question of whether the deeper feature surface introduces operational complexity their staff cannot absorb. Both variants share the same four-section structure; the proof points and the framing question rotate by slot.

Who writes the one-pager — enablement, the AE, or RevOps?

Enablement writes the slot-weighted template and the proof-point bank. The AE writes the four-line situation summary, picks three proof points from the bank for the specific deal, and writes the one-risk paragraph and the decision-asked paragraph. RevOps logs the override firing and confirms the activation cue was matched. The clean split is roughly 70 percent reusable from the template and 30 percent deal-specific. The AE does not write the one-pager from scratch each time — that is what produces inconsistent quality and what makes the artifact unaccountable to the activation log. The AE also does not deploy the template verbatim — that is what makes the document read generic and the executive disengage. The pre-built proof-point bank with deal-specific summary and ask is the operating compromise.

Voicify "Competitor A or B" Dental AI: Executive Briefing One-Pager

Q: What is the Voicify 'Competitor A or B' dental AI executive briefing one-pager?

It is a single-page document the AE hands a newly inserted executive — typically a CFO, chief commercial officer, or clinical director — when that exec drops into a Voicify 'Competitor A or Competitor B' evaluation mid-cycle. The one-pager is slot-weighted: the A-slot variant frames the comparison against a horizontal voice-AI platform and leads with platform consolidation risk, vendor governance, and PMS write-back depth. The B-slot variant frames the comparison against a dental-pure AI receptionist and leads with after-hours coverage uptime, booking conversion, and clinical safety guardrails. The one-pager is not a battlecard. It contains no internal trap-setters or competitive talk tracks. It contains the four data points the new exec needs to ratify the deal direction the buying committee has already converged on, plus the one risk the AE wants the exec to weigh.

A dental AI deal that escalates above its original sponsor — because the CFO got pulled in on pricing, because a chief commercial officer started asking about multi-year terms, because a clinical director is now in the room post-hygienist-objection — has the same problem every late-stage enterprise deal has: a new executive arrives with no context, the buying committee has already converged on a direction, and the AE has roughly one meeting to give the exec what they need to ratify that direction without unwinding the work. The executive briefing one-pager is the artifact the AE hands the new exec. It is slot-weighted — the discovery brief's A-or-B tag determines whether the briefing leads with horizontal-platform consolidation risk or dental-pure feature-surface tradeoffs — and it is fired by the battlecard trigger map on the new-executive signal. This post is the operating spec for that one-pager — what is on it, what is deliberately off it, how the two slot variants diverge, and the failure modes that make the artifact misfire in the field.

TL;DR

One page, four sections, slot-weighted. Situation summary, three proof points from the bank, one risk the AE wants the exec to weigh, and the decision the AE is asking the exec to make. A-slot leads with platform consolidation, governance, PMS write-back depth. B-slot leads with coverage uptime, conversion, clinical safety guardrails. Never a competitive matrix, never trap-setters, never pricing tables — those live in other artifacts and get cited only if asked. The one-pager is a ratification memo, not a sales pitch. Fires on the trigger map's new-exec signal, gets paired with a net-new meeting before the next previously scheduled touch, and is logged so the quarterly refresh can read it.

Why a One-Pager and Not the Full Comparison Matrix

The temptation when an executive drops into a deal late is to send them everything — the comparison matrix, the side-by-side, the pricing battlecard, the pilot results, the integration scoping deck. The reasoning is that the exec needs to get up to speed and more context helps. In practice, more context loses the deal. The exec opens the pack, scans it, sees a sales-shaped document, and forms the impression the deal is being driven by the vendor rather than by their team. The buying committee, who had converged on a direction, now has to defend that direction against an exec who is suddenly skeptical because the package they received reads like marketing.

The one-pager solves this by being deliberately under-scoped. It is a single page. It is structured like an internal recommendation memo, not a sales deck. It assumes the exec will spend ninety seconds with it, not thirty minutes. It cites the deeper artifacts but does not include them. If the exec wants the comparison matrix, the AE has it ready; the AE does not preempt that ask. The discipline of the one-pager is what makes it work: it gives the exec exactly what they need to ratify the committee's direction, and nothing else.

The Four-Section Structure

Every executive one-pager — both slot variants — has the same four sections in the same order. The structure is non-negotiable. The proof points and the framing rotate; the structure does not.

Section one: situation summary. Four lines maximum. Where the deal is in the pipeline, what the buying committee has converged on, who the new exec is and why they were added, what the AE is asking for at the next meeting. This section is the only section that gets read in full by every exec who receives the one-pager. It is also the section AEs most often mis-write — they over-describe the deal history and under-describe the ask. The ask belongs in section one because executives read top-to-bottom and stop when they have what they need.

Section two: three slot-weighted proof points. The AE picks three from the proof-point bank that enablement maintains. The bank is organized by slot and by exec role — CFO proof points, CCO proof points, clinical director proof points, COO proof points. Each proof point is anchored to production data from a comparable account, not to a vendor promise. The proof points are the empirical scaffolding of the recommendation; the exec does not need to ratify them at face value, but they do need to see them.

Section three: the one risk. The AE names the single risk the exec should weigh in deciding whether to ratify. There is always exactly one. Naming zero risks signals the AE is selling; naming three risks signals the AE is hedging. One risk, named honestly, with the AE's recommendation for how the deal is mitigating it, is the section that earns the exec's trust. The risk is slot-specific — for A-slot it is typically integration brittleness or vendor-lock concentration; for B-slot it is typically feature-surface absorption capacity on the practice side.

Section four: the decision asked. One sentence. What decision does the AE want the exec to make at the next meeting, and what is the alternative if the exec is not ready. The alternative is not "we lose the deal." The alternative is the smallest next step that keeps the deal moving while the exec gets more time — a smaller pilot, a sandbox extension, a clinical reference call. Executives who feel the AE has thought about the alternative trust the AE more than executives who feel cornered into a binary.

A-Slot Variant: When the Buyer Is Comparing Voicify to a Horizontal Voice-AI Platform

The A-slot variant of the one-pager fires when the discovery brief tagged the deal as A-slot — the buyer is evaluating Voicify against a horizontal voice-AI platform that treats dental as one vertical of many. The new exec in this deal is typically a CFO who pulled in on commercial terms, a CIO who flagged integration risk, or a chief commercial officer who is consolidating vendor governance across the practice group.

The A-slot proof-point bank leads with platform consolidation risk — what happens to dental performance when the horizontal vendor reallocates engineering toward a different vertical's roadmap. It leads with PMS write-back depth — production data showing the dental-specific integration the horizontal platform does not invest in. It leads with vendor-governance maturity — the audit trail, security posture, and clinical-safety attestation that an enterprise dental group's risk function expects. The framing question the AE expects the exec to ask is whether vertical-specialist software earns its premium against a generalist platform, and the proof points are built to answer that question with production evidence rather than marketing claims.

B-Slot Variant: When the Buyer Is Comparing Voicify to a Dental-Pure AI Receptionist

The B-slot variant fires when the discovery brief tagged the deal as B-slot — the buyer is evaluating Voicify against a dental-pure AI receptionist with a narrower feature surface, a lighter PMS integration depth, and a faster setup wizard. The new exec in this deal is typically a clinical director who got pulled in on operational complexity, a COO who is evaluating staff absorption capacity, or a chief growth officer focused on conversion economics.

The B-slot proof-point bank leads with after-hours coverage uptime — production data from comparable practices showing the answer rate Voicify holds when the dental-pure incumbent's wizard-built coverage gaps appear. It leads with booking conversion — call-to-appointment conversion rate by hour and call type, against the dental-pure baseline. It leads with clinical-safety guardrails — the constraints Voicify enforces on hygienist-adjacent or treatment-coordinator-adjacent calls that a narrower receptionist platform does not enforce. The framing question is whether the deeper feature surface introduces operational complexity the practice cannot absorb, and the proof points are built to show that the absorption work was front-loaded into pilot and is now operationally stable.

What Is Deliberately Not on the One-Pager

A short list of artifacts that exist in the broader library and that the AE does not include in the one-pager. The competitive comparison matrix is not on it; the matrix is for the buying committee, not the exec. The objection-handling card is internal-facing; an exec who receives objection-handling material immediately distrusts the AE. The pricing and procurement battlecard is for the procurement function specifically and a one-pager that includes pricing scope creep gets read as a discount-fishing exercise. The IT integration due-diligence battlecard is for the CIO's technical staff. The migration battlecard is for the project plan conversation. The one-pager points to these artifacts by name and indicates the AE will share them on request. It does not preempt the request.

Failure Modes: Where the Executive One-Pager Misfires

The first failure mode is firing the one-pager without inserting the meeting. The trigger map says the override is a one-pager plus a net-new meeting before the next previously scheduled rep touch. AEs under time pressure send the one-pager as an email attachment, expect the exec to read it, and lose the deal when the exec quietly forms an opinion in the absence of an AE-led conversation. The one-pager is a meeting accelerant, not a meeting substitute. The second failure mode is writing the situation summary too long. Four lines is the budget. AEs who write six paragraphs are writing for themselves, not for the exec. The third failure mode is naming zero risks or three risks — both signal a credibility deficit. Exactly one risk, honestly named, mitigated, and tied to the decision asked. The fourth failure mode is sending the wrong slot variant — the deal was A-slot tagged at discovery, the buyer has been behaving like a B-slot deal for two weeks, the slot tag was never updated in CRM, and the A-slot variant fires for a clinical director who needed the B-slot framing. The quarterly refresh reads slot-flip log entries against one-pager firings to surface this drift; managers reinforce slot-tag hygiene in the forecast call.

The fifth failure mode is the AE writing the one-pager from scratch instead of from the template — which produces inconsistent quality, no measurement surface, and an artifact that is unaccountable to the activation log RevOps maintains. Enablement maintains the template and the proof-point bank; the AE assembles. The cleanest deployments treat the one-pager the way a partner at a consulting firm treats an internal client-facing memo — most of it is reusable structure and pre-vetted evidence, a thin layer of deal-specific framing is added on top, and the partner is accountable for the recommendation, not the boilerplate.

Voicify "Competitor A or Competitor B" in Dental AI: The Executive Briefing One-Pager