.svg)
.svg)
.svg)
A sample email to a client for new business has one job: make a relevant buyer recognize a problem that already matters to them, then give them a low-friction reason to reply. Not a brochure. Not a capability list. One argument, one proof point, one small next step.
Below are 15 anonymized emails from real outbound campaigns I've run, across three programs that produced 92 first meetings in three months, plus two more templates and the exact structure behind them, so you can write your own. To be precise about that number: 92 completed intro calls, from cold email to roughly 6,000 unique prospects, over three months. The wording was one part of that result; targeting, deliverability, sequencing, and follow-up shaped it too. Copy the structure, not the specifics, and send.
I've spent 15 years in lead generation, sales, and outreach. The campaign examples and principles here come from outreach I actually run, not templates I found, which is also why none of it reads like the generic samples online.
The Short Answer: What a New-Business Email Must Do
A sample email to client for new business works when the first screen is about the reader's problem, not about you. Build every email on six parts, in order:
- Subject — a real problem, tension, number, or contrast (under ~50 characters).
- Opening — start at the problem; skip "hope you're well" unless the context earns it.
- Problem — one recognizable operational or commercial friction. Specific beats dramatic.
- Consequence — what that friction costs: time, money, roadmap capacity, risk, missed growth.
- Mechanism + proof — how you fix it, in plain English, with one before-and-after or operating fact.
- CTA — one small next step tied to the problem. "Worth comparing?" beats "Can I show you our platform?"
That shape is the whole template. Everything below is how to fill it well, plus the 15 real examples, and two more built on the same framework, you can lift.
- Fix the offer and the buyer. Decide exactly what you can sell, to whom, and in what scope, and separate what you can prove from what is only possible. One email speaks to one buying role, not to a whole industry.
- Map the before and the after. Write down the friction the buyer lives with today (where work stalls, what is slow, costly, or risky), then the outcome they get once it is solved. Put both in language they would actually use.
- Pick one problem and its proof. List the strongest problem statements, match each to one credible proof point and one consequence, and choose a single pain for this email. One email, one argument.
- Write to the six-part skeleton. Subject, problem, consequence, mechanism and proof, then one small CTA. Draft it fast, then cut anything that does not support the argument.
- Run two passes. The credibility pass: can every number, comparison, and claim be defended? If the evidence is weak, soften the claim. The human pass: read it aloud, strip corporate language, and make the CTA sound like something a person would actually ask.
- Send, learn, revise. Judge the copy on enough volume, track positive replies and meetings rather than opens alone, and change one variable at a time.
15 Sample Emails to Clients for New Business
Every sample email to a client for new business below is an anonymized version of one used in a real campaign, company names, client names, and links removed, the argument and structure intact. They're grouped by the kind of service being sold, because the problem you lead with changes with the buyer. Each one isolates a single problem and earns the reply on that alone. Copy the structure, not the wording: the argument only works if the problem you open with is one your particular buyer already recognizes. The same structure holds whether you sell a product or a service.
Marketing & Branding Outreach (42 Meetings in 3 Months, India)
Each email isolates one market-facing brand problem and ties it to a commercial consequence.
Email 1 · Consistency Gap
Subject: Is your brand telling two different stories?
Hi {{FirstName}},
When customers meet your brand online, on packaging, and in retail, do they recognize the same company, or three different versions of it?
One consumer brand we worked with had exactly that problem. The product was consistent; the identity was not.
We built one system across logo, packaging, and visual guidelines so every touchpoint reinforced the same story.
If consistency across channels is making the brand harder to recognize, would a quick conversation next week be useful?
Best, {{Sender}}
Why it works: opens at a problem the reader can picture in seconds, and the proof is a before-and-after state, not an adjective.
Email 2 · Message Clarity
Subject: Does your brand actually say what it means?
Hi {{FirstName}},
A strong product can still lose if the story around it is wrong.
One personal-care brand we worked with was positioned around a functional benefit, while the real reason customers valued it was emotional: care and protection. The packaging never made that connection.
We rebuilt the message and design system around the value customers were actually buying.
Clearer positioning made the brand easier to understand, remember, and choose.
If your product is stronger than the story around it, worth comparing notes?
Best, {{Sender}}
Why it works: one argument, product-story mismatch, carried the whole email, with a specific, believable example.
Email 3 · Shelf Impact
Subject: Is your packaging working hard enough?
Hi {{FirstName}},
A strong product can still disappear on a crowded shelf if the packaging looks like everyone else.
A consumer brand we worked with had that problem: good products, weak shelf distinction.
We rebuilt the packaging system around clearer hierarchy, stronger storytelling, and consistent premium cues across the range.
The goal wasn't to make it prettier. It was to make the product easier to notice, understand, and choose.
If packaging is doing less selling than the product deserves, is that live for you right now?
Regards, {{Sender}}
Why it works: it pre-empts the "just make it pretty" objection and reframes design as a commercial lever.
Email 4 · Positioning
Subject: Strong products struggle without clear positioning
Hi {{FirstName}},
Two brands can offer solid products and still become interchangeable in the buyer's mind.
We saw this with consumer businesses whose packaging and communication listed features but never established a distinct position.
We helped define who each brand was for, the value it should own, and how that position should appear consistently across packaging and communication.
That moved the conversation away from feature comparison and toward a clearer reason to choose the brand.
If positioning is something you're rethinking this year, would a quick call be useful?
Best, {{Sender}}
Why it works: it translates weak positioning into a commercial consequence: the brand becomes interchangeable and competes on features.
Email 5 · Brand Values
Subject: Do customers see what your brand stands for?
Hi {{FirstName}},
Many brands have a strong internal story that customers never actually see.
One heritage-led consumer brand had distinctive values, but its packaging and communication left those values buried. To the buyer, it competed mostly on product features.
We moved the brand story into what customers actually see, packaging, language, visual cues, and the buying experience.
That gave buyers a reason to connect with the brand beyond function alone.
If your values are stronger than what customers currently see, would it be worth a short conversation?
Best, {{Sender}}
Why it works: turns an abstract idea (values) into something concrete, where the buyer does and doesn't see them.
Specialist Recruitment & Technical Hiring (32 Meetings in 3 Months, India)
This sequence alternates hiring economics, speed, and technical-fit, three different reasons the same buyer might act.
Email 1 · Hiring Economics
Subject: The hidden math of hiring costs
Hi {{FirstName}},
Here is the hiring math many teams never put on one page.
Hire five engineers at INR 30L CTC each and an 8.33% agency fee is roughly INR 12.5L.
A flat-fee model changes that equation materially, without changing the roles you need to fill.
That difference can fund another hire, extend runway, or put budget back into product.
The point isn't to hire cheaply. It's to stop paying a percentage simply because the salary is higher.
Would it be useful to run the math against your current mandates?
Regards, {{Sender}}
Why it works: a real number does the persuading. The reader can check the math themselves, which is more convincing than any claim.
Email 2 · Speed
Subject: Struggling to close technical roles fast?
Hi {{FirstName}},
Product delays aren't always engineering problems. Sometimes the roadmap is waiting for the people needed to build it.
Technical hiring slows when recruiters miss the stack nuance, profiles take too long to screen, or candidates disappear midway.
Our recruitment team focuses on specialist technology roles and can move vetted, stack-aligned profiles quickly instead of sending volume resumes.
If one or two open roles are holding back a sprint or delivery milestone, would a 15-minute conversation be useful?
Regards, {{Sender}}
Why it works: connects hiring speed to a consequence the buyer already feels, a stalled roadmap.
Email 3 · Cost Control
Subject: Why should an easy hire cost a percentage?
Hi {{FirstName}},
Most agency hiring still runs on the same formula: a percentage of CTC, whether the role is difficult, straightforward, urgent, or already well-defined.
That makes hiring cost rise with salary, not necessarily with recruiting effort.
A fixed-fee model gives teams something simpler: predictable cost per hire and clearer headcount planning.
For teams making several technology hires, that can materially change how far the same budget goes.
If you're planning multiple hires this quarter, would it help to compare the two models against your numbers?
Best, {{Sender}}
Why it works: it turns a fee convention into a question, then backs it with math the reader can check.
Email 4 · Technical Screening
Subject: When in-house recruiting hits a ceiling
Hi {{FirstName}},
In-house teams are often excellent at volume hiring but hit friction when the role becomes deeply technical.
The symptoms are familiar: polished resumes that don't match the stack, recruiters unable to challenge technical claims, interviews spent discovering basic mismatches.
A specialist technology recruiter should reduce that load before a profile reaches your engineering team.
We focus on roles across backend, cloud, DevOps, AI and data, with screening tied to the actual brief.
If your team is getting resumes but not enough interview-worthy candidates, worth a quick call?
Regards, {{Sender}}
Why it works: the symptom list lets the reader self-diagnose; they recognize their own week in it.
Email 5 · Summary Value
Subject: Hiring fast doesn't have to cost more
Hi {{FirstName}},
The choice in technical hiring shouldn't be between speed, quality, and cost control.
Teams come to us when they need backend and cloud engineers who match the actual stack, DevOps talent that can contribute without months of handholding, and AI and data candidates screened beyond keywords.
The model is straightforward: specialist screening, fast profile movement, and a predictable fee structure. No resume dumping. No percentage surprise because the candidate earns more.
If you have an open technology mandate, you'll know quickly whether this fits. Worth a short conversation?
Best, {{Sender}}
Why it works: a closing-stage email that summarizes without dumping a generic capability list; it restates the three problems already raised.
IT & Managed Engineering Services (18 Meetings in 3 Months, US / UK / India)
Framed around owning a defined piece of work, not generic outsourcing.
Email 1 · Ownership After Launch
Subject: Who owns your product after launch?
Hi {{FirstName}},
When the product is the business, keeping it running can consume the same engineering capacity needed to grow it.
A managed engineering partner can take specific work off the team's plate, with agreed scope, clear delivery responsibility, implementation, and handover.
Your team still sets product priorities. The external team owns the engineering work that needs to get done.
Is there a specific area of product engineering or maintenance at {{Company}} that needs to move forward but keeps competing with the roadmap?
Best, {{Sender}}
Why it works: names the exact fear behind outsourcing, losing control, and defuses it before asking for anything.
Email 2 · Roadmap Capacity
Subject: Is maintenance eating your roadmap?
Hi {{FirstName}},
A common problem with growing products is that maintenance gradually becomes the roadmap.
Bug fixes, releases, support, and production issues keep the team busy while new features, integrations and AI initiatives wait.
A managed engineering partner can own defined work, from reliability and maintenance to releases, integrations, and feature delivery, while the internal team stays focused on product priorities.
Is there an engineering initiative at {{Company}} that's currently waiting for capacity?
Best, {{Sender}}
Why it works: "maintenance becomes the roadmap" is a specific, recognizable failure mode, not a generic efficiency pitch.
Email 3 · Run Cost
Subject: How much does your product really cost to run?
Hi {{FirstName}},
Product run-cost is usually more than engineering headcount.
Cloud, infrastructure, tooling, vendors, support, and maintenance all contribute to the actual cost of keeping a product running.
A useful starting point is to baseline the architecture, costs, risks, and operating model, then identify the engineering work that would materially improve reliability, cost, or delivery speed.
That turns a broad "managed services" discussion into specific work with a business case.
Would a 45-minute discussion around the current state be useful?
Best, {{Sender}}
Why it works: reframes a vague service category into a concrete, lower-commitment first step, a baseline.
Email 4 · Defined Project
Subject: A defined project, owned through delivery
Hi {{FirstName}},
Sometimes the problem isn't the engineering team. It's simply having enough capacity to finish a specific initiative.
That might be a cloud migration, release automation, production reliability work, a security implementation, an AI feature or a customer integration.
The cleanest version is simple: agree the scope, let one team own the delivery, and show exactly what changed at handover.
Is there a project at {{Company}} that needs to get done but keeps losing priority to the existing roadmap?
Best, {{Sender}}
Why it works: respects the reader's team ("the problem isn't you"), which lowers the defensiveness that kills outbound.
Email 5 · Low-Risk Entry
Subject: Could we identify one project to move forward?
Hi {{FirstName}},
Rather than starting with a broad managed-services proposal, a better first step is often one defined engineering priority.
Agree the scope. Own implementation. Hand over the completed work with a clear view of what changed.
That gives your team extra delivery capacity without adding another layer of coordination or committing to a vague long-term program.
If there's one engineering priority that keeps slipping because your internal team is already fully allocated, would you be open to a 45-minute conversation around that project?
Best, {{Sender}}
Why it works: the smallest possible ask, one project, removes the risk that stops most buyers from replying.
The Company Introduction Email to a New Client
A company introduction email should still open at the reader's problem, not "Dear Sir, we are a leading provider of…". Introduce the company only once you've earned the attention. Here's the structure I use instead of the standard intro:
Template · Company introduction
Subject: A cleaner way to [outcome] at {{Company}}?
Hi {{FirstName}},
Most {{role}}s I speak to aren't short on effort, they're stuck because [specific structural friction].
I run {{YourCompany}}. We help [who you serve] [what you do, in plain language] so [the outcome they can picture].
For one comparable {{client type}}, that meant [a concrete before-and-after or operating fact].
If that friction is on your list this quarter, worth a short conversation to compare notes?
Best, {{Sender}}
Why it works: the company line appears once, after the problem has done the work of earning a read.
The Referral or Warm Introduction Email
When you share a mutual contact or met briefly at an event, spend that trust immediately, then get back to the problem.
Template · Referral / warm intro
Subject: {{Referral}} suggested we talk
Hi {{FirstName}},
{{Referral}} mentioned you're [working on / weighing a specific goal or friction] and thought it was worth connecting us.
I run {{YourCompany}}, we help [who you serve] [what you do] so [the outcome].
With {{Referral}}'s team, that looked like [a concrete result or operating fact].
Given what you're focused on, would a short call next week be useful? Or I can send a one-page overview first, whichever you prefer.
Best, {{Sender}}
Why it works: it leads with the referral (the reason the email gets opened) and closes with two low-friction options.
Follow-Ups That Get Replies: The Five-to-Six-Email Sequence
A sequence should feel like five intelligent reasons to respond, not one email sent five times. Each follow-up must add a new reason, never repeat the last. This is the progression I use:
- Email 1: Primary pain. Lead with the most expensive or urgent problem.
- Email 2: Alternative pain. A different failure mode or operational bottleneck.
- Email 3: Economics. Make the cost, waste or ROI trade-off tangible.
- Email 4: Proof / use case. How the problem was solved in a comparable situation.
- Email 5: Objection / capacity. Address the reason they might not act: in-house team, budget, timing, switching cost.
- Email 6+: Close the loop. Polite and direct. Give them an easy way to say yes, no, or later.
The five recruitment and five IT examples each isolate a different argument, so reading them together shows how a sequence can progress instead of repeating itself.
Subject Lines That Get Opened
The subject earns attention; the opening has to justify it immediately. These are the operating rules I use, a working discipline, not an open-rate guarantee:
- Prefer a real problem, tension, number, contrast, or unexpected question over hype.
- Avoid spammy adjectives and anything that promises what the body can't defend.
- Keep it readable on mobile, aim short, roughly 30–50 characters.
- Never make a promise in the subject that the first line doesn't pay off.
The strongest subjects from the examples above all follow this: "The hidden math of hiring costs," "Is maintenance eating your roadmap?," "Why should an easy hire cost a percentage?" Each names a problem or a tension the reader already feels.
Mistakes That Kill New-Business Emails
- Pleasantries that delay the point. "Hope you're well" before anything of value trains the reader to skim past your opening.
- Generic capability dumps. Listing everything you do signals you don't know which problem is theirs.
- Jargon and pitch-deck phrases. "Leverage synergies to drive efficiency" says nothing a buyer can act on.
- Overclaiming outcomes the evidence doesn't support. One inflated number destroys the credibility of every real one.
- Fake urgency and "just following up" emails. Manufactured FOMO and empty check-ins get muted fast.
- A CTA that asks for too much. "Can I walk you through our full platform?" is a bigger yes than most first emails have earned.
Before You Hit Send: The 12-Point Checklist
Run every new-business email through this before it goes out:
- Is this written for a specific buyer, or merely for an industry?
- Does the first screen contain a real problem, not an introduction to your company?
- Is there only one primary argument?
- Can every claim be defended?
- Is the proof directly related to the problem in this email?
- Have we explained the mechanism in plain English?
- Does the reader understand the cost of doing nothing?
- Is the CTA small, clear, and relevant to the problem?
- Does this email add a new reason to respond versus the previous touch?
- Can any sentence be removed without losing meaning? If yes, remove it.
- Does it sound human when read aloud?
- Would a smart prospect feel informed rather than manipulated?
How to Send and Track These at Scale
A good email is only as good as the system that sends and follows up on it. Writing one great message is easy; sending a problem-led sequence to the right buyers, personalizing each one, spacing the follow-ups, and tracking which emails actually book meetings is where most outbound breaks down. That's the job Alore is built for, sequencing, personalization and reply tracking in one place, so the method above runs consistently instead of living in one person's head.
Frequently Asked Questions
How do you introduce your company in an email to a new client?
Lead with a problem the client recognizes, then introduce the company in one line tied to solving it. For example: "Most {{role}}s are stuck because [friction]. I run {{Company}}, we help [who] [do what] so [outcome]." Keep the company description to a single sentence.
How do you write a business email to a new client?
Use six parts: a problem-led subject, an opening that starts at their friction, the consequence of that friction, your mechanism and one proof point, and a single small CTA. Keep it to about 75–100 words and send it to a specific person, not a role.
How long should a new-business email be?
Roughly 75–100 words. Long enough to make one argument with one proof point, short enough to read in 15–20 seconds. If it's complete in 75 words, stop; never pad to hit a number.
How many follow-ups should you send, and how far apart?
Plan for five or six, each adding a new reason to reply, a different pain, the economics, a proof point, an objection, then a clear close. Space them a few days apart, and stop politely if there's no interest.
How do you write a welcoming email to a new client who just signed?
That's a different email from new-business outreach. Keep it short: thank them, set out what happens next in two or three steps, and give them one clear contact. Save the problem-led structure for winning the business, not for onboarding.
