Business Review Prep

---
name: business-review-prep
description: Drafts the slide content for a client business review from our documentation, financials and team input, tailored to what the client values most. Use when preparing a business review for a client's senior executives.
---

# Business Review Prep

A business review is a periodic presentation to a client's senior executives
covering delivery, team feedback, financials, risks and opportunities. Reviews run
one to three times a year.

This skill works with client data. Confirm you have the client's written
authorisation, and that you are working in the right account, before you attach
anything.

## You need

- The timeframe the review covers
- What the client wants to see and what they value most
- Documentation, including engineering documentation, and client context
- Commercial figures
- CSAT scores and Team NPS
- Impact in the last reporting period, business performance and YLD's contribution
- Key changes since the previous review, positive impacts and engineering
  achievements
- Engineer suggestions and emerging opportunities
- The next steps from the past business review

## Steps

1. State what the input covers and what it doesn't.
2. Confirm what the client wants and the timeframe covered.
3. Decide what the client values most.
4. Gather information from the documentation and team outreach.
5. Gather the financials.
6. Identify areas of risk and opportunity.
7. Write a first draft of the review.
8. List anything you were unsure about.

## Decisions and defaults

- How far the review is tailored to the client, some delivery focussed, some team
  focussed. Default: ask before proceeding.
- Which sections to include, picked from a list. Default: ask before proceeding.

## Output

Text. A draft of the slide content for 15 to 30 slides. Each slide has a title and
its content as text, a table or a described figure. Written for the client's
senior executives and aligned with the brand guidelines. The review is presented
first, then shared with the client.

## Never do this

- Do not leave gaps in content. If the input doesn't cover an area, say so.
- Do not prioritise items the client doesn't value.
- Do not use outdated information. Keep the history of systems apart from the
  latest information.
- Do not focus on one team. Gather insights from all areas.
- Do not add an item the team couldn't explain if asked.
- Do not ignore the client's input.
- Do not include incorrect content or data.
- Do not invent numbers, names, quotes or trends. If the input doesn't support it,
  say so and leave a placeholder.
- Never output anything that identifies an individual. Aggregates and role-level
  findings only.

## Before it goes out

- Every figure checked against its source, including CSAT, Team NPS and the
  commercial numbers.
- The timeframe is right and nothing from older system history is presented as
  current.
- The previous review's next steps are covered.
- The tone matches what the client said they want to see, and we have discussed
  with the client what they want to see.
- Brand guidelines are met.
- The conversation with the PL has happened.
- SLT review is done.

This output is a draft. A person signs it.