What agentic automation
costs in India.

Ask five people what it costs to automate a workflow in India and you’ll get five numbers: ₹15,000, ₹1.5 lakh, ₹6 lakh, ₹25 lakh, and “it depends”. They can all be right — for different scopes, different risk, and different definitions of “done”.

The useful question isn’t “what is the market rate?” It’s “what does a working system cost, and what does it need to save?” This guide gives you the benchmarks, the cost drivers, and a price architecture you can actually budget against.

Two markets, two products

Live automation jobs on Freelancer.in had a median fixed budget of ₹17,374 in November 2026 (n=168), with a middle 50% between ₹5,635 and ₹38,176. At the same time, listed Indian AI agencies cluster at $26–50/hour, and roughly half require a minimum project of $5,000–10,000 (₹4.7–9.4 lakh), according to directory data from TopDevelopers.co.

That’s not a pricing anomaly. It’s two different products:

• A script: one trigger, one action, no permissions, no evals, no handover. Fine for a personal workflow. Not fine for a process your team depends on.
• A system: integrations, error handling, human approvals, logs, cost caps, documentation, and someone to call when it breaks. That’s what a business is buying.

If a quote is below ₹50,000 for a multi-system workflow, ask what happens when the API changes, who owns the code, and what the fallback is. The answer usually explains the price.

Rate benchmarks

The day-rate math: a senior AI engineer in India earns ₹22–36 lakh CTC (Business Standard, July 2026), or ₹16,000–20,000 per working day at 220 days. Add 25% overhead and a 1.25–2.2× margin, and ₹25,000–45,000/day is the honest domestic range. International work carries a 2.5–3× premium because of timezone, security review, and procurement overhead — not because the model is different.

Project ranges

Logo size is a poor proxy for project size. A ₹40 crore manufacturer may pay ₹2.5 lakh for one automation; a ₹400 crore company may pay ₹6.5 lakh. Infer budget from the number of systems touched, whether a P&L owner is in the room, and whether an incumbent IT vendor must be coordinated.

Hourly vs fixed: what the data says

Most consultants still price on time. In a study of nearly 1,000 consultants by Consulting Success, 30% used project-based pricing, 29% hourly, 16% monthly retainers, and 15% value-based pricing. The important number: 51% of value-based consultants landed projects above $10,000, versus 39% of hourly billers. Hourly billing also caps your income and commoditises the work; fixed and value-based pricing remove the client’s uncertainty about the final bill.

But a fixed price before you have seen the data is a guess. That is why we use a middle path: a free 30-minute audit, then a single hourly rate with a not-to-exceed cap. The client gets a fixed ceiling; the studio gets paid for the real scope; neither side is guessing.

How kumoworks prices

Typical ranges: one-workflow pilot 50–70 hours (₹3.0–4.2L at ₹6,000/hour); three-workflow build 120–160 hours (₹7.2–9.6L); ongoing support 4–12 hours/month. These are planning ranges, not quotes. The cap is agreed after the free audit.

Three worked examples:

• Support: 5 CSRs at ₹3.35L CTC, loaded ×1.25. Deflect 35% of Tier-1 contacts = 1.75 FTE released = ₹7.3L/year. A 60-hour build at ₹6,000 = ₹3.6L; 4 hours/month support = ₹24k/month. Payback ≈ 9.8 months.
• Accounts payable: 2 AP staff at ₹4.8L CTC, loaded ×1.25. Release 60% of invoice work = 1.2 FTE = ₹7.2L, plus ₹1L in duplicate/early-payment capture = ₹8.2L/year. A 70-hour build = ₹4.2L; 4 hours/month support = ₹24k/month. Payback ≈ 9.5 months.
• Sales ops: 8 people at ₹3.5L CTC, loaded ×1.25. Release 50% of admin and follow-up capacity = ₹17.5L/year. A 140-hour build = ₹8.4L; 8 hours/month support = ₹48k/month. Payback ≈ 8.6 months.

Count only capacity released or hiring avoided — never headcount cut. And reject work where the fee exceeds 0.9× Year-1 savings. A 12-month payback is the ceiling; 6–9 months is the target.

Commercial terms that matter

• GST: 18% on services. Show GSTIN, invoice series, and place of supply. Exports are zero-rated with an LUT and FIRC/FIRA.
• TDS: clients deduct 10% under section 194J once professional fees exceed ₹50,000/year. Expect a 3–9 month cash lag.
• Payment: hourly, billed weekly against the cap; 4-hour minimum per statement of work. Net-30 maximum.
• Scope: every estimate should list estimated hours, the cap, exclusions — third-party licences, data cleanup, client IT/security approvals, copywriting, change requests, and training beyond two sessions.
• IP: client owns bespoke deliverables on full payment; the consultancy retains generic frameworks and gets a licence back.
• Liability: cap at 12 months’ fees. Exclude indirect loss. Refuse unlimited liability in large procurement MSAs.

Seven questions to ask a vendor

1. What is the hourly rate, and is there a written not-to-exceed cap?
2. How many integrations, and which systems specifically?
3. What is the numeric pass criterion, and what happens if you miss it?
4. Who owns the code, prompts, and credentials at handover?
5. What does ongoing support cover, and what is the monthly cap?
6. What is the cost per run at 10× volume?
7. Can I speak to a client whose workflow is still running after six months?

If the answers are vague, the quote is a guess. A good vendor will show you the scope, the exclusions, the metric, and the handover before asking for a signature.