1000x an idea

To: Marcus Webb and the executive team From: Staff Product Subject: The 1000x bet is a worker-led network, not a broader restaurant suite

Recommendation

Make Tally the portable home for restaurant workers’ shifts, tips, and earned-tip payouts—and use workers’ movement between jobs to distribute Tally to restaurants.

The mechanism in our data is cross-employer distribution: a useful nightly tip experience gives workers a reason to return, and workers carry that experience to another employer. I would push one dimension: the number of workplaces reached by each active worker, not the number of owner workflows we cover.

The calculator saves managers 25 minutes a night. That is a good feature. The potentially much larger business is underneath it:

• Worker-app weekly activity rose from 34% to 81%.
• 41% of beta workers also work at another restaurant.
• 57 restaurants signed after a worker asked them to adopt Tally.
• Those deals closed in nine days versus our usual 41, with roughly one-third the sales spend.

This is evidence of a distribution advantage, not yet proof of a compounding network. The beta restaurants volunteered, and we have no control group.

The most ambitious version

A worker has one consent-linked Tally identity across jobs. At close, they see a trustworthy breakdown of tips they have earned and can receive those tips that night. When another workplace is missing, they can ask its manager to join. The manager gets a compliant tip-pool workflow and a fast path into Tally scheduling and payroll.

Over time, Tally becomes the worker-demanded infrastructure for restaurant pay. Each restaurant adds workers; some workers connect another restaurant; those restaurants add more workers. We win distribution and engagement without needing to subsidize a sprawling suite.

This also gives us a differentiated response to Crewbook’s free scheduling. We should test whether worker demand and trusted tip handling change buying decisions—not assume they eliminate price sensitivity.

We should not include advances in this vision’s first stages. Earned-tip payouts are available through our partner without a licence. Advances introduce a nine-to-twelve-month regulatory dependency in key states without evidence that they strengthen this mechanism.

Opportunity range

Two sensitivities establish the scale; neither is a forecast.

Restaurant acquisition. The beta produced 57 worker-requested signups per 300 participating restaurants in one quarter. At today’s 6,400-restaurant footprint, reproducing 25%–100% of that observed rate would generate approximately 304–1,216 signups per quarter. At our current average ARR of roughly $4,844 per restaurant, that represents $6M–$24M of annual new ARR bookings.

The 25% case is a planning haircut, not an observed result. These signups may overlap with normal acquisition; saturation, duplicate requests, churn, and restaurant eligibility could materially reduce the outcome. For context, we currently sign 380 restaurants per quarter.

Payout revenue. Across today’s 190,000 workers, a sensitivity of 10%–44% adoption and one to five payouts weekly yields approximately $0.6M–$13M in annual Tally payout revenue, at $0.60 per payout, before our operating costs. Ten percent is an illustrative adoption assumption; 44% is stated willingness in a selected beta survey, not demonstrated paid demand. Eligible tipped workers, funding readiness, and actual frequency remain unknown.

Do not add these figures into a single ARR claim: one is new subscription bookings; the other is annual transaction revenue. The pack supports a potentially substantial expansion engine. It does not establish a $1B outcome or a literal 1000x multiplier.

Work backward: prove the loop before scaling it

The thresholds below are proposed decision rules, not facts from the beta.

1. Next quarter: build identity and measure distribution

Squad one: Build consent-based account linking into a single worker identity, including account recovery and clear employer-data boundaries. A restaurant must not gain access to another employer’s records.

Squad two: Productize and instrument the existing tip experience, then build a lightweight worker-request-to-manager-onboarding flow. Run a randomized invitation test within eligible restaurants, tracking requests through signed, activated restaurants. Instrument finalized earned tips and partner readiness in parallel.

Start experimentation with existing accounts; do not wait for identity linking to finish. Use linked identities to improve deduplication and measure the cross-workplace path.

Gate to the next stage: Linked records are accurate; workers understand consent; the nightly tip experience remains reliable; and the invitation test shows incremental activated restaurants, not merely clicks or attributed leads. Target at least a 25% lift over control, with acquisition cost below our normal channel.

2. Then: test paid earned-tip payouts

With identity shipped, one squad builds the partner payout integration; the other improves worker-led restaurant onboarding and expands the controlled acquisition test.

Offer payouts only against finalized, earned, fundable tips. Make the $0.99 fee explicit and the ordinary payment route clear. Compliance must approve the flow, including tip-pool rules and fee treatment.

Gate to broader rollout: Actual paid use—not survey intent—supports positive contribution economics. Set an initial target of at least 10% monthly adoption among eligible workers, with repeat use across two months. Require reconciled payouts, acceptable support burden, and no deterioration in trust or employer adoption.

Payout failure should stop that monetization path, not automatically kill a working distribution loop.

3. Finally: expand the network

Roll out restaurant-by-restaurant and state-by-state only after controlled evidence survives beyond volunteer beta customers. Invest in worker-led onboarding before adding unrelated owner software.

Stop condition: If two adequately powered invitation tests show no incremental restaurant activation, or incremental acquisition costs are no better than normal sales, stop the network expansion thesis. Keep the calculator as a useful retention feature; do not fund a platform story around it. Wrong-person linking, unlawful pooling, or unreliable payouts triggers an immediate pause in the affected flow.

What to do with Marcus’s idea

Keep the ambition; decline the roadmap.

“AI operating system for restaurants” names a destination but does not explain why we win. Inventory, reservations, marketing, and menu pricing would spend both squads across new markets while leaving our strongest observed mechanism undeveloped.

Ask Marcus to sponsor the worker-network bet and its explicit gates. AI can later improve a proven workflow where it demonstrably adds value. It should not substitute for proving our distribution advantage.

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.