From invisible to ranked #1 across Melbourne's north. 5 weeks. $0 ad spend.
When Peter rang me, the first thing I told him was he probably shouldn't hire me. Not yet.

He'd been in business about four months. Most operators that new haven't proven they can run the business consistently, let alone whether they need a full systems build on top of it. I'd rather lose the sale than sign someone who isn't ready. False expectations are the fastest way to ruin both our reputations.
Then Peter asked me a question I couldn't argue with.
01The conversation that changed it
He'd already paid an agency to run ads. They'd pushed traffic at a website that wasn't built to convert. Total result over the full engagement: one booking. He'd had a bad time, and he wasn't interested in another version of it.
I told him straight. Mate, you've just started. You can do a lot of this yourself if you want. Most of it isn't rocket science.
Then he asked me a question most operators don't.
"Mate, you seem honest. Brooke said you're great. Honestly, if you were me what would you do? Do I need this now?"
I told him the truth. "Probably not now."
Then I gave him an analogy. The real one was rougher than what I'm about to write here, so for the sake of this case study still making sense in twelve months, let me clean it up.
"Do you wait until the problem hits before you build the thing that prevents it? Most operators do. They wait until they're losing leads, missing calls, sending invoices at midnight with three messages stacked up on the phone. By then, you're already drowning. Or do you build the rhythm now, so when growth comes it doesn't break you?"
(The real version was about waiting until you're fat to do something about it. Same point, less polished.)
I'll be straight with you. I waited too long with every business I ever built. Told myself I'd invest when the demand was there. Demand turned up. Demand nearly broke me. Peter wasn't going to make that mistake.
He decided to invest. We started the build the following week.
02What we actually built
This wasn't a website refresh. Peter runs his entire business through the system we built. The stack runs in four layers.
The customer-facing layer
- New website with conversion-first structure
- Logo refresh and branding tidy-up so the whole thing felt like one business, not three
- Suburb-specific landing pages for SEO across Melbourne's north
- An interactive quoting tool. Customers search their address, highlight the areas they want mowed, and get an instant estimate. I'll back myself here. It's the best quoting tool a lawn care business has in Australia right now. Happy to be proven wrong
- AI chat agent live across the website, Instagram, and Facebook
- Smart number on every channel. If Peter doesn't pick up within six seconds, Sarah (the AI voice agent we built for him) takes the call, qualifies the job, and books it in
The operations layer
- Automated calendar sequences, booking confirmations, and customer notifications
- Invoicing and payments built into the system. Cards held on file. Peter doesn't chase a single payment. Job finishes, invoice goes out, payment runs automatically
- The pipeline from quote to job to paid runs without him touching it
The reputation engine
- Personalised Google review requests after every job. No template-feeling messages
- Automated review responses. Peter doesn't write any of them
- Every new review auto-posts to his Instagram and Facebook as stories and feed posts
The marketing engine
- Social media scheduling runs through the system
- His presence stays alive across channels without him sitting at a laptop
The point wasn't to give Peter more to do. It was to give him a business that runs itself when he's on the mower.
03What it produced
Five weeks in, the rankings started landing.









Peter is now ranked #1 in Google's local pack across multiple Melbourne suburbs. Top three across a wider spread again. All of this in a market where his competitors have five years on the books and three times his Google review count.
He's a five-month-old business beating operators who've been running since 2020. Thirty-four reviews against their eighty, ninety, one hundred and sixty. Not because he's louder. Because the system underneath him does its job, and his work earns the reviews.
Meanwhile, the system keeps running. Quotes get sent. Invoices get paid. Reviews get requested, responded to, and posted to social. Peter mows. The infrastructure does the rest.
04Let me be honest about what we didn't do
We didn't get him every booking he now has. Peter's also been buying runs, working Grey Army (which he's been winding down), doing his own outreach, building his customer base the old-fashioned way. He's a good operator. Most of his growth is on him.
What the system did was make sure that when people went looking for lawn care in his suburbs, they found him first. And when they called, the call got answered. And when the job was done, the review request went out automatically. And when the next person searched, the reviews were already there.
That's what we built. The hustle is his.
05And this is the slow season
Right now it's autumn heading into winter. The slow months for lawn care. The rankings, the calls, the web enquiries, that's all happening in the off-peak.
Come spring, when every homeowner in Melbourne's north notices their grass got away from them over the weekend, Peter will be the first name they see in Google's local pack across his entire catchment. Sarah will be working overtime. He'll be a Google powerhouse in his suburb.
If you're in his catchment, get him while you can.
06If you're a new operator thinking about something like this
Here's the same thing I told Peter.
You probably don't need a full systems build the day you register your ABN. Most new operators don't. You need to prove you can do the work, do it consistently, and that customers will pay for it. The infrastructure comes after that, not before.
But there's a moment most operators reach where they realise they're losing leads, missing calls, sending invoices at 11pm with a beer in one hand and three missed messages on the phone. That moment is the wrong moment to start fixing the system. By the time you're drowning, you're already losing.
Peter saw it coming and decided to build it before that moment arrived. Most don't.
If you're somewhere in between, where the bookings are starting to come and you're wondering whether you can keep up when they double, you might be at the right point. If you're not sure, ring me anyway. I'll tell you straight.
Read the framework behind the build
This case study is the operational result of the Human Premium framework. Read how to decide what to automate and what to leave human.
Read The Human Premium →Let's map out your system.
Book a 30-minute discovery call. We'll look at the customer interactions you're already handling and show you where automation fits.
Book a strategy call →