Skip to main content
Lead Generation Websites, Google Maps Ranking, WhatsApp Funnels, Ecommerce, SEO, Web DesignSpeed Optimization · Conversion Optimization · Monthly Lead Systems · AI AutomationLead Generation Websites, Google Maps Ranking, WhatsApp Funnels, Ecommerce, SEO, Web Design

Email Marketing · Campaigns & Lifecycle Automation

Email to people who
actually asked to hear from you.

We plan campaigns, build segmented lifecycle flows, and configure sender authentication for opted-in audiences only — purchased or scraped lists are not accepted. Open rates and unsubscribe rates can be tested and reported on, but no agency can honestly promise a specific result: too much of the outcome depends on your list, your content, and factors outside our direct control.

Opted-in lists onlyConsent-respecting mechanicsNo inbox-placement guaranteePlatform scoped per engagement
Email marketing specialist planning campaign sends and lifecycle flows

Prateeksha provides permission-based email marketing campaigns and scoped lifecycle automation for Mumbai businesses — planning, templates, segmentation, testing, reporting and provider configuration for opted-in audiences only. Transactional email generated by your own product and individual sales outreach are explicitly out of scope. No delivery, inbox-placement, open-rate, or unsubscribe-rate outcome is guaranteed.

Where email programs go wrong

Most 'email marketing' problems are actually list, consent, or definition problems.

  1. 01

    Purchased or scraped lists

    A list bought or scraped from somewhere else damages sender reputation and breaks the lawful basis the whole programme depends on.

  2. 02

    Campaigns and lifecycle flows treated as one thing

    A one-off promotional send and a triggered welcome flow have different jobs, different timing, and different measurement — collapsing them into "email marketing" hides that.

  3. 03

    Transactional email bolted onto marketing tooling

    Receipts and account-recovery messages are application-owned, with their own testing and monitoring needs — routing them through a marketing platform without that discipline is a real risk.

  4. 04

    Suppression lists quietly re-imported

    An old list gets re-uploaded without checking against current suppressions, re-emailing people who already opted out.

  5. 05

    Delivery treated as guaranteed

    SPF/DKIM/DMARC get set up once and inbox placement is assumed solved — but content, frequency, and recipient behaviour keep affecting it after that.

What a scoped approach changes

Campaigns and lifecycle automation, kept distinct, built on a lawful list, measured honestly.

We plan and build permission-based campaigns and scoped lifecycle flows for audiences that have actually opted in — never purchased or scraped lists. Content, distribution and promotion for the material inside a campaign are coordinated with our content marketing service, and email sits alongside social media marketing as one channel inside a wider digital marketing plan, measured through analytics & reporting.

  • Purchased, scraped, or improperly shared lists are not accepted
  • Campaigns and lifecycle automation scoped and measured separately
  • Unsubscribe and suppression instructions honoured, never re-imported
  • SPF, DKIM and DMARC configured to reduce authentication risk, not promise delivery
  • Sensitive personal data excluded from segmentation without an approved lawful basis

What's included

Campaign and lifecycle work, scoped and delivered distinctly.

Transactional email and sales outreach are named here specifically because they are not part of this scope.

01

Campaign planning

Strategy, calendar and audience definition for one-off or scheduled sends to your opted-in list.

Marketing campaigns

02

Templates & segmentation

Responsive templates and list segmentation built around real audience differences, not a single blanket send.

Build

03

Lifecycle automation

Welcome and re-engagement flows and similar triggered sequences, scoped per engagement rather than assumed as a bundled suite.

Scoped per engagement

04

Testing

Subject-line and content testing that can show a genuine difference — or show no significant difference, reported either way.

A/B testing

05

Reporting

Campaign and flow performance reported against agreed measures, without a promised open-rate or unsubscribe-rate outcome.

Reporting

06

Provider configuration

Sender authentication (SPF, DKIM, DMARC) and provider setup, confirmed to your existing stack during scoping — not assumed.

Configuration

07

List hygiene

Suppression handling and unsubscribe processing kept current, never casually re-imported or overridden.

List management

08

Not included: transactional & outreach

Receipts, account-recovery messages and other transactional messages stay owned by your application; individual sales outreach runs on separate tooling entirely.

Out of scope

How an email engagement runs

