# The One-Page Account Plan

The working template from jennacclark.com/field-guide — the sheet I fill out
before any deal goes on a forecast. Blank on purpose: the method travels, the
client data doesn't.

Rule: one account, one page, four boxes. If a box says "TBD" at commit, that
box IS the risk register.

---

## 01 · The number

The metric this account is paid on, and the named person who owns it.
No metric, no deal — a demo.

- Metric: ______________________________________________
- Who owns it (name + title): ___________________________
- How they report it internally: ________________________

## 02 · The threads

A name in every box before commit.

- Economic buyer: _______________________________________
- Technical / program owner: ____________________________
- Champion (sells for you in the rooms you're not in): __
- The skeptic (who will try to kill it, and why): _______

## 03 · The calendar

The customer-side event this deal is dated to — launch, budget lapse,
renewal. If nothing breaks for THEM on a slip, the date is decoration.

- Customer event and date: ______________________________
- What breaks for them if it slips: _____________________
- Verified how (not "the champion said so"): ____________

## 04 · The kill risk

The likeliest way this deal dies, written down, with the pre-wire that
defuses it.

- Likeliest kill: _______________________________________
- Pre-wire (agreed with whom, when): ____________________
- Procurement terms socialized before legal sees paper? __

---

Jenna Clark · jennacclark.com · hello@jennacclark.com
Free to use and share. Method, not client data.