How we work

How an engagement actually works.

We run every engagement the same way: diagnose first, then decide what to build and who builds it. That sequence matters. Businesses that skip diagnosis and go straight to delivery end up with software that solves the visible problem while the structural one compounds underneath.

This page documents the process and the capabilities behind it. All of it, plainly stated.

The engagement process

Four phases. Always in this order.

The phases are not bureaucracy. They are the mechanism by which we avoid building the wrong thing. Compressing them produces faster output and worse outcomes.

Phase 01

Discover

Typically 2–4 weeks

Discover is the diagnostic phase. We come from outside the system and look at what it has actually become, not what the strategy document says it is or what the leadership team believes it is. We use our own diagnostic lens: five operating levers every scaling business pulls, plus three amplifiers that intensify them.

The output is a written diagnostic covering what we found, how the levers rank by severity, which problems compound which, and a sequenced set of recommendations. It is a standalone deliverable. Some clients use it to act without us. Most use it as the foundation for everything that follows.

What you experience

Structured interviews with the people who actually run the business. Document review. A written diagnostic with no softening: we tell you what we found. One debrief session to walk through the findings and answer questions.

Phase 02

Design

Typically 2–6 weeks

Design translates the diagnostic into a concrete plan: what gets built, in what order, to what specification. We work through architecture, user experience, technical approach, and scope in enough detail that delivery can proceed without ambiguity. The goal is shared clarity between your team and ours about exactly what we are building and why. Not a thick document.

If the diagnostic revealed that some of the problems are not software problems, we say so here. This is where we determine whether a technical solution is the right lever, or whether process, people, or structural changes should come first. We do not build software to avoid a harder conversation.

What you experience

Collaborative workshops to define scope and priorities. Wireframes and user flows for anything user-facing. A technical architecture document for anything infrastructural. A phased delivery plan with honest estimates rather than optimistic ones.

Phase 03

Deliver

Scoped per project — typically 8–24 weeks

Deliver is the build phase. We work in short cycles. You see working software throughout, not a big reveal at the end. We write production-quality code from day one. There is no MVP shortcut that produces a throwaway prototype; what ships at the end of each cycle is the real product, tested and deployable.

Scope is fixed at the start of Deliver. New requirements will emerge. When they do, we capture them, assess their impact, and make an explicit decision together about whether to include them in scope or park them. Scope creep is not a technical problem; it is a discipline problem. We hold the line on your behalf.

What you experience

Weekly progress updates. Working software deployed to staging at the end of each cycle. A clear definition of done agreed upfront, with no moving goalposts. Direct access to the engineers building your product, not a layer of account management between you and the work.

Phase 04

Evolve

Ongoing — retainer or per-project

Evolve covers everything after initial delivery: iteration cycles that follow launch, measurement of whether what was built is actually working, and decisions about what to build next based on real data. Most businesses treat post-launch as maintenance. We treat it as the phase where most of the value is determined. The feedback loop from real users at scale is the highest-quality signal you will ever have.

Evolve engagements run either as a retainer (ongoing availability for a fixed monthly commitment) or as discrete project phases scoped and delivered the same way as Deliver. We do not accept retainers where the deliverables are undefined. The work always has a clear outcome, even in a continuous relationship.

What you experience

Monthly reporting on the metrics that matter for what was built. Structured review sessions to assess what the data says and decide what to prioritise next. A team that knows your system deeply enough to move fast without introducing risk.

What we can build

After the diagnosis, here is what we deliver.

These are the seven capability areas we draw on. They are not standalone service offerings. They are the technical disciplines behind the work the diagnostic recommends. A single engagement typically draws on two or three of them.

How to start

Four steps from first contact to kick-off.

01

Book a call

A 30-minute conversation. You describe what you're dealing with; we ask questions. No pitch, no pressure. The goal is to establish whether we're looking at a problem we can help with and whether there's a fit worth pursuing.

02

Scope call

If the first call warrants it, we schedule a longer scoping session (typically 90 minutes) to understand the business, the problem, and the constraints in enough depth to propose a Diagnostic. This session is free. We bring specific questions. You bring honesty about what's actually happening.

03

Statement of Work

We issue a written SoW covering scope, deliverables, timeline, and price for the Diagnostic phase. One round of comments. Once signed, we schedule the kick-off. There are no lock-ins. Each phase stands alone and you decide whether to proceed at each gate.

04

Kick-off

We start. You get a named point of contact, a shared workspace, and a clear schedule for the engagement. From here we work the process described above. No surprises, no handoffs to a junior team you haven't met.

Ready to start

The first call is 30 minutes. You describe the problem; we ask questions. Neither of us will know if there's a fit until we talk.