
Better Stack's Hero Section Does the Math for You. Should Yours?
Better Stack replaced vague "cheaper than Datadog" claims with a live cost comparison widget in its hero. Here's what the detection shows and when this pattern is worth copying.
Jordan Reeves
Founder & Operator · · Updated
Better Stack put a calculator in its hero. Not a demo request form, not another testimonial carousel — a live, interactive pricing card that puts Datadog's number next to Better Stack's number for the exact same 1TB of logs, traces, and metrics. We caught this on betterstack.com's homepage, and it's worth slowing down on, because it inverts almost every instinct teams have about what belongs above the fold.
TL;DR
- Detected on betterstack.com, page type: home, surface: hero
- Pattern: interactive side-by-side pricing calculator, category "calculator"
- Comparison basis: identical usage — 1TB of logs, traces, and metrics — priced against Datadog
- Evidence copy: "At a fraction of your current costs — 1 TB (Datadog) vs 1 TB (Better Stack) — Explore pricing"
- Rarity score: 70% (uncommon pattern) · Importance score: 75% (high potential impact)
- Category: calculator widgets in hero position, rare among observability/infra SaaS homepages
What is Better Stack actually showing visitors?
The hero displays a real cost comparison card, not a claim — Datadog's price and Better Stack's price for the same 1TB usage tier, side by side.
Most competitor-positioning copy on SaaS homepages is a sentence: "up to 80% cheaper than X." Better Stack skipped the sentence and shipped the receipt. The widget holds usage constant — 1TB logs/traces/metrics — and lets the pricing math do the persuading. The evidence quote we logged, "At a fraction of your current costs," isn't the headline claim; it's the caption under a number the visitor can actually inspect. That's the entire trick. You're not asking anyone to trust an adjective.
I've shipped plenty of "faster than X" and "cheaper than Y" hero copy over the years, and I can tell you the internal debate is always the same: legal worries about the comparison, design worries about clutter, and growth worries about whether anyone reads past the first five words of a hero. Putting a calculator there settles all three arguments at once, because the widget is the substantiation. Nobody has to take your word for it if you show your work.
Why does this sit in the hero instead of a pricing page?
Because observability buyers are already mid-comparison-shop before they land, so the hero meets them at the exact question they came with.
Nobody arrives at an observability vendor's homepage cold. They arrive because their Datadog bill just did something alarming, or a Slack thread started with "does anyone know what we're actually paying for logs." That visitor's very first mental question is a subtraction problem: how much would I save. Burying the answer three scrolls down or behind a "Pricing" nav link adds friction at the exact moment intent is highest.
This lines up with a point Wingify makes about landing page iteration — the winning move is usually not a bigger claim, it's removing a step between the visitor's question and the answer. A calculator in the hero collapses "read claim → get skeptical → go find pricing page → do mental math → maybe come back" into one glance.
How rare is this pattern, and why does that matter?
We score this detection at 70% rarity — interactive calculators are common on pricing pages but rare as a hero-level surface.
Calculators aren't a new CRO idea. Insurance sites, payroll platforms, and cloud cost tools have used them for years — usually parked on a dedicated "ROI calculator" page that gets a fraction of homepage traffic. What's rare is putting the calculator where the traffic actually is.
| Surface | Common pattern | Rarity |
|---|---|---|
| Pricing page | Static tier comparison table | Low — nearly universal |
| Dedicated ROI/calculator page | Interactive input-driven calculator | Medium — common in fintech, cloud cost tools |
| Homepage hero | Interactive competitor cost comparison | High — this detection, 70% rarity |
| Homepage hero | Vague "cheaper than X" claim only | Low — the default most teams ship |
The importance score (75%) tracks with that rarity. A hero-level calculator isn't just a novelty — it's a substantiation mechanism sitting in the highest-traffic, highest-intent real estate on the domain.
What's the actual risk here, and is it worth it for your team?
The risk is maintenance and legal exposure on competitor pricing data, not conversion — teams should weigh accuracy upkeep against the credibility gain.
Two real costs come with this pattern. First, competitor pricing changes, and a stale comparison widget is worse than no widget — it becomes a trust liability instead of a trust builder the day Datadog repriced and nobody updated the card. Second, legal review on named-competitor pricing claims is not instant, especially if your company has any enterprise sales motion where a competitor's rep will absolutely screenshot it back at your buyer.
Neither of those is a reason to skip it. They're reasons to scope it: pick the one comparison that's true often enough to be low-maintenance (usage-based pricing tiers that don't change monthly), and build a lightweight internal process to re-verify the numbers quarterly. This is the same discipline Coaxsoft describes about isolating variables rather than redesigning everything — you're not redesigning the hero, you're adding one component with a clear owner and a refresh cadence.
Is this a pattern worth testing, or just a Better Stack-specific move?
It's testable by any company with a dominant, well-known competitor and a genuinely favorable, verifiable price comparison.
The precondition matters more than the pattern. This only works if three things are true: your category has one or two competitors everyone already compares you to mentally, your pricing advantage is real and specific (not "generally cheaper" but "cheaper at this exact usage tier"), and you can keep the numbers current without a quarterly fire drill. If any of those three is shaky, you'll ship a hero component that either doesn't move the needle or actively erodes trust when it's wrong.
Common questions
What made this detection rare instead of just another pricing comparison?
Most pricing comparisons live on dedicated pricing or comparison pages, seen by a small slice of visitors. Better Stack placed a live, interactive cost calculator directly in the homepage hero — the highest-traffic surface on the site — which is uncommon; we scored it 70% rarity.
Does a hero calculator like this actually increase conversions?
We don't have Better Stack's internal test data, but the mechanism aligns with established CRO logic: reducing steps between visitor intent and answer, and replacing vague claims with numeric evidence, both of which FullStory lists as core CRO practices.
Is naming a competitor directly in a hero widget legally risky?
It can be, depending on jurisdiction and how the comparison is sourced. Companies doing this typically cite competitor pricing from public rate cards and update it on a fixed schedule, with legal sign-off on the comparison basis (same usage tier, same units) to keep the claim defensible.
Could a smaller SaaS team build something like this in a sprint?
Yes, if the pricing logic is simple. A static-but-accurate comparison card (not a fully dynamic calculator) can ship in a sprint if you already have clean tier pricing for yourself and your named competitor, with the main cost being design and legal review, not engineering.
What I would actually do next
If your product has a clear, named competitor and a pricing structure simple enough to compare honestly at one usage tier, don't build a full dynamic calculator first — ship a static comparison card in the hero for that one tier, get legal and design sign-off fast, and watch scroll depth and pricing-page click-through for two weeks before you invest in making it interactive. The interactivity is the polish; the number is the conversion driver.
Read next
More from the ABWatcher blog
Nov 22, 2026
Snake River Farms Tests a $25-Off Popup on Its Ad Landing Page
We caught Snake River Farms split-testing an email-capture form and $25-off modal on its landing page. Here's the math on what it would take to call a winner.
Nov 21, 2026
Snake River Farms Tests Mid-Page Email Capture on Its Ad Landing Page
SRF is A/B testing a mid-page lead-capture block and a $25-off popup against a simpler hero-only promo banner on its paid landing page, detected 2024 week-over-week.
Nov 20, 2026
Attio Is Testing a New Tier, Higher Prices, and a New Pitch
Attio is running a live pricing page test with a new $1,000 "Ultra" tier, higher Plus/Pro prices, and a new headline — here's what we caught and what it means.
Nov 19, 2026
Found Quietly Tested a 25% Price Cut on Its Pricing Page
We caught Found running a live pricing A/B test with an annual billing toggle that drops Found Plus from $35 to $26.25/mo. Here's what changed and why it matters.
Nov 8, 2026
Astro Proves "Zero Lock-In" With a Live Code Demo, Not a Claim
Astro's homepage replaces a trust badge row with a working, clickable framework demo — here's the hierarchy and interaction design behind it, detected 60% rare on astro.build.
Nov 7, 2026
Basecamp's Big Numbers: Why Hyper-Precise Stats Beat Vague Social Proof
Basecamp's homepage swaps "trusted by thousands" for 1.7 billion to-dos and 5 petabytes of data. We break down why precision beats vagueness as social proof — and how to test it.
From the glossary
Vocabulary the article uses. See all terms →
- Shrinkage Estimator— A statistical adjustment that pulls noisy per-variant or per-segment estimates toward an overall average to reduce overfitting to randomness.
- Flicker Test— A diagnostic check to confirm whether users briefly see the original page before a variant renders in client-side experiments.
- Pre-Experiment Bucketing Audit— A review process confirming users are being randomly and evenly assigned to experiment variants before launch.
- Above-Fold Exclusion Rule— A test-design rule that deliberately prevents changes to above-the-fold elements so an experiment isolates below-the-fold effects.
- Flicker-Free Testing— A technical setup that prevents users from briefly seeing the original page before a test variant loads.
- Orthogonal Test Design— A test structure where multiple variables are changed independently so their individual effects can be measured without interference.
See more like this
ABWatcher catches A/B tests like this across 1,000+ brands.
Watch live experiments at 1,000+ high-converting brands, complete with hypothesis and takeaway. 7 days of Pro, free, no card, then Free forever for ten watched companies.