Land the central buyer at dental service organizations and multi-site groups

Dental service organizations, multi-site medical groups, and physical therapy chains buy differently than a solo practice. Decisions do not get made site by site. They get made once, centrally, by an operations, IT, or procurement lead who then rolls the decision out across every location. Your entire pitch has to speak to that person's problem: rolling out one system, one vendor relationship, and one set of standards across many sites, instead of dealing with a different tool at every location.

This is a business to business play aimed squarely at corporate and operations staff, never at clinical staff or patients. Define your ICP around the number of sites (5+, 20+, whatever your product's sweet spot is), the vertical (DSO, multi-site optometry, multi-site urgent care, physical therapy chains), and the specific centralization problem you solve, such as inconsistent scheduling tools across sites or fragmented billing workflows that make consolidated reporting a mess.

In AI Leads, describe your target as the central buyer, not the individual practice. Something like "DSOs with 8 or more locations where a VP of Operations or Director of Practice Operations owns vendor decisions for the group" will surface a much sharper list than "dental practices," which would return individual site contacts who cannot make a group-wide decision. The quality funnel filters weak matches before they cost credits, and for this vertical that matters more than usual, since a wrongly sized DSO can look similar to a loose collection of independent practices on paper.

Pull separate lists for different DSO sizes if your product's fit changes with scale. A 6-location group and a 60-location group have different procurement processes, different budget authority, and often a different title entirely making the decision.

It is worth mapping which titles typically own this decision at each size band before you start sourcing. Smaller DSOs often route vendor decisions through a founder or a single VP wearing several hats, while larger groups tend to have a dedicated procurement or IT function that a new vendor has to clear before an operations lead will even take a call, and knowing which pattern you are targeting changes how you frame the first email.

Automatic prospect research runs before any draft is written, and the transparency view shows you what it found on each contact: company facts, role, and signals. For DSOs and multi-site groups, look specifically for growth or consolidation signals: recent acquisitions of additional locations, a new operations hire, or a stated expansion plan. A DSO that just added five locations through acquisition has an acute, current problem with standardizing systems across a newly larger footprint, and that is a much stronger opener than a generic pitch about efficiency.

Group growth signals are also useful for sequencing your outreach. A DSO that acquired new locations within the last two quarters is more likely to still be mid-integration and actively evaluating systems, while a group that has been stable at the same site count for years may need a different trigger, such as a leadership change, before a standardization pitch lands with the same urgency.

Create your campaign and set the goal to book a meeting rather than drive an immediate signup. Multi-site deals move through evaluation, pilot, and rollout stages, so your first email should aim for a conversation, not a close. In Campaign guidance, use Describe to frame the offer as a standardization or rollout solution, and use Teach to give the AI language around multi-site deployment, group-wide reporting, and consistency across locations, since those are the concepts this buyer actually cares about.

If your product handles anything that touches patient data across sites, be explicit in your Teach notes about BAA-readiness at the organizational level, since a central buyer evaluating a vendor for the whole group will need a single, group-wide agreement rather than one per site.

Give the AI enough detail in Teach that it can distinguish between a per-site rollout timeline and an organization-wide agreement, since the two are different asks with different owners. A draft that pitches a full rollout before the group has agreed to a pilot at even one site will move faster than a cautious central buyer wants to move, and that mismatch is one of the more common ways multi-site campaigns stall after a promising first reply.

Teach the AI a tone built for an operations audience: direct, numbers-oriented, and framed around consistency across locations rather than any single site's problem. Paste real emails if you have them, or write two or three samples. This buyer reads dozens of vendor pitches a month and filters hard for anyone who clearly does not understand multi-site operations.

Sample opener for a scheduling or billing standardization tool:

Subject: standardizing scheduling across [N] locations

Hi [First Name], noticed [Company] has grown to [N] locations, [detail from research, e.g. after the recent acquisition]. Most groups that size end up running a different scheduling setup at each site, which makes group-wide reporting a headache. We help DSOs run one system across every location instead. Open to a short call to see if it fits how [Company] is structured?

[Your name]

AI Autopilot writes per-contact drafts using the research pulled in step 3, and every draft passes quality gates for format, personalization, and claim checks before sending. Review the first batch closely to confirm drafts stay in the operations lane: site counts, standardization, and rollout language, not clinical claims and not patient-facing language. Multi-site drafts should reference the group's scale and structure specifically, since a draft that reads like it was written for a single practice will undercut your positioning with this buyer immediately.

Set up a multi-step sequence with delays between steps, and let it stop automatically on reply. Give this sequence more room than a single-practice campaign, since group decisions take longer and often involve more than one stakeholder. A useful pattern: step one introduces the standardization angle, step two shares a specific detail about how a multi-site rollout typically works (timeline, what changes for site staff, what does not), and step three is a direct, low-pressure check on timing, since procurement cycles at this level often run on a schedule the prospect controls, not you.

The unified inbox surfaces replies, and AI reply handling responds to the actual content of what the group asked, which at this level is often a scoping question (how many locations does the product support, what does onboarding look like across sites) rather than a simple yes or no. Bounce handling auto-suppresses invalid addresses as you scale the list.

Check analytics for opens, replies, and meetings per campaign, and per step. Standard B2B reply rates run 2 to 5 percent, with meeting rates around 0.5 to 1.5 percent, but for multi-site deals weigh meetings booked more heavily than raw reply count, since a single meeting with the right central buyer can be worth more than a dozen replies from individual site contacts who cannot make the decision.

Give a multi-site campaign at least six to eight weeks before drawing conclusions. Group decisions frequently stall for reasons that have nothing to do with your message, such as a budget cycle or an unrelated internal project, and a campaign that looks flat in week two can still produce meetings in week six once the timing on the buyer's side lines up.