An envelope and magnifying glass stand out among pale envelopes.
By Updated

How to write a B2B cold email from one business problem

Estimated reading time: 6 minutes

Start with a business task your offer can help someone complete. Find a current observation that makes the task plausible for this account. Then write an email that lets the buyer confirm, correct, or reject the connection.

A job opening can support a question about hiring. It does not establish that the company struggles to hire, has budget for an agency, or wants your candidates. Keep that boundary visible while you write.

The first email needs enough context for the recipient to understand why you contacted them and what you can usefully offer. Research, a template, and an AI draft all serve that decision.

Build the account note before writing the email

Use a short note with five fields:

FieldWhat to recordWhat to keep out
ObservationThe source, date checked, and relevant passageA summary that adds facts the source never stated
Business taskThe work the observation suggests someone may need to doA claim that the company has a problem you have not verified
RecipientEvidence that this person's responsibilities relate to the taskAn assumption that a senior title means purchase authority
Useful offerA specific item or service you can deliverA promised result without approved evidence
Open questionThe one uncertainty the buyer can help resolveSeveral discovery questions packed into a cold email

Read the source yourself. Check whether it describes the right company, location, role, and period. If an old announcement says a project was planned, find out whether it is still relevant before describing it as current work.

You do not need an unusual personal detail to fill this note. A clear account fact connected to a real offer is a better writing input than an unrelated compliment. If the company fits your market but you have no current trigger, describe the fit honestly instead of manufacturing urgency.

A B2B cold email template with a reason for each line

Use this as a structure to adapt:

Subject: [The relevant task or account context]

Hi [Name],

[One observation you can verify.]

[What you do for this task, plus a specific useful item or next step you can deliver.]

[One question that checks relevance, ownership, or interest.]

[Your name and company]

The observation explains the contact. The offer explains why your company belongs in the conversation. The question gives the buyer a way to respond without accepting an unverified diagnosis.

Choose the question based on what remains unknown. If you cannot establish ownership, ask who handles the task. If ownership is clear but your offer's fit is uncertain, ask about that fit. Do not hide a complete sales discovery form inside a request for a quick reply.

Worked example: a placement agency approaching an employer

Fictional example. The employer, agency, source details, and messages below are invented to show the writing method. They are not Quantonica campaigns or customer results.

Suppose an employer's current careers page lists maintenance technician roles in Leeds with rotating shifts. In this example, a separate company page identifies Alex as the person responsible for maintenance recruitment there. The seller is a placement agency that serves West Yorkshire and can prepare a role brief before proposing candidates.

The public information supports the role, location, shift pattern, and recruitment responsibility. It leaves the employer's candidate pipeline, use of agencies, purchase authority, and budget unconfirmed.

An unsupported first draft might say:

Subject: Solve your hiring bottleneck

Hi Alex,

Your expansion has clearly left you struggling to hire. We can solve your staffing shortage quickly. Are you free for a call tomorrow?

Neither an expansion nor a hiring bottleneck appears in the fictional source. The seller also promises a speed of result without evidence. Replacing the adjectives would leave those problems intact.

A grounded version could read:

Subject: Leeds maintenance roles

Hi Alex,

Your careers page lists maintenance technician roles in Leeds with rotating shifts.

We place maintenance technicians in West Yorkshire. I can send a short role brief showing the shift and certification details we would check before proposing candidates.

Does your team use outside agencies for these roles?

Maya, [Agency]

The first sentence stays within the source. The offer describes work the fictional seller can do. The question checks a commercial unknown instead of assuming that an open role is an invitation to an agency.

Use those lines only when they are true for your offer and account. If the posting excludes agency approaches, respect that boundary and hold this pitch. If the recipient's responsibility is uncertain, establish the right contact before presenting them as the hiring owner.

Keep the same discipline in a complex industry

