PricingTable
PricingTable and PlanCard: equal-height plan columns with feature lists, a featured plan, and a current-plan state.
- 1 seat
- 20 invoices/ month
- Email support
- Custom branding
- API access
- 10 seats
- Unlimited invoices
- Priority support
- Custom branding
- API access100k calls
- Unlimited seats
- Unlimited invoices
- Named account manager
- Custom branding
- API accessunmetered
import { PricingTable, PlanCard, FilterTabs } from '@objectifthunes/whiteboard'
<PricingTable
columns={3}
toggle={<FilterTabs value={period} onChange={setPeriod} options={PERIODS} />}
>
<PlanCard
name="Team"
price="€29"
period="/ month"
lede="For a small studio with real clients."
featured
badge="Most popular"
action={<Button>Choose Team</Button>}
features={[
{ label: '10 seats' },
{ label: 'API access', detail: '100k calls' },
{ label: 'SSO', included: false },
]}
/>
{/* the plan they already have */}
<PlanCard name="Scale" price="€79" period="/ month" current
action={<ButtonLink href="/billing" variant="secondary">Manage plan</ButtonLink>} />
</PricingTable>featured is for the plan you want chosen; current is for the plan the viewer already has. When both apply, current wins the emphasis — upselling someone into the plan they are on is a bug, not a conversion.
Excluded features are struck through with a cross rather than omitted. Showing what a plan does not include is what makes the comparison do any work; a list of only positives reads the same on every tier.
Prices are ReactNode, so currency, rounding and locale stay yours. The kit does not know whether you charge per seat, in cents, or with VAT included.
Equal-height columns on wide screens, stacking to one column under 880px. The stacking order is your JSX order, so put the plan most people should pick first if the table is likely to be read on a phone.