Custom software, engineered to ship.

Typically a 4-week scoped build. Anything shorter is usually better served by internal engineers or a specialist freelancer. We do run paid discovery sprints (1–2 weeks) to de-risk larger engagements.

Yes. About a third of our engagements start with a codebase review and stabilisation phase before net-new work. We publish a technical due diligence report at the end of the review so you know exactly what you own.

TypeScript and JavaScript on Node.js, React and Next.js for frontends, Python (Django, FastAPI) for data and AI workloads, PostgreSQL and Redis for state. We build on modern web standards so the same code runs cleanly across browser, Node and edge runtimes. We avoid exotic tech unless the problem genuinely requires it.

Yes to both. We have standard NDA and Data Processing Agreement templates that we can sign quickly, or we can counter-sign yours.

The written scope from the discovery sprint is the contract baseline. Any scope change goes through a written amendment describing what’s changing, why, the cost impact and the timeline impact. You decide whether to approve the amendment before work on it begins. We don’t do silent scope creep and we don’t start an amendment clock before you’ve agreed.

Every week you get a live demo of what shipped that week, a written status document covering progress, risks, blockers and upcoming work, and an open issue tracker you can read at any time. If something is off track you hear about it from us before it becomes a problem. No vague weekly reports that say ‘progress made’.

Yes. Post-launch retainers are a standard option: the same engineers who built the system continue to operate and extend it under a monthly retainer with agreed capacity and response times. If a retainer isn’t what you want, we do a clean hand-over with documentation, onboarding and a short training period for your internal team.