Business outcome
Customer-success teams often spend hours copying CRM and product-usage data into slides. This workflow keeps the metrics deterministic while letting Presenton turn them into a clear executive narrative.Before you start
- Create a Presenton Cloud API key.
- Export approved account and product-usage fields from your CRM or warehouse.
- Install Python 3.10 or later.
- Store the API key outside source control:
1. Prepare the account export
Save this example asaccounts.csv:
2. Generate the QBRs
Save asgenerate_qbrs.py:
3. Review before sharing
The account owner should verify:- ARR, renewal date, health score, and adoption metrics.
- Whether the stated outcome is approved for customer-facing use.
- Risk wording and the mitigation plan.
- Owners and dates added during review.
- Branding, customer logo rights, and presentation tone.
Operationalize the workflow
- Use the account ID and reporting period as an idempotency key.
- Generate drafts in a background queue for large account portfolios.
- Store the returned presentation ID in the CRM activity record.
- Require CSM approval before a deck is sent externally.
- Regenerate only when verified source data changes.
Generate asynchronously
Queue larger QBR batches and monitor each task reliably.