The Choice You Are Actually Making
Platform debates are usually argued as if one option is objectively better. They are not comparable in that way. Each of the four represents a different trade between speed of change, degree of control, and who carries the maintenance burden. Picking well means being honest about which of those three you can least afford to get wrong.
The Four Options at a Glance
| Framer | Webflow | WordPress | Custom code | |
|---|---|---|---|---|
| Time to launch | Fastest | Fast | Moderate | Slowest |
| Design ceiling | High | High | Theme-dependent | Unlimited |
| CMS maturity | Adequate | Strong | Strongest ecosystem | Whatever you build or attach |
| Ongoing maintenance | Minimal | Minimal | Significant | Moderate, on your terms |
| Ownership | Platform-dependent | Platform-dependent | Full | Full |
| Cost at scale | Rises with seats and traffic | Rises with seats and traffic | Flat, plus labour | Flat, plus labour |
| Editor experience for non-technical staff | Good | Good | Familiar to most | Depends entirely on the build |
Framer: Speed, and What It Costs You
Best for: startups, landing pages, portfolios, design-led marketing sites, teams who need to ship this month.
Framer's advantage is that a designer can go from idea to live site without a handoff. For a marketing site that will be redesigned within eighteen months anyway, that is a genuine strategic advantage, not a compromise. Performance defaults are good and the output is clean.
Where it strains: deeply structured content with many interrelated collections, complex e-commerce, unusual integrations, and any requirement that falls outside what the visual editor exposes. You are also renting the platform — pricing changes and roadmap decisions are not yours to make.
Webflow: The Middle Path
Best for: growing businesses with real content operations, marketing teams who publish frequently, sites that need structure without a developer on call.
Webflow's CMS is the strongest of the visual builders: multiple collection types, reference and multi-reference fields, and the ability to relate content across collections. That matters the moment you have case studies that link to services that link to industries. Its SEO controls are granular, and its hosting is fast without configuration.
Where it strains: cost at scale, particularly with many editor seats or high traffic; e-commerce beyond moderate complexity; and any logic more elaborate than the platform's interaction model supports. Exported code exists but is not a practical long-term escape hatch for CMS-driven sites.
WordPress: Ownership, With Homework
Best for: content-heavy publishing, sites needing a specific plugin ecosystem, organisations that want to own the whole stack, and anyone with a maintenance budget or an in-house technical owner.
WordPress powers a large share of the web for good reasons: everything integrates with it, editors already know it, hosting is cheap and portable, and nobody can change your pricing or deprecate your features. Used as a headless CMS behind a modern front end, it is a genuinely excellent 2026 architecture.
Where it strains: maintenance is not optional. Plugin updates, security patching, and performance discipline are ongoing work, and neglect has consequences — we wrote a whole guide on what happens when a WordPress site is left unpatched. Page builders and plugin sprawl are also the most common cause of the slow sites we get asked to diagnose.
Custom Code: The Highest Ceiling
Best for: products rather than brochures, distinctive interaction and motion, heavy integration with internal systems, strict performance requirements, and businesses at a scale where platform constraints cost more than engineering does.
A modern custom stack — a React framework such as Next.js, static or hybrid rendering, a headless CMS for editing — gives you complete control over markup, performance and behaviour. The performance ceiling is meaningfully higher because nothing is loaded that you did not choose to load, and that has downstream effects on how the site performs in search.
Where it strains: it needs developers. Not necessarily many, and not necessarily continuously, but the ability to change things is contingent on technical availability unless the CMS layer was designed carefully. For a standard five-page marketing site with no unusual requirements, it is usually solving a problem you do not have. Our longer treatment of that trade-off is in choosing between no-code, low-code and custom code.
Deciding: Five Questions
- Who will change the site after launch, and how technical are they? If the answer is a marketing coordinator with no developer support, that eliminates some options immediately.
- How structured is your content? Flat pages suit anything. Interrelated collections push you toward Webflow, WordPress, or a proper headless setup.
- What has to integrate? List every system. If the list is long or unusual, visual builders start requiring workarounds, and workarounds accumulate.
- What is the realistic lifespan of this build? Eighteen months argues for speed. Five years argues for ownership and control.
- Is there a maintenance budget? If not, choose a platform where maintenance is somebody else's job, and accept the ceiling that comes with it.
The Migration Cost Nobody Prices In
Content moves between platforms with moderate pain. Design does not move at all — every layout is rebuilt. Integrations are rebuilt. URLs must be mapped and redirected, and if that is done carelessly the traffic goes with it. Budget 60 to 100 percent of an original build for a serious migration.
This is the real argument for spending an hour on the decision rather than inheriting whatever platform your chosen vendor happens to sell. Most agencies recommend the platform they are fastest on. That is not dishonest, but it is not the same as the platform that is right for you, and the difference shows up two years later.
What We Recommend, Plainly
- Pre-launch startup, needs a site in three weeks: Framer
- Growing business, marketing team publishing weekly: Webflow
- Content-heavy publisher, or a business that wants to own everything: WordPress, headless if budget allows
- Distinctive brand experience, product-like interaction, or performance as a differentiator: custom code
- E-commerce as the core business: a dedicated commerce platform, with the storefront built to your design
Kalex Studio builds on all four and has no incentive to sell you the wrong one — most of our work is custom, and we still talk clients out of it when the brief does not warrant it. If you are choosing a platform right now, tell us what the site has to do and we will tell you what we would build it on.