I integrate into Canberra businesses as their tech and AI guy.
Websites built correctly from the ground up: structured to be preferred by Google and by AI, and designed to turn visitors into enquiries.
Software I've built and run that makes businesses money and takes work off your plate.
I come into your business, work alongside the people doing the work, and diagnose exactly what to fix.
No tool spitting out a score. I go looking for you the way a customer would, then tell you straight what I find.
I do these because most of the businesses I meet are losing work to a problem nobody has told them about.
Websites for Australian local businesses, each one designed, built and deployed by me, and every one doing the same job: get found by the people searching for that work, and send the owner the enquiry that turns into a sale.
Garden design, construction and care in Melbourne's inner north. Built from the ground up out of their own job photos, with every page pointed at one thing: the quote request landing in Saxon's phone.
Measured July 2026 · mobile
Outdoor structures and renovations in Canberra. A site that puts Ben and Ryan's finished work and credentials in front of whoever is deciding who to call.
Measured July 2026 · mobile
A Canberra brunch spot. The website, plus the QR offers funnel sitting on their counter that signs customers onto their SMS list.
Measured July 2026 · mobile
“Oscar has played a major role in building and managing our website, ensuring it not only looks professional and modern but also performs effectively for customer engagement and lead generation. Since working with him, we have noticed a major positive impact on our business exposure and customer engagement.”
The AI systems I build with keep a written record of how I work, because that is how they stay useful from one session to the next. It is not a character reference, and it is not independent of me: it was mined from about 2,600 of my own messages, grouped into recurring themes and ordered mostly by how often each one shows up. So it is a frequency count of my own corrections, restated back at me. That is a narrower claim than a testimonial. It is also harder to fake, because what someone corrects you on a thousand times is harder to perform than what they say in a first meeting.
He fixes the cause, not the symptom. He repeats this one constantly: “don’t patch it where it appears, patch it where it starts.” If the same class of failure comes back a second time, he treats the earlier fix as having been made at the wrong level, and goes further up.
He does not accept a claim without the evidence attached. “Show me a real one.” “The real number, not a guess.” Work is not finished when it is described as finished. It is finished when the check has been run and the output is on the screen.
He does not always stop where a reasonable person would. The record has him taking a client site from 69 on mobile to a clean 100 in every Lighthouse category, on mobile and desktop, and then measuring it three more times to be sure, because close enough irritates him. He does not reliably tell in advance which of those days was worth it.
Lean, not bloated. Scope that is not carrying weight gets removed. The rule carries its own counterweight, in his words: minimal is good, thin isn’t. This sits against the point above and he has not resolved it.
He tries to break his own work before he calls it done. The standing instruction is to go looking for the flaw, the regression, and the claim the code does not support, and to fix what turns up before declaring anything complete.
He does not leave things half-explained. Every piece of work ends with its state written down, on the assumption that whoever picks it up next knows nothing.
I build my own tooling because the work needs it, not because I intend to sell it. Two of those tools turned out to be useful enough on their own to put up publicly, free, under an MIT licence. If you write software with AI, they are aimed at you. If you don't, they are the plainest evidence I can give you of how I work.
Reads the Claude Code history already sitting on your machine and tells you how you actually work, with the receipts attached.
A Windows manager for running several Claude Code sessions at once, each in its own terminal on its own virtual desktop.
I'm cooking on a lot of projects right now, and the useful parts will land here:
I'm back to you within a day, usually much faster.