All sales email templates

    By buyer

    Multi-threading email templates for a second stakeholder

    Single-threaded deals stall when your one contact goes quiet, changes roles or loses the internal argument. Most B2B purchases involve several people, and the ones you have not met can still say no.

    Quick answer

    Multi-threading means building relationships with more than one person in an account, so the deal does not depend on a single contact. Write to the second stakeholder about their own priority, reference your existing contact only with permission, and ask for a short conversation.

    The second stakeholder does not care about your relationship with their colleague. They care about their own part of the problem, so each email below starts there.

    How to use these templates

    Every {{placeholder}} marks something you must research or write yourself. Replace all of them before you send, and if you cannot fill one with something true and specific, pick a different template.

    The names mean the same thing on every page: {{first_name}} and {{company}} are always the prospect and their business, {{your_name}}, {{your_company}} and {{your_phone}} are always you, and {{their_phone}} is the number you called them on.

    Each email ends with {{signature}} and {{opt_out}}. {{signature}} is your full name, role, company, website and phone number. {{opt_out}} is one plain line. On a cold email: If this isn't relevant, reply "no thanks" and I won't contact you again. In an ongoing conversation it can be quieter: Prefer not to hear from me? Reply "unsubscribe". Keep both in every commercial email, including short follow-ups.

    Map the account before you write

    List who is likely to be involved: the person who feels the problem, the person who owns the budget, the people who must approve it (often finance, IT or legal) and the people whose work changes. Ask your champion directly: 'Who else will want a say in this, and what will they care about?'

    Frameworks such as MEDDIC, which originated at PTC in the 1990s with Jack Napoli and Dick Dunkel, make this explicit with an economic buyer and a champion. Our qualification frameworks guide compares the main ones.

    • Economic buyer: who signs and what outcome they are measured on.
    • Technical or risk approver: what they need to say yes.
    • Day-to-day users: what changes for them.

    Always ask your champion first

    Mentioning a colleague by name without their agreement can embarrass your champion and damage the deal. Ask first, and offer to write the email so they can see what you will say. If they would rather introduce you, use the forwardable introduction.

    The templates

    Each template has subject lines, the body with placeholders, when to use it, why it works, three variants, common mistakes and a compliance note.

    The champion-referenced email

    Subject line options

    • {{champion_name}} suggested we speak
    • {{project_name}} and {{their_area}}
    • {{champion_name}} and {{topic}}

    Email

    Hi {{first_name}}, {{champion_name}} and I have been talking about {{project_name}}, and they suggested I reach out to you, as {{their_area}} would be affected. From what {{champion_name}} said, your main concern is likely to be {{their_likely_concern}}. I'd rather hear it from you directly than guess. Could we take 20 minutes on {{day}}? I'll come with answers to {{specific_question_they_care_about}}. {{signature}} {{opt_out}}

    When to use it

    When your champion has agreed you can contact a colleague and mention them by name.

    Why it works

    It explains why you are writing, respects their role and puts their concern first. Offering to answer their specific question gives them a reason to take the meeting that is about their job, not your deal.

    Variants

    Short

    Hi {{first_name}}, {{champion_name}} suggested we talk about how {{project_name}} affects {{their_area}}. 20 minutes {{day}}? {{signature}} {{opt_out}}

    Formal

    Dear {{first_name}}, {{champion_name}} suggested I contact you regarding {{project_name}}, given its impact on {{their_area}}. I understand {{their_likely_concern}} may be a key consideration, and I would value your perspective. Would you be available for a short conversation on {{day}}? Kind regards, {{signature}} {{opt_out}}

    Aussie-direct

    Hi {{first_name}}, {{champion_name}} reckoned I should talk to you, since {{project_name}} lands on {{their_area}}. Sounds like {{their_likely_concern}} is the big one for you. Rather than guess, keen to hear it straight. 20 minutes {{day}}? Cheers, {{signature}} {{opt_out}}

    Common mistakes

    • Mentioning the champion without asking them.
    • Re-pitching the whole product instead of addressing their concern.

    Compliance note

    Make sure the second stakeholder's address is a published work address or was given to you by your champion with their agreement, and that the message relates to their role.

    The adjacent stakeholder email

    Subject line options

    • {{their_team}} and {{project_name}}
    • question for {{their_team}}
    • {{topic}} from the {{their_area}} side

    Email

    Hi {{first_name}}, We're in early conversations with {{company}} about {{topic}}. When this kind of project reaches {{their_team}}, the question that usually comes up is {{common_question}}. I'd like to make sure we're answering it early rather than late. Is that the right question, or is there a bigger one from your side? {{signature}} {{opt_out}}

    When to use it

    When you need to reach a team that will be affected, such as IT, finance or operations, and your champion is happy for you to contact them but would rather not be named.

    Why it works

    It frames the email as reducing risk for their team, not selling to them. Asking whether you have the right question invites them to set the agenda, which is a strong position for an approver.

    Variants

    Short

    Hi {{first_name}}, We're talking with {{company}} about {{topic}}. Is {{common_question}} the main question from {{their_team}}? {{signature}} {{opt_out}}

    Formal

    Dear {{first_name}}, {{your_company}} is in discussions with {{company}} regarding {{topic}}. In similar projects, {{their_team}} typically raises {{common_question}}, and I would like to address this at an early stage. Could you advise whether this is the key consideration, or whether there are others? Kind regards, {{signature}} {{opt_out}}

    Aussie-direct

    Hi {{first_name}}, We're chatting with {{company}} about {{topic}}. Usually when it gets to {{their_team}}, the big question is {{common_question}}. Keen to get ahead of it. Is that the right one, or is there something bigger? Cheers, {{signature}} {{opt_out}}

    Common mistakes

    • Implying the deal is further along than it is.
    • Asking them to champion the project.

    Compliance note

    Do not imply an existing customer relationship that does not exist. Accurate identification covers what you say about who you are and why you are writing.

    The executive sponsor note

    Subject line options

    • {{project_name}}: one page for {{first_name}}
    • {{outcome}} at {{company}}
    • your input on {{project_name}}

    Email

    Hi {{first_name}}, {{champion_name}} is leading a review of {{topic}}, and I'm supporting them from {{your_company}}. In one line: the aim is {{outcome}} by {{date}}, and the decision your team will face is {{decision_needed}}. Before it reaches you formally, is there anything you'd want us to show? A 15-minute call would let us build the case around your priorities. {{signature}} {{opt_out}}

    When to use it

    When the deal needs a senior sponsor, and your champion agrees it is helpful for you to write to them before a formal proposal.

    Why it works

    Executives want the outcome, the decision and the timing in seconds. Asking what they would want to see positions you as making their decision easier, and it brings their priorities into the proposal early.

    Variants

    Short

    Hi {{first_name}}, {{champion_name}} is reviewing {{topic}}; aim is {{outcome}} by {{date}}. Anything you'd want us to show? {{signature}} {{opt_out}}

    Formal

    Dear {{first_name}}, I am supporting {{champion_name}} on a review of {{topic}}, with the objective of {{outcome}} by {{date}}. The decision required will be {{decision_needed}}. I would welcome any guidance on what you would wish to see addressed. Kind regards, {{signature}} {{opt_out}}

    Aussie-direct

    Hi {{first_name}}, {{champion_name}}'s looking at {{topic}} and we're helping out. The goal is {{outcome}} by {{date}}. Before it lands on your desk, anything you'd want covered? Happy to grab 15 minutes. Cheers, {{signature}} {{opt_out}}

    Common mistakes

    • Going over the champion's head without telling them.
    • Sending the full proposal unprompted.

    Compliance note

    Executive assistants often manage these inboxes. Be clear about who you are and why you are writing, and respect any request to route through someone else.

    Spam Act checklist for every template

    Australian B2B email is legal and regulated by the Spam Act 2003. Before you send any template on this page, check these four things.

    Australian cold calling and Spam Act rules
    • Consent. You need express consent (they agreed) or inferred consent. For B2B, consent can be inferred where a work address is conspicuously published, the message is relevant to the person's role, and there is no statement that they do not want unsolicited messages.
    • Identification. Every message clearly identifies you and your business, with contact details that stay accurate for at least 30 days after you send it.
    • Unsubscribe. Every commercial message includes a working opt-out, which must be actioned within 5 working days and keep working for at least 30 days after sending.
    • No harvested lists. Do not use address-harvesting software or lists built with it. A bought list does not come with consent.

    Calls in the same cadence follow different rules: wash Australian numbers against the Do Not Call Register and call within permitted hours. New Zealand and Singapore recipients are covered by their own laws, summarised on the template library hub. This is general information, not legal advice. AU, NZ and Singapore rules

    FAQ

    Multi-threading to a second stakeholder: questions

    Practical answers from SDR managers who run outbound every day.

    Still have questions?

    Book a 30-minute call

    Building relationships with several people in the same account, so the deal does not depend on one contact. It protects deals from champion changes and internal objections.

    Enough to cover the people who feel the problem, approve the spend and must sign off on risk. For most B2B deals that is three to five people, not the whole org chart.

    Yes. Ask permission to mention them, and offer to share the email first. Surprising your champion can cost you the deal.

    The second stakeholder's own priority or concern, not your relationship with their colleague. Lead with their part of the problem.

    As early as the first discovery call, by asking who else will be involved. Waiting until the proposal stage leaves new stakeholders with objections and little time.

    Yes, when you have a published work address or one given to you with their agreement, and the email relates to their role. This is general information, not legal advice.

    Want Australian SDRs to run your outreach?

    Book a 30-minute call. We will map your market and buyers and show you what a phone-first campaign would book.

    Starting at $7,000 a month. Exact fee quoted after a 30-minute call.