Founders ask for the “best” stack the way tourists ask for the best restaurant. Best for what. At what team size. With which budget for upkeep.
Here is how I pick among WordPress, Shopify, or Next.js for real projects — content sites, commerce, and custom products — without treating any of them as a personality.
Start from the job, not the Hacker News mood
Three jobs cover most of what lands in my inbox:
- Publish and rank — articles, services pages, lead gen, editorial
- Sell products — catalog, checkout, fulfillment, trust
- Ship a product UI — dashboards, generators, signed-in tools, weird workflows
The stack follows the job. Mixing jobs is fine; pretending one tool owns all three forever is how rewrites start.
When I choose WordPress
WordPress wins when content operations are the product:
- Editors need drafts, roles, previews, and plugins they already understand
- SEO tooling and content velocity matter more than custom checkout
- The site is mostly pages and posts with a few forms
- Budget prefers a theme-plus-care retainer over a full JS product team
Playbook-style sites, agency marketing sites, and blog hubs fit here. Gutenberg plus careful performance work is enough. I do not apologize for WordPress when the job is publishing.
Where I push back: stuffing a complex SaaS into WP with twenty plugins, or fighting WooCommerce into something Shopify already solves cleanly for that merchant.
When I choose Shopify
Shopify wins when commerce is the center of gravity:
- Cart, checkout, tax, and payment complexity you should not rebuild
- Merchandising staff live in admin all day
- Apps and Channels matter (ads, marketplaces, POS)
- The brand needs a reliable PDP/collection/cart loop more than a bespoke design system flex
Themes (Online Store 2.0), metafields, metaobjects, and Functions cover a huge amount of “custom” without leaving the platform. Hydrogen / headless enters only when the theme ceiling is real — not because headless sounds senior.
Where I push back: using Shopify as a CMS for a non-commerce content network, or installing an app for every itch until the storefront can barely paint.
When I choose Next.js (or similar)
A React/Next app wins when the UI is the product:
- Auth, billing states, multi-step tools, and dense interaction
- Calculators, editors, agent consoles, B2B portals
- You need full control of rendering, caching, and API routes
- The team can own deployments, previews, and JS complexity
I build a lot of thin utilities and client portals in this world. Commerce can still sit on Shopify via Storefront API or Hydrogen when the storefront must be deeply custom — but that is a cost and staffing decision, not a default flex.
Where I push back: rebuilding a brochure site in Next because someone wants to use server components on a five-page marketing site with one form. WordPress (or even a static site) would ship sooner and edit easier.
Hybrid patterns I actually ship
- WordPress for content + Shopify for store — linked clearly; do not duplicate catalog in two CMSs without a sync plan
- Shopify theme for store + Next for the custom app (playbooks, calculators, account tools)
- Next marketing site + Shopify checkout — only when the team can maintain both honestly
Hybrids fail when ownership is unclear: who updates pricing truth, where redirects live, which domain hosts trust pages.
Questions I ask before recommending
- Who edits content weekly — developers or editors?
- Is checkout a core path or occasional?
- How many SKUs, and how messy is the catalog?
- Do we need signed-in product UI beyond “my orders”?
- Who is on-call for plugins, theme apps, or Node deployments in six months?
- What is the two-year maintenance story, not the launch week story?
Answers beat trend videos.
A simple chooser
- Mostly publish → WordPress (or static if truly tiny)
- Mostly sell → Shopify first
- Mostly tool/product UI → Next.js (or similar)
- Sell + heavy custom UI → Shopify + selective headless/custom app
- Publish + sell lightly → do not force one platform to fake the other; integrate deliberately
Total cost of ownership beats framework Twitter
Licenses are visible. People costs are larger. A Shopify Plus fee can be rational if it removes a checkout engineering team you do not have. A Next.js app can be rational if your product UI changes weekly and editors are not in the loop. WordPress VIP or careful managed hosting can be rational if content is the business.
I put TCO on the page: platform fees, apps, hosting, agency hours, and the cost of a slow hire when something breaks. Trends do not appear in that table — operators do.
SEO and content velocity as a stack input
If the growth plan is fifty articles and landing pages a quarter, WordPress (or a serious CMS) usually wins for editor speed. You can make Next.js editorial-friendly with a headless CMS; you just bought two systems. Sometimes that is right. Often merchants underestimate the editorial UX gap.
Commerce SEO leans on Shopify’s product information architecture plus clean theme templates. Fighting the platform is expensive; extending it with metafields is usually enough.
AI features do not pick the stack alone
People assume AI means Next.js. Nonsense. I ship AI into Shopify apps, theme-adjacent workers, WordPress tools, and Next calculators. The model cares about your API design and your data, not your marketing site generator. Pick the stack for operators; attach AI where the meter and the workflow make sense.
Migration triggers I take seriously
- Theme ceiling reached and business value justifies Hydrogen cost
- WooCommerce maintenance exceeding Shopify migration pain for a catalog-heavy brand
- WordPress plugin debt blocking security updates
- Next brochure site that editors refuse to touch
Migrations are projects, not weekend upgrades. I would rather optimize the current stack for six months than migrate on vibes.
A closing recommendation style
On calls I say the recommendation in one breath: “Shopify for the store, WordPress or the Playbook stack for content education, Next for the signed-in tools and calculators.” When it is simpler — “just Shopify” or “just WordPress” — I say that too. Clarity is the deliverable.
Team skills as a constraint
A brilliant Next.js architecture with no JS maintainers is a liability. A Shopify store with a strong merchandiser and a part-time theme developer is often enough. WordPress with an editor who fears updates needs managed care, not more plugins.
I match stack to the skills that will still be around in eighteen months. If the founder is the only technologist and their strength is merchandising, Shopify-first is kindness. If they have a product engineer and a designer shipping weekly, Next earns its keep. The “best stack” is the one your actual humans can operate without heroics.
Pick for the job, keep the ego out
I work across all three from Karachi: WordPress content systems, Shopify themes and integrations, and Next.js tools with AI features that have cost ceilings. The win is not brand loyalty to a framework. The win is a merchant or founder who can operate the thing after I ship it.
If you are stuck choosing, describe the weekly operator — editor, merchandiser, or power user — and the stack usually announces itself.