Sample email
What a Gridside email looks like
One email before every race weekend, written for your team, budget, free transfers and chips. It takes under two minutes to act on.
Example from Round 16, Bahrain GP at Sepang, October 2026. Written for a real team with $0.7M left in the cost cap.
Gridside
hello@gridside.app
Ocon out, Bearman in · Bahrain GP, Round 16
TRANSFER
Esteban Ocon out, Oliver Bearman in
Same Haas car, $3.5M cheaper, and Bearman finished P9 in Baku. Fits your budget with room to spare.
BOOST
Kimi Antonelli
Already your Boost, so keep it there. P5, P1, P1 in his last three races, and Mercedes bring upgrades to Sepang.
CHIP
Hold
Save Final Fix for Singapore (Round 17), a Sprint weekend on a street circuit where a poor qualifying is hard to recover from.
CONFIDENCE
An 86% rain forecast at a circuit F1 hasn't raced on since 2017 makes this weekend hard to call.
What changes for your team
The calls above were written for one team. Your email is written from your own inputs, so another team at the same race gets a different email.
- Your drivers and constructors. Ocon was in this team, so the transfer starts there.
- Your cost cap. This team had $0.7M left. Every transfer is checked against current prices before the email is sent.
- Your free transfers. How many you have decides whether a move is worth making this week.
- Your Boost. Antonelli already held it, so the email says to keep it there.
- The chips you have left. Final Fix was still available, so the email holds it for a race where it is more useful.
- The weekend ahead. Results and form from the last races, the circuit, the weather forecast and the news.
Want the call written for your own team, budget and chips?
Decision support, not a guarantee.