I was reviewing a tech company's website last week and everything looked great, clean design, solid product, decent copy.
But then I hit their CTA.
"Our battery lasts 12 hours."
That's it. That was the line they were using to get people to buy.
And honestly? I felt a little sad for them. Not because it was terrible writing. But because they were so close and they didn't even know it.
The Problem with Most CTAs Is Not What You Think
Most people assume a weak CTA is a writing problem. Fix the words, fix the results.
But it's a thinking problem.
The company that wrote "Our battery lasts 12 hours" wasn't being lazy. They were proud of that battery. They worked hard on it. Twelve hours is genuinely impressive. So, they put it front and center.
The mistake is that they were thinking about their product instead of their customer.
Because here is the truth, nobody wakes up in the morning thinking "I really need a 12-hour battery."
They wake up thinking "I have three back-to-back meetings today, a flight at 6pm, and I cannot deal with my laptop dying on me again."
That is the feeling your CTA needs to meet. Not the spec. The feeling.
Features Tell. Benefits Sell.
This is the oldest rule in copywriting and somehow still the most ignored one.
A feature is what your product does. A benefit is what your customer gets.
Here is the difference in practice:
Feature: "Our battery lasts 12 hours" Benefit: "Power through a full workday on a single charge"
Same product. Same battery. Completely different effect on the reader.
The first one makes them nod. The second one makes them feel something relief, confidence, freedom from that low battery panic we all know too well.
One more example to make it stick:
Feature: "Our desk adjusts from 28 to 48 inches" Benefit: "Sit, stand, and stay comfortable all day at the push of a button"
Nobody buys a desk for the numbers. They buy it because they are tired of back pain, tired of feeling stiff at 3pm, tired of not having control over their own comfort at work.
The benefit speaks to that. The feature does not.
The 3-Second Test
Here is a simple test I use on every CTA I write.
Read your CTA out loud. Then ask yourself, “So what?”
"Our battery lasts 12 hours." So what? "Our desk adjusts from 28 to 48 inches. “So what?” Our software has 200+ integrations." So what?
If you can ask "so what?" and your CTA does not already answer it, rewrite it.
"Power through a full workday on a single charge." So what? You never run out of battery during your most important moments. Done. That CTA passes.
Keep asking "so what?" until the answer is obvious. That is when you have a CTA worth publishing.
One More Rewrite, This Time for SaaS
I work mostly in SaaS and AI, so let me give you one from that world.
Feature: "Our software has 200+ integrations" Benefit: "Connect every tool your team already uses, no tab switching, no wasted time"
200 integrations are impressive to an engineer. But to a busy operations manager who just wants things to work, it means nothing. What they care about is whether this new tool is going to create more headaches or fewer. The benefit answers that directly.
The Bottom Line
Your CTA is not a spec sheet. It is a promise.
It is the moment where your customer decides, does this brand get me, or are they just talking about themselves?
Write it like you understand their day. Their frustration. The small wins they are chasing.
Because when you do that, you are not just writing better copies.
You are building trust before the sale even happens.
And that is what separates copy that converts from copy that just sits there.
If you find this useful, follow me for more breakdowns on copywriting for SaaS, AI, and tech brands. I post practical tips every week, no fluff, just things that work.
Top comments (0)