We build the software your business runs on.

Fixed price for defined scope, day rate for ongoing work. Either way you get a written scope with assumptions and exclusions before anything starts. We do not publish rates on the site because they depend on the engagement shape, and we would rather quote your actual project than have you compare a number out of context.

You do, on delivery and in writing. Repositories are in your organisation from the first commit, not transferred at the end. Any third-party libraries we use are permissively licensed, and we list them so your legal team can check.

We hold a working overlap with US Eastern hours through your morning and with UK hours through your afternoon. Standing calls sit inside that overlap. Anything urgent has a documented escalation path rather than a hope that someone is awake.

Yes, before discovery. We will sign yours rather than insisting on ours. If your procurement needs a data-processing agreement or security questionnaire, send it over early because those take longer than the contract itself.

Fixed-scope projects are billed in phases, so you are never more than one phase exposed. If a phase misses what was agreed, we fix it at our cost. If you want to stop, you keep everything built to that point, including the repositories and documentation, and we will brief whoever takes over.

Handover is part of the build, not a final gesture. You get architecture notes, environment setup steps, the deployment process, a decision log, and a walkthrough call recorded for whoever joins later. We assume the person reading it has never spoken to us.

Roughly three to four weeks of engineering. Below that we are honest that our overhead is not worth your money, and we will usually point you at a freelancer or a configuration change instead.

Often, and it is usually the best arrangement. We work inside your repositories, your review process and your standards. We will flag process problems once, then work with what you have.

Yes, after a review. We read the codebase, run it, and give you an honest assessment of what it will take to support and extend. Occasionally that assessment is that a rewrite is cheaper, and we show the reasoning rather than just asserting it.

More than you might hope. We need a decision maker available for a weekly call and someone who can answer domain questions within a day. Projects that stall almost always stall on access to people, not on engineering.