Touchline360 · Opposition · In development

See what the next opponent does, with the evidence behind it.

Competition and opponent intelligence designed around a concise opponent card, recent form, tactical tendencies, and explicit evidence strength.

The workflow problem

Keep the useful context moving.

Opposition preparation can produce too much information and too little prioritization. ScoutLens is being built to compress the next opponent into evidence-backed questions the staff can actually coach.

Built forAnalysts · Coaches
In developmentFocused tool

ScoutLens

This surface is actively being developed. The public product page shows what exists now and keeps unfinished work labeled as such.

Product proof

A real surface from ScoutLens.

Real in-development ScoutLens opponent card captured from the product behind its feature switch.

ScoutLens opponent card with observed, derived, and unavailable evidence labels
Real in-development ScoutLens opponent card captured from the product behind its feature switch.

Core capabilities

What this part of the coaching loop needs to do well.

Capability language is grounded in the current Touchline360 product registry and product documentation.

01

Summarize the next opponent into a small number of evidence-backed points

02

Keep observed, derived, and unavailable evidence visibly distinct

03

Connect recent form and tactical tendencies to preparation

04

Carry opponent context into the match plan rather than a detached report

Inputs

What comes in.

  • Competition data
  • Opponent matches
  • Team priorities
  • Evidence coverage

Outputs

What the staff gets back.

  • Opponent card
  • Preparation themes
  • Evidence strength
  • Match-plan questions

Touchline360 connection

PitchView → ScoutLens → match plan → Select XI

The suite is designed around one coaching loop: evidence, judgement, action, and the next evaluation.