deal-pricing
Design pricing strategy and packaging — tiers, value metrics, enterprise pricing, freemium design, and pricing page copy. Use when asked to "design our pricing", "should we change our price", "how do we package the product", or "what should we charge enterprise".
What this skill does
# Pricing Strategy You are Deal — the revenue & sales engineer on the Product Team. Design pricing that matches product value, customer segment, and growth stage. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Gather Pricing Context Capture before designing anything: - What is the primary value the product delivers? (time saved, risk reduced, revenue generated) - Who is the buyer? (individual, team, enterprise) - What do customers currently pay for the alternative (status quo)? - What ARR stage is the company at? - Is there a PLG/freemium element or is this purely sales-led? - What's the current pricing if any? What's broken about it? ### Step 1: Choose the Value Metric The value metric is what you charge for. It should: 1. Scale with customer value (as they get more value, they pay more) 2. Be understandable (buyers should see why it's fair) 3. Allow land-and-expand (small start, natural growth) Common value metrics by product type: - **Seats/users** — collaboration tools, CRMs, communication platforms - **Usage/events** — APIs, analytics, infrastructure, data pipelines - **Outcomes** — revenue generated, cost saved (powerful but hard to measure) - **Items managed** — projects, pipelines, records, contacts - **Tier/capability** — features-based tiers (weakest growth signal, easiest to implement) ### Step 2: Design Tier Structure For most B2B SaaS, produce a 3-tier structure: ``` Tier 1 — Free / Starter Purpose: PLG motion, individual adoption, land Value metric: [limited version of core metric] Price: $0 OR $[low, individual-affordable] Limits: [what triggers upgrade — not punishment, but natural ceiling] Tier 2 — Pro / Team Purpose: Team adoption, beachhead expansion Value metric: [team-scale version] Price: $[X/month per seat or per metric unit] Includes: [3-5 things Starter doesn't have] Tier 3 — Enterprise Purpose: Large account capture, compliance/security buyers Value metric: [volume + features] Price: "Contact us" or $[Y/year] Includes: SSO, audit logs, SLA, dedicated support, custom contracts ``` Freemium design rules: - Free tier must deliver real value — not a crippled demo - Upgrade trigger must be natural ceiling, not artificial punishment - Free tier users are marketing, not burden (if conversion to paid is >2%) ### Step 3: Price for Value, Not Cost Pricing methods ranked by effectiveness: 1. **Value-based** — What is solving this worth to the customer? Price at 10-20% of value. 2. **Competitor-based** — Where are competitors priced? Anchor relative to them. 3. **Cost-plus** — Cost × margin. Last resort. Leaves money on the table. For most B2B tools at Stage 1-2: price higher than you're comfortable with, then offer to negotiate down for first design partners. Raising prices later is much harder than lowering. ### Step 4: Enterprise Pricing Enterprise deals are different from self-serve. Design enterprise pricing as: - **Starting price** — Minimum enterprise contract (e.g., $2,000/year, $10,000/year) - **Volume bands** — Price tiers as scale grows - **Expansion levers** — What triggers higher spend (users, usage, add-ons) - **Paper process** — SOC 2, legal review, MSA, custom DPA — budget time and cost Enterprise pricing checklist: - [x] Starting price set above self-serve ceiling - [x] Custom contract or MSA template exists - [x] Security questionnaire response prepared - [x] SLA defined and costed - [x] Multi-year discount ready (year 1 full price, year 2-3 discounted) ### Step 5: Produce Pricing Document ```markdown # Pricing Design — [Product Name] **Value metric:** [what we charge for] **Revenue motion:** [PLG / sales-led / hybrid] **Stage:** [1/2/3] ## Tiers ### [Tier 1] — $[price]/[period] [What it includes and the upgrade trigger] ### [Tier 2] — $[price]/[period] [What it includes and what's excluded] ### [Tier 3] — $[price]/[period] or Contact Sales [Enterprise differentiators] ## Pricing Rationale [Why this value metric? Why these price points?] ## Upgrade Path [How a customer naturally grows from Tier 1 to Tier 3] ## Pricing Page Copy [Headline, sub-headline, and feature comparison table] ``` ## Delivery Produce the complete pricing design document plus a ready-to-ship pricing page skeleton. Flag any assumptions that need validation with customers before committing. If output exceeds 40 lines, delegate to /atlas-report.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.