Define the right problem.
Review the current website, customer journey and operations. Agree on goals, scope and priorities.
Deliverable: shared project plan02
Email Marketing
From a first hello to a lasting relationship.
How can we help?
Welcome sequences, abandoned cart flows and campaigns. We build content, segmentation and automation around your customer journey.
Let’s talk about your project
Linen dressExplore the collection→
01Welcome
✓02Interest
✓03Return
✓What we work on together
- Customer segments and consent-based communication
- Welcome and abandoned cart flows
- Content calendar and performance review
Delivery and review
We agree on scope, deliverables and review criteria before work begins. Tools and timelines are selected around the needs of your project.
Our approachFrom the first idea to continuous improvement.
Define the goal, deliverables and measurement together. Each step informs the next, turning an ambition into a clear working process.
Design an experience that works.
Bring structure, content and interface together. Make key user journeys tangible before development.
Deliverable: approved experienceGo live with a clear checklist.
Check mobile layouts, links, forms and measurement. Release in planned, recoverable steps.
Deliverable: tested releaseLearn from the evidence.
Review traffic and conversion data against the goals. Prioritise the next experiment by impact and effort.
Deliverable: next-step planCresvona / FAQ
What you need to know before deciding.
A productive partnership starts with clear expectations. Here are practical answers before our first conversation.
Discuss your project scopeWhich email flows should come first?
After reviewing list sources and consent, we prioritise welcome, cart recovery or post-purchase communication against business goals. Entry, exit and sending conditions are defined for each flow.
Can we keep our existing email platform?
We review the tool, store integration, segments and data quality. Improving the current setup may be preferable to migration. Licensing and any data transfer are scoped separately.
Is open rate the main success metric?
Open rate alone is insufficient. Clicks, orders, flow exits and unsubscribes are considered together. Attribution windows and store records are reviewed before interpreting revenue.
How is the project priced?
Page and language counts, product data, design and integrations determine scope. Setup and development are considered separately from ongoing services. Media spend, platform subscriptions, paid themes and apps are third-party costs to clarify separately in the proposal.
When can we start and finish?
Timing depends on content readiness, catalogue size, migration, integrations and approval cycles. Discovery produces a phased plan with dependencies. We establish a realistic scope before committing to a delivery date.
How are accounts, code and support handled?
Access to stores, domains and ad accounts, code handover, documentation and maintenance responsibilities should be agreed in writing in the proposal. Post-launch support and further development need a separate scope, duration and pricing arrangement.