Feature Comparison
Sets two options side by side with checkmarks and notes per row. Use it to contrast your product against an alternative and make the better choice obvious.
Sets two options side by side with checkmarks and notes per row. Use it to contrast your product against an alternative and make the better choice obvious.
Search blocks by description or jump to a page.
Feature Comparison opens with a centered heading and a short supporting paragraph that frames the plan choice, topped by a small badge announcing a new tier. Below that sits a bordered table with four columns: a feature name column on the left, then one column each for Basic, Pro, and Enterprise. Every row shows a green check or a red cross per tier, so a visitor can scan down and immediately see where each plan draws the line. A pair of call to action buttons follows the table, and the section closes with three trust indicators laid out in a row, each pairing an icon with a headline stat and a short caption.
The heading, badge text, and supporting paragraph are independent copy. The feature rows are driven by a plain data array, so you can add, remove, or rename rows without touching the layout. The trust indicators at the bottom are also standalone and can be dropped if your page already establishes credibility elsewhere.
Reach for this block when a visitor needs to decide between service tiers and you want that decision to feel simple. For a logistics and delivery platform it works well on a pricing or plans page, letting fleet operators see at a glance whether the Basic tier covers their route volume or whether they need the Enterprise tier for custom integrations and advanced analytics. It outperforms a plain pricing card grid when the differences between tiers are granular, because the row by row layout lets readers find the one capability they care about without reading every card in full.
A natural flow around it on a Marketing (Legacy) page:
Before
After
The table accommodates any set of capabilities that differ across service tiers. A few ways to put it to work:
Tip: keep the feature list to eight or ten rows so the table fits the viewport without scrolling and the check pattern stays easy to read.