---
name: 01-pipeline-review
description: Run when I paste a pipeline export or deal notes and want the week's priorities. Trigger - "run 01" plus the pipeline.
---

# TASK 01 — PIPELINE REVIEW

## INPUT
Minimum: accounts with stage and value. Better: next step,
owner, close date, and last week's version for comparison.

## PROCESS
1. Rank open deals by (value x closeability this week). Ignore
   anything with no next step older than 30 days for the top-3.
2. Compare against the last version I gave you, if any. Note
   stage or date slips. Flag, never scold.
3. Sum weighted pipeline vs target. Ask for the target once if
   you do not have it.

## OUTPUT — exactly this shape
1. PUSH THIS WEEK — three deals: account, value, the single
   next action, who owes it, by when.
2. SLIPPED — deals that moved backwards, one line each: what
   moved and the one question to ask the owner.
3. COVERAGE — pipeline vs target as a figure and a ratio.
   One line of judgement: enough, thin, or a hole in [month].

## RULES
- One screen total. No commentary on my sales methodology.
- If two deals tie, pick the nearer close date.

## EDGE CASES
- No values in the paste: rank on stage + close date, say
  "unweighted — send values for coverage maths".
- Everything looks fine: say so in one line, then name the one
  deal you would still worry about and why.

## GOOD LOOKS LIKE
"PUSH: Nordic bank counterparty pilot (£84k) — get the
data-scope sign-off; owner me; by Thu 4 Sep."

---
name: 02-client-update-email
description: Run when I need to tell a client something that happened. Trigger - "run 02" plus account and the fact.
---

# TASK 02 — CLIENT UPDATE EMAIL

## INPUT
Account name + what happened. If a delay: the new date. If a
change to the data or delivery: what exactly changed.

## PROCESS
1. Classify: good news, neutral change, or bad news we caused.
2. Draft to the OUTPUT contract. Translate the fact into their
   terms — their model validation, their reporting cycle,
   their committee date — only from what I gave you.

## OUTPUT — one email, 120 words max
- Line 1: the fact, plainly.
- Lines 2-3: what it means for them, in their terms.
- Last line: one ask or one confirmation, with a date.
- Subject line included, under 7 words, never "Update".

## RULES
- Apology only if we caused it. Then once, plainly, with the
  fix and its date. Never twice.
- Bad news never travels with a pitch in the same email.
- No "as per", no "please be advised", no passive fog.

## EDGE CASES
- No new date given on a delay: draft with [DATE] and tell me
  that is the one thing you need.
- The change affects a regulatory submission: say so to me
  above the draft before writing a word of it.

## GOOD LOOKS LIKE
"Subject: February consensus — two days late
The February publication moves to Thu 12 Feb..."

---
name: 03-quote-cover-note
description: Run when a quote or proposal is ready and needs its cover note. Trigger - "run 03" plus client, what is quoted, price, validity, anything unusual.
---

# TASK 03 — QUOTE COVER NOTE

## INPUT
Client, what is quoted (modules, seats, delivery channel),
headline price, validity date, start date. Optional: what they
said they cared about in the last conversation.

## PROCESS
1. Pick ONE value anchor from what I gave you — coverage of
   their unrated exposures, the contributor base, the delivery
   channel they already run — and place it before any number.
2. State validity plainly and factually. Never as pressure.
3. Close with the concrete next step and a date.

## OUTPUT
90-130 words plus a subject line. Anchor, one-line pointer to
the attached quote, validity and start date in one sentence,
the invitation with its next step.

## RULES
- Never restate the price table in prose. The quote carries
  numbers; the note carries the reason to say yes.
- One anchor only. Two read as insecurity.

## EDGE CASES
- No validity date given: insert [VALID UNTIL] and flag it.
- They are running a formal procurement: drop the invitation
  and close on their process date instead.

## GOOD LOOKS LIKE
"Most of the names in your fund-financing book carry no public
rating — the attached covers all of them..."

---
name: 04-price-pushback-reply
description: Run when a client pushes back on price. Trigger - "run 04" plus their pushback and my floor if I have one.
---

# TASK 04 — PRICE PUSHBACK REPLY

## INPUT
Their pushback, verbatim if possible. My floor if I have one.
Deal context: term, seats, what the relationship is worth.

## PROCESS
1. Diagnose the pushback: budget ceiling, competing spend,
   ritual negotiation, or real value doubt. One line to me
   above the draft saying which.
2. Hold the price with ONE reason tied to a figure — coverage,
   contributor base, refresh frequency. One. Three reasons
   read as three excuses.
3. Offer one concession that is not a discount: payment terms,
   a phased module start, a longer term at locked pricing, an
   extra seat band.
4. Write the walk-away line, polite, held in reserve.

## OUTPUT
- One line to me: the diagnosis.
- The reply email (OUTPUT DEFAULTS apply).
- THE RESERVE: the walk-away line, marked "only if they push
  again", not included in the email body.

## RULES
- If I gave a floor, nothing below it appears anywhere, ever.
- If I gave no floor, ask for it BEFORE drafting. Hard stop.
- Never match a competitor number I have not seen in writing.

## EDGE CASES
- Their comparison is a rating agency subscription: it is not
  like-for-like. Say that to me, and make the reply ask what
  their agency feed covers of the unrated book.
- We are genuinely high for their use case: say so above the
  draft and give me the narrower-scope option, not a cave-in.

## GOOD LOOKS LIKE
"Diagnosis: ritual — procurement stage, no competitor named.
Reply holds and offers phased module start."

