Quarterly Business Review

A software provider meets a large customer after three months of use. It could show a list of new features, but the customer cares whether staff are completing work faster, so a QBR connects usage and service data to the outcomes the customer wanted.

Gainsight describes QBRs as strategic customer meetings about impact, challenges and next steps, and Atlassian's executive business review template provides a way to frame goals and decisions, though these are practical formats, not a requirement to meet every exact quarter. Agree on the customer's goals before preparing slides, because reducing delays, improving service quality or controlling costs are more useful starting points than counting login events alone.

Use a clear baseline and period: if on-time deliveries rose from 85% to 91%, explain the dates, denominator and any change in measurement, and do not claim the provider caused every improvement without considering other changes. Discuss what did not work as well, since missed service levels, unresolved support tickets and low adoption should be brought into the open with actions, and a polished deck that hides known issues weakens trust.

Invite the right people, as an operations user can explain daily problems while a decision-maker can set priorities and approve change. Keep the review distinct from a routine support call, since specific incidents may be noted but the meeting should examine patterns and next-quarter decisions, and urgent problems should not wait for a quarterly meeting.

A short pre-read can let participants check figures beforehand, and the provider should ask the customer what it most wants to discuss and leave room for feedback that does not fit its preferred charts. Review contract commitments accurately, because a QBR may surface renewal dates or new needs but should not become a disguised sales pitch, and any new scope or commercial terms need separate agreement by authorised people.

Decide actions in the room where possible and record the owner, due date and measure for each, so that improving adoption becomes more useful when someone will train a defined group by a stated date and check usage afterward. A QBR can also reveal that the original goal has changed, such as a customer that first wanted speed and now cares more about error reduction, so update the success measures together rather than presenting old targets as though nothing changed.

The provider should not share another customer's confidential benchmark without permission, and aggregated comparisons may help if prepared lawfully and meaningfully, with an explanation of what is being compared so a number does not mislead. An illustrative coverage rate is key accounts that completed a QBR divided by key accounts designated for the cadence, so eighteen of twenty is 90%, which says nothing about meeting quality or whether the two missing accounts faced the highest risk.

Quality can be assessed by whether both sides agreed priorities and followed through, and a meeting that ends with a renewal forecast only in the provider's CRM is not a shared business review, so ask the customer whether the review was useful. Some customers do not need a formal quarterly meeting, as a small, stable account may prefer an annual strategic review and responsive support, and force-fitting a QBR can waste time for both parties.

When results disappoint, resist assigning blame before investigating, since the provider may need to fix service while the customer may need training or data changes, so make dependencies visible and agree a workable plan. Afterward, send a concise record of decisions and owners through the approved channel and check progress before the next review, because repeating the same unresolved action each quarter is a sign that the process is not working, and for a business owner the QBR is a chance to learn whether the relationship creates the value both sides expected.