Should I mention a mutual connection in a cold email?

Only if the connection would be comfortable with it. Name-dropping someone who barely knows you can backfire. If you do mention them, say exactly how you know them in one clause and move on. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

How do I follow up on an unpaid invoice without damaging the relationship?

Assume a process issue first. Put the facts up top, offer to fix coding or PO problems, and keep the tone operational. Escalate to the original buyer only after AP has had a fair chance. Rage emails get paid last.

Is it okay to send this cold email on LinkedIn instead of email?

Yes if this CTO is actually active there and the thread isn't about long attachments. Keep the LinkedIn version even shorter. Don't paste the full email. One context line and one question is plenty. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

What should I never say in a Pharmaceuticals cold email?

Don't use consumer-startup slang. It's a credibility leak. Calling it 'AI-powered' with no description of the system. Don't threaten, guilt, or bury the amount. Those three mistakes show up constantly in Pharmaceuticals inboxes and they all read as "this was templated."

Can I use aggressive sales language in pharma outreach?

No. Unapproved claims, off-label hints, and fake urgency can create real problems. Be operational: timelines, review status, access, meeting logistics. Save clinical discussion for approved materials and the right role. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

Pharmaceuticals · CTO · After Invoice

Cold Email Template for Pharmaceuticals CTO: After Invoice

Use this cold email template when you're emailing a CTO in Pharmaceuticals (after an invoice). Money is on the table. The relationship is real. Your job is to make payment simple and keep dignity on both sides. Keep the note aligned with Precise. No slogans. It's fine to be a little dry.

Last updated: 2026-09-02 · Reviewed by: Sales Email Template editors

We write templates the way we wrote emails on quota: short, specific, and easy to forward. When we cite research below, it is because the number changes how a buyer reads your note, not to pad the page.

Sources: HubSpot sales email benchmarks; Gong follow-up research

Why does this cold email work for a Pharmaceuticals CTO?

Show you understand their bottleneck in their language.
Speaks to follow-up that ignores MLR, off-label risk, and the fact that 'just a quick claim' isn't quick instead of a generic "value prop."
Fits how a CTO actually reads: 90 words is plenty if the substance is real. Don't pad.
Restate number, due date, invoice ID, and pay path in the first screen.
Lead with an observed trigger, not a compliment about their About page.

When should I send this to a Pharmaceuticals CTO?

Don't follow a cold email the next morning. Give it 4 business days. A polite reminder a few days after due, then a firmer operational note. For this combo, treat "3 days after due date" as the default, then adjust around launch calendars and review boards set speed. you don't. If you're emailing a CTO, 90 words is plenty if the substance is real. Don't pad. After three touches with different value, send a breakup and archive.

What this CTO actually cares about

A CTO in Pharmaceuticals is protecting reliability, security, and engineering time. They look for architecture, failure modes, and whether you'll create toil for their team. Fluff is a ranking signal that you don't know the work. The hook that earns a look is an incident class, a security gap, or a cost line they already hate. The ask should stay at this size: a technical working session or a written teardown, not a 'vision call'. Delete trigger: Calling it 'AI-powered' with no description of the system. an incident class, a security gap, or a cost line they already hate

How Pharmaceuticals changes the note

Pharmaceuticals buyers are commercial, medical, and ops leads who work under review boards and long timelines. Don't invent clinical claims. Don't treat HCPs like a funnel. If you don't know the rules, your email is a liability. A credible proof point in this vertical sounds like: cut review cycles on a leave-behind by catching claims issues before legal saw the tenth draft. Watch the language. Words that land here include MLR, label, access, HCP, congress, promotional review. A thread that ignores follow-up that ignores MLR, off-label risk, and the fact that 'just a quick claim' isn't quick reads like every other vendor bump.

How should I customize this template before I send it?

Replace the pain line with an agency waiting on MLR while the sales team keeps asking 'is it approved yet'.
Keep the tone precise.
Send from a real name. Role accounts get filtered.
Time it for 3 days after due date. A polite reminder a few days after due, then a firmer operational note.
Don't use consumer-startup slang. It's a credibility leak.

What mistakes should I avoid with this after invoice note?

Opening with your company story is how cold email dies.
Don't threaten, guilt, or bury the amount.
Don't use consumer-startup slang. It's a credibility leak.
Calling it 'AI-powered' with no description of the system.

How does this after invoice scenario compare?

Dimension	For this template
Best send window	3 days after due date
Ideal length	90 words is plenty if the substance is real. Don't pad.
Primary ask	a technical working session or a written teardown, not a 'vision call'
Industry metric to cite	time through MLR, access, and compliant engagement rates
Tone	Precise. No slogans. It's fine to be a little dry.
Unlike proposal follow-up	The commercial terms were already accepted. You're in collections-lite, not sales.
Unlike apology	Only apologize if you invoiced wrong. Don't apologize for asking to be paid.

What should I copy and send?

Copy-ready template

Subject

CTO question on after invoice

Body

Hi [First Name],

Saw [trigger] and figured this might be on your plate.

The version of this that matters for commercial, medical, and ops leads who work under review boards and long timelines is cut review cycles on a leave-behind by catching claims issues before legal saw the tenth draft. Teams like [peer example] use [Your Product] to cut review cycles on a leave-behind by catching claims issues before legal saw the tenth draft in [timeframe]. The fit depends on whether follow-up that ignores MLR, off-label risk, and the fact that 'just a quick claim' isn't quick is actually costing you time through MLR.

Get paid or learn the blocker: PO, coding, approval, or dispute.

Wrong person? Point me to whoever owns [pain].

Best,
[Your Name]
[Your Title]
[Your Company]

Questions people ask before they hit send

Don't follow a cold email the next morning. Give it 4 business days. A polite reminder a few days after due, then a firmer operational note. After that, send a breakup note and archive it. A CTO who wants it will answer a clean close more often than a fifth bump.

Related templates

Want a custom draft instead? Try the email generator.