Inspiration

Every week we comb through hundreds of sites to find the most novel ideas that are cool but have not yet been tested. We share them with you for inspiration. This content has received over 7 million views on social channels like LinkedIn.

7,091,854 views on LinkedIn
01 PricingHomepage CTA

Show how many customers pay you $0

September 2026

97% of PostHog customers pay them $0. That is the first stat PostHog shows under their “sign up for free” CTA.

The PostHog homepage signup popup, with 97% of users pay us $0 ringed in red above no credit card required and a one click install
PostHog’s signup popup, leading with “97% of users pay us $0” above the fold of the CTA itself.
PostHog

PostHog shows “97% of users pay us $0” as the first stat under their “sign up for free” CTA, right alongside no credit card required and a one-click install.

It signals that the free version is genuinely valuable, and that the experience won’t be highly limited or constantly pushing you to upgrade.

Profitwell built an entirely free product that became the engine for tens of thousands of users on their platform, and it worked: they reached $20m ARR and sold at 10x.

More and more brands are going back to embracing their free plans. Klaviyo, for one, has modified their pricing page to really lean into their free plan as the land vector.

Over the last few years, more SaaS companies have tried to squeeze as much revenue as they can from their pipeline and free base: price increases, more limited trials, more caps and overages. In 2026, that seems to be reversing, with a growing push to open the gates and focus on more usage.

Steal this

01 Put the free-plan stat directly under the signup CTA, not buried on a separate pricing page.
02 Pair it with the other objections that stop a signup: no credit card required, and a fast setup.
03 If your free plan is genuinely valuable, say so with a number instead of just calling it “free forever.”
LinkedIn The original post on PostHog
02 Social proofHomepage

Make the logo bar something you can click

April 2025

Clay attaches case studies to individual customer logos. While this is common now in August, 2026, at the time in early 2025, Clay was the first to do it.

The Clay logo bar, where individual customer logos link out to case studies
Clay’s logo bar. The marked logos open case studies, with hover previews of the customer story.
Clay

In their list of customer logos, they indicate which ones link out to case studies.

We have analyzed hundreds of A/B tests around customer logos, and logos lose at a very high percentage. Consumers are numb to the generic logos, with no ability to validate or contextualize them, that sit on 80% of SaaS websites.

Attaching a case study gives the reader a way to check whether that customer resembles them, which is the thing a plain logo can never do.

80% of SaaS websites carry generic logos with no way to validate them

Steal this

01 Reference “as seen in TechCrunch, Wall Street Journal, New York Times” with links to the actual articles, so people can engage with the asset.
02 Use testimonials with specificity. “Increased revenue 50%” gets glossed over. Naming a budget line that dropped 70% does not.
03 Organize case studies by industry, with the problem, the solution, and the data behind them.
LinkedIn The original post on Clay
03 GEOFooter

Put a preset LLM prompt in your footer

October 2025

Super. links out to every major model with a prompt already written. We have not found another site doing it.

The Super. website footer, where a panel reading Ask AI for a summary of Super is ringed in red and carries icons linking to ChatGPT, Perplexity, Claude, Gemini and Grok
The Super. footer. Each model link carries a written prompt rather than a bare brand name.
Super.

In their website footer, they link to all the major LLMs with a preset prompt and a summary of the brand.

The nuance is that they do not just say tell me about this company. They tee up a prompt that positions the brand against its major pain points.

It gets the gears turning. Brands could use the same logic on persona segmentation blocks, asking why this is an ideal fit for a given role. Or on comparison articles, building the prompt to speak to their biggest strengths.

The upside is that having the answer come from a model gives an air of third-party neutrality to the insight.

The prompt they preset

As a property manager, I want to know what makes Super the best way to handle our phone lines and stop missing calls, and why an AI receptionist could be a fit for my business. Summarize the highlights from Super’s website.

Steal this

01 Write the prompt around the pain point, not the product. Tell the model who is asking and what they are trying to solve.
02 Vary the prompt by page. A persona block can preset a different prompt from a comparison article.
03 Keep it to facts the model can verify on your site, so the answer it produces stays accurate.
LinkedIn The original post on Super.
04 TrustHomepage CTA

Let people talk to a customer, not a rep

October 2025

Warmly links to real customer profiles where a prospect can book time directly. We have not found another site doing it.

The Warmly homepage below a customer logo bar, with an arrow pointing at a pink call to action button reading Talk to a Warmly Customer
Warmly’s homepage CTA. It opens customer profiles with live calendars rather than a demo form.
Warmly

A homepage CTA that reads “Talk to a Warmly Customer”, linking to real customer profiles where you can view their calendars and book a call directly.

