What Comes With You -- Field Notes -- Kre8ive Studio

In Standing Next to the Shaft, the website showed up as a throwaway example — the half-finished thing that's sat for two years, one of the hats you'll finally have time for once the motor takes the floor. So you'll go build it. This is about not getting trapped the moment you do.

The trap

When a shop finally builds its site, it rents one. Wix, Squarespace, GoDaddy, Weebly — pick a template, drag some boxes, pay monthly. It works, it looks fine, and you stop thinking about it.

Here's what you didn't notice: you don't own the thing you built. You own a login. Your pages live inside their editor, in their format, on their servers. The day you want to move — better pricing, a feature they don't have, an agency that needs real access — you find out the site doesn't come with you. You rebuild from scratch. That's not a website. That's a lease with no buyout.

The site is not the asset

The site you look at — the pages, the layout, the colors — is a render. It's the output. The asset is what it's rendered from: your content, your structure, your domain, the code. Rent-a-site platforms blur those together on purpose. You think you're buying a website; you're buying a render you can't take with you, with the source held on the other side of their login.

Own four things and you're free.

Your domain. Registered in an account that's yours — not your web guy's, not the platform's. This is the one people lose, and it's the worst one to lose.

Your content. The actual words, images, and structure, in a plain format you hold — files, a doc, a database — not trapped inside a page builder.

Your code. If someone builds you a custom site, you get the code. In a repo. Yours.

Your data. Form submissions, signups, customer info — flowing somewhere you control, not pooling inside a vendor you'd have to abandon.

The host — where the render actually gets served — is the one part that's supposed to be disposable. Own the source and the host becomes a thirty-minute swap instead of a six-week rebuild.

What changed, and why now and not last year

Owning your site used to come with a real cost. The choice was: rent a locked platform and get capability with no ownership, or own it and either pay an agency real money every time you wanted to move a comma, or learn to hand-code the thing yourself. Ownership meant friction. So most shops rented. Rationally.

That trade is gone. As of about now — not last year — AI-assisted build plus cheap modern infrastructure means owning the source is the low-friction path, not the high-friction one. You can stand up a site you fully own, change it by describing the change in plain English, and host it for next to nothing. The thing that used to cost you capability now buys you capability. Owning it isn't the expensive option anymore. It's the better one on every axis at once — and that part is new.

What it actually buys you

I moved this newsletter off a rented platform onto infrastructure I own. The headline isn't that I escaped a vendor. It's what I can do now that I couldn't before — and mostly couldn't have done even a year ago.

The content lives in my own database as the source of truth. The site is just a render of it. So I'm not editing pages — I'm editing the source, and the site rebuilds itself. I can change the entire look without touching a word of the content. I can push the same content to the web, to email, to a PDF, anywhere, because it lives in one owned place instead of being trapped as pages inside someone's editor. None of that is exotic. It's just what owning the source gets you — and the cost of getting there dropped through the floor. And the newsletter is the small version of it. The same owned-source setup runs the rest of the business too.

It doesn't stop at the website

Here's the part that matters more than your website: every SaaS tool you pay for is running the same play. Your CRM. Your accounting software. Your quoting tool. Your email platform. Your inventory system. Each one holds a slice of your business behind a login and hands you back a render of it.

You don't feel it, because the tools work and the data's right there on the screen. But "our customers are in HubSpot" is the same mistake as "our website is on Squarespace." Your customers aren't in HubSpot. Your customers are your customers. HubSpot holds a copy and shows it back to you — and the day you leave, you find out how much of "your" customer relationship was actually structure HubSpot owned, not you. The export is a CSV that drops half of what made it useful. The workflows you built were theirs. You don't migrate. You start over.

And it's worse than the website, two ways. One: that's where the business actually lives — customers, orders, quotes, history, money — so the lock-in costs you the thing the business is made of, not a weekend of rebuilding. Two: it's scattered. Your source isn't held by one vendor, it's smeared across a dozen, each showing you their slice, none of them the whole picture, none of them yours. Nobody holds what's actually true about your business in one place you own. The vendors hold pieces of it, separately, and rent the pieces back to you.

The fix is the same fix, one size up. Hold your own source of truth — one place you own, that the tools render from and write back to — and let each SaaS tool be a swappable surface on top of it instead of the place your business lives. That used to be enterprise-integration money: six figures and a consultant. It isn't anymore. That's the whole reason this is worth telling a 20-person shop — the move that was reserved for companies with an IT department is now in reach for you.

Start this week

You don't have to migrate anything today. You have to stop digging the hole. Before you build, or pay anyone to:

Find your domain. Log into wherever it's registered. If you can't, or it sits in someone else's account, fix that first. Everything else is rearranging furniture in a house you don't own.
Ask the ownership question out loud. To any platform or person building your site: "If I leave, what do I walk away with?" If the answer is "a login," it's a rental. If it's "your domain, your content, your code," it's yours.
Keep your content somewhere you hold. Even a plain doc. The words and images should exist outside the site, in a format you own, before they ever go into one.
Treat the host as disposable and the source as sacred. Spend your worry on owning the source. Let the host be the cheap, swappable part it's supposed to be.
Run the same question up the stack. Once the website's yours, point the ownership question at the tools that hold the real money — CRM, accounting, quoting. You don't have to move them this week. You have to know which ones you don't actually own.

Run the question across your whole stack, one tool at a time: if you walked away tomorrow, what comes with you? Every tool where the honest answer is "a username and a password" is a tool that owns a piece of your business you think you own. Start with the website — it's the cheapest one to get right. Then keep looking up. You don't have to rent your own business back from anybody anymore.