DEV Community

Aayan Saxena
Aayan Saxena

Posted on

How to Build a Freelance Rate Card in India (2026 Guide)

Most Indian freelancers do not lose money because they cannot find work. They lose it because every quote is reinvented in WhatsApp, “small changes” eat unpaid days, and there is no clear advance / mid / final plan.

A rate card fixes the front of that funnel: what you sell, at what INR price, with what is in and out of scope. Paired with a simple proposal and milestone schedule, it is how solo designers, developers, writers, consultants, and VAs look professional without agency software.

This guide is practical and India-specific. It is educational — not legal, tax, or financial advice. Sample package prices below are illustrative; set your own numbers.

What a rate card is (and is not)

A rate card is a one-pager (or short section in a proposal) that lists:

  • Named packages (e.g. Starter / Standard / Premium)
  • What’s included in each
  • Add-ons with ₹ prices
  • Optional hourly / day rate for out-of-scope work
  • Payment shape (advance %, milestones)

It is not a GST invoice, tax planner, or lawyer-reviewed contract for ₹5L+ deals. Invoicing and GST belong in a finance workflow; see Best GST Invoice Templates for Indian Freelancers (2026) (Finance Kit — GST invoices + tracker) for that side.

Why Indian freelancers need one in 2026

Without a rate card, the same week often looks like this:

Step 1 — Find your floor rate (minimum hourly)

Before packages, know the number below which you are working for free.

A simple floor formula many freelancers use:

  1. List monthly costs you must cover (rent share, internet, tools, CA fees, health buffer, tax buffer).
  2. Decide billable hours you can realistically sell per month (not 160 — often 60–100 after admin and sales).
  3. Floor hourly ≈ monthly costs ÷ billable hours.
  4. Add a margin for profit and dry months.

Example (illustrative only): if costs + buffer are ₹60,000/month and you bill ~80 hours, floor ≈ ₹750/hour. Packages should not silently land below that after revisions.

Your rate card can show packages as primary and keep hourly only for extras.

Step 2 — Productise into 3 packages

Three tiers reduce “what do you charge?” into a choice:

Tier Positioning Typical use
Starter Narrow scope, faster delivery First-time buyers, MVPs
Standard Your recommended default Most clients
Premium Priority, more rounds, extras bundled Clients who value speed/access

For each package, write:

  • Deliverables (bullet list)
  • Timeline Yellow sticky note for you: sample ₹ figures online (including in kits) are placeholders — edit for your niche and city economics.

Step 3 — Tie money to milestones

A rate card without payment shape still invites “pay after launch.”

Common India-friendly patterns:

  • Short project: 50% UPI advance to start, 50% on delivery
  • Medium project: 40% advance / 30% mid milestone / 30% final
  • Retainer: monthly in advance, clear hour or deliverable cap

Write triggers, not dates alone: e.g. “30% on homepage approval,” not “sometime mid-project.” Pause-on-nonpayment belongs in your SOW language (have a lawyer review high-value work).

Step 4 — Define in-scope vs billable extras

Your rate card should make revision policy visible:

  • Included rounds (e.g. 2 rounds of consolidated feedback)
  • What counts as a new request (new feature, new page, brand rethink)
  • Extra-revision rate (₹ / round or hourly)

When feedback arrives as 15 WhatsApp voice notes, you need a revision log: in-scope vs billable. That is operations, not personality.

Step 5 — Turn the rate card into a proposal

The one-pager alone rarely closes. A full proposal usually adds:

  • Problem restatement ## Step 6 — Keep it alive with a tracker

A rate card that lives only in Notion still fails if projects have no status. Minimum ops layer:

  • Project status and contract value
  • Balance due and next action
  • Milestone schedule
  • Weekly pipeline glance (what’s overdue)

You do not need full agency PM software for this as a solo operator.

Soft tool recommendation: Indian Freelancer Client Ops Kit

If you want the rate card plus the surrounding ops loop in one place, Pranjal Vyas’s Indian Freelancer Client Ops Kit is built for Indian freelancers who are tired of running client work from WhatsApp.

Who it is for (per the product page): freelance designers, developers, writers, consultants, and VAs in India; solo operators dealing with scope creep and “pay after launch”; same buyer as the Finance Kit but focused on delivery control.

Who it is not for: people who only need GST invoices / ITR tools; large agencies with full PM stacks; anyone needing a lawyer-signed contract for high-value deals without review.

What’s inside (as listed on Gumroad):

  1. Excel Client Ops Workbook (7 sheets)
    • Your Setup (UPI, default advance %, extra-revision rate)
  2. Plain-English Client Ops Guide (India) — proposal → SOW → kickoff → revision → milestone loop, and what belongs in Finance vs Ops

  3. Copy-paste Markdown templates — full client proposal (3-package table), Statement of Work / scope (in/out, IP, pause-on-nonpayment), rate card one-pager, kickoff checklist, Change Order / extra revision, client-facing milestone payment schedule, weekly status update (email + WhatsApp)

