I went from 32 signups/week to 0. One headline change.
I Lost a Full Week of Signups Because I Changed One Headline
I launched PostClaw 3 weeks ago.
Week 1: 8 users. Not bad for a fresh launch.
Week 2: 32 users. Okay, something's working.
Then my ego showed up.
I built PostClaw on top of OpenClaw, which was starting to get some attention. I thought I could take advantage of that and made the landing page focus on the technology instead of what the product actually does for users.
I changed the headline from "Publish on 13 platforms from one chat" to "Your own OpenClaw instance. For social media."
Look at that second headline again. It doesn't really say anything. Who cares about an "instance"? What is OpenClaw? Why would anyone want to sign up?
Week 3: 0 users. Zero. Not a slow week — literally nobody signed up.
For a whole week, I kept refreshing my dashboard, just like I joked about in my last post, and wondered what went wrong. The traffic was still there. People visited the page, but they left right away.
The old headline focused on the outcome: you have 13 platforms, and here's one chat to manage them all. It was simple and clear. Readers could easily imagine themselves using it.
The new headline focused on the technology. "Your own OpenClaw instance" doesn't mean anything to someone who just wants to post on LinkedIn and Twitter quickly. They don't care about the technical details. They care about what the product does for them.
So I switched back, but instead of using the original headline, I wrote one that focused even more on the outcome:
"Your social media. Done in 30 seconds."
8 signups that same night.
It wasn't 8 signups over a week. It was 8 that same night. The traffic and audience were the same, but the results changed completely just because of what the landing page said in the first few seconds.
Here's what I think happened
-
"Publish on 13 platforms from one chat" was good. It explained what the product does and helped me reach 40 users in two weeks.
-
"Your own OpenClaw instance" was bad. It talked about the technology, but nobody cared. I got zero users.
-
"Your social media. Done in 30 seconds" was better than both. It focused on the result. It didn't mention platforms or technology, just promised to save time: something that usually takes too long now takes only 30 seconds.
The lesson is simple, but I had to lose a week of signups to learn it: people don't care about what your product is built on. They care about what it does for them. The more specific the outcome, the better.
I still find myself wanting to talk about the technology because I'm proud of it. OpenClaw is impressive. The architecture is solid. The Telegram integration works well. But none of that should be on a landing page. The landing page has one purpose: to show someone how their life improves if they sign up.
Ignore the urge to explain the technology. People don't need to understand it. They need to see the outcome. Let the numbers guide you.
Great case study in how technical founders think vs how users think. We have the exact same instinct — "look at our cool tech" — and it always underperforms "here is the outcome you get."
I run into this with my own landing page copy constantly. The temptation to lead with "6 ML models scanning 34 sports" is strong. But nobody cares about the model count. They care about whether they make money.
The lesson I keep re-learning: headlines should answer "what do I get?" not "what did you build?"
Great write-up. The cleanest part is that traffic held while signups died — that usually means the leak is between first impression and first action.
If useful, here’s a quick way to test this in 24h without more copy churn:
You’ll usually find whether the next bottleneck is trust, clarity, or effort in one day.
If you want, I can run a fast 3-leak teardown (headline clarity, trust proof, CTA friction) and point to the single highest-impact fix first:
https://roastmysite.io/go.php?src=external_manual_ih_headline_zero_signup_usd_presell_hv
Literally rewrote my own homepage headline last night for the same reason. Switched to leading with the problem the audience has, not our story. Immediately felt more compelling. Your framing of technology vs outcome is spot on, but it goes deeper: even outcome headlines fail if they describe YOUR outcome instead of THEIR outcome. "Publish on 13 platforms" is your capability. "Done in 30 seconds" is their life getting easier. Subtle but massive. The constant traffic with zero signups is the cleanest test data you could ask for.
Painfully relatable. We all want to show off the engine. But users buy the destination, not the car. "30 seconds" works because it's a measurable promise, not a feature.
This hit close to home. I'm building IndicatoriTrading and my current headline is 'Find tools. Sell access. Stay private.' Reading your post made me realize 'Stay private' is exactly the same mistake you made. I'm describing a technical feature, not an outcome.
Nobody wakes up wanting privacy. They wake up wanting to monetize something they built without the risk of getting their code stolen.
Going to rethink this today. Thanks for the honest breakdown.
The traffic staying the same while signups hit zero is the real data point here. That's not a product problem — it's a messaging problem, and it's actually a relieving diagnosis when you catch it.
The technology vs outcome framing is something almost every builder gets wrong at least once. You're proud of how it's built, so that's what you talk about. But nobody buying a drill cares about the metallurgy.
Curious whether you A/B tested at all or just shipped the new headline cold. And what made you finally look at the headline as the culprit rather than blaming traffic quality or some other variable?