Define, build, test, send, report — with consent checked at every stage.

Lifecycle flows and campaigns move through the same discipline, scoped separately in your proposal.

  1. Define

    Audience, list source and lawful basis confirmed before any template or flow is built.

  2. Build

    Templates, segmentation and lifecycle flows built to your written scope, not a default bundle.

  3. Configure

    Sender authentication and provider settings configured to reduce authentication risk.

  4. Test & approve

    Content, offers, targeting and schedule reviewed and approved by you before anything sends.

  5. Send & report

    Campaigns or flows go live, then are reported against agreed measures, including tests that showed no difference.

What changes

A blanket 'email marketing' bundle vs. a scoped programme.

Both can use the same platform. The difference is whether campaigns, lifecycle flows, and transactional email are kept distinct.

What changes
A blanket bundle
A scoped programme
List source
Assumed to be fine, rarely checked
Confirmed opted-in; purchased or scraped lists refused
Campaigns vs. lifecycle flows
Treated as one undifferentiated "email marketing" service
Scoped, built and measured as genuinely different workstreams
Transactional email
Routed through the same marketing tooling by default
Named as application-owned, outside this service's scope
Deliverability
Presented as solved once, guaranteed going forward
Authentication configured to reduce risk, never promised as delivery
Reporting
Only wins get reported
Tests with no significant difference reported honestly too

Scope & deliverability boundary

What this service covers, and what it deliberately does not.

This service covers permission-based marketing campaigns and scoped lifecycle automation only. You must provide a lawful, permission-appropriate audience — purchased, scraped, or improperly shared lists are not accepted, and we will not send to one. Unsubscribe and suppression instructions must be honoured, and suppression lists must not be casually re-imported or overridden once someone has opted out.

Sender identity and domain access require approved authorization before we configure anything on your behalf. We cannot guarantee delivery or inbox placement — SPF, DKIM, and DMARC configuration only reduces authentication risk. Domain reputation, list quality, content, sending frequency, recipient behaviour, provider rules, and mailbox filtering all affect deliverability, and most of that sits outside any agency's control. Sensitive personal data must not be used for segmentation without an appropriate lawful and explicitly approved basis.

Transactional messages generated by your own product or service — receipts, account recovery, and similar system email — require application-level ownership, testing, retry behaviour and operational monitoring outside a generic campaign scope, and are not part of this service. Individual sales outreach emails from a salesperson run on a different lawful basis and different tooling entirely, and are also out of scope here. You approve claims, offers, prices, targeting, schedules, and final content before anything sends. Platform fees and sending costs are separate from our fees unless explicitly included in your proposal. No credentials should be requested through ordinary page copy — access to your accounts uses approved role-based access, confirmed directly with you.

If the real need is coordinating email alongside other channels rather than running it in isolation, that's better addressed by our digital marketing channel strategy, and measured through analytics & reporting.

Choose your starting point

Three ways to start, depending on where your list and flows are today.

Each is a legitimate starting point — the written proposal defines exactly what is included before anything begins.

Start here

List & deliverability audit

A review of your list source, consent records, suppression handling, and sender authentication.

  • List source and consent review
  • Suppression and unsubscribe handling review
  • SPF/DKIM/DMARC configuration review
  • Findings you own either way
Request an audit

Recommended

Campaign & lifecycle build

Campaign templates and scoped lifecycle flows built and configured to your written scope.

  • Campaign templates and segmentation
  • Lifecycle flows scoped per engagement
  • Sender authentication configured
  • Testing and reporting against agreed measures
Scope a build

Ongoing

Managed sending programme

Ongoing campaign management, list hygiene, and reporting on a defined cadence.

  • Recurring campaigns and flow maintenance
  • Ongoing list hygiene and suppression handling
  • Testing programme with honest reporting
  • Reporting cadence agreed in your written proposal
Discuss an ongoing programme

What ships with an email engagement

A written scope

Campaigns, lifecycle flows, deliverables, cadence, access, and exclusions written into the proposal before anything begins.

Consent-respecting mechanics

Unsubscribe and suppression handling configured and honoured, not left to chance.

Sender authentication configuration

SPF, DKIM and DMARC set up to reduce authentication risk, with limits stated plainly rather than promised as delivery.

A reporting cadence

