Padel Coaching Tech — Independent Research
An evidence-graded research portfolio on padel coaching technology in 2026. Eight pages cover the competitor landscape, subscription economics, an MVP design, a first-quarter operating plan, and full disclosure of every AI model used to produce the research. Every numeric claim cites a verifiable source URL fetched at the time of writing.
Read the strategic work
Strategic brief →
Eighteen sections on market sizing, jobs to be done, the competitive landscape, defensibility, go-to-market, risks, and pivot triggers.
Evidence map →
Source trace for the brief — every claim paired with the verbatim source quote and the URL it came from.
Methodology →
How the research was built: agents, models, evidence gates, mobile-first rendering, adversarial review.
Read the supporting analyses
Competitor landscape →
Padel coaching apps, club software, and racket-sport AI. Who has the data moats and where the white space is.
Subscription economics →
Eight pricing anchors verified May 2026. LTV/CAC by channel across four geographic scenarios.
MVP design →
The smallest product loop that earns the right to exist. Three pilot tracks compared, decision tree, risk register.
90-day plan →
Twelve testable hypotheses for the first quarter. A metric tree from the headline number down to weekly leading indicators.
Model provenance →
Every AI model used in the research, by billing class. Paid Anthropic, paid Perplexity, plus a free Alibaba arm as a cross-check.
What this work shows
- Research as a build, not a document. Schemas, fail-fast quality gates, immutable canonical state, regression rules added every time something fails.
- Multi-model orchestration. Strategic models plan and adversarially review. Three deep-research workers fan out in parallel. Smaller models structure the data. Python runs every calculation.
- Evidence over polish. Three rules govern every output. Every number has a verified source URL. Quotes are at most fifteen words verbatim from the source. A documented gap is more honest than a fabricated number.
- Mobile-first frontend. Vanilla HTML and CSS. No framework. No build step. Audited across five device profiles before each release.
- Open and reproducible. The whole pipeline ships as static HTML and the source repository contains every prompt, every script, and every quality gate.