Buyer Boards

The problem

Evaluating a home purchase mixes listings, mortgage assumptions, commute times, schools, and personal filters. Spreadsheets and browser tabs make it hard to compare options or share a clear board with someone helping on the search.

The solution

I built a buyer board that pulls in listing info, adds maps/schools/drive times, and surfaces payment math so decisions sit on numbers and constraints, with an architecture path from a personal board toward multi-tenant brokerage workspaces.

Technical execution

• Next.js with TypeScript domain logic for payment modeling, filters, and listing enrichment.
• Listing ingest via URL paste / multi-source enrichment and Redfin CSV import, with background enrichment for photos, tax/insurance context, and school location.
• Geo and commute context using maps and drive-time tooling; school district and county layers for market context.
• Neon Postgres behind a data adapter layer, with a documented path to organizations → boards → listings when productizing beyond one household.
• Kept gated: personal search details and enrichment cost mean it is not open for random public use.

Why it matters

Turns a stressful personal workflow into a clearer decision tool, and shows how something built for one household can grow into a product shape without pretending multi-tenant brokerage features are finished.