Email Marketing Automation in India: 5 Mistakes

Five avoidable mistakes Indian teams make with email marketing automation — domain setup, segmentation, DPDP consent — and what to fix first.

Sanjay Mandal · · 5 min read

Xin

Most Indian SMBs don't have an email marketing problem. They have an automation setup they paid for and never finished: the tool was bought, the template was loaded, last year's exhibition list was uploaded, and six months later nobody can name a deal those emails brought in. If you're a founder or ops lead carrying marketing on top of your real job, the leak is rarely dramatic — a few thousand rupees a month, plus four to six hours you don't have.

Here are the five mistakes we see most often, and the fix for each.

Mistake 1: Buying a list to make growth feel faster

Purchased and scraped lists are the most expensive free thing in Indian B2B marketing. IndiaMART exports, conference delegate PDFs, LinkedIn pulls — they arrive with spam traps, role addresses and people who never asked to hear from you. The first campaign might get clicks. The second and third train inbox providers to filter you.

The fix is slower but far cheaper: grow the list you own. Invoice footers, WhatsApp auto-replies, the QR code on your expo stall, your website — every place you already touch a customer is a signup point.

Start with the plumbing. Run your domain through the site checker; a broken, hidden or unmonitored signup form is a silent leak, and most teams who check find at least one.

Mistake 2: Sending bulk mail from your main domain

If campaigns go out from the same domain that sends quotes, invoices and support replies — with no SPF, DKIM or DMARC records — you're gambling with all of it. One bad batch and your sales email starts landing in spam too.

Set up a separate sending subdomain (mail.yourcompany.com is the usual pattern), authenticate it, then warm it up: first campaign to your 200-500 most engaged contacts, then roughly doubling volume each week until you're back to full list size. Skipping the warm-up is the most common reason a technically correct campaign still lands in spam.

The India-specific trap is sending 5,000 marketing emails a month from your Google Workspace mailbox because it's already there. Workspace caps outbound recipients per day, and hitting that ceiling affects your everyday business mail too. Marketing volume belongs on a sending platform.

Mistakes 3 and 4: Mailing everyone, and confusing a footer with consent

A list of 12,000 contacts where 7,000 haven't opened anything in nine months is not an asset. It's a liability with a monthly bill.

Here's how it plays out. You mail all 12,000 once a month. The 5,000 engaged people get your message — but so do 7,000 dormant addresses, some of which are now spam traps or closed accounts. Complaints and bounces climb, inbox providers start filtering your whole domain, and the engaged 5,000 stop seeing you.

Split the list instead:

  • Engaged (opened or clicked in the last 90 days): mail normally, every one to two weeks.
  • Cold (91-180 days): quarterly, with something genuinely worth replying to.
  • Dormant (180+ days): one re-permission email, then suppress.

In our experience this costs you 30-50% of your raw list, and it's the fastest route back to inbox placement — typically within two to four weeks. Suppress, don't delete.

Consent sits in the same pile. Under the DPDP Act, consent has to be informed, purpose-limited and easy to withdraw — meaning you can answer three questions for any contact: where did this consent come from, when was it given, and can you prove it. Most setups can't. The source sits in someone's inbox, the unsubscribe link points to a form nobody watches, and the suppression list gets left behind at the next tool migration. Fix three things this quarter: log consent source and timestamp on every record, make one-click unsubscribe work and honour it within 24 hours, and keep a suppression list in a file you control. If you email buyers in the EU or UK, GDPR stacks on top of DPDP.

Mistake 5: Paying in dollars to measure opens

Two leaks sit side by side. The first is paying per contact in USD for a list that is mostly dormant: add 18% GST and a 2-3.5% card forex markup, and the real cost often runs 20-25% above the advertised price. If half the list is dead weight, you're renting storage.

The second is measuring the wrong number. Opens have been unreliable since Apple began pre-fetching email images — a chunk of your open rate is machines, not people. Track what survives:

  • Clicks and replies per 1,000 delivered
  • Replies that turned into a call, quote or order
  • Cost per qualified lead, including tool spend and your time

And remember where Indian replies actually land. A buyer clicks your email and messages you on WhatsApp an hour later. If email, WhatsApp outreach and your CRM don't share one record, you're paying for automation and still doing follow-up by hand — the gap our own products exist to close.

Where to start with email marketing automation in India

Don't migrate tools first. Get the order right:

  • Week 1: authenticate the sending domain (SPF, DKIM, DMARC), create the subdomain, test every signup form.
  • Week 2: export, dedupe, and tag your list by consent source and last engagement date.
  • Week 3: build three flows only — welcome, re-permission, customer onboarding.
  • Week 4: connect replies and clicks to your CRM, and pick one number to report every month.

None of it is exciting. The payoff is a channel that stops leaking money quietly and starts producing conversations you can trace. If you'd rather not run it alone, Maysan Labs does this kind of migration and setup work for Indian SMBs — a short scoping call is usually enough to see what's broken.

Buying software or a website?

Twelve questions to ask any vendor before you sign: price, your data, fit for an Indian business and support.

Get the free checklist

Related case study

Full-Stack Ecommerce Platform

Needed a complete ecommerce platform built from scratch with inventory, orders, payments, and customer management.

View case study

Written by Sanjay Mandal at Maysan Labs, a software studio in Gurgaon, India. Follow us on LinkedIn