Swipe file
Social Proof Bar Swipe File
A social proof bar lives directly under the hero block and answers a single question: 'who else trusts this?' The visitor scans it in under 1.5 seconds. Patterns that earn belief in that window are concrete, cohort-matched, and visually quiet.
Verified · editorial policy
TL;DR
As of , the short version is: A social proof bar lives directly under the hero block and answers a single question: 'who else trusts this?' The visitor scans it in under 1.5 seconds. Patterns that earn belief in that window are concrete, cohort-matched, and visually quiet.
Social Proof Bar Swipe File TL;DR
- Element
- Social proof bars
- TL;DR
- A social proof bar lives directly under the hero block and answers a single question: 'who else trusts this?' The visitor scans it in under 1.5 seconds. Patterns that earn belief in that window are concrete, cohort-matched, and visually quiet.
- When to use
- When time-on-page is over 20 seconds but the visitor doesn't scroll to the offer block. When the headline qualifies but trust is the next bottleneck.
- When NOT to use
- When you don't actually have the proof. Faking a logo strip with companies you don't have a relationship with is a one-strike trust kill.
- Brunson lens
- Story
- Patterns
- 12 named patterns with formula + example + structural notes
- Last verified
- May 21, 2026
When to use
Rewrite this when
When time-on-page is over 20 seconds but the visitor doesn't scroll to the offer block. When the headline qualifies but trust is the next bottleneck.
Do NOT touch when
When you don't actually have the proof. Faking a logo strip with companies you don't have a relationship with is a one-strike trust kill.
12 named patterns
Pattern 1
Real Logo Strip
Formula
'<Customer logo 1> <logo 2> <logo 3> <logo 4> <logo 5>'
Example
Stripe logo, Linear logo, Cal.com logo, Plausible logo, Notion logo, all monochrome
Why it works
Monochrome strip. Real customers only. 5-7 logos at most; more becomes noise.
Pattern 2
Counter Strip
Formula
'<Number> <unit> across <category>'
Example
'1,000+ indie SaaS landing pages diagnosed'
Why it works
One specific number, one specific category. Avoid 'thousands of customers' – be exact.
Pattern 3
Founder Strip
Formula
'Used by founders at <recognizable indie SaaS 1>, <2>, <3>.'
Example
'Used by founders at [recognizable indie SaaS names]'
Why it works
Names beat logos when the audience knows the founder, not the company. Common with Twitter-native audiences.
Pattern 4
Rating Strip
Formula
'<Star rating> on <verifiable platform>, <N> reviews'
Example
'★ 4.9 on G2, 47 reviews'
Why it works
Verifiable rating + verifiable platform. Generic '5-star reviews' without a platform is just text.
Pattern 5
Endorser Strip
Formula
'As recommended by <named person>, <role>'
Example
'As recommended by [Recognizable founder name], author of [book/newsletter]'
Why it works
Single named endorser beats a wall of testimonials when the endorser matches the audience's reference set.
Pattern 6
Counter + Recency
Formula
'<Number> <unit> in the last <time period>'
Example
'47 diagnoses run in the last 7 days'
Why it works
Recency makes the proof feel active, not historical. Refresh the number weekly or it becomes stale and loses trust.
Pattern 7
Press Mention Strip
Formula
'Featured in <publication 1>, <publication 2>, <publication 3>'
Example
'Featured in Indie Hackers, Starter Story, MicroConf'
Why it works
Press names that the audience trusts. Generic 'as seen in' with no audience recognition is decorative noise.
Pattern 8
Used By Cohort
Formula
'Used by <cohort 1>, <cohort 2>, <cohort 3>'
Example
'Used by post-launch SaaS founders, agency owners, and indie hackers'
Why it works
Cohort-named proof. The visitor self-identifies into the strip without needing to know the names.
Pattern 9
Live Activity Strip
Formula
'<N> founders ran the diagnostic in the last <time period>'
Example
'12 founders ran the diagnostic in the last hour'
Why it works
Live counter (Geo-IP optional). Use only if it's actually true – fake live numbers are a trust kill within minutes.
Pattern 10
Capability Strip
Formula
'<Capability claim 1> | <capability claim 2> | <capability claim 3>'
Example
'90-second diagnosis | No-signup required | 60-day money-back'
Why it works
Not technically proof, but reads as proof when paired with the right visual hierarchy. Use as a fallback when other strips aren't available yet.
Pattern 11
Single Big Logo
Formula
'Trusted by <one big logo> + <small text>'
Example
'Trusted by [Big Recognizable Company] – read the case study →'
Why it works
Single anchor logo beats five small logos when the anchor is recognizable enough.
Pattern 12
Honest Stage Strip
Formula
'<Number of buyers> in <time since launch>. <Honest disclaimer>.'
Example
'47 buyers in the first 90 days. Pre-revenue founders welcome.'
Why it works
Honesty about early stage earns belief from other early-stage founders. Stop performing as bigger than you are.
Common implementation mistakes
- Logo strips with companies you don't have a documented relationship with. Lawyer-bait and trust kill.
- Faded logos that look like decoration. The strip needs enough visual weight to be processed as proof, not pattern.
- More than 7 logos in a single strip. Visitors stop scanning after 5; the rest is noise.
- Mixing customer logos with partner logos and integration logos without labeling. Visitors can't tell what 'trusted by' means.
- A strip that's older than your latest product pivot. Update it whenever the cohort changes.
Real examples from indie SaaS teardowns
Pattern names above are illustrative. These are real, named, dated funnels from the Unlock SaaS teardown set where the social proof bar demonstrates the pattern in a shipping product. Funnel-hack the real ones.
story lens
Mintlify – Output-as-proof
Mintlify made beautiful docs a category. The funnel demos itself.
Visible customer aesthetic strip under the hero. Logos buyers already use, mono, well-spaced.
From the teardown: The marketing site itself runs on Mintlify. There is no story to tell because the reader is already inside the proof. Every interaction with the marketing site is a product demo by accident.
story lens
Cal.com – Developer-credibility through artifacts
Cal.com sells the open-source alternative to Calendly. The repo IS the trust signal.
Developer credibility strip: GitHub star count + contributor count + commit cadence as the proof bar.
From the teardown: 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.
story lens
Polar – Maintainer narratives plus GitHub-native UX
Polar bundled MoR plus creator monetization into a single sell. The funnel targets the open-source maintainer specifically.
Maintainer narratives plus GitHub-native UX. The proof bar is a list of named maintainers.
From the teardown: The story is told through GitHub integration, repo-linked monetization, and maintainer-flavored examples. The product itself sits inside the maintainer's workflow, which functions as story by removing the friction the reader expects.
story lens
Beehiiv – Creator-success showcase
Beehiiv positions against Substack on creator monetization, not features. The funnel sells the upgrade path.
Creator-success showcase strip – named creators with newsletters the buyer can verify.
From the teardown: The story is told through specific creator case studies with named newsletters and stated revenue outcomes. Brunson Hard-Rule applies: only use named, opt-in case studies; do not fabricate. Beehiiv does this well and the funnel benefits.
Which Brunson job does this element do?
This element sits in the Storylens. Knowing the lens tells you what the element is supposed to accomplish, not just what shape it takes – so you don’t rewrite a Story element using Hook tactics or vice versa.
People also ask
What is a social proof bar swipe file?
A social proof bar lives directly under the hero block and answers a single question: 'who else trusts this?' The visitor scans it in under 1.5 seconds. Patterns that earn belief in that window are concrete, cohort-matched, and visually quiet.
When should I rewrite my social proof bar?
When time-on-page is over 20 seconds but the visitor doesn't scroll to the offer block. When the headline qualifies but trust is the next bottleneck.
When is the social proof bar not the right thing to fix?
When you don't actually have the proof. Faking a logo strip with companies you don't have a relationship with is a one-strike trust kill.
Questions founders ask about social proof bar copy
Should the social proof bar be above or below the hero CTA?
Below the CTA, in the band immediately under the hero block. Above the CTA pushes the action below the fold; below the CTA lets the visitor anchor the click in trust.
What if I don't have customer logos yet?
Use a counter strip ('47 founders diagnosed'), a press mention strip if you have any, or skip the social proof bar entirely. An empty strip is worse than no strip.
Should I animate the social proof bar?
No motion if possible. Marquee animations on the proof bar reduce belief by signaling 'effort to look impressive'. Static, monochrome, well-spaced wins.
Related Brunson terms
Apply these patterns to your live page
The free 90-second Launch Diagnostic checks whether the social proof bar is actually the broken step on your page, or whether the bottleneck is upstream.