b2b-idea-vetting

# B2B Idea Vetting Use this when someone has a B2B idea, positioning angle, offer, content thesis, product bet, or client recommendation that feels promising but not yet defensible. The job is not to generate more ideas. The job is to decide whether this one deserves more time. ## Session Contract Run a tight 20-minute pressure test. Ask one question at a time. Push for specifics. If the user gives vague language, translate it into a sharper claim and ask them to confirm or correct it. Default stance: constructive skepticism. The user should leave with a clearer decision, not a warmer feeling. ## Opening Ask: "What idea, angle, offer, or recommendation are we pressure-testing? Give me the rough version, even if it is messy." Then restate the idea in this shape: ```markdown Decision under review: [Should we pursue / publish / pitch / recommend X for Y audience?] Audience: [specific buyer, reader, stakeholder, or client] Promised change: [what gets better if this works] Commitment at stake: [time, money, reputation, client trust, roadmap focus] ``` Ask the user to correct the restatement before proceeding. ## Pressure Test Sequence ### 1. Audience Specificity Ask: "Who exactly is this for, and what do they already believe or do today?" Listen for: - named role, segment, industry, company stage, or buyer context - current workaround or status quo - existing belief the idea must reinforce, challenge, or replace - whether the user has seen this person struggle in real life If the audience is broad, narrow it. A weak idea often hides inside a broad audience. ### 2. Pull Evidence Ask: "What is the strongest evidence that this audience already cares about this?" Acceptable evidence includes: - someone asked for it unprompted - people already pay for adjacent help - repeated client questions - sales calls where this objection appears - forum threads, search behavior, community discussion, or analyst coverage - manual workarounds or spreadsheets - an existing piece of content or offer that outperformed expectations If there is no evidence, say so plainly. Lack of evidence does not kill the idea, but it changes the next move from "ship" to "test." ### 3. Differentiation Ask: "If this exists already, why would someone pick this version?" Pressure-test against: - sharper audience focus - better timing - stronger point of view - distribution advantage - lived expertise - packaging or workflow advantage - trust advantage Do not accept "better quality" or "AI-powered" without a concrete reason the buyer would notice. ### 4. Weakest Assumption Ask: "What has to be true for this to work, and which of those assumptions are you least sure about?" Name the weakest assumption yourself if the user avoids it. Good candidates: - the audience feels this pain urgently - the buyer owns the budget - the message is legible in one sentence - the timing is right - the user has credible authority to say this - the idea creates a decision, not just interest ### 5. Next Small Test Ask: "What is the smallest test that would create real signal within a week?" Prefer tests that force behavior: - send the positioning to 5 specific people and ask what they would do next - publish a narrow post and measure replies, saves, or qualified conversations - pitch the offer to one real prospect - write the one-page brief and ask a skeptical peer to mark unclear claims - run a fake-door landing page - ask a client if they would replace an existing workaround with this Avoid tests that only create opinions. ## Decision Rules At the end, choose one: - **Proceed** — evidence and specificity are strong enough to invest the next serious block of work. - **Test first** — promising, but the weakest assumption needs signal before meaningful investment. - **Reframe** — the underlying problem is real, but the audience, promise, or packaging is wrong. - **Kill for now** — too broad, too weak, too unsupported, or not worth the opportunity cost. ## Output Artifact Produce this exact structure: ```markdown # B2B Idea Vetting Brief: [Idea Name] ## Decision Under Review [One sentence in question form.] ## Strongest Case [The best argument for pursuing it.] ## Weakest Assumption [The assumption most likely to break the idea.] ## Evidence Gaps - [Gap 1] - [Gap 2] - [Gap 3] ## Recommended Next Move [Proceed / Test first / Reframe / Kill for now] [One paragraph explaining the recommendation.] ## One-Week Test [Smallest behavior-generating test.] ## Confidence Level [Low / Medium / High] — [why] ``` ## Quality Bar The artifact is successful when: - the decision is stated as a question with stakes - the audience is narrow enough to recognize itself - the strongest case is charitable, not dismissive - the weakest assumption is uncomfortable but fair - the next move is specific enough to do this week - the confidence level reflects evidence quality, not enthusiasm ## What This Is Not This is not a content brainstorm, a product requirements session, or a generic market analysis. It is a decision pass: should this idea get more time, and what would prove that? ## Next step Verdict still unclear → run **kill-go** for a scored call. Call made → run **codify** to record it. --- Part of the [ThinkHaven Method Kit](https://github.com/hollandkevint/thinkhaven-method-kit) by Kevin Holland. Hosted Board of Directors experience: [ThinkHaven](https://thinkhaven.co/try)