On Wednesday morning at 9:47, the office was full. Expectations were high. The mood was confident.
The web agency had just presented the finished site.
The hero text sounded convincing. It had been taken directly from the company brochure and shaped to match the brand guidelines.
The CEO nodded.
The marketing manager smiled.
Someone said it out loud:
“This finally feels like us.”
Everyone was pleased with the result.
The atmosphere stayed high, and to mark the launch, sparkling wine was poured. 🥂
A month later, analytics revealed something less celebratory.
Bounce rate: 87%. 😐
Then the meetings began.
“Maybe the headline is too long?”
“What if we change the color?”
“Should we add a video?”
A working group was formed.
Dozens of new versions were written.
They were reviewed, discussed, voted on, softened into compromise.
Eventually the shared message took shape.
A new launch.
A new measurement.
Bounce rate: 84%. 😞
Three percent better.
The communications team said nothing.
Sound familiar?
I’m not surprised.
I’ve seen this cycle many times — especially in Finnish companies, where decisions are often made by consensus and the hero text slowly turns into an internal compromise.
The problem is not that the text hasn’t been refined enough.
The problem is that it has been refined for the wrong audience.
Companies write homepage copy for themselves.
Not for the person seeing it for the first time.
The problem is not the text
It is the way the text is being approached.
Most teams try to solve this by writing more versions.
“Let’s try another headline.”
“What if we change the wording?”
“Should we add an adjective?”
But a new version does not repair a broken structure.
You do not solve this with:
❌ a new headline
❌ a new color
❌ a new font
❌ “better copy”
You need something else.
Structure.
I’ve seen teams spend weeks A/B testing two headlines.
Both weak.
But because one performs 3% better, it becomes the winner.
And then everyone celebrates a data-driven decision.
Even though the real answer should have been:
“Both of these are bad. Start again.”
But that is difficult to say out loud when someone already spent three weeks on it.
A structure that works psychologically
A hero text is not a creative exercise.
It is not a vision statement.
It is not an identity description.
It is a psychological guidance system that moves the reader:
→ from recognizing a problem
→ to understanding their role
→ to seeing a path toward resolution
⏰ In five seconds.
This article explains how that works.
Not only in theory.
I took three companies:
→ Slack
→ Netflix
Three different industries.
Three different products.
Three different audiences.
But when I broke their hero texts apart…
The same structure appeared.
The same psychological anatomy.
The same order.
👉 Not by accident.
Because human attention works the same way whether someone is buying consulting, software, or entertainment.
This article shows that structure.
What every functioning hero needs to contain.
Why.
And in what order.
⚠️ One warning:
A strong hero usually requires giving up the way your company is used to speaking about itself.
Because none of these three companies begin by describing themselves.
They begin by addressing the customer.
That is the difference between an 87% bounce rate and a page that actually holds attention.
The good news:
The structure can be broken down
Copied.
Applied to your own context.
“But we don’t solve a problem. We sell entertainment.”
One of my favorite arguments.
“We don’t have a problem. We offer opportunity.”
Fine.
But your customer does not wake up thinking:
“Great. Another day full of opportunity.”
They wake up thinking:
“I’m bored.”
“I don’t want to search.”
“Why is everything difficult again?”
And if your page does not meet that state, they leave.
Your opportunity may be inspiring.
But inspiration rarely creates immediate action.
A problem does.
Naming the problem well:
Corporate Rebels
A Dutch consulting company helping organizations build more self-managed ways of working.
They do not begin with:
“We modernize workplace culture.”
“We help organizations grow.”
They begin with:
Work is broken.
Two words.
No ambiguity.
Everyone understands immediately what is being pointed at.
This is where most companies fail:
They try to say too much in one sentence.
“ We help companies improve efficiency, culture, agility, and growth.” 🐢
System 1 does not process lists.
It processes one clear signal.
That is why Corporate Rebels chose one thing:
Work is broken.
Not five things.
Not three.
One.
Test: can your problem be verified in ordinary life?
A good problem is something the customer can immediately check against their own reality.
Try this:
Read your hero text out loud.
Then ask:
“Can the customer nod at this instantly?”
If the answer is:
“Well… you need to think a little about what this means…”
then it is not a real problem statement.
It is internal language.
Example:
❌ “We modernize internal communication.”
→ Customer: “Alright… what does that actually mean?”
✅ “Your team’s messages disappear into email.”
→ Customer: “Yes. Exactly.”
When the problem is testable, it feels real.
Not like brand language.
How do you know it works?
A well-named problem creates three immediate effects:
1. The customer nods internally
“This is true.”
2. System 1 understands the statement in a second
No explanation needed.
3. The customer becomes willing to hear the solution
Because you recognized their situation.
But.
A problem alone is not enough.
If you only describe what is broken, the reader may still leave after agreeing with you.
One more element is needed.
Next:
how you give the reader a role.
Step 2: Give the reader a role
You have named the problem.
The reader nods:
“Yes. This is true.”
System 1 is active.
But something is still missing.
This is where many hero texts fail:
⚠️ The reader understands the problem, but has no idea what to do with it.
The hero becomes a statement.
And statements do not hold attention.
Once the problem has been named, the next task is simple:
Tell the reader what they can do.
Not what you do.
Not who you are.
Ask instead:
What is their place in this story?
Why this matters
Two reasons.
1. People decide through their own role
If no role is visible, the text remains an internal company statement.
The reader stays outside it.
And outsiders leave.
2. A role shifts attention away from the company
It moves attention toward the customer’s motion.
And motion is what keeps people on a page.
What a role actually means
A role is usually one short line — an invitation, direction, or position the reader can immediately recognize:
→ Join
→ Start here
→ Take the next step
→ Find the answer
A role is not passive.
It places the reader where they feel like an actor, not an observer.
Example:
Corporate Rebels
The problem was:
Work is broken.
The role becomes:
Join the rebels fixing it.
Two words carry the movement:
Join the rebels.
Simple.
Physical.
Action-oriented.
Without that second line, the original hero would remain only a statement:
“Work is broken.”
“Alright. Then what?”
The role turns it into movement:
Work is broken. Come help fix it.
Example:
Slack
Slack does not say:
“We modernize workplace communication.”
It says:
Slack is where work happens.
This is not a direct instruction.
But the role is still built in:
→ If you want work to happen in one place
→ come here
→ start here
A role does not always need an imperative like “Join”, “Start”, or “Try”.
This is the interesting paradox:
The less directly you command, the stronger the effect often becomes.
“Join now” feels forced.
“This is where work happens” feels believable.
Why?
Because one sounds like selling.
The other sounds like reality.
And people dislike being sold to.
But they respond well to statements that confirm something they already suspect.
Example:
Netflix
See what’s next.
This line points directly to your action, not to the service itself.
→ You watch
→ You decide
→ You move forward
The role is clear:
Come in and see what comes next.
Why role matters so much
Without a role, three things usually happen.
1. The reader does not know what to do
A passive reader leaves.
An active reader stays.
2. The text becomes the company talking about itself
A brand-centered hero often kills movement.
3. The problem never turns into a solution
The story stops halfway.
A good hero needs motion.
Because motion keeps attention alive.
How to write the role in practice
Use one of these three structures.
1. Direct instruction
→ Join
→ Start here
→ Take one step
→ Try it free
2. Promise of movement
→ See what happens next
→ Find the answer
→ Try what works
3. Implicit role
→ Work happens faster in Slack
→ See the next story, the next feeling, the next episode
Test: is the role clear enough?
Try one simple test:
Remove the company name.
Does the sentence still point toward the reader?
If not, the role is missing.
Example:
❌ “We are a leading player in the industry.”
→ Remove the company name → the sentence means nothing to the reader
✅ “Join the people fixing it.”
→ Remove the company name → the sentence still works
How do you know it works?
When the role is working:
→ the reader recognizes themselves in the text
→ they understand what they are expected to do
→ they feel placed inside the story
Most importantly:
The hero stops describing the company.
It starts describing customer movement.
Step 3: Say what you actually do
(Use concrete verbs.)
The problem has been named.
A role has been given.
The reader now understands:
This concerns me. I can do something here.
But one question remains:
What do you actually do?
This is where many hero texts collapse.
Because this is usually where phrases appear like:
❌ “We help you succeed”
❌ “We support growth”
❌ “We are pioneers”
❌ “We transform thinking”
❌ “We enable success”
❌ “We are here for you”
None of these explain anything.
They are internal company language.
Not useful customer information.
Take this sentence:
“We are here for you.”
What does that mean in real life?
That you exist?
That you acknowledge the customer is human?
⚔️ This is corporate language at its most durable form.
A sentence that sounds warm but contains no usable information.
A sentence that suggests care while describing nothing.
If someone says this in a meeting, ask:
“Remove that sentence. What remains?”
Usually:
Nothing.
Say what you actually do
No vision language.
No abstract adjectives.
No identity phrases.
Describe actions that change the customer’s situation.
What makes a verb concrete?
A concrete verb describes an observable action the customer understands immediately.
It creates a mental image of something real happening.
No brand language.
Just visible action.
For example:
→ build
→ fix
→ speed up
→ clarify
→ simplify
→ remove
→ automate
→ make visible
→ turn data into decisions
When the verb removes friction, the text starts to live.
Example:
Corporate Rebels
We build self-managed organizations that crush bureaucracy.
Two concrete verbs carry the sentence:
→ build
→ crush
The customer can immediately picture what happens.
An organization is built.
Bureaucracy is reduced.
Nothing vague.
Nothing decorative.
💪 System 1 understands the action immediately.
Example:
Slack
Slack does not say:
“We modernize communication.”
Instead, it has long repeated one simple statement:
Slack is where work happens.
The concrete action behind that line is still obvious:
Slack brings work into one place and makes it faster.
Not “enhances.”
Not “optimizes.”
Not “creates new possibilities.”
Simply:
speeds up.
One action.
One promise.
One concrete change in everyday work.
The reader understands immediately:
→ work is scattered elsewhere
→ in Slack it is gathered
→ when work is gathered, movement becomes faster
System 1 needs nothing more.
Example: Quantum E-Commerce Architects Oy
Avoid:
❌ “We improve your ecommerce success through innovative solutions.”
Say instead:
✅ We speed up buying
✅ We remove friction at checkout
✅ We build stores designed for conversion
Each of these describes a physical change.
A note: Quantum E-Commerce Architects is fictional. If such a company exists, this is not aimed at you. At least not intentionally. 😅
Why concrete verbs matter
1. They bypass abstraction
System 1 does not understand “leadership” or “innovation” quickly.
It understands speeding something up.
2. They explain what the customer gets
Not what the company believes.
Not what the company wants to sound like.
3. They reduce cognitive friction
The customer does not need to ask:
“What does this actually mean?”
A concrete verb is a gift to the reader.
It saves mental effort.
The difference between weak and strong hero copy
Weak copy forces the customer to interpret.
Strong copy forces the customer to see.
“We enable growth.”
→ What does that mean?
“We shorten the sales cycle by 40%.”
→ Now I understand.
Interpretation is work.
Seeing is reaction.
Your customer did not come to your site to work.
Three practical structures that work
1. Concrete verb + concrete object
→ We clarify complex services
→ We speed up your team’s decisions
2. Concrete verb + friction removal
→ We remove checkout bottlenecks
→ We cut the sales cycle in half
3. Concrete verb + decisive benefit
→ We build websites that guide sales — not confuse buyers
→ We automate messages so you do not have to
When words describe action, the text begins to breathe.
Test: is the verb concrete?
Ask yourself:
Can this action be seen, heard, or recognized in ordinary life?
If not, the verb is too abstract.
Example:
❌ “We enable growth.”
Too abstract.
✅ “We shorten the sales cycle by 40%.”
Concrete. Measurable. Visible.
A concrete verb leaves a trace in memory.
How do you know it works?
When concrete actions are in place:
→ the customer understands what you do without interpretation
→ the energy moves from problem to solution
→ System 1 stays engaged while System 2 becomes curious
→ the text stops sounding like brand language and starts sounding useful
At this point, the first three parts of your hero are already working:
Problem
Role
Concrete action
Next comes the part that separates an average hero from a strong one.
Step 4: What job are you hired to do?
(Jobs To Be Done)
The problem has been named.
A role is visible.
Concrete actions are clear.
But one thing is still missing before the hero truly works:
Why should the customer choose you, in this moment, now?
Not because of who you are.
Not because of your vision.
Not because you call yourself a pioneer.
But because the customer hires you to do a specific job in their life.
That is the core of Jobs to be done thinking.
Without it, the hero remains abstract.
People do not buy products
They hire them to do work.
Clayton Christensen once summarized it like this:
People do not buy a milkshake. 🥤
They hire a milkshake to make a commute less boring.
The product is secondary.
The job is primary.
Once you understand the job, you understand:
→ why the customer opens your page
→ what moment your service fits into
→ what needs to change in the customer’s situation
→ what the first line of the hero must promise
That changes everything.
What the job looks like in real life
The job is not:
❌ learning more about your service
❌ exploring your company
❌ admiring your identity
❌ reading your vision statement
The job is always concrete.
Usually one of these:
1. Remove friction
“I don’t want to search. Show me the path.”
2. Make something faster
“I want this done now.”
3. Create certainty
“I don’t want to get this wrong.”
4. Create a feeling
“I want relief.”
“I’m bored. I want something now.”
5. Move responsibility away
“Handle this for me.”
The job belongs to the customer’s day.
Not to your identity.
Where most companies get lost
They ask:
“What do we want to be?”
When they should ask:
“What does the customer want us to do?”
These are not the same question.
You may want to sound like an innovative partner.
The customer may simply want someone to take the spreadsheet off their desk.
Which one wins?
The one that improves the customer’s day.
Not the one that solves the company’s identity tension.
Jobs To Be Done is not theory in practice.
It is ordinary behavior:
Nobody buys a product.
Everyone hires relief for a moment.
Example:
Corporate Rebels
Hero:
Work is broken.
Join the rebels fixing it.
What job are they hired for?
Not productivity consulting.
Not workshop slides.
But:
I need an alternative to bureaucracy.
That is the moment the contact begins.
Example:
Slack
The job behind Slack is equally clear:
I need one place where work is not scattered and slow.
They express it like this:
Slack is where work happens.
No identity language.
No vision statement.
No “leading platform.”
One job.
One promise.
Slack gathers work into one place and makes it faster.
It does not “optimize.”
It does not “modernize.”
It speeds things up.
One verb.
One visible change.
One immediate benefit.
Example:
Netflix
What job is Netflix hired for?
Not:
“Producing the world’s best entertainment.”
But:
I want something to watch now — without effort.
Hero:
See what’s next.
It says exactly what the user needs in that moment.
How to find your own JTBD
Try this:
Ask yourself:
In what situation does the customer hire us?
→ when stuck?
→ when uncertain?
→ when rushed?
→ when irritated?
→ when bored?
→ when needing relief now?
Then continue:
What part of their day do we shift into a better state?
Write it like this:
The customer hires us to __________ so they can __________
Examples:
→ The customer hires us to clarify a complex service so they stop losing customers to unclear messaging.
→ The customer hires us to shorten the buying process so purchases do not stall.
→ The customer hires us to keep boredom away so they get a moment of relief.
Once the job becomes clear, the tone of the hero changes immediately.
How do you know it works?
Three signs.
1. The hero stops talking about you
The first line reflects the customer’s situation.
2. Actions start to feel logical
Words like build, remove, and clarify suddenly find the right target.
3. The CTA becomes obvious
When the job is clear, the CTA becomes clearer too:
→ Start now
→ See an example
→ Remove friction
→ Download the guide
→ Try it yourself
The job guides the whole path.
One short test
If you removed your service completely and left only the job behind,
would the customer still understand why they are here?
If yes, the JTBD is probably right.
If not, the hero is still telling your story, not theirs.
Now you have:
the problem
the role
the action
the job
That means the hero is halfway complete.
Next:
how to write all of this in language that System 1 understands immediately.
Step 5: Write in the language of System 1
The problem is clear.
A role is visible.
The action is understood.
The job is defined.
But one question still decides everything:
How do you say all of this so a person understands it in a second?
The answer:
Write in the language of System 1.
What does System 1 actually respond to?
It does not analyze.
It does not compare.
It does not weigh abstractions.
It reacts only to what feels:
→ physical
→ concrete
→ short
→ sensory
→ immediately recognizable
All strong hero texts speak to System 1.
Not to System 2.
What System 1 language looks like in practice
1. Short sentences
If you can read the sentence in one breath, that is usually a good sign.
→ Work is broken
→ See what’s next
→ Work happens faster in Slack
System 1 does not like heavy sentence structures.
2. Remove adjectives. Use verbs.
Adjectives often feel useful because they make text sound polished.
But they usually add nothing.
❌ innovative
❌ radical
❌ new
❌ leading
These belong to System 2 language.
They slow interpretation.
Compare:
“An innovative solution”
vs
“We automate invoicing”
Which one shows what happens?
Which one helps the customer understand?
An adjective describes how you feel about yourself.
A verb describes what changes for the customer.
And nobody pays for how you feel about yourself.
Remove adjectives.
Add verbs.
Then look again.
If nothing remains, there may have been no message there to begin with.
3. Say one thing at a time
System 1 does not hold lists well.
It wants one signal.
Example:
❌ “We help companies improve efficiency, growth, culture, and agility.”
Too much.
✅ “Work happens faster in Slack.”
One signal.
One promise.
4. Leave space for completion
A strong hero does not explain everything.
It gives direction and leaves a small open gap.
See what’s next.
Why does this work?
→ it does not explain what appears next
→ it signals movement
→ it leaves a gap the brain wants to close
This is one reason attention stays active:
the mind wants completion.
Before and after
Before (System 2):
“We help organizations develop customer-oriented services and strengthen strategic competitiveness.”
What goes wrong here?
→ too long
→ abstract
→ adjective-heavy
→ no visible action
→ no movement
After (System 1):
We clarify your service so customers understand it immediately.
Why does this work?
→ one message
→ one action: clarify
→ one benefit: understanding
→ one immediate mental decision
Test: are you writing in System 1 language?
Ask yourself three things:
1. Would I understand this in a glance?
If not, it is too complex.
2. Can I picture the action?
If not, it is too abstract.
3. Can one word be removed without loss?
If yes, it is not tight enough.
A strong hero is not a poem.
And not a company description.
It is a signal that must land fast.
At this point, five layers are already in place
Problem
Role
Concrete action
JTBD
System 1 language
You may now think:
“Fine. I understand the parts. But how do they become one hero?”
This is where theory becomes practice.
And where many teams fail.
Because they assume a hero is:
→ a headline
→ plus a subheading
→ maybe one supporting line
→ and a button
It is not.
A hero is a story.
It just does not look like one because it is so short.
But when the structure is right, the brain still experiences it as movement.
And movement creates attention.
Attention creates conversion.
Step 6: Build a micro-story
You now have five essential elements:
→ a named problem
→ a visible role
→ a concrete action
→ a clear job
→ System 1 language
But one more element is needed before the whole thing feels clear:
A small story.
Not paragraphs.
Not plot.
Not brand storytelling.
Only three lines are needed to create logical movement in the reader’s mind:
Something is wrong
Someone addresses it
The reader is invited into that movement
That is a micro-story.
It does not look like a story.
But it feels like one.
Why a micro-story works
Because the brain does not react strongly to information alone.
It reacts to change.
A story is change:
→ from a problem
→ toward a solution
→ with the reader placed inside that movement
Without this, a hero remains only a statement:
“X is broken.”
Fine.
But static.
A story adds movement:
X is broken. We fix it. Come in.
That movement is what keeps attention on the page.
Example:
Corporate Rebels
Work is broken.
→ Problem. Immediately recognizable.
Join the rebels fixing it.
→ Role. The reader is invited in.
We build self-managed organizations that crush bureaucracy.
→ Action. Concrete change.
Three lines.
A complete story.
Time required to absorb it: about two seconds.
Example:
Slack
Slack does something similar with fewer words:
Slack is where work happens.
→ Problem and solution compressed into one line: work is scattered elsewhere, gathered here.
Try for free.
→ Role and immediate action.
The hidden micro-story underneath is simple:
scattered → gathered → begin
Example:
Netflix
Netflix contains a hidden story too:
See what’s next.
→ Problem: you do not know what to watch.
Watch anywhere.
→ Solution: access without limitation.
Cancel anytime.
→ Friction removed: no commitment.
This is a complete situation resolving itself quickly.
How to build your own micro-story
Use this three-part frame:
1. Problem — one sentence
Something is slow, unclear, broken, frustrating.
2. Role — one sentence
Start here. Join in. See the next step.
3. Action — one sentence
We clarify.
We speed up.
We remove friction.
Example:
Your customers hesitate.
Remove the friction.
We clarify the service so they understand immediately.
That is already a story.
Small enough for System 1 to process in a glance.
Test: does the micro-story hold?
Ask yourself:
1. Does the first sentence describe the reader’s situation?
If not, the problem is too vague.
2. Does the second sentence place the reader inside movement?
If not, the role is missing.
3. Does the third sentence explain what actually changes?
If not, the action is too abstract.
4. Does the rhythm feel right when read aloud in sequence?
If not, the story needs tightening.
If the answers are yes, the story carries.
If something is missing, the hero usually feels flat.
The micro-story is the hidden engine of the hero
When this three-part structure works, the hero stops feeling like isolated text.
It becomes a psychological guidance system moving the reader:
→ from unconscious recognition
→ to conscious role
→ toward resolution
At that point, one element still remains:
time.
A way to show that change happens not someday, but now.
That is what makes a hero feel active instead of static.
Step 8: The CTA is the next scene in the story
By now, movement has already formed in the reader’s mind:
→ this concerns me
→ this is true
→ this can be solved
→ this can be solved now
But if the story stops here, momentum disappears.
You need a CTA.
Not because every page needs a button.
But because the story must continue.
A CTA is not an isolated action.
It is not just a UI element.
It is not a marketing obligation.
A CTA is the next scene in the same story your hero has already started.
If it works, the reader does not feel they are switching context.
They feel they are continuing the same movement.
Why CTAs often fail
Because they are written separately from everything that came before:
→ the problem
→ the role
→ the action
→ the JTBD
→ System 1 logic
→ the rhythm of the micro-story
→ the shortened timeline
The result often looks like this:
Work is broken. Join the rebels fixing it.
…and below it:
Contact us
Why would anyone click that?
The CTA has broken the story.
A strong CTA continues the hero like the final line of the same paragraph:
Work is broken.
Join the rebels fixing it.
Start here.
That rhythm holds.
No interruption.
No drop.
No new subject.
The real job of a CTA
A CTA is not primarily there to:
sell
collect leads
push people into the right funnel
Its first job is simpler:
keep the reader inside the story a little longer.
Conversion happens only after that.
A CTA should emerge from the hero, not from design preference
This is where many teams make the same mistake:
“Let’s use the same CTA everywhere. It looks cleaner.”
The problem is that consistency is often misunderstood.
For designers and managers, consistency easily becomes a virtue in itself.
Sometimes even a fixation:
“The CTA must always stay the same.”
“Every page should feel identical.”
“Don’t change the button — it breaks the system.”
But here is the trap:
👉 consistency does not automatically create clarity
👉 and sometimes consistency works directly against conversion
Sales needs coherence.
Not uniformity.
Coherence means the content supports a decision.
Uniformity means the elements look similar.
Those are not the same thing.
I see this constantly in projects:
The CTA stays unchanged for visual reasons, even when it breaks the psychological logic of the hero.
The intention is good.
The effect is weak.
The CTA must come from the structure of the hero
Ask five things:
1. What was the problem?
The CTA should offer the first step toward resolving it.
2. What role was given to the reader?
The CTA must continue that role, not replace it.
3. What action was promised?
The CTA should move toward that action.
4. What was the JTBD?
The CTA must serve that same job.
5. What was the timeline?
The CTA cannot push the action into an undefined future.
Example:
Work is broken.
Join the rebels fixing it.
Not someday. Today.
A strong CTA here would be:
→ Join us
→ Start here
→ See how we fix it
A weak CTA would be:
→ Read more
→ Learn about our services
→ Contact sales
One continues the story.
The other ends it.
Three CTA tests you can use immediately
1. Read the hero and CTA out loud together
Does it sound like one paragraph?
Good.
Does it sound like a jump?
Weak.
2. Remove the CTA
Does the hero suddenly feel unfinished?
Good.
If the hero feels complete without it, the CTA may be disconnected.
3. Compare verb energy
Hero: Remove friction.
CTA: Explore more options.
Those energies collide.
A CTA should continue the same verb.
The CTA is not a separate command
It is the story continuing in verb form.
And just when this starts to make sense, one more layer appears:
A CTA is rarely one button.
Usually it is two.
A primary action.
And a secondary action.
Each with a different role
Each carrying a different part of the same story.
Next:
why two CTAs often work better than one.
Step 9: The secondary CTA is often more important
Once the hero is clear and the timeline makes action feel immediate, many teams still make one final mistake:
They place only one CTA at the top of the page.
Usually something like:
→ Contact us
→ Start now
It feels logical.
But it is rarely the strongest way to move people forward.
Why?
Because readers are not equally ready to decide.
A primary CTA is for the person ready to act now.
A secondary CTA is for the person who is not there yet.
Both are necessary.
They do not compete.
They serve different moments of readiness.
What the primary CTA does
The primary CTA is the direct path toward conversion:
→ purchase
→ booking
→ demo
→ free trial
→ request
→ signup
Its role is simple:
offer a direct path for the person already close to deciding.
One requirement matters:
It must continue the hero without breaking its rhythm.
Examples:
→ Start now
→ Join us
→ Try for free
→ Start here
→ See how it works
A primary CTA speaks to System 1:
short
physical
active
It serves the visitor already near action.
But that group is small.
Roughly 1–5% of visitors are ready immediately.
The other 95–99% are not ready yet — but may still become customers.
A single CTA serves only the first group.
A secondary CTA serves the rest.
What the secondary CTA does
A secondary CTA does not ask for conversion.
It offers a lower-friction next step.
Something that:
→ requires little commitment
→ carries low perceived risk
→ does not force identity-level decisions
It answers one quiet question:
“If I’m not ready yet, what can I do next?”
Examples:
→ See examples
→ Explore cases
→ Watch how it works
→ Watch a 2-minute demo
→ Download the guide
One important rule:
The secondary CTA must not overpower the primary one.
It must remain a real alternative, not a competing headline.
Why this structure works
People arrive with different levels of readiness.
1. Ready now
→ Primary CTA
2. Interested, but uncertain
→ Secondary CTA
Without the secondary option, many simply leave.
Not because they reject the offer.
Because no psychologically easy next step exists.
I once asked a client:
“How many visitors click your CTA?”
“About two percent.”
“And what do the other ninety-eight percent do?”
“They leave.”
Exactly.
Because no second path was offered.
People do not behave the way companies wish.
They behave in ways that feel comfortable to themselves.
If the only path feels too large, many choose the third option:
leave.
That is why the secondary CTA is not optional.
It is often what keeps most people inside the decision process.
A strong hero usually follows this pattern
Primary CTA: action now
Secondary CTA: understanding now
Together they make the page:
→ more inclusive
→ more flexible
→ psychologically easier
→ stronger in conversion
Choosing the two CTAs in practice
Use one simple rule:
Primary CTA solves the main job.
Secondary CTA solves hesitation.
Examples
B2B service
Primary: Book a 20-minute session
Secondary: See case examples
Ecommerce
Primary: Buy now
Secondary: Watch product video
Consulting
Primary: Start the project
Secondary: See how the process works
SaaS
Primary: Try for free
Secondary: Watch a 2-minute demo
Entertainment
Primary: Start watching
Secondary: Browse titles
This is not a design trick.
It is behavior.
Summary: the complete anatomy of a hero
A strong hero is not created by instinct.
And not by one clever sentence.
It is a clear psychological structure designed to do several things in seconds:
1. Name the problem
something the reader immediately recognizes
2. Give the reader a role
what they can do now
3. Show concrete action
real verbs, not internal language
4. Clarify the job to be done
why the customer hires you
5. Speak in System 1 language
short, direct, sensory
6. Build a micro-story
problem → movement → role
7. Shorten the timeline
change happens now
8. Lead into two CTAs
Primary: conversion
Secondary: low-friction continuation
When these elements are present, the hero stops:
explaining the company
describing identity
repeating vision
using marketing language
It starts doing one thing:
moving the reader forward.
And that is when a hero stops looking good —
and starts working.
A practical hero template
Use this directly.
1. Problem
What in the customer’s day is broken, slow, unclear, or frustrating?
2. Role
What words invite movement?
3. Action
What do you actually do? Use physical verbs.
4. JTBD
The customer hires us to ______ so they can ______
5. System 1 line
One short, physical sentence.
6. Micro-story
Problem → role → action
7. Timeline
How do you make the change feel immediate?
8. CTA pair
Primary CTA
Secondary CTA
Example
Problem
Your customers hesitate because complexity gets in the way.
Role
Remove the friction.
Action
We clarify the service, simplify the structure, and make the path visible.
JTBD
The customer hires us to make complexity understandable so their own customers do not leave.
System 1 line
Your service, made instantly clear.
Timeline
Not someday. Today.
Primary CTA
Start clarity work
Secondary CTA
See an example
Are there good Finnish examples too?
Yes.
Not many at the level of Corporate Rebels, but some strong ones exist.
Valco
“The best headphones you can afford.”
Why it works:
→ one obvious everyday tension
→ one visible value equation
→ no brand language
Varusteleka
“Buy it — you’ll need it anyway.”
Why it works:
→ one direct action
→ one concrete role
→ spoken language that strengthens the signal
Wolt
“Food and groceries delivered.”
Why it works:
→ one daily situation
→ one visible verb
→ no unnecessary language
A strong Finnish hero usually appears when a company dares to:
→ name one problem
→ speak from the customer’s day
→ use concrete verbs
→ remove adjective fog
Then the result often becomes surprisingly strong.
Closing
If you read this all the way through, you already know something many teams never stop to examine:
A hero is rarely weak because of writing alone.
It is weak because the thinking behind it remains unresolved.
Most teams keep adjusting words.
A different headline.
A shorter sentence.
A new visual emphasis.
But if the underlying logic is unclear, none of that changes much.
The bounce rate may move a little.
The confusion usually stays.
Because clarity does not come from polishing language.
It comes from deciding what deserves emphasis, what belongs first, and what should be left out.
That is slower work.
Less visible.
Often harder than writing itself.
But it is also the point where a homepage starts behaving differently.
Once the structure is clear, words stop competing with each other.
The page begins to carry intent.
And when intent becomes visible, visitors do not need persuasion in the same way.
They understand where they are.
Why it matters.
What happens next.
That is usually where a hero starts working.
And once that happens, the rest of the page becomes easier to solve too.
If your own hero still feels uncertain, the issue is often not style.
It is that the page is still trying to say several things at once.
That is where an outside view usually helps most:
not to add more language,
but to make the right signal visible.
A strong hero rarely makes noise.
It removes enough of it that the right thing becomes obvious.
