Set up your client project: account brief, positioning, and past reviews
Teams build one Juma Project per account and add context over time. Every flow the team runs for that account pulls from the same project. If a project already exists, adding account context means each review opens with the full relationship instead of a cold read of a single call.
What to add
Account Brief
Who the account is: stakeholders and their roles, contract stage, headline goals, and how they use the product. With this in the project, every review opens on context the team already knows instead of re-deriving it from one call.
Positioning & Differentiators
Your positioning, the one or two differentiators that resonate with this segment, and competitive battlecards. Add this and the positioning slide and the competitive-risk slide lead with the right message and the right mitigation.
Past QBRs and Review Notes
Previous review decks and call notes saved as reference. The Flow compares the new call against these, so each review shows the arc: what moved since last quarter, what stalled, and what is still open.
Renewal & Commercials
Contract dates, current pricing, and expansion levers. With this in the project, the commercials slide and any renewal framing use real numbers, so the deck never fills a figure that was not actually agreed.
Guide Juma with project info
Add a short description to each knowledge item in the project's info field so Juma knows what each file contains and when to use it. For example:
- Account Brief: "Who this account is and what they care about. Read before building any review."
- Positioning & Differentiators: "Our positioning and battlecards. Use for the positioning and competitive-risk slides."
- Past QBRs and Review Notes: "Previous account reviews. Compare new calls against these to show progress."
- Renewal & Commercials: "Contract dates and pricing. Use for the commercials and renewal slides; never invent figures."
Turn your next account call into a QBR deck
Frequently Asked Questions
How long does it take to build a QBR deck from a call?
Building a QBR deck from a call by hand takes two to three hours: rewatching the recording, pulling notes, structuring the story, and laying out slides. Juma builds the outline from the transcript in minutes, so the time goes into reviewing and refining the deck rather than assembling it.
For a rep or CSM carrying a book of accounts, that difference compounds. Preparing four QBRs a quarter by hand is the better part of a working day in slide assembly alone. Running each account call through the Flow as it happens means the review is half-built before the team sits down to prepare it, and the structure stays consistent from account to account.
What does the QBR deck include?
The deck runs about nine slides: a title slide, the account situation, the account's goals, a ranked list of pain points, your positioning and the differentiator that landed, the proposed plan, the commercials, a competitive-risk slide with mitigation, and a next-steps table with owners and dates.
The ranked pain points matter most. Rather than a flat list, the Flow orders them by what the account emphasized on the call, so the review opens on what the stakeholders actually care about. The positioning slide leads with the one differentiator that got a reaction in the room, not a generic value prop.
Every slide is grounded in the call. The next-steps table carries the specific actions agreed, with an owner and a date against each, so the QBR ends on accountability rather than a vague promise to follow up.
What does Juma need to build the account review?
Juma needs the call. Connect Fathom and it pulls your most recent account recording, or paste the transcript straight into chat. That single input is enough to produce the full deck. Adding a Project with account context makes each review sharper, but it is optional.
With Fathom connected, the recording and transcript come in automatically, so there is no export or copy-paste step. Name the account or the call if your Fathom holds several, and Juma pulls the right one.
For deeper context, set up a Project for the account with the brief, your positioning, and past reviews. The Flow reads from it so the deck opens with the full relationship, not a cold read of one conversation.
How does this compare to writing the QBR from your notes by hand?
The Flow drafts the structure and grounds every point in the call, and judgment stays with the team. Strategy, taste, and judgment stay human: which risks to foreground, how hard to push on expansion, and what to leave out are calls only the account owner should make. Human review on every deck.
Writing a QBR from memory and scattered notes tends to drift toward what the rep remembers rather than what the account said. Building from the transcript keeps the review anchored to the actual conversation, which is what makes it credible when a stakeholder questions a point.
The team still owns the story. The Flow assembles a grounded first draft in minutes; the rep or CSM shapes the emphasis, corrects anything the first pass inferred, and decides what the account needs to hear. Juma augments the team, it doesn't replace it.
Can the same Flow prep a renewal or roll up a whole quarter?
Yes. Point it at the same call and ask for renewal prep, and the review reframes around where the account stands, the risks to the renewal, and the case for expansion. Ask it to pull a quarter of calls, and it rolls them into one account-review deck.
The renewal framing shifts the emphasis from a status update to a decision: what the account still needs, what could put the renewal at risk, and where there is room to grow the relationship, each backed by something they said on a call.
The quarter roll-up reads the arc across every call, showing what progressed, what stalled, and what is still open. For teams running reviews across a book of accounts, that turns a pile of call recaps into a single, consistent review deck per account.