Team 4 · B2B SaaS Landing Page Reference
Inbound Engine Component Framework
A working reference for B2B SaaS marketing pages. Forty-one components, ten page recipes, twenty-four behavioural principles. Same library, different assemblies. Built for teams who want consistency at scale, and a faster path from brief to launched page.
Introduction · Read first
Internal Reference Manual
What this is
A working reference for B2B SaaS landing pages. Forty-one reusable components in twelve categories, ten page-template recipes showing how those components assemble into the common page types, and twenty-four behavioural principles explaining why each block does the job it does.
It's opinionated on purpose. Every component, every recipe, every annotation comes from what we've seen work across hundreds of B2B SaaS pages, and what we've seen quietly fail. Where there's a trade-off, the document picks a side and tells you why.
Why component-first
Most B2B SaaS marketing sites get designed page by page. The homepage gets one creative treatment. Pricing gets another. Product gets a third. Six months in, three different templates are doing similar jobs in different ways. Internal links are tangled. Every new page becomes a fresh design exercise.
Component-first fixes that. Pages stop being designs and become recipes, ordered stacks of pre-decided components. A new page is 80% structural decisions you've already made and 20% content. Pages launch faster. The design system stays coherent. The conversion experience is consistent across the funnel. It also matches how the tooling actually works. Webflow has Components. HubSpot has Modules. Every modern CMS works in blocks.
How to read this document
01 · Component Library
The inventory. Each component has a wireframe, the behavioural principles it uses, the variants worth knowing about, and the templates it shows up in. Use it to look up a specific block.
02 · Page Templates
The recipes. Each template shows the components in order with notes on why this stack and not another. Use it to plan or evaluate a specific page.
03 · Psychological Principles
The reference appendix. Twenty-four behavioural levers, one paragraph each. Useful for defending a structural choice, briefing a copywriter, or pressure-testing a competitor's page.
If you're a client
Use this to understand the structure we're proposing for your site, and to push back on it. The wireframes are deliberately rough so the conversation stays on what goes where and why, not on colours, fonts or animation. Brand and visual layer come on top once the structure is agreed.
Read the page templates first. Find the page types that match what you're building (homepage, pricing, product, etc.), look at the assembled stack, and read the assembly notes to understand why each block is there. If a block doesn't make sense for your business, tell us. The recipe is a starting point, not a contract.
Click any component in a stack to jump to its detail. Use the search in the top-left to find a specific block by name.
If you're a designer
Treat this as the structural constraint for your design work. The components define what kinds of blocks can exist. The templates define which blocks go where for each page type. Within those, you have full freedom on typography, spacing, imagery, motion and micro-interaction.
Start with the template you're designing. Read the assembly notes to understand why the stack is built this way before you change anything. If you want to break a structural rule, read the component's annotations first. Most rules can be broken. Some are load-bearing.
Each component and template has Download PNG and Copy image buttons underneath the wireframe. Drop the image into Figma as a reference layer and build your design from there.
What this is not
Category 02 · 5 components
Heroes
The hero is the page's contract. It says what this page is, who it's for, and what the next step is. Five hero patterns cover the full set of B2B SaaS page jobs.
Outcome hero
Audience hero
Product hero
Story hero
Form hero
• Bullet 2
• Bullet 3
• No obligation
Category 03 · 4 components
Trust & social proof
Borrowed credibility blocks. Used early to validate the buyer's instinct, repeated late to nudge action. Density and recognisability matter more than count.
Logo bar (full)
Compressed logo strip
Stats bar
Awards / analyst row
Category 04 · 5 components
Problem & value
The middle of the page does the persuasion work. These components frame the buyer's current pain, name the alternative, and turn features into outcomes the buyer actually cares about.
Status quo block
Value trio
How it works (3-step)
Day in the life
Feature deep-dive (alternating)
Category 05 · 3 components
Product showcase
Components that show what the product does instead of telling you about it. They bridge the gap between abstract value claims and concrete capability.
Tabbed product showcase
Capabilities grid (6 tiles)
Interactive demo / product video
Category 06 · 6 components
Proof & differentiation
Where the page earns trust and stakes its position. These blocks show specific outcome evidence, name peers who've succeeded, and (used right) acknowledge where competitors do better.
Featured customer + metrics
3-up testimonials
Pull quote
Why choose us teaser
Side-by-side comparison table
"Where they win" honest block
- Specific scenario where competitor wins
- Specific use case where competitor wins
- Specific buyer profile where competitor wins
Category 07 · 4 components
Conversion
The blocks where the page asks for the action. Pricing structure, ROI evidence and CTA blocks. The forms get their own category.
Pricing tier cards
Pricing feature matrix
ROI calculator
Final CTA block
Category 08 · 3 components
Forms
Three separate form components. Split on purpose because the right field set, validation and post-submit flow are different for each goal. Don't reuse a single form across all three jobs.
Demo booking form
Signup form (free trial / freemium)
Lead magnet form
Category 09 · 2 components
Integration & security
Two blocks that close out the practical objections from procurement, IT and security. The people the champion has to sell to internally.
Integrations grid
Security & compliance row
Category 10 · 2 components
Universal closers
Two components that should sit near the bottom of every marketing page. They do two jobs: handling objections and signalling depth (FAQ), and pushing internal link equity to pillar content (Related). Both matter for GEO and organic search.
FAQ block (GEO-optimised)
Related content
Category 12 · 4 components
Cross-link navigation
Card grids that link visitors across your segmentation axes (industry, company size, use case, role) without bloating any one page. The point is to capture long-tail search ("estimating software for small contractors") with focused pages, then connect them so the visitor can refine their path. Same library, different entry points.
Browse by industry
Browse by company size
Browse by use case
Browse by role
Page Templates · 10 recipes
Page templates
Each page is a recipe. A numbered stack of components in the order they appear on the page, plus notes on the structural choices. Same library, different assemblies. Universal closers (FAQ and Related Content) appear on every template.
Template 01 · 15 components
Homepage
The entry point for unaware traffic, brand search and bookmarked returns. Has to compress the whole pitch into one scrollable surface while leaving routes for every visitor type.
Page wireframe, assembled view
Trusted by 5,000+ teams
See full comparison →
100+ integrations · See all →
Assembly logic
Visitors land cold. The first 30 seconds answer three questions in order: What is this? Is it for me? Have others like me used it? The Outcome hero (1–2), Logo bar (3), and Status quo (4) handle that triad in sequence.
Mid-scroll the page does the persuasion work: the Value trio frames three outcomes, the Tabbed showcase compresses 3–5 capabilities into a single position, and a single Featured customer anchors it all to a real result. The Compressed logo strip after the customer story is a deliberate "still on the bandwagon" reinforcement before asking for a comparison.
Why this stack and not more
Homepages bloat. The temptation is to add every persona block, every industry callout, every awards row. Resist it. Solutions / Industry / Role get their own pages; the homepage is the lobby that points to them. A clean 14-component homepage outperforms a 22-component one.
Universal closers
FAQ at position 11 captures the "is this real?" objections that the rest of the page generated. Related Content at 12 gives the not-yet-ready visitor a learning path that still keeps them in the brand's content ecosystem. Both apply on every template.
Variants worth testing
- Swap Tabbed showcase (06) for Interactive demo (C05.3) on PLG/self-serve products
- Add Pricing teaser between Why choose us (09) and Integrations (10) for transparent-pricing brands
- Add Awards row (C03.4) between 03 and 04 for analyst-driven categories
Template 02 · 14 components
Solutions / Use Case
Built around a single job to be done. The visitor knows their problem ("I need to consolidate reporting") but hasn't picked a solution. The page's job is to make the case that this product is the right tool for that specific job.
Page wireframe, assembled view
Assembly logic
The narrative arc is: here's the job → here's the cost of not solving it → here's how this product solves it → here's what it'd cost vs save → here's someone like you who did it. Status quo at position 3 does the loss-framing work; the rest of the page sells the alternative.
Why no logo bar
Use case pages get qualified traffic from organic search and content links. They've already arrived warm, they don't need the "is this legitimate?" check that homepage logo bars do. The Featured customer (07) does heavier proof work because the visitor is here for the specific job.
The ROI calculator's job
Position 6 is deliberate: after the visitor understands what the product does, before they see the success story. Letting them input their own numbers builds investment, and the output anchors the price as a fraction of value when they hit Pricing later.
FAQ specificity
The FAQ on a Use Case page is use-case-specific: "How long does implementation take for [job]?", not generic product Q&As. Each use case page gets its own FAQ. Don't reuse a global FAQ across all pages, that defeats the GEO benefit.
Template 03 · 16 components
Solutions / By Industry
A vertical-specific landing for buyers who filter by industry. The page has one job. Convince the visitor that this product was built with their industry's specific constraints, vocabulary and compliance environment in mind.
Page wireframe, assembled view
Trusted by 5,000+ teams
Security overview →
Assembly logic
The Audience hero (2) is the entire job of this page in one block: it tells the visitor "this is for you" using their industry's eyebrow tag and vocabulary. The industry-filtered logo bar (3) follows immediately because peer logos in the same vertical are the strongest possible relevance signal.
Where compliance fits
Security & compliance row at position 6 (not at the bottom) because regulated industries (healthcare, finance, construction, public sector) have compliance as a deal-blocker, not a footnote. Putting it mid-page tells the visitor "we know your CISO will ask this and we have answers".
Vertical analyst row
The awards row (8) is industry-specific. Healthcare buyers care about KLAS not G2; construction buyers care about ENR. Generic analyst badges weaken the page. Pick badges the visitor's industry actually trusts.
Lead magnet bridge
The Related content (11) on this page should include at least one industry benchmark or report, gated, with the Lead magnet form. Industry decision-makers respond strongly to peer benchmark data, and it's the start of a long-cycle nurture.
Template 04 · 15 components
Solutions / By Role
A persona-led page for the practitioner buyer (RevOps lead, Head of Marketing, VP Engineering). Empathy-led structure. Shows the product understands their day, their KPIs and the case they'll have to make to their boss.
Page wireframe, assembled view
Assembly logic
The role page is empathy-first. The Day in the life (3) at position 3, sitting before any product talk, signals "we know your week, your meetings, the reports you build on Friday afternoons". Visitors who recognise themselves stay; those who don't bounce, which is fine. Self-qualifying is a feature.
Why a Pull quote here
Position 6 sits between the feature content and the capabilities grid because role-buyers respond strongly to peer voice. A 15-word quote from someone with the same job title at a recognisable company is more persuasive than three customer logos for this audience. Pick the quote where their language matches the page headline.
Capabilities as KPI dashboard
Position 7 frames the capabilities grid around the role's own KPIs: pipeline coverage for RevOps, MQL→SQL conversion for Marketing, deploy frequency for Engineering. The screenshot in each tile is the role's own dashboard view, not a generic product screenshot.
Champion enablement
Many role pages need a "bring it to your team" toolkit, a downloadable one-pager, ROI calculator, internal pitch deck. Treat this as a content choice within the Related content block (09) rather than a separate component. Practitioner buyers need ammunition, not just a demo CTA.
Template 05 · 17 components
Product
For the evaluator. The visitor knows roughly what they want and is comparing capabilities. The page's job is to show (not tell) the full surface, deal with the technical objections, and stand its ground against competitors.
Page wireframe, assembled view
▶ Interactive product tour / embedded video
100+ integrations · See all →
Security overview →
| ✓ | − | |
| ✓ | Limited | |
| ✓ | ✓ | |
| ✓ | − |
Assembly logic
The Interactive demo (3) is non-negotiable. It's the single highest-value block on this template. Evaluators want to touch the product, not read about it. A click-through tour or sandboxed environment beats every other proof asset combined for this page type.
Capabilities first, deep-dives second
Positions 4 and 5 work as a pair: the 6-tile grid gives the evaluator the full map at a glance, then the alternating Feature deep-dive zooms into the 3 most-asked-about capabilities with screenshots and outcome framing. Mapping the surface before diving in respects the evaluator's process.
Why integrations + security mid-page
Both blocks (6, 7) sit before the comparison and testimonials because they're objection-removal, not persuasion. The evaluator is mentally checking boxes: "does it work with X?", "is it SOC 2?". Get those out of the way before asking for the comparison decision.
The comparison block
Position 8 lets this page partly do the job of a vs-competitor page without committing to one. Use a generic "vs alternatives" framing rather than naming a specific competitor, the dedicated comparison templates handle named match-ups.
Template 06 · 9 components + editorial
Customer Story
An editorial format. More long-form than the other page types. The visitor wants a narrative they can mentally place themselves inside (same company size, same industry, same problem). Structured components anchor the story. Long-form text fills the gaps.
Page wireframe, assembled view
Assembly logic
The Story hero (2) front-loads the entire payoff: customer logo + headline result quote + three metrics. The visitor knows in 5 seconds whether this story is relevant to them. Everything after that is the case-building for visitors who self-identified at the top.
Why editorial blocks
Positions 3 and 5 are not in the component library. They're long-form prose with a 2-column layout: a sticky sidebar showing Company / Industry / Size / Tools used, and the main column carrying the Challenge → Solution narrative. Customer stories don't compress well into card grids, let them breathe as editorial.
Pull quote as section break
Position 4 does double duty: visual breathing room between the Challenge and Solution sections, and emotional reinforcement of the customer's voice mid-page. Pick the strongest quote you have, not necessarily the one that sells the product, but the one that sounds most human.
Related content as related stories
The Related content (7) on a Customer Story should be other stories, not blog posts. Same industry or same use case, mixed by company size. This is the single highest-converting internal link on a customer story page: visitors who read one story often read three.
Template 07 · 13 components
Free Tool / Lead Magnet
A page where the primary KPI is email capture, not demo booking. The lead magnet itself is the headline value. The product gets a soft, late-page mention as the natural next step. Not the first ask.
Page wireframe, assembled view
Assembly logic
The Form hero (2) is the page. The form is above the fold, the lead magnet is the headline, and the rest of the page exists only to nudge unconvinced visitors back up to the form. This is a conversion page wearing content-page clothes, don't bury the form.
Capabilities grid as "what's inside"
Position 3 reuses the Capabilities grid component but with non-product content: it lists what the lead magnet contains (the 8 templates, the 3 frameworks, the 5 case studies). Curiosity-anchored, not feature-anchored. The visitor's next thought should be "I want this".
The soft product bridge
Position 7's Final CTA is deliberately soft. The lead magnet form has already done the hard conversion; this CTA is about graduating engaged readers to a demo conversation later. Frame it as "ready to see how [Product] applies this in practice?", not as the primary ask.
Why the methodology block
How it works (4) at this position previews the framework or methodology behind the lead magnet. It does two jobs: signals the asset's depth before download, and starts establishing the brand's authority on the topic for organic search.
Template 08 · 12 components
vs Competitor
A bottom-of-funnel page for high-intent comparison searches. The visitor is comparing named products, not exploring categories. The page wins by being credibly honest. Including where the competitor is genuinely the better choice.
Page wireframe, assembled view
| ✓ | − | |
| ✓ | Limited | |
| ✓ | ✓ | |
| ✓ | − |
Why honesty up front
The "Where they win" block (3) at position 3 is counter-intuitive but correct. Acknowledging the competitor's genuine strengths early earns the right to be believed for everything that follows. Buyers verify these pages, sandbagging the comparison destroys the page's credibility on the first row they fact-check.
The two-column comparison
Position 4 covers the surface buyers expect: feature-by-feature parity. Don't pad it with rows where you trivially win. Pick rows that genuinely matter to the buying decision and that the visitor will recognise from their evaluation criteria. Group by category if the row count exceeds 8.
Switcher story as proof
Featured customer (6) on this template should be a switcher, someone who used the competitor and moved. Their testimonial naturally addresses the migration objections without you having to raise them. "We were on [Competitor] for 3 years before…" is the strongest possible opening for this audience.
Migration FAQ
The FAQ (9) on this template is migration-specific: data import, contract overlap, training time, parallel-run period. These are the practical objections that block decisions long after the comparison itself is settled. Answer them directly and the buyer is left with no reason not to start.
Template 09 · 14 components
Pricing
High-traffic, high-intent page. Visitors arrive with a single question: how much. The page's job is to answer cleanly, justify with comparative anchors, and remove every objection that blocks a self-serve start or a demo request.
Page wireframe, assembled view
| ✓ | ✓ | ✓ | |
| 3 | 25 | ∞ | |
| − | ✓ | ✓ | |
Assembly logic
Centered Outcome hero (2) with no image keeps the eye moving down to the prices. The hero copy frames pricing as fair and outcome-led ("Pricing built for teams of all sizes" is wrong; "Pay for what works, not what you might use" is right). Then tiers (3), then matrix (4), then ROI (5). Answer, detail, justification.
The decoy structure
The middle tier in position 3 is the desired conversion outcome. The Starter tier exists to make Growth look reasonable; the Scale tier exists to make Growth look like the value choice. This is intentional, three tiers convert better than two or five for self-serve B2B SaaS.
ROI before testimonials
Position 5 (ROI calculator) deliberately precedes the testimonials. Buyers in pricing-evaluation mode are already running mental ROI math; surface it for them with their own numbers, and the testimonials at position 6 then validate the math socially. Reverse the order and the calculator does less work.
Pricing-specific FAQ
The FAQ (9) on a pricing page handles the deal-blockers: "What happens if we exceed our seat count? Can we change plans? Is there a setup fee? What's your contract length?". These are the questions buyers search for at this stage. Answering them on-page keeps the visitor from bouncing to G2 or Reddit.
Template 10 · 7 components
Book a Demo
A pure conversion page. The visitor arrived from paid, sales outreach or a high-intent CTA. They're already considering a demo. The page exists to remove every reason not to fill in the form. Strip the nav, kill the footer, focus the page.
Page wireframe, assembled view
Assembly logic
The Stripped nav (1) and missing footer are doing real work. Every navigation choice on a demo page is an opt-out, a chance for the visitor to read the case studies, browse pricing, or check the team page instead of filling in the form. Strip them. The only forward path is the form.
What's deliberately missing
No Status quo, no Value trio, no Feature deep-dive, no How it works, no Integrations, no Related content. Visitors at this stage already know they want a demo, they don't need persuading that the product is for them, they need permission now. Educational content here is friction.
The proof stack
Positions 3, 4, and 5 are pure trust reinforcement: peer logos (bandwagon), third-party validation (authority transfer), and named-person testimonials (social proof). All three sit close to the form so the visitor can glance at them while deciding to submit. This is the only persuasion the page does.
Light universal closers
The FAQ (6) is heavily restricted: 3 questions max, all about the demo itself ("How long is the demo? Will it be tailored to my use case? Who'll be on the call?"). No Related content block, the page exists to convert, not to send the visitor elsewhere. Footer is replaced with a thin legal strip (Terms · Privacy · Contact).
Reference · 24 principles
Psychological principles
A reference list of the behavioural, cognitive, and B2B-specific principles applied throughout the components and templates above. Each one is a lever, useful in some contexts, neutral or harmful in others. The components show where to apply them; this section explains why they work.
Social proof
People look to the behaviour of similar others to decide what's correct, especially under uncertainty. In B2B, "similar" matters more than "many", five logos from a buyer's exact segment outperforms fifty from mixed industries. Customer counts, named logos, peer quotes, and review-platform ratings all activate this lever.
Authority
Credentialed third parties shortcut the buyer's evaluation work. Analyst placements (Gartner, Forrester), security certifications (SOC 2, ISO 27001), press citations, and named-expert quotes all transfer credibility from a trusted source onto the brand. Most powerful when the prospect already trusts the source.
Reciprocity
Giving something genuinely useful before asking for anything creates an obligation to return value. Free tools, ungated benchmarks, and templates work because they front-load value. The mistake is gating the useful thing, that's not reciprocity, that's a transaction.
Commitment & consistency
Small actions create momentum toward larger ones. A free tool use → email capture → demo book sequence works because each step is consistent with the last. Asking for the demo on cold traffic skips the commitment ladder.
Liking
People buy from people and brands they feel a kinship with. In B2B this shows up as "they get our world", using the buyer's vocabulary, naming their specific frustrations, showing screenshots of their kind of company. Generic copy tells the buyer this product wasn't built for them.
Scarcity
Genuine scarcity (limited cohort, ending pricing, finite onboarding slots) increases perceived value and urgency. In B2B SaaS this lever is mostly misused, fake countdown timers and false urgency damage trust. Use it only when the constraint is real.
Loss aversion
Kahneman & Tversky, Prospect Theory (1979)
Losses feel roughly twice as painful as equivalent gains feel good. "Stop losing 12 hours a week to manual reporting" outperforms "save 12 hours a week" because it frames the status quo as the losing position. Status-quo blocks on Solutions pages are loss-aversion plays.
Anchoring
The first number a buyer sees becomes the reference point for everything that follows. On pricing pages, leading with the higher tier makes mid-tier feel reasonable. In ROI calculators, the headline output anchors perceived value before the prospect ever sees the cost.
Decoy effect
Huber, Payne & Puto (1982); Ariely
Adding a third option that's clearly worse than one of the others shifts choice toward the "dominant" option. The classic three-tier pricing card with a highlighted middle tier uses this, the cheapest tier exists partly to make the middle look like the obvious choice.
IKEA effect
Norton, Mochon & Ariely (2012)
People value things more when they've put effort into them. Interactive product tours, ROI calculators, and free tools that produce a personalised output all create investment. By the time a prospect has built something with the product, the perceived switching cost of not buying has already gone up.
Hick's Law
Decision time grows logarithmically with the number of choices. Six pricing tiers force more cognitive load than three. A nav bar with 14 items is harder than one with 5. On conversion pages, every option is a chance for the prospect to choose "none of the above", keep choices tight.
F-pattern reading
Nielsen Norman Group eye-tracking
On dense web pages, users scan in an F-shape: top horizontal, then a shorter horizontal, then vertical down the left. Headlines, sub-headlines, and the first 2–3 words of bullets get read; everything else gets skimmed. Front-load meaning. Don't bury the value in paragraph three.
Specificity heuristic
Behavioural economics literature
Specific numbers feel more credible than round ones. "Reduces report build time by 73%" lands harder than "reduces it by ~75%" or "saves significant time". The buyer's brain treats specificity as a proxy for "they actually measured this".
Two-sided argument effect
Hovland, Lumsdaine & Sheffield (1949)
Acknowledging where you're weaker than a competitor increases trust in everything else you say. The "where they win" section of a comparison page is the highest-trust block on the page because it signals you're not just selling. Most brands are too scared to use this, which is exactly why it works.
Bandwagon effect
Asch conformity studies (1951)
"5,000+ teams use this" reframes the buying decision as joining a movement rather than taking a risk. Adoption-led copy works particularly well at the moment of action, just before a CTA, just before a form. It removes the question "am I being early on this?"
Jobs-to-be-done framing
Christensen, The Innovator's Solution (2003)
Buyers don't buy products, they hire them to make progress on a job. Solutions/Use Case pages should be structured around the job (the outcome the buyer is trying to achieve), not around the product's feature list. Job-led pages convert better than feature-led ones because they match how the buyer is actually thinking.
Champion enablement
Adamson & Dixon, The Challenger Customer (2015)
In B2B, the person on your site rarely has unilateral buying power. They need to sell internally to procurement, IT, security, and finance. Role-based pages, ROI calculators, security one-pagers, and "share this with your team" toolkits are all champion enablement, you're arming an internal advocate.
Internal selling enablement
Gartner research shows the average B2B buying group is 6–10 stakeholders. The buyer spends more time selling internally than they do talking to vendors. Pages that work for the user but ignore the buying committee leave the deal stuck in approval. Build assets the champion can forward.
Uncertainty reduction
Unknown duration, unknown next steps, and unknown commitment all create friction at conversion points. "30-minute call. We'll cover X, Y, Z. No obligation." removes three layers of cognitive load before the prospect has to decide. Demo pages and pricing pages benefit most.
Distraction reduction
On conversion pages (demo booking, signup, checkout), every nav link is an exit. Stripping the header to just a logo, removing the footer, and killing related-page links typically lifts demo-page conversion by 20–40%. The prospect is ready, don't give them a graceful way to leave.
Field reduction
HubSpot, Marketo, Unbounce form studies
Every form field reduces submission rate. Going from 11 fields to 4 commonly doubles conversion. The instinct to enrich the lead at form-fill is in tension with the goal of getting the lead in the first place. Capture the minimum; enrich asynchronously with Clearbit-type tools.
Authority transfer
Source-credibility research; Cialdini (1984)
A G2 badge, a Gartner mention, or a SOC 2 logo transfers a fraction of the source's credibility onto the brand. The transfer is strongest when the prospect already knows and trusts the source. Stacking unknown badges has diminishing returns, three credible signals beat ten weak ones.
Risk reduction
B2B buyers are loss-averse on behalf of their company and themselves. "Nobody got fired for buying IBM" is the canonical example. Trust badges, money-back guarantees, free trials, named customer references, and clear cancellation terms all reduce the perceived downside of saying yes.
Async friction removal
CRO field data; Chili Piper / Calendly
Any delay between "I want to talk" and "we're talking" leaks demand. Direct calendar booking converts 2–3× better than "we'll get back to you" forms because it removes the asynchronous wait. The faster the loop closes, the higher the close rate.
How to use these by funnel stage
No principle is universally good. Loss aversion overused becomes scaremongering. Scarcity overused becomes manipulative. The skill is matching the lever to the funnel stage and how warm the audience is.
Top of funnel, reciprocity, liking, JTBD framing, social proof. Earn attention before asking for anything.
Mid funnel, authority, two-sided argument, anchoring, IKEA effect, champion enablement. Build credibility and equip the buyer to sell internally.
Bottom of funnel, distraction reduction, field reduction, uncertainty reduction, async friction removal, risk reduction. Strip out everything that isn't conversion.
Test one lever at a time. If a page improves after three changes, you don't know which one moved the number.