Tessli

Guided research path

SaaS landing-page references

Goal

Focused references for studying SaaS positioning, landing-page structure, pricing presentation, proof, copy, and conversion patterns.

Audience

Founders, product marketers, and designers preparing or revising a SaaS marketing site.

Expected decision

A defensible SaaS landing-page direction covering positioning, page structure, proof, pricing, and iteration signals.

Continue in Boards

Save sources here, then use Boards to record the choices you want to carry into your project.

Ordered research sequence

Inspect one stage at a time

Start with the first stage, inspect each source against its prompt, and save the references that help you make the decision.

Stage 1

Frame the market

Inspect
Compare positioning, information hierarchy, and recurring page structures before choosing a direction.
Decision supported
Choose which category conventions to follow, adapt, or deliberately reject.
  1. Role — Why included
    SaaS Pages anchors the first scan with examples that combine visual structure and copywriting.
    Inspect
    Compare positioning, information hierarchy, and recurring page structures before choosing a direction.
    Decision prompt
    Choose which category conventions to follow, adapt, or deliberately reject.
  2. Role — Why included
    SaaS Landing Page broadens the comparison set across recognizable SaaS companies.
    Inspect
    Compare positioning, information hierarchy, and recurring page structures before choosing a direction.
    Decision prompt
    Choose which category conventions to follow, adapt, or deliberately reject.
  3. Role — Why included
    SaaSpo provides another curated market lens for identifying repeated conventions without treating them as rules.
    Inspect
    Compare positioning, information hierarchy, and recurring page structures before choosing a direction.
    Decision prompt
    Choose which category conventions to follow, adapt, or deliberately reject.

Stage 2

Assemble the page

Inspect
Inspect section-level composition, proof placement, copy patterns, and reusable landing-page structures.
Decision supported
Decide the page sequence and which sections deserve custom design versus established patterns.
  1. Role — Why included
    SaaS Websites supports screenshot-level comparison of complete pages and recurring patterns.
    Inspect
    Inspect section-level composition, proof placement, copy patterns, and reusable landing-page structures.
    Decision prompt
    Decide the page sequence and which sections deserve custom design versus established patterns.
  2. Role — Why included
    SaaS Examples adds product and email references when the marketing journey extends beyond the homepage.
    Inspect
    Inspect section-level composition, proof placement, copy patterns, and reusable landing-page structures.
    Decision prompt
    Decide the page sequence and which sections deserve custom design versus established patterns.
  3. Role — Why included
    Landingfolio helps inspect individual sections and templates before composing the full page.
    Inspect
    Inspect section-level composition, proof placement, copy patterns, and reusable landing-page structures.
    Decision prompt
    Decide the page sequence and which sections deserve custom design versus established patterns.

Stage 3

Validate conversion decisions

Inspect
Study pricing communication, commercial evidence, and visible website experiments.
Decision supported
Decide how to present price, proof, and iteration hypotheses before implementation.
  1. Role — Why included
    Landings supplies a broader landing-page reference set for checking whether the chosen structure is too narrow.
    Inspect
    Study pricing communication, commercial evidence, and visible website experiments.
    Decision prompt
    Decide how to present price, proof, and iteration hypotheses before implementation.
  2. Role — Why included
    Pricing Pages isolates pricing architecture, plan comparison, and purchase-friction patterns.
    Inspect
    Study pricing communication, commercial evidence, and visible website experiments.
    Decision prompt
    Decide how to present price, proof, and iteration hypotheses before implementation.
  3. Role — Why included
    Pages That Print adds examples connected to reported revenue outcomes while remaining directional evidence only.
    Inspect
    Study pricing communication, commercial evidence, and visible website experiments.
    Decision prompt
    Decide how to present price, proof, and iteration hypotheses before implementation.
  4. Role — Why included
    Glance exposes visible experiments and changes so the team can define what to test after launch.
    Inspect
    Study pricing communication, commercial evidence, and visible website experiments.
    Decision prompt
    Decide how to present price, proof, and iteration hypotheses before implementation.