How the work runs.
Five stages. The proportions shift — sometimes the audit is the whole engagement — but the order does not, because each one depends on the last being honest.
The sequence
-
Audit
We get read access to the real account and look at what is actually happening: authentication records, sending reputation, list health, automation logic, the last ninety days of sends and what they returned. Short, fixed-price, and the stage most likely to change what the project turns out to be.
-
Plan
Findings become a sequenced programme: which messages, to which audiences, on which channels, in what order, and what each change is expected to move. Anything uncertain is marked uncertain rather than smoothed over.
-
Make
Copy, art direction and build happen together rather than in a relay. Writers see the template constraints, designers see the platform's module limits, and the developer is in the room before the design is signed off — which is why our builds rarely come back for rework.
-
Send
Loaded, scheduled, seed-tested and QA'd on real devices and real clients. Anything touching a live list has a rollback and a hold point defined before it goes near a send button.
-
Read and iterate
Results against the expectations set in the plan — including the ones we got wrong. Tests are designed to produce a decision, not a percentage, and what we learn goes back into the programme rather than into a deck.
Ways to work together
Fixed scope, fixed price
The audit and plan stages on their own. You get a written assessment and a sequenced programme that is yours whether or not we do the work. Most relationships start here.
A defined piece of work
A migration, a programme rebuild, a template system, a deliverability recovery. Priced against the plan and finished with a handover.
Ongoing programme support
An agreed block of capacity each month for teams that send continuously — creative, deployment and monitoring. Renews monthly.
You create, we send
For teams whose strategy and creative are already strong and who need a reliable pair of hands on the platform. Build, load, QA, deploy, report.
What we need from you
Engagements go sideways for predictable reasons. These are the ones we head off at the start.
Real access
Read access to the sending account during the audit, not a screenshot of the dashboard.
One decision-maker
Someone with the authority to approve copy and a send, available at short notice.
The constraints we cannot see
Legal review, a contract, an immovable date, a stakeholder with a strong opinion about subject lines.
In return: no surprise invoices, no work we cannot justify, and a direct answer when you ask whether something is going well.
Start with an audit.
Fixed scope, fixed price, and a written plan at the end that is yours either way.