1000x an idea

To: Marcus Webb and Executive Team From: Staff PM, Tally Subject: The 1000x opportunity is the worker network—not a broader AI suite

Recommendation

The mechanism that could make Kenji’s tip-out calculator much bigger is a worker-mediated cross-side network effect. A restaurant makes Tally more useful to its workers; those workers can bring Tally to their other restaurants. The one dimension to push is portable worker identity across employers, with worker consent.

The data supports this wedge: 41% of workers at beta restaurants also work elsewhere; 29% of surveyed workers had asked another job to use Tally; and 57 restaurants signed up after a worker asked. Those deals closed in nine days on average, with about one-third the sales effort per deal. That is evidence of a distribution loop—not yet proof it scales across our whole base.

The ambitious version and its opportunity

Build a worker account that follows someone across Tally restaurants. At each job, the worker can see that night’s tips and pay, and—where tips have already been earned—choose to receive them that night. The restaurant still owns its employment and tip records; workers control which jobs they link and what they share. Their use of Tally can also introduce it to their next employer. Over time, that gives Tally a worker-led route into restaurants and a trusted layer for earnings across jobs.

The available data gives us a directional opportunity size for payouts, not a complete market forecast. If the survey’s 44% who said they would pay for instant tip payout held across our 190,000 worker-app users, that would be about 84,000 interested workers. At one payout per month to one per week, and $0.60 retained by Tally per payout, that implies roughly $0.6M–$2.6M in annual payout revenue at full adoption of stated interest. This excludes costs beyond the partner fee and assumes both survey intent and the current user base translate into eligible, paying use. It is not a forecast. The 57 worker-referred restaurant signups are a separate, promising acquisition signal; we should not extrapolate that beta result to all 6,400 restaurants yet.

Build sequence: two squads, one quarter

1. Establish the worker link and the earned-tip foundation. - Squad A: Build consent-based linking of accounts across restaurants, including clear controls for unlinking and keeping employers’ records separate. - Squad B: Build the earned-tip ledger and same-night payout flow using the existing payments partner. Pay only tips the worker has already earned. Do not build advances: they require licences in three of our five largest states, and Compliance estimates nine to twelve months to obtain them.

Gate to pilot: Compliance confirms the flow is limited to earned wages and works in pilot states; linked-account consent is understandable and reliable; and workers can see the fee and payout terms before opting in.

2. Run a controlled pilot with beta restaurants. Test linking, payout choice, repeat use, support burden, and whether workers actually invite other employers. The calculator remains the tip-data entry point; do not widen into unrelated restaurant workflows.

Gate to invest in the network loop: We see meaningful cross-job linking and repeat payout use, positive retained revenue after operating costs, and worker-driven restaurant interest outside the original beta cohort. Set exact thresholds with Finance and Data before launch; treat survey intent as a hypothesis, not a target.

3. Scale only what the pilot proves. If those conditions hold, invest in making worker referrals a repeatable onboarding channel and bring more restaurants onto the calculator and payout flow. Expand state coverage only as compliance allows. Broader earnings tools come later, if workers demonstrate demand.

Stop result: If, after an eight-week pilot, fewer than 10% of eligible workers link another job or repeat payout use is negligible—and worker referrals do not extend beyond the beta cohort—stop building the cross-employer network. Keep the calculator as a useful restaurant feature and reassess payout demand; do not justify further investment with survey intent alone.

What to do with Marcus’s idea

Keep “Tally helps restaurants make better decisions” as a long-term ambition, but do not staff an AI operating system across inventory, pricing, marketing, and reservations next quarter. That scope has no support in this pack and would dilute the one mechanism we do have evidence for. First earn a trusted position in tip operations and worker earnings. Revisit AI decision support when we have a specific operator problem, relevant data, and evidence customers will use it.