00Service
The things that don't fit a category. APIs, infrastructure, hardware bridges.
01What we build
- Internal APIs and integrations
- Browser extensions and developer tools
- CLI tools and automation
- Hardware-connected software (kiosks, IoT, drones)
- Realtime systems (WebSockets, WebRTC, MQTT)
- Migrations, data pipelines, ETL
02How we approach it
The category does not determine the discipline. We bring the same versioning, testing, and observability we bring to a SaaS to a one-off browser extension or kiosk binary.
We optimize for the second engineer. The person who picks up the code in twelve months should be able to ship a change on day one — that means READMEs, runbooks, and a small surface area.
If it is genuinely novel, we say so. We do not pretend a hard research problem is a sprint of feature work.
03Process
- 01
Spike
A small, throwaway prototype to surface unknowns.
- 02
Scope
Fixed-price proposal with explicit out-of-scope.
- 03
Build
Two-week loops, weekly demos.
- 04
Handover
Code, docs, runbooks, on-call playbook.