When someone asks me whether they should build their website in Next.js, WordPress, Webflow or Framer, my honest answer is that all four are good, and each one is the wrong choice for somebody. The right platform depends less on the technology and more on three questions: who will edit the site, what the site needs to do beyond showing pages, and how much control you need over speed and search.
I build on all four, so I don’t have a favorite to sell you. Here’s how I actually decide, and the trade-offs I explain to clients before we start.
The quick answer
- Choose Framer for a polished marketing site or landing page, built fast, where the team mostly edits text and images.
- Choose Webflow for a content-rich marketing site with a structured CMS that a non-technical team manages every week.
- Choose WordPress when you need a huge plugin ecosystem, a familiar editor, WooCommerce, or you want to own and move your hosting freely.
- Choose Next.js when the website is really a product: custom features, integrations, logged-in areas, complex data, or when performance and SEO need to be fully in your hands.
How they compare
| Next.js | WordPress | Webflow | Framer | |
|---|---|---|---|---|
| What it is | A React framework; you write code | Open-source CMS with themes and plugins | Hosted visual builder with a CMS | Hosted visual builder, design-first |
| Who edits content | Developers, or editors through a headless CMS | Anyone, via the familiar dashboard | Marketing teams, via the Editor | Designers and marketers, on the canvas |
| Custom features | Anything you can build | Plugins or custom PHP | Limited; integrations and embeds | Limited; components and embeds |
| Performance control | Complete | Depends on theme, plugins and hosting | Good defaults, limited tuning | Good defaults, limited tuning |
| Hosting | Your choice | Your choice | Webflow only | Framer only |
Framer: fastest from design to live
Framer feels like a design tool that happens to publish websites. Layouts, animation and responsive breakpoints are all visual, and a skilled designer can take a site from idea to launch remarkably quickly. It has a CMS for blog posts and simple collections, and hosting, SSL and a global CDN are handled for you.
Where it fits: startups, portfolios, product launches and campaign pages, where the look and the speed of iteration matter more than deep functionality. Where it struggles: complex content structures, heavy integrations, and anything that needs custom server logic. You’re also committed to Framer’s hosting and pricing, and moving away later means rebuilding.
Webflow: a CMS your marketing team will actually use
Webflow gives designers precise control over layout, with the output mapped closely to real HTML and CSS. Its real strength is the CMS. You can define structured collections like services, locations, team members or case studies, design one template, and let the team add entries without touching the layout.
Where it fits: marketing sites with lots of structured pages that change often, run by a team without a developer on hand. Where it struggles: custom application logic, complex user accounts, and very large collections. Like Framer, it’s a hosted platform, so you trade some freedom for convenience.
WordPress: flexible, familiar, and only as good as its setup
WordPress runs a large share of the web for good reasons. It’s open source, it can be hosted anywhere, nearly every marketer has used its dashboard, and there’s a plugin for almost everything. With WooCommerce it’s also a capable store. I still recommend it often, especially for content-heavy sites and businesses that want to own their stack outright.
The catch is that WordPress quality varies enormously. A lean custom theme on good hosting can be fast and secure. A heavy page builder with thirty plugins can be slow, fragile and a security worry. If you choose WordPress, budget for updates, backups and a sensible plugin policy. This site ran on WordPress before I rebuilt it, and I wrote up how I moved it in migrating from WordPress to Next.js without losing SEO.
Next.js: when the website is really software
Next.js is a framework for building websites and web applications in React. There’s no visual builder. Everything is code, which is both its cost and its power. Pages can be pre-rendered as static HTML for speed, rendered on the server for fresh data, or mixed page by page.
I reach for it when a project needs things the builders can’t do cleanly: booking flows, client portals, dashboards, API integrations, AI features, or a site that shares data with a custom CRM. It also gives complete control over Core Web Vitals, structured data, sitemaps and redirects, which matters when search traffic is a real part of the business. If you want your team to edit content without a developer, you pair it with a headless CMS, so editors get a friendly interface while the front end stays custom.
The trade-off is cost and dependency. A custom build takes more time up front, and changes to layout or features usually need a developer. For a five-page brochure site, that’s rarely worth it.
The questions I ask before recommending one
Who will edit it, and how often?
A site that changes weekly needs an editing experience the team is comfortable with. The best platform is useless if nobody dares to update it.
What needs to connect to it?
Calendars, CRMs, payment systems, EHRs, inventory, AI assistants. Each integration pushes you toward platforms that allow real code. This is often where the custom CRM versus off-the-shelf conversation starts too.
How important is search?
All four can rank well if the fundamentals are right. I cover those in my technical SEO checklist. The difference is how much control you have when something needs fixing.
What happens in three years?
Hosted builders are convenient until you outgrow them. Open platforms and custom code take more care but move with you. Neither is wrong; it’s a choice worth making on purpose.
My honest take
Most small businesses don’t need custom code, and I’ll say so. Many do need more than a template, especially once the website becomes part of how they operate rather than just how they’re found. The sites I’ve built, from PrintVision to real estate and healthcare clients in my portfolio, span this whole range because the businesses behind them did.
If you’re weighing a new site or a rebuild, tell me what it needs to do, who will run it, and what’s frustrating about the current one. I’ll recommend the platform I’d choose if it were my own business, even if that means a smaller project.
