How much a website really costs over 3 years: builder vs CMS.

Over the first three years a website builder is cheaper than a CMS in almost every scenario — for a simple brochure site, several times cheaper. A CMS doesn't pay off because the builder subscription "adds up". It pays off because at some point the builder stops doing what the business needs, and the site has to be built a second time. That second time is the most expensive line in the whole bill.

This post breaks both costs into their parts, runs four scenarios over three years, and shows how to do the same calculation for your own site. The figures are assumptions as of October 2026 — plug in your own. If you first want to know how a builder and a CMS differ beyond price, start with website builder vs CMS: which to choose.

What a builder actually costs.

A builder looks like a single line item — the subscription — but in practice it's five:

• The plan. The advertised price assumes you pay a year up front; monthly billing is 30–55% higher. The cheapest plan is usually not enough for a business: Wix Light can't take payments, and Webflow Basic has no CMS, so no blog and no list of case studies.
• Apps and add-ons. A quote form, booking calendar, pop-up, advanced SEO, a second language — on Wix these are separate apps at somewhere between a few and several dozen dollars a month each; on Webflow, multilingual support is a paid add-on per language. A typical business site has two or three of them after a year.
• The domain. Usually free for the first year on an annual plan, then $15–30 a year. Small, but recurring.
• Price increases. Builder providers raise prices every year or two and migrate old plans onto new ones. Over three years it's worth assuming a 10–15% increase.
• Your time. A builder is cheap because you run the site yourself. If you put a value on your time, every hour in the editor is a cost — and it grows with the site.

What's missing from a builder's bill: the build, hosting, updates, and backups. They're included in the subscription and out of your control — which is an advantage, as long as they work the way you want.

What a CMS actually costs.

The other way round: a large cost up front, then a few smaller, fixed ones.

• The build. Design, development, content migration, testing. With me, a business site on Drupal starts at $1,300; a site with a blog, two languages, and an integration is usually $2,900–5,100; a larger platform with a client area starts at $7,100. It's the only big line item, and you pay it once.
• Hosting. Shared hosting is enough for a brochure site ($85–170 a year); a site with real traffic and integrations needs a VPS or managed hosting ($230–710 a year).
• Technical maintenance. Security updates, backups, monitoring, small fixes. $45–85 a month for a simple site, more for one with integrations. You can do it yourself, but then the cost is your time and your risk.
• Major upgrades. Drupal releases a new major version every two to three years; moving to it takes from a few to a dozen or so hours of work, more for a large site. Over three years, plan for one.
• Development. New features after launch — priced separately, but possible. That's the difference from a builder, where development ends where the app marketplace ends.

What goes into Drupal maintenance and what it costs is covered in detail in how much Drupal maintenance costs.

The assumptions.

Every scenario below uses the same set of assumptions. Builder prices are annual-plan list prices in US dollars as of October 2026. CMS figures come from my price list, which is set in Polish złoty and converted here at about 3.5 PLN to the dollar, then rounded.

I don't include the owner's time in the figures — it's there in both options, more of it with a builder. If you want to account for it, add your hourly rate times the hours you spend on the site each month.

Scenario A: a brochure site.

A service business, 5–8 pages, a contact form, a gallery, one language. Content changes a few times a year.

The result is clear-cut: for a brochure site a builder costs three to six times less, and there's no reason to choose a CMS. The only argument for a CMS here is being sure the site will be more than a brochure a year from now — in other words, that it's really scenario B.

Scenario B: a site with a blog and two languages.

A manufacturer or B2B company: a blog, a catalog of projects or products (a few dozen entries), Polish and English versions, a quote form with a file attachment. New content every week.

The builder is still about four times cheaper in cash. For the difference of roughly $6,300 over three years, a CMS gives you: one set of content in two languages instead of two sites, a catalog with filtering and content types, ownership of the site, and no ceiling on what gets added in year four.

This is the scenario where the decision is genuinely open. If the features in the "what's missing" column don't bother you — go with a builder. If a second language as a copy of the site means double the work on every change, and the catalog is going to grow to hundreds of entries — that price difference is the cost of avoiding scenario D.

Scenario C: a platform with integrations and a client area.

A wholesaler, a manufacturer with a distributor network, a training company: a catalog fed from an inventory system or ERP, a logged-in client area with price lists and documents, forms that feed into a CRM, several hundred pages.

Here the comparison stops being symmetrical, because a builder can't do this on its own. Wix lets you add logic in Velo (its own development platform), but that takes a developer who specializes in Wix, and the client area and integrations work within the platform's limits. Webflow retired its built-in memberships in January 2026 — a client area needs an external service on a separate subscription. Squarespace has no such route at all.

The CMS costs roughly $6,500 more over three years here — but the comparison is skewed in the builders' favor, because their options are assemblies of several services that cover the scope only partly, and on someone else's terms. When the site is a sales tool rather than a brochure, the question isn't "which is cheaper" but "what will still be working in three years, and who will be able to develop it".

Scenario D: a builder, then a rebuild a year later.

