Terms
Who these are between
These terms cover work between you — the studio or company engaging me — and Prithvi Chauhan, working alone from Delhi, India under the name Studio OS. They apply alongside the written scope for your project. Where the two disagree, the scope wins.
Using this site
Everything on this site is here for information. Nothing on it is an offer, a quote or advice you should act on without talking to me first. The pricing shown is indicative of typical engagements; the number that binds either of us is the one in your written scope.
The demos on this site are illustrations of the kind of software I build. The studio names, projects, editors and figures inside them are invented for the purpose and are not anyone’s real data.
Scope and price
Every project starts with a written scope: what is being built, what it costs, and when it lands. Work starts once you have agreed to it.
The price is fixed against that scope. I don’t bill by the hour and I don’t send scope-creep invoices. If you want something outside the agreed scope, you get a new number in writing before I build it.
Payment
50% when you agree the scope, and 50% at handover. Invoices are in USD and due within 7 days. Ongoing support is billed monthly in advance. If a payment is late, work pauses until it’s settled.
Taxes are your responsibility where they apply to you, and mine where they apply to me.
What I need from you
A build runs to time only if it isn’t waiting on anyone. That means one person on your side who can make decisions, feedback within the agreed windows, and timely access to whatever the software has to connect to.
Anything you give me to work with — logos, copy, data, footage, client material — has to be yours to give. You keep responsibility for it, and for having the right to hand it over.
Delivery
Typical delivery is two weeks from the agreed start, with something clickable to look at well before the end of it. That timeline assumes feedback arrives when agreed; where it doesn’t, the date moves by roughly the delay.
Adjustments after launch
Two weeks of adjustments are included after handover, while your team is using the software for real. That covers changes and corrections inside the agreed scope. New features are new scope, priced separately or covered by an ongoing arrangement.
The code is yours
On final payment, ownership of the software built specifically for you passes to you — source included. I hand it over rather than hosting it on your behalf.
Two things stay mine, and neither limits what you can do with what you have: the general-purpose components, patterns and know-how I bring to every build and reuse on the next one, and any third-party or open-source code, which stays under its own licence.
Portfolio
I may name you as a client and describe the build in general terms unless you ask me not to in writing. I only show screens or details of your data with your written approval.
Confidentiality
Anything you tell me about how your studio runs, your clients, your rates or your people stays between us, and I’ll sign your own NDA if you’d rather have it in your words. The same holds the other way.
Third-party services
Your software will usually sit on hosting and services billed to you — a host, a database, a domain, whatever it integrates with. Those are between you and those providers, on their terms and at their prices. I’ll tell you what a build needs before it needs it.
What I warrant, and what I don’t
I warrant that the work is mine, that I have the right to hand it over, and that it will do what the agreed scope says it does. During the adjustment window I fix anything that doesn’t.
After that window, and beyond what the scope sets out, the software is provided as it stands. No software is free of defects and I don’t claim otherwise.
I am not liable for indirect or consequential loss — lost profit, lost business, lost data — and my total liability for any claim is capped at the fees you have paid me for the project it relates to. Nothing here limits liability that cannot legally be limited, including for fraud or personal injury.
Ending the work
Either of us can end an engagement in writing. If you end it, you pay for work completed to that point and I hand over what exists. If I end it for any reason other than your breach, I refund anything paid for work not done.
An ongoing monthly arrangement can be cancelled at any time and runs to the end of the period already paid for.
Changes
These terms can change for future work. The terms that apply to your project are the ones in force when you agreed your scope, and they don’t change underneath you.
Contact
Worth fifteen minutes?
Tell me how your studio tracks projects today. If software isn’t the answer, I’ll say so on the call — that happens often enough to be worth mentioning.