Price listed: launch ₹449 → list ₹599. Open the workbook in Microsoft Excel, LibreOffice, or import to Google Sheets; templates work in Notion, Docs, or any editor.

Explicit positioning from the page: this is not a GST invoice or tax planner. For invoicing + GST + tax, use the separate Indian Freelancer Finance Kit. Ops decides when and why to bill; Finance produces the invoice. Buy one or both — they do not replace each other.

Disclaimer on the product: educational / productivity only; no guarantee of clients, closings, or income; SOW/Change Order text is structural — consult a lawyer and CA for high-value or cross-border work.

Soft CTA: if your next lead still gets a chaotic WhatsApp quote, start from the Client Ops Kit rate-card + proposal templates — pranjalvyas.gumroad.com/l/oejgeh.

DIY rate card template (copy and edit)

Use this skeleton in Docs/Notion if you are not buying a kit yet:

[Your Name] — Rate Card (INR)
Valid: 2026 | Payment: UPI / NEFT | Advance: __% to start

STARTER — ₹______
• Deliverables:
• Timeline:

ADD-ONS
• Extra revision round — ₹______
• Rush (≤__ days) — ₹______
• …

HOURLY (out of scope) — ₹______ / hour
MILESTONES — e.g. 40% / 30% / 30% on [triggers]
Enter fullscreen mode Exit fullscreen mode

Fill yellow cells with your real numbers. Revisit quarterly when costs or demand change.

Rate card mistakes to avoid

  • One blurry “project fee” with unlimited revisions
  • Hourly-only pricing for clearly productisable work
  • No advance (you fund the client’s experiment)
  • Hiding add-on prices until conflict
  • Copying US $ rates without INR cost reality
  • Skipping SOW and then arguing scope in chat
  • Mixing GST invoice formatting into the rate card instead of a finance tool

How this connects to invoicing

Once a package is chosen and a milestone is due, you still need a clean invoice (GST-aware if registered) and a payment ledger. That is the Finance Kit lane — covered in detail here: Best GST Invoice Templates for Indian Freelancers (2026) (Finance Kit — GST invoices + tracker).

Quick split:

FAQ

Should I publish my rate card publicly?

Optional. Many freelancers keep a public “from ₹X” teaser and send the full card inside proposals so prices can flex by complexity.

Fixed packages or pure hourly?

Packages for repeatable offers; hourly or day rate for ambiguous consulting and extras. Hybrids work well.

Do I need GST on the rate card?

Show prices clearly (tax exclusive vs inclusive). Actual GST lines belong on invoices if you are registered — confirm with your CA.

Can I edit kit package samples for my niche?

Yes — the Client Ops Kit FAQ states yellow cells are yours and sample ₹ prices are illustrative.

Bottom line

A freelance rate card in India in 2026 is less about fancy design and more about named packages in ₹, revision limits, UPI advances, and milestones. Build the floor rate, productise three tiers, attach payment triggers, and stop renegotiating your worth in every chat.

If you want that loop as Excel + guide + copy-paste templates, the Indian Freelancer Client Ops Kit matches the ops problem. Pair it with proper invoicing when money actually moves.

Verify commercial and tax rules on official sources; get legal review for high-stakes contracts.


Client Ops Kit Finance Kit
Proposal, SOW, packages GST invoices
Revision log & milestones plan Payment ledger & tax planner
When to pause for non-payment Reminder emails & compliance notes

• Revisions included:
• Not included:

STANDARD — ₹______ (Recommended)
• …

PREMIUM — ₹______
• …

  • Rate Card Packages — Starter / Standard / Premium + add-ons in ₹
  • Project Tracker — status, contract value, balance due, next action
  • Milestone Schedule — money linked to delivery triggers
  • Revision Log — in-scope vs billable extras
  • Ops Dashboard — weekly totals on pipeline, overdue milestones, extras

    • 3-package comparison table
    • Recommended tier + why
    • Timeline and assumptions
    • Milestone payment schedule (client-facing)
    • Next step (kickoff only after advance)

Kickoff should be a commercial gate: advance received, SOW agreed, channels set — then you build.

  • Revision rounds included
  • Response channel / hours
  • Price in ₹ (fixed preferred over open-ended hourly for productised work)

Add-ons (examples): extra revision round, rush delivery, source files, extra page/screen, training call. Price them so scope creep becomes a line item, not a favour.

  • Proposal rewritten from scratch for every lead
  • Client picks a vague “budget around X” and you underquote
  • Scope creep via WhatsApp with no change order
  • “Pay after launch” with no milestone triggers
  • Projects living in your head, not a tracker

Indian defaults that help: UPI advances, clear INR package prices, and splits like 40/30/30 (or 50/50 for short jobs) tied to delivery — not vibes.

Top comments (2)

Some comments may only be visible to logged-in visitors. Sign in to view all comments.