The business from scenario B starts on Wix because "it'll do for now". A year later a second language is needed, the catalog keeps growing, the quote form doesn't work the way it should — and the site moves to Drupal.

In cash it comes out almost even — a year on the builder costs roughly what a year of CMS maintenance does, and in this option that year of maintenance drops out. That's why I don't say scenario D is "the most expensive in dollars". It's the most expensive in what the table doesn't show:

• a year without features the business needed — the second language as a copy of the site, a hand-maintained catalog, enquiries handled by email;
• doing the content, structure, and design twice — decisions made while building on Wix have to be made again;
• the risk of losing Google rankings during migration, which doesn't exist if you start on a CMS;
• the owner's time: two builds mean reviewing, approving, and correcting everything twice.

If you expect to be in scenario B a year from now, start there today.

If you genuinely don't know — a year on a builder is a cheap trial, provided you keep the original texts and images outside it from day one.

Hidden costs on both sides.

None of the calculations above is complete. These are the items that most often come as a surprise:

With a builder

• The plan that "will do" stops doing at the first real need: payments, an attachment in a form, a second collaborator — and jumping to the next tier adds 40–100% to the subscription.
• Transaction fees on the cheaper commerce plans (Squarespace Basic 2%, Webflow Ecommerce Standard 2%).
• Images and texts exist only inside the builder — recovering them during a migration is work that wasn't on any price list.
• The provider changes its pricing or removes a feature (Webflow shut down memberships in 2026) — and you can't say no.

With a CMS

• Hosting "for $30 a year" — too slow and without backups; the difference between that and decent hosting is $85–200 a year, better spent from the start.
• No technical maintenance: you save $45–85 a month until the first breach or an update that breaks the site; then the repair costs more than a year of maintenance.
• Development after launch: every new feature needs a quote. Same with a builder, except there the answer is often "it can't be done".
• Changing developers: possible, but a new developer needs time to get to know the project — good documentation at launch brings that cost down.

How to run the numbers for your own site.

The same calculation for your own site takes about fifteen minutes. You need a spreadsheet with five rows:

1. Write down what the site should do in two years, not today: languages, blog, catalog, store, forms, integrations, client area. This list decides both the builder plan and the scope of the CMS build.
2. Pick the builder plan that can handle it — not the cheapest one, but the one with the features from step 1. Add apps and add-ons. Multiply by 36 months and add 10% for price increases.
3. Get a quote for a CMS build of the same scope. Add hosting and maintenance times 36 months, plus one major upgrade.
4. Add your time to both sides: hours per month on the site, times your rate, times 36. There will be more of them with a builder.
5. Check the "what's missing" column. If anything from step 1 shows up there for the builder, also work out scenario D: a year on the builder, plus a CMS build, plus migration.

The result that comes up most often: for a brochure site, a builder, no question; for a site that grows, a difference of roughly $6,000 over three years that has to be weighed against the list from step 1; for a platform with integrations, a CMS, because the alternatives are assemblies of several services. If a CMS is already decided and the open question is which one, I compare them in how to choose a CMS for your business.

Frequently asked questions.

How much does a website on a builder cost over 3 years? A simple brochure site comes to roughly $620–690; a site with a blog, two languages, and add-ons roughly $2,100–2,300 — on annual plans, including the domain and price increases. Paying monthly raises these figures by 30–55%.

How much does a website on a CMS cost over 3 years? A brochure site $2,100–3,700, depending on whether you buy technical maintenance or do it yourself; a site with a blog and two languages about $8,600; a platform with integrations from about $17,000. Most of that is the one-time build.

When does a CMS become cheaper than a builder? In pure cash over three years — almost never. A CMS is cheaper when the alternative is rebuilding the builder site after a year or two, or when the builder needs several extra services bolted on to do what a CMS includes in the build.

Can I skip paid maintenance and update the site myself? Yes, and many businesses with a brochure site do. You then need to install security updates regularly and keep a backup that someone has actually tested. If you don't have time for that, maintenance costs less than a single breach — why, I explain in the post on Drupal updates.

Are builder prices the same in every country? No. Providers bill in local currencies at roughly similar levels, but regional price lists differ and change — before deciding, check the current price at checkout, not on the marketing page.

Summary.

A builder wins the three-year cash comparison — decisively for a brochure site, clearly for a site that grows. What a CMS buys with that difference is ownership, a scope the builder doesn't have, and no second build. That's why "which is cheaper" is the wrong question. The right one is: "what will it cost to do what the site needs to do in two years — on a builder, on a CMS, and in the option with a rebuild?"

If you'd like me to run these numbers for your site with real figures, get in touch — in a free consultation we'll go through the five steps from this post.

Pricing sources

• Wix Premium plans — Light $17, Core $29, Business $39 per month on an annual plan; updated October 19, 2026
• Squarespace pricing — Basic $16, Core $23 per month on an annual plan
• Webflow pricing 2026 — Basic $15, Premium $25 per month; Localization $9 per language; Core workspace $19; memberships retired in January 2026

Build, hosting, and maintenance figures are my price list and the assumptions described in "The assumptions" section.