Software, built properly.
We take on a small number of projects and give each one the attention it needs. The same standard we hold our own products to.
Conversation
You tell us what you are trying to build and why. We ask questions, and we say early if we are the wrong studio for it.
Scope and estimate
A written scope: what gets built, what it costs, how long it takes. No work starts before you have agreed to it.
Build
Work in short cycles with something to look at each time. You see progress as it happens rather than at the end.
Launch and after
Release, handover, and documentation. Ongoing maintenance if you want it, and a clean exit if you do not.
Fixed-scope project
A defined build with an agreed price and delivery date. Best when you know what you need. Changes are quoted separately rather than absorbed silently.
Websites, apps, first releases
Monthly retainer
A set amount of our time each month for ongoing work. Best when the product is live and evolving, or when you need someone reliably available.
Maintenance, long-running products
Discovery sprint
A short paid engagement to work out what should be built before committing to building it. Ends with a scope, an estimate, and no obligation to continue.
Early ideas, unclear requirements
How much does a project cost?
It depends on scope, so we do not publish a price list — a number without a scope is meaningless. After a first conversation you get a written quote with a fixed price and timeline, and no work starts until you have agreed to it.
How long does it take?
A website is usually 3–8 weeks, an app 8–16, a SaaS product 10–20. Those are estimates to set expectations; the real number goes in your written scope once we understand what you need.
Who owns the code?
You do, on final payment. That includes the repository, the designs, and the accounts we set up on your behalf. We do not hold your product hostage.
Will you sign an NDA?
Yes, before you share anything sensitive. Send yours, or ask and we will send a simple mutual one.
How do we communicate during the project?
Email or WhatsApp for day-to-day, and a short call at the end of each cycle to show progress. You will always know what is being worked on.
What happens after launch?
You get the code, the documentation, and a handover. If you want us to keep looking after it, maintenance is a monthly arrangement you can cancel. If you would rather take it in-house, that is a clean exit with no penalty.
Do you work with clients outside India?
Yes. The studio is remote-first and works across time zones. Most communication is asynchronous, with calls arranged around your hours.
How many projects do you take at once?
Few. Pravshi is a small studio and we would rather do a handful of things properly than run a queue. It means we sometimes say no, and it means the project you hire us for gets real attention.
Have something in mind?
Tell us what you are trying to build. We reply within two working days, and we will say early if we are the wrong studio for it.