Updated November 20, 2026
Webflow vs Framer vs code
Mike Stilling has shipped production SaaS marketing sites both in Webflow (at Abstract) and in code (at Rewatch, FireHydrant, and on 5+ sites through the studio Stilling). This guide is an honest take on how to choose between them, based on that experience. The bias up front: Mike builds in code these days. The comparison tries to be fair anyway.
The short answer
Pick the tool your team can actually maintain.
- Webflow: content-heavy sites, big CMS, and a marketing team that wants visual control without engineers.
- Framer: small, design-led sites that need to launch fast and change often.
- Code (a static site generator like Eleventy): you have someone comfortable in HTML, CSS, and Git, you want custom integrations or interactive demos, or you want no lock-in and no platform bill.
None of these is the wrong answer for most SaaS companies. The wrong answer is choosing a tool nobody on the team can confidently change.
At a glance
| Webflow | Framer | Code (e.g. Eleventy) | |
|---|---|---|---|
| Best for | Content-heavy marketing sites | Small, fast-moving, design-led sites | Custom, performant, long-lived sites |
| Who edits | Designers and marketers | Designers | Developers and design engineers; marketers via a Git-based CMS |
| CMS | Built in, robust | Built in, lighter | Bring your own (e.g. Decap), or Markdown files |
| Custom code | Supported, with limits | Supported, with limits | Unlimited |
| Lock-in | High | High | Low |
| Ongoing cost | Platform plan per site | Platform plan per site | Hosting only, often free or cheap |
| AI-assisted editing | In-tool AI features | In-tool AI features | Any AI coding tool works on the repo |
Pricing and features change often. Check each vendor's current plans.
Webflow
Mike spent the time at Abstract building in Webflow, rebuilding and redesigning core marketing pages, use-case pages, and a content hub called In the Margin. Webflow later featured several of those pages in its own marketing.
What it's great at:
- Visual building that maps closely to real HTML and CSS. A designer who understands the box model can do almost anything.
- A mature CMS for blogs, customer stories, and integration directories.
- Letting marketing ship pages without waiting on engineering.
What to watch for:
- Class systems get messy fast without discipline. Mike spent real time untangling utility class conventions.
- Integrations and marketing ops often end up in no-code automation chains that are hard to see and debug. Mike ran a lot of Abstract's that way.
- You're tied to the platform's hosting, pricing, and roadmap.
Framer
Framer is the fastest of the three for getting a polished, animated site live, especially for designers already comfortable in Figma-style tools.
What it's great at:
- Speed from design to live site.
- Motion and interaction without code.
- Small sites where the design changes frequently.
What to watch for:
- A lighter CMS than Webflow. Sites with lots of structured content can outgrow it.
- Less control over markup, which matters for accessibility, performance tuning, and SEO edge cases.
- The same lock-in tradeoffs as any hosted builder.
Code (static site generators)
Mike's default now is Eleventy with WebC components and Tailwind, deployed to Netlify or Vercel. One shared boilerplate has powered 5+ production sites for the studio, and this site too.
What it's great at:
- Speed of change once set up. At FireHydrant, Mike rebuilt 300+ pages and 25+ templates in under three weeks, with 50% fewer dependencies and Lighthouse scores up 56%+.
- Anything custom. Smart-routing contact-sales forms that post to Slack and the CRM. Product visuals built in HTML and CSS. An interactive demo that pairs a visitor's phone with the page.
- Sharing conventions with the product. At Rewatch, the marketing site's markup mirrored the product's front end, so product folks could contribute.
- No lock-in, no platform bill. Content lives as Markdown in the repo. With a Git-based CMS like Decap, marketers can still edit through a friendly UI.
- AI tools work great on it. A simple, single-file-per-page structure is unusually easy for AI coding tools to read and edit. See prototyping in code for designers.
What to watch for:
- You need at least one person who's comfortable in code and Git. If that person leaves, you need a plan.
- Setup takes longer up front.
- Marketers who want to build whole new layouts themselves will feel limited without a design engineer around.
How to choose
Answer these honestly:
- Who will change the site most often? Marketers → Webflow. Designers → Framer or Webflow. Someone who codes → code.
- How much content is there? Hundreds of CMS items → Webflow or code. A handful of pages → any.
- Do you need custom integrations or interactive demos? Yes → code, or a builder plus custom code you're prepared to maintain.
- How long will this version live? Probably a few years. Most SaaS marketing sites get rebuilt that often anyway. Optimize for easy change now, not imagined scale later.
For what to put on the site, see SaaS website design: what actually matters.
Frequently asked questions
Is Webflow or Framer better for a SaaS marketing site?
Webflow is usually the better fit for content-heavy sites with a large CMS, many templates, and a marketing team that needs fine-grained control. Framer is usually faster for small, design-led sites that change often. Both are good; the right choice depends on who will maintain the site and how much content it has.
When should a SaaS company build its marketing site in code instead of a no-code tool?
When the team has someone comfortable with HTML, CSS, and Git; when the site needs custom integrations, interactive demos, or programmatic content; when the site should share conventions with the product; or when avoiding vendor lock-in and per-seat or per-site costs matters.
Can marketers edit a code-based website?
Yes, with the right setup. A Git-based CMS such as Decap can give non-technical editors a friendly interface for content like blog posts and changelogs, while everything still lives as Markdown files in the repository.
What is the best static site generator for a marketing website?
Eleventy is a strong choice for marketing sites because it outputs plain HTML, CSS, and JavaScript, has very few opinions, and keeps dependencies low. Astro is another popular option. The best one is the one your team can read and maintain.
Is it hard to migrate off Webflow or Framer later?
Migrating is always work, because templates, CMS structure, and interactions are tied to the tool. Exports help, but expect to rebuild templates. Since most SaaS marketing sites are rebuilt every few years anyway, plan for that rather than trying to avoid it.