โ† Coverage hub REPS WITH FRIENDS ยท DOCUMENTS v1.1.0

Reps With Friends โ€” Business Potential Analysis

Prepared for Alexei Brown ยท 26 Aug 2026 ยท Source: intro email from Ben (via Nico)


1. Who we're dealing with

Ben โ€” founding member and drummer of Silverchair. Multi-platinum ARIA-winning Australian band. The name-drop is relevant, not vanity:

Signal quality of the email itself: high. He's been refining for a year, produced a production-fidelity Figma + full blueprint (design risk largely retired), explicitly invites pushback ("what's rubbish and what deserves more room"), and opens with equity-for-work. This is a collaborator-shaped founder, not an idea guy shopping for hands.


2. The product, stripped to its load-bearing ideas

IdeaWhy it matters commercially
The "300" format โ€” any reps, any order, any of the agreed exercises, first to 300 totalBrilliantly simple game loop. Self-balancing (you choose your mix), zero setup friction, instantly understandable in one chat message.
Handicap system โ€” effort & consistency compete, not raw fitnessThis is the moat. It's the difference between a gimmick and a system. Golf proved handicaps keep weak players paying for decades. Nobody in fitness apps does this well. It's also the hardest thing to get right โ€” which is why it's defensible.
Chat-first distribution โ€” the game lives in Slack/WhatsApp/Messenger; app is home baseThis is the second moat. Every match broadcast is an ad seen by the whole group chat. Non-users are spectating the leaderboard within minutes. Near-zero CAC, built-in viral loop.
Pick your days โ€” groups choose 2โ€“3 days/week, go hardAnti-burnout by design. Removes the daily-streak failure mode that kills StepBet-style apps.
Charity wagers โ€” winner directs a pot to charityReal stakes without gambling regulation (mostly โ€” see risks). Also a corporate-sales hook: companies love "team fitness for charity" narratives.
Taunting as a feature โ€” banter, filming mates mid-set, before/aftersThe content engine. User-generated shareable clips = organic acquisition on top of the chat loop.

3. Market position

What exists:

What's empty (verified via GitHub + market scan): small-group, real-time, handicapped competition delivered inside the group chat where the banter already lives. No established player, no serious open-source project (the "gym leaderboard" OSS space is literally 0-star student projects). The niche is open.

Adjacent revenue pools:


4. What Alexei uniquely brings (leverage in any equity conversation)

  1. The chat-integration capability is already built. The Qalarc Hub owns a<br>working Signal + WhatsApp session with an HTTP API. A WhatsApp bot prototype<br>is days, not months. Most teams would stall here on WhatsApp Business<br>approval alone.
  2. AI-agent shipping speed. Rep verification (camera pose estimation),<br>banter bots, match narration โ€” all AI-shaped problems, all in our wheelhouse.
  3. Full-stack + infra. Cloudflare stack, Resend, existing deployment<br>patterns across qalarc/tradez properties.

Ben has design + vision + publicity. We have build + distribution plumbing + AI. That's a complete founding pair, which is exactly what the equity conversation should price.


5. Risks & hard problems (ranked)

  1. Rep verification / cheating โ€” the existential technical problem. If reps<br>are self-reported, the game is a lying contest; if verification is annoying,<br>nobody plays. <strong>Mitigation (from research):</strong> in-browser pose counting<br>(MoveNet/BlazePose, $0, no install) for MVP + heart-rate cross-checks from<br>any BLE strap via Web Bluetooth. Good-GYM (MIT) has portable rep-counting<br>logic. Handicap scoring via %HRR (Karvonen) makes <em>effort</em> verifiable even<br>when reps aren't.
  2. Retention after week 3 โ€” novelty decays. The designed retention stack:<br>handicaps (always winnable) + chosen days (no streak guilt) + charity stakes<br>(real consequence) + chat presence (no app-opening required). Needs a<br>season/league structure to give the loop long arcs.
  3. WhatsApp economics โ€” Cloud API charges per conversation; a chatty match<br>bot in a 20-group portfolio could burn real money. Mitigation: batch<br>standings (not per-rep), Qalarc Hub for dev, model costs before scale.
  4. Charity-wager legal structure โ€” "winner picks charity" must avoid being<br>classified as a raffle/betting product under AU state law. Needs a proper<br>legal opinion before money moves. (Nico's idea is good โ€” it just needs<br>structure.)
  5. Apple Messages โ€” no official bot API. Correct call: skip for MVP, say so<br>plainly.
  6. Single-founder dependency โ€” Ben is design/vision; the build partner<br>(us) is the other half. Equity conversation should reflect co-founder<br>reality, not contractor pricing.

6. Verdict

Strong opportunity. Take the call. Push for the Figma + blueprint.

Position for: co-founder-track equity + build ownership, not a paid build. The email explicitly invites that conversation โ€” take it.