FAQ

Every project starts with a scoping call and a short technical discovery phase. You get a written proposal covering timeline, team and a fixed price or a capped time-and-materials estimate — you approve scope before we write a line of code.

It depends on scope: a focused MVP typically ships in 6 to 10 weeks, a full platform build in 3 to 6 months. Whatever the length, we work in weekly sprints with a visible backlog, so you always know exactly what shipped and what's next.

Yes, entirely. Repositories, infrastructure and documentation are transferred to your organisation — no vendor lock-in, no licensing you don't control. If you want to bring development in-house later, everything is built to hand over cleanly.

Launch is a milestone, not an exit. Most clients move onto a support and maintenance retainer — monitoring, security patching and a defined response SLA — or keep us on for ongoing feature work. Either way, the same engineers who built it are the ones supporting it.

All engagements run under NDA, with GDPR-aligned data handling for UK and EU clients and secure development practices throughout — code review, dependency scanning and access controls as standard, not an add-on.

Project work runs from £10,000 for a focused internal tool to £350,000+ for a complex, multi-role platform, with most engagements landing between £30,000 and £150,000. Ongoing work runs as a monthly retainer from £799. We price after discovery, not before it, so the number reflects your actual scope rather than a generic band — see the pricing page for the full breakdown by project type.

Both, depending on how well-defined the scope is. A tightly-specified integration or feature suits a fixed price; a genuinely new product suits a capped time-and-materials retainer, where cost transparency stays high but scope can flex as you learn. We will recommend one, not just offer both and let you guess.

No fixed minimum, but most projects need at least a few weeks to move past discovery. For ongoing work, our retainer can scale up or down monthly — there is no long-term lock-in contract.

Primarily Laravel, Node.js, React, Vue and Python on the backend and frontend, deployed on AWS or equivalent managed cloud infrastructure. We choose the stack for the problem, not the other way around, and we are equally comfortable extending an existing codebase in a stack we did not originally choose.

Yes — this is a large part of what we do. We start with a short technical audit to understand what is genuinely load-bearing versus what needs rework, then agree a plan before touching production. See our guide on rebuild vs refactor for how we approach that decision.

A small, named senior team — the engineers who scope the work are the ones who build it, not a rotating pool of whoever is free. You will know exactly who you are talking to for the life of the engagement.

A shared channel for day-to-day questions, a weekly progress update with a working demo, and direct access to the engineers — not a project manager relaying messages. You always know what shipped this week and what is next.

No. We engage as a business-to-business services contract, not a personal service company supplying an individual's time — there is no IR35 determination for your business to make. Full detail in our IR35 guide.

Yes, always, and usually before the first proper scoping call — we expect it and will often send one ourselves if you do not.

They usually do, at least a little, and that is normal. We work in short sprints with a visible backlog, so re-prioritising is a conversation, not a formal change-request process — genuinely new scope is quoted separately rather than silently absorbed or blocking progress on everything else.

Tell us — weekly demos exist precisely so nothing surprising shows up at the end. Because engagements are not locked into a long contract, you are never stuck; in practice this comes up rarely because scope is agreed before we build, not after.

Yes — MVPs are a large share of our work, typically delivered in 8 to 12 weeks for a well-scoped core journey. See our MVP delivery guide for how we scope one properly.

Travel and booking platforms, fintech, logistics, healthcare-adjacent (non-clinical) systems, and B2B SaaS, among others. If your sector is not on that list, the underlying engineering discipline — scoping, architecture, secure delivery — carries across regardless.

Yes, as standard, not as an optional extra — automated test coverage, code review and handover documentation are part of every build, so what you own at the end is something your own team (or ours, on an ongoing retainer) can actually maintain.

Yes — alongside UK clients we deliver for businesses across the EU and US, with overlapping working hours and GDPR-aligned data handling as the default, not a special request.