Skip to content

AI Sales Agents

Cold Email Personalisation Agent

A cold email personalisation agent reads each prospect's website, role and recent activity, then writes an opening line specific to them. Equally important, it ships with the deliverability engineering — domain warming, sending limits, authentication — that keeps your main domain out of the spam folder.

Who it's for

Anyone whose cold email reply rate is under 2%.

What changes

Personalisation at volume, which is the only thing that still works.

Starting at
₹75,000
Timeline
3–5 weeks
Built from
Vashi, Navi Mumbai

Key takeaways

  • Volume without deliverability engineering destroys your domain, permanently.
  • Never send cold email from your primary domain — use a separate sending domain.
  • SPF, DKIM and DMARC are the floor, not the strategy.
  • Reply rate is the only metric worth optimising; open rate is now largely noise.
  • Builds in 3–4 weeks from ₹75,000, including the sending infrastructure setup.

The failure mode this exists to prevent

A business buys a list, connects it to a sending tool, and pushes two thousand emails from its main domain in a week. Reply rate is near zero, which is annoying. Then invoices to existing clients start landing in spam, which is a real problem, and it does not resolve quickly.

Domain reputation is slow to build and slow to repair. Burning your primary domain to chase a handful of cold replies is one of the worst trades available in business development, and it is made constantly.

The infrastructure that has to exist first

Before personalisation matters at all, the sending setup has to be right. This is the part most cheap builds skip.

  • Separate sending domains. Never your primary. Usually two or three lookalike domains, so a problem on one does not take the others down.
  • SPF, DKIM and DMARC correctly configured on each. Missing any of these is a straightforward path to the spam folder.
  • Warming. New domains start at a handful of sends a day and ramp over weeks. Skipping this is the single most common cause of failure.
  • Per-mailbox limits. Sensible daily caps per address, with several mailboxes rather than one sending hard.
  • Reply monitoring and automatic suppression, so nobody gets a follow-up after they have answered.
  • Bounce handling with immediate list hygiene, because a high bounce rate is itself a reputation signal.

What actually gets personalised

Not the salutation. Inserting a first name has been table stakes for fifteen years and signals nothing.

SignalWhere it comes fromValue
Something specific on their siteTheir own pagesHigh — proves a human-level read
A recent hire or job postingPublic listingsHigh — implies a live need
Their tech stackSite fingerprintingMedium–high for software offers
Recent news or expansionPublic sourcesMedium — often stale
Role and seniorityEnrichment dataMedium — shapes the framing
Industry onlyFirmographicsLow — reads as a template

The top two rows are what produce replies. If the research cannot find either, the honest move is a short, plainly-written message about the problem you solve — which outperforms manufactured personalisation reliably.

Open rate is no longer a useful metric

Since mail privacy protections became widespread, a meaningful share of opens are pre-fetched by the mail client rather than the human. Your open rate now measures a mixture of real reads and automated ones, in unknown proportion.

Optimising for it produces subject-line games that do nothing for pipeline. We report it because clients expect to see it, and we tell you to steer by reply rate and positive reply rate instead.

Volume ceilings that keep you safe

There is a temptation to raise sends the moment the system works. Resist it. Per-mailbox daily limits exist because inbox providers watch send patterns, and a sudden ramp looks exactly like what they are filtering for.

Growth comes from adding warmed mailboxes and domains over time, not from pushing existing ones harder. We set the ceilings, monitor reputation continuously, and pause sending automatically if bounce or complaint rates move the wrong way — before a human would have noticed.

What is running afterwards

Sending domains configured, authenticated and warmed; the personalisation agent with your research signals; per-mailbox limits and rotation; reply detection with automatic suppression; bounce and complaint monitoring with auto-pause; CRM logging of every touch and reply; and reporting on reply and positive-reply rate by segment.

FAQ

Cold Email Personalisation Agent — your questions

Will this get our domain blacklisted?

Not if the infrastructure is built properly, which is most of what you are paying for. Separate sending domains, correct authentication, gradual warming, sensible per-mailbox limits and automatic pausing on bad signals. Every blacklisting we have seen came from skipping one of those, usually warming.

Is cold email legal in India?

B2B cold email to a business address is broadly permissible in India, unlike some jurisdictions. If you email into the EU or UK, GDPR and PECR apply and the rules are stricter. We configure suppression by region and recommend legal review if a meaningful share of your list is overseas.

How many emails a day is safe?

Start at 10–20 per mailbox and ramp over four to six weeks. A steady 30–50 per warmed mailbox is a sustainable ceiling. Scale by adding mailboxes, not by pushing existing ones — the pattern matters more to inbox providers than the absolute number.

What reply rate should we expect?

It depends far more on your list and offer than on the writing. We would rather set a baseline from your first two weeks and improve against it than quote an industry figure that flatters us. Any supplier promising a specific rate before seeing your list is guessing.

Next step

Want a Cold Email Personalisation Agent for your business?

Tell us what the process looks like today and we'll tell you what it would look like automated — and what it would cost.