---
name: 05-meeting-prep
description: Run before a meeting that matters. Trigger - "run 05" plus who, their firm, what I want, and any history.
---

# TASK 05 — MEETING PREP

## INPUT
Who I am meeting and their role, what I want from the room,
history if I have it. Say if it is first contact or renewal.

## PROCESS
1. Compress their situation from ONLY what I gave you. Mark
   anything inferred as "guess:".
2. Restate my objective as one sentence with a number or a
   date in it. If mine was vague, sharpen it and say so.
3. Build the three questions most likely to move the deal —
   ones they must answer with information, not "yes".
4. Predict the two most likely objections from THIS buyer,
   each with my best one-line answer.
5. Define the close: what I ask for before leaving.

## OUTPUT — one page
THEIR SITUATION (2 lines) / MY OBJECTIVE (1 sentence) /
THREE QUESTIONS / TWO OBJECTIONS + ANSWERS / THE CLOSE.

## RULES
- Nothing generic. Every question must be impossible to reuse
  for another account without editing.
- Risk buyers test rigour. No adjective survives without a
  number behind it.

## EDGE CASES
- I gave you only a name: build the page with [GAPS] and list
  the three facts to get before the room.
- Renewal at risk: the close is a date for the next
  conversation, never the signature itself.

## GOOD LOOKS LIKE
"Q2: When your model validation team challenged the internal
ratings last cycle, what did they benchmark against?"

---
name: 06-follow-up-recap
description: Run after a meeting, from raw notes or a transcript. Trigger - "run 06" plus the notes. The output becomes the written record.
---

# TASK 06 — FOLLOW-UP RECAP

## INPUT
Raw meeting notes or a transcript. Who attended if not obvious.

## PROCESS
1. Extract only what was actually agreed. An idea discussed is
   not an agreement; park those under the open point.
2. Assign every agreement an owner and a date. If the room did
   not set one, propose it in [brackets].
3. Identify the ONE open point that matters. State it
   neutrally — this may be read by procurement or compliance.

## OUTPUT — one email, 150 words max
- WE AGREED: bullets, owner + date on each.
- STILL OPEN: the one point, one sentence, neutral.
- NEXT STEP: confirmed step with its date, last line.
- Subject: "[Firm] — recap and next step, [date]".

## RULES
- Write it so their procurement could read it cold.
- This email is the record. Precision over warmth; warmth is
  one clause in the opening line, no more.

## EDGE CASES
- The notes contradict themselves: take the later statement,
  flag the contradiction to me above the email, not in it.
- Nothing was agreed: say so honestly and propose the smallest
  concrete next step with a date.

## GOOD LOOKS LIKE
"WE AGREED: trial extract on their 200 largest unrated
counterparties — delivered w/c 22 Sep (me)."

---
name: 07-week-plan
description: Run Sunday night or Monday morning. Trigger - "run 07" plus calendar, open deals, and anything on fire. Must read on a phone.
---

# TASK 07 — WEEK PLAN

## INPUT
My calendar, open deals or a pipeline paste, anything on fire.

## PROCESS
1. Pick the three OUTCOMES that matter this week — not
   activities. Each tied to an account or the number.
2. Scan the calendar for what to decline or delegate. Write a
   one-line script for each so it costs me nothing to send.
3. Name one risk I am not looking at, phrased as a question.
   Derive it from what I pasted, not from generic sales risk.

## OUTPUT — half a page, phone-readable
THREE OUTCOMES (account + number each) /
DECLINE OR HAND OFF (item + one-line script) /
THE QUESTION (one line).

## RULES
- An outcome states what will be TRUE on Friday, not what I
  will do. "Trial extract signed off" not "chase the trial".
- Maximum three. If I gave you six fires, choose; say what you
  parked and why in one line.

## EDGE CASES
- Calendar wall-to-wall: the first outcome becomes carving the
  time, with the two meetings to move named.
- Nothing urgent: point the week at the biggest quarter gap
  from the last pipeline review.

## GOOD LOOKS LIKE
"Decline: Tuesday vendor webinar — 'Sitting this one out; send
the deck and I'll come back with questions.'"

---
name: 08-monthly-one-pager
description: Run at month end for the CEO. Trigger - "run 08" plus the month's numbers and anything she must hear from me first.
---

# TASK 08 — MONTHLY ONE-PAGER

## INPUT
Bookings vs plan, pipeline, wins and losses with values, and
anything the CEO should hear from me before hearing it
elsewhere.

## PROCESS
1. Line one is the number vs plan. No wind-up, no weather.
2. Three wins with values. Two losses with the honest reason —
   the real one, not the polite one.
3. Pipeline health in two lines: coverage ratio, biggest risk.
4. End with the ONE decision or support I need, written as a
   direct ask with a date.

## OUTPUT — one page, in this order
THE NUMBER / WINS (3, valued) / LOSSES (2, honest) /
PIPELINE (2 lines) / THE ASK (1, dated).

## RULES
- No adjective a number could replace. "Strong month" is
  banned; "+12% vs plan" is the sentence.
- Losses name the reason, never the person.

## EDGE CASES
- Bad month: same structure, same length. Line one is still
  the number. The ask becomes the recovery decision I need.
- I have no ask: say "No decision needed this month". Never
  invent one to fill the slot.

## GOOD LOOKS LIKE
"£412k booked vs £390k plan (+5.6%). / LOST: a reinsurer
(£61k) — they renewed an agency feed that does not cover their
unrated book, and nobody internally challenged it."