
Current state
Review the existing list and consent information, available evidence, ownership and the practical constraint the work must address.
Plan a clear email journey for enquiries, customers or subscribers, with permission, content and measurement requirements made explicit.

Selected service studies
These editorial studies show the types of decisions and deliverables involved. They are service examples, not client claims.

Review the existing list and consent information, available evidence, ownership and the practical constraint the work must address.

Define the audience segments required for the agreed first scope and record what remains outside it.

Develop the message sequence through reviewable decisions and a defined list of outputs.

Prepare the automation handover and the files, checks or operating notes needed for handover.
Platforms and delivery
The platform must support the consent, segmentation and automation the project actually needs. List ownership and sending reputation are reviewed first.
Explore the main service areas and the platforms or delivery systems that may be used for the project.
Suitable for many campaign and basic automation programmes when list and template needs remain straightforward.

Working process
The proposal names the review milestones. Timing depends on the number of pages and features, content readiness and third-party access.
Agree the audience, business goal, available list and consent information and the decision this project needs to improve.

Industry applications
Email programmes differ according to the relationship with the recipient and the decisions the messages support.

Plan welcome, browse, cart, purchase and retention messages around verified customer events.

Support enquiries, longer evaluation cycles and useful follow-up without buying lists.

Organise updates, events and programme information for permissioned audience groups.
Custom scope / USD
Custom Development. Final quote after scope.
A tailored website feature, application capability or internal tool. The first release is defined before quoting.
User accounts and business state move into application scope. Third-party licences extra.
Read all pricing boundaries ↗Frequently asked questions
Only after ownership, consent, source and suppression requirements are understood. A list should not be treated as usable merely because it exists.
Yes. When both are needed, the proposal sequences shared decisions and states which deliverables belong to each part of the project.
The written proposal names the review stages and included revision rounds. Additional directions or production work are quoted before scope expands.
A concise brief, the available list and consent information, the intended audience, one approval owner and any fixed platform, timing or compliance constraints.
Your next website
Let’s talk about what it needs to do.
Share your brief. We’ll review the scope and reply in writing.