Small team.
Serious systems.
Two of us have been shipping production code since the mid-nineties, and the core team is three people on purpose. We build the tooling that makes that headcount work, then take on systems that would otherwise need a department.
- 631
- controllers brought under test
- 1,494
- inputs fuzzed for injection
- 3 min
- to re-verify all 73 pages
Not a company total. One lending platform, one team, numbers we can point at.
Read how they were measuredThree ways to work with us
The shape of the engagement changes. The people doing the work do not.
Turnkey projects
Best when you know the outcome and have nobody free to build it.
A fixed scope, a named team, and a running system at the end of it. We own delivery, testing and handover.
- Discovery and estimate in two weeks
- One team lead as your single contact
- Handover docs and runbooks included
Embedded delivery
Best when you have engineers but a gap in platform, architecture or planning.
We join your team and drive the work, rather than filling a seat. The gap is usually platform, architecture or process, not hands.
- Platform, DevOps, architecture and planning
- Alongside your engineers, in your repo
- Two weeks' notice either way
Long-term retainer
Best when a system cannot go quiet and nobody currently owns it.
A standing team for the systems you can't afford to leave unattended.
- Reserved capacity every month
- Same engineers, quarter after quarter
- On-call and maintenance windows
That is the whole core team, and it is the point. The numbers above came out of one engagement run by these people and the tooling they build.
See the work