We talked ourselves out of the retainer, and won the build

The aeat.com.au front end was PHP sitting on top of Moodle, with Moodle doing double duty as the learning platform and the student management system, plus custom back-end code and a SharePoint reporting integration behind that. Every content change needed a developer. For an RTO running short courses on rolling dates, that means course availability, prices and page copy all queue behind someone else's calendar. Chris Davies asked for one specific thing on the homepage: a course calendar, so a student can see available dates without phoning.

Acquisition was not the problem. Courses were booked out. Students arrived through a WA Police Licensing referral page that sends people directly, which Chris rates above paid advertising, and the rest came through word of mouth and enterprise relationships. There was no traffic crisis to solve, and Northstar was in the room with an SEO retainer in the deck.

So we did the arithmetic out loud. About five providers in the whole of Western Australia can deliver Aspire's security course. First aid, by contrast, has roughly 2,500 competitors at about A$100 a head, against Aspire's A$1,100 two-day course. Same RTO, two completely different markets, and only one of them is a market where ranking decides who wins. Tommy told Chris on the close call that he did not need the retainer. Chris's reaction to the build pricing that followed: bang on what I expected, reasonable. No negotiation.

What the site did need to do was harder than ranking. It had to speak to individual students referred off a government licensing page and to employers putting around twenty trainees a year through a single relationship, on the same homepage, without reading like a corporate training catalogue. It also had to say Perth and Western Australia early, because there are no plans to operate anywhere else.

A build, deliberately without a retainer attached. The scope was a custom WordPress front end, the architecture, the technical SEO groundwork, and documentation so the team could run it themselves.

The design phase ran from December 2025 through February 2026. Site architecture was locked on 29 January 2026, the WordPress staging build went up for review on 4 February, the student handbook was integrated on 25 February, and the pre-launch technical SEO audit ran on 8 April with most high-priority items closed inside a week. Moodle stayed the system of record throughout, which was Clay's call and the right one: nothing about this project needed to touch the student management system.

There is no performance data for this client and there is no honest way to manufacture any. The new site is not confirmed launched, and at the last check aeat.com.au was still serving the old PHP build. There is no Search Console property, no GA4, no tag manager, no rank tracker and zero tracked keywords. No baseline was captured either, so even after go-live there is nothing to compare against. If you ask how we know this worked, the answer today is that we do not.

What this engagement does demonstrate is the decision at the front of it. A monthly retainer was on the table, the client would have signed it, and the competitor read said it would have been close to worthless. Removing it is why there was a build to win.