Source each figure where it was produced, put its as-at date on the slide with it, mark whatever moved since last quarter, and hold the pack for the account manager who presents it.
A pack is assembled, and each figure on it arrives with the system it came from and the day it was true.
02
A number is placed on a slide, and the source behind it is recorded there rather than remembered.
Reason
03
A figure has moved since it was last shown, and both readings appear with the reason the earlier one changed.
04
A chart is carried over from a previous pack, and it stays unpopulated until its source is read again.
05
A comparison period is chosen, and the rule that chose it is stated rather than left to the assembly.
Decide
06
A slide rests on a system the customer cannot open, and that limit is marked on the slide itself.
07
An export ages past its term, and each slide leaning on it is flagged for re-sourcing before assembly.
Out
08
A deck is quoted back a quarter later, and the pack still holds the source and the date behind each figure.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
Assembly, sourcing and restatement marking belong to the agent. What the customer is told belongs to a named account manager, who chooses the narrative and sends the pack.
Example workflow
One QBR pack, sources to sign-off
AgentHuman
1Source material receivedProduct telemetry, support records, billing systems, CRM and the last pack shown
2Figures sourced and datedEach figure, the system of record it came from, the day it was true and the pack it last appeared in
3Slides assembledThe slides, the figures on them, what moved since last time and confidence
4Controls appliedSource checks, as-at date checks, restatement checks and sourcing confidence
No human action required
Stages 1 to 4 run unaided, and nothing reaches a customer at any of them — the agent is assembling, and the account manager lane opens at the sourcing gate.
5DecisionSplits at the sourcing gate
Every figure sourced
Goes to the named account manager.
Anything unsourced
Adds a reporting review first.
Manager review
The pack is held with its sources, the dates behind them and what moved since the last review.
Approve · Append source · Send to reporting review
Approved — by the account manager▼
6Reporting and CRM records updatedOnly where write access and records policy allow it
7Outcome evaluatedSource coverage, restatement rate, manager corrections and what review found
Corrections
Each manager correction is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Deciding what the customer should be told.
Choosing the narrative the pack argues.
Sending the deck to the customer.
Signing off a figure quoted in a contract.
Automation boundaryAgent acts unaided
✓Assemble the pack from the sources of record.
✓Mark any figure that has moved since it was last shown.
✓Carry the source and the as-at date onto each figure on a slide.
✓Flag what could not be sourced rather than leaving it off the pack.
Nothing reaches a customer except by a named account manager, inside the agreed boundaries.
Judging whether an account is doing well.
Explaining a restated number to a customer.
Choosing which metrics the review covers.
Changes to the pack, the sources or the rules.
Example output
One QBR slide, annotated
This serves an account team who will have the numbers in this pack quoted back at them a quarter later; below is one slide exactly as the agent leaves it.
QBR pack output · single slideIllustrative example
Slide
Figure shown
Account
Source of record
Confidence
Held for
Quarterly review, one account
Adoption across licensed teams
Restated, both shown
Product telemetry, 3 August 2026
Held, not sent
The named account manager, by name
As receivedBuilt from one telemetry export and one billing record, and it claims nothing about the account beyond them.
What the slide holdsProduct telemetryBilling recordSupport history
Why nothing is sentDeciding what a customer is told is a call the account manager makes.
ActionApproveAppend sourceSend to reporting review
What the score decidesBelow the configured threshold a slide gets a reporting read before the manager sees it.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every QBR packFrom the sources of record
03Evidence
Where the pack is used
The operational-reporting agent in Operations reports a number to the company that owns it; this pack is shown to the customer, who checks it against figures of their own.
01Approved path
The deck is not the account
A pack is a selection — which metrics appear, which period is shown, which comparison is drawn — and each of those choices is set by you, not baked in.
02Human review
What was checked, and not found
No figure here is presented as one the customer has agreed: their own reporting may compute the same measure on a different basis, and where the two do not meet, the gap is reported rather than a single number neither side supports.
04Build an evidence trail
The slide, the number on it and the source that produced it stay together.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Product telemetryUsage events · entitlement data Adoption by team and by feature
Support and ticket systemsZendesk · Salesforce Service Ticket volumes and outcomes
Billing and contractsBilling platform · contract records Entitlements, terms and invoices
Agent
QBR assembly and sourcing
Reads the sources Assembles the pack Holds for the manager
Reporting and presentationData warehouse · BI dashboards Templates and the packs already shown
An account-level source-traceability figure can read clean while multi-product accounts carry most of the unsourced slides. Nestack reports the correction rate by account, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Multi-product accounts
7.7%
3.7×
Review
Accounts on migrated data
5.5%
2.6×
Review
Accounts on legacy reporting
3.4%
1.6×
Watch
Single-product accounts
1.9%
0.9×
Normal
Bar: correction-rate lift vs. single-product baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What an unsourced slide costs
The loop shuts when the unsourced slide is a regression case. That suite is what the next deck assembled is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Correction rate rises on multi-product accounts.
02Diagnose
The number on slide nine that three people in the room could each source differently is taken apart until one source is left standing.
03Improve
Every change goes out numbered, with the decks that caused it attached.
04Verify
Nothing releases while one touched deck case is still red.
05Learn
The case stays on, and the sourcing rules are rewritten alongside it.
Learn → DetectThe return edge. The next pack is measured against a suite one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, pack assembly, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01QBR pack workflow and automation-boundary work.
02Telemetry, support, billing and BI sources.
03Source-traceability and pack-coverage mapping.
04Reporting source ingestion.
05Figure, source and as-at date binding.
06Sourcing confidence and review routing.
07Account-manager review workflow.
08Reporting and presentation integration.
09Slide and source cases.
10Guardrails and sourcing controls.
11Deck-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne account, one quarterProductionProduction review workflowAdvancedMultiple accounts / regions
Introduced at Pilot
Pack assembly to your sources✓✓✓
Named manager approval✓✓✓
Reporting-pack baseline✓✓✓
Introduced at Production
Reporting by account—✓✓
Reporting review workflow in your systems—✓✓
Approved write-back—✓✓
Presentation-tooling integration—✓✓
Introduced at Advanced
Multi-entity account packs——✓
Multi-stage pack approvals——✓
Large pack volumes——✓
Multi-account pack controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, pack volume, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your live accounts and the quarterly review each one gets→Source capture and as-at date versioningWeek 1
02Representative telemetry, billing and support sources→Source binding, assembly logic and the pack baselineWeek 2
03Your review calendar and the managers it names→Source mapping, sourcing rules and the automation boundaryWeek 1
04Access to relevant APIs, feeds or exports→Telemetry, billing and support source assessment, then integration setupWeek 2
05Decks you would not want re-derived→Source cases and the evaluation roundWeek 4
06What no slide may settle→Sourcing confidence, review routing, guardrails and release controlsWeek 3
07A named account manager who presents it→Release to the named account manager, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
The fifth band holds two phases, and that is a measurement rather than a flourish in the drawing.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Review-pack discovery, sourcing rules and the automation boundaryW2Source integration and the reporting-pack baselineW3Assembly logic, restatement marking and release controlsW4Evaluation suite, source cases and failure-mode testingW5Presentation-tool integration, pilot packs and targeted correctionsW6One review cycle run under the account manager, then Agent Care handover
Reading the bandEach bar covers only the weeks its own work is named for, and week five is shared by design.
At the end of W6Once the source record validates, Agent Care assumes the agent.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Customer Success AI agent
Build a QBR preparation agent around the number your last pack could not source.
Show us one account you review each quarter and its last pack. Not the figure that felt right on the day. The figure with the system it came from and the date it was true on, because somebody will hold you to it a quarter later. An unsourced slide comes back as a finding.
