Before You Build a Website: 10 Things Regional Businesses Need First

Before you build a regional small business website, ten things need to be in place: a one-sentence answer to what you do, a defined customer, three pieces of proof, a structured offer list, an enquiry-handling process, locked brand decisions, one clear primary action, the boring legal pieces, a content plan, and a measurement plan. None of these require buying a tool. All of them affect whether the website earns its money.

Most regional businesses I talk to in the Central Highlands and across regional Queensland have had at least one website that didn't deliver what was promised. New design, new platform, big invoice — and six months later the phone isn't ringing any more than it was before.

The website wasn't the problem. The system underneath it was missing.

This is a checklist of ten things to have in place — or at least have answers for — before you commission a new website. This isn't about delaying your website forever. It's about making sure the website has something to connect to when it goes live. Run this list, sort the gaps, then build with confidence. If you can tick most of them off, your next website will earn its money. If you can't, you'll be back here in eighteen months wondering why nothing changed.

The ten

1. A one-sentence answer to "what do you do?"

Plain English. No jargon. Tested on someone outside your industry.

If your one-sentence answer is "we provide bespoke end-to-end digital solutions" — that's a sentence about you, not about what you do. Try: "We build websites for tradies in Central Queensland." Now I know.

The website's homepage is going to need this sentence. The version you write before the build starts is almost always better than the one you write under deadline pressure.

2. A list of who you actually want as customers

Not "anyone with money." Specifically: which businesses, which suburbs, which size, which budget, which urgency. The more specific you are, the easier every other decision gets.

If your customer is "a tradesperson with a team of three to ten in the Central Highlands who wants more residential leads," every page of the website knows what to say. If your customer is "everyone," the website ends up bland.

3. Three proofs

Three pieces of evidence that you do what you say you do. Best case: three named customers with real quotes. Acceptable case: three projects with real numbers (revenue, time saved, ranking, whatever's relevant). Minimum: three specific things you've built, sold, or shipped that you can describe in detail.

Generic stock-photo testimonials with first names and last initials count as zero proofs. If the homepage launches without proof, the website is asking strangers to trust a stranger.

4. A list of what you actually offer

Categorised. Bundled where it makes sense. Trimmed where it doesn't. (SOP #009 walks through writing clearer offer copy with AI assistance — useful before the website tries to sell anything.)

The list of services on most regional business websites is a graveyard of things the owner used to do, things they could do if asked, and things they actually want to sell. The website is more honest if you decide which of those is which before the build starts.

5. A clear way pricing is handled

Not "every price must be public." That's not the rule. The rule is that you know how the offer is sold before the website tries to sell it.

For some businesses, public pricing is the right answer — products on a shelf, packages with a fixed scope, anything where the customer can buy without a conversation. For others, pricing only appears after a discovery call, because the right answer for one client is genuinely different from the right answer for another. Both are fine. What's not fine is "we'll figure that out later" — because the website will end up vague, the visitor will leave, and you'll wonder why the form's empty.

Decide before the build: is each offer fixed-price, from-priced, packaged, or scoped on enquiry? Then design the page accordingly.

6. A way for enquiries to land somewhere they won't be missed

Right now, when someone fills out the form on your existing website, where does it go? If the answer is "an email I check sometimes" or "a shared inbox where things get marked read by accident" — fix that before the new website goes live.

Minimum acceptable: a single inbox, checked daily, with a defined response time and a backup person. Better: a CRM where every enquiry gets a record automatically, tagged by source. Best: an automated workflow that tags, routes, and triggers a follow-up reminder.

A new website that delivers more enquiries to a broken inbox makes you slower, not faster. (SOP #008 covers the full intake-to-onboarding flow — intake form, welcome email, agreement, kickoff call, and access checklist — which is what should sit behind the contact form on the new website.)

7. A set of brand decisions that are actually decided

Logo. Two or three brand colours with hex codes. One or two fonts. A tone of voice that someone could write to. A few photos that aren't stock.

If you don't have these, the design phase of the website becomes a brand exercise in disguise — which is fine, but it doubles the timeline and triples the budget. Decide first, design second.

8. A clear answer to "what should someone do on the website?"

One main action. Maybe one secondary. Not seven.

A regional services business probably wants someone to either book a call or fill out an enquiry form. A regional retailer probably wants someone to buy or check stock at the nearest store. A community platform probably wants someone to subscribe or sign up. Pick one. The website is going to be designed around it.

If the answer to "what should someone do on the website" is "everything" — every button is going to compete with every other button. That's how you get pages that look busy and convert nothing.

9. The boring legal bits

You'll need a privacy policy, terms of service, and (if you sell physical goods) a returns policy. Australian Consumer Law has some disclosure requirements. Cookie consent matters if you're running analytics or remarketing.

This is not legal advice. It is a business-readiness check. Your website should not promise things your terms, privacy setup, or internal process cannot support. If you're unsure, get a solicitor or a reputable Australian template service to look over what you're publishing. The point isn't to scare you about compliance — it's to make sure you don't go live and discover the night before that nobody wrote a privacy policy.

10. A plan for the content you don't have yet

Most regional business websites need content that doesn't exist yet — product photos, an "about" story, customer quotes, frequently-asked questions, a few blog posts to seed search visibility.

Decide before the build starts: who's writing it, who's photographing it, who's approving it, when. The most common reason a website launch slips by three months is that nobody's been making the content while the design has been getting built. The design finishes; the content isn't ready; everything stalls.

Score yourself

Run through the ten. Count how many you could answer cleanly today.

If you scored lower than you wanted to, that's a useful diagnostic. The gap between where you are and 9–10 is usually three or four foundation pieces, not a whole rebuild.

What this looks like as a habit

This is the kind of issue we see constantly in regional businesses — hardware stores, service businesses, tourism operators, clubs, cafés, clinics, and local retailers. The pattern is the same. The fix is the same. Only the specifics change.

A worked example: the DermaGen by Botanical Chemist Shopify rebuild went through a version of this list before any code was written. DermaGen had a strong product range and genuine clinical expertise — and a digital presence that wasn't communicating either of those things. The store was producing about $500 a month. We worked through the ten checklist items below before the rebuild brief was even written.

One sentence: "Clinical-grade skincare formulated by a botanical chemist — for sensitive, mature, and reactive skin."

Customer: women across Australia who've tried department-store skincare and can't find anything that actually settles their skin.

Proof: clinical formulator credentials, ingredient sourcing transparency, real reviews from a small but loyal existing customer base.

Offer list: products grouped by skin concern (sensitivity, ageing, breakout) with clear ranges and no overlap — so a buyer could land on the homepage and move straight to the right product.

Pricing: public on every product page. Ecommerce — public pricing was the right answer.

Enquiry handling: Shopify storefront plus an email capture, tagged into Klaviyo flows for abandoned cart, post-purchase, and replenishment. Every interaction had a follow-up.

Brand: existing brand pack was solid — logo, hero photography, product photography, voice doc — locked before design started.

Main action: "Shop the range" and "Find your skin type." One primary action per page.

Legal: privacy, returns, Australian Consumer Law disclosures — handled before launch.

Content plan: product copy, blog posts on skin science and ingredient guides, full email sequence — written before launch, not after.

The result: within six months of going live, monthly online revenue went from ~$500 to $30,000. Over three years the system has produced $592K+ in total sales. The website wasn't doing the heavy lifting on its own — the system underneath it was. The website was the front door.

Your next step depends on where you are

The website doesn't fail because it's bad. It fails because there's nothing behind it.

Build the system first.

---