Your /examples page is doing more conversion work than the page your sales team probably argues about in standups. Clarity shows 84% scroll depth and zero dead clicks across the board, and /pricing is the one with a dedicated funnel behind it. That gap is the whole story: proof beats pitch, and a pattern library is the most copy-pasteable way to weaponize it.
The pattern is reliable because it answers the only question buyers actually have: "Will this look like something I'd ship?" Galleries answer it with screenshots. Pattern libraries answer it with reusable mental models. Buyers skim the same five-second layout — problem, solution, before/after, metric — and pattern libraries give them seven named versions of it instead of one mystery blob. The scroll-depth stat is the receipt: people stay because each post is a self-contained proof of competence, not a teaser for a demo call.
Three structural moves keep these posts converting instead of just looking nice. First, every pattern ships with a label — "The Pricing-Tease Hero," "The ROI Receipt," "The Mute-and-Reveal CTA" — because unnamed patterns don't transfer. Buyers remember "the mute-and-reveal" in a sales call; they don't remember "the third screenshot down." Second, each post isolates one variable. Don't compare two CTAs side by side; build two full pages where only the CTA changes, then name which one cleared 80% scroll and which one stalled at 40%. Single-variable posts are what make /examples outperform /pricing — readers see cause and effect, not decoration. Third, every post ends with the same three lines: the metric, the source, and the offer. "84% scroll depth, Clarity, last 30 days. Want the template?" That closing is doing more work than the headline is, and it's the part most teams forget to write.
Two failure modes will quietly drain the conversion you're seeing now. One: letting the gallery turn into a screenshot dump. The moment a page shows twelve logos and one paragraph, scroll depth drops and the rage-click stat goes to zero for the wrong reasons — confusion instead of clarity. Two: refusing to update it. A pattern library that still shows 2024 design patterns in 2026 isn't proof anymore; it's evidence you stopped shipping. Treat the page like a product surface with a release cadence, not a portfolio you set up once.
Build the library as seven posts, each with a named pattern, a single-variable before/after, and the closing three lines. Publish one per week, tag them in your nav as /examples/pattern-name, and link the newest one from your highest-traffic page. Within a quarter, /examples becomes the page your sales team sends instead of the deck they built.