Solutions · Customer Success
View pricingWhere it fits
The QBR is already written. The numbers came out of the product, the assistant turned them into a report, and the report went out as an attachment to three people at the account. Whether any of them read it, you find out on the renewal call, which is the one moment the answer stops being useful.
HTMLvault does not replace your CS platform. It replaces the attachment. The health score still lives where it lives, and the QBR still gets written the way it is written today. It takes the report and puts it at one canonical URL on your own domain, then mints a URL per stakeholder, so “the account engaged” resolves into which person read it, how far they got, and who never opened it at all.
Nothing changes for the customer. No portal to log into, no file to download, no version to keep track of. They click a link on your domain and the report is simply there, and it is current, because you edit it in place. When a champion leaves, their URL quietly stops working while everyone else at the account keeps reading.
ONE STEP BETWEEN THE QBR AND THE ACCOUNT
How it works
Vault the QBR your AI created. Keep one canonical URL and update it in place as numbers change.
Champions, admins, exec sponsors. Each contact gets their own tracked URL.
Who opened, how far they scrolled, whether they came back. Per person, not per account.
Take the renewal call knowing who read what, and who never opened it at all.
Worked example · The QBR that flags itself
Three people matter on this account: the champion who lives in the product, the admin who owns the configuration, and the exec sponsor who signs the renewal. Send the QBR as one attachment and all three collapse into a single data point: sent.
Publish it once and mint a URL per stakeholder. Now the champion opening it twice and the sponsor never opening it are two different facts, and the second one is the one worth acting on.
On day four your CS platform gets the absence rather than the presence. That is three weeks before the renewal call, which is enough time to do something other than write a post-mortem.
Use cases
The exec sponsor never opening the QBR is a churn signal. You see it three weeks before the call instead of reading about it in the post-mortem.
One URL for the whole account, edited in place as your product changes. No stale PDF getting forwarded to new hires for the next two years.
Revoke their link and it 404s without announcing anything. The rest of the account never notices, and neither do they.
Password-protect account-level metrics and expire them when the review cycle closes. Sensitive figures stop existing on schedule.
A link.viewed webhook tells your CS platform the moment the buying committee goes back to the pricing section. That is your call window, and it is short.
Reports open on your own domain with no vendor chrome and no sign-in wall. It reads like something you made, because it is.
What actually changes
Publish the report, send the links, read the room three weeks early.