This guide walks you through Performance Radar one piece at a time — what it is, when to use it, and what every button does. Read it start to finish, or jump to the part you need. Nothing here is urgent or complicated; if you ever feel stuck on the app, this page is meant to get you unstuck.
What it is
Performance Radar reads the transcript of a sales or customer call and gives it a score. The score answers one question: how much of the standard the manager set did this call actually meet?
It looks at ten specific selling skills — things like how the rep opened the call, whether they uncovered the real problem, how they handled pushback, and how they closed. For each one it gives an actual score, compares it to the level you expect, and rolls everything up into a single number with a short written explanation and a list of next steps.
It does not record calls or listen live. You give it a transcript that already exists, and it gives you a read on that one call.
Why we use it
Reviewing calls by hand is slow, and two people often grade the same call differently. Performance Radar applies the same standard to every call, so a score means the same thing across reps, managers, and weeks. That makes coaching fairer and the patterns easier to see.
It also makes the good stuff repeatable. When you can point to exactly which skills a call hit or missed — with the lines from the transcript behind each one — you can teach the rest of the team to do the same thing on purpose.
When to use it
Reach for it whenever you have a transcript and want a quick, even-handed read. Typically:
- Right after an important call, while it's still fresh.
- Before a one-to-one, to decide what to praise and what to work on.
- When you want to compare how a skill is landing across several calls.
- When a rep wants honest feedback on their own call before their manager sees it.
Who it helps
CROs & sales leaders
A consistent read on call quality across the whole team, so coaching and forecasts rest on the same yardstick instead of gut feel.
Enablement
See which skills are landing and which need training — based on real calls, not opinions — and measure whether training actually moved the number.
Front-line (Tier 1) managers
A second pair of eyes on each call before a one-to-one: what went well, what to fix, and the exact moments to point to.
Reps
A clear, specific read on your own call and a short list of what to do differently next time — no waiting, no guesswork.
The screen at a glance
The app is one page. From top to bottom you'll see:
- Top menu — links: Getting Started (this guide), Project Moneyball, and Sign out.
- Toolbar — the main action buttons: Import transcript, Run, Stop, Download PDF.
- Notifications & Runtime Monitor — the box on the left reports progress and warnings; the grid on the right lights up each skill as it's scored.
- Call Details — the rep, role, business, and call type, filled in for you after import.
- Final Score — the big number, its meaning, and how much of the call had evidence to score.
- Performance table — the actual result next to the expected minimum and weights you can adjust.
- Score Analysis & Recommendations — what worked, what didn't, and a single combined list of next steps.
Step by step
-
Import a transcript
Click Import transcript and pick a file, or drag the file onto the notification box. Plain text works best (.txt, .vtt, .srt, .md, .log, .csv). The app reads the call, works out the call type, and loads a matching scorecard.
-
Check the Call Details
The rep's name, role, business, and call type fill in automatically. These are read-only — they come from the transcript, so there's nothing to type.
-
Review the expected minimum and weights
In the performance table, each skill has an expected minimum (the bar you set, 1 to 5) and a weight (how much it counts). The defaults are already sensible. Adjust them if this call should be held to a different standard. See Expected minimum & weights for what each setting does.
-
Run
Click Run. The Runtime Monitor lights up each skill as it's scored. The first run on a new transcript takes a couple of minutes; after that, re-running is quick and free — until you change a setting, which scores again.
-
Read the score
The big circle shows the final number, with its meaning underneath (for example "Below expected") and how much of the call had evidence to score. Green means the call met or beat the standard, amber means it fell a little short, red means a serious gap. See Reading the score.
-
Read the analysis and next steps
Score Analysis lists what worked and what needs improvement. Recommendations is a single, de-duplicated list of next steps. Use the Copy button on either box to paste it into your notes or an email.
-
Download the report
Click Download PDF for a clean, one-page branded report you can save or share.
Every button explained
Top menu
| Button | What it does |
|---|---|
| Getting Started | Opens this guide in a new tab. |
| Project Moneyball | Opens the Project Moneyball website. |
| Sign out | Ends your session. You'll sign in again next time with a one-time PIN. |
Toolbar
| Button | What it does |
|---|---|
| Import transcript | Load a call transcript file (or drop the file onto the notification box). |
| Run | Score the call against the current expected minimum and weights. |
| Stop | Stop a run in progress and reset the screen. Re-import to start again. |
| Download PDF | Save a one-page branded report of the result. |
Performance table
| Button | What it does |
|---|---|
| Reset | Put the expected minimum and weights back to the call-type defaults. Active only once you've changed something. |
| Save template | Save your current expected minimum and weights under a name, to reuse later. |
| Open template | Load a built-in or previously saved template. |
| Copy | On the Score Analysis and Recommendations boxes — copies that box as plain text. |
Expected minimum & weights
These are the two dials you control for each skill. Together they tell the app what "good" means for this kind of call.
Expected minimum (the bar)
Click the segments to set the level you expect for a skill, from 1 to 5. The score for that skill is measured against this bar: meet it and the skill is on target, fall below it and it counts against the call.
Set the bar to 0 to make a skill optional. An optional skill is never required — if the rep does it, it adds a small bonus; if they don't, there's no penalty. Use this for skills that are nice-to-have on a given call type but not expected.
Weight (how much it counts)
| Weight | Counts as | Use it for |
|---|---|---|
| Standard | ×1 | A normal skill for this call. |
| Important | ×1.5 | A skill that matters more than usual here. |
| Critical | ×2 | A make-or-break skill for this call. |
Critical does one extra thing: it acts as a safety gate. If a critical skill badly misses its bar, the whole call's score is capped — so a strong call can't paper over a critical failure. More on that below.
Reading the score
The final score is built around 100. 100 means the call met exactly the standard you set. Above 100 means it beat the standard; below means it fell short. The scale runs up to 120.
| Score | Meaning | |
|---|---|---|
| Under 70 | Serious execution gap | Red |
| 70–84 | Below expected | Amber |
| 85–99 | Close, but not enough | Amber |
| 100 | Met manager expectation | Green |
| 101–120 | Exceeded expectation | Green |
Evidence coverage & confidence
Under the score you'll see something like "72% – Medium Confidence". Coverage is how much of the scorecard the call actually gave evidence to score — not every skill comes up on every call. Confidence follows from coverage: High at 85%+, Medium from 60–84%, Low below 60%. A lower coverage doesn't mean a bad call; it means there was less to go on, so read the score with that in mind.
When a score is capped
The app holds a score back in a few cases, so a high average can't hide a real problem:
- A critical skill far below its bar — the score is capped at 74.
- Two or more critical skills below target — capped at 79.
- Low coverage (under 60%) — capped at 79 and confidence set to Low.
A capped score shows in red as a flag that something needs a closer look.
The ten skills
Every call is scored on these ten. Each gets its own actual score, compared to your expected minimum.
| Skill | In plain terms |
|---|---|
| Setting Expectations | Did the rep agree the purpose, agenda, and outcome up front? |
| Call Prep | Did the rep recap earlier conversations and pick up where things left off? |
| Problem Development | Did the rep uncover the real business reason behind the buyer's need? |
| Moneyball Gap Identifier | Did the rep surface the gap between where the buyer is and where they want to be? |
| A-Ha Moment | Did the buyer have a genuine realization — not just polite agreement? |
| Objection Handling | How well did the rep deal with pushback and concerns? |
| Competitive Proactivity | Did the rep get ahead of rivals, build-vs-buy, and the "do nothing" option? |
| Domain Expertise | Did the rep know the buyer's world and speak their language? |
| Active Listening | Did the rep prove they heard the buyer — reflecting and reacting, not just pitching? |
| Next Steps | Did the call end with a clear next step both sides agreed to? |
Templates
A template is a saved set of expected minimums and weights. When you import a call, the app loads a template that fits the call type, so you rarely start from scratch.
- Save template — once you've set the bars and weights the way your team wants, save them under a name so everyone can reuse the same standard.
- Open template — load a built-in template or one you saved earlier.
- Reset — go back to the defaults for this call type if you've changed things and want to start over.
If something looks off
A few things you might run into, and what they mean:
A skill says it couldn't be scored
Sometimes a skill simply doesn't come up in a call, or the transcript is too short or unclear for that one. That skill is left out rather than guessed. If many skills drop out, coverage falls and you'll see a Low-confidence note — try a fuller transcript.
The score is in red / capped
That's the safety gate doing its job: a critical skill missed badly, or there wasn't enough evidence. It's a signal to look at the call more closely, not a glitch.
It says "AI unavailable" or a daily limit was reached
The scoring engine is briefly unreachable or has hit its limit for now. Nothing is broken on your side — wait a little and Run again.
The run won't start
Run only lights up once a transcript is loaded. If it's greyed out, import a transcript first. If a run is stuck, click Stop and re-import.
Still stuck? The notification box at the top of the app explains what's happening at each step — read the latest message there first. For anything else, reach out using the contact below.