price-psychology-strategist – skill Tài liệu & Office cho agent AI

Use a marketing planning and audience-research lens. Your task is to apply behavioral economics and price perception psychology to how pricing is structured, presented, and framed.

When to Use

• Use when pricing, packaging, or offer framing needs better perception of value and fairness.
• Use when testing anchors, tiers, decoys, or price presentation for conversion impact.

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](https://github.com/sickn33/agentic-awesome-skills/pull/451) by MMEHDI0606; [immutable source snapshot](https://github.com/MMEHDI0606/antigravity-awesome-skills/blob/9c61357e3e6bb167946036f52ac1e28fc82e04d0/skills/price-psychology-strategist/SKILL.md). This identifies the contributed instructions, not scientific validation or a new upstream endorsement.

CONTEXT GATHERING

Before designing pricing presentation, establish:

1. The Target Human - psychographic profile, willingness to pay, and trust stage.

2. The Objective - conversion, upsell, or plan selection.

3. The Output - pricing presentation strategy.

4. Constraints - product type, market norms, and ethical limits.

If the value context is unclear, ask before proceeding.

PSYCHOLOGICAL FRAMEWORK: PRICE SIGNAL ARCHITECTURE

Mechanism

People judge price relative to anchors, reference points, and perceived pain of paying. Price presentation changes valuation, not just arithmetic. Use anchoring, decoy effects, framing, and payment decoupling only when they strengthen honest value perception (Ariely et al., 2003; Beggs & Graddy, 2009; Bertrand et al., 2010; Houdek, 2016; Yu et al., 2025; Whitley et al., 2025).

Execution Steps

Step 1 - Set the reference point

Decide what the audience will compare the price against.

*Planning hypothesis (verify before presenting as research): valuation depends on the anchor and the local cognitive frame (Houdek, 2016; Ariely et al., 2003).*

Step 2 - Choose the price structure

Pick monthly, annual, per-use, bundle, or tiered framing.

*Planning hypothesis (verify before presenting as research): unit framing and price format shift perceived value (Whitley et al., 2025; Yu et al., 2025).*

Step 3 - Decide on decoys and anchors

Use a decoy only if it clarifies the preferred option.

*Planning hypothesis (verify before presenting as research): asymmetrically dominated alternatives can redirect choice without changing actual value (Ariely et al., 2003; Beggs & Graddy, 2009).*

Step 4 - Reduce pain of paying honestly

Consider payment timing, bundling, or subscription framing.

*Planning hypothesis (verify before presenting as research): the pain of paying and payment decoupling affect willingness to buy (Bertrand et al., 2010; price perception research).*

Step 5 - Check for quality signal collapse

Ensure the price presentation does not undermine premium positioning.

*Planning hypothesis (verify before presenting as research): price is also a quality cue; discount framing can damage inference (Houdek, 2016; Yu et al., 2025).*

DECISION MATRIX

Variable: audience sensitivity

• If price sensitive -> emphasize affordability, savings, and clarity.
• If value sensitive -> emphasize outcomes and total return.
• If premium sensitive -> emphasize quality signal and confidence.

Variable: product type

• If commodity-like -> use comparison and savings framing.
• If premium -> use anchor strength and quality cues.
• If recurring service -> reduce monthly pain with annual or bundle framing.

Variable: trust stage

• If low trust -> keep pricing plain and transparent.
• If medium trust -> add anchors and comparison.
• If high trust -> optimize the package, not just the number.

FAILURE MODES - DO NOT DO THESE

Failure Mode 1

• Agents typically: use anchors so high they feel fake.
• Why it fails psychologically: fake anchors trigger suspicion.
• Instead: use credible anchors tied to real alternatives.

Failure Mode 2

• Agents typically: use decoys that feel manipulative.
• Why it fails psychologically: people resent being steered without understanding why.
• Instead: use decoys only when they clarify value.

Failure Mode 3

• Agents typically: discount premium offers until quality signals collapse.
• Why it fails psychologically: cheap-looking pricing can weaken perceived quality.
• Instead: protect the product's status signal.

ETHICAL GUARDRAILS

This skill must:

• Present real prices honestly.
• Avoid deceptive countdowns or fake comparisons.
• Support informed choice.

The line between persuasion and manipulation is framing a real value choice versus engineering confusion so a customer cannot tell what they are actually paying for. Never cross it.

SKILL CHAINING

Optional context from related skills (equivalent supplied research is sufficient; do not create a prerequisite cycle):

• [ ] @loss-aversion-designer
• [ ] @trust-calibrator

This skill's output feeds into:

• [ ] @copywriting-psychologist
• [ ] @pitch-psychologist
• [ ] pricing-page drafts

OUTPUT QUALITY CHECK

Before finalizing output, the agent asks:

• [ ] Did I set a credible reference point?
• [ ] Did I choose a price format that fits the product?
• [ ] Did I avoid manipulative decoys?
• [ ] Did I protect the quality signal?
• [ ] Does the pricing presentation preserve trust?

Example

User request:

> Review this pricing and packaging for perceived value, fairness, anchoring, and avoidable confusion.

Illustrative output: If approved prices are €12 monthly or €120 billed annually, state the annual charge and €24 annual saving against twelve monthly payments; disclose renewal and cancellation terms.

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.