Rebuild Relief Website

Rebuild Relief manage hail and storm damage insurance claims for homeowners across Queensland. The site has to do two jobs that pull in different directions: explain a claims process plainly to someone whose roof has just been hit, and feed qualified enquiries into the team that books the inspection.

The rebuild runs on Astro with Supabase behind it, so the marketing pages ship as static HTML while the enquiry flow writes into the systems the office already works in. Lead capture connects through to the CRM, and the hail map gives both the public and the office a view of where claims are clustering after an event.

It sits inside a wider estate rather than standing alone — eight applications built for the same business, from crew scheduling through to a damage estimator carrying over 6,000 geocoded claims.

How it came together.

The work moves from the right question to a system the team can actually use.

1. 01

   Strategy

   It starts with a strategy session — I come to you, learn the business inside out, and shape a plan you actually want and that actually works. Goals first, never template-first.

2. 02

   Design

   Then I design it — interface, brand and the feel of using it — mapped straight to that strategy. One person, one vision, no handoff gap between designer and developer.

3. 03

   Development

   I build the real thing: fast, typed end-to-end, Supabase-backed, and yours outright — the website and the operations behind it, shipped on a tight loop.

4. 04

   Iteration

   We iterate on the live product — real usage, real numbers — tightening the funnel and the workflows until it genuinely performs.

5. 05

   Handed over — run in-house

   Then I hand over the keys: the team runs and grows it themselves, fully in-house, with the admin dashboard and docs to do it confidently. Honestly my favourite outcome — a business that owns and drives its own tools.

Role

Full-stack rebuild & brand

Year

2026

Client

Rebuild Relief