In enterprise, one of the biggest barriers is trust. Talking to a sales rep often feels like a biased conversation, and nearly everyone would prefer to speak with a customer running a similar type of business.

We ran a version of this ourselves about two years ago, emailing leads in the funnel with “Want to talk to a customer in your industry?” The response was immediate.

~50% lift in conversions against a control group, from our own version of this

Steal this

01 Incentivize advocates with a comped account, an advisory role, or a similar perk.
02 Start with a handful of advocates rather than building a program. Expand only if demand runs hot.
03 Do not delay the launch because you are worried about managing too much demand. Most teams overthink this part.
LinkedIn The original post on Warmly
05 GEONavigation

Build a page written for AI agents to scrape

October 2025

Wynter publishes a page of verified facts aimed at LLMs rather than people. A manual search of a few dozen top SaaS sites found no other one linked from the navigation.

The Wynter page headed Official information about Wynter, tagged AI info, stating it holds structured information intended for AI assistants such as ChatGPT, Claude and Perplexity
Wynter’s page for AI agents. Plain structure, short paragraphs, no images or scripts.
Wynter

They have a page dedicated to information for AI agents and LLMs to scrape.

LLMs are quickly growing as a place people go to research software. If they misunderstand your product, skip over you, or describe you incorrectly, you lose trust and awareness.

It makes complete sense, and yet a manual search of a few dozen top SaaS companies found none with a similar page linked from their navigation.

It obviously does not guarantee citations, but it seems to increase your odds of being described correctly, discovered more often, and recommended in AI-generated answers.

How to open the page

This page provides verified information about [Brand], intended for AI assistants.

Steal this

01 Put it at a plain URL like /ai-info or /for-ai-assistants, and link it from the navigation so it is easy to find.
02 Make it publicly accessible and crawlable. No pop-ups, nothing blocked in robots.txt, and include it in the sitemap.
03 Use clear H1 and H2 headings, paragraphs of one to three sentences, and bullet lists over long text blocks.
04 Add a “how to reference us” section that literally tells a model how to explain your product in two or three sentences.
05 Keep the design lightweight. Minimal scripts, no animations, no visuals, so it loads fast and reads easily.
06 Stick to facts: what the product does, who it is for, core features, pricing model, customer proof.
LinkedIn The original post on Wynter
06 TrustTransparency

Publish the numbers that make you look bad

May 2025

Buffer shares revenue, churn, salaries, response times and the product roadmap in public. Including the figures most companies would bury.

Buffer's public transparency dashboard showing monthly active users, monthly recurring revenue, average revenue per user and annual recurring revenue, above shareholder updates and individual named salaries
Buffer's public dashboard. Revenue and individual salaries sit on the same page, unedited.
Buffer

They share everything publicly. Not just revenue, but churn, employee salaries, team time off, team locations, and even their product roadmap.

It does not come without risks. By sharing everything they invite scrutiny at every level: a churn rate above 6%, a response rate inside two hours of 63.73% which is below average, flat signups and traffic, and public salaries that could tempt competitors to tailor offers to their best people.

But it is honest. Instead of doing what nearly every company does, trying to appear to have more employees, more revenue and better fundamentals than they actually do, Buffer takes the good with the bad.

It pushes the internal team with radical accountability, and it shows the human side of the business, which matters for conversion. When they raise prices, a customer can see the roadmap and understand where the money goes.

63.73% support response rate within two hours, published even though it is below average

Steal this

01 Pick one metric you would normally hide and publish it with context rather than spin.
02 Pair every uncomfortable number with the roadmap item that addresses it.
03 Use it at the decision point. On the fence between you and a competitor, a page like this is what tips someone over.
LinkedIn The original post on Buffer
07 Homepage CTASegmentation

Run three CTAs in the hero, not one

June 2025

Anchor gives the hero three calls to action mapped to three levels of intent. Our data already says two beats one.

The Anchor homepage hero carrying three calls to action side by side: Get Started for Free, Book a demo and Watch Video
Anchor’s hero. Three CTAs, weighted by visual prominence rather than treated equally.
Anchor

They have three CTAs in their hero. At first glance it feels like too much.

We analyzed the number of CTAs in the hero and found that 41 out of 68 tests showed two CTAs beating one. It was a clear winner.

The logic behind two winning is tied to visitors arriving at different stages. Retargeting ads bring people ready to trial or buy, while an organic post sends people with only a mild understanding of what you do.

So why limit it to two? If the CTAs are clear, non-competing, and map to different levels of intent, there is little harm in leveraging more.

