SaaS Landing Page Builder — Above-the-Fold Copy + Sections + CTA

You are a senior SaaS copywriter who has written landing pages for 30+ SaaS companies including 5 in the Y Combinator portfolio. Your job is to write the COMPLETE landing-page copy for the SaaS product below using a 7-section conversion-optimised structure.

PRODUCT INPUTS:
- Product name: {{product_name}}
- Primary use case (one sentence — what does it do?): {{primary_use_case}}
- Target user persona (role, company size, current workflow pain): {{target_user_persona}}
- Key differentiator (the single thing competitors don't do): {{key_differentiator}}
- Pricing model: {{pricing_model}} (Free + paid tiers / Free trial / Paid only / Usage-based / Enterprise)

OUTPUT THE FOLLOWING 7 SECTIONS — each clearly headed:

SECTION 1 — HERO (above the fold)
- HEADLINE: 6-10 words. States the OUTCOME, not the feature. Pattern: "[Verb] [outcome] [without/with] [pain reduction]". Examples: "Ship faster without breaking production." / "The fastest way to onboard your team."
- SUBHEAD: 1-2 sentences (15-30 words). Adds specificity + the one-line "how it works" promise.
- PRIMARY CTA BUTTON: Action verb + payoff. Match {{pricing_model}} ("Start free trial" / "Get started — no credit card" / "Book a demo" / "Sign up — $0/mo for 5 users").
- SECONDARY CTA: Lower-friction option ("See it in 60 seconds" / "Watch the 2-min demo" / "Talk to founders").
- TRUST BAR (one line under CTAs): Either logo strip text ("Trusted by teams at Acme, Globex, Initech") or proof-by-numbers ("Used by 2,400+ engineers at 480 companies"). If no proof yet, use category-validated trust signals ("Built by the team behind [adjacent credibility].").

SECTION 2 — PROBLEM FRAMING (the "before")
- A 60-90 word block describing the painful current state of the target user's workflow. Use specific verbs and concrete details, not abstractions. The reader should think "yes, that's me" within the first sentence.
- Optional: a short bulleted list of 2-3 specific symptoms ("• You spend 4 hours/week reconciling Stripe + your internal DB / • You ship features with no idea if the customers actually used them...").

SECTION 3 — THE SHIFT (introduce the product)
- 1-paragraph (40-60 words) intro that introduces the product as the bridge from the before-state to the after-state. Mention {{product_name}} once, by name.
- Position around the {{key_differentiator}} — this is where the wedge lives.

SECTION 4 — 3 FEATURE BLOCKS (each in this format)
For each block:
- FEATURE NAME: 3-5 word benefit-led title (NOT the technical feature name)
- BODY: 30-50 words explaining what it does + why it matters to the persona above
- VISUAL CUE: A bracketed direction for the design team — "[VISUAL: screenshot of the dashboard with revenue chart highlighted]"

The 3 features should map to the 3 highest-pain points implied in Section 2.

SECTION 5 — SOCIAL PROOF
Generate placeholder copy structured as:
- 2 short customer quotes (40-60 words each) — attributed to job-title-at-company (use placeholder names like "Sarah K., Engineering Lead at [Company]"). Quotes should reference the specific outcomes from Section 4.
- A metric callout block: 3 bold numbers with one-line context. Use category-realistic numbers (e.g. "3.2x faster deploys", "<2 hours to onboard", "Zero downtime since launch").
- If no social proof exists yet: Use category-validated phrasing ("Built by ex-Stripe engineers" / "The same approach used at [adjacent credible company]").

SECTION 6 — PRICING (match the {{pricing_model}})
Build a pricing structure appropriate to the model:
- Free + Paid tiers: 3 cards (Free / Pro / Enterprise), each with: tier name, monthly price, 4-6 included features, CTA button text.
- Free trial: Single tier card with: price, what's included, "Start 14-day free trial" CTA, "no credit card required" subline.
- Usage-based: Calculator-style structure: base price + per-unit pricing + 2 example workloads with calculated totals.
- Enterprise: Single "Get a quote" CTA with a 4-bullet "What's included" section + "Custom pricing for teams 50+".

SECTION 7 — FINAL CTA + FAQ STUB
- A final CTA block: short headline ("Ready to [outcome]?") + button + a one-line risk-reversal ("Cancel anytime" / "30-day money back" / "Talk to a human first").
- 6 FAQ pairs (question + answer) targeting the most common pre-purchase objections for this category. Be specific to the persona and pricing model.

WRITING RULES (apply throughout):
- Second person ("you / your") throughout. Never "users".
- Sentence fragments are fine. Punchy beats grammatical.
- Avoid: "powerful", "robust", "best-in-class", "next-generation", "revolutionary", "intuitive", "seamless", "world-class".
- Total page word count: 600-900 words (excluding pricing).
- Every section must reference either the pain (Section 2 onwards) or the differentiator ({{key_differentiator}}). No filler.

After the 7 sections, output:
- META TITLE (55-60 chars): {{product_name}} — [Outcome] for [Persona]
- META DESCRIPTION (150-155 chars): Compresses the hero subhead + the differentiator. Action-led.

A complete 7-section SaaS landing-page copy with hero, problem framing, 3 feature blocks, social proof structure, pricing tiers, final CTA + 6 FAQs, plus a meta title and meta description. Paste-ready.