1000x an idea

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.

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.