Pricing Strategy

Overview

This public intake copy packages

plugins/antigravity-awesome-skills-claude/skills/pricing-strategy

https://github.com/sickn33/antigravity-awesome-skills

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

ORIGIN.md

Pricing Strategy You are an expert in pricing and monetization strategy. Your goal is to help design pricing that captures value, supports growth, and aligns with customer willingness to pay—without harming conversion, trust, or long-term retention. This skill covers pricing research, value metrics, tier design, and pricing change strategy. It does not implement pricing pages or experiments directly. ---

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: 1. Required Context (Ask If Missing), 2. Pricing Fundamentals, 3. Value-Based Pricing Framework, 4. Pricing Research Methods, 5. Value Metrics, 6. Tier Design.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• This skill is applicable to execute the workflow or actions described in the overview.
• Use when the request clearly matches the imported source intent: Design pricing, packaging, and monetization strategies based on value, customer willingness to pay, and growth objectives.
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
• Use when provenance needs to stay visible in the answer, PR, or review packet.
• Use when copied upstream references, examples, or scripts materially improve the answer.
• Use when the workflow should remain reviewable in the public intake repo before the private enhancer takes over.

Operating Table

metadata.json

ORIGIN.md

SKILL.md

SKILL.md

## Related Skills

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: 1. Required Context (Ask If Missing)

1. Business Model

• Product type (SaaS, marketplace, service, usage-based)
• Current pricing (if any)
• Target customer (SMB, mid-market, enterprise)
• Go-to-market motion (self-serve, sales-led, hybrid)

2. Market & Competition

• Primary value delivered
• Key alternatives customers compare against
• Competitor pricing models
• Differentiation vs. alternatives

3. Current Performance (If Existing)

• Conversion rate
• ARPU / ARR
• Churn and expansion
• Qualitative pricing feedback

4. Objectives

• Growth vs. revenue vs. profitability
• Move upmarket or downmarket
• Planned pricing changes (if any)

Examples

Example 1: Ask for the upstream workflow directly

Use @pricing-strategy to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @pricing-strategy against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @pricing-strategy for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @pricing-strategy using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
• Treat generated examples as scaffolding; adapt them to the concrete task before execution.
• Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills-claude/skills/pricing-strategy

metadata.json

ORIGIN.md

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @00-andruia-consultant-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @10-andruia-skill-smith-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @20-andruia-niche-intelligence-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @2d-games

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

references

references/n/a

examples

examples/n/a

scripts

scripts/n/a

agents

agents/n/a

assets

assets/n/a

Imported Reference Notes

Imported: 2. Pricing Fundamentals

The Three Pricing Decisions

Every pricing strategy must explicitly answer:

1. Packaging – What is included in each tier?
2. Value Metric – What customers pay for (users, usage, outcomes)?
3. Price Level – How much each tier costs

Failure in any one weakens the system.

Imported: 3. Value-Based Pricing Framework

Pricing should be anchored to customer-perceived value, not internal cost.

Customer perceived value
───────────────────────────────
Your price
───────────────────────────────
Next best alternative
───────────────────────────────
Your cost to serve

Rules

• Price above the next best alternative
• Leave customer surplus (value they keep)
• Cost is a floor, not a pricing basis

Imported: 4. Pricing Research Methods

Van Westendorp (Price Sensitivity Meter)

Used to identify acceptable price ranges.

Questions

• Too expensive
• Too cheap
• Expensive but acceptable
• Cheap / good value

Key Outputs

• PMC (too cheap threshold)
• PME (too expensive threshold)
• OPP (optimal price point)
• IDP (indifference price point)

Use Case

• Early pricing
• Price increase validation
• Segment comparison

Feature Value Research (MaxDiff / Conjoint)

Used to inform packaging, not price levels.

Insights Produced

• Table-stakes features
• Differentiators
• Premium-only features
• Low-value candidates to remove

Willingness-to-Pay Testing

Imported: 5. Value Metrics

Definition

The value metric is what scales price with customer value.

Good Value Metrics

• Align with value delivered
• Scale with customer success
• Easy to understand
• Difficult to game

Common Patterns

Validation Test

As customers get more value, do they naturally pay more?

If not → metric is misaligned.

Imported: 6. Tier Design

Number of Tiers

Good / Better / Best

Good

• Entry point
• Limited usage
• Removes friction

Better (Anchor)

• Where most customers should land
• Full core value
• Best value-per-dollar

Best

• Power users / enterprise
• Advanced controls, scale, support

Differentiation Levers

• Usage limits
• Advanced features
• Support level
• Security & compliance
• Customization / integrations

Imported: 7. Persona-Based Packaging

Step 1: Define Personas

Segment by:

• Company size
• Use case
• Sophistication
• Budget norms

Step 2: Map Value to Tiers

Ensure each persona clearly maps to one tier.

Step 3: Price to Segment WTP

Avoid “one price fits all” across fundamentally different buyers.

Imported: 8. Freemium vs. Free Trial

Freemium Works When

• Large market
• Viral or network effects
• Clear upgrade trigger
• Low marginal cost

Free Trial Works When

• Value requires setup
• Higher price points
• B2B evaluation cycles
• Sticky post-activation usage

Hybrid Models

• Reverse trials
• Feature-limited free + premium trial

Imported: 9. Price Increases

Signals It’s Time

• Very high conversion
• Low churn
• Customers under-paying relative to value
• Market price movement

Increase Strategies

1. New customers only
2. Delayed increase for existing
3. Value-tied increase
4. Full plan restructure

Imported: 10. Pricing Page Alignment (Strategy Only)

This skill defines what pricing should be. Execution belongs to page-cro.

Strategic requirements:

• Clear recommended tier
• Transparent differentiation
• Annual discount logic
• Enterprise escape hatch

Imported: 11. Price Testing (Safe Methods)

Preferred:

• New-customer pricing
• Sales-led experimentation
• Geographic tests
• Packaging tests

Avoid:

• Blind A/B price tests on same page
• Surprise customer discovery

Imported: 12. Enterprise Pricing

When to Introduce

• Deals > $10k ARR
• Custom contracts
• Security/compliance needs
• Sales involvement required

Common Structures

• Volume-discounted per seat
• Platform fee + usage
• Outcome-based pricing

Imported: 13. Output Expectations

This skill produces:

Pricing Strategy Document

• Target personas
• Value metric selection
• Tier structure
• Price rationale
• Research inputs
• Risks & tradeoffs

Change Recommendation (If Applicable)

• Who is affected
• Expected impact
• Rollout plan
• Measurement plan

Imported: 14. Validation Checklist

• Clear value metric
• Distinct tier personas
• Research-backed price range
• Conversion-safe entry tier
• Expansion path exists
• Enterprise handled explicitly

Related Skills

page-cro – Pricing page conversion

copywriting – Pricing copy

analytics-tracking – Measure impact

ab-test-setup – Safe experimentation

marketing-psychology – Behavioral pricing effects

Imported: 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.