Approach
Every engagement is designed to end.
Four phases, in the same order, whatever the work is. The last one is the point: a client who no longer needs us is the outcome we are optimising for, and the only kind of reference worth having.
- 01
Weeks 1–2
Diagnose
Find the real constraint before spending a dollar against the wrong one.
We interview the people who actually do the work, read the systems rather than the org chart, and look at your numbers. Most engagements surface a constraint different from the one in the original brief. Better to learn that in week one than in month six.
Leaves behind
- Written diagnostic
- Ranked constraints
- Go / no-go recommendation
- 02
Weeks 2–4
Direct
Commit the direction in writing, with the tradeoffs stated out loud.
A decision that lives only in a meeting is not a decision. We put the thesis, the sequence, and the cost of each path on paper, then stress-test it with the people who have to execute it. What we disagree about, we write down too.
Leaves behind
- Strategy memo
- Sequenced plan
- Named owners
- 03
Weeks 4–12
Build
Ship in fixed-scope phases that each end in production.
Work is cut into phases short enough to hold in your head. Each one lands something real and ends at a decision point where continuing is a choice, not an assumption. Scope changes get priced when they are proposed.
Leaves behind
- Working software, weekly
- Live production system
- Instrumented metrics
- 04
Final 2 weeks
Transfer
Leave your team able to run it without us.
Every engagement is designed to end. We hand over source, infrastructure, documentation written for whoever inherits it, and a working session with your team or your next vendor. Continuing with us should be a preference, never a dependency.
Leaves behind
- Handover package
- Runbooks
- Team walkthrough
Operating principles
The rules we do not bend for a signature.
These have cost us work. That is roughly the point. They are what makes the engagements we do take worth taking.
The diagnostic comes first
We will not quote a build before we understand the constraint. Firms that skip this step are selling capacity, not judgment.
Written beats spoken
Recommendations, tradeoffs, and disagreements go on paper. Documents can be argued with six months later; a slide read aloud cannot.
Small and senior
The people in the first call are the people doing the work. There is no bench to keep busy and no hand-off to a team you have not met.
You own the output
Source code, infrastructure, accounts, and documentation are yours. We do not build dependencies on ourselves and call it a relationship.
Fixed scope, priced changes
Phases have a defined end and a defined price. When scope moves, and it does, it gets priced at the moment it is proposed.
We say no
If the work does not need doing, or another firm is the better fit, we will tell you. A declined engagement costs less than a bad one.
In practice
What working with us actually feels like.
There is a weekly written update whether or not there is a meeting, and it says what moved, what did not, and what we are worried about. Bad news arrives early and in writing. A schedule slip you learn about in week three is a problem you can still solve.
You get direct access to the people doing the work, not an account manager relaying questions. Decisions we make on your behalf are documented with the reasoning, so a new engineer can read why the system is the shape it is a year from now.
We keep a small number of engagements running at once. That means we will sometimes give you a start date further out than you want, and it is the reason the date holds once we give it.
See engagement modelsNext step
Tell us what is actually in the way.
Send a short note about the business and the constraint you are hitting. You will get a considered reply within two business days: a real assessment, not a sales sequence.