revenue-reportinglisted
Install: claude install-skill mbfinotti/revops-skills
# Revenue Reporting
Build the executive or board revenue report as one coherent story: a small, stable metric spine wrapped in an answer-first narrative organized around plan vs. actual vs. forecast. The hard part is rarely the arithmetic - it is agreeing on definitions, reconciling the CRM record against the finance record, and making sure the board never learns bad news live.
Scope boundary, stated up front:
**In scope:**
- What goes in the report and how it reads.
- The number and its confidence.
**Out of scope:**
- Building a dashboard in any specific BI tool.
- Designing the org-level KPI framework (which metrics matter at which org level and how they roll up) - a separate strategy exercise outside this repository.
- Investigating why a forecast was wrong - hand that to `mbfinotti/revops-skills@sales-forecast-diagnostic`, then use this skill to turn the finished diagnosis into the board narrative.
## Interview
Ask before proposing anything. One question per message; offer multiple-choice options when possible. Skip anything already answered.
- What is the business model - B2B contract subscription, usage/consumption-based, PLG/self-serve, B2C/transactional/marketplace, or mixed?
- Which artifact is being built - quarterly board deck, monthly executive review, weekly revenue review, an investor update, or the whole cadence stack?
- What stage is the company - pre-institutional, early venture, growth, or late? (The spine tightens and shifts with stage.)
- What exi