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, CEO; Executive Team FROM: Staff Product Manager DATE: October 24, 2023 SUBJECT: Strategy, Sizing, and Execution: The Labor Network & Tip-Out Engine

---

Executive Summary

Kenji’s beta did not just build a utility that saves managers 25 minutes; it accidentally uncovered our most powerful growth loop.

In 90 days, 300 beta restaurants generated 57 closed-won new restaurant deals driven entirely by workers asking their other employers to adopt Tally. That represents 15% of our total quarterly adds, closed in 9 days (vs. our 41-day baseline) at one-third of our typical CAC.

We should not dilute our resources building a horizontal AI operating system. Instead, we should pursue the Worker-Led Distribution Loop. By unifying worker identities and monetizing daily earned tip liquidity, we transform Tally from back-office SaaS into the dominant two-sided labor and financial network for the restaurant industry.

---

1. The Mechanism and the One Dimension

The Mechanism: Cross-Employer Worker Virality. 41% of restaurant staff work at more than one restaurant, and 29% have already pitched Tally to their other manager. Restaurant labor is not stationary; it is an interconnected, multi-tenant network. When Tally provides workers with transparency and immediate utility, workers pull Tally into non-Tally restaurants.

The One Dimension to Push: Worker Liquidity & Engagement Velocity. Workers do not advocate for scheduling software; they advocate for their money. Beta WAU jumped from 34% to 81% because workers opened the app at close to see their tips. If we pair same-night earnings visibility with instant earned payouts, Tally shifts from a passive schedule viewer into an indispensable daily financial lifeline. This creates an intense worker preference that Crewbook’s commodity payroll bundle cannot match.

---

2. The Ambitious Version & Sizing the Opportunity

#### The Vision: The Portable Hospitality Passport & Financial Network Instead of restaurant-siloed accounts, Tally issues a portable Tally Profile & Wallet. * For Workers: A single app to manage shifts across multiple employers, access earned tips instantly at clock-out, and carry validated work history across jobs. * For Operators: Automated, compliant tip pooling, faster shift-filling from a verified labor pool, and automated close-of-day payouts without cash handling. * For Tally: Zero-CAC customer acquisition driven by workers, monetized via both high-margin fintech transaction fees and resilient core SaaS ARR.

#### Sizing the Opportunity (Range)

We model the incremental annual revenue opportunity over the next 12–24 months across two engines:

At network maturity (30,000+ restaurants connected via worker mobility), this labor-fintech network alone represents a $50M–$80M ARR business, creating a structural moat no standard payroll provider can cross.

---

3. The Sequence: Two Squads, Stage Gates, and Kill Criteria

We have 2 squads for next quarter. Rather than pursuing wage advances that require 9–12 month regulatory licenses, we immediately monetize earned tips same-night ($0.99 fee / $0.60 Tally net) via our current payments partner with zero licensing hurdles.

``` QUARTER 1 QUARTER 2 +-----------------------+ +--------------------------+ | Squad 1: | | Squad 1: | | Unified Worker ID | | "Bring Tally" Virality | | (Tally Passport) | | In-app manager pitch kit | +-----------+-----------+ +-------------+------------+ | | | ===> [GATE 1: Identity & Volume] ===> | ===> [GATE 2: CAC & Conversion] | | +-----------+-----------+ +-------------+------------+ | Squad 2: | | Squad 2: | | Earned Instant Tip | | Multi-Employer Shift & | | Payouts ($0.60 net) | | Consolidated Payout Hub | +-----------------------+ +--------------------------+ ```

#### Quarter 1: Foundation & Monetization * Squad 1 (Worker Identity): Build the account-linking architecture to allow workers to merge multiple restaurant profiles into one consent-based Tally ID (estimated at 1 squad-quarter). * Squad 2 (Instant Tip Payouts): Build the payment rails with our current partner for instant end-of-shift earned tip transfers ($0.99 fee; $0.60 net to Tally).

Gate 1 (To proceed to Q2 expansion): 1. $\ge 20\%$ adoption of linked accounts among multi-job workers within 45 days of availability. 2. $\ge 25\%$ opt-in for instant tip payout at close among eligible beta workers.

#### Quarter 2: Network Growth Loops * Squad 1 (Virality & Referral Rails): Build native worker-to-manager referral tooling (“Add my other restaurant to see my unified schedule and pay me instantly”), complete with an automated lead routing hook to sales. * Squad 2 (Multi-Employer Experience): Deliver a unified calendar and consolidated multi-job earnings hub for workers.

Gate 2 (To scale go-to-market): 1. Worker-sourced leads convert at $\ge 25\%$ with a sales cycle under 15 days. 2. Blended CAC for worker-sourced leads remains $\le 40\%$ of standard outbound CAC.

#### Kill Criteria (When to Stop) We halt the standalone network strategy and fold tip-pooling back into a baseline retention feature if: * Adoption fails: Fewer than 12% of workers use instant tip payouts after 60 days of GA, indicating that tip liquidity is not a strong enough engagement trigger. * Network loop collapses: Fewer than 2% of multi-job workers trigger an invite to their second restaurant, indicating the 57 beta conversions were an unrepeatable anomaly rather than a scalable loop.

---

4. What to Do with Marcus’s Idea

Marcus’s Proposal: Build an "AI Operating System for Restaurants" spanning inventory, menu pricing, reservations, and marketing.

Recommendation: Shelve this immediately.

1. It attacks entrenched, well-capitalized specialists: Entering reservations (OpenTable/Resy), inventory (Toast/MarginEdge), and marketing turns every partner in the ecosystem into an enemy. We do not have the balance sheet or vertical domain expertise to out-execute all of them at once.
2. It fails to solve our primary commercial vulnerability: Crewbook is taking 11% of our deals on price by commoditizing payroll and scheduling. Building predictive menu pricing does not insulate our core payroll business from pricing pressure.
3. It ignores our proprietary advantage: Our unique asset is the 190,000 workers already using our app daily. Toast and Crewbook own the restaurant contract; we have the opportunity to own the workforce.

The Pivot to Marcus: We share Marcus's ambition to reach a $1B valuation, but the right wedge is not horizontal ops software—it is labor network liquidity. If we own scheduling, tip distribution, and the worker’s financial wallet across employers, we control the restaurant industry’s single largest operating cost (labor). Once we establish this two-sided network moat, we can deploy labor-focused AI (e.g., dynamic shift-pricing and automated staffing forecasts) from an unassailable market position.