A dashboard is a set of questions with numbers attached.
A free Claude skill that specs your GTM reporting before anyone opens Looker: audience, the 5–7 questions that matter, engineer-grade metric definitions, tile-by-tile layout, and the data gaps that would sink it.
FREE · BUILT BY GROW & CLOSE · WORKS IN CLAUDE + CLAUDE CODE
INPUT
Who looks at the dashboard and when, your stack (CRM, analytics, spreadsheets), and how you define a qualified opportunity today — even if the answer is “we argue about it.”
OUTPUT
Metric: Qualified pipeline created · Formula: Σ opportunity amount where created in period and stage ≥ SQL · Source: HubSpot, Opportunity object · Exclusions: renewals, test accounts · Owner: RevOps · Target: 4× coverage of next-quarter number
WHAT THE SKILL DOES
Method, not magic.
- 01Separates operator, leadership, and board dashboards instead of building one for all three
- 02Writes the questions first — every metric must serve one or gets cut
- 03Defines each metric like an engineer: formula, source, filters, owner, target
- 04Forces decisions on the classic ambiguities: MQL definition, attribution model, date basis
- 05Names every data gap and its workaround, so the dashboard survives week 2
Who it’s for: Founders, marketing leaders, and RevOps at B2B SaaS companies whose reporting is a pile of contested numbers, or who are standing up pipeline reporting for the first time.
HOW IT WORKS
Three steps to a working skill.
Download and install
Get the .skill file by email and add it to Claude via Settings → Capabilities → Skills.
Answer the audience questions
The skill pins down who the dashboard is for and what they argue about — the questions become the spec's skeleton.
Hand off the spec
One document: questions, metric definition blocks, layout with the top-left tile first, data gaps, and an ordered build checklist for whoever implements it.
GET THE SKILL
Free. Yours. Installed in two minutes.
Enter your email and we’ll send the GTM Dashboard Spec .skill file plus the install steps. One email, no drip campaign ambush.
QUESTIONS, ANSWERED
Before you install.
01Which tools does the spec work with?+
Any — Looker, Metabase, HubSpot, Salesforce dashboards, or a spreadsheet. The spec is deliberately tool-agnostic: questions, definitions, and layout are the hard part; charting is the easy part.
02What GTM metrics should a B2B SaaS team track?+
Depends on the audience: operators need campaign-level qualified pipeline and stall points weekly; leadership needs coverage, CAC payback, and win-rate movement; boards need efficiency (burn multiple, magic number) and forecast accuracy. The skill builds the right set per audience instead of a 40-tile wall.
03How does it handle attribution?+
It forces you to pick one model, name its known bias, and move on — because teams that argue about attribution ship no reporting at all. The spec records the choice so future arguments have a written baseline.
04What if our data is too messy for a dashboard?+
That's step five of the workflow: every metric the stack can't produce cleanly gets listed with the missing piece and an interim workaround. A spec that pretends the data is clean gets abandoned in two weeks.