← the noteCHAPTER 3 OF 4 · THE TWO HARD QUESTIONS
Chapter 3 of 4 · expands the note

The two
hard questions.

If chapter 2 made sense, two objections should already be forming, because they formed in our group too: why would anyone pay hours before a game, and what happens to per player data when one phone pays for four people. Both are fair. Both have answers that make the business stronger, not weaker.

Question one · asked by every organizer
"People do not want to pay immediately."

Correct, and they are being rational. This part shows why delaying is the smart move today, four ways to price a reservation, and the design that keeps holds honest without deleting anybody.

A1 · Why the list beats the link

Four rational reasons nobody pays at 12:30 PM

REASON 1Game risk

The game itself might not happen. Until a list is clearly filling, paying early means lending the game money and waiting out the refund if it dies.

"You will get it in a few days, the game had been cancelled so the refund is automated."
Trisha · 30 Jun, answering "I did not get the refund yet"
REASON 2Plan risk

Office, rain, Hennur traffic, mom. Plans firm up at 5–6 PM; the list opens at noon. A name is reversible, a payment isn't (quickly).

"my mom will not let me back home"
~ राठौड़ · 4 Jun · and a hundred variants like it
REASON 3Squad gravity

Half this group joins because their friends did, 862 "+1s" in ten weeks. You commit when your people commit, not before.

"7 people from my side"
~ Isaac · 26 Jun, a whole team, contingent on timing
REASON 4The free option

Writing your name costs nothing and can't be enforced. Economics 101: make an option free and everyone takes one, then payers find the door blocked by holders.

"Guys clear your payments otherwise others will click on the link and pay and I will have to remove a random name from the list :("
Trisha · 3 Jun, squatters taxing payers, in one sentence
So the diagnosis changes. The gap between the list and the link is not carelessness, it is unmet demand for reservations. A system that only accepts instant payment would kill the soft names, and soft names are what make a game look alive at 2 PM. The move is to keep reservations and price the option honestly.
A2 · Four ways to price a reservation

The ladder, worst to best

Free, foreverthe WhatsApp list today
Costless holds that never expire, enforced by people deleting each other's names at 5 PM. Maximum liquidity, zero fairness. This is the system that produced the 22 July incident in chapter 1.
✕ Reject
Deposit ₹30skin in the game
Reserve for a token amount, forfeit if you ghost. Prices commitment, but adds a second payment step, and forfeiture creates support drama for Trisha. Worth revisiting for hot games (Sunday 11v11) only.
◷ Maybe later
Timed hold + bumpfree, but honest
Hold a spot for free, with a visible countdown. It expires at the game's deadline, and it's bumpable by real money when the game is full (rules on the right). No money friction, no squatting, no name-deleting. Pure rules, buildable now.
✓ Ship first
Block, don't paythe IPO pattern
Reserve = UPI mandate that blocks ₹180 without debiting it, exactly how India applies for IPOs. Captured only when the game locks; released instantly if it cancels or you drop in time. Refund anxiety, the root reason people delay, ceases to exist, because no money ever moved. Needs mandate rails, so it's phase two.
★ The endgame
A3 · The design

Two lanes, three rules

The roster stops pretending everyone is equally committed. It shows two truths side by side: money and intent, and converts one into the other under clear rules instead of social violence.

Rule 1 · Holding is legit

Free hold, visible clock

Anyone can hold a spot without paying, one tap. The hold lasts until the game's pay-deadline (Trisha sets it, e.g. 5 PM) and everyone can see the countdown. Your "maybe" is honest now: it seeds the game like the old list did, but it can't silently become a squat. Holds shrink as the game fills, last 3 spots are pay-only.

Rule 2 · Money talks, politely

The pay-or-release bump

Game full, and someone new wants to pay? The oldest unpaid hold gets a push notification: "Someone's ready to pay for your spot, confirm in 30 min or it releases." That's the Taru–Tahir incident turned from a crime into a rule: payers are never blocked for long, holders are never deleted without warning and a fair chance.

Rule 3 · Reliability is remembered

Earned hold length

Show up and pay on time → your future holds get longer and safer. Let holds expire repeatedly → you go pay-first for a while. Regulars get trust automatically; serial squatters lose the option, the system learns who "maybe" actually means yes from.

Wednesday 9v9● 15/18 · DEADLINE 5:00 PM
Confirmed, money attached13
AMAmanPAID
ILIshan LeninPAID
TATahirPAID
+10ten more…
Holding, free, expiring2
KAKaushik2:14:09 LEFT
ATAtharva28:41 · BUMPED
PLAYSPACES · to Atharva only
Game's full and someone is ready to pay for your spot. Confirm ₹180 in 28:41, or it releases to them. No hard feelings either way.
Pay ₹180 · keep itRelease
Nobody deleted. Nobody blocked. The clock does
what Trisha's 195 chase messages used to do.
A4 · How this lands in the sketch

