Every guide to hero copy argues from a dozen hand-picked winners. We cleaned and measured 5,000+ real SaaS headlines instead, and the famous 8-word rule turns out to describe practice rather than prescribe it.
Search for advice on SaaS hero copy and you will find the same article a dozen times. It names two or three copywriting formulas, shows eight to eleven hand-picked headlines from companies like Linear, Loom and Stripe, and closes with a checklist. One of the better-ranking guides states the central rule plainly as a launch requirement: the headline stays under eight words or 44 characters.
Nobody checks it. Every one of those pages reasons from a handful of examples, and every example is a winner, which means the entire genre is built on survivorship bias. So we did the boring version instead. We pulled every homepage hero headline we hold for companies taking payments on Stripe, cleaned it properly, filtered it down to actual software companies, and counted.
The result is 5,000+ real SaaS headlines. The 8-word rule holds for most of them, which is the least interesting finding. The interesting one is that headline language shifts systematically with who the product sells to, in two directions at once, and no example-based guide could have found it.
If you came here to find out whether your headline is too long, the honest answer is that length is probably not your problem. Seven in ten of your competitors are already inside the recommended range, so compliance buys you parity, not advantage. The measurable differences between SaaS homepages sit in word choice and in who the sentence is pointed at, which is the part the checklists skip.
Our Stripe Index dataset holds companies listed on the Stripe public directory, each enriched with a scraped homepage and an AI classification layer covering business model, target customer and whether the product reads as micro SaaS. The hero headline is one of the scraped fields. Getting from the raw field to a countable corpus took four stages, and each one removed a meaningful amount of junk.
| Stage | Rows remaining | What it removes |
|---|---|---|
| Companies with a non-empty hero headline | 23,000+ | Starting point |
| After HTML strip, entity decode, length 8 to 120 characters | 21,000+ | Markup fragments, single words, whole paragraphs |
| After removing scraper artifacts | 21,000+ | JavaScript walls, error pages, loading states |
| After filtering to software companies only | 5,000+ | Every non-software business in the directory |
That last stage is the one that matters most, and it is the reason a study like this has not been done from this source before. The Stripe directory is not a SaaS directory. It is a directory of businesses that accept card payments, which means a raw pull of hero headlines returns junk removal companies, boutique hotels, chimney sweeps and chiropractic clinics alongside the software. Roughly three quarters of the cleaned corpus is not software at all. Skipping that filter would have produced confident numbers about the wrong population.
Two cleaning details are worth recording because they are easy to get wrong. First, the hero headline is stored as raw scraped HTML, so tags and comments have to be stripped before any word counting. Second, and less obvious, stripping tags is not enough: HTML entities survive it. Headlines come through carrying–, ' and &, which inflate character counts and corrupt any quoted example. Both passes are required.
Every number in this article comes from that cleaned 5,000+ corpus, queried live in September 2026. The same approach underpins our other analyses of this dataset, including who micro SaaS actually sells to and the state of micro SaaS competition. If you want to run queries against the same source yourself, the MCP server for AI research exposes it directly.
| Limitation | Effect on the findings |
|---|---|
| Stripe directory only | Skews toward companies that take card payments. Pre-revenue products and enterprise software sold by invoice are under-represented. |
| Headlines scraped once | A point-in-time snapshot, not a time series. We cannot show how a given headline changed or what happened when it did. |
| Target customer is AI-classified | Segment boundaries are model judgements rather than self-reported data, so treat segment sizes as estimates and the direction of travel as the finding. |
| Software filter is AI-derived | The 5,000+ figure depends on classification of business model, so the corpus edge is fuzzy. |
| No conversion data, at all | This is the big one. We measure what headlines say, never what they earn. Nothing here supports a claim that any pattern converts better. |
The typical SaaS homepage headline is six words and 38 characters. The mean sits slightly higher at 39.3 characters, pulled up by a long tail of companies trying to fit an entire value proposition above the fold.
That is short. It is roughly the length of the sentence you are reading up to the comma. It is also remarkably consistent: across every buyer segment we measured, the median lands at five or six words, and the segment means run from 5.92 to 6.83. Whatever else SaaS companies disagree about, they have converged on headline length.
Convergence is itself worth noticing. When 5,000+ independent companies land in the same narrow band, the band is not a competitive edge. It is table stakes, in the same way that having a pricing page is table stakes. If you are looking for an angle, length is the wrong place to hunt for one, and the same logic applies to most of the surface-level advice covered in our SaaS market research guide.
Here is the rule as the top-ranking guides state it: keep the headline under eight words, or 44 characters. One agency page lists it as a pre-launch checklist item. A widely upvoted r/SaaS teardown states a stricter version, telling founders the headline "should state the outcome in 7 words or less." Neither tests it.
| Constraint | Share of SaaS headlines that comply |
|---|---|
| Under 8 words | 69.8% |
| 44 characters or fewer | 65.0% |
| Both constraints at once | 60.7% |
So the rule broadly holds, with an important wrinkle. The two halves of it are not interchangeable. A headline can be under eight words and still exceed 44 characters, because words vary in length, which is why the combined compliance rate drops nearly ten points below the word-count rate. If you are going to apply the rule, apply the character version, because it is the stricter of the two.
The more useful reading is the inverse. Roughly three in ten SaaS homepages break the word rule outright. That is not a rounding error or a handful of outliers, and it is far more deviation than you would guess from a guide showing you eleven compliant examples in a row. A meaningful minority of real software companies have decided a longer headline serves them better, and the checklists have no account of why.
This is the finding the example-based guides could not have reached, because it only appears when you segment thousands of headlines by who the product sells to.
| Target customer | Headlines | Avg words | Mentions AI | Opens with a command | Names the buyer |
|---|---|---|---|---|---|
| Consumer | 1,600+ | 5.92 | 5.9% | 7.8% | 6.4% |
| SMB | 1,600+ | 6.53 | 7.9% | 10.7% | 11.5% |
| Prosumer | 700+ | 6.20 | 10.7% | 13.5% | 11.1% |
| Mid-market | 800+ | 6.83 | 13.1% | 10.0% | 15.7% |
| Developers | 200+ | 5.98 | 16.8% | 9.5% | 17.3% |
| Enterprise | 400+ | 6.21 | 17.2% | 5.0% | 18.7% |
Read the AI column top to bottom. It climbs at every single step: 5.9%, 7.9%, 10.7%, 13.1%, 16.8%, 17.2%. An enterprise-targeted SaaS headline is close to three times as likely to say AI as a consumer-targeted one.
That ordering is counterintuitive if you assume AI is consumer hype. Consumer software is where you would expect the buzzword to be deployed hardest, because consumer buyers are the least equipped to evaluate the claim. The data says the reverse. AI language concentrates where buyers are most technical and most sophisticated, which suggests it is functioning as a specification rather than as decoration. To a developer or an enterprise buyer, "AI" narrows what the product is. To a consumer, it mostly does not.
A founder in r/SaaS put the decorative failure mode precisely: "90% look like they were built from Claude with a one sentence prompt... headlines like 'Empower your workflow with AI.' Zero clarity." The distinction is not whether you say AI. It is whether saying it tells your specific buyer something they did not already know. That is a positioning question, and it is the same one we work through in validating niche viability.
Now read the command-verb column in that same table. It does not climb. It peaks in the middle, at prosumer (13.5%), and collapses at enterprise (5.0%). Prosumer headlines are more than two and a half times as likely to open with an instruction as enterprise ones.
Put the two gradients together and a coherent rule falls out, one that no checklist states: the larger and more sophisticated the buyer, the more a headline names them and the less it commands them.Naming climbs from 6.4% at consumer to 18.7% at enterprise, almost tripling, while commanding falls away.
The mechanism is not hard to guess. "Stop wasting hours on payroll" works on someone who personally does payroll and personally feels the hours. An enterprise buyer is rarely the person doing the task, is evaluating on behalf of a department, and does not respond to being told what to do by a homepage. They respond to recognising themselves in the sentence. The imperative assumes the reader is the user. At the top of the market, they usually are not.
This is the most directly actionable finding here, and it inverts the generic advice. If you sell to prosumers, an imperative is native to your segment. If you sell to enterprise, it is a tell, and naming the buyer does more work. Getting that wrong is a positioning error long before it is a copy error, which is why it belongs upstream in idea validation rather than in a copy pass.
The naming pattern deserves its own look because it is the cheapest change on this list. Headlines that explicitly name an audience, usually with the word "for", run from 6.4% at consumer to 18.7% at enterprise, with developers close behind at 17.3%.
One of the sharpest real examples in the corpus comes from a UK company selling compliance software to a trade: a headline offering certificates, diary, reminders and invoices in one place, "Made for UK and IE chimney sweeps and stove installers." It is 18 words. It breaks the rule comprehensively. It is also impossible to misunderstand, and every chimney sweep who reads it knows instantly whether it is for them.
That is the trade the length rule hides. A longer headline that names a narrow buyer can outperform a short vague one for exactly the audience it names, and vertical software lives on that trade. We see the same dynamic in the categories covered in boring business ideas, where the winning products are unembarrassed about naming an unglamorous trade. A generic six-word headline would be worse for that company, not better. The same instinct shows up in how those companies price, which we cover in SaaS pricing strategies, and in the vertical patterns behind micro SaaS trends.
Micro SaaS headlines are shorter, but only slightly: a mean of 5.93 words against 6.43 for everyone else, a gap of half a word. It is a real difference and a small one.
This is worth saying plainly because the micro SaaS genre encourages a belief that small products need radically different copy. On this measure they do not. They write the same length of headline as everybody else, give or take. The difference between a micro SaaS homepage and a funded competitor homepage is not headline brevity, and founders working through micro SaaS ideas or launching in a weekend should not spend a cycle on it.
Where micro SaaS does differ is in who it sells to, which we measured separately in who micro SaaS actually sells to. Since the language patterns above track the buyer rather than the company size, a micro SaaS product selling to developers should write like the developer segment, not like a small company. Segment beats scale.
The most common opening words across the corpus are, in order: The, Your, Stop, then AI and Turn tied, then A, Get, Build, Run and Welcome.
Two things stand out. The first is that Stop is the most common opening verb by a wide margin, ahead of Get and Build combined in some cuts. Problem-first framing is more common in practice than benefit-first framing, even though the formula lists in the ranking guides skew heavily toward benefit framing. Real companies lead with the pain.
The second is Welcome, which appears as an opening word dozens of times. It is the single most warned-against opener in every guide on the first page of Google, and it is alive and well in the real corpus. That gap between what is universally advised against and what companies actually ship is a decent summary of this whole exercise.
The pattern behind the strong openers is consistent: Your at second place is doing the same job as the naming pattern, pointing the sentence at a specific reader. Finding the language your buyers use for their own problem is a research task, not a brainstorming task, and it is what the Reddit market research and complaint analysis tools exist to do.
A real corpus contains the bad ones, and this is where measurement earns its keep over example lists.
One company selling browser extension security to enterprise buyers has a homepage hero headline reading, in full, "Get in touch." Whether that is a scraping artifact or a genuine choice, it is what sits in the hero slot. Another leads with a headline that runs to sixteen words explaining that a credit score tells you a number while their product tells you what you can actually borrow, which is a good idea expressed at three times the median length.
You will never see either in a listicle of hero section examples, because the genre selects on outcome. It shows you Linear and Stripe and Loom, companies that succeeded for a hundred reasons, and invites you to infer that the headline was one of them. The honest version of the genre would have to admit that most of the companies it draws lessons from would have succeeded with a worse headline, and that the thousands of companies with compliant, well-formed, six-word headlines mostly did not break out.
This is the same reasoning error we document across multi-signal validation: a single signal read off survivors tells you what winners have in common, not what causes winning. Headline advice built on eleven winners is a textbook case.
The Stripe directory gave us a control group almost by accident. Alongside the 5,000+ software companies sit 15,000+ non-software businesses that went through exactly the same cleaning pipeline: the hotels, junk removal outfits, clinics and trades we filtered out earlier. Their headlines are directly comparable, and the comparison is unflattering.
| Group | Headlines | Avg words | Avg characters | Under 8 words | Mentions AI |
|---|---|---|---|---|---|
| Non-software businesses | 15,000+ | 5.41 | 34.9 | 77.9% | 2.0% |
| Software companies | 5,000+ | 6.30 | 39.3 | 69.8% | 9.6% |
SaaS companies write longer headlines than ordinary businesses, by almost a full word and four and a half characters, and they comply with the 8-word rule eight points less often. The entire brevity sermon is being preached at the one group already doing it worst.
It is not hard to see why a plumber outperforms a SaaS founder here. A local trade knows exactly what it sells and to whom, and the headline writes itself in four words. Software has to explain a category that may not exist yet, to a buyer who may not know they have the problem, which is precisely the situation that tempts a founder into a sixteen-word explanation. The length is a symptom of unresolved positioning, not a copywriting failure, and no amount of editing fixes it at the sentence level.
That reframes the advice entirely. When a guide tells you to cut your headline to six words, it is treating the symptom. If you cannot say what you do in six words, the problem is upstream in understanding the market you are entering, not in the sentence. Cutting words without resolving that produces a headline that is short and still says nothing, which is how you end up with "Empower your workflow with AI."
The AI column makes the same point from the other side. Software headlines are nearly five times as likely to mention AI as non-software ones, which is unsurprising, but it does mean the word is doing a lot of differentiating work in a field where everyone is reaching for it. Our micro SaaS examples show the alternative: name the specific job instead.
The guides are not wrong about everything, and it would be dishonest to imply otherwise.
They are right that brevity is normal, and the data confirms it at 69.8% compliance. They are right that clarity beats cleverness, a point a solo founder at $10k MRR made in r/SaaS more plainly than any agency page: "Your landing page should make it obvious what the product does. That matters more than some vague, clever-sounding headline. People are tired of reading landing pages." They are right that the hero slot carries disproportionate weight, which is the sense behind the Ogilvy line repeated in r/SaaS that "when you've written your headline you've spent 80 cents of your dollar."
They are also right that naming the specific job beats describing the category, and our naming data supports it directly, at least as a description of what more sophisticated segments do.
What they lack is evidence. Every one of those claims is asserted from examples, and several of them turn out to describe existing practice rather than identify an improvement. Knowing that 69.8% of your competitors already comply changes what compliance is worth.
The honest limit of this study is that it has no outcome data whatsoever. We measured 5,000+ headlines and zero conversion rates. We cannot tell you that short headlines convert better, that command verbs lift signups, or that mentioning AI helps or hurts. Nothing here supports any of those claims.
Worth noting: neither can the guides ranking above this page. They assert conversion outcomes while citing eye-tracking studies about attention and CTA-wording studies about buttons, which are not the same thing as evidence about headline text. The difference is that this page says so.
The one genuine conversion data point we found came from the audience rather than from any vendor. A team in r/SaaS swapped headlines, proof bars and logos per audience segment across their top five pages and reported demo submissions moving from 0.9% to 1.7%, with time on page rising from 56 seconds to 1 minute 18. One team, one self-reported test, so treat it as a lead rather than a finding. But it points the same direction the segmentation data does: the win came from matching the message to a named audience, not from shortening it.
There is also a fair challenge to the entire premise, and it came from a consultant in r/SaaS who cancelled a client redesign after checking one number: "Everyone is A/B testing headlines on the landing page while user number 4,000 rage clicks a settings screen that assumes knowledge they don't have." Headline work is cheap and visible, which is exactly why it absorbs attention that a broken activation flow deserves.
Four things follow from the data, in order of how much they are likely to matter.
Stop optimising length. You are almost certainly already inside the band, and so is everyone you compete with. Check the character count once, keep it at or under 44, and move on.
Match the verb to the buyer. If you sell to prosumers or SMBs, an imperative is native and common. If you sell to enterprise, it reads wrong, and naming the buyer does more work. This is the clearest segment-specific signal in the dataset.
Say AI only if it specifies something. The gradient suggests AI functions as a specification for technical buyers and as decoration for everyone else. If removing the word would not change what a reader understands your product to be, it is decoration.
Consider breaking the rule deliberately. Three in ten SaaS companies do. If you sell to a narrow vertical, a longer headline that names the trade may beat a compliant one that could describe forty products, and the chimney sweep example is a better model for vertical software than any of the famous ones.
All four are downstream of knowing who you are selling to, which is the actual hard part. If you are still resolving that, start with the idea validation tool, work through how to validate an idea, and use market research tools to find the language your buyers already use, the same way the teams in our Stripe Index user stories did. Copy is the last step, not the first, and how to find SaaS ideas covers the step before it. Our idea validation tools roundup and guide to AI market research both cover the upstream work, and companies using Stripe plus micro SaaS ideas from the Stripe Index show what else this dataset surfaces.
Want the data behind the copy? BigIdeasDB tracks 1M+ complaints alongside the Stripe Index, funded company data and revenue intelligence, so you can find the exact language a market uses about its own problems before you write a word of a homepage.
Start researching with BigIdeasDB →Most real ones are short. Across 5,000+ measured SaaS homepage headlines the median is 6 words and 38 characters, and the mean is 39.3 characters. The widely repeated advice to stay under 8 words describes what 69.8% of SaaS companies already do, so treat it as a description of common practice rather than a tested rule.
69.8% are under 8 words and 65.0% are 44 characters or fewer, but only 60.7% satisfy both constraints at once. That leaves roughly 3 in 10 SaaS homepages breaking the rule, considerably more deviation than any example-based guide suggests.
It depends entirely on who they sell to. AI mentions rise steadily with buyer sophistication: 5.9% of consumer-targeted SaaS headlines, 7.9% for SMB, 10.7% for prosumer, 13.1% for mid-market, 16.8% for developers and 17.2% for enterprise. Enterprise headlines are close to three times as likely to say AI as consumer ones.
That depends on the buyer, and the pattern runs opposite to the AI one. Command verbs such as Get, Build, Stop and Turn open 13.5% of prosumer headlines but only 5.0% of enterprise ones. The larger the buyer, the more often headlines name that buyer and the less often they issue an instruction.
This dataset cannot answer that, and neither can the guides that claim it. We measured what 5,000+ SaaS homepages say, not what those homepages earn. There is no conversion, traffic or revenue data attached to these headlines, so any claim that a shorter headline converts better is unsupported by this research.
BigIdeasDB Research. (2026). SaaS Homepage Headlines: What 5,000+ Actually Say. BigIdeasDB. Retrieved from https://bigideasdb.com/what-saas-homepage-headlines-actually-say