The reporting schedule for your engagement, agreed in the proposal rather than assumed to be weekly for everyone.

Who this is not a fit for

A poor fit, or a dependency worth naming honestly.

An email engagement works best when a few things are true first.

01

No opted-in list yet

Without a lawful, permission-appropriate audience there is nothing to email — we will not send to a purchased or scraped list to fill that gap.

Dependency

02

Expecting a guaranteed outcome

If the expectation is a guaranteed open rate, delivery rate, or inbox-placement result, we are not the right fit — no agency can honestly promise that.

Poor fit

03

Needing transactional email built

Receipts, account-recovery messages, and similar system email need application-level ownership, testing and monitoring — that is a different scope from this service.

Dependency

04

Wanting individual sales outreach

Personal, non-bulk outreach from a salesperson runs on different tooling and a different lawful basis — it is not part of this service.

Poor fit

Ready when you are

Tell us about your list and your goals — we'll scope campaigns and lifecycle flows separately.

Share your current list source, provider, and what you're trying to achieve. We'll come back with a written proposal defining exactly what's in scope, with no guaranteed open-rate or delivery outcome implied.

FAQs

Email Marketing — Frequently Asked Questions

Straight answers about campaigns, lifecycle automation, consent, and deliverability limits.

Didn't find your question? Share your list source and goals and we'll scope a proposal — in writing, with what's included made explicit.

Permission-based marketing campaigns and lifecycle automation only — campaign planning, templates, segmentation, scoped lifecycle workflows, testing, reporting and provider configuration for an audience that has actually opted in. It does not cover transactional email generated by your own product or application, and it does not cover individual sales outreach emails from a salesperson.

A campaign is a one-off or scheduled send to an opted-in list. Lifecycle automation is a triggered flow — a welcome sequence or a re-engagement message — scoped per engagement, not a bundled universal suite. Transactional email (receipts, account-recovery messages) is generated by your product and is owned by your application, not this service — it needs its own testing, retry behaviour and monitoring outside a campaign scope. Sales outreach is an individual, non-bulk email from a salesperson, on a different lawful basis and different tooling entirely. We do not treat these as interchangeable.

No. Purchased, scraped, or improperly shared lists are not accepted under any circumstances — we require a lawful, permission-appropriate audience that has actually opted in. This protects your sender reputation and is a condition of the engagement, not a preference.

No — we cannot guarantee that. SPF, DKIM and DMARC configuration reduces authentication risk, but it does not guarantee delivery or inbox placement — domain reputation, list quality, content, sending frequency, recipient behaviour, provider rules and mailbox filtering all affect where an email lands, and most of that sits outside any agency's control.

We can describe and run the activity — subject-line testing, segmentation, send-time testing, list hygiene — but we will not promise a specific open-rate or unsubscribe-rate result. A/B testing can also show no significant difference between versions, and we report that honestly rather than only reporting wins.

No. Abandoned-cart recovery is an automation type we can build — a triggered flow reminding a shopper about items left in their cart — not a promised recovery rate, AOV increase, or repeat-purchase outcome. Results depend on your offer, pricing, audience and timing, none of which any agency controls.

Platform choice depends on your existing stack and is confirmed during scoping, not assumed. We do not claim universal, bundled expertise across every provider on the market — the right fit for your engagement is discussed and written into your proposal before anything is configured.

We cannot certify GDPR compliance — that is a legal determination your own counsel needs to make. What we can do is configure consent-respecting mechanics: honouring unsubscribe and suppression instructions, not re-importing or overriding suppression lists, and building segmentation that does not use sensitive personal data without an appropriate lawful and explicitly approved basis.

Those are available if scoped into your engagement, not included as standard. We confirm what CRM or lead-scoring integration is actually needed during scoping rather than bundling it into every package by default.

You do. Claims, offers, prices, targeting, schedules and final content are all approved by you before anything sends — nothing goes out on the strength of our judgement alone.

Aeroboom
ARC
Chinadaila
Logo FNS
HB Roofer
Heranba
Instagram
Logo 1
Operando
Sea Star Logo
Womenzza
Aeroboom
ARC
Chinadaila
Logo FNS
HB Roofer
Heranba
Instagram
Logo 1
Operando
Sea Star Logo
Womenzza

Loading…