Step 1
Forecast variance equals actual minus forecast, divided by forecast.
Public tool method · Version 1.0.0
Revenue Story
Use this method when you need to answer: Does the growth narrative match the mechanics producing revenue? It turns the evidence you supply into a Revenue dependency model by applying explicit, versioned decision rules. The result is not a benchmark or certification. It shows the strongest evidence, riskiest input, next action, owner, and review date so another reader can inspect and challenge the decision.
Last material review 2026-08-08 · Next review 2026-11-06
Question answered
Does the growth narrative match the mechanics producing revenue?
The revenue dependency model compares concentration, recurring share, forecast variance, attribution confidence, retention, and the narrative claim.
Step 2
A dependency is fragile when channel share is at least 40%, recurring share is below 50%, absolute forecast variance is at least 20%, or attribution confidence is below 50%.
Step 3
Estimated repeatable share sums each revenue share multiplied by its recurring share.
Step 4
Record the required inputs and label missing or estimated evidence before classification.
Step 5
Apply the versioned decision rule and preserve the reason behind each row state.
Assumptions and limits
- Raw amounts remain local and user-supplied; the model is not an audit.
Usefulness hypothesis
A dependency model reveals fragile growth hidden by aggregate narrative.
Primary metric: Dependency-model export or Revenue Story workshop click
Worked example and modes
The same method, preserved entry intent.
- Channel
- Founder-led referrals
- Revenue Share
- 46
- Recurring Share
- 35
- Forecast
- 850000
- Actual
- 620000
- Attribution Confidence
- 80
Distribution package
Use, embed, and share the instrument.
Blank CSV template90-second demonstrationThree share treatmentsPlain-language answer
Embed with canonical attribution
<iframe src="https://petrichorgrowth.com/tools/revenue-story-audit/embed.html" title="Revenue Story" loading="lazy" width="100%" height="900"></iframe>
<p>Source: <a href="https://petrichorgrowth.com/tools/revenue-story-audit">Revenue Story by Petrichor</a></p>Ownership and change control
Who keeps the result defensible?
Product
Petrichor product
Method
Petrichor strategy
Evidence
Petrichor research
Privacy
Petrichor operations
Security
Petrichor web platform
Distribution
Petrichor growth
Support
Petrichor client experience
A material method change requires a reason, impact note, fixture rerun, semantic-version increment, and public entry in the method change log.
Related decision methods
Continue through the evidence chain.
Signal Triage
Decide which market signals require action, observation, or deliberate disregard.
Bottom-Up TAM Builder
Build a transparent market estimate from named accounts, adoption, and economics.
Spend-at-Risk Calculator
Estimate how much planned growth spend is exposed to an unresolved relevance problem.
Related plain-language answers
Signal Triage answerBottom-Up TAM Builder answerSpend-at-Risk Calculator answer
Method questions
What another reader should know.
What does the Revenue Story method produce?
A versioned Revenue dependency model with visible reasoning, evidence status, next action, ownership, and review date.
What inputs does Revenue Story require?
Only the structured decision evidence named by the instrument. Missing or estimated inputs remain visible in the result.
Does the method use AI or a cross-customer benchmark?
No. It applies deterministic rules to the user's inputs and does not compare one customer with another.
When is the method reviewed or changed?
The current method is reviewed at least every 90 days. Material changes require new fixtures, a version increment, and a public change note.
When should the artifact move into facilitated work?
When the unresolved decision requires team challenge, evidence reconciliation, dissent, ownership, and an organizational commitment.