FAQs
How we work — commercially, technically and when things go wrong.
The questions clients ask before engaging us, answered in more detail than a sales conversation usually allows.
01 — Category
Working with us
5 questions
With a conversation, then a short discovery phase. The conversation is free and typically lasts about an hour — we want to understand the problem, the constraints and who needs to be convinced. If there is a fit, we propose a discovery engagement that produces a costed roadmap, an architecture direction and a delivery plan.You own everything discovery produces, whether or not you continue with us.
We work on everything from a focused piece of work — a Drupal migration, an accessibility remediation, a technical audit — through to multi-release platform programmes.What matters more than size is whether the problem is well suited to us. If it is not, we will say so early rather than take the work and disappoint you.
Both, and the choice should follow the uncertainty in the work. Discovery and well-defined scopes are fixed. Multi-release platform work runs as costed increments you can stop at any boundary, re-forecast against actuals as we go.We are cautious about fixing a figure on genuinely novel work, because that figure has to contain a risk premium you pay whether or not the risk materialises.
Most of our larger engagements are blended. Our engineers join your repositories, standups and review process, and we are explicit in writing about which components each side owns.
We are based in Kolkata and work with clients across India and internationally. Delivery is remote-first with regular scheduled contact, and we agree working-hours overlap at the start of every engagement.
02 — Category
Delivery and quality
4 questions
Short increments with working software, a single named delivery lead on our side, and a change process that puts the cost of a change in front of the person requesting it before it is accepted.Most drift is not caused by engineering. It is caused by decisions taken slowly and changes accepted informally, so we make both visible.
The people named in the proposal. We do not bid with senior profiles and staff with juniors — a practice common enough in this industry that it is worth stating plainly. Team composition, including seniority mix, forms part of the agreement.
You get told early. Our delivery leads are expected to escalate quickly rather than manage bad news, and there is a defined path to a director.Post-incident reviews are blameless, written down and shared with you, including the ones that reflect badly on us.
Quality engineering is built into delivery rather than added at the end. Automated testing runs in the pipeline, accessibility and performance budgets are enforced per release, and defects that escape to production are reported to you rather than quietly fixed.
03 — Category
Commercial and legal
4 questions
You do. All code, designs, documentation and assets created in the engagement are assigned to you on payment. We retain no licence over your product and we do not reuse client-specific work elsewhere.Where we use our own pre-existing internal libraries, they are identified in the agreement and licensed to you perpetually and royalty-free.
Yes. Non-disclosure agreements, data processing agreements and client-specific security policies are routine, and we can complete supplier security questionnaires as part of onboarding.
We process client data only for the purposes and in the locations agreed in the engagement, apply least-privilege access, and prefer anonymised or synthetic data in non-production environments. Details are set out in our privacy policy.
Yes, on notice. Exit assistance, documentation and handover are defined in the agreement from the start rather than negotiated under pressure at the end.
04 — Category
Technology
4 questions
We keep a deliberately limited set — TypeScript, Python, PHP and Java, React and Vue, Drupal, and the four major clouds — because depth beats breadth for outcomes. Within that we choose per engagement based on your team, your constraints and the problem.We will recommend technology your team already knows over technology we prefer, most of the time.
Frequently. We start with a technical audit covering architecture, dependency risk, test coverage and operational readiness, then give you a prioritised plan before committing to a schedule.
Yes, with governance. AI assistance is used under human review, with licence and provenance checks in the pipeline, and not at all where a client's agreement prohibits it. It does not change our IP position or our quality gates.
Optional retained support with defined response targets, covering monitoring, patching, dependency and security updates, incident response and a monthly allocation for enhancements.
Still unanswered
Ask us the awkward one
If your question is not here, it is probably the interesting one. We would rather answer it before you engage us than after.
Start a conversation
Tell us what is not working. We will tell you what we would do about it.
An hour with our team, no charge and no obligation. You will leave with a point of view on the problem whether or not you work with us.
Monday to Saturday, 10:00 – 19:00 IST