The two bands, side by side
The full argument lives in the main comparison guide; this page is the India-market INR math from the calculator:
| Scope | WordPress band (INR) | Custom band (INR) |
|---|---|---|
| Business site, 5 pages | ₹80,000 – ₹3,30,000 | ₹1,05,000 – ₹4,40,000+ |
| Ecommerce store | ₹1,80,000 – ₹9,60,000 | ₹4,50,000 – ₹13,60,000+ |
| Complex application logic | ₹2,50,000 – ₹15,00,000 (fighting the CMS) | ₹5,40,000 – ₹28,00,000+ (built for it) |
| Monthly care | ₹4,000 – ₹14,200 | ₹5,000 – ₹15,000 |
Where WordPress wins the math
- Content-driven sites: blogs, news, marketing pages. The CMS is the product.
- Budgets under ₹3,00,000 with real content needs.
- Teams that need to publish without a developer on retainer.
- Ecommerce under a few thousand SKUs where WooCommerce's ecosystem covers the requirements.
Where custom wins the math
- Application logic: workflows, permissions, calculations, integrations that no plugin models.
- Long-lived products where plugin lock-in becomes an annual tax.
- Performance-critical builds where CMS overhead is the bottleneck.
- Anything where "the plugin does 80% of it" means the remaining 20% is your business.
The escape cost nobody prices
Page-builder WordPress (Elementor/Divi stacks) accumulates an escape cost: moving away means rebuilding pages from scratch. That future cost belongs in today's comparison. A cleanly built WordPress with native blocks and a sane theme escapes cheaply. A builder-stack WordPress does not. Ask any quote which kind of WordPress you are buying.
The decision, compressed
Content site with standard needs: WordPress, done properly, at the lower band. Application logic, unusual requirements, or a product you will maintain for years: custom, at the higher band, bought once instead of fought forever. Still unsure: run both configurations in the calculator and compare the bands against your three-year plan, not your launch month.