Pitchside prospect lookup chat for scouts
Problem
A regional scout watching a lower-league fixture on a wet Tuesday night wants one answer before writing anything down: has the club already seen this player, and what did the last report conclude. The chief scout is off site, the analyst has gone home, and the prospect history lives partly in a scouting database only the office uses and partly across a shared spreadsheet with years of tabs nobody fully trusts. So the scout asks in the messaging group used for everything else and either waits two days for a reply or writes up a full report regardless, adding another entry for someone to notice as a duplicate weeks later. A player already on the watch list, already rejected, or already the subject of three unread reports gets assessed again anyway.
Product idea
A chat line scouts can message any time, from the ground or after, by typing a player's name and club. It searches the prospect history and replies with what is on file: prior assessment, verdict, scout, date, and current watch status. If nothing exists, it says so and logs the scout as now watching, so a second scout does not open the same player cold. Where the question needs judgement rather than a lookup, such as whether to escalate interest or approach a club, it stops short of answering and books a callback slot with the chief scout or head of recruitment instead. It does not write scouting reports or replace the database; it only tells a scout what is already known before they add to it.
Who it is for
Regional scouts checking a player before writing a report, and the chief scout or head of recruitment who sponsors it to stop duplicate assessments and unanswered late-night questions reaching them directly.
Possible first version
A text-based chat channel, not voice, built on a fixed prospect list loaded from a CSV export of the existing spreadsheet. It matches a typed player name and club, returns the most recent assessment summary and current watch status, and logs a new watcher when no record exists. Escalation offers a fixed set of callback slots rather than a live calendar. There is no voice recognition, no automated report writing and no live connection to the scouting database in version one; the CSV is re-uploaded on a schedule the recruitment team controls.
- Build classification
- Workflow application
- Rough effort
- 4-6 week first release
- Roles involved
- Regional scout, Chief scout, Head of recruitment
- Relevant to
- Professional club, Academy & youth, Collegiate athletics, Women's league
- Systems in play
- Scouting and recruitment databases, Spreadsheets and shared documents, Messaging apps
- Product framing
- Voice or chat interface
Questions we get asked
What has to be in place before we could even try this?
A recruitment analyst would need to export the current prospect list and its existing assessments into a single CSV, one row per report, with player name, club, verdict and date. Without that, the chat line has nothing to search and every answer becomes 'no record found', which is not a useful demonstration. The export does not need to be tidy, just complete enough to cover the players scouts are actually asking about, which is usually a few hundred names rather than the whole historical archive.
Does this replace the scouting database we already pay for?
No. The database stays the system of record for full reports, ratings and history; this sits in front of it as a fast-answer layer for the specific question a scout has mid-match. Version one does not even connect to the database directly. It reads a CSV snapshot the analyst refreshes on a schedule, so an answer is only as current as the last export, not the live record. That is a limitation worth knowing before anyone relies on it for a decision that matters.
Our scouts already have a group chat for exactly this. Why would they use something else?
The group chat is where scouts talk tactics and logistics, and it will stay that way. The problem is that a specific question about one player gets lost in that stream within a day, and nobody can search it reliably later. This gives that one question a dedicated place with a structured answer instead of a scroll-back exercise. If scouts keep asking in the group anyway, that is a sign the chat line is not answering fast enough or clearly enough, and worth fixing before pushing adoption harder.
What happens if a scout messages from a ground with no signal, or at eleven at night?
The message queues on the phone and sends once it reconnects, and the answer comes back the same way with no human involved, because it is reading a snapshot rather than asking a person. Eleven at night is not a special case here; the chat line has no office hours because there is no office behind it. The only time a human enters the loop is when the question genuinely needs judgement, and that produces a booked callback for the next working day rather than an immediate answer.
Is this your workflow?
Tell us one sports workflow that still runs on paper, spreadsheets, WhatsApp or an outdated system. We will map it and show you what a simpler product looks like.
Tell us about itMore in Scouting & recruitment
- Player approach and agent-contact clearance trackerA workflow that routes a scout's request to approach a player, guardian or agent through formal sign-off, logging who approved contact and when, in place of a phone call or group chat message nobody records.
- Scout report intake and duplicate-assessment routerA workflow that matches new scout reports against existing prospect records, routes them for triage and chases overdue watch list assignments so no player gets assessed twice or forgotten.
- Voice capture for trial day player evaluationsA voice tool that lets evaluators dictate structured ratings on each trial player station by station, removing the paper card and the evening typing-up that loses detail.