Onboarding sequences
One action per message, not a tour of the whole product. The sequence stops when the user does the thing it was asking for.
Email and CRM
for retention.
You pay to acquire a user once. Keeping that user depends on everything that happens afterwards. Email and CRM are where that work happens, and both depend on product data, so the same team that writes the code sets them up.
- Events Signals before templates
- Records Product activity on the lead
- Delivery Authenticated, warmed, cleaned
- Consent Captured, stored and honoured
Programmes we build
The programme types we build. Most accounts start with a couple and add the rest once the event data is reliable.
Activation nudges
Tied to a missing step rather than to a day count. A person who already invited a teammate never gets asked to invite one.
Trial and renewal reminders
Sent on the dates that matter to the account, with the state of their usage in the message.
Win-back for users who went quiet
Inactivity is an event like any other. We define it with you and write to it once, not every month.
Sales follow up
The message a person would send, with the product activity a rep needs in front of them when the reply arrives.
Measured properlyHow a programme gets built
In this order every time. Skipping the first stage produces a lifecycle programme you cannot rely on.
See the full service map-
Wire the events
A lifecycle programme is only as good as the signals behind it. Signed up, invited a teammate, hit the value moment, went quiet — the product sends these first. That wiring is engineering work and we do it in house.
-
Write the programmes
Now the messages can be about the person rather than about the calendar. Each one drives a single action and stops when it gets it.
-
Make the CRM trustworthy
A CRM full of stale records gets ignored. Fields mapped properly, deduped on import, product activity pushed onto the record. A rep opens a lead and sees what that person did last week.
-
Report on what it kept
Activation rate, retention by cohort and revenue per user. Open rate is a diagnostic, never the goal.
Deliverability, consent and privacy
The floor under every programme. None of it is optional and none of it is billed separately.
- Authentication set up correctly before the first send.
- A warm-up plan for any new sending domain.
- Lists cleaned on a schedule, not after a bounce spike.
- Sending less, to people who want it, rather than sending more.
- Consent captured, stored and honoured.
- Unsubscribes that work on the first click.
Before you ask
Answers as we would give them on a call.
Can you work in our existing CRM?
Yes. We work inside your accounts, not beside them. Fields get mapped, imports get deduped and product activity gets pushed onto the record you already use.
Our product does not send events yet. Where do we start?
That is stage one, and it is engineering work rather than a marketing task. Our own engineers do it, so the work gets finished.
Do you report on open rate?
As a diagnostic only. The numbers that decide anything are activation rate, retention by cohort and revenue per user.
How do you handle consent?
Consent is captured, stored and honoured, and an unsubscribe works on the first click. Our privacy notice sets out how we treat the data itself.
Tell us where users drop off
One sentence about the drop-off is enough. We reply with the events we would wire first, the message we would send, and how we would know it worked.