Trust is a product feature
A QBR deck generator for CSMs at Lumapps: why every design choice was a trust choice, and why the model never writes a number.
QBR deck generator at Lumapps
Planhat record to a QBR draft with real numbers, in a few clicks. No model writes a figure.
Planhat API Lumapps Agent Hub Lumapps micro-app Google Slides Google Drive
Problem
Every quarter, for every customer, a CSM built the Quarterly Business Review deck by hand. The figures lived in Planhat, Looker, Pendo, Mixpanel and more. Most of the prep time went into copying numbers, not into the story the customer needed to hear.
What I built
I built a QBR generator that opens from a link on the customer record in Planhat. The CSM picks a customer and a quarter. The tool reads contract and adoption figures live from Planhat: licences, renewal date, package, MAU, WAU and stickiness. One more click builds a Google Slides deck in the customer's Drive folder. The figures are filled in from Planhat, and Lumapps Agent Hub drafts the narrative around them without touching a number. It reads from Planhat whether the customer runs on Lumapps or Beekeeper and picks the right template. A missing figure shows as "?" for the CSM to fill in. Nothing is estimated.
What I learned
Keep the model away from the numbers. A QBR with one wrong figure costs more trust than it saves time, so every value comes straight from the source and gaps stay visible. That rule is what makes the draft safe to start from.