What to Ask Before Someone Builds Your Website

Most people who hire someone to build their website assume they own it. The domain, the hosting, the files, the whole thing. In practice, that’s often not what happens.

This is not a rare edge case. It’s one of the most common situations I run into when talking to small business owners who have had a site built before.

The Subscription Trap

Wix and Squarespace are not website builders. They are website rentals.

The site works as long as the monthly payment goes through. Stop paying, the site disappears. The files are not yours to take. There is no export that produces a real, self-contained website. The platform owns the infrastructure, and the infrastructure is the product.

For a solo teacher with one page and no technical interest, that trade-off might make sense. Quick to set up, nothing to manage. But for any business that depends on its online presence, building on a subscription platform means building on borrowed ground. The moment the subscription stops making sense, the asset disappears with it.

The Agency That Holds the Keys

Subscription platforms are at least transparent about the model. The agency situation is less obvious.

A business hires an agency to build a WordPress site. The agency registers the domain in their own account. They host the site on their server. Years pass. The relationship ends, or the agency closes, or the owner just wants to work with someone new.

That’s when they find out the domain is not theirs to take. The hosting account belongs to the agency. The client has to negotiate to recover access to a site they paid for.

I’ve seen this with music schools in the Nice area. A director who had a site built three years ago and had no idea which company was holding the hosting account. They had the invoices. They did not have the login. Two different things.

The WordPress Plugin Problem

WordPress is different from a hosted builder, but it has its own version of the dependency.

A WordPress site built on a stack of plugins works fine until one plugin stops being maintained, conflicts with an update, or needs a configuration that only the original developer understands. The site breaks. The owner calls the developer. If that developer is unreachable, the owner is left with a broken site and no clean path forward.

The dependency is not visible at handover. It becomes visible when something breaks.

When the Freelancer Goes Quiet

Not every dependency is a platform or an agency. Some of it is a person.

A freelancer builds the site. They set up the hosting, create the admin account, and handle the deployment. The owner gets a nice-looking website and a handshake. No credentials. No documentation. No clear record of where anything lives.

Six months later the owner needs a change. The freelancer takes a week to reply, then two weeks, then nothing. The owner has no admin access, no hosting login, and no idea which registrar holds the domain. The site is live, but effectively out of reach.

The website is held by a person instead of a platform, but the result is the same: someone else has control over an asset the owner paid for.

What the Real Cost Is

Nobody actually wants a website. What they want is for parents to find their school before a competitor does. They want enrollment inquiries to come through without someone having to dig for a buried contact form. They want to stop waiting on someone else every time a class schedule changes.

The real cost of a bad ownership structure is not technical. It’s operational. Time spent chasing a developer for a simple text update. Inquiries lost because the contact form has been broken for three weeks and nobody noticed. A director who cannot make a simple change to their own site without going through a middleman.

That’s what poor ownership looks like in practice.

What Actual Ownership Looks Like

When I deliver a site through Nextbyrd, the last step is a handover. The domain is registered to the client’s account. The hosting is deployed to the client’s Vercel account. The environment is theirs. If they never contact me again, the site still runs. Any developer can pick it up.

The code is not locked behind a proprietary platform. No subscription needs to stay active for the site to exist. The editing layer is built in. Not a developer console. A real admin interface where the owner can update a price, add a class, publish a news item, without calling anyone.

That admin layer is not a premium add-on. It’s the baseline. It’s what separates a website the owner controls from a website someone else manages on their behalf.

Maintenance is optional. If they want ongoing help, that’s a separate conversation. It is never a condition for the site to keep working.

Three Questions Worth Asking First

Before signing anything with a developer or an agency, three questions are worth getting clear answers to:

Who will own the domain registration?

Who will own the hosting account?

Can the content be updated directly after delivery, without calling anyone?

If the answer to the third question is no, or if the first two are answered with “we handle that for you,” the ownership is not complete. Those answers are worth getting in writing before the project starts, not after it ends.

Nextbyrd builds custom websites for small businesses and institutions. Sites are delivered on Next.js with full client ownership: domain, hosting, code, and a built-in editing layer. https://nextbyrd.com