top of page
Nov 8
6 min read

Updated: 10 hours ago

Who Runs Your Email Marketing Account After the Pitch?

By Trayan Hristov · Thrivelia · 8 November 2026

Who owns your email account?. Strategy: Choose the next decision. Build + QA: Make the journey work. Release: Confirm what is live

The person who understands your business during the sales call may not be the person writing the next brief. Before choosing an email marketing agency, ask how that understanding reaches the people making daily decisions.

I would start with a named owner for the customer strategy, a realistic production scope and a visible decision process. You should be able to follow a priority from the original business question to the work that shipped and the decision made afterwards. This guide shows what to ask for and how we approach that responsibility at Thrivelia.

A reference check that gets past the sales team

Ask a former client for the last idea the account manager brought them without a brief. Then ask when the same person told them to stop a campaign that was generating attributed revenue. Those two answers reveal whether the manager can initiate work and challenge it. Put the names, decision rights and expected contact time into the proposal.

Define the responsibility you are buying

A brand can have a good designer, an experienced coordinator and a full campaign calendar while still lacking someone who decides what the programme should improve. Another brand may know its priorities and need reliable implementation capacity. The proposal should distinguish those situations.

Write down the missing decisions before comparing headcounts: which customer group matters, which product deserves a different explanation, where the journey fails, what should be tested and what the result would change. Then name the person responsible for each decision.

Responsibility

What to establish

Evidence to expect

Lifecycle direction

Who sets and challenges priorities?

A prioritised customer roadmap and reasons for the sequence.

Copy and design

Who turns the brief into accurate, recognisable messages?

A reviewable version with approved product and offer information.

Implementation

Who builds eligibility, events, messages and destinations?

A traceable account change and working customer path.

Release QA

Who can approve activation?

A release record, test results and unresolved dependencies.

Measurement

Who explains the result and proposes the next action?

A decision log with dates, definitions and limitations.

One person can hold several responsibilities. The important capacity question is whether that person can cover the agreed workload, including maintenance and unexpected issues. Founder involvement, holiday cover and response commitments should be specified in the engagement.

Ask to see how product knowledge is maintained

The team needs more than a brand questionnaire. It needs access to the product experience, current commercial priorities, customer questions and the people who know what is changing.

For a clothing brand, that might mean understanding fit, returns, fabrics, stock and the differences between first-time and repeat buyers. For software, it includes using the product, understanding the owner and invited-user journeys, and maintaining an event dictionary as features change.

Ask how new launches, stock changes, product claims and customer feedback reach the lifecycle lead. A recurring review should update the working brief. For each language, identify who checks natural expression and product accuracy, whether a native reviewer is included and how much review remains with your team. Translation capability and a fully outsourced local-language service are different scopes. Otherwise, a team can keep producing polished messages around an increasingly outdated understanding of the product.

Use one decision queue

A useful queue connects finding, hypothesis, brief, production, QA, release and review. Each item should show its customer group, owner, dependencies and next decision. Keep verified defects separate from proposed experiments: a missing welcome connection and a new welcome angle require different acceptance criteria.

Consider an illustrative welcome problem. Subscriber growth looks healthy, but few new subscribers reach the first message. The first assignment is to trace a valid signup through its source, profile, consent, list and entry rules. If that route fails, rewriting the email cannot resolve the entry problem. If it works, the team can move to a properly defined offer or content test.

Use the same queue when your internal team creates the emails. The external partner can own diagnosis, briefs and review while your team owns production. Agree that split using our consultant briefing guide.

Separate creative approval from permission to launch

A design approval confirms a version of the creative. Activation also needs the correct audience, event timing, product data, offer, destination and purchase exits. Name the final release owner and record the approved version.

Before a seasonal launch, test a customer who buys during a delay, a repeat buyer, an unavailable product and a customer receiving another journey. Keep a way to stop the affected message if the observed path differs from the approved one. Our flow monitoring guide explains the checks that continue after launch.

Inspect work that demonstrates the promised responsibility

Ask for a comparable customer decision, the actual work and its documented outcome. A creative gallery shows design capability. A launch record shows implementation. A properly defined performance comparison answers another question.

Our LunHer project separates four welcome concepts approved in April 2026 from flow batches 1–2 confirmed live in July. Our Goldwing Parts case distinguishes core live journeys from the remaining migration handover. Those are inspectable operating milestones.

The perfectwhitetee case shows a broader programme, including customer analysis, capture, message development and flow consolidation. Its reporting periods remain explicit. None of these cases establishes that the same staffing or result is guaranteed for another brand.

Make the reporting meeting produce a decision

A useful review explains what changed, what shipped, what happened and what the team will do next. Compare a small set of measures appropriate to the work, such as eligible entrants, delivery, revenue per delivery and customer progression. Keep attribution settings and observation windows visible.

Ask what the agency would stop doing after a weak result. Ask what it needs to learn before scaling a promising one. A report earns its place when it changes the next priority, rather than merely documenting activity.

What combining creative and technical teams changes


Creative and technical teams working from one brief can reduce the gap between the promise in the email and the customer's actual experience. The copywriter needs to know which product, offer and customer state the build can reliably support. The implementer needs to understand which parts of the message change when the customer buys, returns an item or asks for help.


Consider a fictional launch offering early access to existing customers. Strategy defines the eligible customers and purpose. Creative explains the benefit and uses the right product information. Implementation checks membership and destination access. QA tests a customer who qualifies, one who does not, and someone whose state changes before sending. If each team only approves its own fragment, the email can look correct while the promised access fails.


A shared brief should carry the audience, customer problem, source fields, message variants, offer rules, destination, exclusions, owner and acceptance criteria. Use a single version identifier across the approved creative and build. When stock or offer terms change, identify which messages and journeys depend on that information before replacing one image in isolation.


Thrivelia combines these responsibilities within agreed engagements through its team across London and Sofia. The proposal should say which creative, implementation, testing and ongoing monitoring work is included. If your team supplies design or development, we can discuss a split scope with explicit handoffs. The benefit comes from coordinated decisions and verified delivery, not from claiming every specialist must work in the same office.


For ecommerce, review the Klaviyo audit checklist. For software, use the SaaS event brief. Ask a prospective partner to walk through a real brief-to-release example and explain who checks the complete customer path.


What the account owner should put in writing

Ask for the next customer decision, the evidence behind it, the person authorised to act and the date the team will review the outcome. Put those four details in the same place as the creative brief.

The right scope may be advisory support, a defined rebuild or ongoing delivery. Bring your current calendar, flow inventory and one commercial priority. We will discuss the responsibilities your team needs covered and put the proposed ownership into the scope. Compare the ways to work with Thrivelia, then apply to work with us.

Questions to resolve before signing

Should the founder personally run every account?

Ask for the actual working team, senior decision owner and agreed founder involvement. A founder-led pitch does not establish who handles strategy, implementation or review after onboarding.

Can we keep our designer and hire for strategy?

A consulting or hybrid scope can retain your production team while assigning diagnosis, priorities, briefs, QA and measurement explicitly. The proposal should define which responsibilities Thrivelia accepts and which remain internal.

What should a weekly review include?

Review the priority, changes released, observed customer path, performance evidence, unresolved dependencies and next decision. The frequency and depth should fit the scope and the customer buying cycle.

 
 
 

Recent Posts

See All

Comments


Commenting on this post isn't available anymore. Contact the site owner for more info.
bottom of page