Terms

Last updated

Two things live on this page: the terms for using this website, and the standard positions that project work runs under.

The second half is a summary, not the contract. Every engagement is governed by its own written scope and quote, and where that document and this page disagree, the signed one wins.

Using this website

The writing, design, code, images and case studies on this site belong to Harsh Vaghela. You are welcome to read, quote and link to any of it with attribution. Republishing a page or an article wholesale, or presenting the work shown here as your own, is not covered by that.

The case studies describe real projects, several of them self-initiated concept work, and each one says which it is. Nothing on this site is a guarantee of a particular result for a different project — a portfolio shows what was done, not what will happen next time.

Scope, quotes and changes

Work is quoted as a fixed price against a written scope agreed before it starts. That document lists what is included, what is explicitly excluded, the phases, the review points and the payment milestones.

Anything outside the agreed scope is a change to both the scope and the price, recorded in writing before the work continues. This cuts both ways: it protects you from an invoice you did not expect, and it protects the project from growing quietly until nobody can say what was agreed.

Payment

Payment is split across the milestones set out in the scope, rather than collected in full up front or in full on delivery. The schedule is written down before work starts.

Third-party costs are yours and are billed to you directly by whoever provides them — platform subscriptions such as Webflow or Framer, hosting, domains, licensed fonts and stock imagery. I do not resell them or hold client accounts, and nothing you pay for should be locked behind an account of mine.

Ownership of the work

On final payment, the deliverables produced for you are yours: the design files, the source code in your repository, and the built site in your own platform account. There is no licence to keep paying and no bespoke framework you are tied to.

Two things stay with me. General knowledge, methods and reusable non-client-specific components are not transferred — they are how the next project gets built. And unless we agree otherwise in writing, I keep the right to show the work in this portfolio and in professional profiles. If a project is confidential, say so at the brief stage and it is excluded.

What you provide

Projects depend on content, access and feedback arriving when they are needed. Copy, images, brand assets, logins and approvals are yours to supply, and a timeline assumes they arrive roughly on the dates the scope names.

You confirm you have the right to use anything you hand over — images, fonts, copy, trademarks. I design and build with what I am given, and I cannot verify the licensing behind a client’s own assets.

What is and is not promised

The work is carried out with reasonable professional skill and care, and a build is tested across current browsers on desktop and mobile before it is delivered. If something delivered does not work as agreed, tell me and I will fix it.

What cannot be promised is a business outcome. Nobody can guarantee a search ranking, a conversion rate, a revenue figure or the behaviour of a third-party platform, and any supplier who does is guessing. Liability is limited to the fees paid for the piece of work concerned.

Ending an engagement, and which law applies

Either side can end a project in writing. Work completed and phases already begun are payable up to that point, and everything finished and paid for is handed over — files, code and access — rather than held.

These terms and any engagement under them are governed by the laws of India, with the courts of Ahmedabad, Gujarat having jurisdiction. Anything unclear here is better raised before a project than after: design.harsh25@gmail.com.

Anything here you want clarified before we work together?

Get in touch