Plan, launch, test, learn
Discovery covers audience, channels and tracking; launch includes tracking verification; improvement runs as a regular test-and-review cycle.
Every engagement follows the same backbone — discover, plan, build, launch, improve — adapted to the work. Here is what happens in each phase, what you receive and what we need from you.
From first call to continuous improvement.
- 01
Discover
Goals, audience, current state, data and constraints, gathered through a short structured discovery.
- 02
Plan
A written plan with priorities, scope, owners, timeline, budget and the measures of success.
- 03
Build
Assets, campaigns, searches, platforms or models delivered in increments you can review.
- 04
Launch
A controlled start with checks, monitoring and a clear route to fix early issues.
- 05
Improve
Regular reviews of results, lessons and the next set of priorities.
What you receive at each step.
Durations depend on scope; we confirm them in the plan.
Discovery summary
What we learned, the main opportunities and risks, and open questions. We need access to the right people and existing data.
Written plan and proposal
Priorities, scope, responsibilities, timeline, fees and measures. Nothing starts until you approve it.
Reviewable increments
Drafts, designs, shortlists, environments or prototypes shared early, so feedback shapes the result.
Launch checklist
Tracking, quality and rollback checks completed, with named owners for the first weeks.
Review and roadmap
A regular report against agreed measures, with recommendations and an updated backlog.
Change control
Scope changes are discussed, estimated and approved in writing before work changes.
Same backbone, different details.
Intake, search, shortlist, offer
Discovery is the role intake; build is sourcing and screening; launch is the start date, followed by check-ins with you and the hire.
Assess, design, build, migrate, operate
Work is delivered as code with peer review; launches and migrations are rehearsed with rollback plans; operations end with documentation and handover.
Frame, prototype, evaluate, deploy
A short feasibility prototype comes before a full build; evaluation against agreed criteria happens before launch and continues after it.
Process questions.
How long does the discovery phase take?
It depends on scope. A focused discovery for a single service can take a few days; broader programmes take longer. We agree the timeline and who we need to speak to before starting.
Do we have to commit to a long contract?
No. Many engagements start with a defined first phase. Longer retainers or programmes are agreed once both sides have seen how the work goes.
How often will we hear from you?
At a cadence agreed in the plan — commonly weekly updates during build and launch, and a monthly review of results. You can always reach your engagement lead.
What happens if the scope changes?
We describe the change, its effect on timeline and cost, and agree it in writing before the work changes.
Let's build what's next.
Tell us what you're working on and what you want to change. We'll reply with where we would start and who from our team would be involved.