01 · Story
Why I built Homsy.
The idea started while reading an article that mentioned a home-maintenance task in passing. It made me realize I had no idea how often that task should happen, or what else around my house I might be missing.
The information existed, but it was scattered across articles, manuals, regulations, supplier recommendations, old emails, and other people's memories. Coordinating individual suppliers for every part of the house was its own separate frustration.
A second motivation ran alongside it: understanding AI-assisted product development by completing the whole loop: idea → research → product definition → UX → architecture → implementation → testing → deployment → users. AI shortened the distance from idea to working prototype; I still owned the product judgment and every final call.
“What if I could describe my house once and receive a practical maintenance plan showing what needs attention and when?”
The first prototype was intentionally small
Describe the house and its equipment
Generate a maintenance plan
Add it to a calendar
Receive reminders
Where this could go next
Talking to other homeowners showed me the friction wasn't only mine. These ideas came out of it. They are hypotheses, and none has shipped.
- Ready-to-send supplier communication
- Automatic follow-ups on outstanding requests
- Recurring service workflows
- Grouped requests across similar homes
- Coordination between nearby homeowners
- Better supplier pricing through aggregated demand

Welcome
Thinking
Checklist
Technician
Success
Email
Reminder