The Honest Answer Most Agencies Won't Give You

Most web agencies push you toward the tool they are most comfortable building in, or the one with the highest margin, rather than the one that best fits your situation. We are going to do the opposite. We have built over 250 websites across both Webflow and custom code stacks (primarily Next.js with various CMS options), and we have a clear picture of when each is the right choice.

The short version: Webflow wins for the vast majority of marketing websites, professional service sites, portfolios, and content-driven businesses. Custom code wins for web applications, complex integrations, high-performance SaaS products, and anything that requires backend logic. Choosing the wrong tool for either category creates real problems — either an over-engineered solution with unnecessary maintenance overhead, or an under-powered one that constrains your business within 18 months.

What Webflow Actually Is

Webflow is a visual web development platform. You design in a Figma-like interface, and Webflow generates clean, semantic HTML, CSS, and JavaScript. The output is a real website — not a template with limited customisation, but production-quality code that you can inspect, and in many cases export.

What makes Webflow genuinely different from other visual builders like Squarespace or Wix is the ceiling of what you can build. A skilled Webflow developer can create designs and interactions that are indistinguishable from custom-coded sites — scroll animations, complex hover states, dynamic CMS content, custom-styled components. The constraint is not design flexibility. The constraint is backend capability.

Webflow has no server-side code. No custom database logic. No user authentication built in. No real-time data. It is a frontend tool with a simple built-in CMS, and within that scope, it is exceptional.

What Custom Code Actually Means

When we say custom code, we typically mean Next.js (a React framework) on the frontend, connected to either a headless CMS (Contentful, Sanity, or Notion as a data source), a database (PostgreSQL, PlanetScale), and deployed on Vercel or similar infrastructure. This stack has essentially no ceiling — whatever you can imagine building on the web, this stack can build it.

The cost of that flexibility is complexity. Custom code requires a developer to update it. It requires monitoring, dependency updates, security patches, and careful management of the deployment pipeline. When something breaks — and in sufficiently complex codebases, things break — it requires someone with the technical knowledge to diagnose and fix it. For a marketing website that needs a blog and a contact form, this overhead is unnecessary and expensive.

The Decision Framework

These are the questions that reliably lead to the right answer. Work through them in order — the first "yes" in either column determines your answer.

Choose Webflow if:

  • Your site is primarily a marketing or content website — home, services, about, blog, contact
  • Your marketing team needs to update content without involving a developer
  • Design quality and visual distinctiveness matter significantly to your brand
  • You want predictable hosting costs and minimal maintenance overhead
  • Your timeline is weeks rather than months
  • You are a professional services business, agency, healthcare provider, SaaS marketing site, or content publisher
  • You have been burned by WordPress maintenance and want out

Choose custom code if:

  • You need user accounts, login, or personalised dashboards
  • Your site is a web application — something users do things in, not just read
  • You need real-time data — live prices, inventory counts, dynamic user-specific content
  • You are building complex multi-step forms, calculators, or interactive tools that go beyond what JavaScript embeds can handle
  • You need custom backend API integrations that go beyond Webflow's native integrations or Zapier
  • You are a technical team with developers in-house who will own the codebase
  • Your traffic is very high and you need granular control over caching, CDN behaviour, and infrastructure

Performance: The Honest Comparison

Performance is often cited as the reason to choose custom code over Webflow. This is true in theory and largely irrelevant in practice for most marketing websites.

A well-built Next.js site on Vercel can achieve perfect 100/100 PageSpeed scores. A well-built Webflow site typically achieves 90–98. For the user experience of someone visiting a marketing website, the difference between a 1.1-second load time and a 1.4-second load time is imperceptible. The ranking difference in Google is marginal at scores above 90.

