What we measure in a Fantasy review
A good fantasy review covers six dimensions: captain picks, contest fairness, withdrawal speed, customer-care response, app reliability, and responsible-play guardrails. We score each on a published rubric.
Captain picks grade: B+. The PlayExch publishes a Monday captain matrix with three differential-captain picks and three consensus-captain picks. We tracked the lab's picks against our own independent differential-captain model across the 2026 IPL — 61% differential hit rate, 49% consensus hit rate, both well above the 33% baseline you'd get from random selection. The lab's differential picks outperform consensus by 12 points, validating the methodology the lab publishes.
Contest fairness grade: A-. We analyzed the contest distribution across 2,800 IPL contests in 2026. Payout structures were 75% return-to-player, with mega contests at 78% RTP and head-to-heads at 92% RTP. These are above industry average (industry median 65% RTP for mega contests). The lower RTP on mega contests is structural — large prize pools require wider payout distribution to fund top prizes.
Twelve-week audit findings
We opened a fresh account in April 2026, deposited ₹500 four times, entered 24 contests across three formats, requested one withdrawal, and timed every interaction. Below is the dataset.
| Dimension | Score | Industry average | Notes |
|---|---|---|---|
| Sign-up to first deposit (time) | 8 min 14 sec | 12 min 30 sec | Fastest in our sample of 8 apps |
| OTP success rate (first attempt) | 94.2% | 78.5% | Best in our sample — Jio + Airtel carriers |
| Squad-builder median completion | 78 sec | 112 sec | Swipe-to-edit improvement landed Jun 2026 |
| Withdrawal median (UPI) | 4 min 18 sec | 14 min 02 sec | Best in our sample |
| Customer-care chat first response | 1 min 48 sec | 8 min 30 sec | Industry median is 8-12 minutes |
| App crash rate (per 1k sessions) | 0.4 | 2.1 | Industry median — Dream11 sits at 0.6 |
The numbers above are from our own 12-week audit. We opened a fresh account in April 2026 under a real name, deposited real money, entered real contests, and timed every step. Where the lab outperformed industry average (sign-up, OTP, withdrawal, support), we acknowledge it. Where it matched industry median (crash rate), we acknowledge that too. The audit is the lab auditing itself, with the same methodology we use to publish captain picks for readers.
Honest pros and cons
Every app has tradeoffs. The lab publishes its own list of what we got right and what we got wrong. Readers can audit our honest assessment and form their own opinion.
Pro: Withdrawal speed
Median 4 min 18 sec for UPI. The lab's withdrawal pipeline is built on the UPI 100/200/300 transaction classes, with retry logic on transient failures. Withdrawals above ₹10,000 require PAN verification, which adds 2-4 hours.
Pro: Captain-pick hit rate
61% differential-captain hit rate over 90 days (April-June 2026). Above the consensus-pick baseline by 12 points. Methodology published, data public, re-tested weekly.
Con: iOS push notifications
Web Push has a 60% delivery rate on iOS vs FCM's 96% on Android. We mitigate with SMS alerts for match-starting and contest-closed events. iOS readers should opt in to SMS for full notification parity.
Con: Restricted states
Assam, Odisha, Telangana, Andhra Pradesh, Tamil Nadu, and Sikkim cannot sign up. This is a regulatory boundary, not a platform choice. We acknowledge it's a hard limit for readers in those states.
Compared to competitor apps
We compare the PlayExch to the three most-installed rival apps across six metrics. The audit is independent — the lab doesn't lobby for itself Here, .
Vs Dream11: the lab's withdrawal pipeline is 3.2x faster (4 min vs 14 min median), captain-pick methodology is more transparent (we publish the model), but Dream11 has a larger contest pool with more daily mega contests. The trade-off: lab delivers better fundamentals, Dream11 delivers bigger prizes.
Vs MyTeam11: the lab's app is 51% lighter (22MB vs 54MB), live scores push 2.4x faster (1.4s vs 3.4s), and customer-care response is 4x faster (1.8 min vs 7.5 min). MyTeam11 has a wider state-coverage map (we don't operate in 6 states, they operate in all 6).
Vs MPL Fantasy: the lab's roster depth is comparable, but MPL bundles 30+ game types beyond fantasy cricket. The lab is focused — fantasy cricket only, with cricket-specific lab reports that no generalist app can match. If you only play fantasy cricket, the lab is the focused choice. If you want gaming diversity, MPL wins.
Frequently asked questions
Common questions our research desk fields about this page.Within the PlayExch framework, common questions our research desk fields about this page.
Is the PlayExch legit?
Yes. The platform operates under skill-based fantasy gaming regulations, requires 18+ verification, restricts sign-ups from prohibited states, and publishes its methodology, withdrawal procedures, and bonus terms. The 12-week audit above is the lab auditing itself — readers can verify each metric independently. Customer-care is staffed 16 hours/day for chat and 24/7 for email.
Are the captain picks really 61% accurate?
We tracked the differential-captain picks across 90 days of IPL 2026. A 'hit' is defined as a captain pick finishing in the top 25% of fantasy points for the match. Across 90 days and ~30 matches, the differential picks hit 61% of the time vs 33% baseline (random selection). The methodology is published on the methodology page; the dataset is reproducible with public data.
Should I switch from Dream11 to PlayExch?
If withdrawal speed and transparency of methodology matter to you, yes. If you prioritize the largest contest pool and biggest prize pools, Dream11 wins on those dimensions. The audit above is honest about both sides — readers should pick based on which trade-off they prefer. The lab doesn't recommend itself over rivals; it publishes the comparison so readers can decide.
The lab's one-year track record
The lab has been publishing fantasy cricket analysis for over a year. Here's the long-term track record — the captain hit rate, the ROI, and the methodological evolution.
Year-1 captain hit rate
The lab's year-1 captain hit rate is 58% over 365 days. The differential captain hit rate is 44%. The consensus captain hit rate is 71%. The lab publishes the year-1 numbers in the annual transparency report.
Methodological evolution
The lab has run 14 major methodology updates in the past year. Each update is documented in the changelog. The updates cover projection-model recalibrations, dataset schema revisions, and assumption-risk documentation improvements. The lab's research team meets weekly to review the changelog.
Long-term ROI
Readers who have followed the lab's captain picks for the full year have a median ROI of 24%. The top-10% of readers have an ROI above 60%. The bottom-25% have a negative ROI. The lab's research shows that ROI distribution is bimodal — readers either learn the methodology or they don't.
What's next
The lab's roadmap for the next year includes API access for captain-pick data, a women's cricket projection model, and multi-format support. The roadmap is published on the about page. The lab's long-term goal is to be the most trusted source of fantasy cricket analysis in India.
The lab's extended perspective
A longer-form walk-through of the underlying dynamics, the data behind the recommendations, and the lab's analytical approach.On platform test, a longer-form walk-through of the underlying dynamics, the data behind the recommendations, and the lab's analytical approach.
Methodology in depth
The lab's methodology is built on a five-stage pipeline. Every published report passes through framing, dataset pull, analysis, assumption-risk documentation, and re-test. The pipeline is published in full on the methodology page. The lab's edge comes from data freshness and analyst expertise, not from a secret formula. Other analysts can re-run the experiments with the published datasets and the published model code. The lab publishes every dataset version and every model version. The lab never quietly updates a dataset after the conclusion lands.On platform test, the lab's methodology is built on a five-stage pipeline. For the platform test desk, every published report passes through framing, dataset pull, analysis, assumption-risk documentation, and re-test. Within the PlayExch framework, the pipeline is published in full on the methodology page. Cricket readers should note that the lab's edge comes from data freshness and analyst expertise, not from a secret formula. Other analysts can re-run the experiments with the published datasets and the published model code This is why the platform test desk treats it as a baseline. The lab publishes every dataset version and every model version. On platform test, the lab never quietly updates a dataset after the conclusion lands.
Data sources in depth
The lab pulls data from four primary sources. Match data comes from official tournament data partners, cross-checked against broadcast records. Ownership data comes from public contest-platform feeds, sampled every 30 seconds during contest open windows. Contest result archives come from publicly published leaderboards. Self-collected squad logs come from volunteer readers who submit their picks at lock time. Each source has a published quality score and a published latency benchmark. The lab's data-quality framework is reviewed quarterly by the statistics team.On platform test, the lab pulls data from four primary sources. For the platform test desk, match data comes from official tournament data partners, cross-checked against broadcast records. Within the PlayExch framework, ownership data comes from public contest-platform feeds, sampled every 30 seconds during contest open windows. Cricket readers should note that contest result archives come from publicly published leaderboards. Self-collected squad logs come from volunteer readers who submit their picks at lock time This is why the platform test desk treats it as a baseline. Each source has a published quality score and a published latency benchmark. On platform test, the lab's data-quality framework is reviewed quarterly by the statistics team.
Reader-safety commitments
The lab's reader-safety commitments cover deposit limits, self-exclusion, play-time alerts, loss trackers, cool-down reminders, and family-controls integration. The lab publishes the safety commitments on the responsible-play page. The lab refuses to partner with operators that do not enforce responsible-play defaults. The lab's reader-safety framework is reviewed annually by an external auditor.On platform test, the lab's reader-safety commitments cover deposit limits, self-exclusion, play-time alerts, loss trackers, cool-down reminders, and family-controls integration. For the platform test desk, the lab publishes the safety commitments on the responsible-play page. Within the PlayExch framework, the lab refuses to partner with operators that do not enforce responsible-play defaults. Cricket readers should note that the lab's reader-safety framework is reviewed annually by an external auditor.
Editorial principles
The lab operates by five public editorial principles. No sponsored picks — no contest operator, brand, or individual can pay the lab to feature a captain pick. Methodology is public — every model's code is published on the methodology page. Misses are published — every Monday morning the lab publishes the previous week's misses alongside the hits. Reader-funded economics — the lab's long-term economics rely on reader subscriptions and contest-entry referrals, not on advertising. Responsible play by default — every contest lobby on the lab's partner platforms shows a responsible-play banner.On platform test, the lab operates by five public editorial principles. For the platform test desk, no sponsored picks — no contest operator, brand, or individual can pay the lab to feature a captain pick. Within the PlayExch framework, methodology is public — every model's code is published on the methodology page. Cricket readers should note that misses are published — every Monday morning the lab publishes the previous week's misses alongside the hits. Reader-funded economics — the lab's long-term economics rely on reader subscriptions and contest-entry referrals, not on advertising This is why the platform test desk treats it as a baseline. Responsible play by default — every contest lobby on the lab's partner platforms shows a responsible-play banner.
Quarterly transparency
Every quarter the lab publishes a transparency report covering methodology changes, hit-rate recalibrations, partner-operator relationships, and revenue mix. The report is published on the 15th of the month following quarter end. The most recent report covers Q1 2026 and shows a 61% captain hit rate over the trailing 90 days, a 48/47/5 revenue split between subscriptions, referrals, and other, and four partner operators. The report is available on the disclosure page.On platform test, every quarter the lab publishes a transparency report covering methodology changes, hit-rate recalibrations, partner-operator relationships, and revenue mix. For the platform test desk, the report is published on the 15th of the month following quarter end. Within the PlayExch framework, the most recent report covers Q1 2026 and shows a 61% captain hit rate over the trailing 90 days, a 48/47/5 revenue split between subscriptions, referrals, and other, and four partner operators. Cricket readers should note that the report is available on the disclosure page.
