Shopify, Webflow, or Framer: choosing the right surface

The platform question is a business question

The three platforms we get asked about most often — Shopify, Webflow, Framer — sit in the same conversation despite solving different problems. The choice between them is rarely a design preference. It is a business model question wearing a tooling disguise.

Each platform has a clear centre of gravity. Shopify is built around commerce. Webflow is built around content scale. Framer is built around design velocity. Pick the one that matches what the site is actually doing, and the rest of the decisions get easier. Pick the wrong one, and every workaround afterwards is friction.

The wrong choice is usually a small irritation in month one and a real cost by month six. By the time a team decides to migrate, they have a year of content, an SEO history, a payment integration, and a handful of customisations that do not transfer cleanly. The platform question deserves more thought than it usually gets.

Shopify when commerce is the business

If the business sells physical or digital products and revenue runs through a cart, Shopify is the default. The platform has spent more time on the boring parts of commerce — payment gateways, tax compliance, inventory, shipping, fulfilment integrations, returns — than any other team is going to be able to match.

Shopify works best when the store is the product surface. The marketing site, the catalogue, the cart, the account area, all live in one place, and the team's job is to make that one place convert. Custom themes via Liquid, app extensions, headless storefronts using Hydrogen — the platform stretches a long way before custom development becomes necessary.

Where Shopify pinches is content. The blog and CMS layer is functional rather than excellent. Sites that need significant editorial or marketing content beyond product pages often end up pairing Shopify with a separate marketing site on another platform — and that pairing, while common, adds complexity.

The honest test is whether more than 60 percent of the site's job is to sell. If yes, Shopify almost always pays back. If the site is mostly content, with commerce as a small bolt-on, the calculation is different.

Webflow when content scale matters

Webflow earned its place by making content-heavy marketing sites maintainable. The CMS, the structured content model, the editorial workflow, the page-builder discipline — all of these mature on a site that has thirty pages and dozens of dynamic items, where most other tools start to creak.

Webflow works best when a marketing or content team needs to publish, update, and iterate without going through engineering for every change. SEO foundations are strong by default. Performance is usually good if the build is restrained. The hosting and CDN handle most of the operational work.

Where Webflow pinches is custom logic. Anything that needs serious application behaviour — gated content, user accounts, complex e-commerce, real-time data — strains the platform quickly. Memberstack, Outseta, Wized, and similar add-ons cover some of this, but each one is a new dependency.

The fit is strongest for businesses where content is the lead generation engine — agencies, SaaS marketing sites, professional services, scaled blog operations. The site is read often, updated often, and rarely transactional.

Framer when design velocity matters

Framer started as a design tool and grew into a publishing platform, and the legacy shows in both directions. Design output is fast, animation-rich, and visually current in a way that Webflow does not always match. Teams that prioritise the marketing site as a design artifact — and want to iterate weekly — find Framer faster than most alternatives.

Framer works best when the marketing site is a small set of pages — homepage, product, pricing, about, contact, maybe a few campaign pages — and the design changes often. Startup launches, product reveals, agency portfolios, conference sites, anywhere the design rhythm matters more than the content volume.

Where Framer pinches is at scale. The CMS is improving but still less mature than Webflow's. SEO and structured content are workable but require more discipline. Complex layouts with many dynamic templates can become harder to manage as the site grows.

The fit is strongest for sites under twenty pages, with a small editorial team, where the design quality of every page is part of the brand and the team wants to ship changes without a developer.

The decision questions

Three questions usually settle it.

Is the site selling, or explaining? If selling, the answer is Shopify (or a headless commerce setup). If explaining, the question moves on.

How much content will live here in a year? If fifty-plus pages of structured content, Webflow. If under twenty, Framer is on the table.

Who maintains the site day to day? If a marketing or content team that needs autonomy, Webflow or Framer. If a developer who is comfortable in code, the choice opens up further to platforms like Next.js with Sanity or Payload, but the maintenance cost shifts.

A few cases bend the answer. Sites that need both significant content and significant commerce often end up with Shopify for the store and a separate platform for the marketing surface — connected at the brand level, separated at the platform level. Sites with serious application behaviour usually outgrow all three and need a custom build.

What teams get wrong about each

The most common Shopify mistake is over-customising the theme to the point where the platform's strengths disappear. A heavily forked Liquid theme becomes hard to maintain, slow to update, and brittle through Shopify's own version changes. The platform is opinionated for a reason. Working with the grain is cheaper than fighting it.

The most common Webflow mistake is using it for things it is not built for. Membership systems hacked together with three plugins. Booking flows held together with Zapier. Search experiences that strain the CMS. Each individual workaround works, and the combined system eventually does not.

The most common Framer mistake is treating it as a permanent home for a site that should be on Webflow or Next.js. Framer is excellent for the first eighteen months of a fast-moving brand. Some companies outgrow it cleanly and migrate. Others stay too long and end up rebuilding under pressure.

The cost of switching later

Platform migrations are expensive in the ways that do not show up on the invoice. SEO equity has to be preserved with careful redirect maps. Content has to be moved without losing structure. Integrations have to be rebuilt or replaced. The team has to relearn an editorial workflow. None of this is impossible, but all of it is friction that compounds.

The cost of choosing right the first time is mostly in the upfront thinking — an hour of honest conversation about what the site is for, what it will look like in eighteen months, who maintains it. The cost of choosing wrong is paid over years, usually in small frustrations that the team stops noticing until they migrate and feel the difference.

The platform is not the product. But the platform shapes what the product can become, and how cheaply. That is enough reason to pick it deliberately.