Custom is a cost, not a status symbol
Custom means you pay for unique templates, unique bugs, and unique knowledge in one team’s heads. That can be the right cost. It is never a brand badge buyers check.
Status-driven React builds often recreate WordPress badly: a tiny CMS bolted on later, no preview, founder waiting on a developer to change GSTIN in the footer.
We ask “what can WordPress not do?” If the answer is “look premium,” that is a design and performance problem — often solvable on WordPress or a static build without a full app.
Write the constraint on one line
Example: “Editors cannot create the 40 location landing templates we need without breaking layout” or “We need a logged-in pricing calculator.” If you cannot write the constraint, you are not ready to go custom.
What WordPress already does well
Drafts, roles, media library, a million tutorials, and a Chennai freelancer market that can take over a sane theme. For brochure + blog, that is the product.
WooCommerce remains a reason to stay in the WP orbit if the store is modest — see WordPress vs Shopify.
WordPress fails when the front becomes a page-builder swamp, when you need app routing, or when every plugin is a security and speed incident. Those are reasons to leave or to rebuild WordPress strictly — not automatically to React.
A strict WordPress rebuild is a valid “custom”
Custom theme, almost no plugins, block patterns. That is still WordPress. It is cheaper to maintain for editor-heavy teams than a React app with no CMS.
What Next.js uniquely buys you
Component-level control, routing, SSR/SSG choices, and a codebase you can review in Git. Marketing + product UI can share a design system. Performance is yours to win or lose — not a theme author’s accident.
You can generate thousands of SEO pages from data (locations, SKUs, docs) without 1,000 WordPress pages someone must click “publish” on. That is a real Next.js job.
You also buy Node deploy, preview environments, and the need for a developer on retainers. Unique does not mean free.
App Router is not a business requirement
Founders should not specify React versions. Specify outcomes: TTFB, editor flow, templates. We pick Next.js features to match, not to follow last year’s conference.
Team skill and maintenance
WordPress maintainers are easier to find in India at SME budgets. Next.js maintainers cost more and will not “just hop on cPanel.” Plan the retainer before the repo.
If your IT person is a cousin who updates plugins on Sundays, WordPress (or static HTML) matches the org. If you have engineers who already ship Next.js, custom matches the org.
Agencies that disappear after a React launch leave you with a black box. Demand documentation, env vars ownership, and a walk-out packet — same as we demand for WordPress credentials.
Who merges the next copy change
If the answer is “open a GitHub ticket,” custom is honest. If the answer is “the intern in wp-admin,” stay on WordPress or add a real CMS to Next.js from day one.
SEO: SSR, metadata, and content ops
Next.js can render crawlable HTML and precise metadata. WordPress can too. Google does not award points for using React. Thin pages lose on both.
Content ops: WordPress wins brute force publishing. Next.js wins structured generation and consistent templates. Choose based on how pages are born — writers vs data.
Core Web Vitals: Next.js gives you the knife; you can still ship a 3 MB client bundle. WordPress gives you a theme; you can still strip it. Measurement on Indian mobile stays mandatory.
Preview for SEO pages is non-negotiable
If marketers cannot preview a landing template before it ships, they will stop requesting pages — and your custom SEO factory dies. Budget preview, not just production render.
Headless WordPress as a middle path
Writers keep wp-admin; the public site is Next.js fetching WP. You keep familiar editing and gain a custom front. You also keep WordPress hosting, plugin risk, and a front-end deploy.
Use it when the editorial process is the reason to stay on WP and the front-end is the reason to leave themes. Skip it when you have five pages — that is a static or simple Next.js markdown site.
Preview, webhooks, and image pipelines are the hard parts. Demos that only show a title fetch are not a build estimate.
Two uptimes, two bills
If WordPress is down, editors stop. If Next.js is down, the site is down. Monitor both. Headless is not “serverless magic” that deletes operations.
Budget floors from Chennai
Published: Landing Page ₹7,500; Static Website from ₹18,000; Business Website ₹28,000; E-Commerce Store ₹38,000; Dynamic Business Website + SEO ₹50,000 + ₹15,000/mo; custom Next.js / web apps from ₹50,000.
The custom floor covers a scoped app or marketing front — not an unbounded design studio plus a CMS plus a dashboard. Discovery exists so we do not lie with that number.
Hosting on Vercel/similar or an Indian VPS is extra unless quoted. WordPress hosting is extra unless quoted. Compare apples: build + host + care.
₹50,000 custom vs ₹50,000 WordPress + SEO combo
Those are different products that happen to share a number. One is an engineering floor. The other is a CMS site plus a month-one SEO retainer. Do not swap them in a spreadsheet without reading the scope.
Security, hosting, and ownership
WordPress security is patch hygiene and least-privilege users. Next.js security is dependency and env-var hygiene plus whatever APIs you added. Neither is “secure by brand.”
Ownership: Git repo on the company org, domain on the company registrar, CMS keys on company email. We insist on this from Thousand Lights projects.
A custom site you cannot deploy without us is not ownership. CI/CD and a documented release path are part of going custom — not a nice-to-have.
Secrets do not live in WhatsApp
.env files, hosting tokens, and DB URLs stay in a password manager the company owns. That is more important than whether the stack is PHP or Node.
When to stay on WordPress
Editor-led SME, brochure + blog, possible WooCommerce, no in-house JS, success = WhatsApp leads from service pages. Stay. Spend the custom budget on content and SEO instead.
Also stay if your only complaint is visual. A strict theme rebuild or even Framer (marketing-only) may be cheaper than React. See Wix vs WordPress if the real issue is editor fear, not architecture.
Boredom is not a migration reason
Teams get bored of wp-admin and buy Next.js. Six months later they miss drafts and roles. We will push back on boredom-driven custom work.
When to go Next.js — and a phased path if you are unsure
Go Next.js when: product + marketing share UI, you generate pages from data, performance/ownership is a board-level constraint, and a maintainer exists. Go headless when writers must stay in WordPress.
Phased: ship a static or WordPress site for the 90-day lead job; isolate the one custom widget (calculator, portal) as a Next.js island later. Do not bet the whole domain on an unproven app.
Phased: keep WordPress, measure the template that hurts, then rebuild only that template family in Next.js behind the same domain with redirects. Incremental is allowed.
Start with consultation or contact. Hubs: Next.js, WordPress, Website Development.
The 90-day test
If custom Next.js cannot name a metric that will move in 90 days (speed on a template, editor time, conversion on a tool), it is a rewrite for its own sake. We would rather sell you a ₹7,500 lander that supports ads this month.
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.