The jobs headless wins — and the jobs it loses
Wins: structured content reused across surfaces, custom front-end performance, preview of componentised pages, and engineering ownership in Git. Loses: plugin-install culture, cheap theme tweaks, and non-technical preview that “just looks like the site” unless you build that.
WordPress classic wins at volume publishing with contractors you can hire in any Indian city by tomorrow. That labour market is a feature, not nostalgia.
Multi-channel is the real trigger
If the same case study must appear on the marketing site, a partner portal, and an app, APIs earn their keep. If the case study lives on one URL, classic CMS is enough.
Editor experience after the demo
Sanity Studio and Contentful can be excellent once schemas match how writers think. They are hostile when engineers model “modules” that writers experience as a puzzle. WordPress Gutenberg is uneven but familiar.
Preview is the hidden project. Without a working preview URL, editors will Slack screenshots and you have not gone headless — you have gone blind.
Tamil and Hindi in headless studios
Locales must be first-class fields, not a second project. See multilingual sites. Image-only Tamil is still a failure in any CMS.
WordPress as a headless API
Keep WP admin, ACF or block data, and existing editor training. Pay for a Next.js app, hosting, and the plugins that break when nothing is “the theme.” Preview and drafts need extra work.
This path is a bridge for brands with a large WP archive who refuse another migration. It is not cheaper than staying coupled if the front end is a simple brochure. Migration context: Wix to WordPress SEO is a different problem; do not mix them.
Plugin tax does not disappear
SEO, redirects, and forms still need a home. Some WP plugins assume PHP rendering. Budget replacements on the front end.
Sanity, Contentful, and “we will model it later”
SaaS CMS quality is high. India billing, GST invoices, and seat counts are the grown-up conversation. A 12-seat Contentful plan plus Vercel plus an agency retainer is a different sport from a ₹28,000 business website.
Model the content types you have, not a future design system of 40 blocks. Unused flexibility is how writers stall.
Vendor lock-in is real both ways
Export JSON from a SaaS CMS is not a site. WordPress lock-in is plugins and theme PHP. Pick the lock-in you can hire for in Chennai.
Front ends: Next.js is the default for a reason
App Router, metadata, and hosting options make Next.js Development the usual Indian headless front end we recommend. Static export helps some marketing sites; dynamic rendering helps personalised or frequently updated hubs.
Compare coupled options in static vs WordPress vs custom. Headless is a subset of custom — not a third religion.
Preview, ISR, and festival publishes
Editors who publish a Diwali landing at 18:00 need predictable refresh. Document revalidation. A cache that updates “sometime” is a war room.
SEO and GEO implications
You own titles, canonicals, sitemap, and schema in code. That is good if you have a developer. It is bad if marketing expected Yoast. Pair a headless build with monthly SEO that understands the front end.
llms.txt and crawlable HTML still matter for GEO; a JS-only shell without SSR/SSG is how AI and Google both shrug. We add those files when GEO is in scope on Next.js builds.
Redirects live in the front end now
WP redirect plugins will not save you if WP is only an API. Own a redirect map in code or edge config before you cut DNS.
Commerce: do not headless a store you cannot staff
Headless Shopify is a product company decision. Theme Shopify from ₹38,000 is a catalogue decision. WooCommerce coupled to WordPress still wins modest catalogues with content — Shopify vs Woo.
Growing D2C brands often need a better theme and ops, not Hydrogen. We will say so.
Two-site patterns
Shopify checkout + headless or WordPress journal is valid with one analytics plan. Two homepages is not. Stack mixing notes live in the five-stack guide.
Three-year cost, not launch week slides
Classic WP: hosting, care plan, occasional rebuild. Headless: CMS seats, front-end host, agency or salary, schema changes. Model year three. Many “growing” brands are still one marketer and a founder — they should not buy a platform for a 40-person content ops team.
Published Brevia floors remain the brochure and custom entry points, not a promise that headless equals ₹50,000. Complex schemas are quoted.
Hiring in India
WP contractors are abundant. Senior Next.js + CMS people are not cheap in Chennai or Bengaluru. Availability is part of TCO.
When we refuse headless
No in-house or retained developer after launch. No content model. A 8-page brochure. A founder who wants to “just drag.” We will recommend WordPress or even a static site.
Refusal is cheaper than a stranded Studio. Redesign vs rebuild thinking: redesign vs rebuild.
When we refuse to stay on classic WP
Design-system sites that page builders keep breaking, or product UX that is an application. Then custom Next.js is the honest package.
Decision grid from a Chennai discovery call
Editors-first + marketing site → classic WordPress. Design-led small site → Framer/Webflow discussion, not headless. Product UX or multi-channel → Next.js + CMS. Store-first → Shopify coupled. Write the job list before the logo.
Bring sitemap, editor list, and who ships after we leave. Consultation or Contact. Timeline honesty: how long a site takes.
Cost reminder
Landing ₹7,500; Business ₹28,000; Static from ₹18,000; E-Commerce ₹38,000; Dynamic + SEO ₹50,000 + ₹15,000/mo; custom from ₹50,000.
Ready to automate one painful workflow?
Tell us your stack — n8n, Make, Zapier, WhatsApp, or Playwright. Chennai HQ · India delivery · reply within one business day.