Product
Pitch In (pitchin.house)
Year
2026
Role
Founder, Product Designer & Developer
Status
Live, Open Sign-Up

Pitch In: One Household, Everyone Sees Their Part

I designed, built, and launched Pitch In, a multi-tenant SaaS where a household keeps its money, its bills, and its chores in one place, and everyone who lives there gets their own sign-in. It started as my own family’s budget app and is now live, open to anyone, with real households in it.

"One household. Everyone sees their part. The money, the bills and the chores in one place, and every person who lives there gets their own sign-in." Beside it, the demo household's dashboard in a browser, as Ana, a parent: two chores left today, $2,418.60 in checking, $5,838.00 forecast for the end of the month, and a $48.60 water bill overdue. In front, a phone shows the same day as Maya: her chores and no money.
"Same house, two views. A teenager can't pitch in on something they can't see. Ana sees the balance, what's overdue and the budget. Maya, 16, gets the same day and the same chores, and the money simply isn't there for her." Two phones side by side. Ana, parent, sees everything: checking balance, end-of-month forecast, the overdue bill and her chores. Maya, 16, sees chores and no money: soccer practice, feed Biscuit, tidy the living room, and chores up for grabs.
"Home. The day and the money, at a glance." The dashboard in light mode: a row of four figures (chores left, checking, end of the month, overdue), today's chores with some up for grabs, and the balance planner showing the lowest balance before payday.
"The house. Chores, the calendar, and whose turn it is." Today's chores in a browser, each with the person it belongs to, beside a phone showing the October calendar with today's chores listed under it.
"The money. Budget, bills and accounts, in light or dark." Three phones in light mode: the budget ($1,370 budgeted, $864.86 spent, spending by category), bills grouped by overdue, due this week and later, and accounts with net worth and a connected credit union.
"Bills and transactions. Every bill by its due date, and where the money went." Bills in a browser, grouped by overdue, due this week and later, each with a Paid button, beside a phone showing the month's transactions: $2,650 in, $864.86 out, and a day-by-day balance chart.
"Everything else a house runs on. Groceries, wishes to vote on, the car." Three phones: the shared grocery list with who asked for each item, Horizon, where the household votes on wishes like a trampoline or a weekend in Chicago, and vehicles with registration and oil change dates.
"People. Who sees the money is a setting for each person. Enforced in the database, so a screen that forgets to ask who is looking still can't show it." The household's members page: Ana is the owner and Luis an admin, both seeing all the money. Maya is a member with no money, only chores and people.
"One household. Everyone sees their part." The demo household's home screen on a phone, as Ana, a parent: two chores left today, $2,418.60 in checking, $5,838.00 forecast for the end of the month, and a $48.60 water bill overdue.
"Ana sees the money. Maya, 16, sees her chores." Two overlapping phones: Ana's home screen with balances and the overdue bill, and Maya's with today's chores and no money at all.
"Home. The day and the money, at a glance." The home screen in light mode: chores left, checking balance, end-of-month forecast, the overdue bill, and today's chores.
"The house. Chores, and whose turn it is." Today's chores on a phone, each with the person it belongs to.
"The house. One calendar for everyone." The October calendar on a phone, with today's chores listed under it.
"The money. Budget, in light or dark." The budget in light mode: $1,370 budgeted, $864.86 spent, $505.14 left, and spending by category.
"The money. Every bill, and what's left after." Bills grouped by overdue, due this week and later, each with a Paid button.
"Everything else. Wishes the house votes on." Horizon on a phone: $2,850 of wishes on the list, and a trampoline and a weekend in Chicago waiting for votes.
"People. Who sees the money is a setting for each person." The members page: Ana and Luis see all the money; Maya, 16, sees chores and people only.

The Challenge

Household money apps like YNAB, Monarch, and Copilot are built for the one person who does the books. Kids’ allowance apps like Greenlight and GoHenry are built around a debit card and treat the child as the whole account. Nobody serves both halves of the same house.

That gap is widest in a household with teenagers. They are old enough to do chores that matter and hold money of their own, but not old enough to be shown the mortgage. The product had to make a shared household ledger safe to hand to a 15-year-old, and it had to go from one family to many without breaking the app my own family relies on every day.

The Approach

Prove it at home, then generalize. I kept two codebases on purpose. The family app stays single-household and fast-moving, and features get proven there with real bills and real chores before they're ported into Pitch In. A written working agreement between the two repos keeps ideas flowing one way, so what ships in the product has already been used for real.

Per-member visibility, enforced in the database. A parent sees every balance and every bill. A teenager might see their chores and nothing else, or spending without balances, or one shared account. A withheld account isn’t blurred or shown as zero. It simply isn’t there, and it drops out of their totals. That rule is enforced in the data layer, so a screen that forgets to ask “who is looking?” doesn’t compile.

A real SaaS foundation. Each household's data is isolated with Postgres row-level security, under a restricted database role that can’t bypass it. On top of that sit email and Google sign-in, two-factor with trusted devices, invitations, roles, and multi-household membership (for separated co-parents and adult kids helping a parent). There's also an operator console for access requests and announcements, and versioned legal consent recorded from day one.

Designed like a product, not a project. Pitch In has its own brand book, a logo generated from parameters so it never drifts between files, and a type system where monospace is reserved for money. The landing page puts a parent’s view next to a teenager’s because that comparison is the product. A no-account demo household lets anyone try it, and the app installs to a phone with push notifications.

The Results

Pitch In is live at pitchin.house with open sign-up and real households using it. Everything a household types in is free, and the paid Connected plan, $10 a month per household, fills itself in from the household’s bank. Brand, product design, front end, back end, infrastructure, billing, and legal were all delivered end to end by one person.

It runs on a Next.js and TypeScript monorepo on Vercel, with Postgres on Neon and Better Auth, and it has no analytics, no tracking, and no ads. Next up is the bridge between chores and money: chores that earn an allowance. It's a ledger, not a bank, so the product records what was earned and never holds anyone’s money. The near-term goal is ten families who would be annoyed if it disappeared.

Have a house full of people who all pitch in? Create your household, or read the story behind it in From Our Family’s Budget App to a Product.

End to End
Brand, Design & Build
Multi-Tenant
Postgres Row-Level Security
Live
Open Sign-Up at pitchin.house
Next Project
Corewell Health
→