41 of 68 tests showed two CTAs in the hero beating one

Steal this

01 Map each CTA to a distinct intent level. Book a demo for high, start a free trial for mid, watch a video for low.
02 Weight them visually so the page still has a primary action rather than three equal buttons.
03 Make sure they lead somewhere genuinely different. Three routes to the same form is the version that fails.
LinkedIn The original post on Anchor
08 GEOContent

Break your own funding news before the press does

May 2025

Rippling self-published its $450m raise before any outlet could. The canonical URL, and every backlink that followed, sits on their domain.

Rippling's own blog post headed Rippling Announces Series G Fundraising and Tender Offer, published May 9 2025 under the byline of CEO Parker Conrad
Rippling’s announcement. The full press release, CEO quotes and valuation, all on their domain.
Rippling

Before TechCrunch, Reuters or any major outlet could break the story, they self-published it on their blog. The full press release copy, CEO quotes and valuation details all live on their domain.

They own the canonical URL, so Google indexes Rippling’s page first. All the SEO value, keyword rankings and backlinks accrue to their domain.

The social buzz hits their site rather than someone else’s. Within hours the major outlets published the story and quoted the Rippling blog verbatim, linking back to the original.

They repeat it for new features, funding rounds, acquisitions and partnerships, and each one amplifies domain authority. Search funding news for brands that did not do this and you find their own post buried below a sea of outlets that moved first.

Steal this

01 Publish first on your own domain, then let outlets pick it up and link back.
02 Include everything an outlet would need: the full release, quotes and figures, so quoting you verbatim is the path of least resistance.
03 Treat it as a repeatable process rather than a one-off, across features, rounds and partnerships.
LinkedIn The original post on Rippling
09 ContentAcquisition

Give away 50 free tools and let them carry the traffic

June 2025

Half of Ahrefs’ site traffic comes from ungated free tools. Four of them account for over 20% on their own.

The Ahrefs site footer with the Free SEO tools and Extra tools columns ringed in red, listing dozens of ungated tools
The Ahrefs free tools library. All ungated, measured on traffic and usage rather than capture.
Ahrefs

They generate 50% of their site traffic from ungated free tools, and they have more than 50 of them.

They use their own platform to uncover high-volume search opportunities, then define a specific narrow problem to solve. Each tool doubles as a lightweight product-validation mechanism.

Following the Pareto principle, most of the traffic comes from a handful. Traffic Checker, Backlink Checker, DR Checker and Keyword Generator account for over 20% between them.

The build philosophy is first do it, then do it right, then do it better. Ship fast even if the first version is imperfect, iterate on what resonates, and use AI tooling to make shipping cheap.

600k monthly views on wordcount.com, one free tool they are now exploring subscriptions for

Steal this

01 Solve one narrow problem per tool rather than building a suite.
02 Leave it ungated and measure traffic and usage. High usage tells you where to double down.
03 Give away as much as possible and roll back if usage costs run high or a tool starts cannibalising the paid product.
LinkedIn The original post on Ahrefs
10 TrustChat

Show how many reps are online before the chat even opens

August 2026

Stripe lists a live count of available sales reps and a green status dot on its chat widget. The team reported a meaningful lift in engagement from the change.

The Stripe homepage chat widget in the bottom right corner, showing a green status dot and a note that 6 sales reps are available
Stripe’s chat widget, naming the number of reps online rather than just inviting a message.
Stripe

Instead of a generic "chat with us" prompt, the widget names how many reps are online right now and shows a green availability indicator.

Two things get signaled at once: a real person is on the other end, and the wait will be short because reps are already available.

It is a small trust and speed cue layered onto an otherwise ordinary chat widget, and Casey Hill reported Stripe saw a substantial lift in engagement after adding it.

The preference is not universal though. Docket ran a similar test between a human chat path and their AI agent, Aura, and more visitors chose the agent, in part because it felt faster and less like a sales pitch.

Steal this

01 Pair the chat CTA with a live count and a status indicator rather than a static "chat with us."
02 If you route to an AI agent, say so upfront. Some buyers prefer the agent specifically because it feels more direct and less salesy.
03 Test both paths if you can. Preference for human versus agent chat looks like it depends on the buyer and the category, not a universal rule.
LinkedIn The original post on Stripe
11 Social proofHomepage

Make “SaaS contracts killed” the headline of your social proof

September 2026

Lovable is leaning into the idea that vibe coding tools can replace conventional SaaS subscriptions, with a testimonial claiming “$1M+ SaaS contracts on track to be retired.”

