The 3-Sentence Framework for a Hero Message That Actually Converts

Most hero sections fail for one reason. They describe the product instead of the buyer's situation.

"AI-powered platform for enterprise workflow automation." The visitor reads this and thinks: does this fix my problem? The page has already lost them.

The 3-sentence framework is a tool for writing a hero message that matches what is already in the visitor's head. It takes ten minutes to apply and does not require touching your design.

Why Most Hero Sections Miss the Buyer Completely

When founders write copy, they write from the inside out. They know the product, so they describe the product. Features, capabilities, integrations.

Visitors arrive from the outside. They have a problem. They want to know if this product solves it. They are not ready to evaluate features until they have confirmed the product is relevant to them.

The gap between those two starting points is where most hero sections fail. The page is written in product language. The visitor is thinking in outcome language. The translation never happens, and they leave.

The 3-Sentence Framework: Desire, Doubt, Proof

The framework has three sentences. They map directly to how people make decisions.

Sentence 1 — They want: the outcome your buyer is chasing. Not the product category. The actual change they are trying to create in their work or business. Specific. Measurable if possible.

Sentence 2 — But they are worried: the single biggest hesitation standing between them and saying yes. Setup time, switching costs, internal adoption, getting charged by accident. Name the one that appears most often in your lost deals and customer calls.

Sentence 3 — So we: how you deliver the outcome while removing that specific worry. This is where your differentiator belongs. Not in a twelve-bullet feature list — in a single sentence that connects your capability directly to their hesitation.

A Working Example

Here is the framework applied to a CRM product.

They want: a sales pipeline that stays full without living in spreadsheets.

But they are worried: switching CRMs will be a migration nightmare and the team will not adopt it.

So we: sync your existing data in under an hour and build the workflow around how your team already works, so adoption is not a project.

Those three sentences contain everything the hero section needs: the outcome, the objection, and the proof. The headline speaks to sentence one. The subheadline addresses sentence two. The CTA and supporting copy deliver sentence three.

How to Write Your Three Sentences

Start with sentence two, not sentence one. The worry is the hardest to name and the most important to get right. Pull it from lost deal notes, support tickets, G2 reviews, or customer onboarding calls. What comes up repeatedly as the reason people hesitate? That is your sentence two.

Then write sentence one. The outcome should be specific enough that the right buyer reads it and thinks: yes, that is exactly what I am trying to do. If it is broad enough to apply to anyone, it will not resonate with the person you actually want.

Then write sentence three. Test it against sentence two directly. Does it neutralise the worry named in sentence two? If not, it is not specific enough. A sentence three that does not answer sentence two is a feature claim, not a proof.

Applying the Framework to Your Hero

The three sentences do not go on the page verbatim. They are inputs, not outputs. They give you the brief for every element in the hero section.

The headline comes from sentence one. Make it specific. Remove the product category language ("platform," "solution," "software"). Lead with what changes.

The subheadline comes from sentence two. Name the worry and dismiss it in one sentence. "No migration required. Works with your existing stack." is better than "Easy to use and integrates with everything."

The CTA comes from sentence three. Match it to the promise you just made. If you positioned fast setup, the CTA is "Get set up in 10 minutes," not "Get Started."

What This Framework Is NOT

It is not a shortcut for customer research. You cannot invent the three sentences from inside your own head. Sentence two in particular requires you to know what your buyers are actually worried about. The framework only works when the inputs are real.

It is not a rigid template. The sentences are diagnostic tools. Some hero sections express all three in a single headline. Others spread them across the headline, subheadline, and a trust signal. The structure of the page does not need to change. The clarity of the message does.

It is not a one-time fix. Your best buyer and their primary hesitation change as your market matures. Run the framework again every six months, or whenever you change your go-to-market focus.

Frequently Asked Questions

What is the 3-sentence framework for hero copy?
A messaging tool that structures a hero section around three inputs: the outcome the buyer wants, the hesitation stopping them from acting, and how the product delivers the outcome while removing the hesitation. The three sentences — They want, But they are worried, So we — map to the headline, subheadline, and CTA of the hero section.

How do I find the right "worry" for sentence two?
Review your lost deals, support tickets, G2 reviews, and customer onboarding calls. The hesitations that appear most frequently are the ones worth addressing above the fold. If you do not have that data yet, ask five recent customers: "What almost stopped you from signing up?" The answers will be consistent enough to act on.

How is this different from just writing benefit-led copy?
Benefit-led copy addresses what you get. This framework adds the layer of what is stopping you. Most visitors who leave a page were not unconvinced by the product — they were unconvinced that the risk of trying it was worth it. Addressing the hesitation directly is what separates copy that converts from copy that just describes.

Does the 3-sentence framework work for high-ticket or complex sales?
Yes, and it is especially effective there. In high-consideration sales, the hesitation is more specific and more powerful. Naming it precisely on the page signals that you understand the buyer's world in a way that generic benefit copy does not. The longer the sales cycle, the more important it is to address the worry early.

Can I use this framework for pages other than the homepage?
Yes. Every landing page that asks a visitor to do something has a hero section. Paid traffic landing pages, product pages, and campaign-specific pages all benefit from the same structure. The inputs change (different traffic sources bring visitors with different worries), but the framework applies to any page where the first thing a visitor sees needs to earn their continued attention.