A BETTER WAY TO SHARE THE WORK
Create a quarterly business review around your customer's goals
Your customer needs to see what changed for them—not a quarter of your team's activity.
New to creating with an agent? The request will guide it through the task. Bring your notes; you don’t need to write HTML.
How do I create a useful quarterly business review with an AI agent?
Supply the customer's agreed objectives, comparable quarterly measures, feedback, and open commitments. Ask your agent to connect each objective to verified evidence, distinguish product adoption from business outcomes, and propose the next joint decision. Review the facts with the accountable people before sharing a readable HTML pre-read.
01 / SEE THE DIFFERENCE
Adoption improved. Time savings are still unmeasured.
A fictional reporting customer reviews a completed quarter. The figures describe the same ten analysts in both periods.
Harbor Ops wants less report preparation time. Weekly active analysts rose from 4 of 10 to 7 of 10 between the April–June and July–September review periods. An analyst is active if they create at least one report in the review's final complete week. No preparation-time baseline was collected. Two customer comments describe easier navigation, not measured time savings. The glossary was delivered and accepted. Template ownership is still unconfirmed. Propose a two-week timing exercise, subject to the customer lead's approval; no renewal or expansion is agreed.
- Objective
- Reduce report preparation time; no preparation-time baseline was collected.
- Observed adoption
- Weekly active analysts rose from 4 of 10 to 7 of 10 using the same definition and group.
- Evidence boundary
- Two customer comments describe easier navigation, not measured time savings.
- Unresolved
- The glossary was delivered and accepted; template ownership is still unconfirmed.
- Next decision
- Approve or revise a two-week timing exercise. No renewal or expansion is agreed.
Open a complete fictional HTML example, with its source notes →
Create my quarterly business review02 / MAKE IT YOURSELF
Start with the evidence. Shape the page around the reader.
Start with the customer's objective
Name the result the customer wanted and the evidence needed to assess it. An increase in logins may show adoption, but it does not establish time saved or value realized. When a success measure was never agreed, make defining it a next step rather than inventing an achievement.
Compare like with like
Keep each measure's definition, period, and denominator visible. Explain changed account coverage or incomplete data. Show whether a past commitment was delivered and whether the customer accepted it; neither alone proves the intended business benefit.
Give the unresolved objective space
Include feedback and blockers that qualify the positive story. Separate one person's comment from an account-wide conclusion. Pair each gap with a confirmed owner or an explicit ownership question. A business review is useful when it makes an honest conversation possible.
Propose a joint next step
For each proposed action, say what it should establish and who must agree. Keep the next plan separate from existing commitments. An HTML pre-read can put the decision first and evidence below; it cannot conduct the review, renew a contract, or assign the customer's staff.
03 / TRY THIS PROMPT
Copy this into your agent. Add your source material.
Use the conversation where you already did the work, or start one with your notes. Replace the placeholders and supply any missing context; only attach information you are allowed to share with your agent.
Get the ready-to-copy creation request for guided questions, this task, and a draft review before anything is published.
Create a quarterly business review for [customer audience] using only supplied or authorized objectives, dated metrics, feedback, and previous commitments. Ask only for missing essentials: reporting periods, definitions, customer objectives, evidence, and the next decision. Organize around the customer's goals. Separate adoption from measured business outcomes, and delivered work from acceptance. Preserve denominators, comparability limits, missing baselines, and unresolved owners. Do not invent ROI, savings, customer quotations, renewal intent, commitments, or dates. Label proposed next-quarter actions as proposals and keep actual agreement in our existing customer workflow. Use only audience-safe evidence and links; leave private account notes in my authorized tools. Create readable static HTML with no scripts, forms, or live-data claims. Use my saved artifact style if available. Show the draft and claims to verify. Do not publish or change access without separate explicit approval.
04 / BEFORE YOU SEND
A polished page still needs your judgment.
- Does the opening address a customer objective rather than seller activity?
- Are adoption and business outcomes separate, with missing baselines visible?
- Are quarterly comparisons valid for the same population and definitions?
- Are proposed actions, commercial terms, and commitments correctly labeled?
- Has the customer-facing disclosure and recipient access been reviewed?
When HTML fits
A customer-facing pre-read or recap connecting evidence across approved sources without asking every reader to navigate the account system.
When another format fits better
Keep the customer platform as the source for changing account data and commitments. Use the existing dashboard if it already answers the question. The page does not measure ROI, replace a review conversation, or update customer records automatically.
FROM DRAFT TO A LINK
Make it clear. Make it yours. Then share it.
Keep creating and revising in the agent you already use. With a compatible connection, share/artifacts publishes the reviewed HTML so you do not have to rebuild it in another editor. Ask your agent to use your saved artifact style for headings, color, and tone; review the result before sending it.
Choose who should be able to open the page and verify the returned link. For corrections to the same deliverable, update the existing artifact without changing its link. Publish a separate artifact when the old edition needs to remain available.
These are static pages, not live apps: no scripts, forms, or automatic data refresh. Source collection and scheduling depend on your agent and its available tools, not on share/artifacts.
Make this with my agentQuestions before you start
Is a QBR just a longer status report?
No. It revisits customer objectives and the evidence for value over a period, then shapes the next joint plan. Keep routine tickets and delivery detail in the status report unless they affect that discussion.
What if we cannot prove the business benefit?
Show what is measured and what is not. Propose a practical measurement step with the customer instead of multiplying usage by an invented time-saving estimate.
Should renewal be the main message?
Only include a commercial decision when it is actually part of the agreed conversation. Do not turn engagement or positive feedback into evidence that a renewal is approved.