Contact
Tell us what you are trying to build
A short description of the problem is enough to start. We read everything and reply within two working days - with questions and an honest view of the approach, not a pitch deck.
Common questions
Before you write
Working together
How do we start?
Send a short description of the problem through the contact form or by email. We reply within two working days with questions - usually the ones that change the estimate most. If it looks like a fit, we have a 30-minute call, then send a written proposal covering scope, timeline, cost and what we would deliberately leave out of version one. No charge for any of that.
Are we too small a client for you?
Probably not. We take on everything from a two-week design sprint to a year-long build. What matters more than budget is whether the problem is well enough understood to make progress on, and whether you can give us a decision-maker who is actually available. A small, focused project with an engaged client beats a large vague one every time.
Who will actually do the work?
The people you meet. We are small on purpose, so there is no account manager layer and no swapping the senior developer you were shown for a junior after the contract is signed. You will have direct access to the people writing the code.
Do you work with clients outside India?
Yes - most of our work is with clients in Europe, North America and Australia. We are in IST and typically hold two to four hours of overlap with European and Australian clients, and early-morning overlap with North America. Everything is documented in writing so progress never depends on catching each other live.
Will you sign an NDA?
Yes, happily, before you share anything sensitive. Send yours over or ask us for our standard mutual one. Please do not put confidential material into the contact form - ask for a secure channel first and we will arrange one.
Can you work with our existing team?
Often that is the better arrangement. We regularly work alongside in-house teams - taking one workstream, providing a capability they do not have in-house, or reviewing architecture. We use your tools and your process rather than imposing ours.
Cost & payment
What does a project cost?
It depends entirely on scope, and we would rather give you a real number than a misleading one. Tell us what you are trying to build and we will come back with a considered estimate - usually within a few days of the first conversation. Quoting a figure before understanding the problem helps nobody.
Why not a fixed price for everything?
We do fix the price, once the scope is actually known - which is what discovery is for. A fixed price quoted before anyone understands the problem is either padded to cover the worst case, or it is about to be revised upward through change requests. Both are worse for you than spending two weeks working out what you are actually buying.
How does payment work?
A deposit to start, then invoices against delivered work at agreed milestones, with the balance on handover. Retained engagements are invoiced monthly. Everything is set out in the proposal before you commit, and we can invoice in USD, EUR, GBP or INR.
What happens if the scope changes?
Scope changes are normal and we plan for them. Anything outside the agreed scope gets estimated in writing before work starts, and you decide whether it is worth it - often the answer is to swap it for something already in scope rather than add budget. You will never receive an invoice for work you did not approve.
Who owns the code and the designs?
You do, completely, once invoices are settled. That includes source code, design files, and the repositories and accounts they live in. We do not retain a licence, we do not hold anything hostage, and we do not build on a proprietary platform that requires you to keep paying us. Any third-party open-source libraries remain under their own licences, which we list for you.