What a Website Rebuild Actually Involves: Scope, Stack and Cost in Australia

What a website engagement actually covers

A website build for an established business is rarely just the pages visitors see. It covers design and content structure, the technical stack the site runs on, integrations with the systems already in place — the CRM, the accounting platform, the booking calendar — plus performance and accessibility testing, and a migration plan for existing content, redirects and search rankings. Skipping any one of these pushes the real cost and risk into the months after launch.

Scope changes sharply once a site needs to do more than publish information. A booking calendar that has to hold availability against a back-office system is a different build to a brochure site, and the line between a website and a platform is where most budget confusion starts. Businesses taking payments, managing accounts or scheduling appointments online are usually better served treating that part of the build as its own project: see how scheduling software for growing businesses differs from the marketing pages sitting around it, or how a self-service customer portal changes the integration requirements entirely.

32% (Australian Bureau of Statistics, 2026) of Australian businesses now receive orders online, which means the website is increasingly the operational front door to the business, not a brochure sitting next to the real systems.

Choosing the stack: Astro, Next.js or WordPress

National Digital builds marketing and content sites on Astro or Next.js by default, and uses WordPress where WordPress genuinely fits: typically a content-heavy site a marketing team edits daily with no developer on staff, where the plugin ecosystem covers a genuine need. The wrong default runs the other way too. A WordPress site stretched to carry booking logic, membership accounts or complex integrations tends to accumulate plugins until it becomes harder to maintain than a purpose-built application would have been, one update away from breaking the page that drives revenue.

When a business migrates off WordPress, the real risk sits in what gets left behind: incomplete redirect maps, forgotten backlinks, metadata that never carries across. Redirect maps are usually incomplete the first time a team checks them against analytics, because old campaign links and partner backlinks point at URLs nobody remembers creating. Carrying metadata and structured data across deliberately protects search rankings through the transition. Regenerating everything from scratch during the rebuild is the more common path, and it's what usually breaks them.

How long a website project actually takes

Timeframes depend on what's being integrated, not on page count. A marketing site redesign with no system integrations can move through discovery, design and build in a short, predictable run. Add a CRM sync, a payment gateway or a booking calendar that has to talk to a reservation system, and the integration work, testing and staged rollout extend the timeline well past what a template site would need. Any fixed number quoted before scope is confirmed is a guess dressed up as a plan.

Cost follows the same logic. The design and the pages are a small, fairly predictable part of the budget. What varies is the number of systems the site has to talk to, how much historical content and how many URLs need to migrate safely, and how much custom functionality — booking, membership, inventory — sits behind the public pages. A realistic estimate only exists once those variables are scoped in writing.

When a website is really a platform in disguise

Some projects that arrive labelled a new website are actually a different kind of build. A brief with customer logins and account history behaves like portal software, not a content page. A brief with a product catalogue, stock levels and checkout is an e-commerce platform integration question, with its own decisions around Shopify, WooCommerce or a custom build. Confusing the two is where most budget surprises start; see how National Digital separates build vs buy software decisions before quoting anything.

National Digital rebuilt the Coral Expeditions booking experience as a mobile-first Next.js site on a typed API layer it designed and maintains (case study) The split shows up clearly in its booking flow: a marketing site exists to get a visitor into a reservation process doing real, integrated work underneath. Treating the two halves as one project usually means the marketing site's release schedule gets held hostage by the booking logic's testing cycle, or the other way around.