Briteview BI describes the category. Two lines down, it could describe a buyer.
A sub-hero that restates the hero is a missed beat. Here is what happens when the second line earns its keep.
Each post takes one fictitious company under a software category and rewrites a single positioning artifact — the hero, the tagline, the product overview, the about-page argument. The Before is the copy a real marketer might ship on autopilot. The After is the outside-in rewrite, grounded in a named buyer, a stated outcome, and a claim a competitor could not make without changing it.
Meet Briteview BI.
A 60-person BI tool aimed at revenue operations leads who gave up on Tableau dashboards nobody in sales will open.
Artifact: Hero tagline — The sub-hero line below the H1 — where the clarifier goes.
“Powerful analytics for data-driven decisions, built for the modern enterprise.”
“For RevOps leads whose CROs stopped opening Tableau dashboards a year ago.”
Briteview BI is invented. We use fictitious names so the “Before” can be honestly bad without embarrassing a real team.
What actually changed — and why it generalizes.
The sub-hero is the hardest line on a homepage. The hero has to stay categorical enough for a scanning reader to place the product in five seconds. That leaves the sub-hero to do the specificity work — the named buyer, the particular failure mode, the reason this product exists that the hero could not fit. Most sub-heroes fumble the handoff. Briteview's Before sub-hero is the common failure.
"Powerful analytics for data-driven decisions, built for the modern enterprise." Read it slowly. Every phrase is a synonym for something the hero already said. Powerful analytics restates the product category. Data-driven decisions restates the outcome. Modern enterprise restates the audience. The sentence takes up twelve words to add zero information, which is worse than twelve words that add wrong information, because silence at least reads as style.
The After sub-hero gives the twelve words a job. "For RevOps leads whose CROs stopped opening Tableau dashboards a year ago." It names a persona (RevOps lead — not "data-driven decision makers"). It names a specific, concrete failure (CROs stopped opening Tableau dashboards — a pattern anyone in the category recognizes). It implies a deselection (if your CRO still happily opens Tableau dashboards, you are not the buyer — go back to Tableau). It uses a number ("a year ago") to anchor the pain in recent lived time, not abstract possibility.
Notice what the After does not do. It does not claim to be faster, easier, more modern, or more AI-native than Tableau. It does not name the product's features. It does not reach for superlatives. The rewrite's whole move is subtractive — strip out every word that a competing BI tool could use without editing, and see what is left. If what is left names a real person and a real failure, the sub-hero is earning its space. If not, keep subtracting.
There is a structural lesson here that transcends the sub-hero. Category claims (the hero) and buyer claims (the sub-hero) are different jobs. Most homepages put a category claim in both slots and waste the second one. The rewrite pattern is: let the hero stay categorical enough to be placed; let the sub-hero be so buyer-specific that a rival in the category could not copy it without either becoming a different product or being dishonest.
If your own sub-hero reads like a restatement, try the test Briteview failed. Read your hero. Read your sub-hero. Ask yourself: if I deleted the sub-hero entirely, what would the reader lose? If the honest answer is "not much," the sub-hero is paying rent on a seat it is not occupying. Rewrite it to name the specific breakdown your product exists to fix — the meeting that would be better, the Tuesday-morning friction that would stop. Specificity that excludes the wrong buyer is the specificity that earns the right one.
The rewrite is a pattern, not a miracle. You can run it on your own copy in minutes.
Copy Studio drafts outside-in rewrites grounded in your strategic context — named buyer, stated outcome, claim a competitor cannot also make. Positioning Audit tells you where the drift lives on your site.