Overview
A GTM scorecard helps a revenue operations lead keep pipeline, demand, conversion, campaigns, and owner actions in one recurring operating review. This playbook installs a scorecard page and metrics table so the team is not rebuilding the same deck or workbook every week.
Use it when the numbers are scattered across exports, pasted updates, meeting notes, and half-remembered targets. Juno starts from the metrics you provide, labels the source and freshness of each row, and turns the scorecard into a durable view the team can refresh weekly or monthly.
It does not pretend to replace a full data warehouse or automatically ingest every CRM and analytics system. The narrow job is simpler and more useful: keep the GTM read, caveats, and next owner actions together.
Why you should keep GTM health in one scorecard
GTM reviews get noisy when sales, marketing, demand generation, and campaign owners each bring a different reporting surface. A pipeline miss may actually be a demand problem, a conversion issue, a campaign timing gap, or a stale source. The scorecard gives those signals one operating frame.
That cross-functional frame is exactly where revenue operations lives. Gartner describes RevOps as aligning sales, marketing, and customer success around revenue growth (Gartner). Salesforce makes the same practical point for sales and marketing alignment: shared KPIs and common definitions help teams measure total pipeline health rather than isolated activity (Salesforce).
Juno keeps the useful friction in the process. Missing targets stay visible. Manual updates are labeled. Owner actions do not drift away from the metric that created them. The result is less "which number are we using?" and more "what needs a decision before the next review?"
Step-by-step
- 1Confirm the company or business unit, reporting period, GTM motion, scorecard sections, starter metrics, targets, and whether the workspace should run once, weekly, or monthly.
- 2Set up the installed scorecard workspace with a primary GTM scorecard page and a metrics table that preserves definitions, caveats, and open questions.
- 3Load the latest user-supplied metrics from pasted updates, uploaded exports, existing workspace tables, or manual owner notes, then attach source and freshness context to each row.
- 4Group the scorecard around the operating questions: whether pipeline is healthy, demand is creating enough qualified motion, conversion is holding, campaigns are contributing, and owners have clear next actions.
- 5Compare metrics against targets, prior periods, or supplied benchmarks where available, while marking missing, stale, delayed, or low-confidence inputs instead of smoothing them away.
- 6Refresh the scorecard page and metric rows so the revenue operations lead can run the next GTM review from one place.
Frequently asked questions
What does this replace?
It replaces a narrow GTM scorecard deck or workbook: the recurring place where pipeline, demand, conversion, campaign movement, caveats, and owner actions are reviewed. It does not replace a CRM, warehouse, or full BI stack.
What metrics should I include?
Start with the metrics already used in your GTM meeting: pipeline created, pipeline coverage, MQLs, demo requests, conversion rate, campaign-sourced pipeline, sales follow-up, channel pacing, or owner action status.
Does it require connected source systems?
No. The default workflow uses metrics supplied in the workspace, pasted into the task, uploaded as files, or already stored in Juno tables. Source-specific automation can be added later, but it is not required for the minimum replacement.
How often should the scorecard run?
Weekly works well for active operating reviews, while monthly fits leadership summaries or slower motions. Keep it as run-once while the team is still agreeing on metric definitions and targets.