Example document · made-up company
What this is about
Over the next year we hand our most repetitive work to agents, one part of the agency at a time, starting with monthly reporting. December gets the basics in place and measures where we stand. From January to March the report drafter and the drop watcher go live, so account managers find a draft waiting on the first working day of the month and drops are caught within a week. At the same time we test the two bets that change what clients pay for: the AI visibility audit and pricing on what we are responsible for.
Waves
| Wave | When (roughly) | Agents take over | People keep | Whose work changes | Lead | Done when |
|---|---|---|---|---|---|---|
| 0. Foundation | 23 Nov – 23 Dec 2026 | Nothing yet | Writing down how reporting works, measuring today's numbers, the rules in the Brain | Priya, head of analytics | Priya | Reporting is written down client by client, the three baselines are measured, the report drafter has a spec |
| 1. Monthly reporting | Jan – Mar 2027 | Pulling data, drafting reports and the "what happened", drafting tasks after the call, the Monday drop watch | Checking numbers, priorities, the client call, anything a client sees | Analysts (stop building decks), account managers | Head of analytics | All 68 reports start from an agent draft for two months in a row, and account managers spend at least half less time on reporting |
| 2. Content briefs | Apr – Jun 2027 (outline) | Drafting briefs in the one agreed format | Topics with the client, editing, sign-off | Content leads, writers | Content leads | Every brief starts from an agent draft (outline) |
| 3. Digital PR | Jul – Sep 2027 (outline) | Finding journalists, drafting pitches | Relationships with journalists, sending pitches | PR team | PR lead | (outline) |
| 4. Invoices and reminders | Oct – Dec 2027 (outline) | Drafting invoices and payment reminders | Exceptions, contracts, anything that moves money | Finance | Finance lead | (outline) |
The change team
| Person | Role in the change | Hours per week |
|---|---|---|
| Mara | Leads the change, the price list, the audit offer | 6 (25 a month) |
| Priya | Runs it day to day, Brain pages, measuring | 8 |
| Head of analytics | Owns the report drafter | 6 |
| Pilot account manager (to be chosen) | Tries the drafts first | 3 (founder's estimate) |
| Head of SEO | Owns the drop watcher | 2 (founder's estimate) |
| Daniel | Audit offer and new pricing | 2 (founder's estimate) |
Timeline
| Month | Wave | Main actions | Priya | Head of analytics | Mara | Daniel | Head of SEO | Pilot AM |
|---|---|---|---|---|---|---|---|---|
| Dec 2026 (3 working weeks) | 0 | Write down reporting, measure baselines, spec the report drafter, audit offer | 22 of 24 | 13 of 18 | 6 of 19 | 6 of 6 | 0 | 2 of 9 |
| Jan 2027 | 1 | Drafter side by side for the pilot AM, task drafting after calls, drop watcher spec, price list | 10 of 34 | 15 of 26 | 6 of 25 | 4 of 9 | 4 of 9 | 9 of 13 |
| Feb 2027 | 1 | Drafter for all AMs, drop watcher side by side, AMs trained on new pricing | 8 of 34 | 26 of 26 → 14 of 26 | 4 of 25 | 2 of 9 | 6 of 9 | 3 of 13 |
| Mar 2027 | 1 | All 68 reports from drafts, drop watcher on all clients, measure | 6 of 34 | 8 of 26 | 2 of 25 | 2 of 9 | 3 of 9 | 2 of 13 |
Moved to fit the hours:
- February: the head of analytics was at 26 of 26 hours, because checking corrections on all 68 drafts took about 17 hours. Analysts check the numbers on every draft as part of their job already; the head of analytics now reviews a sample of 20 drafts (about 5 hours). That brings February to 14 of 26.
- December: Daniel is at his limit with the audit offer, so picking the three audit clients moves to Mara.
What these hours can't reach: nothing in Q1. The strategy's end-2027 milestone (first five clients on the new pricing) depends on renewals Daniel and the account managers win, which is customer work and sits in the Sales CRM, not here.
This quarter (Q1 2027, with wave 0 starting now)
Only six weeks of Q4 2026 are left, so Mara chose next quarter's OKRs, with the wave 0 actions starting now.
Objective 1: Account managers find a draft report waiting, and spend the time on clients · owner: Priya
Serves: strategy milestone "reports are drafted by agents" (end 2027) and the signal "drafts save account managers at least half their reporting time by end of March 2027".
KR 1.1: Reports that start from an agent draft: 0 → 68 a month by March · owner: head of analytics · baseline: 0 (measured: the drafter doesn't exist yet) · target: 68 (proposal, all reports) · source: cards on the Monthly reporting board · status: live
| Action | Accountable | Does the work | Size | When | Done when |
|---|---|---|---|---|---|
| Write the report drafter's spec | Head of analytics | Head of analytics, with Claude | 6–8 h | 1–18 Dec | The spec has job, inputs, output, asks before, never, owner, undo |
| Choose the report template | Head of analytics | Pilot AM and head of analytics | 3–4 h | 7–18 Dec | One template for all clients, or one per client type, agreed |
| Run the drafter side by side for the pilot AM | Head of analytics | Report drafter, checked by the analyst | 10 h + 6 h AM | 4–15 Jan | The pilot AM's January reports all started from a draft |
| Roll the drafter out to all account managers | Head of analytics | Report drafter; Priya trains the AMs | 8 h + 4 h | 1–12 Feb | Every AM's February reports started from a draft |
| Review a sample of 20 drafts a month | Head of analytics | Head of analytics | 5 h a month | Feb–Mar | Corrections per draft logged in Monday's meeting |
KR 1.2: Hours per report: baseline → half by 31 March · owner: head of analytics · baseline: measure in December reporting week, from Tooling Studio Time · target: 50% of baseline (from the strategy) · source: Tooling Studio Time, tag "reporting" · status: draft (no baseline yet)
| Action | Accountable | Does the work | Size | When | Done when |
|---|---|---|---|---|---|
| Start logging reporting hours in Time | Priya | Priya sets it up, analysts and AMs log | 2 h | by 27 Nov | Every analyst and AM logs reporting time with the tag |
| Measure hours per report in December | Head of analytics | Head of analytics | 3 h | 1–11 Dec | The December baseline is written in the key result |
KR 1.3: Days from the client call to tasks on the board: baseline → 1 · owner: Priya · baseline: measure from December calls · target: 1 day (proposal) · source: Kanban Tasks, card created date against the call date · status: draft (no baseline yet)
| Action | Accountable | Does the work | Size | When | Done when |
|---|---|---|---|---|---|
| Measure days from call to tasks in December | Priya | Priya | 2 h | 1–18 Dec | The December baseline is written in the key result |
| Set up task drafting after the client call | Priya | Report drafter drafts, AM confirms | 6 h | 4–22 Jan | After every pilot client call, draft tasks are on the board the same day |
Objective 2: We catch a drop within a week, not in the monthly report · owner: head of SEO
Serves: the operating system's new weekly drop watch.
KR 2.1: Clients watched every Monday: 0 → 68 · owner: head of SEO · baseline: 0 (measured: nobody watches weekly today) · target: 68 (proposal, all clients) · source: drop watcher run log · status: live
| Action | Accountable | Does the work | Size | When | Done when |
|---|---|---|---|---|---|
| Write the drop watcher's spec | Head of SEO | Head of SEO, with Claude | 4 h | 4–22 Jan | The spec has what counts as a drop and who hears about it |
| Run the drop watcher side by side for the pilot AM | Head of SEO | Drop watcher | 4 h | 1–26 Feb | Four Mondays of alerts the pilot AM agrees with |
| Turn the drop watcher on for all clients | Head of SEO | Drop watcher | 3 h | 1–12 Mar | Every client is watched every Monday |
KR 2.2: Days from a drop to the account manager knowing: about 30 → 7 · owner: head of SEO · baseline: about 30 (founder's estimate: drops show up in the monthly report; confirm from the last three drops) · target: 7 (proposal) · source: drop alerts by email against the drop date · status: draft (baseline is an estimate)
Objective 3: Clients start paying for what we are responsible for, not for articles · owner: Mara
Serves: the strategy's first two bets.
KR 3.1: AI visibility audits sold: 0 → 3 by 28 February · owner: Daniel · baseline: 0 · target: 3 (from the strategy) · source: won deals in Tooling Studio Sales CRM, pipeline "New business and renewals" · status: live
| Action | Accountable | Does the work | Size | When | Done when |
|---|---|---|---|---|---|
| Write the audit offer and its fixed price | Daniel | Daniel, with Claude | 6 h | 1–18 Dec | A one-page offer and price Mara agrees to |
| Pick the three clients for the audit | Mara | Mara, with the AMs | 2 h | 7–18 Dec | Three clients named in the CRM, each with a deal |
KR 3.2: Renewals offered on the new pricing: 0 → 5 by 31 March · owner: Mara · baseline: 0 · target: 5 (from the strategy) · source: deals tagged "new pricing" in the Sales CRM · status: live
| Action | Accountable | Does the work | Size | When | Done when |
|---|---|---|---|---|---|
| Draft the new retainer price list | Mara | Mara and Daniel | 8 h | 4–29 Jan | Price list agreed and on a Brain page |
| Show the account managers how to offer it | Mara | Mara | 3 h | 1–12 Feb | Every AM with a renewal this quarter has seen it |
Selling the audits and offering renewals are customer work: those deals live in the Sales CRM, not on this roadmap.
Wave actions that move no key result
| Action | Accountable | Does the work | Size | When | Done when |
|---|---|---|---|---|---|
| Write down how reporting works, client by client | Priya | Priya | 12–16 h | 23 Nov – 11 Dec | Every client's report is described: sources, template, who builds it |
| Put the reporting rules and agent pages in the Brain | Priya | Priya, with Claude | 4 h | 1–18 Dec | Rules for reports and the two agent pages are in the Brain, each with an owner |
| Choose the pilot account manager | Mara | Mara | 0.5 h | by 27 Nov | One AM named and told |
Not this quarter
- Content briefs (wave 2): waits until the teams agree one brief format.
- The weekly client update (third bet): to June 2027.
Next quarters (outline)
| Quarter | Objectives | Main key results | Wave |
|---|---|---|---|
| Q2 2027 | Account managers only spot-check reports; briefs start from drafts | Hours per report stays at half; briefs drafted 0 → all; weekly update tried with 10 clients | 1 hand-over, 2 |
| Q3 2027 | PR finds journalists faster; the audit is a regular offer | Hours per placement; audits sold per month | 3 |
| Q4 2027 | Finance stops chasing invoices; five clients on the new pricing | Days to payment; clients on new pricing 5 | 4 |
For the setup step
- Who can see the goals: everyone at the agency.
- Board for the change work: "AI change", with lists Wave 0 · Foundation, Wave 1 · Monthly reporting, Bets and Done.
- Actions that start before the quarter: the wave 0 actions in December go on the board now, under the Q1 key results they prepare.
For a person to do
| What | Who | By |
|---|---|---|
| Confirm hours with the head of SEO, Daniel and the pilot account manager | Mara | 27 Nov |
| Add the "reporting" tag in Tooling Studio Time | Priya | 27 Nov |
Rhythm
- Weekly: "Check in on the roadmap" before Monday's meeting; owners confirm their key results.
- End of wave 0 (23 Dec): Priya checks the done-check before wave 1 starts.
- Signals from the strategy: drafts don't save half the reporting time by end of March → rethink the approach; no audit sold by end of April → drop the audit.
- End of quarter: "Plan next quarter".
About this document
Version 1, 19 November 2026. Written with Mara Halvorsen and Priya, building on our foundations, Strategy v1 (11 Nov) and Operating system v1 (18 Nov). Confirmed with the founder: waves, the change team's hours (three as estimates), the quarter choice. Still proposals: the targets marked as such, the action sizes, and the later quarters.