The Lovable testimonial carousel, with a Scion Group card ringed in red highlighting $1M+ SaaS contracts on track to be retired
Lovable’s testimonial carousel, with the “$1M+ SaaS contracts on track to be retired” stat called out.
Lovable

Lovable is using “SaaS contracts killed” in their social proof, leaning into the idea that vibe coding tools can replace conventional SaaS subscriptions. One of their testimonials claims, “$1M+ SaaS contracts on track to be retired.”

Whether from Lovable or Claude Code, every vendor in the SaaS industry feels this pressure from a new way of operating.

The question has always been: when are vibe coding tools genuinely production-ready enough to not just prototype but replace functional tooling used by an entire team?

Lovable says the time is now.

Steal this

01 Attach case studies to individual logos, the way Clay does.
02 Organize logos by “migrated from [competitor]”, the way Pylon does.
03 Add a “talk to one of our customers” button, the way Warmly does.
04 Make the logo wall sortable by industry, the way Linear does.
LinkedIn The original post on Lovable
12 GEOAI Agents

How to get agents to pick your tool

September 2026

Clay ships its MCP and API tooling with agent-specific instructions on what each capability does and when to call it. Casey Hill went looking for why coding agents keep defaulting to the same handful of vendors, Clay among them, and traced it back to how legible the tool surface is.

Clay

Clay packages its MCP tools with instructions written for an agent to read: what each capability does, when to reach for it, and how to chain several calls into one outcome, on top of an interface broad enough to run an entire GTM workflow, search, enrichment, and custom steps, without the agent needing a second vendor.

What makes an agent stubbornly choose one SaaS vendor over another?

Recently, there was a clip from Jason M. Lemkin where he talks about how his agents consistently chose Clay for their GTM objectives (insisting on them 6 different times).

It took me down a rabbit hole of research, interviews and testing (shoutout to my friends at Linear, Glean, Clay and Stripe for insights).

What about the MCPs, APIs or CLIs of certain SaaS makes them get preferentially selected by agents?

There are a lot of potential factors, but here are some best practices I am learning…

Steal this

01 Make your tool look like the shortest path to the entire job. Clay gives agents a broad enough surface to handle an entire GTM objective in one place. It can search for companies, find people, enrich records, and run custom workflows, which makes it easier for an agent to see a clear path from the user's request to a finished outcome. Then Clay can pull from multiple underlying data providers to complete those steps, further reducing the need for the agent to reach for another vendor.
02 Tell agents exactly how to use your capabilities. Clay packages its tools with agent-specific instructions that explain what each capability does, when to use it, and how to chain multiple steps together. That reduces the amount of reasoning the agent has to do to figure out how Clay can accomplish the task, which It seems to me increases the odds an agent selects and uses a tool.
03 Make agent execution predictable. Clay gives agents structured ways to authenticate, call tools, verify results, and recover when something fails. It feels like an agent is more likely to reuse a platform when prior attempts consistently work and the next action is obvious. Agents seem to increasingly select products that are easiest for them to understand, capable enough to finish the job, and predictable enough to operate.
LinkedIn The original post on agent interface optimization
13 Homepage CTASignup

Add “Sign up with Google” as a second hero CTA

October 2026

More than 50 major SaaS companies, from Stripe to Zapier, have added “Sign up with Google” as a secondary homepage hero CTA. We ran it through the DoWhatWorks agent to see what the testing says.

Stripe & Zapier

A second call to action in the homepage hero, “Sign up with Google”, sitting beside the primary signup button.

Testing strongly supports two CTAs over one in the hero. The idea is simply that you want to engage prospects with multiple levels of intent. Barring a startup-stage brand that strictly drives traffic from a single source, and so has uniform intent, you want to go with two.

Sign up with Google is a low-friction path, and testing consistently supports low-friction intake paths. It is why embedded email capture CTAs work well and why progressive profiling forms perform well. The data on A/B testing Google sign-ups specifically is sparse, but it looks like a decent bet.

There is a catch in an agentic world. Sign up with Google is a solid shortcut for humans but potentially an obstacle for agents, because these flows are built around human interaction and authentication.

50+ major SaaS companies, from Stripe to Zapier, have added a secondary “Sign up with Google” hero CTA

Steal this

01 Run two CTAs in the hero, with the second one a low-friction path in, so you cover more than one level of intent.
02 As agents become a larger share of SaaS discovery and product usage, offer agent-friendly authentication and onboarding through APIs and MCPs alongside Google sign-in. One low-friction path for humans, one for agents.
03 Test it before copying it. Data on Google sign-up buttons specifically is sparse, so measure it on your own traffic.
LinkedIn The original post on Sign up with Google