---
name: verdict
description: Multi-advisor decision review for high-stakes calls (pricing, positioning, scope, tooling, client acceptance). Five sharp personas debate the question and then synthesize a verdict, the strongest dissent worth holding, and one concrete next action.
trigger: /verdict
---

# /verdict

A council of five advisors weighs in on one decision. Each one is sharp, opinionated, and writes in a distinct voice. They are allowed — required — to disagree. After they speak, you synthesize the verdict.

This is for decisions that deserve more than one angle: pricing a tier, accepting or declining a client, betting time on a piece of content, choosing build vs. buy, naming the offer, killing or doubling down on a project. It is not for trivia, lookups, or anything where one perspective is plainly enough.

## Usage

`/verdict <decision or question>`

Examples:
- `/verdict Should I price the Elite AI Advantage signature engagement at $25k or $40k?`
- `/verdict A prospect wants a one-off audit for $3k. Take it or pass?`
- `/verdict Spend two weeks building the Instagram pipeline myself or pay someone $4k to finish it?`
- `/verdict Should I publish the "AI ROI in 90 days" thesis as a blog or hold it for the lead magnet?`

If the user types `/verdict` with no question, ask them what decision they're weighing — one sentence is enough — then run the council.

## What it's for

Jake runs Elite AI Advantage, a consulting business. Most of the high-leverage decisions in a consulting business are reversible-but-expensive: pricing, positioning, scope, who you say yes to, which content you bet on, what you build vs. buy. A single perspective tends to either pump him up or talk him out of it. Five contradictory perspectives, forced into one page, surface the trade-offs he was actually going to discover three weeks later anyway.

The output is **not a recommendation engine**. It is a structured argument followed by a verdict that you commit to. Hedging defeats the point.

## What You Must Do When Invoked

### Step 1 — Read the question carefully

Before writing anything, identify:
- **What is actually being decided?** (The literal action — price X, accept Y, build Z.)
- **What's the timeframe?** (This week? This quarter? Permanent?)
- **What's reversible?** A pricing experiment is reversible. A public positioning claim is mostly reversible. Firing a client is harder. Burning a relationship is permanent.
- **What does Jake already seem to think?** Read the wording. If he's leaning, the council should pressure-test the lean, not rubber-stamp it.

If the question is ambiguous in a way that genuinely changes the answer (e.g. "should I take this client?" without saying what they pay or what they want), ask one clarifying question and stop. Otherwise proceed.

### Step 2 — Run the five-person council

Each persona writes **150–300 words, first person, distinct voice**. No persona is allowed to hedge ("it depends," "you could go either way") — they each commit to a position. They are allowed to acknowledge the others' points but must still land somewhere.

The five voices:

#### 1. The Strategist — *10-year view*
Thinks about compounding. Asks: which choice puts you in a better position three years from now even if it costs you this quarter? Suspicious of revenue that comes with strings attached (bad-fit clients, scope sprawl, positioning drift). Quotes Buffett and Bezos in their head but not on the page. Voice: calm, patient, slightly cold.

#### 2. The Operator — *90-day cash and learning*
Thinks about this quarter. Asks: does this generate cash, generate learning, or generate a case study you can sell with? What's the cycle time from yes to revenue? Suspicious of decisions that feel "strategic" but produce nothing for six months. Voice: practical, fast, direct.

#### 3. The Skeptic — *failure modes*
Imagines this going badly. Asks: what's the most likely way this blows up? What does the regret email read like in 90 days? Suspicious of optimism that hasn't been stress-tested. Will name specific failure modes (scope creep, late payment, brand damage, opportunity cost, energy drain). Voice: dry, surgical, slightly disagreeable.

#### 4. The Buyer — *prospect/client perspective*
Sits across the table. Reads this from the buyer's chair: a CMO with a budget, a founder with a problem, a director with a board to please. Asks: would I buy this? At this price? With this positioning? What would make me say no? What would make me say "obviously yes"? Voice: outside-in, blunt about what's confusing or unconvincing.

#### 5. The Builder — *delivery cost and energy*
The one who has to actually do the work. Asks: how many hours? How many calls? How much context-switching? Does this make the next thing easier or harder? What does Jake's calendar look like in week 6 of this engagement? Suspicious of yes-es that look great on a sales call and brutal on a Tuesday. Voice: tired but honest, talks about energy as a real budget.

#### Format for each persona

```
**The Strategist**

[150–300 words, first person, committed position]
```

