The web builder cost per client site in 2026: what freelancers actually pay

Every freelancer quotes a build fee. Almost none of them quote the web builder cost per client site — the bill that arrives every month after the invoice is paid. That second number is the one that decides whether a client site is a business or a hobby, and it’s the number nobody puts in a proposal.

Independent reviews keep flagging the same problem: Webflow‘s pricing clarity scores 2 out of 5, because site plans, ecommerce plans and workspace plans carry different features. So we did the arithmetic across the web builders in our own catalogue, and the gap between the cheapest and the most expensive way to keep one client site live is wider than most people assume.

The web builder cost per client site, and why it matters

We compared the builders in our catalogue that a freelancer could realistically put a client site on: not the free tiers, not the enterprise quotes, the plans you’d actually bill against.

The result is uncomfortable. The spread runs from a flat per-site charge to a workspace plan plus a site plan for anything with a CMS or a store, before hosting, domains, or your own time. The tool you pick in the first week of a project sets that number for as long as the client stays.

That’s the real cost of a builder. Not the build. The keeping.

The three ways freelancers get billed

Builders don’t price the same way, and the difference matters more than the sticker.

  • Per-site plans. You pay for each site you keep live. Predictable, and it scales linearly with your client list.
  • Per-seat workspace plans. You pay for the person, and sites sit inside the workspace. Cheap at five sites, painful at thirty.
  • Hybrid. A workspace plan plus a site plan for anything with a CMS or a store. This is where quotes go wrong, because the second charge only appears once the client asks for a blog.

Webflow sits in the hybrid camp, and reviewers have flagged exactly this. Memeburn’s Webflow review scores pricing clarity 2 out of 5, noting that site plans, ecommerce plans and workspace plans carry different features, which makes the total cost hard to work out. Tech.co’s WordPress vs Webflow comparison makes the same point from the other direction: WordPress offers better value on the free tier partly because Webflow users often end up buying both a site plan and a workspace plan.

If you’ve ever quoted a client from the site-plan page and then discovered the workspace charge, you already know the shape of this problem.

The comparison, priced per client site

Here’s how the main options in our catalogue stack up for a freelancer keeping a client site live. This is a billing-model comparison, not a price list — check each vendor’s current pricing before you quote.

BuilderBilling modelBest forThe catch
WebflowWorkspace plan plus site planCustom layouts, CMS collections, design-led client sitesTwo charges per site; pricing clarity is the weakest score in independent reviews
WordPressHosting plus optional pluginsBlogs, publishers, content-heavy client sitesYou own maintenance, updates and security yourself
CarrdPer-site, flatOne-page sites, portfolios, landing pagesEmbedding control sits behind Pro Plus or higher
DorikPer-site with template libraryPersonal sites, blogs, quick client buildsTemplate-led, so custom work hits the ceiling sooner

The pattern is clear. Flat per-site pricing is the freelancer’s friend; hybrid workspace-plus-site pricing is the freelancer’s tax.

What Carrd’s changelog tells you about the cheap end

Carrd‘s own changelog is a useful read for anyone weighing the low-cost route. The September 28, 2026 entry adds new integrations including MyGameList, Primal, Trakt and XMPP. Earlier in the year, the August 23 entry added a framing option under Publish → Settings that controls when and where a site can be embedded in an iframe, and notes it requires Pro Plus or higher.

That last detail is the honest small print of cheap builders. The base plan is genuinely cheap. The control you need for a client who wants their site embedded in a partner page sits one tier up.

Dorik takes the opposite approach, leaning on templates. Its blog template page promises built-in SEO tooling, automatic sitemaps, schema markup, newsletter forms that connect to Mailchimp and ConvertKit, and mobile-first responsive layouts. Its personal-website guide frames the whole decision around picking a builder for ease of use, design flexibility, mobile responsiveness and content features.

Both are reasonable. Neither is free once a client asks for something specific.

The decision rule that actually holds

Stop comparing build features. Compare the keeping cost against what the client pays you to keep it.

  • Client pays a retainer? A hybrid builder is fine. The workspace charge is a line item you can pass through.
  • Client pays once and disappears? Put them on flat per-site pricing. Every monthly charge after handover comes out of your pocket.
  • Client wants a blog or store later? Price the CMS tier now, in the proposal, before they ask. That’s the upgrade that breaks budgets.

And check the embed and framing rules before you promise a client their site will appear inside someone else’s page. On at least one builder, that’s a paid tier.

What to do this week

Open your client list and write the platform fee next to each name. If the total is more than one project’s profit, you’re subsidising your clients’ hosting.

Then pick one builder for new work and standardise on it. The freelancers who get hurt aren’t the ones on the expensive platform. They’re the ones on four platforms, paying four sets of charges, and remembering none of them at tax time.

Reviews rate Webflow strongest for custom layout control and CMS work. WordPress offers better free-tier value and a lower price point for content-heavy sites, provided you’re willing to own the maintenance. Carrd and Dorik cover the simple end honestly, as long as you read which tier unlocks the feature you just promised.

The build is the fun part. The bill is the part that decides whether you keep the client.

Sources

Get the next one by email

Occasional, honest write-ups on design tools — including where they fall short.

No spam, unsubscribe in one click. Privacy.


This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.