1000x an idea

MEMORANDUM

TO: Marcus Webb (CEO) & Executive Team FROM: Staff Product Manager, Tally DATE: October 24, 2023 SUBJECT: From Tip Calculator to Network Effect: The $1B Path for Tally

---

1. The Mechanism and the Dimension

Kenji’s beta proved that the tip-out calculator saves managers 25 minutes a night and drives worker app engagement from 34% to 81%. But the real mechanism that makes this 1000x bigger isn't automation—it is multihoming labor coupled with a viral consumer loop.

Right now, 41% of workers at beta restaurants work at another restaurant. Because the tip calculator demands they check the Tally app at close to verify earnings, they are carrying our brand into competitor venues. When they ask their other managers to switch, those inbound deals close in 9 days (vs. our 41-day average) at one-third of the acquisition cost.

The single dimension we must push is Cross-Restaurant Worker Identity. Right now, a worker with two jobs has two siloed accounts. By unifying them into a single identity, we transform Tally from isolated B2B restaurant software into a consumer-grade network where workers organically pull non-Tally restaurants onto our platform.

---

2. The Most Ambitious Version & Opportunity Sizing

The 1000x version is Tally Financial Network: a closed-loop financial operating system for hourly hospitality labor.

We stop selling software top-down to stressed operators alone and start growing bottom-up through the financial urgency of 190,000+ hourly workers. Tally becomes the infrastructure where workers instantly access, manage, and move their daily earnings across the fragmented restaurant landscape.

#### Opportunity Sizing (Range) * Conservative Case ($35M–$50M ARR added in 24 months): Driven purely by viral acquisition velocity. If we reduce sales cycles from 41 days to 9 days across a larger cohort of worker-referred restaurants, our organic acquisition rate triples, lowering CAC and accelerating ARR past $80M without expanding headcount. * Aggressive Case ($120M–$180M ARR added in 24 months): Driven by Same-Night Tip Payouts. Our payments partner allows us to pay out tips already earned the same night for $0.99, netting Tally $0.60 per payout. With 190,000 workers (plus viral additions), assuming an average of 3 shifts a week and a 44% adoption rate (validated by our survey), this creates a massive, high-margin transactional revenue stream that dwarfs our current SaaS subscription model.

---

3. The Execution Sequence

We have two engineering squads allocated for next quarter. Here is the strict sequence, prerequisites, and hard stop-conditions.

#### Squad 1: Unified Worker Identity & Viral Loops (Q1) * What they build: The underlying database architecture to link a worker’s identity across multiple restaurant profiles (with explicit worker consent), alongside the frictionless "Invite Your Other Job" referral and onboarding flow inside the worker app. * Prerequisite: Legal review confirming that linking accounts via worker consent does not violate data-sharing agreements with restaurant operators. * Stop Condition: If fewer than 15% of multi-job workers consent to linking accounts, or if viral referral conversion drops below 10%, we abort and keep accounts siloed.

#### Squad 2: Same-Night Tip Payouts (Q1) * What they build: Integration with our payments partner to enable same-night, post-close tip payouts for $0.99, ensuring strict compliance with state tip-pool rules (keeping managers/owners out of the pool) and avoiding early-wage-access licensing traps. * Prerequisite: Final sign-off from Compliance confirming that paying out already-earned tips post-close requires zero new state licenses (avoiding the 9-to-12-month licensing delay). * Stop Condition: If payment partner error rates on same-night liquidity exceed 0.1%, or if take-rate margins are squeezed below $0.40 per payout, we halt.

---

4. What We Should Do with Marcus’s Idea

Marcus’s vision—“Tally becomes the AI operating system for restaurants: inventory, menu pricing, marketing, reservations, all of it... That's how we become a $1B company”—is the right long-term destination, but the wrong sequence for next quarter.

If we try to build inventory, menu pricing, and reservations right now, we dilute our engineering focus and walk straight into a bloody feature-parity war with entrenched incumbents, while simultaneously losing deals to Crewbook on price (11% loss rate last year).

Recommendation: Politely shelve the "AI Operating System" breadth for 12 months. Instead, weaponize Kenji’s tip calculator.

By unifying worker identity and launching same-night tip payouts, we leverage our unfair advantage: the workers. We use consumer-grade financial utility to bypass the restaurant owner's sales resistance entirely. Once we own the liquidity of the hourly workforce across 50,000+ restaurants, then operators will have no choice but to adopt our broader operational suite—because their staff demands it. That is how Tally becomes a $1B company, starting with a 99-cent tip payout.

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.