---
title: "Land the central buyer at dental service organizations and multi-site groups | FirstSales"
description: "A rollout-focused cold email playbook for selling into DSOs and multi-location healthcare groups, targeting the central ops buyer instead of individual sites."
canonical: "https://firstsales.io/tutorial/playbook-healthcare-dso-multisite/"
---

[Home](/)/ [Tutorials](/tutorial/)

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

A rollout-focused cold email playbook for selling into DSOs and multi-location healthcare groups, targeting the central ops buyer instead of individual sites.

Tutorials

Playbooks

min read

13 min

steps

8 · Intermediate

8 steps

[01Understand why this buyer is different from a single practice](#step-1)[02Build the list around the central role, not the site level](#step-2)[03Use research to find the rollout signal](#step-3)[04Set campaign goals around evaluation, not immediate purchase](#step-4)[05Write in a rollout voice, not a per-practice voice](#step-5)[06Let AI Autopilot draft with the rollout framing intact](#step-6)[07Design a sequence around the evaluation timeline](#step-7)[08Track meetings, not just replies, and expect a longer cycle](#step-8)

[All tutorials](/tutorial/)

1. ## 01 Understand why this buyer is different from a single practice  
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.
2. ## 02 Build the list around the central role, not the site level  
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.  
![Build the list around the central role, not the site level](/tutorials/app/contacts.webp)
3. ## 03 Use research to find the rollout signal  
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.
4. ## 04 Set campaign goals around evaluation, not immediate purchase  
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.  
![Set campaign goals around evaluation, not immediate purchase](/tutorials/app/kb.webp)
5. ## 05 Write in a rollout voice, not a per-practice voice  
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\]
6. ## 06 Let AI Autopilot draft with the rollout framing intact  
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.
7. ## 07 Design a sequence around the evaluation timeline  
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.  
![Design a sequence around the evaluation timeline](/tutorials/app/c-steps.webp)
8. ## 08 Track meetings, not just replies, and expect a longer cycle  
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.  
![Track meetings, not just replies, and expect a longer cycle](/tutorials/app/c-analytics.webp)

## Pro tips

* 01  
### Lead with site count  
Lead with the site count in your subject line or opening sentence. A central operations buyer skims for scale first, since it tells them in one glance whether your product fits an organization their size.
* 02  
### Don't double up contacts blind  
Do not split your sequence across multiple contacts at the same DSO unless you know the org chart. Emailing two people at once without acknowledging it reads as spray-and-pray to a buyer who is used to a single-threaded vendor relationship.
* 03  
### Track which growth signal wins replies  
Keep a running list of which growth signal (recent acquisition, new ops hire, stated expansion) got the best reply rate, and weight your AI Leads targeting toward that signal in future batches.

## Frequently asked questions

How is targeting a DSO different from targeting an individual dental practice?

The buyer is centralized. Instead of reaching a single practice owner, you are reaching an operations or procurement lead who decides for every site at once, so your ICP and messaging need to describe group-wide fit, not single-location fit.

Should I mention specific site names in the email?

Reference the group's total footprint or a specific expansion detail if research surfaced one, rather than naming individual sites, since the central buyer thinks in terms of the whole organization.

What if the group has grown through acquisition recently?

That is one of the strongest signals for this vertical. A group that just added locations usually has real, current pain around standardizing systems, and referencing that directly in your opener tends to outperform a generic efficiency pitch.

How long should my sequence run for multi-site deals?

Give it more room than a single-practice sequence. Group-level procurement moves slower and often involves more than one stakeholder, so a three to four step sequence with longer delays between steps fits this buyer better than a fast, compressed sequence.

## Playbooks

* [└ Pitch retainer contracts to in-house marketing teams 20 min ](/tutorial/playbook-agency-retainer-pitch/)
* [└ Open cold outreach with a free channel audit 18 min ](/tutorial/playbook-agency-audit-opener/)
* [└ Build white-label partnerships with other agencies 22 min ](/tutorial/playbook-agency-whitelabel-partnerships/)
* [└ Win back churned clients after a results dip or team change 19 min ](/tutorial/playbook-agency-churned-client-winback/)

## Outreach that keeps going after you log off. Leads, emails, follow-ups and replies, handled. 

Connect unlimited mailboxes and let AI agents find leads, write each email and follow up. Or send your own templates in manual mode. From $29/mo.

[Start your $1 trial T](https://app.firstsales.io)[See pricing](/pricing/)

$1 for 3 days · Cancel anytime · No contract

## Install with AI

Your coding agent sets up the FirstSales CLI and skills for you.

Prompt for Claude Code

I'm setting up FirstSales (https://firstsales.io), an AI outbound sales platform: campaigns, contacts, a reply inbox, deliverability and lead signals. Help me get my workspace sending real, good emails end to end, from Claude Code.

Read these first so you know how FirstSales works:
- Developer docs and API: https://developer.firstsales.io
- CLI: https://www.npmjs.com/package/@firstsales.io/cli
- Skills for coding agents: https://github.com/firstsalesio/firstsales-skills (read README.md and GUIDE.md)

Setup
1. Install the CLI: npm install -g @firstsales.io/cli
2. Install the FirstSales skills:
   claude plugin marketplace add firstsalesio/firstsales-skills
   claude plugin install firstsales@firstsales
3. Ask me if I already have a FirstSales account. If not, send me to https://app.firstsales.io to sign up.
4. Ask me to create an API key under Settings → API → API Keys, with only the scopes we need.
   Never ask me to paste the key into this chat. Tell me to run this in my own terminal, so the key stays hidden:
   read -rs FS_KEY && firstsales auth login --api-key "$FS_KEY"; unset FS_KEY
5. Run `firstsales whoami` and tell me which workspace and organisation we are connected to.

Then ask me about my business: what I sell, who I sell to (roles, company size, countries), my best customers, and what I use today for outbound (tools, lists, mailboxes). Walk me through:
1. Teaching FirstSales my business: website, offer, proof points and case studies in the knowledge base, so the AI writes like someone who knows the product.
2. Connecting my sending mailboxes and checking my sending domain: SPF, DKIM, DMARC and warm-up. If anything is unhealthy, tell me the exact DNS record to add.
3. Bringing in contacts: import my CSV or CRM export into a clean list, remove duplicates and bad emails, and block domains I must never email (customers, competitors, my own).
4. Building my first campaign: the right list, senders, steps and timing. Write the sequence with me, show me the drafts, and do not launch until I say yes.
5. Setting up Signals if it fits: find people engaging with LinkedIn posts about topics my buyers care about, and turn them into leads.
6. Inviting my team and giving each person the right access.

Once campaigns run, show me how to work the reply inbox from here: which replies need an answer, draft responses in my voice, and move good conversations into deals. If I use Cal.com, connect it so follow-ups can offer my booking link (not the first email).

Throughout, as you learn about my business, proactively suggest and help create:
- Reply templates for the questions and objections my prospects are likely to raise, based on my product, site and codebase if you can see them.
- Campaign ideas and segments worth testing, with the reason for each.

Safety rules:
- Show every change as a dry run (--dry-run) first and wait for my yes. Never send emails, launch campaigns or delete anything without my yes.
- Tell me before anything that spends credits, and how many.

Be opinionated. If the docs give a sensible default, just use it. Don't make me choose between five options.

[Developer docs ↗](https://developer.firstsales.io)[npm: @firstsales.io/cli ↗](https://www.npmjs.com/package/@firstsales.io/cli)[GitHub: firstsales-skills ↗](https://github.com/firstsalesio/firstsales-skills)