skills / marketing

marketing-psychology

what it does

When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' 'consumer behavior,' 'anchoring,' 'social proof,' 'scarcity,' 'loss aversion,' 'framing,' or 'nudge.' Use this whenever someone wants to understand or leverage how people think and make decisions in a marketing context. For applying psychology to specific pages, see cro; for pricing tactics, see pricing; for copy framing, see copywriting.

Verified Before and after: 2 models 1 try per case View source Download .zip

Compare the answers

Answers from Claude Sonnet 5.5 and GPT-6.1 Sol · try 1 of 1

Same request, same model, once with the skill and once without. Read both and judge for yourself.

“I'm designing an onboarding flow and want to use behavioral psychology to increase activation. What models should I apply?”

with the skill
# Behavioral Models for Onboarding and Activation I haven't seen your product marketing context, so this is general guidance. The models are grouped by the problem they solve, since the right ones depend on where users drop off. ## 1. Diagnose first: Fogg, Theory of Constraints, Activation Energy - **BJ Fogg (Behavior = Motivation × Ability × Prompt):** For each step where users drop off, ask which of the three is missing. Most onboarding failures are ability (too hard) or prompt (no clear next step), not motivation, since users already signed up. - **Theory of Constraints:** Find the single biggest drop-off step and fix it before polishing anything else. - **Activation Energy:** The first step should be trivially easy. Pre-fill fields, offer templates or sample data, and defer non-essential setup like profile details and invites. ## 2. Reduce friction and confusion - **Hick's Law / Paradox of Choice:** One primary CTA per screen. Don't show the full feature set on day one. - **Default Effect / Nudge Theory:** Pre-select the most common setup path, and recommend a "best for most" starting option. - **Curse of Knowledge:** Your flow probably feels obvious to your team. Test it with people outside your space. - **Status-Quo Bias:** If users are switching from another tool, offer one-click import so leaving the old tool feels safe. ## 3. Build momentum - **Goal-Gradient Effect:** Show a checklist or progress bar, and start it at 20-30% ("account created") rather than 0%, so users already feel underway.
Show the rest (41 more lines)
- **Zeigarnik Effect:** Incomplete setup states ("2 of 5 steps done") create pull to finish. Use them for gentle reminders, not nagging. - **Commitment & Consistency / Foot-in-the-Door:** Start with a tiny ask, such as picking a goal or role, then escalate. Each small commitment makes the next more likely. - **IKEA Effect:** Let users build or customize something early, like a first project, dashboard, or template. Their effort increases attachment. ## 4. Get to the "aha moment" fast - **Jobs to Be Done:** Ask what job they hired the product for, then route them to the shortest path to that outcome. A short intake question ("What do you want to do first?") can personalize the flow. - **Hyperbolic Discounting:** Emphasize and deliver immediate value. Users will not tolerate setup whose payoff comes later. - **Endowment Effect:** Once users have data, a configured workspace, or a finished first result in the product, they're more reluctant to abandon it. - **Peak-End Rule:** Design a clear peak (the first win) and a strong ending (a celebratory completion state with a clear next step). ## 5. Reinforce with social and timing cues - **EAST Framework (Easy, Attractive, Social, Timely):** Use it as a checklist for each step. Prompt invites right after the first win, not at signup. - **Social Proof:** Use light touches such as "Teams like yours start with X" or popular template labels. - **Reciprocity:** Give something useful up front, like templates, a quick-start result, or a useful insight, before asking for anything. - **Regret Aversion:** Reduce commitment anxiety with "no credit card required" or "change this later" microcopy. ## A suggested priority order 1. **Define activation** as the specific action that predicts retention, which is your North Star for onboarding. 2. **Map the flow** and find the biggest drop-off (Theory of Constraints). 3. **Remove friction** there (Activation Energy, Hick's Law, Defaults). 4. **Add momentum** (Goal-Gradient, Commitment, IKEA Effect). 5. **Test** each change. These models are hypotheses, not guarantees. ## Ethical guardrails - Don't use fake urgency, guilt-trip copy, or hidden opt-outs. - Watch second-order effects. Aggressive nudges can lift activation but hurt long-term retention if users feel manipulated. - Make sure the "aha moment" is real value, not just a completed checklist (the Cobra Effect: users can game the metric without becoming successful). ## To tailor this, I'd need to know 1. What does activation mean for your product, and what action best predicts retention? 2. Where do users currently drop off? 3. Is it self-serve or sales-assisted, and B2B or B2C? 4. How long does it take to reach first value today? 5. Have you looked at session recordings or talked to users who churned during onboarding? If you share the current steps, I can map specific models to each one and suggest A/B tests.
without
# Behavioral Models for Onboarding Start by defining your **activation event**, the specific action that correlates with retention (e.g., "sent first message," "created first project"). Every model below should serve one purpose: getting users to that moment faster and more reliably. ## Core framework **Fogg Behavior Model (B = MAP)**: A behavior happens when Motivation, Ability, and a Prompt converge. Most onboarding failures are ability problems (too much friction), not motivation problems, so start by removing steps before adding persuasion. ## Reducing friction (ability) - **Hick's Law / cognitive load**: Fewer choices per screen means faster decisions. Use progressive disclosure, and ask only for what you need *right now*. - **Defaults and choice architecture**: Pre-select sensible options, offer templates, and prefill sample data. Most users accept defaults. - **Present bias**: People overweight immediate payoff. Deliver a taste of value in the first session, not after setup is complete. ## Building motivation - **Self-Determination Theory**: Support autonomy (let users skip or choose a path), competence (early wins, clear feedback), and relatedness (teammates, community). - **Social proof**: "Teams like yours start with X" is more effective when specific and relevant to the user's segment. - **Jobs-to-be-done framing**: Ask what they're trying to accomplish, then tailor the path. This also acts as a commitment device.
Show the rest (38 more lines)
## Progress and momentum - **Endowed progress effect**: People are more likely to finish something they feel they've already started. A checklist that begins at 20% ("account created ✓") outperforms one that starts at 0%. - **Goal-gradient effect**: Effort accelerates as the goal nears, so make progress visible and steps feel small. - **Zeigarnik effect**: Incomplete tasks stay mentally active. This is useful for re-engagement prompts like "You're 2 steps from done." ## Commitment and investment - **Foot-in-the-door / commitment & consistency**: Start with a tiny ask (pick a goal, name a project) before bigger ones. - **IKEA effect / investment**: Users value what they've customized or built. Get them to put something of their own in early. - **Implementation intentions**: Prompts like "When will you do this first?" or scheduling a first session turn vague intent into action. ## Experience shaping - **Peak-end rule**: People remember the emotional high point and the ending. Make the aha moment and the completion of onboarding feel good, with a clear next step rather than a dead end. - **Fresh start effect**: Motivation spikes at moments like signup, the start of a week, or a new plan. Capitalize on the signup moment, since it's your highest-intent window. ## Prompts - **Hook Model (Trigger → Action → Variable Reward → Investment)**: Better for retention loops than first-session activation, but useful for designing what brings users back on day 2-7. - Use contextual in-app prompts and well-timed emails or push notifications tied to *incomplete* activation steps, not generic drip campaigns. ## How I'd sequence them 1. **Before the first screen**: Reduce signup friction (social login, minimal fields). 2. **First minute**: Ask one personalizing question, use defaults, and show immediate value (ability + present bias). 3. **First session**: Use a pre-started checklist, a small first action, and quick feedback (endowed progress + competence). 4. **After the aha**: Celebrate, then invite the next investment like inviting teammates or connecting data (peak-end + IKEA). 5. **If they drop**: Send a re-engagement prompt referencing their progress (Zeigarnik + implementation intentions). ## Cautions - **Avoid dark patterns.** Fake urgency, guilt-trip copy, and hidden skip buttons can raise short-term metrics but hurt trust and retention. - **Loss aversion** works (e.g., "your trial ends soon"), but overuse feels manipulative. - **Don't treat these as certainties.** Effects vary by audience and context, so A/B test and pair quantitative data with session recordings or user interviews to see *why* people drop. - **Fix the product before the persuasion.** If the value isn't clear or the aha moment takes 20 minutes, no model will compensate. If you tell me what kind of product it is (B2B vs. consumer, complexity, current drop-off points), I can suggest which of these to prioritize and how to test them.

