Owning Your Digital Codebase vs. SaaS Site Builders: Lock-In Costs

The builder was the right call

Most small businesses that have a website built it on a hosted builder: Webflow, Squarespace, Wix, Shopify. Those are SaaS site builders, and for the first two or three years of a small business that is usually the correct decision. You can publish on a Tuesday without calling anybody, the monthly cost is small, and you never had to think about a server.

This article is not an argument against that. It is about the moment it stops being the right decision, and about why that moment is much less painful if you can see it coming while the site is still small.

The question is not “builder or code”. It is who decides what happens next: the platform, or you.

Four things change as you grow

1. You need a page the builder cannot give you

Every builder has a shape. A grid of sections, a list of collection items, a set of templates that snap together. That shape is why they are fast to launch and easy to use.

The shape is also the limit. A comparison table with two hundred rows, a jobs list, a quote calculator, a page in three languages, a page that changes completely on mobile: these do not fit the shape, and the workaround is always a compromise. You either accept a worse version of the page, or you embed something odd, or you leave.

2. You want to change one thing without breaking another

On a builder, every change is a click by a person with a login. There is no record of what the page looked like last Tuesday. If somebody changes a setting and the navigation stops working on phones, the way back is to remember what it used to be.

That is a small problem until the day it is not.

3. The price and the limits are not yours to set

Publishers change their plans. They change the number of pages, the number of content items and the number of seats a plan includes, and they tell existing customers afterwards. The published limits are in the platform’s own documentation, and they are worth reading before you rely on them: Webflow, for example, lists the price of every site plan next to its page, bandwidth and form-submission limits on its own pricing page, and the number that matters to you is the one attached to the plan you are actually on.

You can check this today. It costs five minutes, and it is the cheapest check available to a small business.

4. The code is not yours to fix

A builder has to support every possible arrangement a customer might drag into place, so the markup it produces is usually heavier than the page actually needs. You cannot remove the weight, because you did not write it and you cannot reach it. When a page is slow, your options are to ask the publisher, or to accept it.

What owning it actually means

Owning a website means owning the digital codebase behind it: the files that make up the pages, your copy, the styles and the images, in formats any web server can serve, kept in a repository that records what changed and when.

┌──────────────────────────────────────────────────────────────────────────────┐
│  WHAT YOU OWN                        │ WHAT YOU RENT                         │
├──────────────────────────────────────┼───────────────────────────────────────┤
│  The pages, as files                 │  Pages inside someone else's editor   │
│  Your copy, as text you can edit     │  Copy locked in a form                │
│  The styles                          │   Styles you can override, not change │
│  A history of every change made      │  No history of previous states        │
│  Any host, any developer             │   The platform, its price, its limits │
└──────────────────────────────────────┴───────────────────────────────────────┘

None of this is exotic. It is a folder of files, a repository that records what changed, and standard web files that any server can serve.

The four costs of renting

There is one word for all of this, and it is lock-in: the platform gets to decide what leaving costs, and you find out how much it costs only once you want to leave.

The exit cost. When you outgrow the builder, somebody has to rebuild the site. That is a project with a price, and the price is not small because the work is the same work, whoever does it. A rebuild of a small business site sits in the same range as a new one.

The dependency. If the relationship with the platform, or with the agency that built it, goes wrong, you do not have a site you can hand to somebody else. You have a login.

The performance ceiling. The page you have is the page the builder is willing to output. You cannot do better than that without leaving.

The ownership question. The domain is separate from the site, and it is the part customers actually arrive through. Registrars hold it on your behalf and you keep control by keeping the renewal in your own name and your own account. ICANN’s registrant FAQs explain the renewal and expiry process, including what happens if a renewal is missed.

The arithmetic, with your own numbers

Here is a model you can fill in yourself. Take a builder plan at $50 a month — a round figure to model with rather than any publisher’s list price, since published prices range widely: Webflow’s own pricing page lists a free Starter plan, a Basic plan at $15 a month billed yearly and a Premium plan at $25, each with its own limits. Over three years, $50 a month is about $1,800 of subscription.

In the same model, hosting a small static site at a few dollars a month comes to around $180 over three years. The difference is not the point, and we are not going to pretend it is. The point is what each of those numbers buys.

The line that matters is the last one. If you own the files, rebuilding is not a project, because there is nothing to rebuild.

When to stay on a builder

Stay if the site is small, the content changes rarely, and the platform does everything you need. Plenty of small businesses should never leave a builder, and paying a developer to rebuild a five-page site that works perfectly is a waste of money.

Move when one of these is true: you need a page the builder cannot express, the site has grown past what a plan gives you, you want to change things safely, or the page is slower than you need and you cannot fix it yourself.

What to ask whoever builds it

Five questions, and they are worth asking whoever you hire next, whoever you have now, or yourself:

1. Can I have the site as files I can read and edit, with my copy in plain text?
2. Can I host it somewhere else, and how long would that take?
3. Can I change the prices and the words myself, without a developer?
4. Is the domain registered in my name or my business’s name, and do I have the account details?
5. If our relationship ended tomorrow, what would you hand over, and how long would it take to take it in?

If the answer to the first one is no, everything else on the list is theoretical.

What it costs to own

Owning your code is not free. It costs a little more to begin with, because somebody has to set up the structure properly, and it costs a little ongoing attention, because files need a new home when things change. What it buys is that the last decision about your website stays with you.

A business that has been running for five years has already paid for its website several times over. Owning the files is what stops it paying again for the same thing.

Want to see what a rebuild looks like before deciding? Model your project with the estimator, or read whether to improve your website or start again.