A website built by a relative or friend
A website built as a favor is the cheapest site available and the most expensive to recover. The problem is almost never the quality of the work. It is what happens two years later.
Compare
Short answer
A site built by a relative or friend usually costs nothing and carries a specific risk: the domain, hosting and accounts often end up in their name, and nobody documents anything. Agree ownership and access in writing before it starts, whoever is building it and however informal it feels.
The real risk is not the quality
Plenty of sites built by a capable relative are perfectly good. They answer the questions, they load, and they do the job the business needed at the time.
The risk is structural. The domain is registered in their name, the hosting is on their account, the password is in their head, and nothing about how it works is written down.
Two years later the relationship has changed, they have moved, or they have simply lost interest, and the business discovers it does not control its own address.
It puts the relationship at risk too. A business asking for changes it is not paying for, and a relative who has stopped enjoying it, is a conversation neither side wants to have at a family gathering.
Agree the ownership first
The domain must be registered in the business name, in an account the business controls, paid on a business card. This is the single most important item and it takes ten minutes.
Hosting and every connected account should be the same. Analytics, business profiles, form delivery, anything that could stop the site working or hide what it is doing.
Our page on one business, one domain covers why the address is the asset. Everything else on a site can be rebuilt; the address cannot be recovered on demand.
Agree what happens when they stop
Not if. Every informal arrangement ends eventually, and the version that goes badly is the one where nobody discussed it while everybody was still enthusiastic.
Ask for a written note of how the site is built, where everything lives, and what needs doing periodically. An afternoon of documentation is what makes the handover survivable.
And agree what maintenance means. A favor that turns into an unpaid obligation is how these arrangements sour, and being explicit protects the relationship as much as the business.
Decide who they hand it to. Naming a successor, even loosely, turns an ending into a handover, and it is far easier to agree that at the start than to arrange it in a hurry later.
What to settle before anybody starts
The list below takes an hour and prevents nearly every version of this going wrong. None of it implies any distrust; it is the same list you would agree with a paid provider.
- The domain registered in the business name and account
- Hosting and all accounts in the business name
- A written note of where everything lives
- Who does updates, and how often
- What happens when they stop
- Whether anything is licensed rather than owned
- That the business can hand it to somebody else without a conversation
Recovering a site you do not control
Start with the domain. Registrars have transfer processes, and they generally require the registered holder to act, which is why the conversation has to happen while relations are good.
Then the content. Words and photographs can be copied from a live site even without access, so a rebuild is always possible. Our page on moving a site covers the mechanics.
What cannot be recovered is the standing an address has built with a search engine or an answer engine. That is the actual cost, and it is why the first conversation matters more than any technical detail.
Paying something changes it
Even a small payment turns a favor into an arrangement, which makes it reasonable to ask for documentation, access and a response time without anybody feeling awkward.
It also sets a natural end point. Paid work concludes; favors drift, and drift is what produces a site nobody has looked at since a rebrand two years ago.
If payment is not appropriate, write down the arrangement anyway. The writing is what matters, not the money.
When it is genuinely the right choice
For a new business with no budget and a capable relative, a simple honest site now beats a professional site in six months. Being live matters more than being polished.
Keep it small so it can be replaced easily. A handful of pages that say the right things is both a good first site and a cheap thing to move away from.
And treat it as a first site rather than a final one. Our page on a new business website covers what that first version actually needs.
Questions people ask
What is the main risk?
Not the quality of the work. It is that the domain, hosting and accounts end up in somebody else's name with nothing documented, and the business discovers two years later that it does not control its own address.
What should I agree before it starts?
That the domain and every account are in the business name, that there is a written note of where everything lives, and what happens when they stop. It takes an hour and prevents nearly every bad version.
Can I recover a site I do not control?
The content can always be rebuilt. The domain requires the registered holder to act, which is why that conversation should happen while relations are good rather than after they are not.
Should I pay a relative for the work?
Even a small payment turns a favor into an arrangement, which makes it reasonable to ask for documentation and access. If payment is not appropriate, write the arrangement down anyway.
Keep reading
See your website built from a conversation
15-day free trial. Card required. Cancel before day 15 and you pay nothing.