The performance argument for custom code only becomes relevant in specific scenarios: extremely high-traffic sites where every millisecond of infrastructure cost matters, sites with complex data fetching requirements, or sites needing highly customised caching strategies. For the vast majority of business websites, a 95/100 Webflow site outperforms a 62/100 WordPress site by a margin that genuinely affects business outcomes — and that comparison is far more common in practice than Webflow vs a meticulously optimised Next.js build.

Team Ownership: Often the Deciding Factor

The question we ask every client before recommending a stack: "After the site launches, who needs to update it and what do they need to be able to change?"

If the answer is "our marketing team needs to publish blog posts, update the team page, and add case studies," Webflow is the right answer. The Webflow Editor is designed for exactly this — non-developers can manage CMS content, swap images, update text, and publish pages through a visual interface with no code exposure. The developer who built the site can lock down which parts are editable and which are structural, giving the marketing team genuine autonomy within guardrails.

If the answer is "our engineering team will own this and we want full control over the codebase, deployment pipeline, and infrastructure," custom code is the right answer. A technical team that finds the Webflow Editor constraining will be far better served by a codebase they can edit directly and deploy through a CI/CD pipeline they control.

The mismatch — a marketing team trying to own a Next.js codebase, or a technical team constrained by Webflow's visual editor — creates friction that compounds over time. Getting this question right upfront saves significant frustration later.

Timeline and Cost

A Webflow build is typically 30–50% faster than an equivalent custom-coded build. There are two reasons: Webflow's visual editor accelerates frontend development significantly compared to writing HTML and CSS by hand, and Webflow's hosting, CMS, and deployment infrastructure is pre-built, eliminating the setup time required for a custom stack.

For a 10-page marketing site, a Webflow build takes 14–20 days. An equivalent custom Next.js build takes 25–35 days. The difference is not developer productivity — it is the overhead of custom infrastructure setup, build pipelines, and the additional testing required for a custom codebase.

On cost, Webflow's ongoing hosting is $39/month. A comparable Vercel deployment is $20/month, but the maintenance cost differential — developer time for updates on a custom site versus near-zero maintenance on Webflow — makes Webflow significantly cheaper over a 2–3 year horizon for most businesses. We covered this in detail in our Webflow ROI analysis.

The Hybrid Approach

An increasingly common pattern we use for clients who need the best of both: a Webflow marketing site combined with a separate custom application for the product or logged-in experience. The marketing site (home, pricing, blog, documentation) lives on Webflow at webflow.company.com and benefits from Webflow's speed, ease of content management, and design flexibility. The application (dashboard, user accounts, product features) lives on a Next.js app at app.company.com with its own infrastructure.

This pattern is used by a significant number of SaaS companies. It is often the most practical answer for funded startups: ship the marketing site on Webflow in two weeks so you can start generating leads, build the product on custom code in parallel. Neither side constrains the other.

The Two Most Common Mistakes

We see two mistakes repeatedly. The first is choosing custom code for a site that does not need it, usually because the developer recommended what they know best or the business wanted to feel like they had a "real" technical setup. The result is a site that costs 3x more to build, takes twice as long, and requires ongoing developer involvement for tasks that would take three minutes in Webflow. The business pays for complexity it does not need and does not benefit from.

The second is choosing Webflow for a project that genuinely needs backend capabilities, usually because the client wanted a faster timeline or lower initial cost. The result is workarounds and integrations that become increasingly fragile, or a rebuild 12 months later when the limitations become constraints. Webflow cannot become a web application with enough Zapier workflows strapped to it. If you need backend logic, build it on a stack that supports it from the start.

Our Recommendation

The rule of thumb we use internally: if you are building something people read and enquire through, use Webflow. If you are building something people log in to and do things inside, use custom code.

If you are not sure which category your project falls into, that uncertainty is itself useful information. Projects that are genuinely ambiguous usually have a marketing-facing component and an application component — and the hybrid approach described above is often the right answer.

If you want to talk through your specific situation, book a free 30-minute call. We will ask you the questions in this framework, give you a direct recommendation, and explain exactly why — not try to sell you the most expensive option.