Aamir.melbourne

Guide · Melbourne

Melbourne rooftop at twilight with chaotic wireframes resolving into one calm landing page card

When a focused brochure site beats a full rebuild

· 9 min read
  • websites
  • scope
  • budget
  • planning

Not every outdated website needs a six-month agency project. How to decide between targeted fixes, a new brochure site, and a bigger platform build.

Rebuild sales cycles favour vendors, not operators

Agencies make margin on large replatforming. Operators make margin on clear positioning, working forms, and credible pages customers can load on a phone in a tram shed under flaky Wi-Fi.

This guide is a decision framework for Melbourne owners: fix, new brochure site, or larger product build—with the honest middle where I am not the right fit.

What a brochure site is actually for

Credible story: who you are, what you sell, proof, pricing or “from”, FAQs, contact, and basic local SEO. Fast handover so you are not locked into a proprietary blob you cannot patch. Maintainable stack (I often ship Next.js or similar for marketing sites).

It is not a logged-in customer portal, multi-vendor marketplace, or bespoke booking engine—those can be valid, but they are different contracts and risk profiles.

Signals you probably need fixes, not a rebuild

Brand and layout still represent you well, but forms fail, Lighthouse scores hurt mobile, or analytics double-fires. Your CMS is familiar to staff. Those are website fix paths—smaller blast radius, faster certainty.

  • Visual identity and copy are broadly current.
  • Content updates happen without developer tickets today.
  • Pain is reliability, speed, tracking, or a specific integration—not “everything is wrong.”

Signals a new brochure site is the rational move

Mobile layout is broken in ways patch CSS will not cure cheaply. HTTPS or domain hygiene is a mess. You merged two businesses and need a single story before spending on ads again. You are on unmaintained tech the next contractor will refuse to touch.

For many local businesses, a focused rebuild from a clear scope beats death-by-a-thousand retainers on a site you secretly hate.

Signals you need more than a brochure

Customer accounts with saved payment methods, complex entitlements, multi-tenant admin, or heavy custom workflows usually belong in application engineering—not a marketing brochure quote. I will say that early rather than stretch a brochure scope into a product pretending to be a website.

A briefing template you can send any developer

Goals: What must improve for the business in 90 days?

Pages: List must-haves vs nice-to-haves.

Integrations: Forms, CRM, booking, analytics—what must fire on submit?

Content owners: Who writes and who approves?

Success metrics: Lead volume, page speed, accessibility, cost to change a price—pick two numerics.

That packet reduces rework for you whether you hire me or someone else.

Melbourne context

Hybrid calls and occasional on-site in the inner north or CBD can unblock whiteboard scope faster than another Zoom. AEST matters when your customers and staff are local—even if hosting is global. More on how I work locally on the Melbourne hub.

When to get help

If the table below does not land you in one clear column after a serious internal discussion, bring an external pair of eyes—scope arguments are cheaper before contracts than after.

  • Fix: isolated failures, acceptable design, known CMS.
  • New brochure: credibility gap, mobile/HTTPS crisis, post-merger story reset.
  • Bigger build: product features, complex auth, regulated workflows—plan budget and owner time accordingly.