Methodology

How we frame football data for defendable shortlist decisions.

Tifolab is built to be useful before it is impressive. This page explains the assumptions behind the public surface so users know what the product is measuring, what it is not, and where the launch boundary sits.

Public launch scope

What is live, and what stays out of the trust page.

Live
  • Player search, shortlist, and comparison flows that are stable enough to defend publicly.
  • 51 domestic leagues and 79 indexed competitions on the current public surface.
  • Two current seasons, role presets, and plain-language metric definitions.
Held back
  • Accounts and billing remain separate from the trust page.
  • Anything unfinished stays hidden instead of being described as part of the launch.
  • Coverage claims stay aligned with the current public product surface.
Principles

The page is a trust asset, not a feature dump.

These are the rules that keep the public surface honest while the launch is still narrowing.

Strong defaults over open-ended dashboards

Tifolab keeps the workflow opinionated. Role presets define the metric lens, tables stay readable, and compare surfaces stay focused instead of turning into dashboard sprawl.

Context before conclusion

Raw output, percentile context, and similar-player comparisons are designed to be read together. No single card is meant to replace scouting judgment or role-specific film review.

Narrow public scope

The public launch covers the current discovery and comparison surfaces we can defend consistently. Less obvious or less stable features stay out of sight until they are trustworthy.

Interpretation

Read the output as directional evidence.

The public pages compress a larger analytical process. The goal is to help users narrow attention quickly without pretending the product can make the decision for them.

The system is built around shortlist work: a small number of role-aware presets, a consistent way to compare players, and supporting notes that make the output easier to read in context.

Percentiles+

Percentiles are precomputed for a season and role bucket so player profiles can load fast. A 90th percentile marker means a player ranks above most peers in that scoped sample, not that the raw value itself is universally elite.

Similarity+

Similar-player results come from normalized vectors that emphasize profile shape rather than raw totals alone. Minutes thresholds and role buckets are applied before ranking so the comparisons stay directionally useful.

Compare views+

Compare cards and profile summaries compress a larger analytical process. They are meant to accelerate a decision, not replace the deeper profile and match context behind it.

Match ratings+

Per-match ratings are sourced from API-Football on a 0-10 scale. They reflect a statistical composite of a player’s in-game actions. Season averages are the mean of all rated appearances, and ratings are independent of percentile rankings.

Why the scope stays narrow

Trust improves when the public page is honest about limits.

Tifolab is intentionally not framed as a dashboard that does everything. It is a working surface for discovery, comparison, and evidence-led shortlisting. That means the pages need to say less and defend it better.

Coverage note

The public surface is grounded in the current 51-league coverage and its companion competitions, so the pages do not make promises the data layer cannot keep.

That constraint is a feature, not a weakness. It keeps the marketing pages aligned with the product and makes the trust story easier to defend.