Email marketing proposals: list size, ESP, and what you will not do

Email marketing job posts mix strategy, design, copy, automation, and analytics into one paragraph. Then they add “must increase revenue” and a tool you have never seen.

Freelancers who reply “I am a Klaviyo expert” without naming list size, ESP, deliverables, and what you will not do invite scope creep: migrate the list, fix DNS, write twelve flows, design templates, and run ads, all for one fixed fee.

This guide helps you write proposals that sound like an operator, not a buzzword bundle. The reader has a job post open and needs to send today.

What the buyer is trying to de-risk

Common hidden fears:

• Our flows are broken and nobody knows why
• We are paying for an ESP we do not use well
• Compliance (unsubscribe, consent) is scary
• Last freelancer blasted discounts and hurt deliverability
• We need campaigns and someone to fix technical setup

Your proposal should classify which bucket their post is in, then answer it.

For ignored proposals in crowded inboxes, remember the basics in why clients ignore proposals.

The scope header: list size, ESP, and health basics

Put this near the top:

List: ~[size] subscribers, [B2C/B2B], primary segments [if known].

ESP: [Klaviyo / Mailchimp / HubSpot / Customer.io / other]. I work in your account; you keep billing ownership.

Deliverability posture: I do not buy lists or use scraped emails. Campaigns go to opted-in contacts only. I flag if bounce/complaint rates need cleanup before scaling sends.

Access needed: ESP admin or role with campaigns, flows, templates; optional Shopify/integration read access.

If they did not state list size, ask or propose an audit milestone. Guessing “small list” on a 400k list changes price by an order of magnitude.

What you will not do (saves your reputation)

Clients will assume you do everything email touches unless you say otherwise.

Pick honest lines:

Not included unless added: paid ads management, full brand redesign, SMS, cold outreach to purchased lists, legal compliance sign-off, 24/7 monitoring on holidays.

DNS/SPF/DKIM: I can coordinate records with your DNS host using a checklist; if your IT team must click approve, we add a day for that.

Saying limits does not make you difficult. It makes you safe to hire.

Three proposal patterns by post type

Pattern A: campaign production (one-off or monthly)

When they want: newsletters, promos, product launches.

Proposal focus:

• Cadence (4 campaigns/month, etc.)
• Who provides copy vs you write
• Segments and personalization level
• Approval turnaround

Monthly: [4] campaigns. I draft subject lines + body from your brief, build in [ESP], send test to your team, launch after one consolidated approval round. Reporting: open/click/revenue if tracking is wired.

Link pricing habits to fixed-price project proposal pricing when they want a flat monthly fee.

Pattern B: automation / flows (welcome, cart, post-purchase)

When they want: flows built or fixed.

Proposal focus:

• Map existing flows vs net-new
• Trigger data (Shopify, Woo, API)
• How many emails per flow in v1

Milestone 1: audit current flows + data diagram (what triggers what). Milestone 2: rebuild [welcome + abandoned cart] with your brand template, test purchases on staging, document in Loom for your team.

Use milestones when the client never mentioned them because flow work hides unknown integrations.

Pattern C: deliverability rescue or ESP migration

When they sound burned: spam folder, blocked domain, messy lists.

Do not promise instant fixes.

Milestone 1: deliverability audit (bounce/complaint history, authentication records, sending domains, content patterns). Deliverable: prioritized fix list. Milestone 2: implement agreed fixes, warm-up plan if domain changed (timeline depends on list size; no guaranteed inbox placement).

If they want migration from Mailchimp to Klaviyo, name data mapping, template rebuild, and parallel send pause risks.

List size bands (how to talk about price without fake precision)

You do not need a public rate card in the proposal. You need bands that explain effort:

Rough list size	Proposal note
Under 10k	Faster QA, simpler segmentation, migration lighter
10k-100k	Segmentation and hygiene matter; test sends still manageable
100k+	Compliance, warm-up, and send volume planning dominate time

One sentence in the proposal is enough:

At ~[80k] subscribers, I allow time for segment QA and send scheduling so we do not trip rate limits or hurt reputation.

That sounds more professional than a single dollar figure with no context.

Reporting: promise metrics you can actually pull

Do not promise “300% ROI” in the proposal.

Promise reporting you control:

After each campaign: sends, delivered, opens, clicks, unsubscribes, revenue attributed in [ESP/Shopify] if tracking is configured. If tracking is broken, milestone 1 includes fixing UTM or integration gaps before we judge performance.

If they want CRO on the site, that is a different job. Email proposals should not silently include landing page redesign unless priced.

Compliance and consent (short, not a law lecture)

One paragraph protects both sides:

I work only with contacts you have permission to email. I include unsubscribe links and physical address where required by your ESP and region. If you need GDPR/LCAN-specific flows, tell me your markets; implementation can be scoped, legal wording remains yours.

You are not their lawyer. You are their implementer.

Sample proposal excerpt

You are on Klaviyo with ~25k Shopify customers and want welcome + post-purchase flows rebuilt. I would audit current flows and tracking in milestone 1 (fixed, 3 days), then rebuild two core flows in milestone 2 with test orders on staging, one revision round per flow, and a short handoff doc.

I do not manage ads or buy lists. You keep ESP billing; I need admin access and a single marketing approver with 48-hour feedback turnaround.

Collaboration and tools

Name how you work:

Drafts in Google Doc or ESP comments; assets from your Figma/brand folder; tasks in Notion/Slack as you prefer.

If they have no brand guidelines, propose a lightweight template milestone instead of improvising every send.

What not to do

Promise revenue lifts without baseline.

Offer measurement setup first.

Agree to blast a cold list.

Decline or redirect; deliverability damage becomes your blame.

Hide that you only write copy but they asked for technical flows.

Split roles or partner; do not fake ESP skills.

Underprice migration + rebuild + campaigns together.

Three projects wearing one hat.

If the post is vague (“email expert needed”)

Use short job post proposal logic: restate goal, propose audit milestone, ask three questions (ESP, list size, main pain: campaigns vs flows vs deliverability).

FAQ

They want Mailchimp and Klaviyo compared.

Offer a paid audit recommendation, not free consulting.

They need design-heavy templates.

Say if you code HTML, use drag-and-drop, or need their designer.

Agency white-label work.

Confirm who talks to the end client and approval paths.

AI-generated copy.

State your policy. Some clients want disclosure; some want human-only.

Before you send

Run the proposal checklist and add:

• List size band or audit milestone if unknown
• ESP named; access and billing ownership clear
• “What I will not do” lines present
• Deliverables split (campaigns vs flows vs migration)
• Reporting metrics match their tracking reality

---

Bottom line: email marketing proposals win when you sound like you have opened a broken account before. Name list size, ESP, limits, and the first milestone. Saves, flows, and revenue talk come after the scope is real.