Updated: 6 hours ago
Email Marketing Agency Brief Template and Proposal Scorecard
By Trayan Hristov | Published 16 November 2026

An agency proposal is easy to like when nobody has agreed what it must include. One team prices campaigns. Another includes a flow rebuild. A third assumes your designer will do the creative. The monthly fees look comparable, but the work is different.
I would start with one shared brief. Give each shortlisted agency the same commercial problem, account context, delivery requirements and evidence request. Then compare the proposed work, people and total cost. This guide provides the brief, a weighted scorecard and a worked example you can copy.
This is Thrivelia's buying framework, published by a company that offers these services. The scoring weights and examples are editorial tools, not independent agency ratings or market-price benchmarks. Change them to reflect your business.
A reference question to attach to the brief
Give each finalist permission to describe an anonymised case, but ask the same follow-up. What did the customer buy, what stopped them buying again, which person spotted it and what other explanation did the team rule out? Record who actually made the change and whether that person would be assigned to your account. A category logo alone earns no points for solving your problem.
When to use this agency brief
Use it when you need a team to own some combination of lifecycle strategy, copy, design, campaign production, automation, testing and reporting. It also works as a short request for proposal, or RFP. It is not a request for every agency to do an unpaid account rebuild before you choose.
If your team can already implement and you mainly need diagnosis or senior guidance, use our consultant brief. If you are still building a shortlist, start with the UK email agency comparison or retention agency guide.
Copy this email marketing agency brief
Replace the square brackets with your answers. Mark unknowns as unknown. A proposal based on an invented baseline is less useful than one that includes a clear discovery phase.
1. Business and decision
Brand: [name, website, markets and product categories]. Business model: [one-off purchase, replenishment, subscription or a mix]. We are choosing a partner because [specific problem]. Our main decision is [what should change and why now]. Our internal decision owner is [role].
Example: acquisition has grown, but too few first-time buyers return within our normal purchase window. We need to diagnose the gap and implement a post-purchase programme while maintaining the existing campaign calendar. This is an illustrative brief, not a client result.
2. Baseline and evidence
Available evidence: [store orders, CRM reports, customer cohorts, support questions, research and current journey inventory]. Baseline period: [dates]. Known limitations: [tracking changes, missing data, promotions, new markets or product launches]. Current attribution setting: [platform and window]. Customer outcome we want to understand: [definition and eligible cohort].
Separate a target from an established baseline. A first-to-second purchase target needs customers who have had enough time to repurchase. Ask the agency to explain cohort maturity and the comparison period instead of comparing a recent cohort with one that has had a year to develop.
3. Platforms and account structure
Commerce platform: [ ]. Email and SMS platforms: [ ]. Subscription, loyalty, reviews, support and analytics tools: [ ]. Markets, stores, languages and currencies: [ ]. Known data or integration problems: [ ]. Internal technical owner: [ ].
Identify whether integrations already exist and work. If the brief depends on an event or field that is missing, ask who will create it, validate it and maintain it. A message cannot reliably respond to a customer behaviour that the system does not receive.
4. Work to keep running
Existing campaign calendar: [ ]. Essential flows and service messages: [ ]. Current sender configuration and known deliverability issues: [ ]. Upcoming launches and trading periods: [ ]. Approval deadlines and brand restrictions: [ ]. Work that must not be paused during transition: [ ].
5. Work to change
Priority problems to investigate: [maximum three]. Expected deliverables: [diagnosis, roadmap, specific builds, creative or experiments]. Explicit exclusions: [store development, paid acquisition, customer support, data engineering or other work]. Dependencies supplied by us: [assets, access, developer time, stock and offer information].
6. People, approvals and access
Our commercial owner: [ ]. Day-to-day contact: [ ]. Final creative and audience approver: [ ]. Technical owner: [ ]. Agency roles requested: [strategy, copy, design, build, QA and account management]. Working-hours overlap and escalation route: [ ]. Who may pause a launch: [ ].
Keep the brand's ownership and access responsibilities explicit. Use individual accounts and suitable permissions rather than sharing one login. Check the current Klaviyo user-management documentation for the roles available in your account. Agree removal of supplier access as part of the exit process.
7. Budget and commercial terms
Budget range and billing currency: [ ]. Setup budget: [ ]. Preferred initial term: [ ]. Software and message charges: [included, separate or unknown]. Optional services: [ ]. Additional-work approval process: [ ]. Notice, handover and asset delivery requirements: [ ].
8. Response requested
Please return: your interpretation of the problem; proposed first 90 days; deliverables and exclusions; named delivery roles and capacity; dependencies on us; QA and escalation process; evidence from comparable work; measurement approach; full fees and terms; and questions that must be resolved before committing to scope.
Define the production units before comparing prices
“Eight campaigns and five flows” is not yet a comparable scope. A campaign might be one message in one language, or several market versions with distinct segments and creative. A flow might contain one message or a branching journey with email, SMS and integration work.
For each campaign, specify the concept, channels, market or language variants, copy, design, build, QA, approval and revision allowance. For each flow, specify messages, branches, triggers, exclusions, platform changes and test cases. Ask how new work is prioritised when the agreed capacity is full.
Example scope line: “One post-purchase journey for UK first-time buyers, up to four email messages and two product branches, including copy, design, build, purchase-exclusion logic, QA evidence and handover notes. Subscription-platform changes and additional languages quoted separately.” This describes a unit of work; it is not a universal recommendation for every account.
Request acceptance criteria alongside quantities. A flow is ready when the agreed entry, exit and suppression cases have been checked, the messages render correctly, links work, someone has approved the audience and an accountable owner has accepted the launch. A screenshot of a canvas alone does not show those checks.
Score proposals on the same evidence
Set weights before reviewing prices. Score each criterion from 0 to 5: 0 means absent; 1 is a generic claim; 3 is relevant evidence with some open questions; 5 is a specific, credible response that meets the brief. Record the evidence and unresolved question next to each score.
Calculate each weighted result as score ÷ 5 × weight, then add the results. Treat the total as a discussion aid. A high score should not override a failed requirement, such as unacceptable account access, unavailable delivery capacity or missing platform expertise.
Criterion | Weight | Evidence to request |
Understanding the customer problem | 25% | A reasoned diagnosis and the data needed to test it |
Scope and delivery ownership | 25% | Named roles, production units, dependencies and QA acceptance |
Relevant work and measurement | 20% | A comparable case with dates, baseline, attribution and limitations |
Team fit and operating rhythm | 15% | Meet delivery leads; check availability, approvals and escalation |
Total cost and contract fit | 15% | Setup, recurring fees, extras, term, notice and handover |
Illustrative scores: Proposal A earns 4, 4, 3, 4 and 3 across the five criteria. Its weighted score is 73/100. Proposal B earns 3, 3, 4, 3 and 5, producing 70/100. Neither has automatically won. Ask whether A's evidence gap or B's scope gap can be resolved, then update the score using the answer. These are fictional proposals.
Compare the total commitment, including your team's work
A lower fee may rely on more internal labour or a separate implementation project. Compare the same period and work. Separate agency invoices, platform charges, message costs, external technical work and the internal time needed to make the arrangement function.
Here is a fictional six-month comparison in GBP. Both options are assumed to cover the same agreed outputs. Proposal A charges £3,500 per month plus £6,000 setup, totalling £27,000. Proposal B charges £5,000 per month with no setup fee, totalling £30,000.
Now include internal coordination and production time. If A needs 16 hours a month and B needs four, valued at an illustrative £50 per hour, the six-month internal cost is £4,800 versus £1,200. The combined totals become £31,800 for A and £31,200 for B. The cheaper agency invoice is not the cheaper overall arrangement in this example.
This calculation excludes VAT and shared software costs for simplicity. It is not a market-rate claim, a tax assessment or a prediction of either supplier's results. Replace the assumptions with your actual quotes and internal costs. Our agency pricing guide covers fee models and break-even questions in more detail.
Add these requirements when hiring for a UK brand
Specify your billing currency, required working-hours overlap, approval deadlines and any need for in-person meetings or a particular contracting entity. Serving UK customers does not necessarily mean an agency has a UK office. Verify the requirement that matters to your procurement process.
Ask for customer-facing work that fits your market, product and buying context. British spelling is a basic check. More useful questions concern delivery promises, returns, stock, local offers and the differences between UK and international customer journeys.
For a UK and US business, state which accounts, currencies and calendars are shared. Request a reporting view that identifies each market. Ask your finance team to confirm the applicable tax treatment and your own responsible team to approve consent, audience eligibility and data-handling rules for the actual arrangement.
Use one decision meeting to resolve the remaining gaps
Give shortlisted agencies the same brief and a reasonable opportunity to ask questions. Where an answer changes the scope, share the clarification with all candidates. Ask for an example diagnosis or a walkthrough of relevant existing work; commission a defined paid discovery if a substantial account investigation is necessary.
In the final meeting, ask five questions: What would you investigate first? What would you stop or postpone? Who will actually do the work? What depends on our team? What evidence would make you change the proposed plan? Ask to meet the relevant delivery lead, not only the person presenting the proposal.
Evaluate case studies carefully. Ask what period is covered, what else changed, whether figures are attributed or incremental, what the supplier actually owned and how customer outcomes were measured. A large attributed-revenue number can be useful context without proving that the agency caused all of it.
Turn the chosen proposal into a first-90-day plan
Days 1–30: validate access, data, the current journey inventory and the commercial baseline. Agree immediate risks, first priorities and who approves changes. Document the difference between work needed to keep the programme running and work intended to improve it.
Days 31–60: implement the agreed priority changes, record QA and launch dates, and start the measurement plan. Maintain a change log so an unusual trading week can be interpreted alongside promotions, inventory, acquisition and site changes.
Days 61–90: assess delivery, early performance and unresolved dependencies. Keep longer customer purchase cycles in view. A 90-day review can judge operating quality and leading signals even when the cohort needs more time before a repeat-purchase outcome is mature.
Define exit requirements before the engagement begins: account ownership, editable assets, flow documentation, access removal, outstanding tests and a handover meeting. Use our agency handover checklist to make the transition explicit.
Common questions
Do we need a formal RFP?
Not always. A smaller engagement may only need a concise brief and a comparable written scope. A complex multi-market account may need a structured RFP with procurement and technical review. The useful part is agreement on the work and decision criteria.
Should we choose the agency with the highest score?
Use the score to expose trade-offs and missing evidence. Check mandatory requirements separately, resolve material gaps and use judgement. The suggested weights are not a validated predictor of future results.
Can this brief be used for Klaviyo or subscription retention?
Yes. Name the actual platforms and specify the implementation boundary. For subscription retention, clarify who owns billing, cancellation, customer-portal and integration changes, alongside the messaging. A lifecycle proposal should not silently assume another team will deliver those dependencies.
What to keep after the pitch
Keep the version of the brief every finalist received, the assumptions each team made and the first decision agreed with the winner. Use these at the first monthly review.

.png)
Comments