Questions
Frequently asked.
The questions we get on most first calls, answered as plainly as we would answer them on the call. If yours is not here, ask — we will add it.
Who owns the code you write?
You do, outright, including everything produced in phases you paid for but chose not to continue past.
We do not retain licences to client work, and we do not build on proprietary internal frameworks that would trap you with us. You get the repository, the infrastructure definitions, the evaluation harness and the documentation. If you want to take it in-house or to another vendor afterwards, nothing in our contract stops you.
What does a project typically cost?
Scoping diagnostics start in the low lakhs; production builds are usually a multiple of that depending on integration surface.
We will not quote a range on a website without knowing your problem, because the honest answer varies by an order of magnitude. What we can say is that our engineer-hour rate is materially below a comparable US or UK firm, and that we would rather you spend the difference on evaluation and observability than take it as a discount.
How long before we see something working?
A working proof of concept in weeks; a production system you would trust unattended usually takes months.
The gap between those two numbers is where most AI projects fail, and where most of our value sits. Anyone telling you a production-grade agent takes three weeks is describing a demo.
Do you work with clients outside India?
Yes. Roughly half our work is for clients in the UK, the Gulf, Singapore and Australia.
Mumbai gives genuine working-hours overlap with Europe, the Gulf and APAC, and a partial overlap with US East. We are straightforward about the US West limitation rather than pretending we are awake at 2am.
Where does our data go?
Wherever you require. Data residency is a deployment decision we make with you, not a default we impose.
We can deploy inside your cloud account, in a specific region, or with self-hosted models where the data cannot leave your infrastructure at all. That last option costs more and performs somewhat worse. We will tell you honestly whether your situation warrants it.
Do you still do blockchain work?
We maintain existing client systems but no longer take new blockchain engagements.
Our focus is AI engineering. The blockchain heritage informs how we build — idempotency, auditability, adversarial thinking — but it is no longer what we sell.
What happens if we are unhappy with the work?
Fixed-scope phases end at a decision point, so the most you can lose is a single phase.
Every engagement is broken into phases with explicit exit criteria. You can stop after any of them and keep everything produced so far. We would rather lose a phase than spend a year arguing inside a contract nobody wants to be in.
Can you work alongside our existing engineering team?
Yes. The embedded pod model puts our engineers in your sprints, on your board, reporting to your people.
It suits teams who have engineering capacity but not the specific AI experience, and it transfers knowledge as it goes rather than leaving you dependent on us. Priced monthly with a three-month minimum, because anything shorter is mostly onboarding.
Ask us something not covered here
Tell us what you are trying to build. We will tell you honestly whether we are the right team for it, and what it would realistically take.