The questions everyone asks on the call, answered before it. How we scope, how long things take, how pricing works, what happens when the brief changes, and what you own when it is finished.
01
A 30-minute call, free, no deck. We want the actual problem: the thing costing you money or time, not a feature list. If we think you do not need us, or that an off-the-shelf tool solves it for a fraction of the cost, we say so on that call. That happens often enough that it is worth saying out loud.
02
Before you commit, we usually build a piece of it. A working prototype of your page, a sketch of the automation, a read of your attack surface. It is faster for us to show than to pitch, and it means you are deciding against an artifact rather than a promise. This is unpaid and yours either way.
03
A written scope: what ships, what does not, what it costs, and when. Fixed price for defined projects. We would rather spend an extra day getting the scope right than discover the misunderstanding in week three.
04
You see progress as it happens, on a real URL, not in a status meeting. The two people who scoped it are the two people building it. There is no account manager between you and the work, which is the entire reason this studio is two people and not ten.
05
Code, accounts, infrastructure, domains, all handed over. Security hygiene is part of the build rather than an upsell: hardened headers, a real content-security policy, rate-limited and bot-protected forms. Then we tell you what we would watch for next.
A landing page or brand site is usually days. A storefront rebuild runs two to six weeks depending on catalogue size and how much of it needs restructuring. An MVP web app is typically a few weeks to a first usable version. A security audit is scoped in days, not weeks. Every one of those is a range until we have seen your actual situation, and we would rather give you a real number on the call than a comfortable one on a web page.
On scope, decided after the problem call, and quoted as a fixed price for a defined project rather than an open-ended hourly rate. Retainers are monthly and cancellable. We do not publish a rate card because the honest answer to "what does a website cost" is a question, not a number, and every studio that publishes one either quotes high to cover the worst case or quotes low and finds the difference later in change requests.
It usually does, and that is fine. Small things inside the spirit of the scope we absorb without a conversation about money. Anything that materially changes the size of the job gets priced before it is built, not invoiced after. You will never get a surprise line item.
Anirudh Goel and Arnav Amar. The people on the call are the people writing the code. Nothing is offshored, subcontracted, or handed to a junior while a senior name stays on the invoice.
Everything. Source code, repositories, hosting accounts, domains, third-party accounts set up in your name. No proprietary platform you have to keep paying us to stay on, and no dependency on us continuing to exist. If you want to move to another team, you can, and we will help you hand over cleanly.
A period of support is included so the things that only appear under real traffic get fixed. After that you can take it in-house, come back per change, or move to a monthly retainer. We do not require a retainer to hand over a finished project, and we will tell you if we think you do not need one.
Yes. The studio is remote and India-based, and we work across timezones. Most of our shipped work is for Indian D2C and retail brands, which is where our commerce experience is deepest.
Show us the problem. We will show you the solution, in one call, at no cost.
Thirty minutes, no deck, and an honest answer about whether we are the right people for it.
Book a problem call