Framer vs Webflow vs Next.js for your marketing site

Every solo founder, twice a year, has the same internal debate. Framer is so pretty. Webflow is so powerful. Next.js is what I'm already using. Which one for the marketing site? They post on X, get 40 contradictory replies, and ship nothing for two weeks.

The honest answer is that the three tools are good at different jobs, and the wrong-tool penalty is real. Here's the tradeoff, by job, with the indie-hacker shipping speed factored in.

The three jobs of a marketing site

Before the tool argument, name the job. Most marketing sites do one of three things, and the right tool depends entirely on which.

1. 01Editorial site. A landing page, an about page, a pricing page, a small set of marketing surfaces. Updated weekly or less. The job is visual polish and fast iteration on copy and design.
2. 02Content engine. A site with a blog, changelog, docs, customer stories. Updated daily. The job is SEO, content authoring, and scaling structure.
3. 03Product + marketing as one app. The marketing site shares components with the product UI. The job is consistency and engineering velocity, not Figma-style design ergonomics.

Framer: the editorial site weapon

Framer in 2026 is closer to a magazine layout tool than a website builder. Its motion primitives are excellent, the components library is real, and the design-to-publish loop is the fastest in the category.

Where it wins

• Visual polish per minute spent. Nothing else gets a landing this pretty this quickly. Animations, scroll effects, and editorial type are first-class.
• Designer-friendly authoring. A non-engineer can update the hero copy at 11pm without a deploy. This sounds small until you live it.
• Built-in CMS for marketing pages. For 5–15 marketing pages, the CMS is more than enough.

Where it loses

• Doesn't share components with your product. Your button in the app and your button on the marketing site will drift. Forever.
• Custom code is awkward. You can embed components, but the moment you need real React, you're fighting the tool.
• SEO is fine, not great. Page speed varies; rendering and meta control are weaker than a hand-built Next.js site.
• Monthly cost. $15–$30/site/month, which is fine until you have three sites.

Reach for Framer if your job is editorial site, you have a designer (or design taste) on the team, and the marketing surface is meaningfully separate from the product UI.

Webflow: the content engine workhorse

Webflow is the boring-but-capable choice. It's the tool agencies pick when they need a CMS that won't break, an SEO foundation that's actually solid, and a non-engineer ability to add pages indefinitely.

Where it wins

• Real CMS at scale. Hundreds of blog posts, customer stories, doc pages. Webflow handles this; Framer doesn't pretend to.
• SEO is excellent. Built-in sitemap, meta control, schema markup, page-speed scores in the 90s when you behave.
• Editor workflow for non-engineers. Marketing hires can ship pages without touching Git.
• Mature ecosystem. Memberships, e-commerce, multi-language. You'll outgrow Webflow last.

Where it loses

• Visual ceiling lower than Framer. You can build beautifully in Webflow, but you'll work harder for it. The motion and layout primitives are less expressive.
• Same product-share problem. Webflow components don't reach into your React app.
• Pricing climbs fast. Sites + CMS + workspace hits $40–$60/month quickly. Worth it if the CMS is doing real work.

Reach for Webflow if your job is content engine, you'll publish weekly, and you need a CMS that won't be your bottleneck at year two.

Next.js: the spine that scales

Next.js (or Astro, or Remix) is the unfun answer that usually compounds best. Your marketing site shares the tokens, components, and deploy pipeline with the product. Your hire-able skill stack is the same on both sides.

Where it wins

• One component library across product and marketing. The button, the input, the card, all shared. Brand consistency is free instead of constant work.
• Total control over performance, SEO, and rendering. Edge functions, ISR, static generation, OG image generation, all native.
• No monthly cost. Vercel free tier or $20/month covers most indie launches.
• Compounds with your eng team. Every improvement to the product UI also improves the marketing UI.

Where it loses

• Designer/marketer workflow is engineer-mediated. A copy change is a PR. This is fine for a one-person team; it's a bottleneck for a six-person one.
• Slower visual iteration. What Framer does in a drag, Next.js does in five minutes of CSS. Multiply by every section.
• You'll build a CMS layer eventually. MDX, Sanity, Contentful, something. Webflow gives this for free.

Reach for Next.js if your job is product + marketing as one app, you're an engineer or you have one, and the marketing site is small (under 20 pages) for the foreseeable future.

The decision matrix

• Solo founder, ships fast, has design taste, marketing site is the main surface: Framer.
• Solo founder or small team, publishes weekly, content-heavy site: Webflow.
• Solo engineer-founder, marketing site is small, product is the main surface: Next.js. The component-sharing alone pays for itself.
• Small team with a designer and an engineer, both surfaces growing: Framer for the marketing pages + Next.js for the product. Hand off at the auth wall. This combination is more common than the X discourse admits.
• Agency-style team shipping client sites: Webflow. Hand-off is mature; clients can update without you.

Three things tool choice doesn't fix

1. 01A weak hero. Framer's prettiest template can't save a vague value prop. Tool follows clarity, never the reverse.
2. 02A missing distribution plan. A flawless landing page nobody sees is a portfolio piece, not a launch. Where you'll get traffic is a bigger decision than which tool you used to render it.
3. 03Inconsistent brand voice. If your tweets read formal and your hero reads sarcastic, no tool unifies them. That's a writing problem.

Ship one

The landing pages collection has examples in all three tools, tagged by stack, so you can see how the same hero pattern looks when shipped from Framer, Webflow, and Next.js. Pair with the UI libraries collection if you're going the Next.js route, the library decision and the framework decision are joined at the hip.