A residential real-estate team in northern Nevada · Real estate
Inspection dates on the calendar only after a yes.
An email pilot that drafts in the team’s voice and puts every inspection and contingency date up for approval before it reaches the calendar.
- Status
Scoped and proposed. Nothing on this page is a result.
- When
- Proposed August 2026
- Works inside
- Gmail · Google Calendar · Top Producer · Mailchimp · Claude
What is happening now.
Luxin, an AI consulting firm, built, is building, or proposed this work. The status above says which.
Two to three hours of typing per new escrow, split across the team.
Around 100 follow-up tasks every two days.
Weekly seller updates assembled by hand across up to 15 listings.
One missed inspection traced to a hand-typed calendar date.
The numbers, with what they mean.
- 2–3 hours
- of typing per new file, as the problem found
- The problem found
- ~100 tasks
- follow-ups every two days, as the problem found
- The problem found
- Up to 15
- listings covered by a hand-built weekly update
- The problem found
Every figure says where it came from. A problem found is not a result.
What is proposed.
- 01
An email pilot that reads the inbox on a schedule and drafts replies in the team’s own voice, into Drafts, never sent.
- 02
Inspection and contingency dates pulled out of the offer email and pushed to the calendar after approval.
- 03
A weekly learning loop that compares what was drafted with what was sent.
- 04
A full operating system proposed next: the escrow timeline, Monday expireds, seller updates and prospecting lists.
The tools it works inside.
Nothing goes out without you.
Dates reach the calendar only after the team approves the list. Replies are drafted, never sent. Their words: no client should ever feel an automated response.
Where this stands.
Proposed, not yet delivered. Nothing on this page is a result.
More case studies.
Bender Engineering
Read what happened: Bender EngineeringA San Jose law firm
Read what happened: A San Jose law firmThe operating system Luxin runs on
Read how it runs: The operating system Luxin runs on
Tell me what’s eating the most time.
Thirty minutes, no deck. You describe how the work actually happens, and I tell you plainly whether there is something worth building.