1000x an idea

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.

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.