Five principles we actually argue about.
01Build for the real operating environmentThe messy import, the flaky third party, the user on a bad connection at the end of a shift. If the design only works in the demo, it does not work.
02Make quality visibleCoverage, pass rates, error budgets and incident counts belong on a page anyone can open. Confidence should come from evidence, not from tone of voice.
03Keep complexity earnedEvery service, queue and abstraction has to justify the cost of being understood by the next engineer. We remove more than we add in year two.
04Communicate clearlyOne written update a week: what shipped, what moved, what worries us. Bad news travels fastest here — it is cheapest when it is early.
05Design for long-term ownershipWe aim to be replaceable. Runbooks, decision records and a team that can change the system without asking us are part of the deliverable.
The people you’d work with
You meet the actual delivery team on the scoping call — the engineers who would write the code, not a sales layer in front of them. Who joins depends on the work, so we introduce them once we know what we are building.
Senior-only delivery
Pods of three to six engineers, with no bench juniors billed against your budget to learn on the job.
Dubai and Lahore
Two bases, one team. Working hours are arranged to overlap yours rather than ours, and that window is in the agreement.
One accountable lead
A named engineer owns the outcome and writes the weekly update. You always know who to ask.
How working together actually goes.
- WEEK 0Scoping callThirty minutes on the problem, the constraints and the deadline. You get an honest read on whether we are the right partner — sometimes the answer is no.
- WEEK 1Written approachA short document: what we would build, in what order, what it costs, and what we would deliberately leave out of the first release.
- WEEK 2Discovery startsFixed-price, time-boxed. Interviews, system walkthroughs, data review, and a risk register with named owners at the end of it.
- WEEK 4+Delivery incrementsTwo-week cycles with a working demo and a written update at the end of each. Reprioritisation between cycles is normal and free.
- ONGOINGOwnership handoverRunbooks, decision records, subsystem walkthroughs and a support line while your team takes over. Retained capacity if you want us close by.