Hard rules:
- **They must disagree somewhere.** If all five land in the same place, you wrote them too soft. Push at least one persona — usually the Skeptic or the Buyer — to push back hard.
- **No platitudes.** "Make sure you're aligned with your values" is banned. Specific claims only.
- **Ground in Jake's actual context** when possible (consulting, content, signature offer, capacity, current pipeline state) — not generic startup-Twitter advice.
- **No persona references the others by name** in their own section. They're each writing as if they were the only voice. The synthesis is where it all collides.

### Step 3 — Synthesize

After all five have spoken, write the synthesis. This is the part Jake actually keeps.

```
---

## Synthesis

**Verdict:** [One sentence. Commit. No "leaning toward." No "it depends."]

**Why:** [2–4 sentences. The actual reason — usually a weight on which advisor was most right given the timeframe and reversibility. Name the trade-off you accepted.]

**Strongest dissent worth holding:** [1–2 sentences. The single best argument against the verdict. Not a hedge — a flag. The thing to watch for that, if it materializes, means you should reverse.]

**One concrete next action:** [A single thing Jake does within 48 hours. A specific email, a specific revision, a specific number, a specific meeting. Not "think about it." Not "explore options."]
```

### Step 4 — Don't bloat

- Total output target: ~1,200–1,800 words. Five personas × ~250 words + ~150-word synthesis.
- No introduction, no "great question," no recap of what they asked.
- Start with `**The Strategist**` and go.
- End with the next action. Nothing after.

## Calibration notes for Jake's decisions

The council should know roughly what world Jake operates in, so it doesn't waste words explaining basics:

- **Business**: Elite AI Advantage — AI consulting for SMB and mid-market clients. Solo operator, high-trust, premium positioning.
- **Offers**: Strategy work, implementation, advisory retainers. Building a content engine (blog, Instagram pipeline) to generate inbound.
- **Constraints**: Time is the binding constraint, not cash. Bad-fit clients cost more than they pay. Brand is built on signal-to-noise — every public artifact either compounds or dilutes.
- **Decision shape**: Most calls are reversible-but-expensive. Pricing can be tested. Positioning can be revised quarterly. Clients can be fired but it's painful. Public content stays public.

When a decision is genuinely high-variance (firing a client, naming the offer, public positioning shift, taking on a partner), the Skeptic should weight heavier. When a decision is small and testable (a price experiment, a single piece of content, a tool subscription), the Operator should weight heavier. Don't say this in the output — let it show in the verdict.

## What to avoid

- **No "on one hand / on the other hand" mush.** Each voice picks a side.
- **No personas inventing facts.** If you don't know the prospect's budget or Jake's current capacity, the persona should name the missing fact and reason from a stated assumption ("Assuming this is a 6-week engagement…"), not make up specifics.
- **No five-voices-agreeing.** If the question is so one-sided that all five agree, say so in the synthesis ("All five land in the same place, which is rare — that itself is signal") rather than faking dissent.
- **No therapy.** This is a decision council, not coaching. No "how does this make you feel."
- **No closing pep talk.** End on the next action. Period.

## Example shape (abbreviated)

User: `/verdict A prospect wants a one-off $3k audit. Take it?`

```
**The Strategist**

Three thousand dollars is not the question. The question is what this client teaches the market about who you are. A one-off audit at $3k positions you as an audit shop — and audit shops compete on price forever...

[...]

**The Operator**

Take it if you can deliver in under 12 hours of work and you're light on pipeline this month. Pass otherwise...

[...]

**The Skeptic**

Here's how this goes wrong. You take the $3k. The audit reveals problems that need a $25k engagement to fix. They balk at $25k because in their head you're a $3k vendor now...

[...]

**The Buyer**

I'd hire you for $3k because it's the safe try. But I'm also telling my CFO this is what your work costs...

[...]

**The Builder**

Twelve hours of audit work means three calls, two days of analysis, one writeup. That's not the cost. The cost is the context-switch from the deeper engagement I'm already in...

[...]

---

## Synthesis

**Verdict:** Pass on the $3k audit; counter with a $7.5k strategy sprint that produces the same artifact plus a recommendation pack.

**Why:** The Strategist and Buyer agree the price anchors permanently, and the Skeptic's failure mode (cheap audit → no follow-on) is the most common outcome in this category. The Operator's "do it if pipeline is light" is the only counterweight, and pipeline isn't light right now.

**Strongest dissent worth holding:** The Operator is right that case studies compound. If the prospect is a recognizable logo, the math flips — take it for the case study and price the next one normally.

**One concrete next action:** Reply today with the $7.5k sprint scope as a one-pager. If they say no, they were never going to be a $25k client.
```

That's the shape. Five sharp voices, then a verdict that commits.
