Well Kept
A mobile and web product for making scattered home information easier to capture, organize, and find.
The idea
A home accumulates a lot of information. The plumber’s number is in a text thread. The last repair is in an email. The warranty is somewhere in a drawer.
Well Kept explored a simple question: what if those scattered pieces could become a useful, ongoing record of the home?
What we built
A mobile app, a web interface, and a backend for structured home information. I directed the product decisions and the build and review process.
Homeowners could log services through conversation, upload documents, or forward invoices by email. The record brought together services, vendors, costs, warranties, and documents.
History, calendar, vendor, and Home Knowledge views made that information easier to find. TestFlight builds and feedback supported iteration.
Built with React Native and Expo, an Express/TypeScript API, and PostgreSQL. Claude Code, Codex, and Replit supported development.
Getting an empty state right
When the assistant had no recommendations, the screen made the home sound problem-free. We changed that message.
“Your home is in great shape.”
“No recommendations right now.”
No recommendations could mean there wasn’t enough information. It wasn’t proof that the home had no problems. The screen needed to say what the record actually supported.
The same principle shaped the Home Knowledge summary: show what’s in the record, and make uncertainty visible.
Why I moved on
Well Kept reached TestFlight, but I felt I’d taken it as far as I could with my technical knowledge and the AI tools available at the time.
Other well-funded companies were working on the same problem. That made the idea feel validated, but I didn’t feel ready to compete at that scale. I’d learned a lot from the project and decided to move on before a full public launch.