Questions we get asked

We quote after a short call and, for larger work, a discovery phase. A number given before that is a guess, and guesses given early become numbers people hold you to. What we can do on the first call is tell you the rough order of magnitude and whether it is worth continuing.

You do, from the first commit. We work inside your repository and your cloud accounts wherever possible, so there is nothing to transfer at the end. That covers source, database schema, deployment configuration and documentation. No licence, no lock-in, no fee for leaving.

Most first versions are three to five months from discovery to production. The range depends on how many systems we integrate with and how clean your data is. We narrow it after discovery, which takes about two weeks. Anything quoted before that is not reliable enough to plan against.

We work Indian Standard Time with a guaranteed overlap: four hours with US Eastern in your morning, most of the afternoon for Europe, the full day for India. Anything raised in the overlap gets a same-day answer rather than a next-day one.

Yes, before any detail is discussed, and we will sign yours rather than insisting on ours. For partner work the NDA is mutual and signed before client details are shared in either direction.

You stop at the end of any two-week cycle and keep everything delivered, in your repository, with the documentation written to date. There is no exit fee and we do not hold code or credentials as leverage. We would rather be kept because the work is good.

Often, yes. We start with a short assessment of the existing code before quoting, because taking over an unknown codebase blind is how estimates go badly wrong. Sometimes that assessment concludes it is cheaper to rebuild, and we will say so even though it is the less appealing answer.

For well-defined scopes, yes. For anything exploratory, a fixed price means one of us is gambling, and the price includes the risk premium. Most of our work runs as two-week cycles with an agreed rate, which gives you the ability to stop that a fixed price does not.

Standard practice on every project: no secrets in source, dependencies scanned in the pipeline, least-privilege access, and code review on everything. For projects handling sensitive data we add a threat model and a review before launch. We also do security work as a service, but it is not the main thing we do.

Defects in what we built are fixed at our cost, and every project includes a post-launch window for exactly that. After it, maintenance is a separate arrangement, monthly or as-needed. What we do not do is disappear at handover and reappear only for new work.

Yes. The lead engineer stays from discovery to handover, and there is a named backup who has been reading the code throughout. If a change is unavoidable you hear before it happens, not after.

Yes, and a good part of our work is that. We join your standups, use your tools and follow your review process. That arrangement works best when someone on your side owns the technical direction, because two teams both waiting for the other to decide is slower than either alone.