I rebuilt my own website in a weekend, without a developer

This site used to run on one of the AI site builders, the kind where you describe a page and it appears. It did the job for a year. Last weekend I replaced it with ordinary web pages sitting in a folder I own, and I did it myself, which is not a sentence I expected to write when I started this business.

What the builder was good for

I want to be fair to it, because I still use it. When I need to show a client what their tool could look like, I can have a working demo in an afternoon. The demos linked from the case studies on this site still live there, and they will stay there. For a prototype, for a proof of concept, for anything whose job is to be looked at and then thrown away, it is the right tool and I would recommend it without hesitation.

Where it stopped being right

Two things changed. The first is practical. I wanted a blog, and I wanted every post to be a real page that a search engine could read on its own, not something assembled inside the browser after the page loads. Builders are not great at that, because it is not what they are for.

The second is quieter. I spend my working week telling businesses they should own the software their operations run on, the code, the data, the accounts it sits in. It felt odd to be renting my own front door. Not wrong, exactly. Just odd, in the way that is worth listening to.

So the new site is a set of plain files. No builder, no account that can be closed, no monthly plan holding the pages. If I stopped paying for everything tomorrow, the site would still be there, and I could move it anywhere in an hour.

What I got wrong on the way

Honesty section. The logo broke the minute the domain moved, because every page was still fetching it from the old builder's address and I had not noticed. The blog addresses ended with a slash, the new host wanted them without, and every link on the site was quietly bouncing twice before it landed. Neither would have cost a visitor anything they would notice. I found both by checking rather than assuming, which is the only reason I am allowed to tell clients to do the same.

The rule I would give a client

Use the builder for anything you need to see. Own the thing you need to keep. The mistake is staying on a builder past the point where the thing it built has become the business, and that point arrives earlier than the pricing page suggests.

And do it yourself at least once. I am not a developer. I have said so on this blog more times than I would like. But moving my own site taught me more about what my clients are actually buying than a year of selling it did. There is a difference between knowing that ownership matters and having felt, at eleven on a Saturday night, exactly what you do not own.

Own what you keep. Rent what you throw away.