Price Formation » Histórico » Versión 2
Pedro Yobanis Piñero Pérez, 2025-07-15 19:09
| 1 | 1 | Pedro Yobanis Piñero Pérez | h1. Price Formation |
|---|---|---|---|
| 2 | |||
| 3 | Pricing - Reflection Guide |
||
| 4 | |||
| 5 | *1 · Product & Strategy ⬇️* |
||
| 6 | |||
| 7 | * What single business goal must pricing accelerate right now? |
||
| 8 | |||
| 9 | * Why: Price crafted for adoption (freemium) can starve cash if runway is the real need. |
||
| 10 | |||
| 11 | * Is the product inherently sticky once adopted? |
||
| 12 | |||
| 13 | * Why: Sticky products recoup revenue via expansion; non-sticky products must charge earlier. |
||
| 14 | |||
| 15 | * Will we run product-led, sales-led, or hybrid GTM in the next 12 months? |
||
| 16 | |||
| 17 | * Why: Each motion sets different list-price and discount expectations. |
||
| 18 | |||
| 19 | * Does pricing reinforce our positioning (premium vs. disruptive)? |
||
| 20 | |||
| 21 | * Why: Price signals market segment louder than marketing copy. |
||
| 22 | |||
| 23 | *2 · Customer & Value ⬇️* |
||
| 24 | |||
| 25 | * Who is the ideal customer profile and which budget line pays? |
||
| 26 | |||
| 27 | * Why: CIO budgets tolerate very different prices than hobbyist credit cards. |
||
| 28 | |||
| 29 | * What quantified outcome do we deliver (hours saved, \$ gained, risk avoided)? |
||
| 30 | |||
| 31 | * Why: Value-based pricing needs a credible ROI anchor. |
||
| 32 | |||
| 33 | * Have we run a real Willingness-To-Pay test? |
||
| 34 | |||
| 35 | * Why: A 1 % price lift ≈ 12 % profit boost in SaaS; don’t leave money on the table. |
||
| 36 | |||
| 37 | * Do different segments show different WTP? |
||
| 38 | |||
| 39 | * Why: Drives tiering or usage caps that match value delivered. |
||
| 40 | |||
| 41 | *3 · Cost & Unit Economics ⬇️* |
||
| 42 | |||
| 43 | * What is our fully-loaded COGS per unit of the value metric? |
||
| 44 | |||
| 45 | * Why: AI / usage products must price to cost anchor to protect margin. |
||
| 46 | |||
| 47 | * What gross-margin floor will we defend (≥ 70 %)? |
||
| 48 | |||
| 49 | * Why: Ensures cash for R&D and GTM. |
||
| 50 | |||
| 51 | * How volatile are those costs over time? |
||
| 52 | |||
| 53 | * Why: Volatile costs argue for variable or hybrid pricing over flat subscriptions. |
||
| 54 | |||
| 55 | 2 | Pedro Yobanis Piñero Pérez | *4 · Market & Competitive Context ⬇️* |
| 56 | |||
| 57 | * Which pricing models dominate our segment today? |
||
| 58 | |||
| 59 | * Why: Buyers anchor on familiar patterns; swimming upstream needs extra messaging. |
||
| 60 | |||
| 61 | * Where do we sit on the price spectrum vs. substitutes? |
||
| 62 | |||
| 63 | * Why: A premium can work—if extra value is obvious. |
||
| 64 | |||
| 65 | * Are rivals shifting to usage or hybrid because of AI costs? |
||
| 66 | |||
| 67 | * Why: Flat pricing may soon look outdated or risky. |
||
| 68 | |||
| 69 | *5 · Packaging & Metrics ⬇️* |
||
| 70 | |||
| 71 | * Which value metric best tracks customer success? |
||
| 72 | |||
| 73 | * Why: Tight linkage makes upsell feel natural, not punitive. |
||
| 74 | |||
| 75 | * Do we keep plan choices ≤ 5 blocks/tiers? |
||
| 76 | |||
| 77 | * Why: Too many options hurt conversion; 3–5 captures 95 % of demand. |
||
| 78 | |||
| 79 | * Do feature gates create or destroy value for our ICP? |
||
| 80 | |||
| 81 | * Why: One-plan models use usage caps; some markets expect classic feature tiers. |
||
| 82 | |||
| 83 | *6 · Expansion & Retention ⬇️* |
||
| 84 | |||
| 85 | * What built-in levers let customers spend more as they succeed? |
||
| 86 | |||
| 87 | * Why: Without them, Net Revenue Retention caps at 100 %. |
||
| 88 | |||
| 89 | * Do we know the target attach-rate for add-ons (e.g., 5–10 %)? |
||
| 90 | |||
| 91 | * Why: Add-ons lift margin without complicating core pricing. |
||
| 92 | |||
| 93 | * Will annual pre-pay or credit packs smooth cash flow? |
||
| 94 | |||
| 95 | * Why: Improves capital efficiency and shortens CAC payback. |
||
| 96 | |||
| 97 | *7 · Operational Guard-Rails ⬇️* |
||
| 98 | |||
| 99 | * Can we meter usage in real-time and show it in-product? |
||
| 100 | |||
| 101 | * Why: Transparent meters reduce “bill-shock” churn. |
||
| 102 | |||
| 103 | * Do we offer budget caps or auto-throttles? |
||
| 104 | |||
| 105 | * Why: Gives buyers confidence to experiment with variable pricing. |
||
| 106 | |||
| 107 | * Is there a schedule for price experiments (≥ twice a year)? |
||
| 108 | |||
| 109 | * Why: Pricing is a product—iterate with data. |
||
| 110 | |||
| 111 | *8 · Changes & Messaging ⬇️* |
||
| 112 | |||
| 113 | * Can we state the price in one clear sentence a buyer gets in < 10 s? |
||
| 114 | |||
| 115 | * Why: Complexity kills conversion. |
||
| 116 | |||
| 117 | * Do we have a grandfather policy for existing users when prices rise? |
||
| 118 | |||
| 119 | * Why: Prevents public backlash and churn spikes. |
||
| 120 | |||
| 121 | * Is there a playbook for migrating beta/freemium users to paid? |
||
| 122 | |||
| 123 | * Why: Smooth upsell preserves goodwill and ARR. |
||
| 124 | |||
| 125 | * Do we keep a documented price-increase playbook (timing, notice, refunds/credits)?Why: Being proactive avoids support fire-drills and lost trust. |
