1000x an idea

Memo: Shared budgets, the 1000x version

To: Ruth | From: Product | Re: Ana's shared-budgets proposal

The short version

The big opportunity isn't a "share a budget" setting. It's turning Pocketbook from a tool one person uses alone into the place a household runs its money and talks about it. Our current users already show this. People who share a budget are 14% of our users. They account for about 36% of users still with us at six months and about 45% of Premium subscribers.

The 1000x version

Every household's money runs through Pocketbook: couples first, then the teenager, the parent you support, the roommates, the trip group. Each group recruits its next member at the moment money is shared. We stop selling budgeting discipline to individuals and become the shared ledger and conversation for the people you split life with. The business model becomes a household plan, not a per-person subscription.

The growth engine is the key difference. Solo budgeting apps grow one user at a time through marketing. A household product grows through its members. Each shared rent payment, holiday or new dependent is a chance to recruit someone.

The mechanism: three loops

1. The other person is the reason to open the app. Couples open Pocketbook 11 days a month, against 4 for solo users. Most of those sessions start from a notification about the partner's spending ("Alex spent $48 at the grocery store"). Solo budgeting runs on willpower, which fades. Shared budgeting runs on another person, who keeps giving you reasons to open the app.

2. The product is the money conversation. 41% of couples add a "money talk" note to a transaction in their first month. They do this even though notes were an afterthought. Couples are using us to talk about money, not just to track it. Talk is the habit that holds a household together.

3. Groups grow, and they start at shared-expense moments. 16% of couples add a third person within a year, and households retain best of all (71%). Shared budgets that start from an invite link during rent or a holiday retain best.

Today the growth loop barely works. 3% of solo users invite someone, and 22% of those invitees join. That's under 1 new member per 100 solo users. This is the biggest lever we have.

What could make this wrong

The numbers above are not proof that sharing causes retention. Couples who found today's sharing are self-selected: committed, organised, probably already engaged. The 100% invite and join rates for shared groups are true by definition, not a result.

The real question is whether a solo user nudged into sharing starts behaving like today's couples (58% retention) or stays like a solo user (17%). The plan below is built to answer that.

We also need to confirm how the 19% and 31% Premium rates are counted, per person or per budget, before designing any household pricing.

What we build first (next quarter)

Couples only. We build three things, aimed at the moments the data says matter:

1. "Share this" on a transaction or bill. Rent, a trip, a big purchase each generate an invite link that opens straight into a shared budget. This targets the entry point that retains best, instead of a buried settings page.
2. Partner activity notifications, on by default. Users get simple controls over what their partner sees, for example categories only or purchases over $X. Privacy is a real risk in couples' money; getting the defaults wrong will cause harm and generate support tickets.
3. Notes upgraded to replies on transactions. This turns the afterthought into a lightweight conversation thread.

Not this quarter: - 3+ person households - Roommate or trip groups - Household pricing

These come only if the couples loop proves causal.

How we'll know it's working

We'll run a holdout: a random slice of solo users who don't see the new invite prompts. That lets us measure impact rather than selection.

Leading indicators (readable within the quarter):

