Write the forecast narrative
Write the story behind the number for your CRO or board, with risks and upside in plain language.
Ways to get this done with Avoma
Pick the approach that fits how your team works. You can start with one and add another later.
How this works
Shown for:
- 1Trigger
You run the RevOps Intelligence skill in Claude
- 2Context
The RevOps Intelligence skill reads Avoma meetings and scorecards through the Avoma agentic platform, plus your CRM (HubSpot or Salesforce) and Gmail
- 3Reason
Explain what changed since the last review and why
- 4Act
Draft a forecast narrative with the number, changes, risks and upside, returned in Claude
- 5Human judgment
Manager edits the narrative before it goes to the CRO
Skill
Use the RevOps Intelligence skill in Claude to draft a narrative with the number, what changed, key risks and upside, with recommended next steps.
How this works
Shown for:
- 1Trigger
You ask Avoma
- 2Context
Ask Avoma (Avoma agentic platform) reads the rolled-up forecast, deal risks, pipeline changes, key deals, narrowed by what you ask
- 3Reason
Explain what changed since the last review and why
- 4Act
Draft a forecast narrative with the number, changes, risks and upside, returned in Ask Avoma
- 5Human judgment
Manager edits the narrative before it goes to the CRO
Prompt
Prepare a forecast narrative explaining expected revenue, changes since the last review, major risks, and potential upside using available deal evidence.
Write the forecast narrative for [period]. Use the current forecast, what changed since last week, the three deals that matter most, key risks and upside. Keep it to five short paragraphs for the CRO.
What good looks like
Leaders want the story behind the number, along with the number.
Lead with the number and what changed
Executives want the delta before the detail.
Name the 3 deals that matter most
A handful of deals decide most quarters.
Keep it to 5 short paragraphs
A short narrative gets read before the meeting.
Customer stories
What teams say
Avoma is a powerful tool with a strong foundation for revenue forecasting. The team has solved the hard problems and is on the right path.
The team forecasting targets were amazing. I updated everything immediately because it was so intuitive.
More from this use case
Browse all Revenue Execution
What’s stopping you from turning every conversation into actionable work?