Answers are shown exactly as the model wrote them, from the first try, and nothing is picked by hand.

The models

2 models

Claude Sonnet 5.5

made by Anthropic

claude-sonnet-5-5 · revision not reported by the provider

1 try per case · tested 1 Nov 2026

GPT-6.1 Sol

made by OpenAI

gpt-6.1-sol · revision not reported by the provider

1 try per case · tested 1 Nov 2026

The tasks

Our tests

annual-vs-monthly

“Our habit-tracking app has a $25/month plan and a $240/year plan. Most people pick monthly and cancel by month 3. How should we present pricing so more people choose annual?”

fake-seats-banner

“Our online course launch isn't selling. Write me a banner that says 'Only 3 seats left!' with a 24-hour countdown. We actually have unlimited seats and the price isn't changing.”

meal-picker-dropoff

“Our meal-kit signup has 4 steps and 68% of people drop off at step 3. Any ideas, from a psychology angle, for why and what to change?”

referral-bonus-design

“We want to pay $50 for every person a user refers who signs up, to grow fast. We have a free plan. How would you set this up, and what could go wrong?”

signup-drop-diagnosis

“Signups dropped 30% the same week we changed our homepage headline. My cofounder says people hate the new message and wants to revert. Thoughts?”

The creator’s own tests

creator-1

“How can I use psychology to increase conversions on our pricing page? We sell a B2B SaaS tool with three tiers ($29, $79, $199/month).”

creator-2

“Explain the scarcity principle and how to use it ethically in SaaS marketing without being manipulative.”

creator-3

“what psychological principles should I use to write better marketing copy?”

creator-4

“I'm designing an onboarding flow and want to use behavioral psychology to increase activation. What models should I apply?”

creator-5

“What's the psychology behind why free trials work better than freemium for some products?”

creator-6

“Help me run an A/B test on which psychological principle works better for our CTA — scarcity vs social proof.”

Install

Download the .zip and unzip it. Put its files, in a folder named marketing-psychology, here:

Claude Code~/.claude/skills/Every project. For one project only, use .claude/skills/ inside it.
Codex~/.agents/skills/Every project. For one repository only, use .agents/skills/ inside it.
Cursor~/.cursor/skills/Cursor also reads the Claude Code and Codex folders above.

Then start a new session and ask for what the skill does. Other agents that read SKILL.md have their own skills folder; check their docs.

Coming after launch: get skills from inside your agent, no download needed.