Headless vs. WordPress: pick the right tool

Stop letting your developer pick your stack. Here's how to choose between headless, WordPress, and Webflow based on who maintains the site, not what's trendy.

The wrong way to pick a website stack is to ask your developer what they want to build in. The right way is to ask who's going to update the site every week for the next three years, and pick the tool that suits them.

Three real options for service businesses: WordPress, Webflow, or a headless setup (typically Next.js or similar with a CMS like Sanity or Contentful). Each one is correct for a specific situation and disastrous for the others.

Webflow — for marketing-led teams that ship weekly

If a marketer is updating the site without a developer, Webflow is the default answer. Designers can build pages without a developer in the loop, marketers can ship campaigns and landing pages on their own, and the visual fidelity is high enough to compete with custom builds.

Trade-offs: hosting cost is higher than WordPress, custom integrations require some workaround, and very large sites (500+ unique pages) start to creak. For most service businesses with 20–80 pages and weekly updates, none of that matters.

WordPress — for SEO-heavy plays with non-technical updates

If the site is going to grow into hundreds of long-form pages — locations, services, blog content, glossary entries — and the updaters are non-technical, WordPress with a clean theme and a structured CMS setup is still the right answer. The plugin ecosystem covers almost every integration. Hosting is cheap.

Trade-offs: design quality drifts over time as plugins layer up, security patches are constant, and the codebase will eventually need a developer to keep clean. WordPress rewards teams that are willing to maintain it and punishes teams that aren't.

Headless — for developer-led builds with custom backends

If the site is a product surface — gated content, complex data integrations, custom user flows, real-time data — headless is correct. Next.js plus a structured CMS gives the engineering team the flexibility they need without forcing the marketing team into a developer queue for every copy change.

Trade-offs: highest cost to build, highest cost to maintain, requires an engineer in the loop forever. Choose this only when the site is doing things a no-code tool can't do.

Pick the stack the people maintaining the site can use without asking for help. Everything else is secondary.

The decision tree

• Who updates the site? Marketer → Webflow. Marketer + occasional developer → WordPress. Engineer → headless.
• How many pages in 12 months? Under 80 → Webflow. 80–500 → WordPress. Doesn't matter if user flows are custom → headless.
• Are there custom integrations beyond marketing tools? No → Webflow. Some, with plugins → WordPress. Yes, deep → headless.
• Is SEO long-tail (locations, services × cities, glossaries)? No → Webflow. Yes → WordPress or headless with a strong CMS.
• How fast does the team need to ship landing pages? Daily → Webflow. Weekly → WordPress or Webflow. Monthly is fine → headless.

Mistakes we see most often

• Picking headless because it's trendy, then realizing every copy change requires a deploy
• Picking WordPress for a small site and watching plugin sprawl wreck the load time
• Picking Webflow for a 500-page SEO play and hitting CMS limits at month six
• Letting an agency pick the stack based on what they're best at, not what the team can maintain

What to do before you decide

• Map who updates the site — names, not roles
• Project page count over 24 months, including landing pages
• List every integration the site needs to talk to (CRM, scheduler, payments, analytics)
• Decide the publishing cadence the team actually wants to maintain
• Then pick the stack

On our funnel and website builds we ship in all three depending on the brief — there's no house favorite. The question is always 'who maintains it after we're gone.'

The bottom line

Stack is downstream of maintenance. Pick the tool the people running the site can run. And if you're rebuilding, the six funnel sections piece covers the structure before you pick the platform.