Internal systems
The unglamorous software a company runs on: presence, scheduling, inventory, approvals. Built around the process you already have, not the one a SaaS assumes.
OFFLINE-FIRST · POSTGRES · REAL TIME
Back to portfolioTaking on projects for Q4 2026
I build the internal systems a business actually runs on.
Contract work, remote across AEST or on site on the Gold Coast. You talk to the person who writes the code — no agency layer, no forty-page proposal.
Internal tools/Operations dashboards/React & Node/Applied AI/Data pipelines/Integrations/Field apps, offline-first/TypeScript end to end/Next.js/PostgreSQL/Supabase/Data modelling/Process automation/Getting off spreadsheets/Reports nobody assembles by hand/Auth and permissions/Installable PWA/End-to-end tests/REST APIs/Python for data/Docker/Deploy and observability/
Where I'm useful
Web products
Customer-facing applications and interfaces in React and Node — fast, accessible, and maintainable by whoever comes after me.
NEXT.JS · REACT · ACCESSIBILITY · PWA
Applied AI
Models, classification and assistants where they pay for themselves — and an honest answer when they don't. Usually the data pipeline is the actual project.
IN-BROWSER CLASSIFICATION · PIPELINES · PYTHON
How I work
- FIRSTUnderstand the process — on site or on call
- BEFORE ANY CODEData model and security boundaries, in writing
- EVERY WEEKSomething working for you to look at
- AT THE ENDDeployed, documented, handed over running
What I hold to
01
I start with the process
Two days on site or on call, watching how the work actually happens. The software comes after.
02
I ship the boring part first
Data capture before dashboards. A clean entry point solves half of what people call an AI problem.
03
I hand it over running
Documented, deployed, and simple enough that the team keeps using it in month six.
Proof
Case 1 of 1
Helix
Operations app for the field crews of an electricity distribution contractor with 4,000+ employees.
Client: SIRTEC·ELECTRICITY DISTRIBUTION
The blind spot
Managers couldn't see in real time what each crew was doing, and much of the work happens where there is no mobile signal.
What I built
I started the project and worked across the whole app. It is an offline-first web app (PWA): with no signal, it stores each task's start and end times on the device and syncs when the connection returns. With Supabase Realtime, managers see the moment a crew starts an activity. The crews' third-party safety-camera software is integrated into the app.
What changed
Around 500 field workers use the app, every field activity is now measured in real time, and safety and productivity are tracked in one place.
Built with: REACT · NEXT.JS · TYPESCRIPT · NODE.JS · SUPABASE · POSTGRESQL
View liveIs this a fit?
Worth a conversation if
- Your operation runs on spreadsheets and loose messages, and it has already cost you money.
- You want someone who understands the process before proposing screens.
- You need the system documented and handed over running, not a pretty prototype.
- The people who will use it aren't office staff — they're in the field, the shop or the floor.
Probably not me if
- You want a good-looking brochure site and nothing beyond that.
- You need a team of ten starting tomorrow.
- The deadline is non-negotiable and was set before anyone looked at the process.
Start a conversation
Tell me the problem, not the solution
The first conversation is about how the work happens today — what breaks, who works around it, and what it costs. If I'm not the right person for it, I'll say so and point you somewhere better.