The Standings table block was built for a sports season table, but the mechanic — rows sorted by one number, top three medaled — is exactly what a sales leaderboard needs, rendered as a real HTML table in every client, Outlook included.
A leaderboard that only looks right in Gmail isn't much of a leaderboard for the half of a sales team still on Outlook.
One row per rep
Team holds the rep's name, and Points holds whatever number should rank them — revenue closed, deals won, calls converted. Rows sort by Points descending automatically, with a 🥇🥈🥉 badge on the top three.
The column headers are fixed — and abbreviated in the mailed table
Team, Played, Won, Drawn, Lost, Points for, Points against, and Points label the row-editing fields in the Studio, and none of them rename. The mailed table itself is more compact: its header row reads Team, P, W, D, L, PF, PA, Pts. It reads most naturally when your metric maps onto that shape (calls attempted/won/lost). If it doesn't, leave the extra columns at 0 and lead with Team and Points — those two are what actually drive the ranking and medals, regardless of what the other columns show.
Highlight your own team
Highlight team matches a row's Team value case-insensitively and bolds/tints it — useful for a manager's own digest sent per-team via an audience filter, so each manager's version highlights their own report.
No live binding yet
Unlike the KPI/bar/line/pie chart family, Standings table is authored-rows only — you (or a quick export from your CRM) update the rows by hand before each send.
Getting started
Add a Standings table block, list your reps as rows with Points as the number to rank by, turn off Show draws, and set Highlight team to call out a specific rep.