Design · Create · Writing & Content
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
Example
A sample of what this play produces. Your result is generated for your inputs.
Tiers
Starter
- Segment
- Solo founders
- Monthly Price
- 20
- Included Feature Ids
- F1
- F2
- F3
- F4
- F5
- Positioning Line
- For one founder: a 500-credit pack ($20) on auto-refill, per-play pricing at 4 cents a credit, and credits spend only on accepted work.
Team
- Segment
- Small product teams
- Monthly Price
- 100
- Included Feature Ids
- F1
- F2
- F3
- F4
- F5
- F6
- F7
- F8
- Positioning Line
- Everything in Starter plus a 2,500-credit refill ($100, 250 bonus credits), multi-project workspaces, and results that feed the next run.
Scale
- Segment
- Ops and engineering leads
- Monthly Price
- 200
- Included Feature Ids
- F1
- F2
- F3
- F4
- F5
- F6
- F7
- F8
- F9
- F10
- F11
- Positioning Line
- Everything in Team plus a 5,000-credit refill ($200, 750 bonus credits), team seats on one shared fact store, and a priority run queue.
Features
| Id | Name | Value Driver |
|---|---|---|
| F1 | Play catalog access (265 plays, 14 playbooks) | Ready-made plays replace the blank prompt |
| F2 | Workspace fact store | State a fact once and it fills every intake |
| F3 | Acceptance check on every deliverable | Credits are consumed only when a deliverable passes |
| F4 | Structured deliverable library | Results stay current and feed later runs |
| F5 | Auto-refill from the 500-credit pack ($20) | Purchased credits never expire, so a light month is never wasted |
| F6 | Auto-refill from the 2,500-credit pack ($100, 250 bonus credits) | Bonus credits stretch the monthly budget across weekly runs |
| F7 | Multi-project workspaces | A small team runs several product lines from one account |
| F8 | Deliverable composition (results feed later plays) | Each run leaves the system knowing more |
| F9 | Annual prepay packs (6,000/$240 and 18,000/$720) | The deepest bonus credits (1,500 and 5,000) for a year of runs |
| F10 | Priority run queue | Ops-scale usage settles without waiting |
| F11 | Team seats with shared fact store | One venture memory across ops and engineering leads |
Segments
- Solo founders
- Small product teams
- Ops and engineering leads
Opens soon
Cost50 credits
ProtectionSpent when the run starts · returned only if STUD is at fault
STUD opens runs for everyone soon, on every play at once.
Get early access to STUD the day it goes live.