How to write a freelance quotation in India (with a ₹ example)
A step-by-step guide to writing a freelance quotation in India: the 8 parts to include, a worked ₹ example, and how to send it so the client says yes.
Prakash Mummidisetty · · 7 min read
"Bhaiya, website ka kitna lagega?" It's a message every freelancer in India has answered at 11 pm, usually with a single number: "₹30,000 should be fine."
That number is the start of most payment arguments. The client hears "a full website with everything." You meant five pages and no logo. Nobody is lying; the quote just didn't say. This guide shows you how to write a freelance quotation in India that says it clearly, with a full ₹ example you can copy and adapt.
What a quotation is (and what it isn't)
A quotation is your offer, before any work starts: what you will deliver, for how much, by when, and on what terms. It is not a tax invoice. The invoice comes later, when you bill for the work.
A good quotation does two jobs. It helps the client decide, and it protects both of you later, because it's the document you both point to when someone says "I thought that was included."
The 8 parts of a quotation that works
1. Your details and the client's
Your name or business name, contact details, the client's name or company, and the date. If you're GST-registered, add your GSTIN. If you aren't, you don't need to invent anything.
2. A one-line project summary
One plain sentence: "Website design and development for Aroma Café, Hyderabad: 5 pages, mobile-friendly." This is the sentence you'll quote back if the project drifts.
3. Deliverables, by name and count
This is the part that matters most. Compare these two lines:
- Weak: "Website design"
- Strong: "5 pages (Home, Menu, About, Gallery, Contact), designed for mobile and desktop, with a contact form"
For other trades, the same rule applies. Not "social media posts" but "12 static Instagram posts (1080×1350) and 4 story versions". Not "video editing" but "2 Reels, up to 45 seconds each, from footage supplied by the client".
4. Revision limits, with a price for extra rounds
Say how many rounds are included and what a round means. For example: "2 rounds of revisions per deliverable. A round is one combined list of changes. Extra rounds are ₹1,500 each." The price is an illustration here; set yours from your own hours.
5. A "Not included" list
Most quotes skip this, and it's where most disputes begin. For the café website above:
- Writing the menu and page text (client provides it)
- Logo or brand design
- Food photography
- Domain and hosting fees
- Changes after handover, beyond 15 days of bug fixes
Be specific about the things clients commonly assume are included in your trade. If you've been caught by the same assumption before, put it on the list.
6. Timeline
Give dates or durations, and say what they depend on: "Delivery in 3 weeks from the advance payment and receipt of text and photos." A timeline that depends on the client's content should say so, or their delays become your delay.
7. Price and payment terms
Show the price per deliverable or phase, so the client can see what they're paying for, and then the total. State the payment split: for example, 50% advance and 50% before final files are handed over.
If you are registered for GST, show it as a separate line. Registration becomes compulsory when a service provider's aggregate turnover crosses ₹20 lakh in a financial year, or ₹10 lakh in some special-category states (Section 22 of the CGST Act). Check with your CA about what applies to you.
Add how you accept payment: bank account details, UPI ID, or both.
8. Validity and how to accept
A quote shouldn't stay open forever, because your costs and availability change. Write "Valid until 30 November 2026." Then say how the client accepts: "Reply 'Approved' to this message, and I'll share the advance payment details."
A worked example (illustrative prices)
The prices below are an example to show the structure. They are not market rates. Build yours from your own hours and costs.
Quotation: Website for Aroma Café, Hyderabad
| Item | Details | Amount |
|---|---|---|
| Website design | 5 pages: Home, Menu, About, Gallery, Contact. Mobile and desktop. | ₹22,000 |
| Development | Contact form, Google Maps embed, basic on-page SEO setup | ₹10,000 |
| Revisions | 2 rounds per page, included | ₹0 |
| Subtotal | ₹32,000 |
Not included: page text and menu content, logo, photography, domain and hosting, changes after handover beyond 15 days of bug fixes.
Extra rounds: ₹1,500 each. Extra pages: ₹4,000 each.
Timeline: 3 weeks from the advance and receipt of text and photos.
Payment: 50% (₹16,000) advance, 50% (₹16,000) before final files. GST extra if applicable.
Valid until: 30 November 2026.
Notice what the client can do with this: compare it with other quotes line by line, ask to drop an item to lower the price, and see exactly what an extra page costs before they ask for one.
Send it so it gets answered
How you send a quote matters nearly as much as what's in it.
- Send a document, not a chat message. A PDF (or a single link) is easy to forward to a partner or accountant, and it doesn't get lost among 400 messages.
- Walk through it in one short note. "I've listed what's included and what isn't, so we're both clear. Do check the 'Not included' list."
- Ask for a specific reply. "Reply 'Approved' and I'll send the advance details" is easier to act on than "let me know."
- Follow up once. If there's no reply in 3 or 4 days, one polite nudge is enough: "Just checking if you had any questions on the quote. Happy to adjust the scope if the budget is tight."
If the client wants a lower price, change the scope, not just the number. "I can do 4 pages for ₹26,000" keeps the deal fair. A discount with the same scope teaches the client that your first price was negotiable padding.
Lock the version they approved
An approval is only useful if you can later show what exactly was approved. If you change a line after the client says yes, you now have two versions, and an argument about which one counted.
Keep the approved PDF and the client's "Approved" message together. If anything changes, issue a new version and get that approved too. This is also the base you use when extra work comes up later, as covered in our guide to stopping scope creep.
Doing this without version confusion
You can build all of this in a document template and keep the PDFs in a folder. It works until the third revision of the same quote.
Scopeflow is built around this workflow. You write the quote with named deliverables, a revision limit per deliverable, a "Not included" list, GST and a valid-until date, and you can start from a template. A scope checker flags vague or incomplete scopes before you send. The client approves through a private link, with no account needed, and the approved version is locked with a record of who approved it and when. It's in beta, and the Free plan covers 2 active projects and 5 clients. You can start free or see pricing.
Before you send your next quote
- A one-line project summary
- Every deliverable named, with a count
- Revision rounds stated, and a price for extra rounds
- A "Not included" list, with the things clients usually assume
- A timeline that says what it depends on
- Price per item, a total, and the payment split
- GST shown separately if you're registered
- A valid-until date and a clear way to say yes