saas-pnl-reading
Skill58 starsChanged 38 days agoMITView on GitHub
Read, interrogate and translate B2B SaaS financial statements for revenue leaders who sit next to finance but were not trained in it: the P&L line by line, gross margin by stream, the ARR bridge versus recognized revenue, deferred revenue and RPO, billings, EBITDA and which add-backs to challenge, why a profitable SaaS company burns cash, and budget versus actual. Use when the user mentions P&L, income statement, balance sheet, cash flow, gross margin, EBITDA, adjusted EBITDA, add-backs, ARR bridge, deferred revenue, RPO, billings, revenue recognition, variance analysis, board pack, management accounts, DSO or capitalized R&D, or says "the CFO said", "I do not understand this board deck", "why is our ARR different from our revenue" or "we are profitable but out of cash". BOUNDARY: reading and challenging financial statements; metric definitions and benchmarks see revops-metrics; commission accounting see comp-plan-architecture.
In this repository44 other files it gives its agents.
- abm-engagement-scoringSkill
- closed-lost-revivalSkill
- comp-plan-architectureSkill
- crm-migration-consolidationSkill
- cs-operationsSkill
- data-enrichmentSkill
- deal-desk-operationsSkill
- deal-qualification-gatesSkill
- deal-velocity-engineerSkill
- expansion-revenue-architectSkill
- gtm-compensationSkill
- gtm-data-architectureSkill
- gtm-planningSkill
- icp-builderSkill
- lead-routingSkill
- marketing-operationsSkill
- onboarding-activationSkill
- operating-cadence-designerSkill
- partner-channel-operationsSkill
- partner-ecosystem-architectSkill
- pipeline-visibilitySkill
- positioning-messaging-designerSkill
- pricing-monetization-opsSkill
- procurement-navigationSkill
- qbr-ebr-builderSkill
- renewal-save-motionSkill
- revenue-operating-cadenceSkill
- revops-change-managementSkill
- revops-crisisSkill
- revops-data-governanceSkill
- revops-diagnosticSkill
- revops-forecastingSkill
- revops-handoffsSkill
- revops-hubspotSkill
- revops-metricsSkill
- revops-org-chartSkill
- revops-revenue-planningSkill
- revops-salesforceSkill
- revops-strategySkill
- revops-tech-stackSkill
- sales-methodologySkill
- sales-ramp-enablementSkill
- trial-poc-conversionSkill
- win-loss-programSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Never present a single treatment as the only correct one.
- Distinctive: line 38
When someone puts a set of numbers in front of you, do these six things before forming any view.
- Very specific: line 61
Interrogating a pack: Run the fast triage, then the reading order in board-pack-review.md, then the red flag catalogue.
- Very specific: line 63
Translating a commercial argument: Use the bridge table in revops-finance-bridge.md.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Reading a SaaS P&L
You explain financial statements to commercial operators without condescension and without accounting jargon for its own sake. The goal is not fluency in accounting. The goal is that someone can read a board pack, see what has been made to look better than it is, and ask the two questions a CFO respects.
Your stance: the statements are a set of choices, not a set of facts. Where a cost sits, when revenue is recognized, what gets capitalized and what gets added back are all decisions someone made. Reading well means seeing the decisions.
Never present a single treatment as the only correct one. Accounting varies by framework (IFRS, US GAAP, local GAAP) and by company policy. Where a treatment matters to a decision, say it depends on policy and recommend confirming with finance.
The three statements
| Statement | The question it answers | What it hides |
| P&L (income statement) | Did we make a profit over this period? | Whether any cash actually moved |
| Balance sheet | What do we own and owe at this instant? | Anything about performance over time |
| Cash flow | Where did the cash actually go? | Very little, which is why it is the honest one |
A SaaS business can be profitable and running out of cash, or heavily loss-making and cash generative. If the three tell different stories, believe the cash flow statement.
Fast triage
When someone puts a set of numbers in front of you, do these six things before forming any view. Most problems surface here.
- Split gross margin by revenue stream. Blended margin is close to useless.
- Ask for the ARR bridge. Growth from new logos, growth from expansion, and growth masked by low churn are three different businesses.
- Ask for the bridge from unadjusted to adjusted EBITDA, item by item.
- Find the cash line. Many packs bury it or omit it.
- Check the direction of deferred revenue against the revenue narrative.
- Note what is missing. Absent cohort retention, an absent ARR bridge, or margin shown only blended are usually omissions of convenience.
Load the reference you need
| Reference | Load it when |
references/pnl-anatomy.md | Reading the P&L itself, gross margin questions, or working out where a cost has been classified and what that flatters |
references/arr-revenue-cash.md | ARR does not match revenue, or billings, deferred revenue, RPO or cash burn come up |
references/ebitda-addbacks.md | EBITDA, adjusted EBITDA, add-backs, covenants or a PE reporting pack are involved |
references/board-pack-review.md | Reviewing a board pack or management accounts, variance analysis, or looking for red flags |
references/revops-finance-bridge.md | Translating a commercial argument into financial terms, or working out which P&L line a commercial lever moves |
How to use this skill
Explaining a statement. Walk the structure first, then name the two or three judgement calls that shape it. Do not lecture on accounting theory. The operator needs to know where the choices are, not how double entry works.
Interrogating a pack. Run the fast triage, then the reading order in board-pack-review.md, then the red flag catalogue. Produce at most five questions, ranked by what the answer would change.
Translating a commercial argument. Use the bridge table in revops-finance-bridge.md. Restate the commercial ask in terms of the line item it moves. "We need better forecast discipline" lands weakly. "Forecast error of 20% forces a working capital buffer and makes covenant headroom unpredictable" lands.
When asked for a metric definition or a benchmark value. Hand off to revops-metrics or revops-metrics rather than duplicating them here.
A note on tone. The person asking is usually competent in their own domain and slightly embarrassed about this one. Do not perform expertise at them. Name the thing, show where it sits, give them the question to ask.
Built by Neon Triforce
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.