Before you start
Bring the facts, not more tabs.
- You run the business alone or with one partner, and the website decision is yours to make.
- You need a working site in the coming weeks, not a months-long brand project.
- You can put a rough number on what an hour of your working time is worth to the business.
You will learn to
- Price both paths in the same unit: your hours count as cost, not as free labour.
- Decide who will make the routine edits — prices, photos, opening hours — for the life of the site.
- Name the situations where hiring a designer is clearly the right call.
- Use the middle path deliberately: template first, designer for a scoped job later.
Price both paths honestly, your hours included
The usual mistake is comparing a designer's quote against "free". Building it yourself spends working hours, and in a one-person shop those hours come out of serving customers. The comparison only means something once both sides are in money.
- Write down what one hour of your working time earns the business, based on a normal busy week rather than a quiet one.
- Estimate your DIY hours for a first version, then add the rounds of fixes that follow once real customers see it. If you have never built a site, doubling your first estimate is a reasonable starting point.
- Get at least one written quote for the site you actually need — the pages, any ordering or booking, and who handles changes afterwards — so the hiring side is a number too.
Done when: You hold two comparable figures: estimated hours times your hourly value on one side, a written quote plus your remaining coordination hours on the other.
Decide who controls next Tuesday's change
Launch happens once; edits happen for years. A price rises, a photo ages, holiday hours change. Whoever can apply those edits controls the site in practice, and a site the owner cannot touch quietly goes stale.
- List the edits your business makes in a normal month: prices, menu or service items, photos, opening hours, staff, short announcements.
- For each path, name who applies such an edit and how long it takes to go live: you in an editor the same day, or a message to a designer plus their turnaround and their rate.
- If you outsource, agree in writing before work starts who owns the domain, the hosting account, and the logins — and that you can change text and photos yourself without a service fee.
- Decide how much ownership you actually need. For most shops, holding the domain and the edit access is the part that matters. If the code matters too, Storefront Pro downloads the complete source of the site you built — you keep the files without leaving the tool that maintains them.
Done when: For every routine edit you can name the person, the tool, and the expected delay — and none of the three surprises you.
Know the jobs where a designer is clearly right
Build-or-hire is not a pride contest; some jobs are simply cheaper done by a professional the first time. Naming those jobs keeps the decision about facts instead of feelings.
- Hire for a brand rebuild: a new name, logo, colours, and voice that must hold together across the site, the storefront, and the packaging at once.
- Hire for complex integrations: the site must talk to an existing POS, inventory, or membership system, or needs custom behaviour no standard tool provides.
- Do not hire to fix unclear content. If you cannot yet say what the site should say, a designer will be guessing at your expense — write the offer, the prices, and the contact path first, then decide again.
- If the only trigger is "it should look more professional", try the narrower fix first: one coherent design style, real photos, consistent wording. Buy a full custom build only if that still falls short.
Done when: If you hire, the reason is a named job — rebrand or integration — written in one sentence, not a general unease about doing it yourself.
Take the middle path seriously: template first, design help where it counts
The choice is rarely all-or-nothing. Starting from an industry template puts a working site up at DIY cost, and a designer is then hired for a small, well-scoped job instead of the whole build. The gaps you find in real use make a far better brief than the worries you had before launch.
- Start from a template built for your industry, so the everyday structure of the trade — menu, services, portfolio, the pages customers expect — exists before you spend anything on design. In Naratake, that means picking one of 40 industry starting points and one of 15 design styles, in the browser.
- Publish and run it for a few weeks. Storefront is $49 a month or $468 a year — hosting, automatic HTTPS and one custom domain included — so set that against the quote you collected in step 1. Walk the customer’s path on your phone and keep a list of what you genuinely could not fix on your own.
- If that list is not empty, turn it into a fixed-scope designer brief — for example a logo, photo direction, and one pass over the homepage — priced as a small job on top of a site that already works.
Done when: The site is live and serving customers on the template path, and any designer engagement is a short written brief built from real gaps, not pre-launch guesses.
Make the call, and put a review date on it
This decision is reversible, and treating it as permanent is what causes the stalling. Decide on today's numbers, write them down, and re-check on a date when real usage has replaced guesswork.
- Apply the rule you built: rebrand or complex integration means hire; a standard shop, menu, or booking site plus hours you can spare means build; unsure means template first with a designer scoped in later.
- Record the decision with its numbers — your hourly value, the quote, the expected monthly edits — so the later review argues with facts instead of memory.
- Put a review date about three months after launch in your calendar: check which edits actually happened, what stayed broken, and whether a designer brief has written itself in the meantime.
Done when: The decision is written down with the numbers behind it, you have started on the chosen path, and there is a date in your calendar to check it against how the site is actually being used.
Final check
Do not call it done until these are true.
- You priced both paths in money, with your own hours counted at what they are really worth.
- The owner of the domain, the logins, and each routine edit is named for the path you chose.
- If a designer is involved, the brief is a fixed scope for a named job — rebrand, integration, or a specific list of gaps.
- The decision and the numbers behind it are written down.
- You have a review date roughly three months out in your calendar.