# #0007 Roof Commander

> Which lead sources actually produce closed jobs?

- Kind: case study
- Status: Active
- Entity: GalaxyCo
- Role: Design, build, run
- Stack: Next.js, pnpm monorepo, Postgres, Vercel
- Started: Jul 2026
- Platform: web
- Production deploys since Sep 1: 7 (since Jul 10), read live from Vercel
- Last deploy: 27 h ago (2026-10-16T04:11:31.861Z)
- Live: https://roofcommander.ai
- In one line: Multi-tenant attribution with a tenant-facing agent. Every closed job traced to its source; unknown stays unknown, never redistributed.
- Page: https://daltoncox.com/jobs/roof-commander

## Context

Roofers buy leads from six places and cannot say which ones turn into closed jobs. Every vendor reports its own numbers.

## Role

Design, build, run, under GalaxyCo.

## Approach

Honest attribution. Show exactly which source produced which closed job and how much revenue. Unknown stays unknown and is never redistributed. That rule lives in the code.

## Solution

A multi-tenant platform: site, backend, and a tenant-facing agent named Homer. A homeowner portal is specced in five checkpoints.

## Result

Nine checkpoints complete. Tenant zero live.

## Learned

Name the rule that must stay true and write it at the top of every spec. Blind find-and-replace broke the build once; the naming rule stopped it from happening again.

*Clip, 7s: roofcommander.ai. Type a company name and the site preview rebuilds around it. No sales call. (https://daltoncox.com/clips/roof-commander.mp4)*

## Punch list (3 open)

- @rc/ui depth pass
- Homeowner portal CP-P1
- Twilio A2P registration