WATAhub

Shutdown contractors staff hundreds of trades for windows of a few days, mostly through spreadsheets, phone calls and recruiter inboxes. I live that problem from the planning side every rotation.

Crewing a shutdown is slow, opaque and error-prone. Planners lack a live view of who is available, qualified and mobilised, and workers lack a clear pipeline into the next job.

1. 01Framed the problem from first-hand planner pain on site.
2. 02Defined a narrow MVP around availability, qualifications and mobilisation status instead of a full HR suite.
3. 03Two-sided product: workers keep documents and availability current; recruiters see who is available over their dates and track every candidate to site.
4. 04Recruiter dashboard with a Kanban pipeline, compliance checklists and mission changes (withdrawals, rescheduling).
5. 05Built and iterated quickly with AI-assisted tooling on React and Supabase to keep build cost low and learning speed high.
6. 06Running user testing to prioritise the roadmap.

• MVP live at watahub.au and in user testing.
• End-to-end ownership: discovery, positioning, product scope, build, go-to-market.