Services

We do the work,
not just advise on it

We get inside your tools, build the thing, and measure what happens. Every piece of work produces a number that either moved or did not.

01

Work out what makes people stay

4 to 6 weeks

Before any new messages go out, we look at who stayed and who left, and pin down the few early moments that decided it. Then we map who each message should reach, on which channel, and how you will know if it worked. Built from your real customer behaviour, not a template.

What you get

  • A clean set of the events worth tracking, named consistently and checked across web and app
  • A simple model of where each customer is (new, active, going quiet, gone) with clear rules for moving between
  • A plan for every automatic message: who it reaches, when, and why
  • The handful of numbers to watch, and how to read them
Best for: Teams who already pay for a messaging tool but are not seeing results. The tool is rarely the problem.
02

Build it in the tool you already have

8 to 12 weeks

We take over your messaging setup, whether that is MoEngage, Netcore, Klaviyo or something else, and get it working. We clean up the tracking, switch off the campaigns fighting each other, and ship the new automatic messages against the plan from step one.

What you get

  • A full review of what is currently running: campaigns, segments, tracking
  • Rules so campaigns stop overlapping and people stop getting double-messaged
  • Six to twelve new automatic journeys across sign-up, first use, staying, and coming back
  • A weekly review of what is working, with changes made off the back of it
  • Notes so your team can run it after we leave
Best for: Teams with a messaging tool that is live but not moving the numbers. You are paying for it already.
03

A focused 90-day push

90 days

A short engagement with a single target: fewer people leaving in the first month, more people getting through sign-up, or old customers coming back. We look, we plan, we build, we measure. You have the result before we leave.

What you get

  • Weeks 1 to 2: dig into your data and name the real problem
  • Weeks 2 to 4: design what to change
  • Weeks 4 to 10: build it and adjust as the numbers come in
  • Weeks 10 to 12: a plain report of what moved, and a handover
Best for: Teams with one specific problem and 90 days to shift it, before committing to anything longer.
04

Fix churn that starts with support

10 to 14 weeks

Not every retention problem is a messaging problem. If people are leaving because support is slow, sign-up is confusing, or nobody notices an account is in trouble until it cancels, this is the layer we work on.

What you get

  • A health score for each account, wired into your help desk
  • A proper sign-up flow that gets ahead of problems instead of reacting to them
  • Clear playbooks for complaints and escalations, so the answer is good every time
  • A short satisfaction check at day 14 and day 30
  • A weekly review of which groups of customers are actually leaving
Best for: Subscription businesses where people leave because of support quality, not lack of interest.
How We Work

From first call to results

01

A short call

30 minutes. We ask about your numbers, your current tools, and what you have already tried. You get a clear read on what is wrong and whether we are a fit.

02

A written diagnosis

A day or two later you get a short write-up: what we think the core problem is, what we would tackle first, and what a realistic result looks like.

03

A scoped proposal

If it makes sense to work together, we send a plan with the work, the timeline, and the cost. No open-ended retainer before we both agree on what you are getting.

04

The work

We start. We work inside your tools, alongside your team, and produce something you can measure. Weekly check-ins. You always know where things stand.

Get Started

The call is free.
The results are not luck.

30 minutes. Tell us where people are dropping off. We will tell you what we would do about it.

No pitch deck · no retainer before diagnosis · a number that moves or nothing