The hidden costs in software projects — the ones that turn a ₹8 lakh quote into a ₹14 lakh spend — are usually five: change requests priced after signing, data migration nobody scoped, third-party fees (payment gateways, WhatsApp, SMS, maps, AI inference), maintenance treated as optional, and vendor lock-in that makes leaving more expensive than staying. Each is predictable, and each can be capped in the contract before you sign.
After years of building software for Indian SMBs — and inheriting projects that went wrong elsewhere — we at NexaEx can say the overruns are rarely exotic. They're the same six or seven items, project after project. This guide names them, puts realistic 2026 INR numbers on each, and gives you the contract language that prevents them.
Why do software projects go over budget?
Because the quote and the project are scoped at different levels of detail. A quote says "admin panel"; the project discovers that means five user roles, an approval chain, and an audit log. The gap between a two-line feature list and working software is where every hidden cost lives. Vendors aren't always being sly — sometimes neither side knew — but the financial risk of that gap almost always sits on the buyer unless the contract moves it.
The fix is boring and effective: pay for a short discovery phase (₹25,000–1 lakh, 1–2 weeks) that produces a written scope with screens, roles, and integrations listed. Vendors who resist discovery are pricing blind — and you'll pay for their blindness in change requests.
The seven hidden costs, with numbers
1. Change requests — the classic
Typical impact: 20–40% over the quoted price. A vendor quotes low to win, then bills every clarification as a change at ₹1,000–2,500/hour. Protection: a discovery-backed scope document, a defined change-request process with written estimates before work starts, and a contingency line of 15% that you control.
2. Data migration
Typical impact: ₹50,000–3 lakh, almost never in the quote. Your ten years of customers live in Excel sheets, Tally, or an old system with no export. Cleaning, deduplicating, and mapping that data into the new system is real engineering. Ask directly: "Is migration of our existing data included, and what format do you expect it in?" Get the answer as a line item.
3. Third-party and usage fees
The subscription layer under your software, billed forever:
| Service | Typical 2026 cost |
|---|---|
| Payment gateway (Razorpay/Cashfree) | ~2% + GST per non-UPI transaction |
| WhatsApp Business API | ₹0.30–0.90 per conversation + BSP fees ₹1,000–5,000/mo |
| Transactional SMS | ₹0.12–0.25 per SMS + DLT registration |
| Google Maps APIs | free tier, then usage billing that stings at scale |
| AI/LLM inference | ₹3,000–40,000/mo depending on volume |
| Email (transactional) | ₹800–5,000/mo |
| Cloud hosting | ₹2,000–50,000/mo |
None of this appears in a development quote because none of it is development. Budget it anyway — for a typical SMB platform, ₹8,000–60,000/month. Our AI chatbot cost guide breaks down the AI line specifically.
4. Licences and "free" components
That admin theme, PDF library, or reporting tool the vendor used may carry a commercial licence (₹5,000–2 lakh one-time or annual) — or worse, a GPL licence with obligations nobody read. Ask for a list of third-party components and their licences at handover. This costs the vendor an hour and can save you a legal headache.
5. Maintenance treated as optional
The largest hidden cost by far over five years. Software needs 15–25% of its build cost annually for patches, API-churn fixes, and small changes — skip it and failures arrive at crisis prices. We wrote a full breakdown in Software AMC and maintenance cost in India; the one-line version is that deferred maintenance compounds like an unpaid credit card.
6. Infrastructure surprises
Projects are demoed on a ₹1,500/month server and sized for launch-day traffic. Then Diwali happens. Load testing before your first peak (₹30,000–80,000) is cheaper than discovering your checkout dies at 200 concurrent users. Also verify: who pays for staging environments, backups storage, and SSL — small numbers, but they arrive as surprises when unowned.
7. Vendor lock-in — the most expensive one
Lock-in isn't a fee; it's the removal of your ability to say no. Symptoms: code in the vendor's repository, hosting in the vendor's cloud account, domain registered to the vendor, WhatsApp/gateway credentials under the vendor's business, no documentation. Each is individually small. Together they mean every future price the vendor quotes is really a hostage negotiation. Escaping a locked-in system typically costs ₹2–10 lakh (reverse-engineering, rebuild, data extraction) — we've done these rescues, and several case studies started as exactly this.
What should you demand in the contract?
A one-page checklist that closes most gaps:
- IP and code ownership transfer to you on full payment; repository access from day one.
- All accounts in your name: cloud, domain, gateway, WhatsApp BSP, app stores. The vendor gets access; you hold ownership.
- Line items for data migration, training, deployment, and documentation — priced or explicitly included.
- Change request protocol: written estimate and approval before any billable change.
- Warranty period: 60–90 days of free bug fixes post-launch (bugs, not new features — be honest about the difference).
- Handover kit: README, deployment runbook, credentials inventory, third-party licence list.
- Exit clause: on termination, vendor must hand over code, data dump, and a transition walkthrough within a defined window.
Any competent agency will sign this without flinching. The ones who won't have told you something valuable before you paid.
How much contingency should you keep?
For a well-scoped project with a discovery phase: 10–15% of the build cost, held by you, released only against approved change requests. For a project quoted off a feature list with no discovery: 25–30%, and honestly, go do the discovery instead — it converts unknown risk into a known price.
Also budget the internal cost nobody counts: your own time. A ₹10 lakh project needs 3–6 hours a week from a decision-maker for reviews and approvals across 3–4 months. Projects where the owner disappears until "final delivery" are the projects that get delivered wrong. Put weekly demos in the contract cadence; our take on running this without drowning in jargon applies whether you work with us or anyone else.
Hidden costs specific to AI projects in 2026
AI features add three cost lines traditional software never had, and most 2026 quotes still omit them:
- Inference is a metered utility. A chatbot or document-processing feature that costs ₹4,000/month in the pilot can cost ₹40,000/month at full rollout. Demand a projection at your real volumes, not demo volumes.
- Evaluation and retraining. Model accuracy isn't a launch property; it's a maintained property. Budget 10–20 hours a quarter for evaluation runs and prompt/knowledge updates, or watch quality drift silently.
- Model deprecation. The model your feature launches on will likely be retired within 18–24 months. If the vendor hard-coded one provider's API with no abstraction layer, the migration is a mini-project (₹50,000–2 lakh) you'll fund on their schedule, not yours.
None of this makes AI features a bad buy — the ROI math often works, as we showed in the AI chatbot cost guide — but they must appear in the total cost of ownership, not be discovered on the third invoice.
GST and payment-term traps
Two commercial details that surprise first-time buyers. First, software development attracts 18% GST — confirm whether quotes are inclusive or exclusive, because on a ₹10 lakh project that ambiguity is ₹1.8 lakh. Registered businesses can claim input tax credit, so an exclusive quote from a GST-registered vendor is normal; an unregistered vendor offering "no GST" is also offering you no enforceable paper trail. Second, watch milestone structures: 50% advance with the balance "on completion" invites disputes about what complete means. Healthier: 30% to start, 40% against demonstrated milestones, 30% on UAT sign-off — and work should begin only after a signed agreement, not a WhatsApp thumbs-up.
A worked example: the ₹8 lakh CRM that cost ₹13.8 lakh
A composite from real projects we've audited. Quoted: ₹8 lakh custom CRM. Actual first-year spend:
- Build: ₹8,00,000
- Change requests (scope gaps around roles and reports): ₹1,60,000
- Data migration from Excel + old system: ₹90,000
- WhatsApp + SMS + hosting, 12 months: ₹1,10,000
- Emergency fixes (no AMC signed): ₹70,000
- Reporting add-on the quote's "reports" line didn't cover: ₹1,50,000
- Total: ₹13,80,000 — 72% over quote.
Every line was foreseeable, and with a ₹60,000 discovery phase and the contract checklist above, roughly ₹4 lakh of it was avoidable. Before you sign anything, pressure-test the numbers in our project cost calculator — and compare quotes on total 3-year cost, never on build price alone. The cheapest quote is frequently the most expensive decision, a pattern we also unpack in the custom CRM cost guide.
Talk to us
If you're holding a quote and want a second opinion, send it over — we'll tell you what's missing from it, even if you build with someone else. Reach us at /contact or WhatsApp +91 97912 97741. We reply within 24 hours.
Frequently asked questions
What are the most common hidden costs in software projects?
Seven recur constantly: change requests priced after signing (20–40% over quote), unscoped data migration (₹50,000–3 lakh), third-party usage fees of ₹8,000–60,000 monthly, component licences, maintenance treated as optional, undersized infrastructure, and vendor lock-in — the most expensive, because escaping it typically costs ₹2–10 lakh.
How much contingency should I keep for a software project?
10–15% of build cost for a project scoped through a paid discovery phase, held by you and released only against approved written change requests. For projects quoted off a bare feature list with no discovery, the honest number is 25–30% — at which point spending ₹25,000–1 lakh on discovery to convert unknown risk into a known price is the better trade.
How do I avoid vendor lock-in in a software contract?
Keep every account in your name — cloud, domain, code repository, payment gateway, WhatsApp BSP — with the vendor holding access, not ownership. The contract should transfer IP on full payment, include a handover kit with runbook and credentials inventory, and define an exit clause delivering code, data dump and a transition walkthrough within a fixed window.
Is GST charged on software development in India?
Yes, software development services attract 18% GST. Always confirm whether a quote is inclusive or exclusive — on a ₹10 lakh project the ambiguity is worth ₹1.8 lakh. GST-registered businesses can claim input tax credit, so exclusive quotes from registered vendors are normal; a vendor offering to skip GST is also skipping the enforceable paper trail.