Everything you’d ask on the first call.

Thirty minutes, no presentation. We ask what you are trying to fix or build and what has already been tried, and you get a straight answer on whether we are the right people for it. Within 48 hours you receive a written summary and an indicative plan.

No, and most of the people we work with are not. Our job is to translate what your business needs into software, and to explain the choices in terms of cost, time and consequence rather than technology.

Yes — that is a normal starting point. We spend the first conversation on the problem rather than the solution. Quite often the answer is smaller and cheaper than people expect, and occasionally it is an existing product rather than anything we would build.

Very small pieces of work are often better handled by an individual freelancer than by a team, and we will say so. Where a small piece is genuinely the first step of something larger, we are happy to start there.

Yes, and it is more common than starting from scratch. We begin with a paid review — usually a week — so both sides know the real condition of the code before anyone commits to a plan.

Three ways: a fixed price for a defined piece of work, a monthly rate for an ongoing team, and a monthly support arrangement for software that is already live. Which one fits depends on how settled your plans are, and we will recommend rather than upsell.

Because an honest range before we understand the work is too wide to be useful to you. One conversation is usually enough to narrow it to a number you can take to whoever holds the budget.

It varies far too much for a headline figure to be meaningful — a marketing website and a multi-app delivery platform are not the same kind of purchase. What we can promise is that you get a real number in writing within 48 hours of the first call, before you commit to anything.

Yes, and we would rather you knew early. Hosting, domains, app store accounts and any paid services the software uses are billed to your own accounts rather than through us with a margin added. We estimate them up front so the number in your budget is the real one.

No. We take a fee and you keep your equity. Partial deferral is occasionally possible where there is a clear funding event, but it is an exception rather than a standing offer.

Usually within two weeks of agreeing terms. If your deadline is tighter than that, say so on the first call — we will tell you honestly whether we can staff it rather than book you in and hope.

On fixed-price work we price the change and you decide before we build it. On a monthly team the priorities are re-set every two weeks at no extra cost, which is why most longer projects use that arrangement.

You do, from the first day. The work lands in your repository, the hosting and app store accounts are in your name, and nothing requires our involvement to keep running.

Frequently, and it usually produces the best handovers. Your team can review the work as it happens and take ownership gradually rather than all at once on launch day.

You hear about it in that two-week cycle, not at the end. We would rather have an awkward conversation in week six than a surprise in week sixteen, and we bring options — reduce scope, extend, or reorder — rather than just the bad news.

Yes. The first stage is sold as a standalone piece of work with its own deliverables. If the plan concludes the project is not worth building, that is a useful answer, and the plan is still yours to keep.

Real customer data stays where it is wherever possible. Where we genuinely need real records to build against, we work with anonymised or made-up sets instead, under a signed data processing agreement.

We build to it by default rather than adding it before launch: consent capture, retention rules, export and deletion, and a record of what is stored and why. Final legal sign-off stays with your own advisers.

Wherever you need it to be. UK, EU and US hosting are all straightforward, and if data residency matters for your sector we settle that before the build rather than after.

No. On AI projects we use business-grade services with training on your data switched off, and where regulation requires it we can run models inside your own environment instead.

Gladly, usually before the first call. We have our own mutual NDA if you would rather move quickly and skip a round of legal review.

The people building it, in a shared channel. The person who scopes your project is on the team that delivers it, so nothing is lost in the handover between sales and delivery.

Less than most people fear. A few sessions at the start, one person available to answer questions within a working day, and forty-five minutes every second week to look at the demo. Projects slow down when that last part slips.

Tell us and we change them, without an argument about billing. Continuity matters, but not more than the work being right.

A written handover, a walkthrough with your team, and instructions for the parts that would page someone at 3am. You can keep us on a support arrangement afterwards, but nothing about the setup requires it.

Yes. Most of the work happens over shared documents, video calls and a group chat, so location matters far less than availability. We agree the hours we will overlap with your team before starting.