My landing leads with what we don't do. Mistake?
Most SaaS landing pages open with a feature list or social proof. Mine opens with a negative. The headline is "Run a referral programme. Not a compliance audit", and the first real section is titled "the three things every European affiliate stack gets wrong." It says what's broken before it says what I do. I want that torn apart, because I'm not sure it's the right call.
The reasoning, so the roast is fair:
I build affiliate tracking for EU SaaS. The product exists because the usual tools set browser cookies, which in the EU means a consent banner, and attribution that quietly breaks in Safari and behind ad blockers. Mine is server-side and first-party, so there's no banner to show. That's a real difference, but it's a difference shaped like an absence, and absences are hard to sell.
The other reason I led this way is less noble: I launched weeks ago and have no customers yet, so "trusted by 200 teams" isn't a line I can write. Problem-first was partly forced on me.
Here's what worries me. Leading with the problem assumes the reader already feels it. Someone who has never fought a cookie banner or lost sales to a Safari attribution gap reads "no cookie banner" and feels nothing. A feature list at least tells a cold visitor what the thing does. Mine might be nodding along with people who already agree while losing everyone who hasn't hit the wall yet.
So roast it. Is opening with what's wrong with the category an edge, or a way to lose the 80% who haven't felt the pain? Link's in the first comment.
The question I actually want answered: if you've ever led your landing with a differentiator instead of a feature list, did it work, or did you quietly switch back?
w/ no customers yet the headline is unfalsifiable tho. i'd take the two versions to 5 eu saas founders and watch which one they read twice
You've diagnosed this more sharply than most people could, so let me push on the part your own analysis half-solves. You're framing it as "problem-first vs feature-first," but that's not the real fork. The real fork is whether your buyer arrives pain-aware, and for your specific product, they mostly do.
Nobody googles affiliate tracking for EU SaaS cold. They arrive because their current tool broke: attribution went weird in Safari, legal flagged the banner, numbers stopped reconciling. By the time someone's shopping your category, they've usually already hit the wall. Your worry ("losing the 80% who haven't felt the pain") assumes a cold top-of-funnel visitor, but a niche B2B tool like this rarely gets those. The person on your page is more qualified than a generic SaaS visitor, so problem-first isn't as risky here as it'd be for a horizontal product.
But your instinct isn't wrong, it's aimed at the wrong fix. The issue isn't problem-first vs feature-first. It's that "no cookie banner" states an absence, and absences don't sell. Convert the absence into a gain they feel: "no cookie banner" is a negative, "track every affiliate sale Safari and ad blockers currently hide from you" is the same fact as recovered revenue. Lead with the problem, but frame the payoff as something they get, not something they avoid. "You're losing money right now and can't see it" beats "you don't need a consent banner."
On your actual question: leading with a differentiator works when it maps to felt pain, and quietly fails when it's a cleverness the buyer doesn't yet value. Yours maps to real pain for the qualified visitor. Keep problem-first, just make the absence concrete and money-shaped.
This absence-into-gain reframing is what I spend my time on, I'm part of the team building Hivemind, an AI strategy copilot. If you want to pressure-test the headline variants: https://hivemind.myosin.xyz. Either way, your structure is right, it's the framing of the difference that needs work.
The pain-aware split holds for switchers, and the money-shaped reframe is the direction the headline rework is taking. But the visitor your model leaves out is the one we keep meeting: the founder who never launched a programme at all because legal, or their own GDPR anxiety, said no. "Recover the sales Safari hides" doesn't land there, because there's no affiliate revenue to recover yet; for them the absence sells as permission, run the programme without the audit, rather than as recovery. So the page likely needs both shapes: recovery for the switcher, permission for the first-timer. Credit where due, absence-into-gain is the most useful line this thread has produced.
You're right and I under-modeled that segment. "Permission, not recovery" is the sharper frame, the never-launcher doesn't have revenue to recover, they have a programme they're too scared to start. Different job entirely.
Which surfaces something bigger than a headline: those two segments might be two funnels, not two lines on one page. They arrive from different searches, feel different pain, need different proof. A switcher wants "attribution that doesn't break." A never-launcher wants "compliant by design, legal will approve this." One hero serving both usually means a muddy compromise. Cleaner play: segment at the top ("already running a programme?" vs "haven't launched because of GDPR?") and route each to its own shaped message.
The never-launcher might be your better wedge, actually. Switchers have a working-ish tool, so switching is friction. The blocked founder has zero solution and acute anxiety, hotter and less contested, and "we make legal say yes" is sharper than "we track better." Test which converts before assuming the page must serve both equally.
Which do you meet more, switchers or never-launched?
Never-launched, by a wide margin: most founders we talk to shelved the idea at the legal step, so "permission" is the conversation we keep having. But there's a wrinkle in the wedge logic. The never-launcher's pain is hot and deadline-free; nothing breaks for them next month if they keep not launching, so the anxiety doesn't convert on its own. The switcher's pain is duller but arrives with a renewal date or a broken dashboard forcing a decision.
So my current read: never-launched is the bigger pool and the better content wedge, switchers are the faster close. Your "already running / haven't launched" split at the top is the cheap test of the two-funnel theory, two routed questions before any rebuild, and that's the version I'll try.
It depends on the goal of the landing page. Starting with what you don’t do can sometimes build trust by setting clear expectations, but the first message should usually focus on the value you provide and the problem you solve. What made you decide to lead with what you don’t do instead of the main benefit?
Two reasons, one principled and one forced. The product is basically defined by an absence, no cookie banner, no consent step, so "what it doesn't do" is the main benefit for the people who feel that pain. With no customers yet, I've also got no "trusted by X" proof to lead with instead.
That said, you and a couple of others in this thread have talked me into it: the absence needs a positive bridge right after, naming the cost of the thing removed (lost attribution, consent friction) before the reader has to care that it's gone. That rework's happening. The failure mode you're pointing at is real. Lead with the absence and you only land people who already feel the pain.
Landing that leads with what you don’t do can work if the reader is already in-market.
Quick check: are you also hunting Reddit/forum threads where buyers describe the pain, or is distribution mostly the page + ads?
(If Reddit is in the mix, I built a daily scored digest for that — happy to share a sample.)
Honestly it's mostly the third thing: showing up where the pain already gets described, which for us is threads like this one. Ads and the page are secondary, partly by necessity. Barely anyone searches "cookieless affiliate tracking", so almost no one arrives in-market via a query.
That's the deeper version of your point. For a category this new the page can't wait for in-market readers, it has to manufacture the in-market moment by naming a pain people haven't filed under a product category yet. Which loops straight back to the invisible-loss thing: they're not searching because they don't know they're losing anything.
The scored-digest idea is a smart wedge for exactly that, since surfacing the threads where the pain shows up is half the work. Where I've landed for now: the page's job might be less "convert the in-market visitor" and more "be the thing someone forwards to a founder who just got burned." Have you seen differentiator-led pages win as share-forwards rather than as search landing pages?
Yes — for invisible-loss categories I’ve seen differentiator-led pages win more as share-forwards than as search landings. Someone gets burned → pastes your page in a Slack/IH thread → that’s the in-market moment.
Same loop I’m testing with ThreadScout: surface the thread where the pain is already named, then the page is what gets forwarded.
If you’re actively hunting those cookieless/affiliate threads (not only writing about the motion), happy to map a quick scored sample. If not — all good, strong framing either way.
Yeah, that's the loop exactly. The forward is the in-market moment, and the thread is where you earn the forward. We do the hunting by hand right now, which is slow, but it keeps me reading the actual language people use, and that language is where half my copy comes from. When it stops scaling I'll want something like ThreadScout, so I'll keep it in mind. Appreciate the back-and-forth, it genuinely sharpened how I'm thinking about the top of the page.
Makes sense — while the hunt is still teaching you the language, keeping it manual is the right call.
Whenever reading threads stops being leverage and starts being the bottleneck, ping me. Founder rate is $19 first month if you want to try then.
Glad the back-and-forth helped on the page.
I would not switch all the way back to a generic feature list. The negative framing is useful, but it needs a positive bridge immediately after it.
Right now "not a compliance audit" speaks to people who already know the pain. For colder visitors I would make the first screen answer: who this is for, what gets fixed, and why the absence matters.
Possible shape:
Headline: Run an EU-friendly referral program without cookie banners.
Subhead: First-party, server-side attribution for SaaS teams that need affiliate tracking to survive Safari, ad blockers, and consent friction.
Then the "three things every affiliate stack gets wrong" section becomes proof, not the first explanation.
Differentiator-led pages work best when the differentiator is tied to a cost: lost attribution, lower conversion, compliance work, payout disputes, etc. If the page says "no banner" before it says "recover attribution and avoid consent friction," the absence feels abstract. If it names the business damage first, the absence becomes valuable.
This is the most useful version of that critique, thanks. The bridge line is the bit that's missing, and you're right that "not a compliance audit" only lands for someone who's already felt it.
The wrinkle I keep hitting with "name the damage first": the damage is usually invisible to the buyer. A founder losing up to a third of their affiliate attribution to Safari and ad blockers doesn't feel it, because the tool that failed to capture those clicks never reports what it missed, so the dashboard looks complete. "Recover attribution" reads as abstract as "no banner" until they've seen a number they couldn't get any other way. The hard copy problem isn't naming the cost, it's making an invisible loss feel real to someone who thinks their current numbers are fine.
Taking the bridge point though. The top jumping straight to the absence, with no "here's the damage, here's who it's for" step, is the actual gap. Going to rework that section around cost first, absence second.
When you've led with a cost the visitor can't see yet, what made it land: a benchmark stat, a "you're probably losing X" line, or letting them self-diagnose?
Here's the page, be brutal: https://selgeo.com — it's the "three things every affiliate stack gets wrong" block near the top I'm least sure about.