Shadcn featured sections for SaaS

Four to six. More than six and visitors stop reading; fewer than four and the section feels thin. The mistake is to list every feature you've shipped — that's a spec sheet, not a marketing page. Pick the four or five features that actually drive conversion and lean into them. Visitors decide based on whether your product solves their specific problem, not based on whether your feature list is exhaustive.

Bento for products with visual outputs (dashboards, design tools, analytics). Alternating rows for products where each feature needs deep context (developer tools, complex workflows). Bento works because it lets visitors visually scan five features in five seconds; rows work because each row gets a paragraph and a screenshot. Don't ship both — pick the one that matches your product's visual character and commit.

No. Feature-section CTAs fragment the visitor's attention — five 'Learn more' links pulling toward five different docs pages dilute the funnel. Use one section-level CTA at the bottom ('Start free trial' or 'See all features') that consolidates intent. The feature tiles themselves do the work of telling the story; the CTA at the bottom captures whatever conversion intent the section earned.