For growth leaders
More experiments into production.
Growth ideas need engineering time to become experiments. I build the landing pages, product changes and measurement, using agents across research and implementation so the work can move alongside the core product roadmap.
Alongside 100+ client engagements.
A few teams I’ve worked with:
The context
A useful experiment needs a product change and a way to measure it.
That may mean editing an onboarding flow, connecting a partner channel or repairing event tracking before a test can begin. I work through those dependencies with your growth and engineering teams, then build the agreed changes.
My background spans paid acquisition, attribution, product analytics and software engineering, including work for Groupon, The Motley Fool and Contra. We define the metric and baseline before implementation, then agree how long the experiment needs to run before drawing conclusions.
Areas of work
From the hypothesis to the measurement
- 01
Activation and conversion
Build the onboarding, landing page and product changes behind the metric you need to improve.
- 02
Acquisition and partnerships
Develop channel tooling, research workflows and conversion paths around a defined commercial opportunity.
- 03
Lifecycle and retention
Connect customer behaviour, billing and messaging so the next useful intervention can be tested.
- 04
Measurement and decisions
Repair instrumentation, establish a baseline and make the result clear enough to inform the next investment.
Work that’s live
Product and growth projects
Recent client work includes publishing, organic acquisition and commerce for Vouchernaut, and discount-extension measurement and attribution for Benson. The build accounts describe the systems behind the work.
Publishing & commerceVouchernautA UK shopping and editorial business, including guides, offers and a browser extension.vouchernaut.com
Discount attribution & marginBensonSoftware for measuring how discount extensions affect attribution and store margins.trybenson.com
- Live products in the Vouchernaut rebuild
- Days for the Vouchernaut rebuild
- Specs for the Benson rebuild
- Commits in the Benson rebuild in under a fortnight
From clients
What working together was like.
Each review links to the profile it was left on, so you can check it.
Doug was incredible to work with. He operated quickly & efficiently, and even proposed ways to improve the feature to exceed our expectations. 10/10!
Allison NultyHead of Product, ContraDoug is a pro. I'd hire him again for any future marketing & technology initiatives.
Brian TigheHead of Technology, The Motley FoolSmart, fast, and trustworthy.
Shelby StevensFounder, Snacker.ai — Techstars alumni
Ways to work together
Choosing an engagement
A working day can cover a research or reporting workflow. A sprint covers the implementation of one experiment. An ongoing partnership supports a longer testing programme.
- Working day
Team adoption
Build and test one research, campaign or reporting workflow, with team ownership and a measurable baseline.
£2,500 fixed - Focused release
Delivery sprint
Put the onboarding change, integration or tooling behind your next growth experiment into production, with measurement in place.
From £10,000 per project - Working with your team
Ongoing partnership
Build and run the growth experiments your team needs, with monthly scope across engineering, measurement and agent adoption.
From £12,000 a month
Your starting point
Review your growth workflows
The 2-minute scorecard covers research, production, reporting and other recurring work. It suggests areas to investigate based on your answers. No email needed.
How do landing pages and experiments get made?
We start with the commercial goal and choose a problem that can be tested. We agree the baseline, implementation and success measure, so progress is judged by the result of the work.
Yes. I work across product engineering, integrations, lifecycle systems and measurement. We agree access, dependencies and review with your product and engineering team before implementation.
Yes. We inspect the current instrumentation and definitions first. Any gaps needed to evaluate the change become part of the scope, with ownership clear at handover.
No. The commercial problem determines the implementation. Agents can accelerate research, production and operating workflows; a direct product or engineering change may be the right answer to the underlying constraint.
We agree the release timeline after checking the scope and dependencies. The time needed to observe a result depends on traffic, the metric and the size of the change. We agree how it will be evaluated before starting.
Discuss a project
Discuss an experiment.
A free 30-minute call to review the hypothesis, what needs building and how you would evaluate the result.