Build Your Own Website or Hire a Web Designer?

Build it yourself if the site is simple, you have time to learn and you enjoy the process; hire a web designer if the site has to bring in business soon, needs custom features or must look polished from day one. Many people end up somewhere in between: a professional sets up the structure and design, and the owner edits pages and posts afterwards. The right answer depends less on skill level than on what the site has to do and how much of your time it is worth.

Two kinds of do-it-yourself

"Building your own site" can mean two quite different things, and the trade-offs are not the same.

• Coding it by hand. You write the HTML, CSS and perhaps some JavaScript yourself, then put the files on a host. You control every detail and learn a great deal, but every feature is your job.
• Using a site builder. You pick a template and drag in blocks. It is quick to get something online, but you work inside the builder's limits and its way of doing things.

If you are still getting comfortable with the basics, this explainer on what HTML and CSS each do on a page is a good place to see how much hand-coding a simple site really involves.

The trade-offs side by side

Time is the hidden cost

The first version of a home-built site usually comes together quickly. The slow part is everything after: making it look right on phones, fixing the contact form, writing the pages, sorting out images that load too slowly. If you are learning to code, that time is also practice, which has real value. If you are running a business, it is time not spent on customers.

Upkeep does not stop at launch

Websites need care. Software and plugins get updates, some of them for security reasons, and a site that is never updated becomes easier to break into. Builders take care of much of this for you, while a hand-coded static site has less to patch but still needs attention when you add forms or scripts. A designer can include maintenance in an agreement, so ask about it before work starts.

Own your domain and content either way

Whichever route you choose, a few things should always be in your name:

1. The domain name, registered to you with your own login.
2. The hosting or builder account, or at least admin access to it.
3. Your text, images and any customer data the site collects.
4. A recent backup you can download.

This matters because you may want to switch builder, host or designer later. Moving is much easier when the domain and content were never tied to someone else's account. Check the terms of any service or agreement you sign, since the rules on exporting content and code differ.

The hybrid approach

A popular middle path is for a designer to build the site and for you to manage day-to-day updates. The designer handles structure, look, speed and anything technical, then hands over a site with an editing area you can use for new pages, blog posts or price changes. Someone in Auckland, for example, might compare local studios such as a Website Company New Zealand to see how they set up handover and training for owners who want to keep editing themselves.

For learners, this can work well too. Watching how a professional organises templates, styles and files is a practical lesson, and you can take on more of the work as your skills grow. Understanding the split between front-end and back-end development helps you see which parts you could realistically take over.

Questions to help you decide

What does the site need to do in the next few months?

A portfolio or personal project can grow slowly. A shop, a booking page or a site that clients will judge you by has less room for trial and error.

Would you rather learn this or hand it off?

If building websites is part of what you want to be able to do, the DIY route is training as much as a cost. If it is a distraction from your real work, paying someone may be the better use of your time.

Who will look after it next year?

Picture the site a year from now with a broken form or an outdated page. If the honest answer is "nobody", plan for that now, either by learning maintenance or by agreeing support with a designer.

There is no wrong choice as long as it matches the job. Try building a small site yourself to learn what is involved, keep your domain and content under your control, and bring in help where the work goes beyond what you want to do on your own.