1000x an idea

MEMORANDUM

TO: Ruth, CEO FROM: Product Team DATE: October 24, 2023 SUBJECT: The 1000x Version of Shared Budgets (Ana’s Proposal)

*

1. The 1000x Version: Pocketbook as the Operating System for Shared Life

Right now, personal finance assumes an individual user in a quiet room looking at bar charts. But money doesn't live in a vacuum—it is the friction point of human relationships.

If we take Ana’s proposal to its logical, 1000x extreme, Pocketbook stops being an app for tracking your money and becomes the financial operating system for shared lives.

Today, couples use a fractured stack of tools to manage their shared reality: splitwise for dinner bills, spreadsheets for rent, Venmo for groceries, silent resentment for lifestyle inflation, and separate banking apps that don't talk to each other. It is exhausting.

The 1000x version of Pocketbook captures this entire surface area. We don't just "share a budget"—we remove the emotional labor of financial coordination. Imagine an ecosystem where: * The system auto-negotiates equity: It understands income differentials and automatically scales contributions to shared goals without manual math. * Micro-communication replaces macro-arguments: Financial friction is dissolved via contextual, inline micro-notes on transactions ("Bought your mom's gift early! ❤️"), turning spending alerts from panic triggers into connection points. * Organic household expansion: It scales naturally from couples to households (adding aging parents or kids) and handles life milestones (buying a home, taking a sabbatical, having a child) as collaborative multiplayer projects rather than administrative nightmares.

Look at our current data. It already whispers this truth: Solo users retain at 17% and convert to Premium at 4%. But Couples retain at 58% and convert at 19%. Households retain at 71% and convert at 31%.

Shared budgets are not just a feature request; they are our escape hatch from single-player churn. The 1000x version transforms Pocketbook from a utility you check once a week into the digital kitchen table where couples align their lives.

---

2. The Mechanism: Why This Spreads Exponentially

The engine of the 1000x version is relational virality.

Traditional personal finance apps have terrible organic loops because money is private and taboo. You don't text your friend a screenshot of your grocery budget.

Shared budgets invert this entirely. By definition, a budget for a couple requires an invitation. Our data proves this mechanism is already working: couples have a 100% invite rate because the product cannot function without the second person.

The compounding loop looks like this: 1. The Trigger: A couple experiences a shared-expense friction point (paying rent, booking a holiday) and one partner invites the other via Pocketbook. 2. The Dopamine Hit: The invitee joins, and within minutes, they receive their first real-time notification about shared financial momentum ("Alex spent $48 at the grocery store"). Engagement spikes immediately (couples open the app 11 times a month versus 4 for solo users). 3. The Cultural Artifact: They use the accidental "money talk" note feature (which 41% of couples adopt in month one). Money stops being a taboo source of anxiety and becomes a shared chat thread. 4. The Network Effect: As life expands, the network expands. 16% of couples naturally add a third person within a year—a teenager learning financial literacy or an aging parent they support.

We don't need expensive paid acquisition to scale this. Every shared budget creates an involuntary, high-intent acquisition channel for our highest-value segment.

---

3. What We Build First & How We Know It’s Working

To capture the 1000x vision without boiling the ocean next quarter, we must sequence our roadmap ruthlessly. We will not build complex multi-user permissioning or robo-advising out of the gate.

We build the "Shared-Expense Moment" onboarding flow.

Based on data showing that shared budgets originating from specific collaborative moments retain best, our Q1 MVP focuses exclusively on friction-free pairing around a single shared goal or expense: * Streamlined Invite-to-Split: Allow a user to instantly spin up a shared bucket for a specific vector (e.g., "Our Apartment" or "Japan Trip") and text an invite link that resolves in under 10 seconds. * First-Class "Money Talk" Notes: Elevate the transaction note feature from an afterthought into a core UI element. Make leaving a context note or emoji reaction on a partner’s transaction frictionless. * The Notification Loop: Tune real-time push notifications so they foster alignment rather than anxiety, capitalizing on the behavior that drives our 11x/month engagement.

