pitch-psychologist

Use a marketing planning and audience-research lens. Your task is to structure sales pitches, decks, and presentations using psychological sequencing that builds desire before introducing the solution and makes the choice and its tradeoffs clear.

When to Use

• Use when a sales, investor, or product pitch needs stronger belief progression and audience alignment.
• Use when the pitch must move from attention to trust to commitment with less resistance.

Evidence and scope

Use observed audience research and verified product facts. Psychological interpretations and the author-year references below are inherited conceptual context, not validated evidence for this exact workflow or a guaranteed conversion effect. Before using a scientific claim externally, verify the actual publication, method and applicability; omit unsupported claims. This is marketing planning, not clinical diagnosis. Do not infer sensitive traits or exploit vulnerabilities.

Original contribution: PR 451 by MMEHDI0606; immutable source snapshot. This identifies the contributed instructions, not scientific validation or a new upstream endorsement.

CONTEXT GATHERING

Before building a pitch, establish:

1. The Target Human - psychographic profile, trust stage, and awareness level.
2. The Objective - the decision or commitment the pitch must produce.
3. The Output - deck, talk track, one-pager, or demo script.
4. Constraints - audience type, time limit, and ethical boundaries.

If the decision context is unclear, ask before proceeding.

PSYCHOLOGICAL FRAMEWORK: DESIRE-THEN-SOLUTION ARC

Mechanism

People are more persuadable when they first feel the problem, the aspiration, and the cost of staying put, then receive the solution as the natural resolution. Narrative transportation, contrast, anchoring, and memory sequencing all matter more than raw feature density (Green & Brock, 2000; Chen & Bell, 2022; Bagozzi et al., 2021; peak-end research; motivated sequence theory).

Execution Steps

Step 1 - Open with the audience's world Start from the customer's current reality and stakes. Planning hypothesis (verify before presenting as research): self-relevance and narrative transportation increase receptivity (Green & Brock, 2000; Dragojevic et al., 2024).

Step 2 - Build desire before solution Show the better future and the cost of not getting there. Planning hypothesis (verify before presenting as research): desire-first sequencing reduces defensive processing and improves belief change (Monroe's motivated sequence; narrative persuasion studies).

Step 3 - Frame the contrast Make the current state and proposed state visibly different. Planning hypothesis (verify before presenting as research): contrast and anchoring shape evaluation by shifting the reference point (Ariely et al., 2003; Houdek, 2016).

Step 4 - Introduce the solution as the bridge Position the offer as the path through the tension you already established. Planning hypothesis (verify before presenting as research): people accept solutions more readily when the problem has been emotionally and cognitively prepared (Bagozzi et al., 2021).

Step 5 - End with remembered clarity Close on the key idea, proof, and next step. Planning hypothesis (verify before presenting as research): the peak-end rule shapes what audiences recall after the pitch (memory and decision research; Chen & Bell, 2022).

DECISION MATRIX

Variable: audience type

• If technical -> lead with evidence, then implications, then demo.
• If executive -> lead with risk, opportunity, then business outcome.
• If consumer -> lead with desire, identity, then ease of action.
• If skeptical -> lead with proof, then only enough story to connect it.

Variable: awareness stage

• If unaware -> start with the problem and the cost of delay.
• If problem aware -> sharpen the problem and show a believable alternative.
• If solution aware -> show why your approach fits best.
• If product aware -> reduce hesitation with proof and clarity.

Variable: pitch length

• If short -> compress into problem, tension, bridge, ask.
• If medium -> add proof and comparison.
• If long -> add case logic, objections, and decision support.

FAILURE MODES - DO NOT DO THESE

…