Project, retainer,
or embedded.
Different problems need different shapes of engagement. We keep the models simple: clear scope when the finish line is known, continuity when the work compounds, and embedded support when your team needs us in the room.
Choose the right shape
Three ways to work with us.
Project
Best when the scope is clear and the outcome matters more than seat time. A fixed objective, a defined plan, and a clean handoff at the end.
Best for
- A new product, redesign, launch, migration, or delivery sprint with a concrete finish line.
- Teams that need focused momentum without committing to a long-term engagement on day one.
- Work that benefits from a clear scope, milestones, and a defined delivery window.
Typical rhythm
Discovery, scoped plan, milestones, weekly updates, then handoff.
Retainer
Best when the roadmap keeps moving. We stay close to the product over time and help design, ship, optimise, and steady the system as priorities evolve.
Best for
- Ongoing product improvement, growth experiments, infrastructure hardening, or design/system maintenance.
- Founders and teams who need a high-context partner month after month, not a new onboarding cycle every quarter.
- Work where speed comes from continuity and decisions compound over time.
Typical rhythm
Monthly planning, weekly execution cadence, shared priorities, and continuous iteration.
Embedded
Best when you need us inside the team. We plug into your operating rhythm, collaborate in your tools, and work alongside product, engineering, or leadership with direct accountability.
Best for
- Critical initiatives where close collaboration matters more than a separate agency lane.
- Teams that need senior design, DevOps, growth, or build capacity without hiring full-time immediately.
- Situations where speed depends on being in the room for decisions, not waiting for handoffs.
Typical rhythm
Integrated into your standups, planning, tools, and shipping cycle.
How engagements run
We do not optimise for looking busy. We optimise for clarity, cadence, and visible progress.
Every engagement starts with diagnosis, moves into a clear plan, and stays legible as the work unfolds. You should always know what is being solved, what changed this week, and what comes next.
Operating principles
What stays true in every model.
Start with pressure-testing
We begin by diagnosing the real constraint, not just the symptom you first felt. Sometimes that changes the brief. Good.
Show the work early
No black boxes. You see drafts, systems, dashboards, and trade-offs as they happen, while there is still time to steer.
Keep ownership crisp
Clear outcomes, clear decision-makers, clear deliverables. Ambiguity is expensive; we try not to bill you for it.
Leave things handover-ready
Whether we stay or not, your team should be able to run what we built. That means legible systems, documentation, and sane defaults.
Not sure which fits?
That is normal. Most teams do not need a pricing menu first. They need the right shape of help for the problem in front of them.
Tell us the goal, the constraint, and the urgency.
We will tell you candidly whether this is better handled as a scoped project, an ongoing retainer, or embedded support inside your team. If the right answer is "none of the above", we will say that too.
Start the conversation →