Skip to content

House Manager — PARKED

Original idea: Shared shopping list with your spouse, household bills (rent/ZESA/DSTV/WiFi/maid) with reminders and who-paid tracking, and a weekly meal plan.
Rank: 2 of 5. Score: 6.05.
Verdict: Do not build. It's a feature, not a company. Reopen if: Car Care reaches 2,000 active households and a household module becomes a genuine retention play.


1. Why it looks good

It scores 9 on market size and 9 on buildability. Every urban household has these problems. The founder lives it personally, which means validation would be fast and the details would be right.

And the pain is genuinely real:

  • Shared shopping list that syncs — "she adds tomatoes, you see it at OK"
  • Bills that are easy to forget and awkward to divide — ZESA, DSTV, WiFi, rent, domestic worker pay
  • The daily "what are we eating?" decision loop
  • Couples disagreeing about money and chores

None of that is imagined. It's just not defensible.


2. Why it loses

The competitor isn't an app — it's WhatsApp and a notebook

What the household needs What they already use Is it good enough?
Shared shopping list WhatsApp message, or a shared note Yes. Zero install, zero learning curve, everyone already has it
Bill reminders Phone calendar, or remembering Almost — this is the weakest link
Who paid what Memory, or a notebook Almost
Meal plan Habit, or asking Yes

The gap is real but narrow: it's the bill reminder and who-paid ledger, not the shopping list. And that gap is a single feature, not a product.

The global competition is free and polished

App What it does Cost
AnyList Shared lists, recipes, meal planning Free + optional premium
OurGroceries Shared shopping lists Free
Spondle Family/household management Free
NestSync Family budget and household Free
Splitwise Shared expense tracking Free
Google Keep / Apple Notes Shared checklists Free, pre-installed

A Zimbabwean household that wanted a shared list could install AnyList today. They don't, because WhatsApp already works.

Willingness to pay is the killer

Segment Would they pay US$1/month? Evidence
Consumers No Established pattern; free alternatives; recurring debits disliked
Businesses Who? There is no business on the other side of a household shopping list

This is the structural problem. In Car Care, there's a garage that gains a customer and will pay US$3–40. In House Manager, there's a supermarket that gains nothing from your list — they already have your foot traffic. There is no payer.

The monetisation path in monetise.md doesn't hold

monetise.md suggested freemium for this idea: free basic list, US$1/month or US$8/year for family sharing and no ads. The flaw: family sharing is the core value, not a premium add-on. Gating it means the free tier doesn't deliver the product's reason to exist, so nobody experiences enough value to upgrade. And ads on a household list app earn almost nothing at this scale.


3. What would actually make it work

If someone insisted on building this, there are only two viable shapes. Neither is obviously worth the effort.

Shape A — Bill-payment infrastructure, not an app

Stop building a household organiser and build a bill aggregation and payment layer: one place to see and pay ZESA, DSTV, WiFi, rent, and school fees, with a shared household ledger on top.

Why better Why still hard
Revenue comes from billers (integration/collection fees), not consumers Requires biller integrations and a payments licence or partner
Solves the real gap — the payment, not the list Heavy regulatory and partnership work
Defensible through integrations Competes with EcoCash, banks, and every biller's own portal

This is a fintech company, not a household app. It's bigger and harder than Car Care, with more regulatory exposure.

Shape B — Domestic worker and landlord management

A narrow tool for households with domestic workers and/or tenants: pay tracking, leave days, rent received, maintenance requests. There is a real payer (landlords) and a real compliance angle (employment records).

Why better Why still hard
A landlord with 3 properties has a real problem and money Small market in Harare; long sales cycle; informal
Compliance angle creates a reason to record Employment law compliance for domestic workers is poorly enforced
Not competing with free global apps Niche enough to be ignored by them

Still a small business, and a harder one to sell than Car Care.


4. Revival criteria

Reopen only if all of the following hold:

  1. Car Care has reached 2,000 active users with proven retention.
  2. A household module can reuse the existing account, payment relationship, and notification infrastructure — i.e. it's a feature, not a new product.
  3. There's evidence users want it inside the Car Care app (e.g. repeated requests, or a natural adjacency such as household vehicle + household budget).

What it would look like then: not a separate app. A "Household" tab inside Mota for shared expenses that already relate to the vehicle (fuel, service, insurance, licence) — expanding to household bills only if the vehicle-expense version gets used. That's a wedge, and it's built on an audience that already exists.

What it should never look like: a standalone House Manager app competing with WhatsApp and free global products for a market with no payer.


5. The transferable lesson

"I would use this" is not the same as "someone would pay for this."

This idea has the highest founder-market fit in the set and the lowest willingness-to-pay. That combination is the most dangerous kind, because it feels right. You build it, you use it, your spouse uses it, and it still makes zero revenue because the value lands on the consumer side of a market where consumers don't pay for software.

The test that would have caught this earlier:

Who is the payer, and what do they get that they can't get for free?

For Car Care: the garage gets customers it can't otherwise identify. There is no free alternative that does this, because global apps can't monetise a Harare garage.

For House Manager: nobody. The answer is nobody.

Apply that question to every future idea before writing a line of code.