Playbooks

Outbound to healthcare technology buyers: a playbook

A playbook for cold email to healthcare technology buyers: find the operations owner, use one sourced reason to write, and keep outreach compliant.

This playbook works from one assumption: a healthcare technology deal passes through reviews before anyone signs. It is a working assumption, not a finding. The first email cannot close anything. Its job is to get a short conversation with the person who owns the process your product touches.

Public sources give us no sales-cycle length for healthcare technology and no reply rate for healthcare buyers. This guide leaves those numbers out rather than guess. Where it has no fact to offer, it says less and points you to your own data.

Who buys

We cannot give you a verified profile of who buys healthcare technology. A claim like "the CIO signs" or "clinical leaders hold the budget" would be a guess, and a guess does not belong in a playbook.

Your closed deals are a better source than any generic profile. Outlevo can import past deals from a CSV or your CRM and run a win/loss analysis that proposes ICP hypotheses [[1]](#sources). What it reads depends on where your deals live:

  • HubSpot: companies, deals and owners. Deal fields include pipeline, stage, amount and closed-lost reason [[2]](#sources).
  • Salesforce: accounts, opportunities and users. This integration is a pilot that Outlevo installs with you, and there is no AppExchange listing [[3]](#sources).
  • CSV: companies and won or lost deals, up to 200,000 rows [[4]](#sources).

Read the output with its limits in mind. Win/loss analysis counts companies, not deals. Fewer than 10 won companies is labeled very low confidence [[5]](#sources). If you have sold to only a handful of healthcare organizations, treat what the analysis says as a lead to test, not a finding.

Segments proposed by the analysis stay labeled experimental until a person approves them [[5]](#sources). Outlevo also asks which countries you sell into and never proposes markets [[5]](#sources). Choose your markets yourself before you build any list.

Roles to reach

The working hypothesis in this playbook is the operations owner: the person who runs the process your product changes. That is a hypothesis, not a finding. Check it against your won deals before you build a list around it.

To test it, look at who was on the deals you won. HubSpot contact import is optional. It brings in email, name, job title and email opt-out, and an admin must turn it on with a stated purpose [[2]](#sources). If the titles on your wins cluster around one function, write to that function. If they do not, your hypothesis was wrong, and it is better to learn that before sending.

When you need contacts at accounts you have already qualified, contact discovery costs 4 credits and volume contact discovery costs 2 credits [[6]](#sources). Run discovery after you have settled on the role, not before.

If the person you need is a security reviewer rather than an operations owner, the approach differs. See Cold email to CISOs.

Triggers to watch

No published list of healthcare buying triggers is available to us, so none is offered here. What you can do is watch signals tied to your own accounts. These are the ones Outlevo supports:

  • Website visits. Add one script to your site and Outlevo shows which companies visit, which pages they read and whether they fit your ICP. It looks up the organization behind a visitor's network and never identifies a person or sets a cookie. Browsers that send Do Not Track or Global Privacy Control send nothing [[7]](#sources). The cost is 1 credit per company identified per day [[7]](#sources).
  • Competitor changes. Competitor tracking covers quoted facts from competitors' public pages, changes, win/loss by competitor and competitor signals on accounts [[8]](#sources).
  • Your own closed-lost reasons. The HubSpot deal field for closed-lost reason is one input to win/loss analysis [[2]](#sources). A pattern in why you lost can point to the reason to write next time.
  • Signal checks. A signal check costs 1 credit and a person signal costs 1 credit [[6]](#sources).

A signal is a reason to look at an account. It is not yet a reason to email. Write only when you can state one observation, name where you saw it and give its date.

Build one narrow, sourced reason to talk

Aim for a specific, checkable line: what you noticed, where, and why it relates to what you sell.

Outlevo's Readiness Card follows a similar rule. Each qualified account gets one, with fit, intent and data quality scores, and it needs at least three observations that each carry a source and a date [[9]](#sources). Facts read from a website are kept only when their quote is found on the page. Guesses are labeled as hypotheses, never presented as findings [[9]](#sources).

Borrow the habit even if you write by hand:

  1. Pick one observation you can point to on a public page.
  2. Note the page and the date you read it.
  3. Say in the email what you saw, in the same words the page uses.
  4. If you are inferring something, say "I'm guessing" or leave it out.

The free ICP assessment shows this labeling on your own site. It reads up to 5 public pages and returns facts labeled as verified observations or AI inferences, plus up to 5 experimental segment hypotheses [[10]](#sources).

Set a realistic expectation for replies

Across industries, 0.45% of emails get a reply, according to Belkins' cold email response rates page, checked October 22, 2026 [[11]](#sources). The nearest industry figure there is Legal Services at 0.56–0.60%, and that is not healthcare [[12]](#sources).

We have no healthcare figure, so treat the cross-industry number as a benchmark, not a minimum, and measure your own. With a long cycle, one reply is the start of a process, not a result. Count a reply from the right role as the win, and judge the campaign by who answered, not by how many.

Rules for the email itself

Check the rules that apply to each recipient. This is not legal advice. Have counsel confirm your setup.

What the primary sources say, each checked October 22, 2026:

  • The FTC's CAN-SPAM guide for business says: "The law makes no exception for business-to-business email." [[13]](#sources)
  • The UK ICO's guide to electronic mail marketing says: "You can email or text any corporate body (a company, Scottish partnership, limited liability partnership or government body)." [[14]](#sources)
  • GDPR Article 6(1)(f) covers "processing is necessary for the purposes of the legitimate interests pursued by the controller or by a third party". [[15]](#sources)
  • Recital 47 adds: "The processing of personal data for direct marketing purposes may be regarded as carried out for a legitimate interest." [[16]](#sources)
  • Google's sender guidelines say: "Marketing messages and subscribed messages must support one-click unsubscribe, and include a clearly visible unsubscribe link in the message body." [[17]](#sources)
  • Yahoo's sender best practices say: "Honor unsubscribes within 2 days" [[18]](#sources)

The practical result is that every first email needs a working opt-out and a process to honor it. Build both before the first send.

Sending setup

Before a campaign sends through Smartlead, every mailbox must be connected and warmed up, and its domain must have SPF, DKIM and DMARC checked in the last 7 days [[19]](#sources).

If you use managed mailboxes, a new one sends nothing until it is warm: at least 14 days, usually about 3 weeks [[20]](#sources). Plan for that wait before your first healthcare campaign. Builder includes 1 domain and 2 mailboxes, and Growth includes 2 domains and 4 mailboxes [[20]](#sources). For background, see deliverability.

Verify addresses before sending. Email verification costs 1 credit in Outlevo [[6]](#sources). If you compare standalone verifiers, see ZeroBounce pricing, plans and integrations.

Keep approvals and records

Reviewers on the buyer's side may ask how you handle contact data, and you may ask the same of your own tools. These are the facts Outlevo states:

  • Nothing is sent outside a policy that a person approved. Policies set who can be contacted, on which channels, how often and with what budget [[21]](#sources).
  • Every external action is checked against the approved policy before it runs, and recorded in a ledger [[21]](#sources).
  • Kill switches pause a campaign, a channel or the whole workspace at once [[21]](#sources).
  • Every customer table is protected by row-level security, and personal data such as email addresses is encrypted at the field level [[22]](#sources).
  • Staff support access is time-limited and shown in your activity feed, with the reason and the number of changes made [[22]](#sources).

The Security page has the full statement. For the approval model, see How Outlevo works.

Sample first email (example)

Example only: written for this playbook, not sent to anyone.

Subject: Question about [process your product touches]
Hi [First name],
I read on [page name] that [quote from the page, in the page's own words]. I'm writing because we build [one-line description of your product] for teams that run [that process].
I don't know whether this is a priority for you, and I'm not assuming it is. If it is, I can send a one-page summary of how [specific part of your product] fits that process, including points a compliance reviewer may ask about. If it isn't, tell me and I'll stop.
Would a short call next month be useful, or would you prefer the summary first?
[Sender name]
[Company name], [postal address]
If you'd rather not hear from me, reply "no" or use this link: [unsubscribe link]

Why it is built this way:

  • It opens with one quoted observation and names the page. The reader can check it in seconds.
  • It states no result, customer or statistic. Anything like that must come from your own sourced facts.
  • It offers a document first, because the reader may need to pass the idea to others.
  • It carries a clear opt-out, in line with the rules above.

After the first email

Plan the follow-up before you send. Consider a sequence with a few short steps, each adding one new fact, rather than repeating the first message.

If you add LinkedIn, Outlevo sends a connection invitation with a short note of at most 300 characters, then one message after the person accepts. A reply stops that lead's emails [[23]](#sources). Automatic LinkedIn sending comes with Growth and Managed, or with a LinkedIn seat on Builder. Otherwise the invitations and messages are drafted for you to send by hand [[23]](#sources).

When someone replies with interest, Outlevo can answer with your Calendly link, with their name and email filled in. On autopilot the answer goes at once. Otherwise it waits in Replies for you to send [[24]](#sources). Cal.com works the same way [[25]](#sources).

Next step

Before you write to anyone, find out what your own site says about who you serve. Run the free ICP assessment on your public pages. Then compare its segment hypotheses with your won deals, and pick one role and one reason to write.

Sources

  1. Release 2026-10-19
  2. HubSpot integration
  3. Salesforce integration
  4. CSV and Excel integration
  5. ICP from evidence
  6. Outlevo pricing
  7. Website visitors integration
  8. Release 2026-10-19
  9. Readiness Cards
  10. Free ICP assessment
  11. Belkins, cold email response rates (2026)
  12. Belkins, cold email response rates (2026): Legal Services in the 0.56–0.60% range
  13. FTC: CAN-SPAM Act compliance guide for business
  14. ICO: Electronic mail marketing (PECR)
  15. GDPR Article 6(1)(f): lawfulness of processing
  16. GDPR Recital 47: legitimate interests of the controller
  17. Google: Email sender guidelines
  18. Yahoo: Sender best practices
  19. Smartlead integration
  20. Managed mailboxes integration
  21. How Outlevo works
  22. Security
  23. LinkedIn integration
  24. Calendly integration
  25. Cal.com integration

Related

See what Outlevo finds on your own website

Free, no sign-up, about a minute.