Case study · Melbourne service businesses (composite)
Local services · lead capture · Brochure rebuild + form plumbing
Brochure sites that actually convert on mobile
- websites
- forms
- next.js
- melbourne
- local-seo
Composite patterns from Melbourne salons, cleaning crews and coaching businesses: sites that looked fine on a desktop audit but leaked leads on phones. Scope stayed brochure-grade while forms, speed and CRM handoff became reliable.
Why this is a composite
This case study blends recurring patterns from several Melbourne operators (beauty, cleaning, coaching, trades-adjacent services). No single brand is named because the delivery was not one literal repo swap. The technical and scope lessons are the same ones I use on real rebuilds and rescues.
Context
Each business already had a marketing site that “passed” a quick desktop glance. Owners invested in photos and copy, then wondered why enquiries still arrived through DMs instead of the contact form.
Mobile traffic dominated. Forms failed on iOS Safari after autofill, thank-you pages never fired analytics consistently, and CRM or inbox automations dropped when spam filters changed. Staff learned not to trust the website.
What broke
- Mobile layout and field validation. Long single-column forms with tiny tap targets; submit errors only visible after scroll.
- Slow first paint on cheap phones. Large unoptimised hero assets and blocking scripts made people bounce before they read pricing.
- No reliable CRM record. Successful submits sometimes landed only in an admin mailbox, not in HubSpot, Zoho or the shared inbox rules the team expected.
- Analytics double-fired on soft navigations or duplicate GTM tags, so leadership stopped trusting conversion numbers.
Approach
We treated the project as a brochure site, not a product platform. That meant a tight page list (home, services, proof, pricing or “from”, FAQs, contact, legal), honest performance targets, and integrations scoped as “form in, CRM or email out, with failure alerts.”
Implementation leaned on a maintainable static or Next.js marketing stack depending on hosting and who will edit copy later. Forms used server-side validation, honeypot or provider spam controls, and explicit success and error states so visitors are never left guessing.
Where the old CMS was the bottleneck, we either fixed the minimum viable path or rebuilt only the public marketing layer, keeping booking or payment tools unchanged when they still worked.
What improved
- Enquiries that actually arrive where staff already work (CRM, shared inbox, or both).
- Contact flows that survive flaky train Wi-Fi and small screens.
- A handover document: what to edit, what not to touch, and who to call when spam volume shifts.
- Leadership could trust “did the site send anything this week?” without opening three systems.
Lessons you can reuse
If the pain is mostly one broken integration, a full rebuild may be the wrong sale. Start from When a focused brochure site beats a full rebuild and be honest about rescue vs replace.
Test three real phones, not one Lighthouse run in Chrome. Autofill, keyboard overlap, and upload fields behave differently in the wild.
For a self-audit before you brief anyone, Website form audit checklist mirrors the checks we run in discovery.