Pricing Table
A pricing table organizes plans, prices, limits, features, and buying terms for comparison.
| Capability | Starter | Studio | Team |
|---|---|---|---|
| Price per month | $0 | $12 | $29 |
| Projects | 1 | Unlimited | Unlimited |
| Members | 1 | 3 | 10 |
| SVG export | — | ✓ | ✓ |
| Support | Community | Priority | |
| Purchase condition | No card | 14-day trial | 14-day trial |
| Next step |
A real example
Three plans line up monthly price, yearly billing, limits, support, taxes, and a trial action.
Main parts
- 01Trigger or task context
- 02Primary control surface
- 03Feedback, focus, and dismissal
Use it when
Use it when buyers need to compare important differences in cost and value.
Do not use it when
Never hide fees, fake old prices, or fake limited supply. Explain why a plan is highlighted.
Name used in code
plans + billing period + feature matrix Before you ship
Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states.
Outcome: Use Pricing Table to solve this user need without losing the current context. User context: Three plans line up monthly price, yearly billing, limits, support, taxes, and a trial action. Recommended pattern: Pricing Table. Why it fits: Use it when buyers need to compare important differences in cost and value. Do not use it when: Never hide fees, fake old prices, or fake limited supply. Explain why a plan is highlighted. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.
Check this request
Review the current use of Pricing Table. Definition: A pricing table organizes plans, prices, limits, features, and buying terms for comparison. Release checks: Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.