15 SaaS Landing Page Copywriting Frameworks That Convert Cold Traffic

Framework: PAS, coined and codified by Dan Kennedy in The Ultimate Sales Letter (1993). One of the most reproduced direct-response structures in existence.

Problem it solves: Hero copy that opens with the product — "We built a better CRM" — instead of opening with the reader's pain. Features-first copy assumes the visitor already understands why they need the category. Cold traffic doesn't.

SaaS example applied: Intercom's early homepage didn't open with "customer messaging platform." It opened with the problem: customers were arriving on websites and leaving without talking to anyone. The agitation: every one of those visitors had a question. The solution: Intercom puts a conversation interface where the silence was. The product was the third thing they mentioned, not the first.

How to use it: Write the single most painful problem your user admits to having — in their exact words, not your product vocabulary. Then agitate it: add one sentence showing the consequence of the problem going unsolved. Then introduce your product as the specific exit from that consequence. PAS is the safest default for a hero section rewrite when you don't know where to start.

Framework: AIDA, attributed to advertising theorist Elias St. Elmo Lewis (1898). The oldest named framework on this list and still the most useful diagnostic tool for auditing an existing page.

Problem it solves: Pages that open with a great headline and then immediately ask for a signup. The visitor got Attention and then jumped to Action, skipping the two stages that do the heavy lifting of conversion: Interest (why does this matter for my specific situation?) and Desire (I want this, not just understand it).

SaaS example applied: Stripe's homepage executes AIDA cleanly. Attention: "Financial infrastructure for the internet" — a bold positioning claim. Interest: Stripe then shows what that means concretely — payments, billing, fraud prevention, tax — with logos and specific use cases. Desire: social proof from Shopify, Amazon, and Google shifts the visitor from "I understand what this is" to "I want to be in this company." Action: "Start now" appears after the desire has been built, not before.

How to use it: Use AIDA as a diagnostic, not a template. Open your current landing page and label every section: which stage does it serve? Most SaaS pages have a strong Attention section, a weak or missing Interest section, almost no Desire work, and a CTA that appears before the visitor is ready. Identify which stage you're skipping and write to fill that gap.

Framework: The Villain Frame — original. Every hero needs an antagonist. The villain in SaaS copy isn't a competitor; it's a painful situation, a broken tool, or a mode of working that your ideal customer has already decided they're done with.

Problem it solves: Copy that describes what a product does without explaining what it's replacing feels abstract. "A better way to manage projects" is meaningless without a reference point for "better." The villain creates that reference point and forces a comparison the visitor can feel.

SaaS example applied: Linear's messaging doesn't attack Jira by name — it attacks the feeling: "Built for high-performance teams who find existing tools slow and cumbersome." The villain is bureaucratic project management, sluggish interfaces, ticket-ceremony. Linear's speed and minimal UI are positioned not in a vacuum but in explicit contrast to everything the reader has learned to tolerate. The copy works because the villain is a shared enemy.

How to use it: Identify the tool, habit, or system your best customers were escaping when they found you. Name it by feeling rather than by brand. "The spreadsheet that's grown unmanageable" is a villain. "The 40-tab nightmare" is a villain. Your product appears not as a category entrant but as a rescue. The villain frame also pre-qualifies: readers who don't recognize the villain aren't your customer.

Framework: BAB (Before-After-Bridge), popularized in direct response copywriting. A structural framework for establishing transformation rather than features.

Problem it solves: Hero sections that open mid-story — they describe the product without establishing the before state that makes the transformation meaningful. A transformation without a before state is just a claim. A transformation with a vivid before state is a story the visitor can project themselves into.

SaaS example applied: Loom's hero copy at various points has used the BAB logic precisely: Before — you schedule a 30-minute call to explain something that could be shown in 2 minutes. After — you record a quick video and the other person watches it when they're ready. Bridge — Loom is the mechanism that closes that gap. The copy doesn't start with "screen recording software." It starts with the painful before state that every knowledge worker recognizes.

How to use it: Write three sentences. One for the before state (make it specific and uncomfortable). One for the after state (make it concrete and desirable — not vague like "save time" but "meetings cut in half"). One that names your product as the bridge. This three-sentence structure becomes the copy scaffold for your hero section. Everything else — features, proof, CTAs — expands on the bridge.

Framework: The Velocity Frame — original. Built for product-led growth products where time-to-value is the actual differentiator, not the feature set. The velocity frame makes speed the headline.

