1000x an idea

To: Marcus Webb and Executive Team From: Staff PM Subject: Make tip-out a worker-led distribution network—not an everything app

Recommendation

Give the two squads next quarter to test a bigger thesis: Tally can become the portable earnings account that workers bring from restaurant to restaurant, making workers a distribution channel for our employer business.

The dimension to push is reach across workplaces, not breadth of restaurant software. Kenji’s calculator may be the entry point to that network. The evidence does not yet establish a literal 1,000× opportunity; it establishes a mechanism worth testing before we commit to a broader platform.

1. The mechanism: one worker can recruit the next workplace

The calculator solves a nightly manager problem, but its more consequential effect may be on workers:

• Worker-app weekly activity rose from 34% to 81% at beta restaurants.
• 41% of beta workers also work at another restaurant.
• 29% of surveyed workers say they have asked another manager to adopt Tally.
• We recorded 57 worker-requested restaurant signups last quarter. Those deals closed in nine days versus our usual 41, with roughly one-third the sales spending per deal.

The potential loop is:

Accurate nightly tips → workers return at close → workers request Tally at another job → another restaurant adopts → more workers encounter Tally.

This could change acquisition economics, not just improve a feature. It also creates a reason to choose Tally that Crewbook’s free scheduling does not directly answer.

But this is not yet a demonstrated network effect. The beta was self-selected, the survey measures stated behavior, and we have not established how many of the 57 signups were incremental or originated in the beta.

2. The ambitious destination—and a defensible size

The most ambitious version is a worker-consented earnings network spanning restaurants:

• One identity connects a worker’s jobs, shifts, and earned tips.
• Workers see verified nightly earnings and can optionally receive already-earned tips immediately.
• A worker can ask a second employer to join through a lightweight invitation and onboarding path.
• Restaurants join first to deliver trusted tip accounting and settlement; scheduling and payroll expansion follow.

Eventually, the network could extend beyond restaurants already using Tally’s full suite. That requires proving we can verify earnings and onboard an employer without compromising compliance. It is a destination, not next quarter’s scope.

We can size a beachhead from our current footprint, not a national TAM:

Subscription sizing uses today’s average of approximately $4,844 ARR per restaurant. The acquisition scenarios are sensitivity cases, not forecasts: we must validate the referral denominator, incremental lift, saturation, retention, and pricing. They are not automatically additive to our existing 380 quarterly signups.

Payout adoption likewise discounts—or at its upper end accepts—the survey’s 44% stated willingness to pay; transaction frequency is an assumption. Not every worker will have eligible tips.

These are separate revenue measures, not a combined ARR claim. They show a potentially material business on our existing footprint. The larger, cross-platform opportunity remains unquantified.

3. Work backward: earn each expansion

Next quarter: establish the worker connection and test causality

Squad 1: Portable identity. Build consent-based linking of existing restaurant accounts into one worker account, with clear employer boundaries, revocation, and no leakage of one employer’s information to another. This is the stated one-squad-quarter investment; do not bury unrelated work in it.

Squad 2: Prove the distribution loop. Harden tip correctness and dispute handling, instrument worker invitations through restaurant activation, and run a controlled expansion beyond the volunteer beta. Randomize rollout or invitations at an employer/network-cluster level where practical, accounting for workers who connect clusters. Distinguish an invitation, a signed contract, and a restaurant actually running payroll.

Test referrals using existing accounts while identity work proceeds. Do not wait a quarter to start learning, and do not promise advances or build a broad financial product.

Gate to broader rollout: After at least two normal sales cycles, demonstrate incremental, retained restaurant acquisition versus a comparison group—not merely faster attribution of deals we would have won anyway. A provisional investment hurdle is 0.05 incremental activated restaurants per participating restaurant per quarter, roughly one-quarter of the provisional beta rate, with lower fully loaded acquisition cost than ordinary sales. Set retention and tip-accuracy guardrails before launching.

Next: monetize earned tips without weakening the loop

Once verified tip accounting and payout reconciliation pass Compliance review, Squad 2 can pilot the partner’s $0.99 optional same-night payout; Squad 1 extends proven identity and invitation flows. Preserve free tip visibility.

Gate to expansion: Observed repeat purchases—not survey intent—produce positive contribution after support and losses, with no material increase in disputes or deterioration in worker engagement. Failure here means dropping paid payouts, not automatically abandoning referrals.

Then: open the network beyond full-suite customers

Only after acquisition and retention replicate outside the beta should we test a lightweight tip-and-earnings entry product for employers not ready to switch payroll.

Gate: Verified earnings, enforceable pool rules, economical onboarding, and incremental customer value without unacceptable full-suite cannibalization.

Stop result: If an adequately powered test over at least two sales cycles shows no meaningful incremental retained restaurant acquisition—or economics below our agreed hurdle—we stop funding the network expansion. Keep the useful calculator. Pause immediately for material tip-allocation or privacy failures.

4. What to do with Marcus’s idea

Keep Marcus’s ambition; reject the proposed scope for this planning cycle.

Inventory, menu pricing, marketing, and reservations each require new data, workflows, and distribution advantages that this pack does not establish. Calling them an AI operating system does not connect them to our strongest evidence.

Reframe the vision as “Tally becomes the earnings network workers bring to every restaurant.” AI can support that strategy where it demonstrably improves outcomes; it is not the strategy itself. Defer advances and their licensing burden. Return to broader platform bets only after we prove the mechanism that earns us the right to expand.

MEMO To: Marcus Webb and the exec team From: Staff PM Re: The 1000x version of the tip-out calculator

---

1. The mechanism and the dimension to push

