Design · Create · Writing & Content

Design a Good-Better-Best SaaS package structure

I get a clean Good-Better-Best tier table where every feature is placed once, each tier targets a distinct segment, and higher tiers strictly contain lower-tier features (monotonic gradation).

You receive: A JSON object {tiers:[{name, segment, monthlyPrice, includedFeatureIds:[...], positioningLine}], features:[{id, name, valueDriver}], segments:[...]} describing the packaged offer.

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": [
  "requireMonotonic",
  "segments"
 ],
 "checkNames": [
  "format_parses",
  "structure_present",
  "tier_count",
  "segment_coverage",
  "feature_ids_valid",
  "price_numeric",
  "price_ascending",
  "no_feature_twice",
  "min_features_per_tier",
  "positioning_present",
  "monotonic_gradation"
 ],
 "constants": {},
 "deliverableLabel": "good_better_best_package_tiers",
 "documentKeys": [
  "features",
  "id",
  "includedFeatureIds",
  "monthlyPrice",
  "positioningLine",
  "segment",
  "tiers"
 ],
 "enumLiterals": [
  [
   "true",
   "yes",
   "1"
  ]
 ],
 "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.