Problem it solves: PLG products often bury their biggest selling point — the fact that a user can go from signup to value in minutes — under feature descriptions and use-case lists. Cold traffic evaluating a PLG product needs to understand the investment required. The shorter the time-to-value, the lower the perceived risk of trying. Copy that doesn't communicate velocity is leaving conversion on the table.

SaaS example applied: Calendly's core copy — "Share your Calendly link. Watch your calendar fill." — is a velocity frame. It compresses the entire workflow into two actions and implies that the gap between those two actions is trivially small. There's no "powerful scheduling platform" or "eliminate the back-and-forth." The copy communicates that the time between deciding to use it and getting value from it is measured in seconds.

How to use it: Calculate the time from signup to your product's first meaningful output for a motivated new user. If it's under 10 minutes, that number belongs in your headline or subheadline. Rewrite your hero copy around the verb sequence: what does the user do first, what happens next, what's the outcome? Compress the sequence to its shortest legible form. The words "in minutes" or "in 2 steps" in a headline are measurably conversion-positive for PLG products.

Framework: The Job Story Frame, derived from the Jobs to Be Done theory developed by Clayton Christensen and operationalized for copy by Bob Moesta and Alan Klement. The Job Story format: "When [situation], I want to [motivation], so I can [outcome]."

Problem it solves: Copy that describes what a product does without anchoring it to the specific situation that triggers the need. Features without a triggering situation feel like a menu without hunger. The Job Story grounds the copy in the moment where your customer realized they needed something different.

SaaS example applied: Notion's positioning lives in Job Story logic without always stating it explicitly: when I'm managing a product roadmap, writing docs, and tracking a project in three different tools and constantly losing context, I want everything in one connected workspace, so I can stop tool-switching and actually think. The reason Notion resonates is that it's written about the trigger (fragmented tools) and the outcome (coherent thinking), not the features (databases, pages, blocks).

How to use it: Write a Job Story for your single most common customer type. "When [the specific moment of friction they experience], I want to [the change they're seeking], so I can [the outcome that matters to them]." Don't publish the Job Story — use it as the spec for your copy. Your headline comes from the situation and the outcome. Your feature descriptions come from the motivation. Your testimonial curation comes from finding quotes that match the job.

Framework: The Specificity Stack — original. A rewrite discipline, not a structural framework. The rule: every unquantified claim on the page gets replaced with a specific number, named outcome, or verifiable fact. Stacking specific claims builds compound trust.

Problem it solves: SaaS landing pages saturated with words like "powerful," "flexible," "seamless," "easy," "best-in-class," and "robust." These words have been used so often, by so many products, that they register as noise. A visitor who reads "the most powerful project management tool" feels nothing. A visitor who reads "closes 37% more support tickets without adding headcount" feels something.

SaaS example applied: Superhuman's landing page copy is a masterclass in the Specificity Stack. They don't say "email that's fast." They say "the fastest email experience ever made" — and then they immediately prove it: average users save 4 hours per week. The superlative is earned because the specific number follows it. The number creates a mental simulation: what would I do with 4 extra hours? That simulation is where conversion happens.

How to use it: Open your current landing page. Highlight every adjective and comparative claim in yellow. For each one, ask: what's the specific number, named customer, concrete scenario, or verifiable fact behind this claim? If there isn't one, either find it or cut the claim. A page with 5 specific, provable claims outperforms a page with 20 vague ones. The goal isn't to remove all qualitative language — it's to earn every qualitative claim with a specific proof point nearby.

Framework: The Hook-Proof-Pivot — original. A micro-framework specifically for the CTA section of a PLG landing page, where the visitor has arrived at the moment of decision and needs one final piece of leverage to convert.

Problem it solves: PLG pages that do the work of converting throughout the page and then close with a naked button — "Get started free" — that asks for commitment without giving anything in return. By the time a visitor reaches the CTA section, they've read the pitch. What they need at the moment of decision isn't more features. They need a small, high-credibility proof point that confirms others have already made this decision and it worked out.

SaaS example applied: Figma's CTA section structures itself as Hook-Proof-Pivot: Hook — "Design, prototype, and gather feedback all in one place" (this is the value restatement at the moment of decision). Proof — "Used by over 4 million designers" appears immediately adjacent to the button. Pivot — "Get started free." The Proof element (4 million users) reduces the felt risk of clicking. It's a social signal inserted at maximum anxiety.

How to use it: Immediately above your primary CTA button, add a single sentence of proof. This might be a user count, a named company ("Trusted by Shopify, Stripe, and Twilio"), an outcome stat, or a one-line testimonial with attribution. Don't add three proof elements — one is enough. The proof should be your single strongest credential. Then the CTA follows. The structural sequence is: restate the core value → deliver one proof point → make the ask.

