# Sample account brief: Northwind Studio before the renewal call

A fictional result of the Account brief recipe: how the account is doing, what is new, open issues and three things to raise on the call.

> [!info]
> **Fictional example.** Northwind Studio and Tally are invented. This shows the shape of what the *Account brief* recipe pulls together before a call.

<!-- onecell:block {"type":"stats","items":[{"tone":"good","delta":"+3 since spring","label":"Seats","value":"14"},{"label":"Invoices a month","value":"about 220"},{"tone":"good","delta":"−6","label":"Average days to paid","value":"18"},{"label":"Renews","value":"1 Sept"}]} -->
| Metric | Value | Change |
| --- | --- | --- |
| Seats | 14 | +3 since spring |
| Invoices a month | about 220 |  |
| Average days to paid | 18 | −6 |
| Renews | 1 Sept |  |

## How they use Tally

A design studio with clients across Europe. They invoice per project milestone, mostly in euros, and lean on reminders. Their finance lead, Ana, asked for part payments in June; it shipped last week.

## Open issues

- Some of their clients got a reminder twice on 14 August (our incident). We apologised the same day.
- They want notifications for only some team members. Not built yet.

## Raise on the call

1. Part payments are live
   The feature Ana asked for. Offer to walk her through it.
2. Own the reminder incident
   Say what happened and what changed, in two sentences.
3. Annual plan
   At 14 seats, annual billing saves them about £400 a year.