One brief, one watchlist, one shortlist you can defend.
The four moments from the scouting use case, walked through the actual product — the review inbox, the record detail, the proposal frame, the briefing, a chat answer. Nothing here is a mock-up of a screen Frontless does not have.
A club emails the search brief. Forward it to Frontless and the mandate lands in your pipeline — criteria parsed, deadlines noted, follow-up scheduled.
New recordNew Mandate — "Centre-back, summer window" for FC Lakeshore, stage active search, ceiling €15,000,000.00, salary band €1,200,000.00/year, window closes Sep 1
New recordNew Task — "Shortlist back to Lakeshore", due Mar 22, assigned to Noor Haddad
Already applied
auto Filed the brief and its attachment against FC Lakeshore — source: email.
auto Matched the sender to Roland Kovacs, sporting director, an existing contact at 97%.
A forwarded email never writes to your records on its own. Anything that would is queued here, under the message it came from.
Fixed data, real surfaces. The proposal, answer and confirmation frames are the
product’s own components; the briefing, grid and record detail are read-only twins of
theirs, built from the same markup. space plays and pauses, ←→ step.
Four moments, one spine.
The brief, the feed, the shortlist and the placement record all landed on the same records. That is why the shortlist could filter on criteria nobody re-typed, why a player carried three sources at once, and why the placement answer knew which brief each transfer was made against.
Nothing was written without you approving it first.
Every value carries where it came from — a feed, an email, a rule, or a scout’s own hand.
The fit score is fit to the brief — and it names what it could not satisfy.