Copywriting Psychologist

Execution Steps

Step 1 - Anchor on the audience state Start from what the reader already believes, fears, and wants. Research basis: message effectiveness depends on prior belief structure and involvement (ELM; Zhang et al., 2024).

Step 2 - Translate the job into desired progress Turn the JTBD into a concrete before/after promise. Research basis: people respond to progress, not feature inventory (Volpp & Loewenstein, 2020).

Step 3 - Choose the dominant mechanism Decide whether the copy should rely on problem agitation, proof, identity, social belonging, relief, or aspiration. Research basis: persuasion routes differ by audience motivation and trust stage (Quick et al., 2018; Bagozzi et al., 2021).

Step 4 - Mirror voice of customer language Use the customer's own terms for the problem and desired outcome. Research basis: self-relevance and similarity increase processing and persuasion (Moyer-Gusé et al., 2022; Ooms et al., 2019).

Step 5 - Add proof at the resistance point Place evidence where skepticism will rise, not just at the end. Research basis: trust and credibility reduce perceived risk and improve adoption (Nagy et al., 2022; Rowley et al., 2015).

Step 6 - Close with a low-friction next step Make the call to action feel like a continuation of the reader's intent. Research basis: autonomy-preserving prompts outperform pressure when resistance is possible (Grandpre et al., 2003; Lavoie & Quick, 2013).

DECISION MATRIX

Variable: awareness stage

• If unaware -> write problem-led copy with high clarity and low jargon.
• If problem aware -> intensify consequences and define the problem precisely.
• If solution aware -> compare approaches and frame differentiation.
• If product aware -> lead with proof, specifics, and objections.
• If most aware -> compress and make the CTA frictionless.

Variable: emotional state

• If anxious -> emphasize safety, certainty, and support.
• If frustrated -> emphasize relief and speed.
• If aspirational -> emphasize identity, status, and progress.
• If skeptical -> emphasize proof, transparency, and specificity.

Variable: category trust

• If trust is low -> use more evidence and less flourish.
• If trust is moderate -> blend emotion and proof.
• If trust is high -> move faster into vivid desire language.

FAILURE MODES - DO NOT DO THESE

Failure Mode 1

• Agents typically: write pretty copy with no mechanism.
• Why it fails psychologically: style without mechanism does not change belief.
• Instead: label the psychological job each block is doing.

Failure Mode 2

• Agents typically: use emotional appeals for an audience that needs proof.
• Why it fails psychologically: the reader feels pressure instead of confidence.
• Instead: match proof density to the awareness stage.

Failure Mode 3

• Agents typically: overstate claims or invent certainty.
• Why it fails psychologically: credibility collapses when reality does not match the promise.
• Instead: be specific, bounded, and honest.

ETHICAL GUARDRAILS

This skill must:

• Tell the truth in persuasive language.
• Keep claims specific and verifiable.
• Preserve the user's freedom to decide.

The line between persuasion and manipulation is when the copy tries to bypass informed choice by distorting reality or inventing urgency that is not real. Never cross it.

SKILL CHAINING

Before invoking this skill, the agent should have completed:

• @customer-psychographic-profiler
• @awareness-stage-mapper
• @jobs-to-be-done-analyst

This skill's output feeds into:

• @headline-psychologist
• @social-proof-architect
• @objection-preemptor
• @sequence-psychologist
• @pitch-psychologist

OUTPUT QUALITY CHECK

Before finalizing output, the agent asks:

• Did I match the audience's awareness stage?
• Did I write from the customer's language and not mine?
• Did I place proof at the right resistance point?
• Does every major block have a psychological job?
• Does the copy preserve autonomy and credibility?

Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.