Custom website vs WordPress: which is right for your Australian business?

Most Australian businesses asking "should we use WordPress or build something custom" are really asking three different questions at once. Some of them have a clear answer. Others don't.

Here's how to figure out which one applies to you, from a studio that has built sites on both sides of the line.

The honest summary

WordPress is the right choice for most small businesses that need a content-heavy site they can update themselves and don't mind a slightly dated feel. It is well-trodden, well-supported, and cheap to run.

A custom website is the right choice when your site is core to how you sell or operate, when performance matters, or when you want it to feel meaningfully different from every other site in your industry. It costs more upfront and less long-term, in most cases.

If you're already sure which side you're on, stop reading and brief someone. If you aren't, the rest of this post is for you.

What WordPress is genuinely good at

A few things WordPress does well that custom builds often struggle with.

Editorial workflow at scale. If your business publishes a lot (blog, news site, large multi-author site), WordPress's editor and roles system is hard to beat. Twenty years of refinement is a real moat.

Plugin coverage. There's a WordPress plugin for almost anything. SEO, forms, e-commerce, memberships, learning management. Half of them are mediocre, but the good ones are very good.

Hire-ability. There are more WordPress developers in Australia than developers in any other web stack combined. If you need a quick fix on a Sunday night, you can find someone.

Low day-one cost. A competent WordPress site can be built quickly and cheaply by a freelancer. For some businesses, that's exactly right.

What WordPress is genuinely bad at

Performance. WordPress is slow by default. You can make it fast, but you'll spend real engineering hours doing so, and the result is usually still slower than a modern static or React-based site. If Core Web Vitals matter to you (and they should), WordPress is fighting you.

Security. Most hacked Australian small business websites we've seen were on WordPress, almost always due to outdated plugins. It's manageable with a real maintenance retainer. Without one, you're rolling the dice.

Looking distinct. Most WordPress sites look like WordPress sites, even when they don't have to. The defaults pull you toward a familiar layout, and most themes amplify it. Standing out costs effort.

Hidden complexity. The "WordPress is simple" line is partly true and partly not. Once you have 6 plugins, a custom theme, a builder like Elementor, and a CDN in front, WordPress becomes a stack you have to maintain like any other.

What custom websites are good at

When we say "custom website" we usually mean a modern site built on something like React + a headless CMS (Sanity, Contentful, Payload) or a static framework like Astro or Next.js. The specifics don't matter much for this comparison.

Speed. A well-built custom site loads in under a second. WordPress without a lot of optimisation usually doesn't. For e-commerce or lead-gen sites, that speed difference shows up in conversion rates.

Looking like you. Custom design and custom code means the site can feel like your brand instead of a theme. For early-stage companies trying to look ahead of the curve, this is often the whole point.

Tightly scoped editing experience. Headless CMS setups let you build an editor that only shows the fields your team actually needs. Your marketing person isn't fighting plugin settings to publish a blog post.

Cleaner integrations. Custom builds connect to Stripe, your CRM, your auth provider directly. No layer of plugins between you and the thing.

Less maintenance surprise. Modern custom sites don't have the plugin auto-update churn that breaks WordPress sites at 2am.

What custom websites are bad at

Day-one cost. A custom site starts at $5,000 to $15,000 from a small studio. WordPress can be in the low thousands. If budget is the binding constraint, that matters.

Editor familiarity. Your team has probably used WordPress before. A custom CMS, even a nice one, has a learning curve.

Long-term ownership. If you part ways with the team that built it, finding someone to maintain a custom React + Sanity site is harder than finding someone to maintain WordPress. Not hard, just harder.

How to decide

If three or more of these are true, WordPress is probably right:

• Your site is primarily content (blog, news, association, directory)
• You publish multiple times a week
• Budget is tight (under $5,000)
• You need to do everything yourself with no developer help
• Performance is "nice to have" rather than central

If three or more of these are true, custom is probably right:

• Conversion rate matters (lead-gen, e-commerce, signup-driven)
• You want the site to feel meaningfully different from competitors
• You're raising or selling and need it to look the part
• You publish less than once a week
• You have at least $5,000 to $10,000 for a small site
• The team that uses the editor is small (one or two people)

The middle option

Webflow sits between the two. It gives you a visual editor like WordPress and the design freedom of a custom build, at a price point closer to WordPress than to custom. For a marketing site of moderate complexity, it's often the right answer.

The trade-off with Webflow is that you're locked into their platform. Custom code escapes are limited, hosting is theirs, and complex web app functionality is off the table. It's a marketing-site tool, not a product-build tool. We've written more about Webflow specifically in another post.

What we actually recommend

For most Australian businesses that ask us this question, the answer is one of these:

• "You sound like you need WordPress, and we don't build on WordPress, so we're not the right team."
• "You sound like you'd be well-served by Webflow. We can build that for you."
• "You sound like you need a real custom build, and that's what we do."

The honest answer for your business depends on how content-heavy you are, how performance-sensitive your traffic is, and whether the site is central to how you sell. If you want a second opinion on which bucket you're in, tell us a bit about the project and we'll give you a straight answer.