Offer Stack and Pricing Builder

SKILL.md Preview

---
name: offer-stack-pricing-builder
description: Use this skill when the user asks Claude to package an offer, build a value stack, set pricing tiers, design good-better-best options, or decide how to present and price something. Trigger when the user mentions not knowing how to package a course, anchoring price, or phrases like 'how should I price and present this.' This skill helps produce a named value stack and a tiered price structure.
compatibility: Claude.ai, Claude Desktop
---

# Offer Stack and Pricing Builder

## Purpose
Convert a rough offer into a clear value stack and a tiered price structure, so the offer's worth is visible and pricing follows a repeatable logic.

## When to Use This Skill
Use it when the user has a deliverable but no clear packaging or pricing, or wants to add tiers to an existing offer.

## When Not to Use This Skill
Do not use it to write sales copy (use the sales page or VSL skills). Do not use it before the user knows what the offer actually delivers.

## Required Inputs
- What the offer delivers and the transformation it produces.
- The target buyer and their budget reality.
- Any existing assets that can become stack components.
- Whether the user wants one offer or multiple tiers.

## Workflow
1. Identify the core deliverable and its transformation.
2. Break supporting assets into named components, each with a plain value statement.
3. Assign an honest standalone value to each component and total the stack.
4. Set the price below the stacked value to create a visible gap.
5. If tiering, anchor with the high tier, make the middle the obvious choice, and keep the entry tier viable.

## Output Format
Return the named stack with per-component value lines and a total, then the recommended price, or the full tier table with what each tier includes and who it is for.

## Quality Standards
- Anchoring is deliberate: high tier first, target tier reads as the sensible pick.
- Tier differences are concrete (more access, more done-for-you, more support).
- Component values are defensible, not inflated.
- Uses contractions, no em dashes, no hype.

## Edge Cases
If the user has only one deliverable and no supporting assets, suggest realistic components to add rather than padding values. If budget reality is unknown, ask before recommending a price point.

## Safety and Limitations
Do not inflate component values past what is defensible or imply guaranteed returns.

## Test Prompts
1. I have a 6-week copywriting course I sell for $800. I also have templates, a private community, and could add monthly calls. Help me build a value stack and three pricing tiers.
2. I'm a web designer who only sells custom sites at $5,000. I want a good-better-best structure so I can capture smaller clients too. Help me design the tiers.
3. I have a single $1,500 done-for-you offer. It feels overpriced to prospects. Help me stack the value so the price feels like a deal instead of cutting it.

Skill Details

Package Preview

Trigger Phrases

• "I have a 6-week copywriting course I sell for $800. I also have templates, a private community, and could add monthly calls. Help me build a value stack and three pricing tiers."
• "I'm a web designer who only sells custom sites at $5,000. I want a good-better-best structure so I can capture smaller clients too. Help me design the tiers."
• "I have a single $1,500 done-for-you offer. It feels overpriced to prospects. Help me stack the value so the price feels like a deal instead of cutting it."