Valentine's Day, but for shipping
Day 2 was Dwellsmith day. Dwellsmith is our answer to the question: "Why is running a household so much invisible work, and why does nobody build software for it?"
The answer to the second part is that it's a terrible business. We're building it anyway.
What we shipped
Dwellsmith web app, live. The core app went into early access. It tracks household tasks, maintenance schedules, and the kind of unglamorous work that keeps a home running — HVAC filter changes, gutter cleaning, appliance warranty tracking. The stuff that lives in someone's head (usually one specific someone's head) until something breaks.
13-tool MCP server. We expanded our MCP implementation to 13 tools. You can now create tasks, set schedules, query upcoming maintenance, log completed work, manage household members, and more — all through the Model Context Protocol. This means any AI agent that speaks MCP can interact with your Dwellsmith data.
Marketing site at dwellsmith.com. Designed and deployed in about 4 hours. Work Sans font, clean layout, explains what the product does without buzzwords. We're trying to talk about household management without making it sound either trivial or like a productivity-bro optimization exercise.
iOS app, first build. Jonathan got the first iOS build running on a physical device. It's rough — mostly a web view wrapper with native notifications — but it exists. Household reminders that buzz your phone are table stakes for this category.
What went wrong
We underestimated the data model complexity for recurring tasks. "Clean the gutters every 6 months" sounds simple until you need to handle: skipped occurrences, variable schedules by season, completion by different household members, and the difference between "due" and "overdue" (which is a philosophical question, apparently).
The MCP server had an auth bug that let unauthenticated requests through for about 20 minutes. Nobody was using it yet, but still — not great. Fixed with a middleware check and added integration tests.
The iOS build crashed on launch three times before we found a missing entitlement. Classic.
By the numbers
- 120 commits across 8 repositories
- 1 web app launched (early access)
- 13 MCP tools implemented
- 1 marketing site deployed
- 1 iOS first build (crashy but alive)
- 20 minutes of accidental unauthenticated API access (0 exploits, ∞ lessons)
What it means
Two products are now live. That's the thesis at work — instead of going deep on one product for 18 months, we're shipping a portfolio. Some will work. Some won't. But we're learning fast about what it takes to go from zero to live in a day.