Web Development
Two Businesses, Two Websites for Impact Plumbing
Impact had grown into two businesses selling to two different buyers, behind one ageing website nobody at Impact could edit. So we built them two. The construction site carries a project portfolio their own staff publish. The maintenance site is built around one booking form that lands a complete job request, photos and all, in the systems the office already works from.
01
The challenge
Impact Plumbing had outgrown its own website.
By 2026 the business was really two businesses with two different buyers. The construction side wins plumbing packages on commercial projects and gets judged on the work it has delivered. Impact Maintenance is who you call when a drain backs up in a body corporate building, or a backflow device is due for testing. One WordPress site was trying to talk to both, and doing neither well.
Underneath that sat three problems.
Nobody at Impact could update the site. Every finished project, every changed detail, meant asking someone outside the business. So in practice it sat still while the business moved on.
Maintenance enquiries turned up as a phone call or a bare email, which started a chase. What's the address, what does the problem actually look like, who lets us in, when can we come. All of that has to happen before anyone can be scheduled.
The old site had years of search equity in its URLs, and a careless cutover throws that away.
02
The solution
We built two independent websites instead of one site with a maintenance section.
impactplumbing.net.au is the construction business: a project portfolio, capability pages, and enquiry and job-application forms that route by topic to estimating, accounts or applications.
impactmaintenance.com.au does one job. It gets a maintenance request booked with everything the office needs to act on it. One booking form serves the contact page, a standalone /book page for QR codes and fridge magnets, and a booking window that follows you down the home page. It asks whether you're a household or a business, takes the address and pins it on a map, takes a preferred date and a morning or afternoon window, and lets people attach up to five photos of the problem.
Around that sit the pages people actually search for. Eight service pages covering blocked drains, hot water, burst and leaking pipes, taps and cisterns, gas fitting, backflow prevention, planned maintenance and emergencies. Five more for the buyers Impact serves. Fourteen advice articles that answer plumbing questions plainly.
Enquiries land where the office already works. A request writes a record into Impact's own business platform and sends an email into the maintenance mailbox with the photos attached. Nobody has to log into a separate form tool to find out someone needs a plumber.
And Impact edits the site from the tool they already have open. The construction site's admin sits inside the Office app the team uses every day. Edit a project, upload photos, press Publish, and the site rebuilds itself.
03
The results
Both sites went live in August 2026 with conversion tracking on from day one.
Maintenance enquiries now arrive complete: photos, an address on a map, who's asking, and when they want someone there. They land in the mailbox the office already works from, and in Impact's own platform, where the data stays theirs.
Impact publishes its own project work now. Adding a finished job is something the team does in the app they already use.
Every indexed page from the old site redirects into the new structure, so the search equity carried over instead of 404ing at cutover.
The maintenance site is indexed and showing up for the work it does: backflow testing, blocked drains, hot water, gas fitting and commercial maintenance across Brisbane and regional Queensland. It ranks first for the business's own name.
We're not going to dress that up as an SEO win yet. The site is weeks old, it sits deep in the results for the competitive service terms, and the clicks haven't come. What's there now is what rankings get built on: real content answering real questions, on a site that loads as plain HTML and that the business can add to itself.
The delivery journey
How the transformation took shape
01
The journey
We've built and supported Impact's internal systems for years. Purchase ordering, workforce management, site sign-ins, reporting. So the websites weren't a cold start. We already knew how the business quotes, schedules and invoices, and what the office does with an enquiry once it lands.
The first decision was about structure, not design. Impact Maintenance had grown into an operation with its own customers and its own way of being found, so it needed its own front door. Everything else followed from that.
The /book page came from watching how the maintenance team actually meets people. A QR code on a fridge magnet or the back of a van is a different entry point from a Google search, and it deserved a page that starts the booking straight away.
02
Implementation strategy
- Both sites are plain HTML pages, generated ahead of time. If a search engine or an AI crawler gets an empty shell that fills itself in later, the content may as well not be there. Impact's internal apps work the opposite way, because nobody crawls those.
- They run on Azure Static Web Apps with a small API each, on the same cloud account as Impact's other systems. One account, one set of logins, no new vendor to manage.
- The maintenance enquiry path is built around which failure would hurt most. Photos go to storage, a record goes to Impact's platform, an email goes to the office. The email is the one that must never fail, because the office works from the mailbox. A database problem gets logged, and the customer's request still arrives.
- The construction site's content lives in a database and is baked into each build. Editors work in the admin and press Publish, which triggers a fresh build and deploy. Visitors get static pages, staff still edit for themselves.
- Editing rights come from group membership in Impact's own directory, inside the Office app the team already signs into. No extra password to hand out or take back.
- Deploys sign in with short-lived tokens, so there are no long-lived cloud credentials sitting in the pipeline.
03
Long-term impact
The content is Impact's to change. The usual reason a contractor's website goes stale is that updating it means asking someone else, and that dependency is gone.
Enquiry data builds up in Impact's own platform, next to the operational data that's already there, instead of inside a form product they'd have to export from.
The maintenance business has its own front door. It can grow its own services, service areas and advice content without being held back by the construction brand, or holding it back.
And the content keeps working. Service, buyer and advice pages are what earn rankings and get quoted in AI answers, and Impact can keep adding to them.