Framework: The Anti-Pitch — original. A PLG-specific counterintuitive opener that converts by explicitly pre-qualifying the reader — and by extension, creating strong affinity with the readers who remain.

Problem it solves: PLG signup pages written to appeal to everyone that, by attempting broad appeal, feel credible to no one. "Project management software for teams" describes 200 products. When copy refuses to exclude anyone, it implicitly includes everyone, and the reader never feels specifically addressed.

SaaS example applied: Basecamp has deployed the Anti-Pitch at various points in their positioning: openly stating that Basecamp is not for everyone, that it's specifically not built for teams who want a customizable enterprise platform, and that this simplicity is a feature rather than a limitation. The effect: teams who are tired of configuration-heavy tools immediately feel seen. The exclusion of one audience is the inclusion of another. The anti-pitch is also honest — which builds trust at the top of the page before any claim has been made.

How to use it: Write a version of your hero section that opens with one sentence naming who your product is not for. Keep it specific — "not for enterprise teams with dedicated IT procurement" is more useful than "not for everyone." The visitors who don't fit should self-select out quickly; this is good for your trial conversion rate. The visitors who see themselves in the exclusion — who recognize themselves as the opposite of who you're excluding — will feel chosen. That feeling is worth more than the generic "powerful and flexible" opener it replaces.

Framework: The Segment Gate — original. An opening structure that names the specific user type in the first sentence, forcing immediate self-identification.

Problem it solves: Generic copy that speaks to a vague "you" when the product has a clearly defined user type — or multiple user types. If the visitor can't place themselves in the copy within the first few seconds, they leave. The Segment Gate names them immediately, at the top of the page, before they've had a chance to disengage.

SaaS example applied: Webflow's hero copy — "For designers who don't want to code. For developers who don't want to compromise." — is a Segment Gate executing on two audiences simultaneously. Each audience reads one sentence and recognizes themselves. The copy doesn't try to describe what Webflow does before naming who it's for. Segment first, product second. This sequence matches the mental model of someone landing on an unfamiliar page: their first question is "is this for me?" not "what does this do?"

How to use it: Write your hero headline or subheadline as a "For [specific role or situation]" statement. If you have multiple user types, use the "For X. For Y." construction — but cap it at two. More than two segments and the reader stops self-identifying and starts reading a list. The most powerful version names the job title, company stage, or specific frustration: "For growth engineers tired of waiting on data teams" converts harder than "for modern data teams." Specificity of audience signals specificity of solution.

Framework: The Proof Sandwich — original. A proof placement strategy, not a writing framework. The principle: social proof inserted immediately after a specific claim is more persuasive than social proof aggregated in a dedicated section.

Problem it solves: Pages that make a series of value claims in the hero and features sections, then group all testimonials into a single "What our customers say" section near the bottom. The testimonials are divorced from the claims they validate. A reader who sees "40% faster onboarding" in the features section has no immediate proof. By the time they reach the testimonials section, they've already formed their skepticism.

SaaS example applied: HubSpot's product pages embed proof throughout. After a specific claim — "See your entire pipeline at a glance" — they place a testimonial that references pipeline visibility specifically. After a claim about reducing manual data entry, a quote from a sales ops manager quantifying the time saved. The proof doesn't appear in a separate section; it appears in the sentence after the claim it validates. The structural pattern: Claim → Proof → Next Claim → Proof.

How to use it: Map your landing page claims to your testimonial library. For every major value claim, find the testimonial or case study quote that directly validates it. Place that proof immediately below the claim — not in a separate section, not above the fold, but directly adjacent to the claim it supports. If you have no matching testimonial for a specific claim, that's a signal to either collect it or reconsider whether the claim belongs on the page.

Framework: The Pricing Anchor Frame — original. A pricing-page-specific technique for reframing the presented price against a reference point that makes it feel proportionate. Price without context is always "expensive." Price against the right anchor is often "obvious."

Problem it solves: Pricing pages that display a number — "$99/month" — with no reference point for evaluating it. The visitor's brain immediately searches for a comparison: is this cheap or expensive? Without an anchor from you, they'll compare it to zero (free alternatives) or to the most superficially similar thing they've priced recently. Both comparisons make your price look worse than it is.

SaaS example applied: Zapier's pricing page has used the anchor frame to position their paid plans against the alternative: building and maintaining custom integrations. The anchor isn't a competitor price — it's the cost of not using Zapier. "Replace the equivalent of a part-time developer's workflow automation work" frames $99/month differently than "$99/month" alone. The price hasn't changed. The reference point has, and that's what converts.