Small additions, same mechanism

Game pageGets a second button: "Hold my spot" next to "I'm in, ₹180". Fill bar already had the amber "held" state, it now means this.
SquadsA captain can hold N spots for the squad, then convert with one payment, Isaac's "7 people from my side" becomes a first-class action.
Admin knobsTrisha sets the pay-deadline, the bump window (default 30 min), and how many spots stay pay-only at the end. The 5 PM norm the group already invented, made official.
Phase twoSwap free holds for UPI blocks where possible, reserve without paying, money never moves unless the game locks. Then even "confirmed" carries zero refund anxiety.
Question two · the data concern
"One payment per phone, so every player is known."

The goal is right and the note keeps it. This part shows where the current rule leaks (stuck funnels, proxy payments, no shows) and how squad payments can capture more identity, not less.

B1 · What the database sees tonight

The rule does capture people ·
at the worst tollbooth: checkout.

AMpaid, own №
ILpaid, own №
TApaid, own №
SUpaid, own №
RApaid, own №
ROpaid, own №
PRpaid, own №
FApaid, own №
YApaid, own №
KUpaid, own №
SApaid, own №
AJAjay played,
Ron's number
+1told "go pay" ·
hasn't opened link
+2stuck at
OTP login
+3UPI failed,
gave up
+4"will pay
by 5" (maybe)
LU"Luke ✅" on list
· never came
?paid, no-show
nobody logged it
11
known, finished solo checkout
4
+1s stuck mid-funnel
1
proxy-paid, wrong human
2
attendance unknowable

Identity is only captured when a solo checkout succeeds. Every failure, no time, no OTP, no UPI, becomes a hole in the list or a lie in the DB.

B2 · The split

Money moves once.
Every player is still known.

Money rail1 payment
RORohanany phone, any UPIPAYS ₹540
Wednesday 9v93 spots locked together
Who paid is a finance fact. It was never a good proxy for who played, see Ajay.
Identity rail3 humans
RIRitikmember, already knownLINKED
TUTusharguest → claim link on WhatsAppCLAIMS W/ OWN №
LULukeguest → claims, or spot stays unverifiedCLAIMS W/ OWN №
No spot without a person. Guests claim with their own number, same identity yield as today's login, minus the checkout. And the DB finally records both truths: paid-by Rohan, played-by Ajay. No more proxy-pay fiction.
Today · squad of 412+ steps · 4 phones
RohanopenOTPpay ✓
+1"bro go pay"openOTPpay
+2"bro go pay"openOTPUPI failsretry…
+3"bro go pay"…still hasn't opened it
With claims · same squad1 payment + 3 taps
Rohanpays ₹720, all 4 spots locked ✓
Ritikmember, auto-linked ✓
Tushartaps claim → own № in DB ✓
Luketaps claim → own № in DB ✓

Same four people end up in the database, more, actually: the ones who currently give up at OTP or UPI. The checkpoint moves; the data doesn't shrink.

B3 · The no show problem

Paid is not played. Stats need a third fact: showed up.

Today · one name, three unknowable truths
WhatsApp list saysLuke ✅ON LIST
Database sayswhoever's № paidMAYBE LUKE
The turf saysno LukeNO-SHOW
Fix: captain or admin taps attendance at kickoff, 20 seconds, or players self check-in at the ground. “Played” becomes a recorded fact, per person, per game.
Tomorrow · the leaderboard Trisha posts by hand, live & verified
Top players · July● GAMES PLAYED, NOT PAID
1TRTaruvar14 played · 0 no-shows14
2AMAman13 played · 1 no-show13
3RORohan12 played · brings +2.1 friends/game12
4RARathore11 played · 96% on-time pay11
B4 · What the asset becomes

Today: phone № → payment count.
With the split: this.

Person profiles

Games, position, attendance %, pay speed, per human, not per paying phone.

RO
GAMES · 41 ATTENDANCE · 96% PAYS ON TIME · 100%

The squad graph

Who brings whom. Your real acquisition map, invisible today because +1s are ghosts.

RO TU LU RI NA VI KA

Demand curves

Fill-speed by slot, format, price. Stop guessing between 7v7 at 8 or 9v9 at 9:30, the data answers.

6 PM 7:30 8 PM 9:30 10:30

Reliability, priced in

No-show risk per player, feeds hold length, reminders, and who you trust with a “maybe”.

TR97% shows
RO96%
LU61% 👀
Both questions resolve the same way: keep the goal, move the mechanism. Reservations stay but get a clock. Identity stays per player but moves from checkout to claim. What is left is pure upside: chapter 4 is what ten weeks of this data already says about when to schedule what.
PreviousThe fix, screen by screenBack toThe noteNext chapterWhen Hennur plays