Define: Pricing Strategy

This skill puts one honest price on the user's product — fast. It turns a filled-in Product Offer (and Persona, if available) into a four-section Pricing Strategy: who pays, one launch price said out loud, 2–3 real anchors, and the plain-English price line that carries the number into the Mini-Launch.

The goal is deliberately not a complete monetization model. That work — pricing ladder, tiers, cost & margin, revenue-model coherence — lives in the optional BONUS-Business-Strategy-Deep-Dive.md (filled by studio-define-business-strategy), which most people don't need until the money questions get real — typically before spending on paid channels in Distribute. This skill exists because the Mini-Launch (the next step in the Define checklist) needs a price to carry, and founders will happily spend three weeks "figuring out pricing" as a way of not talking to anyone. Twenty to thirty minutes, one number, done.

A price the founder has never said out loud is not a price — it's a guess hiding in a spreadsheet. The measure of success for this session is that the user can finish the sentence "it'll be about ___" to a stranger without flinching.

Session length: 20–30 minutes. Claude does the anchor-price research live in the session; the user's job is to react and commit. Do not let this session expand into business-strategy territory — if the conversation drifts to tiers, margins, or freemium debates, park it: "that's the optional Business Strategy Deep Dive; right now we need one number you can say this week."

Inputs

Before starting, locate the following in the ProductOS folder — productos/ at the app repo root, or the current folder in a standalone ProductOS checkout. Look there before searching more widely, and never search node_modules/, build output, or vendored code:

1. The Product Offer — usually 1-Product-Offer.md. The required input. The Customer, Outcome, and Mechanism sections drive who pays and what shape the price takes.
2. The Pricing Strategy template — usually 3-Pricing-Strategy.md. Defines the exact output structure, and is also the file the skill rewrites in place at the end.
3. The Customer Persona — usually 2-Customer-Persona.md, if filled in. Optional but the single most useful input: willingness-to-pay, anchor products, and budget bucket come from here.

If the Product Offer is missing or mostly empty, stop and point the user to studio-define-offer-builder first.