How it works
From brief to send, clearly.
A straightforward process designed around your calendar and your team’s review cycle. Clear scope at the start, careful QA at the end, and no surprises in between.
Project phases
-
Brief & scope
We review the designs, platform, audience and deadline, and agree on the email clients that matter. You get a written scope covering deliverables, review rounds and timing before any work begins.
- Designs or wireframes
- Platform and account access, when needed
- Target email clients and devices
- Copy, links and tracking conventions
-
Build
Hand-coded development against the scope, with the structure, fallbacks and accessibility the email needs. Questions come early, so assumptions don’t become rework.
- Table-based, responsive HTML
- Outlook and dark-mode handling
- Personalization and dynamic content
- Platform setup, when in scope
-
Review & refine
You review a live preview and send consolidated feedback for each agreed round. Changes are made and confirmed against the list, not from memory.
- Shareable preview links
- Consolidated feedback rounds
- Change notes for each revision
-
QA
Rendering, links, images-off views, dark mode, personalization and copy are checked against the agreed list, in the clients agreed for the project.
- Client and device review
- Link and tracking checks
- Accessibility review
- Test sends through your platform
-
Deliver & support
Final files or configured templates, with notes on anything your team should know. Questions after delivery are welcome, and ongoing partnerships pick up the next piece of work.
- Production files or platform setup
- Build notes and usage guidance
- A clear point of contact afterwards
Working together
Easy to work with, by design.
-
A written scope, first
Deliverables, review rounds and timing are agreed before work starts, so everyone is working to the same plan.
-
Questions early
Anything unclear in the designs or data is raised at the start, not discovered at the end.
-
Consolidated feedback
One combined set of comments per round keeps revisions fast and avoids conflicting changes.
-
Plain-language updates
Status, decisions and anything that changes are shared clearly, in writing.
Questions
Good to know.
How does a project start?
Book a call or send a brief through the contact page. We’ll ask about the designs, your platform, the email clients that matter and the deadline, then come back with a written scope.
What do you need from us?
Approved designs or wireframes, final or near-final copy, links and tracking conventions, and access to your platform if setup is part of the work. A list of your audience’s most-used email clients helps focus QA.
Which email clients do you check?
The ones agreed for your project, based on where your audience reads email. The list is written into the scope, and QA covers exactly that list.
Can you work inside our platform?
Yes, when it’s part of the scope and you provide access. Otherwise we deliver production-ready files your team can load.
Do you work white-label for agencies?
Yes. We can work behind your agency, follow your conventions and deliver work for you to present. Confidentiality is agreed up front, and NDAs are welcome.
Is there a minimum commitment?
No. Projects are scoped individually. Ongoing partnerships are available for teams with steady volume, but they’re never required.
Choose how you’d like to work
Project-Based Development
A defined piece of work with a written scope: one complex campaign, a modular template system, a platform migration or a QA review.
Discuss a ProjectOngoing Production Partnerships
Reserved development and QA capacity around your campaign calendar, for teams and agencies with a steady flow of email work.
Explore a PartnershipStart a conversation
Let’s make your next send exceptional.
Whether you’re planning one complex email build or looking for a dependable production partner, we’re ready to hear what you’re working on.