Lagging indicators (we'll have early reads; full answer after the quarter): - 3-month retention of new couples against the holdout, as an early read. 6-month retention against the holdout as the verdict. - Premium conversion of new couples against the holdout.

Decision rule: We commit to the household roadmap if both of these hold: - Couples formed through the new flows retain at least twice as well as the holdout at 3 months. - They are active more than 8 days a month.

If they look like solo users, we've learned the uplift is mostly selection. In that case shared budgets stay a solid retention feature for people who already want it, not a growth strategy. That is still worth shipping, but it's a 2x, not a 1000x.

The ask: One quarter for one squad to build the three couples features and the holdout. The household decision goes on the next planning cycle, made on real evidence.

Memo: Shared Budgets, the 1000x Case and a First Build

To: Ruth From: PM, Pocketbook Re: Ana's shared-budget proposal

Recommendation

Commit next quarter to shared budgets, scoped as a household product rather than a feature. Start with the invite and the partner-activity loop, and hold the wider household roles until the couple data holds up.

The 1000x version

Today, Pocketbook is a product for one person. Shared budgets make the household the unit. The 1000x version is a household financial operating system: the place a couple, and eventually a family, runs its shared money. That covers bills, spending, savings goals, allowances for teens, and money support for a parent.

The scale argument rests on what the data already shows:

• Couples are worth far more per user. Couples retain at 58% at six months against 17% for solo users. Their premium conversion is 19% against 4%.
• Shared users are 14% of our base and about 45% of premium revenue. Our 24,600 couples and 3,900 households produce roughly $35k a month in premium revenue. Our 182,000 solo users produce about $44k.
• The invite is the bottleneck, not the product. Solo users invite at 3%, but 22% of invitees join. Most people who would share have never been asked.

If couples alone reached 1000x today's count (about 24.6M couples) and kept today's 19% conversion, that would be roughly 4.7M premium users, or about $28M a month. Conversion won't hold at that scale, so treat this as an upper bound. The point is the shape: one shared budget brings in two daily users and a higher-value subscription. Households add a third person, which the data suggests happens for 16% of couples within a year.

The mechanism

Three loops drive it.

1. Notification pull. Couples open the app on 11 days a month, against 4 for solo users. Most sessions start from a message about a partner's spending ("Alex spent $48 at the grocery store"). Each shared budget creates a second daily user who is pulled back by the other person's activity.

1. Conversation as the product. 41% of couples add a "money talk" note to a transaction in their first month. The note was an afterthought, but it is the behavior that most resembles what the product is for: couples discussing money inside the app. Making it a first-class feature deepens the habit.

1. Expansion through real life. Couples who add a third person (a teenager, a parent they support) move from a two-person budget to a household budget. Households retain at 71% and convert at 31%. Each expansion raises value per account.

The invite is the entry point. Shared budgets started from a shared-expense moment, such as rent or a holiday, retain best. The invite should appear at the moment money is actually shared, not as a generic "invite your partner" button.

What we build first

1. An invite anchored to a shared-expense moment. When a user sets up a recurring shared bill (rent, utilities) or tags a transaction as shared, offer to bring in the partner. This targets the 3% invite rate directly.

2. Partner-activity notifications, with controls. The data says these drive sessions. Ship them with clear, per-transaction hiding and easy unsharing from day one.

3. Promote the money-talk note. Make notes on transactions a visible, first-class part of a shared budget.

Deliberately deferred: third-person and household roles, teen allowances, and parent-support flows. We should build these only once the couple version shows retention holding up.

Guardrails. A product where one partner can see the other's spending creates real risk, including financial control in abusive relationships. Before launch we need: - Opt-in visibility, with each person able to hide transactions from the other. - Unsharing that is easy and fully private, with no notice to the partner. - A separate review of defaults and copy with the trust and safety team.

How we'll know it's working

Set baselines now, and measure against cohorts rather than the current group averages.

Caveat on the data. The invited-someone and invitee-joined columns read 100% for the couple and household groups. That is true by definition, since these groups only exist because someone invited a partner. The real comparison is the solo invite rate (3%) against the join rate (22%). The 58% and 71% retention figures may also overstate the effect of shared budgets: couples who stay together may be the ones who stick with the app. We need a randomized holdout, with invited and non-invited users matched on tenure and activity, before we credit the product for that retention.

Kill or rethink criteria. If invites don't lift past 4% within the quarter, or if new-couple retention doesn't separate from the holdout, we stop expanding the feature and keep the notifications and notes as solo-plus-partner improvements.

From shared budgets to the household money network

To: Ruth From: Product Decision: Invest next quarter in testing shared money coordination—not simply adding a second user to a budget.

The 1000x version

Pocketbook becomes the place people manage money with everyone whose financial life touches theirs.

Start with a couple managing groceries and rent. Expand to saving for a home, giving a teenager spending autonomy, supporting a parent, and coordinating expenses across a blended family. One person can belong to several private money circles without exposing their entire financial life.

Today, Pocketbook answers: “Where did my money go?” The ambitious version answers: “What can we afford together, what have we agreed to, and what happens next?” It becomes a durable coordination layer above individual bank accounts—not a joint bank account and not a public financial social network.

That expands both our acquisition model and our reason to exist. Each shared obligation can introduce another person; each new life stage can create another circle. We stop rebuilding an individual’s budgeting habit from scratch and become part of an ongoing relationship.

This could support a materially larger subscription business. For scale, one million users converting at the observed couples rate of 19% would represent $13.7 million in annualized subscription revenue at $6/month. That is an illustration, not a forecast: we have neither established a million-user market nor shown that sharing causes that conversion rate.

Why it could work

Our strongest signal is not feature-request volume. It is that shared budgeting appears to change the product’s underlying behavior loop.

Couples also open Pocketbook on 11 days per month versus four for solo users. Most sessions start with a notification about a partner’s spending. And 41% add a “money talk” note during their first month—even though notes were an afterthought.

The mechanism is coordination:

1. A real obligation creates an invitation. Rent or a holiday provides a concrete reason to join. These shared-expense entry points already retain best.
2. Shared activity creates useful context. A transaction changes what remains available to both people.
3. Context creates a conversation or decision. A note resolves uncertainty; a budget adjustment records the agreement.
4. Repeated decisions create shared history. Pocketbook becomes more useful as a relationship’s financial memory accumulates.
5. New responsibilities extend the network. Sixteen percent of couples add a third person within a year.

This is a local network effect: the product improves when the right person joins, not when everyone joins.

But the evidence is observational. Existing sharers may be unusually motivated or financially organized. The groups’ 100% invitation and join rates largely reflect who qualifies as a sharer; they are not evidence of a frictionless funnel. We must test whether we can create the behavior, not merely identify people who already have it.

What we build first

A private, two-person shared-expense circle, launched around one immediate obligation.

Next quarter’s experience:

• Create a circle for rent, groceries, or a trip; set an amount and timeframe.
• Invite a partner through a link that explains the purpose and exactly what will be visible.
• Let the partner join without first connecting a bank account.
• Explicitly select transactions to share; keep all other accounts and spending private.
• Show the shared amount remaining and support transaction-level notes.
• Offer controllable activity notifications and a lightweight weekly check-in.
• Make leaving, revoking access, and handling shared history understandable.

We should build on existing sharing and notes rather than launch an entirely separate product. We should not begin with payments, joint accounts, complex household roles, or automated financial advice.

Trust is part of the mechanism. Unwanted visibility can turn coordination into surveillance. Privacy controls and notification consent are launch requirements, not follow-up polish.

How we know it is working

Randomize eligible solo users, before they invite anyone, into the new shared-expense journey or today’s experience. Keep each resulting circle in one experiment arm. Analyze outcomes per assigned initiator, not only among successful sharers.

Primary near-term outcome: incremental eight-week retained coordinators—initiators whose circle has both people active and a meaningful shared-budget action in weeks seven or eight.

Track the full mechanism: invitation sent → partner joins → both contribute → first note or budget decision → repeated coordination. Notification opens alone do not count as success.

Also measure net additional retained invitees, Premium conversion, and support costs. Guardrails include privacy complaints, unwanted notifications, partner exits, and any reduction in initiators’ overall retention.

Set the minimum worthwhile lift and required sample size before launch using baseline rates and implementation costs. Scale only with credible retention improvement, healthy guardrails, and evidence that both partners get value. Maintain a holdout for six-month retention and monetization.

The bet is not that two people need one spreadsheet. It is that shared financial decisions can become Pocketbook’s acquisition engine, daily utility, and long-term moat.