Most Voicify A-or-B dental AI deals do not lose to a competitor — they lose to a missing close date. The buyer is running a 14-day comparison rubric, a 30-day pilot, an IT due-diligence packet, and a procurement workflow the rep does not control. Without a mutual action plan threading those four workstreams into a single timeline, they run in series instead of overlap, the close date slips by 30 to 60 days, and the deal often slot-flips to the competitor whose rep ran the cleaner timeline. The mutual action plan — the MAP — is the artifact that converts a folder of thirty enablement instruments into one sequence reps and buyers can run together, milestone by milestone, against a real close date. It is the only artifact in the Voicify A-or-B cluster that lives on both sides of the table.
TL;DR
Eight milestones. Named owners on each side. Three exit ramps. One close date both sides can defend. The Voicify A-or-B mutual action plan lists eight milestones from disqualifier sweep through master-agreement signature, assigns one named owner per side per milestone (not a role), writes three exit ramps into the document at signature (disqualifier, pilot, slot-flip), and re-baselines on a published trigger list rather than getting torn up. Total elapsed is 60 to 75 days from first qualified meeting to signature when milestones run on schedule, 90 to 120 days when procurement compresses late, and the gap between those two ranges is almost entirely whether the MAP existed at discovery or got bolted on at pilot close. The MAP is the only artifact in the cluster the forecast call scorecard treats as primary input.
What a Mutual Action Plan Is — And Is Not
A mutual action plan is a single shared document, owned jointly by the buyer's lead and the vendor's account executive, that lists every milestone between qualified discovery and master-agreement signature, the named owner on each side per milestone, the date each milestone has to land for the close date to hold, and the exit ramps that retire or re-baseline the plan when reality changes. It is not a project plan. It is not a Gantt chart. It is not the vendor's internal forecast view dressed up for the buyer. It is a working contract about the deal lifecycle that both sides re-read before every meeting and that the forecast call scorecard reads as its primary input.
The MAP exists because the Voicify A-or-B comparison runs four parallel workstreams the rep does not control. The buyer rubric runs on the office manager's calendar. The IT integration due-diligence runs on the IT lead's calendar. The 30-day pilot runs on the practice's clinical calendar. Procurement and legal run on their own calendar. Without a MAP, these queue in series and the close slips. With a MAP, they overlap on a published timeline that both sides hold their owners to.
The Eight Milestones in Default Order
Eight milestones is the default count. Most deals fit this shape; outliers either compress to six (no IT due diligence required at single-location dental practices) or expand to ten (multi-DSO with two procurement teams). The default eight are below.
| # | Milestone | Default duration | Primary source artifact |
|---|---|---|---|
| 1 | Disqualifier sweep complete across short list | 3 days | Buyer rubric — five disqualifiers |
| 2 | Eight-scenario live demo recorded against buyer scenarios | 4 days | Demo script |
| 3 | IT due-diligence packet delivered and reviewed | Parallel to #2 | IT integration due-diligence battlecard |
| 4 | Weighted rubric scored independently across stakeholders | 4 days | Comparison rubric |
| 5 | Pilot terms signed (vendor selected) | 2 days | Slot decision instrument |
| 6 | 30-day pilot complete with scorecard read-out | 30 days | Pilot scorecard |
| 7 | Procurement and legal review of master agreement | 10 to 15 days | Pricing & procurement battlecard |
| 8 | Master agreement signed | 2 days | Sales-to-CSM handoff |
Total elapsed at default cadence is 60 to 75 days from first qualified meeting to signature. Deals that miss a MAP at the discovery call routinely run 90 to 120 days because milestones one through three queue serially instead of overlapping, and procurement compresses into the final window with no time to pre-stage redline cycles.
Named Owners on Each Side
Every milestone has a named owner on each side, not a role. Role-only ownership produces the same decay pattern as the battlecard library without governance: every milestone is everyone's job and therefore no one's. Below is the default owner map. Names go into the actual MAP document at signature.
- Milestone 1 — disqualifier sweep. Buyer: office manager or DSO ops director. Vendor: AE.
- Milestone 2 — live demo. Buyer: office manager (scoring). Vendor: solutions engineer + AE.
- Milestone 3 — IT due diligence. Buyer: IT lead or DSO ops director. Vendor: security or trust lead.
- Milestone 4 — weighted rubric scoring. Buyer: office manager + billing lead + (where applicable) DSO ops director, independently. Vendor: AE (does not score).
- Milestone 5 — pilot terms signed. Buyer: owner-dentist or operations VP. Vendor: AE.
- Milestone 6 — pilot complete. Buyer: office manager (daily) + owner-dentist (read-out). Vendor: CSM + AE.
- Milestone 7 — procurement & legal review. Buyer: procurement or legal lead. Vendor: AE + deal desk.
- Milestone 8 — signature. Buyer: owner-dentist, operations VP, or DSO finance. Vendor: AE + deal desk.
Owners get republished if anyone leaves a role mid-deal. The MAP gets re-signed when ownership shifts on the buyer side — this is a small ceremony with a real purpose: the new owner reads the milestones their predecessor accepted and confirms the close date holds.
The Three Exit Ramps Written at Signature
Three exit ramps go into the MAP at signature, not added when reality breaks. Pre-writing the ramps is what keeps the document a living working contract instead of a negotiated artifact reps avoid showing the buyer when the deal turns.
- Disqualifier exit. If the vendor fails any of the five buyer-rubric disqualifiers during diligence — no BAA, no PMS write-back, no production references, no SOC 2 Type 2, no pilot exit clause — the deal exits and the MAP retires with a logged reason. No salvage attempt. The disqualifier exit is what separates a serious MAP from a wishlist.
- Pilot exit. The 30 to 60-day pilot exit clause is referenced in the buyer rubric but it lives inside the MAP itself, with the exit notice owner and the procedure for returning to short list named explicitly.
- Slot-flip exit. If the slot-decision instrument flips the vendor from primary to fallback or out, the MAP gets re-baselined with a new close date and new milestone owners — it does not get torn up. Preserving the slot history in the MAP is what lets the win-loss debrief read original close-date forecast against actual.
Re-Baseline Triggers — When the MAP Gets Updated, Not Replaced
A MAP that gets torn up and rewritten loses its memory. The default rule is re-baseline, not rewrite. Three triggers fire a re-baseline:
- Any milestone slips by more than five business days. Two-day slips happen and the original date holds with a noted variance. Five-day slips compound into close-date risk and the close date gets republished on the re-baselined MAP.
- Any change in a named buyer-side owner. When the office manager rotates or the IT lead changes mid-deal, the new owner re-signs the MAP — and the close date often re-baselines by one to two weeks in the process, because the new owner needs time to read into milestones their predecessor accepted.
- Any material change in contract scope or per-location count. A practice that adds two locations between pilot and signature changes both the pricing structure and the procurement review timeline; the MAP re-baselines to absorb the longer milestone seven window.
Re-baselined MAPs preserve every milestone date history below the current row. Forecast call scorecards read the history, not just the current line — repeat re-baselines on the same milestone are signal worth surfacing to the manager coaching cadence.
How the MAP Connects to the Existing Cluster
The MAP is the timeline layer. It does not replace any other artifact; it sequences them. The discovery brief feeds the milestone-one qualified-meeting threshold. The objection handling map runs throughout. The CSM B-slot defense activates after milestone eight if the deal closed in fallback slot. The pricing and procurement battlecard drives milestone seven. The forecast call scorecard reads the MAP as its primary input — a deal forecast without a MAP-anchored close date is a guess, and the forecast review dispositions it as such.
The MAP is also the artifact procurement reads when the rep asks for the close date to hold and the artifact the office manager points to when the practice owner asks why the rollout has not started. It is the only document in the cluster that lives on both sides of the table — which is why the discipline of pre-writing exit ramps, naming owners on both sides, and re-baselining instead of rewriting is what determines whether the MAP is competitive infrastructure or theater.