INSIGHT / HOMEPAGE REVIEW PATTERNS

Five homepage patterns, one first decision.

We compared five public product homepages to see how they explain a broad offer, guide a first choice, and use proof. This is a qualitative analysis, not a conversion study.

Sample: Stripe, Linear, Notion, Vercel, FigmaReviewed: August 10 to September 7, 2026

01 / FIRST DECISION

A broad promise needs a smaller entry point.

Stripe, Linear, and Vercel lead with a category-level promise. Each page then asks visitors to choose a more specific path, such as a business type, workflow, or product area. The broad line creates context, but the next choice makes it useful.

SiteLens read: After the hero, give visitors one clear way to choose where to start.

Cases: Stripe · Linear · Vercel

02 / PRODUCT BREADTH

Product breadth works better when it follows a job.

Notion presents knowledge, projects, search, and AI as parts of one workspace. Figma connects design, code, collaboration, and AI through a shared canvas. In both cases, the suite has a clear idea behind it, but a new visitor still needs a job based route into the product.

SiteLens read: Let visitors choose the problem they came to solve before showing the full product map.

Cases: Notion · Figma

03 / PROOF

Proof is strongest beside the decision it supports.

The five pages use customer names, adoption figures, scale statements, or customer quotes. Those details matter most when they sit near the workflow or product choice they help explain. A proof block at the bottom of a page asks the visitor to remember a claim for too long.

SiteLens read: Place the most relevant proof beside the first choice, not only in a later trust section.

Cases: Linear · Notion · Figma

04 / LANGUAGE

A product metaphor can unify a suite, but it cannot choose for the visitor.

Notion uses the idea of a shared workspace. Figma uses the canvas. These ideas make a large product family easier to remember, but they do not tell every visitor which product or workflow to open first.

SiteLens read: Keep the umbrella idea, then translate it into a role, job, or use case.

Cases: Notion · Figma

05 / NEXT ACTION

The next action should match the promise.

A page about product infrastructure can lead to deployment or a sales conversation. A page about a product system can lead to a workflow. A page for a broad financial platform can lead to a choice between business paths. The button makes the promise concrete.

SiteLens read: Name the action in the language of the visitor's next decision, not the company's internal navigation.

Cases: Stripe · Linear · Vercel

01 / CATEGORY

Name what the product is

Use the first line to place the offer before you explain the full product.

02 / FIRST JOB

Give visitors a place to start

Route the next click through a role, workflow, or problem the visitor recognizes.

03 / PROOF

Put evidence beside the choice

Use the proof that answers the hesitation created by the decision in front of the visitor.

CASE SOURCES

Read the five page reviews.

This comparison is based on public pages and dated observations. It does not claim that any page produces a measured conversion result.