Services
Product engineering engagements: building new products end to end, taking existing ones to production readiness, and short technical reviews of an existing system.
We take a small number of engagements at a time. These are the shapes that tend to work.
Build a product end to end
For founders and teams with a product to build and no engineering organisation to build it. Domain modelling, architecture, implementation, billing, deployment, monitoring and launch-grade technical SEO — the whole surface.
This is what HoopoTrack , Nissab-Zakat and Portflossio each were.
Take an existing product to production readiness
For a product that works in the happy path and falls over everywhere else. Typically: correctness under concurrency and retries, tenancy and authorisation boundaries, billing and entitlement reconciliation, notification delivery guarantees, observability, and the performance work that shows up in Core Web Vitals.
Technical review
A fixed-scope read of an existing system, delivered as a written report: what will break first, what is load-bearing, what the realistic remediation sequence is, and what we would leave alone. Useful before a fundraise, an acquisition, or a decision to rewrite.
Localisation and AI discoverability
Two narrower specialisms, both drawn from products we run:
- Genuinely multilingual products — up to eleven locales in production including right-to-left Arabic, with locale negotiation, translated URL slugs and hreflang that holds together.
- Making a product legible to agents — MCP servers,
llms.txt, well-known discovery documents and structured data. We wrote up how we did this for a public data service.
Working with us
We start with a conversation about what you are building and what is in the way — not a form. If we are not the right fit we will say so quickly.