Hands-on Growth Support
Fewer decks. More shipped experiments.
I own your activation, retention and monetisation experiments end to end, from hypothesis to prototype to results. For founders and lean teams where nobody owns product growth.
Who this is for
Teams who know growth needs an owner, and don't have one yet.
- Solo founders doing everything themselves, who want someone to take the experiments off their plate.
- A PM stretched across products who wants paywall and lifecycle experiments run properly, not squeezed in.
- Teams paying for Superwall, Customer.io or OneSignal who never got round to switching them on.
- Anyone who has had an audit and now needs someone to actually run the roadmap.
How we split the work
I lead the strategy, data, experiment design, prototypes and user interviews.
Where your setup allows, I build directly:
- Paywall configs in RevenueCat or Superwall
- Push and email journeys
- Web funnels and landing pages
- Dashboards
You, your developer, or Claude Code and Lovable bring the changes live.
Core app code stays with your developers or AI tools, unless you want me in it.
How a sprint works
Two-week sprints against 2 to 3 focus metrics. No status meetings for the sake of it.
- A sprint call every two weeks. We review what shipped, what we learned and what's next, against the 2 to 3 metrics that matter right now.
- I pull the data myself. You don't need to prepare reports for me.
- Every test gets a volume check first. Enough traffic for an A/B test, or is a before/after read the better call? I decide that before we build anything.
- Slack for quick decisions, so nothing waits two weeks for an answer.
- Everything documented in your tools. Every experiment, result and next step, so you own it.
A sample first month
Every app is different, but the rhythm often looks like this.
-
Onboarding prototype
A clickable onboarding flow that changes by user stage, ready for a developer to build.
-
Day-3 push sequence
Written and set up in their push tool, aimed at the users who go quiet after the first session.
-
Five cancellation interviews
Conversations with users who cancelled, to hear why in their words, not ours.
-
Paywall test
Live once the onboarding change has shipped, so we know which change moved what.
Your first 30 days
What I personally deliver, before you've had time to wonder what you're paying for.
- Week 1
- Access, a data pull, and a walk through your app as a brand new user.
- Week 2
- Interviews with 5 users who cancelled, and your activation metric defined: first meaningful value, not onboarding completion.
- Weeks 3 to 4
- The first experiment specced, prototyped and live, with a readout date in the calendar.
Onboarding completion isn't activation.
A user who taps through every onboarding screen hasn't got anything yet. Activation is the first moment a user gets the result they came for, and the habit that follows in the first 7 days.
So I look at both: first value (the moment it clicks) and habit forming (days 1 to 7). Fix one without the other and the retention curve still drops.
I talk about this in "Your onboarding completion rate is lying to you".
Not activation Finished onboarding
First value Got the result they came for
Habit Came back for it in days 1 to 7
Scope and price
Part-time support on a 3-month minimum, starting after an audit, so we both know what we're fixing before you commit.
Need more? I take on interim Head of Growth roles, and I'm open to permanent product growth roles too, depending on availability.
What I don't do
Paid acquisition, ASO and brand. Core app code stays with your developers or AI tools, unless you want me in it.
I work on everything after the install: activation, retention and monetisation. Paid acquisition, ASO, influencer and brand aren't my lane, and I'll tell you who to call when that's the real problem.
Questions people ask
We don't have much dev time.
That's normal. I start with low-dev-lift wins: copy, question order, paywall configs and lifecycle messages. When something does need building, I make the prototype clear enough to hand straight to a developer or Claude Code.
Our volume is too low for A/B tests.
I check before every test. When there isn't enough volume for an A/B test, I use a before/after read backed by user evidence instead, and I'll tell you which one we're running and why.
Do I have to commit to three months upfront?
No. The Growth Audit is a standalone decision point. You decide once you've seen the diagnosis and the roadmap.
We've been burned by freelancers before.
Everything lives in your tools and is documented as we go: every experiment, result and next step. Nothing depends on me, and you can see the work at any point.
Can you do more than part-time?
Yes, depending on availability. I take on interim Head of Growth roles, and I'm open to permanent product growth roles too.
Daphne was all in from day one. She dug into our onboarding, paywall, and Mixpanel data, demoed the app herself with friends, and built a detailed FigJam board breaking down every onboarding step: what worked, what didn't, and how we compared to competitors. She pinpointed the specific friction points holding back activation, then followed up with implementation notes, articles, and best practices. She went above and beyond the whole way. I thoroughly enjoyed working with her and would recommend her to any subscription app founder serious about growth.