#### How We’ll Know It’s Working (Metrics for Q1): 1. Viral Coefficient (K-factor) of Invites: We will track the percentage of new solo sign-ups who successfully dispatch a partner invite within 7 days, targeting a baseline of >25% conversion from solo to shared. 2. Day-30 Retention of Paired Users: We will measure whether our MVP couples maintain the elevated retention baseline (targeting >50% retained at 30 days, pacing toward our 58% 6-month benchmark). 3. Note Adoption Rate: We will track whether >40% of newly paired couples use the transaction note feature in their first 14 days, proving that we are successfully replacing financial stress with communication. 4. Free-to-Premium Conversion Lift: We will monitor if newly paired users convert to our $6/month Premium tier at rates mirroring our existing cohort (19%+).

Ana’s proposal isn't just a feature to check a box against our competitors. It is the architectural shift that transforms Pocketbook into an indispensable, sticky, multi-player platform. Let’s build it.

To: Ruth From: Product Subject: Shared budgets: from feature to household money layer

The 1000x version

Don’t just let two people see the same budget. Make Pocketbook the place a household coordinates money: what’s shared, who’s responsible, what changed, and what the group wants to do next.

The product could grow from couples splitting rent or groceries to families managing bills, parents helping teenagers, and adults supporting relatives. Each person would bring in only the accounts and spending they choose to share. The household could set shared budgets and goals, see relevant activity, and discuss a transaction in context—without giving up the ability to keep other finances private.

The bigger opportunity is a financial habit, not a shared spreadsheet. A change in spending prompts a timely heads-up; people can add context or a note; the household can agree on an adjustment and see whether it’s working. Over time, Pocketbook could help households plan around bills, goals, and cash flow. Premium could offer richer household planning and controls.

Why it could work

Shared budgets appear to be associated with much stronger engagement: six-month retention is 58% for couples sharing a budget and 71% for households of three or more, versus 17% for solo budgeters. Premium conversion is 19% and 31%, respectively, versus 4% for solo users. Couples open the app 11 days a month versus four for solo users; most of their sessions start with a notification about the other person’s spending. And 41% add a “money talk” note in their first month—even though notes were built as an afterthought.

That suggests a reinforcing loop: an expense creates a useful moment to coordinate; a notification brings the other person in; context and discussion make the budget more useful; shared progress gives the household a reason to return. An invite sent during a real shared-expense moment—such as rent or a holiday—is associated with the best retention. Some couples also add a third person later, pointing to expansion beyond two-person households.

These are promising signals, not proof that sharing causes better retention or conversion: people who choose to share may already be more engaged. And the 100% invite/join figures for shared-budget groups describe people already in those groups, not a general invite-funnel benchmark.

What we build first

Start with one use case: a couple coordinating a shared expense or budget. Let one person create a shared budget and invite their partner with a link. Each person explicitly chooses which accounts or spending to share. Both can see shared-budget activity, get configurable notifications, and add a note to a transaction. Keep personal spending private by default; make it clear who can see what and allow people to mute notifications or leave the shared budget.

We should make the invite flow work in the moment of need, rather than asking solo users to make a vague “invite your partner” decision. Don’t build full household roles, complex permissions, or automated financial advice yet. First learn whether shared visibility and lightweight conversation produce a lasting joint habit.

How we’ll know it’s working

Track the funnel from shared-budget creation to invite acceptance, both people viewing shared activity, and both taking a meaningful action (for example, reviewing a transaction, adding a note, or changing a budget). Our leading indicator should be jointly active shared budgets: both members take an action in the shared budget in at least three of the first four weeks.

Use a randomized offer or holdout among eligible solo users to test whether offering shared setup improves activation and subsequent retention—not just whether people who opt in retain well. Follow six-month retention and Premium conversion, comparing like-for-like users, while monitoring privacy complaints, notification mutes, and shared-budget exits as guardrails.

If the experiment lifts joint activity and retention without eroding trust, we’ve earned the next step: support more household members and more of the financial decisions they share.

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.