I build the systems your business runs on.

Enquiries wait until Monday. The same details get typed in three times. I find the jobs that eat the most hours and hand them to software.

• Automation sprintTeams losing hours to retyping and copy-paste2 weeks
• AI agent buildMissed calls, repeated questions3 weeks

I built the Journey Engine in AgentHub 360: automations with 12 action types and if-this-then-that rules.

1. 0.0s

   Sam K., Footscray

   Call after hours. The office closed at 5.

2. 2.0s

   Wants a deck repair quote

   AI agent answered. Asked about the job, the suburb and a good time.

3. +2 min

   New job: deck repair

   Saved to your CRM. Call summary and recording attached.

4. +3 min

   Booked: Thu 10:00 am

   Sam confirmed by SMS. Quote visit on the calendar. Sam gets a reminder.

Your numbers live in five tools and nobody fully trusts them. I build one place where they're right, updated daily, with the reports you actually check.

• Data foundationNumbers spread across tools4 to 6 weeks

I built StreetXray, which turns government map data into instant bushfire, flood, heritage and powerline overlays across 5,000+ suburbs.

1. 2:00 am

   Five tools read

   Nightly sync. Accounting, the job system, the CRM and two spreadsheets.

2. 2:03 am

   Jobs matched to invoices

   Checked. Duplicates merged. Three mismatches flagged for you.

3. 2:05 am

   One set of numbers

   One table. Revenue, jobs and margin by week and by job type.

4. 7:00 am

   Monday report

   In your inbox. The numbers everyone checks, with no copy-paste.

Off-the-shelf software fits your business badly. I build software around how you work, from internal tools to full SaaS products.

• MVP buildFounders with a validated idea6 to 10 weeks

I built AgentHub 360, a CRM used by more than 50 paying property agencies, and Review Lens, a Chrome extension that flags fake reviews and has 1,500 installs.

1. Week 1

   One page, one fixed price

   Scope agreed. What version one does, and what waits for later.

2. Week 3

   Sign-up and the core flow

   First working build. In your GitHub, with a video update every week.

3. Week 7

   Your first sign-ups

   Real users. What they trip on gets fixed before handover.

4. Week 8

   You own the code

   Handover. Docs, a walkthrough and 30 days of fixes.

Your cloud bill grew and nobody knows why. I set up AWS and Google Cloud properly, and find the waste in what you already run.

• Cloud and BigQuery bill checkAWS or Google Cloud bills that keep growing5 business days

1. Day 1

   12 months of AWS spend

   Bill read. Every service and account, month by month.

2. Day 2

   Idle servers, a database too big

   Waste found. Plus logs kept forever and no savings plan.

3. Day 4

   Every change, priced

   Plan written. What to switch off, resize or commit to.

4. Day 5

   Your plan, in plain English

   Walkthrough. What to change first, and what each change saves.