Package
Experimentation Programme Build
A testing engine your team owns, built in 8–12 weeks.
- Duration
- 8–12 weeks
- Format
- fixed scope, alongside your team
- Best for
- teams with traffic and tools but low trust in results
Is this for you?
- Tests run, but results aren't trusted.
- There's no agreed prioritisation.
- "Winners" get shipped and nothing moves.
- You're about to hire or grow a CRO team.
Probably not for you if…
- You have no product or engineering capacity to run tests over the next quarter.
What's included
- prioritisation framework tied to commercial value
- test design standards
- statistical guardrails (sample size, stopping rules, guardrail metrics, SRM (sample ratio mismatch) checks)
- QA process
- governance and reporting
- team training
- the first 3–5 experiments launched with your team
What you get
- A programme playbook
- your team can run.
- Templates
- test brief, readout, roadmap.
- A decision log.
- What was tested, what was decided, and why.
- A trained team.
- The people who will run the engine after we leave.
How it runs
Sequence fixed, dates set with you at kick-off.
- Weeks 1–2
current-state review and standards.
- Weeks 3–6
process, tooling and first experiments.
- Weeks 7–12
further experiments, governance and handover.
What it isn't
- a test-volume promise. We'd rather you ran fewer tests you can act on.
Pricing
Fixed fee, depending on team size and tooling, scoped after a discovery call.
Related
Next in the ladder
Optimisation Partner
Rolling, 6-month minimum. Research, test and decide, every month.
If conversion matters to your P&L, let's talk.
A 30-minute call to understand your funnel and whether a Diagnostic makes sense. No pitch deck.