Email Marketing for SaaS Companies: Product Events Send the Mail, and Billing Mail Is a Compliance Stream

In a SaaS company, email is mostly not campaigns. Nine tenths of the value sits in messages sent because of something that happened inside the product: a trial started, a key step was skipped, a limit was reached, a card failed, a renewal is due. Set those up first, and keep the newsletter and the product update broadcast as the smaller, later part of the programme. For an Indian SaaS business there is a third category that is neither marketing nor product, which is the billing stream, and it is governed by the rules around recurring payments rather than by your content calendar.

Build the programme in that order: lifecycle, billing, then broadcast. Teams that start with the newsletter usually have a beautiful monthly send and a trial funnel that leaks at step two.

The trial and onboarding sequence, written against events

Every message below fires on a condition, not on a day. Timing is the fallback when the event has not happened.

Trigger	What the mail does
Signup	Confirm access, name the one action that makes the product useful, nothing else
First key action completed	Show the next action, and only now introduce a second feature
Key action not completed in forty eight hours	Remove the obstacle: a two minute walkthrough, or an offer to set it up for them
Invited a teammate	Different message entirely, because multi user accounts convert and retain differently
Hit a plan limit	Explain the limit and the upgrade plainly, with the number they actually hit
Three days left on trial, active	Summarise what they did with it, then the upgrade path
Three days left on trial, inactive	Ask one question and offer to extend. Do not list features

The inactive branch is the one most teams skip, and it is where a large share of recoverable trials sit. An unengaged user does not need another feature tour, they need somebody to ask what stopped them.

Billing mail is a compliance stream, not a campaign

If you charge Indian cards on a recurring basis, some of your email is required. The Reserve Bank of India's framework for recurring e-mandates requires a pre-debit notification to the customer in advance of the charge, and an additional authentication step for mandates above a set value, with the exemption threshold having been raised to INR 15,000 per transaction. Treat the current threshold and notification window as something to confirm with your payment gateway, since both have been revised. What matters for your email programme is the design consequence: pre-debit notices, mandate confirmations and authentication prompts are transactional messages that must arrive, so they belong in the same reliability tier as a password reset and never in a marketing sending stream.

The GST invoice is the other mail nobody plans. An Indian business customer needs a correct tax invoice with the right place of supply, and the finance person chasing it is the one who decides whether renewing you is easy. Send it automatically, attach the PDF, and make it retrievable from the account without a support ticket. The portal at gst.gov.in is where your customer's accountant will be reconciling it, so the numbers have to match.

Two sending domains, because a reset cannot share a reputation with a newsletter

Split your sending before you scale it. Product and billing messages go from one subdomain, marketing from another, and the main domain is reserved for people writing to each other. One badly targeted broadcast that collects spam complaints should never be able to stop invoices reaching your customers. Authenticate each stream with SPF, DKIM and DMARC, and set DMARC to monitor before you enforce it so you can see what is sending on your behalf.

Keep the lists separate too. A user is a user, and a subscriber is a subscriber. The same person may be both, and unsubscribing from your newsletter must never stop their renewal notice.

The deliverability floor every sender has to clear

Since early 2024 the large mailbox providers have published explicit requirements for bulk senders. Google's email sender guidelines set out the current position, and the short version is: authenticate with SPF and DKIM, publish a DMARC record, offer one click unsubscribe in marketing mail, and keep reported spam complaints well below a threshold of a few tenths of a percent. A SaaS company sending to a few thousand users crosses into bulk territory faster than it expects, particularly during a launch.

Warm a new sending domain gradually rather than mailing your whole list on day one, and suppress addresses that have not opened anything for six months before a large send. Our longer piece on deliverability, list health and the flows that earn covers the mechanics in detail.

Dunning is the least glamorous mail you will write and the best paid

Cards expire, mandates lapse, limits get hit, and in India a failed recurring charge is more common than teams expect because of the authentication steps involved. A failed payment series is therefore pure recovered revenue:

• Four attempts across about two weeks, each with a different subject line and a single button that goes straight to updating the payment method.
• Say what will happen and when, in plain terms. Access continues until a named date.
• Tell the account owner and the billing contact, because they are frequently different people and only one of them holds the card.
• Add a WhatsApp or phone follow up for your larger accounts. For an annual contract it is worth a call.
• Never make a dunning email look like marketing. It gets filtered with the marketing.

What to measure instead of open rate

Open rate has been unreliable since mail clients began prefetching images, so judge lifecycle email on product outcomes. For each triggered message, measure the share of recipients who completed the action it asked for, within a defined window, against a holdout group that did not receive it. That holdout is the only honest way to know whether the mail caused anything. For the broadcast programme, track replies, feature adoption after an update mail, and unsubscribes per thousand. For billing, measure recovery rate on failed payments and nothing else.

What the tooling costs

Pricing moves in this category, so the figures here are indicative from my side only. Check current plans before you put them in a budget. Transactional sending is cheap and priced per message, and an early stage product can run its entire billing and product mail for a few thousand rupees a month. Lifecycle tools that read product events and branch on them are the real cost, usually priced by tracked users, and they become the larger line item as you grow. Many Indian SaaS teams run broadcast email on an inexpensive marketing tool and keep lifecycle inside the product with their own job scheduler for the first year, which is a reasonable trade while the flows are few.

Software bought from an Indian vendor carries GST at 18 percent, and imported software subscriptions have their own treatment, so have your finance team confirm how each one is handled. TDS can apply on certain payments to vendors, which is a question for your accountant and not for the tool's pricing page.

SaaS email: the questions growth and product teams bring

How many emails should a SaaS trial sequence contain?

Between four and seven, each tied to an event rather than a day, with a separate branch for users who never completed the first key action. More than that and you are describing features instead of removing obstacles.

Should product update emails go to every user?

Send them to the users affected by the change. An update about an integration matters to the accounts using it and is noise to everybody else, and noise is what raises your complaint rate.

Can a SaaS company send marketing email to Indian business contacts without consent?

Build on consent regardless. Permission based lists perform better, protect your sending reputation, and keep you on the right side of mailbox provider rules that now apply to everybody at volume.

Which emails should never come from a marketing tool?

Password resets, mandate and pre-debit notices, invoices, failed payment notices and security alerts. Those go through transactional infrastructure on a separate authenticated subdomain.

Is a newsletter worth it for a small SaaS company?

Only when somebody owns it and has something specific to say monthly. A lifecycle programme with a holdout test on each flow returns more per hour of work in the first year.

How do you win back users who cancelled?

One honest message about what has changed since they left, sent when the thing that made them leave is genuinely fixed, and a second never. Repeated win back mail is the fastest way to accumulate spam complaints.

Named in the answer, before the first signup

Email reaches people who already know you exist. The step before that has quietly changed: a buyer comparing tools in your category now asks ChatGPT or Perplexity which options are worth considering, and acts on the three or four names that come back. Nobody on your growth team sees that answer, and no amount of lifecycle email changes it, because the people it names were chosen from review sites, comparison pages and documentation long before a signup form was filled. AI Knows Us was built to show which products come back for the questions buyers in your category ask, and what those answers are reading. It is the one part of the funnel most SaaS teams have never looked at, and it sits right at the top of it.