Fictional example. A manufacturer announces another production line. A water-efficiency consultancy wants to determine whether the project includes a water-use review. The announcement alone does not establish excess consumption, a permit problem, or an equipment requirement.

The consultancy could write:

Subject: Water review for the new line

Hi [Name],

Your announcement describes another production line at [site].

We help plant teams scope water-use reviews before recommending equipment. I can share a scoping checklist covering the process boundary and existing metering.

Is a water-use review part of the new line's preparation?

[Name], [Consultancy]

This message asks about a possible task. It does not tell the prospect that their plant wastes water or needs a particular treatment system. The consultancy would still need to verify the recipient's responsibility and confirm that its service fits the site.

If your evidence points to a formal procurement process, use its stated contact route and submission instructions. A cold email template does not replace the buying process the account has published.

Make the subject and next step honest

Write a subject that accurately describes the message. Avoid fake reply subjects, invented introductions, and references to meetings that never happened. In its guidance for messages sent to personal Gmail accounts, Google warns against using “Re:” or “Fwd:” unless the message is an actual reply or forward.

Choose a next step that fits the evidence you have. A role brief, a scoping checklist, or a question about responsibility can be a concrete starting point. The buyer should be able to tell what they would receive and why it relates to their work.

Gong's published CTA analysis separates cold emails from emails within active deals. Keep that distinction when borrowing advice: a meeting arrangement with an engaged buyer addresses a different decision from an introduction to a stranger. Its provider data does not establish a universal ranking for your next-step wording.

You can ask for a meeting when you can explain why that meeting would be useful. You can also offer something smaller. Avoid promising a checklist, comparison, candidate brief, or analysis that you cannot actually supply.

Review an AI draft against the account note

Give the AI the source passage, account context, approved offer, and unresolved questions. Ask it to draft within those limits. A longer prompt or a more capable model does not verify a fact missing from the source.

Before approving the email:

  1. Match each account claim to the source passage.
  2. Separate an observation from an inference about the buyer's situation.
  3. Check that the recipient's responsibilities relate to the task.
  4. Confirm that your team can deliver the offer as described.
  5. Remove any unsupported result, urgency, customer name, or implied prior conversation.
  6. Check the account's exclusions and current conversation history before sending.

For low-volume B2B outreach, you can do this manually. Keep the account note beside the draft so you can review targeting, prospect selection, and wording together. Include that research and review time when you compare the full cost of an AI BDR and a human BDR.

If the source is weak, hold the account or write a narrower question. Do not ask the AI to make the message sound more certain.

Keep the research after the first email

Save the source, the approved message, and the reason you contacted the account. When a buyer replies, record what they confirmed or corrected. Use that information before drafting the next message or adding similar accounts.

Read the draft from the buyer's side. They should be able to identify the observed fact, the work you offer, and the question you need them to answer.

Bring that draft and its source note to a Quantonica pilot discussion if you want help with account research and campaign operation.

Don't miss out

How we think about AI SDRs
2026-05-15

How we think about AI SDRs

The AI-versus-human framing misses the point. We build AI SDRs that hand the work that compounds back to your BDRs — research, conferences, ten-call days, LinkedIn presence — while the system handles prospecting in the background. The contest worth winning is a BDR team with intelligence underneath versus one without.

Continue reading
A conference badge scan needs context before sales follow-up
2026-11-20

A conference badge scan needs context before sales follow-up

Check account fit, conversation claims, restrictions, and existing ownership before adding badge-scan contacts to a B2B sales campaign.

Continue reading
How to ask for a small next step without hiding the sales intent
2026-11-18

How to ask for a small next step without hiding the sales intent

Commitment decision ladder plus a worked resource request, fulfillment and separately agreed transition to discussion.

Continue reading
Which AI BDR decisions should a person approve?
2026-11-16

Which AI BDR decisions should a person approve?

Assign AI BDR approval rights with a decision matrix, evidence requirements, expiry conditions, and tests that rejected actions stay blocked.

Continue reading