--- title: "FAQ Section Swipe File" summary: "An FAQ section is an objection-handler in disguise. Every question on the list should match a real buyer hesitation. Questions that pretend to be educational (but are actually self-praise) burn trust; questions that name real objections earn the click on the CTA below them." canonical: https://unlocksaas.com/swipe-file/faq-section updated: 2026-05-21 publisher: "Unlock SaaS" author: "Maryan" license: All rights reserved. Quotation with attribution permitted. --- # FAQ Section Swipe File > An FAQ section is an objection-handler in disguise. Every question on the list should match a real buyer hesitation. Questions that pretend to be educational (but are actually self-praise) burn trust; questions that name real objections earn the click on the CTA below them. ## Brunson lens Story ## When this is the right thing to rewrite When scroll depth reaches the offer block but the CTA doesn't fire. When customer support inbox has the same 3-5 pre-purchase questions weekly. When the buyer needs one more permission to act. ## When the FAQ section is NOT the constraint When traffic doesn't reach the FAQ block. Move the questions higher (inline in the offer block) rather than relying on the visitor to scroll. ## Pattern library ### 1. Price Objection **Formula.** 'Is too much for ?' + honest answer. **Example.** 'Is $49/month too much for a diagnostic tool? If you're pre-revenue, probably. The $1 Starter exists for that reason.' **Why it works.** Honest answer with a redirect to a cheaper tier earns more trust than defending the price. ### 2. Cohort Match **Formula.** 'Is this for ?' + qualifier. **Example.** 'Is this for pre-launch founders? No. The diagnostic needs a live page to read. Come back once you've shipped.' **Why it works.** Disqualifying the wrong cohort qualifies the right cohort. Counter-intuitive trust lift. ### 3. Time-To-Value **Formula.** 'How long until ?' + specific time range. **Example.** 'How long until I see my first paying customer? 30-90 days for diligent operators. 6 months for those who skip the rewrite step.' **Why it works.** Specific time range + named operator condition. Earns belief because it's testable. ### 4. Comparable Product **Formula.** 'How is this different from ?' + structural answer. **Example.** 'How is this different from a course? A course teaches the framework. This applies the framework to your live page.' **Why it works.** Names the comparison the buyer is privately running. Honest structural difference, not 'we're better'. ### 5. Refund Mechanics **Formula.** 'What's the refund process?' + step-by-step answer. **Example.** 'Reply to any email or message support@unlocksaas.com within 60 days. Refund processed within 24 hours, no questions asked.' **Why it works.** Specific mechanics earn more belief than 'yes, we refund'. Names the channel and the SLA. ### 6. Founder Question **Formula.** 'Who built this?' + 2-line founder + link to /about. **Example.** 'Who built this? Maryan, indie SaaS founder, 3 launches, 1 working. Full story at /about.' **Why it works.** Personalized FAQ entry. Earns belief by surfacing the founder where buyers are already evaluating trust. ### 7. Privacy Question **Formula.** 'What do you do with my data?' + plain-English answer. **Example.** 'What do you do with the URL I submit? Run it through the diagnostic, then delete after 30 days. We don't sell or share inputs.' **Why it works.** Plain-English answer. Avoid legalese; buyers reading the FAQ are reading for honesty, not for terms. ### 8. Integration Question **Formula.** 'Does it work with ?' + honest yes/no/partial. **Example.** 'Does it work with my Webflow site? Yes. Framer? Yes. Custom Next.js? Yes. Webflow CMS dynamic pages? Partial.' **Why it works.** Honest 'partial' answers earn more trust than blanket 'yes'. Buyers who get a 'partial' here often buy anyway. ### 9. Cancel Question **Formula.** 'How do I cancel?' + plain-English steps. **Example.** 'How do I cancel? Go to /dashboard → billing → cancel subscription. One click. No phone call required.' **Why it works.** Surfacing the cancel mechanics openly is a trust signal. Hidden cancel flows are remembered worse than expensive products. ### 10. Success Story Cross-Link **Formula.** 'Show me a real example.' + 'Yes, see /stories/.' **Example.** 'Show me a founder who actually got results. Yes, see /stories/[real-founder-slug].' **Why it works.** Drop-in cross-link. Visitor who clicks self-qualifies into a deeper trust path. ### 11. Public Roadmap **Formula.** 'What's on the roadmap?' + link to /roadmap or /press. **Example.** 'What are you building next? See the public roadmap at /press/roadmap.' **Why it works.** Forward-looking trust. Pairs especially well with active, dated roadmap updates. ### 12. Honest Limitation **Formula.** 'What doesn't this do?' + 2-3 honest gaps. **Example.** 'What doesn't this do? Not a copywriter. Not an ad strategist. Not a designer. It diagnoses the page and labels what's broken.' **Why it works.** Honest limitations earn the most trust of any FAQ pattern in this list. Most founders skip this entry. You shouldn't. ## Common implementation mistakes - FAQs that are praise in question form. 'Why is your product so good?' is a bullshit detector for buyers. - FAQs ordered by writer convenience instead of buyer-objection intensity. Lead with the price objection, end with the cohort filter. - Three FAQs total. Most buyers have 5-9 real objections; 3 makes the page look thin. - No FAQ at all on a SaaS pricing page. The objections happen whether you address them or not – you just don't get to set the framing. - FAQ entries that are 200-word essays. Buyers scan FAQs; 2-3 sentence answers convert better than walls. ## Real examples from indie SaaS teardowns ### [Plausible Analytics](https://unlocksaas.com/funnel-teardown/plausible) – Operational transparency as proof _Plausible sells transparency as the product. Open revenue dashboards do the conversion work._ **Why this is a reference for FAQ section.** Operational transparency carries into FAQs – every common objection is answered with verifiable specifics. **From the story lens analysis.** The story is told through public artifacts: open source code on GitHub, a public revenue page, named founders writing blog posts about real failures and pivots. The reader does not need to take a marketing claim on faith because the receipts are linked. ### [Tally](https://unlocksaas.com/funnel-teardown/tally) – Show, do not tell _Tally turns the freemium ceiling into the headline. The funnel is the price line._ **Why this is a reference for FAQ section.** FAQs handle the 'why no long sales page' objection head-on. Disqualifies the wrong cohort honestly. **From the story lens analysis.** Story is told through live form examples and the in-product trial flow, not through a written narrative. The reader is funnelled into building a form within two clicks of the homepage. The proof is the build experience itself, which removes any need to claim ease of use in copy. ### [Cal.com](https://unlocksaas.com/funnel-teardown/cal-com) – Developer-credibility through artifacts _Cal.com sells the open-source alternative to Calendly. The repo IS the trust signal._ **Why this is a reference for FAQ section.** Self-host FAQ doubles as a trust signal – the answer alone makes the buyer feel safer. **From the story lens analysis.** The repo on GitHub is the story. Star count, contributor count, and the integration directory are the proof that this is real software, not a marketing claim. The reader who values code-as-truth lands fast. ### [Senja](https://unlocksaas.com/funnel-teardown/senja) – Demo-by-existence _Senja sells a problem most SaaS know they have but never name. The funnel uses its own product as the demo._ **Why this is a reference for FAQ section.** FAQs re-state the universal pain in the user's own words, so the cohort match compounds through the page. **From the story lens analysis.** Testimonials displayed on the Senja marketing site are themselves collected via Senja. The story is told by the live walls and embed widgets the reader is currently looking at. The product is the marketing. ## Related terms - [Weak Belief](https://unlocksaas.com/glossary/weak-belief) – One of three diagnostic labels: the person and the offer are fine but the page does not make the reader believe it will work for them. ## FAQ ### How many FAQs should I have on a landing page? 5-9 is the working range. Below 5 looks unprepared; above 12 reads as defensive. Order them by descending objection intensity (price, cohort fit, time-to-value, refund) rather than by topic. ### Should FAQs use schema markup? Yes, FAQPage JSON-LD on every FAQ block. It earns the AI-Overview citation surface and the People Also Ask serp module. Without it, your FAQs are just text. ### Should I show all FAQs expanded or collapsed by default? Top 2-3 expanded (the objections everyone has), the rest collapsed. Full-collapse hides too much; full-expand creates a wall and visitors don't scan it. --- Canonical URL: https://unlocksaas.com/swipe-file/faq-section Publisher: Unlock SaaS (https://unlocksaas.com) Contact: maryan@unlocksaas.com