The mechanism: the worker is our distribution channel. The calculator gave workers a reason to open Tally every night, because they can see their tips. Weekly active use rose from 34% to 81%. Because 41% of those workers hold a second job, a worker who opens Tally nightly is a salesperson in a second restaurant. In one quarter, 57 restaurants signed up because a worker asked. Those deals closed in 9 days against our 41-day average, at about a third of the sales cost.

That is the mechanism. The 25 minutes a night that managers save is why they adopt the calculator, but it isn't what grows the business.

The dimension I would push: cross-restaurant worker identity. Today a worker at two Tally restaurants has two unconnected accounts. We can't see the overlap, can't make the second job's invitation easy, and can't give the worker one place that holds their pay across jobs. Linking accounts, with consent, turns 190,000 isolated app users into a network. Crewbook can bundle free scheduling, but it can't copy a worker base that is already pulling restaurants in.

2. The most ambitious version

Tally is where restaurant workers see and receive their pay, and the worker network is how restaurants find us. It has three parts: - One worker account across every job. - A same-night tip payout. It pays out tips already earned, so it needs no licence, and Tally keeps $0.60 of the $0.99 fee. - A one-tap "bring Tally to my other job" flow.

Sizing. Today we make about $4,800 ARR per restaurant and have about 30 workers per restaurant.

Payout revenue on today's base (190,000 workers). Survey intent was 44%, which overstates real behavior, so I used 22% to 44% adoption at 2 to 3 payouts a week at $0.60. That gives $2.6M to $7.8M a year. This is real money, but on its own it is not 1000x.

Referral growth. The beta produced 0.19 referred restaurants per calculator restaurant per quarter. Beta restaurants chose to join, so I discounted that to 0.05 as a floor. I compounded both rates over eight quarters on the 6,400 base, excluding our current 380 signups a quarter and assuming no churn:

Planning range: $50M to $155M ARR in two years, against $31M today. I would plan on the low end. The high end needs the beta rate to hold at about 4x the scale with no saturation.

This is a 2x to 5x outcome, and the data does not support 1000x. What can be much larger is the shape of the business: customer acquisition that costs a third as much, sales cycles of 9 days instead of 41, and a revenue line that scales with workers rather than with restaurants. A $1B company needs the high end sustained for longer than two years.

Caveats: - The beta restaurants chose to join. - We don't know how many of the 57 referred restaurants were already in our pipeline. - Survey answers are stated intent, not behavior. - The 190,000 figure counts accounts, so unique workers are fewer. Linking accounts will give us the real number.

3. The sequence

Two squads next quarter. Before they start, spend two weeks of analyst time on the 57 referred deals. We need to know how many were already in the pipeline and what the true multi-job share is across the whole base. This costs no squad time.

Step 1 (next quarter) - Squad A (Worker Identity): builds the linked worker account with consent, plus the "bring Tally to my other job" invite in the app. This is the one-squad, one-quarter estimate. - Squad B (Money and Rollout): takes the calculator from 300 restaurants to about 1,500, including state-rule coverage in our five main states. It also pilots same-night payout in the beta restaurants. The pilot uses earned tips only, so no licence is needed.

Before Step 2, all of these must be true: - Outside the self-selected beta, referral runs at 0.10 or more new restaurants per calculator restaurant per quarter, and referred deals close in under 15 days. - At least 50% of multi-job workers who are prompted link their accounts. - At pilot restaurants, at least 20% of workers use payout within 30 days, and half of them use it again. - Referred restaurants show no worse early churn than the rest of the base.

Step 2 (quarters 2 and 3) - Squad A: builds the referral loop, with a fast onboarding path for a restaurant invited by one of its own workers. - Squad B: makes payout available across the whole calculator base. - Compliance starts the early-wage licence work in the background at low cost. It is an option, not a dependency.

Before Step 3: - Payout revenue per active worker is tracking toward the $14 to $41 a year range. - The referral rate holds at scale. - Win rate against Crewbook is better in markets where Tally already has worker density.

Step 3 (quarter 4 onward). Decide whether to pursue early wage access, which needs licences in 3 of our 5 main states and 9 to 12 months. Decide this with real payout data in hand, not before. Explore labor-adjacent products on the worker network, such as availability across jobs.

The result that would make us stop. After two quarters at about 1,500 calculator restaurants, referrals run below 0.03 per restaurant per quarter (about 190 new restaurants a quarter at full base, fewer than half of what we sign today), and payout adoption is under 10% of workers. That would tell us the beta was a self-selected group and the calculator is a good retention feature for managers, not a growth engine. We would keep the calculator, stop investing in the worker network, and put the squads elsewhere.

4. What we should do with Marcus's idea

Don't build it now, and don't drop the ambition behind it. The "AI operating system" is four separate products: inventory, menu pricing, marketing, and reservations. Each has a different buyer, different data, and different incumbents. Nothing in our data shows owners want any of them from us. What our data does show is that workers pull restaurants into Tally, and that is our right to win.

The two ideas fit together in sequence. If the worker network works, we will have something no inventory or marketing tool has: the people in the restaurant, using Tally every night, across several employers. A broader platform is much more credible once owners are already adopting Tally because their staff asked for it. A labor-first path, where Tally uses availability and pay across jobs to make scheduling and staffing decisions smarter, can grow into the larger vision.

My recommendation: adopt the worker network as the plan for next quarter, and revisit the operating-system vision at the Step 2 gate, with data from the referral loop and payout in hand. If the gates pass, the case for the larger vision will be much stronger than it is today.

Kenji deserves credit here. His calculator turned a free worker app into a nightly habit. The habit created the mechanism, and the plan above is how we turn it into a business.