Design work starts long before a client calls
Hungerford is an interior design firm. Its best leads show up early, in places nobody has time to watch: a building permit filed at the city, a listing that will need a designer once it sells. By the time a client calls, the work is often already promised to someone else.
Five surfaces on one database
- Listing scout. It reads realtor listings and keeps the ones that signal design work.
- Permit leads. It watches municipal building permits, an early sign of renovation and design work.
- Outreach drafts. For each realtor worth contacting, the system drafts a first message, and a person edits and sends it.
- Content suggestions. It reads industry content and suggests what the firm could publish.
- Portal messaging. The firm and its clients talk in one portal instead of scattered threads.
Underneath sits an execution layer of 24 Python scripts on a schedule, including the scrapers that watch permits and listings and enrich what they find. The system drafts and suggests. A person sends every message and sets every rule.
A custom front end, one database, scheduled scripts
The front end is React and Vite, written for the firm's own way of working. Supabase holds the data on one instance for this engagement and no other. Railway runs the scripts on their schedules. Claude does the language work: reading listings and permits, and drafting the outreach.
The engagement has ended.