The terms we work under.

Every project starts with a written proposal that says what is being built, what it costs, and when it is due. A proposal is valid for 30 days. Work begins when you accept it and the advance clears.

Scope is fixed at the proposal. Anything outside it is a change request: we quote it, you approve it in writing, and only then does it enter the work. That is not bureaucracy — it is how a project stays on the date and the price we both agreed to, and it is the difference between a fixed fee that holds and one that quietly does not.

Timelines assume you come back to us within five business days on anything we need from you. If reviews or content stall, the delivery date moves by the same amount.

Projects are billed in three parts: 50% before work begins, 40% when you approve the staging build, 10% at launch. The site does not go live until 90% is paid. There is no version of this where we start on a purchase order that is still clearing.

• Invoices are due within 30 days. After that, late payment carries 1.5% per month, stated on every invoice.
• At 45 days past due we stop work on a project until the account is current. Plans are not invoiced, so this clock does not apply to them; a plan whose payment fails is handled by the dunning ladder in the service level agreement.
• Care and hosting plans are charged in advance and automatically: Razorpay for India, Stripe elsewhere. There is no manual-invoice option on a plan.
• Indian prices are quoted before GST, which is added at 18%. Export invoices are a zero-rated export of services supplied under a Letter of Undertaking, with no IGST charged. Pounds and Australian dollars are shown for convenience; the charge is in US dollars unless you ask otherwise.

Refunds are covered by the refund policy, and plan billing detail is in the service level agreement.

You own everything we build for you, once it is paid for in full. The design, the code written for your project, the content and the data: yours, transferable, with no licence back to us and no clause that takes it away if you leave.

Two honest exceptions, both normal:

• Third-party components. WordPress, Shopify themes, plugins, fonts and stock assets stay under their own licences. We buy them in your name where the licence allows it and hand the licence over with the site.
• Our own tools. Internal libraries, build scripts and checklists we bring to every project stay ours. Nothing your site depends on to run is in that category — if we walked away tomorrow, the site keeps working.

Until a project is paid in full, what we have built is licensed to you for review, not assigned.

• Access. Admin to the site and, where relevant, the host, registrar and DNS. We do not take on work we can get neither admin nor staging access to.
• Content. Copy, images and product data by the dates in the plan. We publish what you give us; we do not write it unless the proposal says so.
• Rights to that content. You confirm you are allowed to use the text, images, fonts and trademarks you send us. If a third-party claim comes from something you supplied, it is yours to answer.
• A decision-maker. One person who can approve. Two people with different opinions is a schedule risk, not a review process.
• Lawful use. We will not build or host anything illegal, deceptive, or designed to harm people.

Updates are tested on staging before production. Changes are deployed in low-traffic windows. Anything destructive is preceded by a backup we have checked, not one we assume exists.

We may name you as a client and show your logo. We will not publish a case study, a metric, a quote or a screenshot of your analytics without asking you first and getting a yes in writing.

Both sides keep the other’s confidential information confidential — your data, your plans, our pricing on a negotiated deal — for as long as it stays confidential.

We do what a careful, experienced team would do, and we say plainly when something is outside what we can promise. What we do not do is accept unlimited exposure for a fixed fee, and no studio honestly can.

Our total liability for any claim is limited to the fees you paid us in the three months before it arose. Neither side is liable to the other for lost profit, lost revenue, lost data beyond our backup obligations, or indirect losses.

Nothing here limits liability for fraud, for death or personal injury caused by negligence, or for anything else that cannot be limited under Indian law.

The internet is not ours. Registrars, hosts, payment gateways, plugin vendors and platform providers all fail sometimes. We will manage the consequences and we will not be liable for the failure itself.

Plans end on 30 days’ written notice, at the end of your paid period. Projects can be stopped by either side in writing; the refund position for a stopped project is in the refund policy.

We may end an engagement if an account is more than 60 days past due, if the work turns out to be something we said we do not do, or if somebody is abusive to our team. In every case you get 30 days’ notice and a full handover.

Leaving is not punished. You get the files, the database, the backups and the credentials, and we will spend a reasonable amount of time helping your next developer pick it up.

These terms are governed by the laws of India, and the courts of Bengaluru, Karnataka have exclusive jurisdiction.

Before anyone files anything, both sides talk — a call between the people actually involved, within 30 days of the problem being raised in writing. Almost everything ends there.

If a clause here turns out to be unenforceable, the rest still stands. We may update these terms; the date at the top is when this version took effect, and clients are told in writing about anything material. Questions: hello@ohmyweb.in.