How to use it: Before your pricing table, add a single sentence that establishes the comparison the visitor should be making. Three options: (1) Cost of the status quo — what does the problem cost per month in time or money? (2) Cost of alternatives — what would the stack that does what you do cost, added up? (3) Value produced — what does an average customer gain per month from using you? Choose the anchor that makes your price look most proportionate to value delivered. Place it above or adjacent to the pricing table, before the visitor sees the number.

Framework: The Reverse Demo — original. A PLG-specific visual strategy where the product's output is shown before the product is explained. The visitor sees what "done" looks like before they read a single word of copy.

Problem it solves: PLG products where the value is visual and experiential but the landing page tries to describe it in words. Abstract descriptions of product capabilities create a cognitive load that slows signup velocity. Cold traffic can't simulate an unfamiliar experience from a description. They can react to a screenshot of a filled-in database, an annotated design file, or a completed workflow — immediately and viscerally.

SaaS example applied: Airtable's homepage doesn't explain what a relational, no-code database is — a description that would confuse most non-technical visitors. Instead, they lead with the product: a fully populated Airtable base with real-looking data, custom views, and colored fields. The visitor understands the product in under 3 seconds through the image, before the copy has done any work. The headline and subheadline function as captions for what's shown, not as standalone arguments.

How to use it: Choose the single screenshot or GIF that represents maximum value — not the empty onboarding state, not the settings panel, not a feature you're proud of internally. Show the product at the moment of highest utility: the dashboard with live data, the document fully annotated, the campaign fully built. Lead with that image above the fold. Write your headline and subheadline as if they're explaining what the visitor is looking at. This inversion — show first, explain second — reduces the cognitive load of evaluating an unfamiliar product.

Framework: The Cost-of-Inaction Frame — original. A PLG conversion technique that quantifies what the visitor is already losing by not using the product, rather than focusing on what they'd gain.

Problem it solves: PLG pages that describe value in terms of future gain — "save 4 hours a week," "reduce churn by 20%" — without establishing that the problem is already costing them. Cold traffic doesn't feel urgency from future gains. They feel urgency from current losses. The Cost-of-Inaction Frame makes the cost of doing nothing concrete and personal.

SaaS example applied: Monday.com has deployed this logic in various forms: "Teams without a shared work OS spend an average of 3 hours per week chasing status updates." The comparison isn't to a competing product. It's to the status quo. The visitor who manages teams immediately performs a mental calculation: 3 hours × my team size × 52 weeks. That calculation is the emotional engine of the conversion. Monday.com doesn't have to argue they're better than the alternative — they just have to make the alternative feel expensive.

How to use it: Identify the specific, quantifiable cost your best customers were paying before they found you. Frame it per week or per month — annual numbers feel abstract; weekly numbers feel personal. Put this cost in your hero subheadline or in the sentence immediately above your primary CTA: "You're already spending [X] on this problem." That reframe shifts the risk calculus from "should I risk trying this product?" to "can I afford to keep doing this the old way?" For PLG, this is the highest-leverage copy change you can make.

Framework: The Contrast CTA — original. A CTA architecture strategy that replaces the single-button close with two options that make the primary choice feel clearly superior by contrast with the secondary.

Problem it solves: Single-button CTAs that ask the visitor to choose between "yes" and "back button." The visitor's alternative isn't articulated, so they're choosing between your product and an undefined option. Leaving the alternative undefined leaves the contrast undefined — and contrast is what makes a choice feel easy.

SaaS example applied: Two distinct executions worth studying: Slack's CTA section — "Try for free / Talk to sales" — uses the secondary option (sales) to reframe the primary (self-serve trial) as the lower-friction path for the reader who's evaluating independently. ClickUp's two-button approach — "Get started free / Book a demo" — lets the visitor self-select their readiness level, which means a higher total conversion rate across both commitment levels. The secondary CTA doesn't dilute the primary; it captures the segment who wasn't going to click the primary anyway.

How to use it: Add a second CTA option to your primary CTA section. The secondary should have lower commitment: "See a 2-minute demo," "Watch how it works," or "Book a walkthrough." Write the secondary CTA label to make the primary feel decisive by comparison — if your primary is "Start free trial," the secondary should emphasize that starting requires something: time, a decision, willingness. The contrast makes the primary feel like the easy option. Do not use two equal-weight CTAs that create genuine decision paralysis — one should clearly be the recommended path.