pricing

Comparison Grid Structure

Side-by-side plan tiers with prices, feature checklists, and one recommended column.

Variant

Use for the plans / packages slide — two to four tiers compared on price and features, with one tier elevated as the recommendation. The recommended tier is marked explicitly (it is usually the middle one, not the last), so the eye lands where you want it.

pitchtradeoffrecommendation

When to use

Two to four tiers. Each tier is one column; the grid holds three across by default (two / four adjust the count). Past four the columns crowd and the prices stop scanning — move secondary options to a follow-up slide.
Same features, same order, every tier. The columns only compare if each tier lists the identical feature set in the identical order — [x] where it's included, [/] where it isn't. Drifting features between tiers defeats the at-a-glance read.
Mark the recommendation. Add *Most popular* (or *Best value*, *Recommended*) to the tier you want chosen — it renders as a ribbon and elevates the card. Usually the middle tier, which is why the marker is explicit rather than positional.
A 'who it's for' line per tier. Each tier ends with one marker-less line naming its audience (‘For scaling teams.’). It anchors the bottom of the card and turns a price into a decision.

When not to use

More than four tiers. Five-plus columns shrink below readability and the price comparison collapses. Curate to the tiers that matter, or use compare-table for a dense feature-by-plan matrix.
Every tier marked popular. Elevate exactly one tier. Two ribbons cancel out and the eye has nowhere to land — the whole point of the marker is a single recommendation.
Features that drift between tiers. If each tier lists a different set of features, the columns can't be compared row-for-row. Keep the feature list and order identical; toggle inclusion with [x] / [/].
A wall of red 'not included'. Use [/] (muted, struck through) for an absent feature, not [ ] (alarming empty/fail). A pricing table sells what's included; it shouldn't read as a list of denials.

Authoring

<!-- _class: pricing -->

## Pick the plan that fits the team.

- Starter `$0`
  - [x] First feature
  - [/] Second feature
  - For evaluating, one team.
- Growth `$49 / mo` *Most popular*
  - [x] First feature
  - [x] Second feature
  - For scaling teams.
- Enterprise `Custom`
  - [x] First feature
  - [x] Second feature
  - For procurement and compliance.

Slots

Slot	Selector	Required	Description
`title`	`h2`	yes	Slide heading — the choice the tiers resolve (‘Pick the plan that fits the team.’).
`tiers`	`ul > li`	yes	One top-level li per tier. Lead with the plain tier name (auto-bold), then a trailing inline-code price (`$49 / mo`, `Custom`). Add a single-asterisk marker (`Most popular`) to elevate one tier — it renders as a ribbon. Then a nested list: one feature per line led by a state marker, and a final marker-less ‘who it's for’ line.
`features`	`ul > li > ul > li`	yes	Feature rows, each led by a state marker: `[x]` included (green check), `[/]` not included (muted, struck through), `[-]` limited (half). The LAST nested li carries NO marker — a short ‘who it's for’ line that anchors the bottom of the card. Keep the feature set and its order identical across every tier so the columns scan.

Anatomy

┌─────────────────────────────────────────┐
│  header                                 │
│        Pick the plan that fits.         │
│                                         │
│    Starter    Growth*    Enterprise     │
│      $0         $49         Custom      │
│     [x x /]    [x x x]     [x x x]      │
│   one team   scaling     procurement    │
│                                         │
│  footer                           1/19  │
└─────────────────────────────────────────┘

Variants

`two` — Two — a pair of tiers

Two columns instead of three — self-serve vs. enterprise, monthly vs. annual, the classic good/better pair. The recommended marker still elevates whichever tier carries it.

<!-- _class: pricing two -->

## Two ways to buy.

- Self-serve `$49 / mo`
  - [x] Up to 25 seats
  - [x] SSO
  - [/] Dedicated CSM
  - [/] Custom contract
  - For teams that onboard themselves.
- Enterprise `Custom` *Recommended*
  - [x] Unlimited seats
  - [x] SSO + SCIM
  - [x] Dedicated CSM
  - [x] Custom contract
  - For procurement, security review, and scale.

`four` — Four — a full ladder

Four columns for a complete ladder from free to enterprise. Pair with compact if the feature lists run long; past four tiers reach for compare-table instead.

<!-- _class: pricing four compact -->

## The full ladder, free to enterprise.

- Free `$0`
  - [x] 1 seat
  - [/] SSO
  - For trying it out.
- Team `$29`
  - [x] 10 seats
  - [/] SSO
  - For small teams.
- Growth `$49` *Most popular*
  - [x] 25 seats
  - [x] SSO
  - For scaling teams.
- Enterprise `Custom`
  - [x] Unlimited
  - [x] SSO + SCIM
  - For procurement.