Operating Model
How we operate.
A three-part model — Build, Manage, Scale — applied consistently across everything we ship. Same approach for an internal venture or an external build.
Build
We design and engineer software end to end — interfaces, data models, APIs, and infrastructure — using a small set of practical tools we trust.
- Discovery and scoping in days, not weeks
- Typed, tested code from the first commit
- Deployable to production from day one
Manage
We run what we ship. Observability, on-call rotations, support workflows, and the operational discipline that keeps live systems healthy.
- Uptime budgets we actually track
- Incident response with written post-mortems
- Customer support handled by people who shipped the code
Scale
We grow products deliberately. Sustainable architecture, clear documentation, and decisions made on a long horizon rather than a quarterly one.
- Architecture that survives a tenfold traffic increase
- Documentation maintained as we go
- Roadmaps measured in quarters, not sprints
Principles
Three principles we return to.
01
Smaller scope, finished work
We finish what we start instead of leaving half-built systems for the next team.
02
Fewer tools, used well
A small surface area means any engineer can understand and operate the whole venture.
03
Documentation before dependency
We write the notes while the decisions are fresh so ownership never becomes a mystery.
Engagement model
How an engagement is shaped.
We work in two stages. A fixed first build that proves the system in production, then a retained operating arrangement priced by month. We do not publish a rate card — each engagement is sized to the venture in front of us — but the shape is consistent and written down before any work starts.
01 — First build
Fixed scope, fixed price.
Written brief, a small set of measurable outcomes, a single price, and a date. Anything outside the brief is quoted before we touch it.
02 — Retained operation
Monthly, scaled to the system.
Uptime, incidents, small features within an agreed envelope, and a named human on call. Priced by traffic, complexity, and response time you need.
03 — Exit on your terms
Same-day handover, no lock-in.
Code, data, accounts, and domains live in your name from day one. The handover pack is ready before you ask for it.
Cadence
What our week actually looks like.
Review incidents, risks, and open decisions.
Ship the smallest useful slice.
Write down what changed, what is fragile, and what comes next.