← Selected work

Personal build · Small-business operations

A real-estate transaction command center built around the work a broker tool leaves behind.

My wife is a real-estate agent, and the tools supplied by her broker did not make the day-to-day work easier to organize. I built a web and mobile transaction-management system around the clients, properties, deadlines, files, tasks, reminders, commissions, expenses, and vendors she actually needs to run the business.

Role
Creator and product engineer
Context
Real-estate transaction management
Disclosure
Personal project for my wife’s business

The problem

The problem

Broker-provided software tries to serve every agent and every workflow, which can leave an individual agent with more places to look but less clarity about what to do next. The problem was not a lack of software; it was translating a real-estate transaction—from first relationship through escrow and close—into a small, reliable system that fit the way one person works on a laptop and away from it.

What I built

The system, not just the screen.

A transaction record that holds the actual deal

Built connected client, property, listing, sale, contact, file, and expense records. A property can carry escrow dates, inspection, appraisal, and loan contingencies, the people involved, documents, and the commission inputs and outputs that matter at close.

The work between opening and closing, made repeatable

Added task templates, relative due dates, reminders, and a transaction calendar. Instead of rebuilding a checklist for every deal, the app can create the operating work around a property milestone, then surface it in the calendar and an iCalendar subscription.

A companion app for when the desk is not nearby

Built an Expo mobile app against the same authenticated API, with client and property access, notes, contacts, tasks, files, expenses, calendar, vendors, and commission calculations. It persists its query data locally and registers for push notifications, so the operating system travels with the agent rather than being trapped in a browser.

System sketch

How the system works.

A simplified view of the system boundary and the work it moves through.

  1. Client + property
  2. Sale details + documents
  3. Template-driven tasks
  4. Calendar + mobile reminders
  5. Commission + vendor context

Key decisions

Key decisions

  1. Start with the agent’s repeated decisions and follow-ups, not a feature checklist borrowed from a brokerage CRM.
  2. Keep client, property, and transaction details connected while making each record simple enough to update during a busy day.
  3. Make deadlines first-class: escrow, contingencies, reusable task templates, calendar subscriptions, and push reminders all serve the same need to stay ahead of the deal.
  4. Put commission, expense, vendor, and document context inside the transaction workflow instead of treating them as separate spreadsheets or tools.

What it enables

What it enables

The result is a private operational home for a real-estate business that works on the web and on the go: less time reconstructing a transaction, clearer follow-through around every deadline, and more of the broker software’s complexity left out on purpose.

Return to selected work

Similar problem?

Facing a similar kind of product or systems problem?

Tell me where the complexity is piling up. If there’s a strong fit, I’ll reply personally.

A few sentences is plenty.

Your note goes straight to me—no mailing list.