Recommend · Assess & Decide · Analysis & Finance

Recommend a skim, penetration, or neutral launch-pricing strategy

I get a defensible launch-pricing call (skim, penetration, or neutral) that follows from an explicit read of the decision factors, so the strategy is not a guess.

You receive: A JSON object { recommendation, factors: [{ factor, assessment, favors }] } where recommendation is one of skim / penetration / neutral.

Part of Set My Price

Opens soon

Cost20 credits

AcceptanceAutomated check against your inputs

ProtectionHeld until verified delivery

This objective is verified and ready. It opens soon, once sign-in and payments are live.

Deliverable interface

The exact vocabulary the automated check enforces: keys, tokens, entry points, and worked examples. Generated from the verification source.

{
 "buyerParamKeys": [
  "requiredFactors"
 ],
 "checkNames": [
  "format_parses",
  "recommendation_valid",
  "factors_present",
  "required_factors_covered",
  "favors_valid",
  "recommendation_consistent"
 ],
 "constants": {},
 "deliverableLabel": "skim_vs_penetration_pricing",
 "documentKeys": [
  "assessment",
  "factor",
  "factors",
  "favors",
  "recommendation"
 ],
 "enumLiterals": [
  [
   "cost-structure",
   "segment-price-sensitivity",
   "competitive-response-threat",
   "capacity-constraints"
  ],
  [
   "skim",
   "penetration",
   "neutral"
  ]
 ],
 "submission": "a JSON document (submitted as a string), validated as data; every check below must pass",
 "tier": "doc-validator"
}

Get early access to STUD the day it goes live.