Custom software development
Software projects break at the seams: a spec nobody re-read after week two, a subcontractor who left before the tests were written, a handover that arrived as a zip file. We take the whole job instead, from the first scoping call to the walkthrough on launch day. The engineers who scope it are the engineers who ship it.
Product engineering, spec to launch
Web and mobile applications, internal tools and customer-facing products. We choose the stack with you, and we weight that choice towards what your team can maintain once we leave. If an off-the-shelf tool would do the job, we say so on the call.
APIs and third-party integration
API design, plus the integration work that gets estimated at a day and takes three weeks: payment providers, CRMs, ERPs, and internal services whose documentation stopped being true two years ago. We scope the failure modes and the retry behaviour with the rest of it.
Legacy system modernisation
Systems that still run the business and nobody wants to touch. We read the code first, then tell you whether to rewrite it, migrate it piece by piece, or leave it alone and fix the two things that hurt. A rewrite costs the most of the three, so it needs the best reason.
QA, testing and documentation
Part of the engagement and on the same invoice as the build, so a tight deadline does not quietly remove it. We write the documentation for whoever maintains the system after us, and it is ready before launch day rather than during it.
What we hand over.
- Product engineering from spec to launch
- API design and third-party integration
- Legacy system modernisation
- QA, testing and documentation. Included, never billed separately
Questions this work usually raises.
What tech stacks do you work in?
We choose the stack based on your team's ability to maintain it after we leave, not our own preference. In practice: TypeScript/Node, Python, and Go on the backend; React and native mobile on the front end; AWS, GCP, or Azure for infrastructure.
Who owns the code and IP?
You do, outright, on delivery. No licensing fees, no dependency on us to keep running your own software.
What happens if requirements change mid-project?
They usually do, a little. Small changes get absorbed. Anything that meaningfully changes scope gets a written change order, with its price and timeline impact, before we build it. You approve the number first.
What happens after launch?
A handover walkthrough and documentation are included in every engagement. Ongoing support is a separate, opt-in engagement, never bundled in by default.
Most engagements cross more than one.
Bring us the whole problem.
Book a one-hour scoping call. No deck, no pitch: you describe the problem, we ask the questions that usually get skipped, and you get a straight answer on whether we're the right people for it. Scoping comes after, in writing.