Five phases. Each ends with something you can use.
Discovery
1–2 weeksWe start by understanding the business: the market, the customer, the existing product surface, and the constraints: commercial, technical, regulatory. The deliverable is a shared, written articulation of the problem we are actually solving.
Definition
1–2 weeksWe translate the problem into a product shape: positioning, IA, the moves we will and will not make, and the success criteria for the engagement. Everything that follows is measured against this document.
Design
3–5 weeksHigh-fidelity design of the surfaces that matter most, usually the two or three customer interactions that carry the product. We design in production-grade tools and against the real stack, so what ships is what was shown.
Build
4–12 weeksProduction engineering against the design. We write the same code we would write inside a company: typed, tested, observable. We ship incrementally. Stakeholders see working software each week, not a milestone at the end.
Launch & handover
1–2 weeksWe hand the work to the team that will own it. That means written documentation, a runbook, a recorded walkthrough, and one or two weeks of paired work with the receiving team. The goal is that the engagement ends and the product does not.
How we work, regardless of phase.
Small teams, full stack.
Three to five people per engagement, each fluent across strategy, design and code. No handoffs that lose context.
Ship weekly, not at milestones.
Working software in your hands every week. Progress is something you can use, not something you read about.
Production from day one.
We build against real stacks and real constraints. No prototypes that have to be re-written before launch.
Leave a team behind.
Every engagement is structured around handover. Documentation, pairing, and a runbook. The goal is durability after we leave.
Three ways we work with teams.
Fixed-scope project
A defined engagement with clear deliverables, milestones and exit. Best for first products, launches, replatforms, and discrete pieces of work where the shape is known.
Embedded team
A small TTM team integrated with your existing product and engineering org, working as if they were inside. Best for in-flight work where you need senior firepower without hiring.
Founder pairing
One or two senior operators working directly alongside the founding team during a critical window: a raise, a launch, a pivot. Strategic, hands-on, time-boxed.