Most AI homepages fail in the same place: the first screen. A visitor lands, reads a headline about the future, and cannot tell what the product does or whether it is for them. We saw the same failure three times in a row while redesigning hero sections for Engati, Intelmatix and Avaamo as Kraftbase concepts.
Three AI company homepages, seven repeated mistakes. We reviewed each page on October 29, 2026, fixed each mistake in a concept rewrite and kept the method so you can run it on your own hero, with a five minute test at the end. None of these companies is a Kraftbase client, and we are not associated with them. The rewrites are our concepts, not their copy.
Key takeaways
The same seven mistakes appeared across three different AI products, which suggests they are habits of the category, not one company’s slip.
Every fix follows the Hero Stack: Outcome, Mechanism, Proof, Product, in that order.
The mistake that costs the most is skipping the mechanism, because the buyer never learns what the AI actually does.
All captures are dated. Live homepages change, and one of the three has already changed its headline.
You can score your own hero in five minutes with the test near the end.
What is the Hero Stack?
The Hero Stack is the order in which the first screen of an AI homepage should answer a buyer’s questions. It has four layers: Outcome, Mechanism, Proof and Product.
Layer | What it says | Where it sits | Quick check |
|---|---|---|---|
Outcome | What the buyer gets, in their units | Headline | Is there a result, not an adjective? |
Mechanism | What the AI reads, decides and does | Subhead | Does one sentence name three verbs? |
Proof | Why to believe it | Beside or under the headline | Is there a named customer, number or rating on the first screen? |
Product | The product working | Hero visual | Does the image show the product, not a mood? |
Add one primary button and one low commitment secondary, and you have a hero. The seven mistakes below are what happens when a layer is missing or out of order.
Also read: Product Messaging for AI Startups: What It Is and When to Hire Help
What are the most common AI homepage messaging mistakes?
The seven below came up across the three teardowns. Each includes the evidence from the page we reviewed on October 29, 2026.
Mistake 1: Is your headline a promise anyone could make?
A generic promise fits every competitor. Engati’s headline read “Acquire more customers, faster!” Any marketing tool could say that. It names no buyer and no mechanism, so it works as a slogan but not as an explanation. Our concept rewrite: “Turn every conversation into a customer, on any channel.”
Mistake 2: Does your subhead use jargon the buyer never uses?
The Engati subhead stacked terms such as “multi touchpoint” and “omni channel.” A buyer has to decode it before reading on. Our concept replaced it with one plain sentence: the AI reads each message, works out what the customer needs, and does it or passes it to the team.
Mistake 3: Does the headline use a metaphor instead of a value?
Intelmatix opened with “Empower Your Enterprise with our Digital Brain.” A digital brain is a metaphor. A buyer cannot tell whether it forecasts demand, answers questions or writes reports. Our concept headline: “One AI providing enterprise wide insights,” with the product named in the subhead.
Mistake 4: Is there a button in the hero?
On the Intelmatix page we reviewed, the hero offered a scroll cue and no call to action. A visitor who is interested has nowhere to go. Our concept added a primary button, “See EDIX in action,” and a secondary, “Read case studies.”
Mistake 5: Does the visual show the product?
Engati’s hero used an abstract funnel chart. Intelmatix used a dark abstract 3D image. The Avaamo version we reviewed used a still of a dancer from a video. None of them showed the product working. Our concepts replaced each with a product view: a live inbox with AI status tags for Engati, a tabbed product demo for Intelmatix, and a call player with Triage, Scheduling and Refills labels for Avaamo.
Mistake 6: Is the proof buried?
Intelmatix had a World Economic Forum Pioneer recognition for 2025 that the page did not use in its hero. Engati’s Meta award sat below the fold. Proof in section five is proof most visitors never see. We moved each to the first screen as a badge or a rating line.
Mistake 7: Is the headline about the future instead of the buyer’s day?
The older Avaamo version led with “Meet the AI contact center from the future.” Futurism is not an outcome. Our concept narrowed the buyer to health systems and the result to a number a manager cares about: “Resolve more patient calls without adding staff.” Avaamo has since changed its live headline, so treat our capture as a snapshot from October 29, 2026.
Mistake | Where we saw it | Hero Stack layer it breaks |
|---|---|---|
Generic promise | Engati | Outcome |
Jargon subhead | Engati | Mechanism |
Metaphor headline | Intelmatix | Outcome |
No hero button | Intelmatix | Product |
Mood imagery | All three | Product |
Buried proof | Engati, Intelmatix | Proof |
Future talk, no buyer | Avaamo | Outcome |
Pro tip: If you can swap your competitor’s name into your headline and the line still works, the headline is not doing its job.
What did the fixed heroes have in common?
Each fixed hero chose one buyer, one outcome and one verb phrase for the AI, then showed the product and one proof element above the fold. The look matters less than that order, which makes the three concepts handy AI SaaS homepage examples for any team starting a rewrite.
The three concepts also shared a visual system: warm light neutrals, tight editorial display type, dark brown primary buttons and a logo strip. That was a design choice we made for consistency across the set, not a requirement of the method. You can apply the Hero Stack in any visual style.
A few limits are worth stating plainly. Our concepts use sample data in the mockups. A real project would replace it with the company’s own numbers, and the proof lines would come from clients, not from us. Our rewrites also reflect our reading of each company’s product from public pages, not a conversation with their teams. Treat them as method demonstrations.
To see how we work, read our ORYN AI agent monitoring landing page and Simora AI simulation landing page case studies, or browse all of our case studies.
What does a strong AI homepage look like?
A strong AI homepage tells you what the product is and when you would use it in the first line, and answers the first objection in the second. Granola’s hero on November 2, 2026 did this with “The AI notepad for back-to-back meetings,” followed by a subhead that said notes, actions and memory, with no meeting bot joining the call.
It does not do everything. The proof, a logo wall and an App Store rating, sits below the hero, so a visitor deciding quickly sees the promise before the evidence. That is a small gap in an otherwise clear page, and it shows that even good heroes can move one layer higher.
How do you fix your own AI homepage hero?
Work through the Hero Stack from the top to fix your AI startup hero section, and stop at the first layer that fails. This is also how to write homepage messaging for an AI startup from scratch: start with the outcome and add one layer at a time.
Outcome. Write the result in the buyer’s units. Calls resolved, hours saved, deals closed.
Mechanism. Write one sentence with three verbs: what the AI reads, decides and does.
Proof. Choose the strongest proof you can show today, and place it in the first screen.
Product. Replace mood imagery with a view of the product doing its job. Label demo numbers as sample data.
Calls to action. One primary button that matches the buyer’s next step. One low commitment secondary.
Pro tip: Write the mechanism sentence before the headline. If you cannot name three things the AI does, the headline has nothing to stand on.
Also read: How to Explain Your AI Product on Your Website
How do you test an AI homepage in five minutes?
Show the hero to five people in your buyer role for five seconds and ask two questions: what does this company do, and who is it for? Count how many get both right.
Score | What it means | What to do |
|---|---|---|
4 or 5 correct | The hero is clear | Move to testing the CTA |
2 or 3 correct | One layer is failing | Fix the first failing Hero Stack layer and retest |
0 or 1 correct | The page is not explaining the product | Rewrite the Outcome and Mechanism before touching design |
Run the test before you spend on an AI homepage redesign. It is cheap, it takes minutes, and it tells you whether the problem is words or visuals. Nielsen Norman Group’s analysis of page visits, led by Jakob Nielsen, found that visitors decide quickly whether to stay. The study is from 2011, so use it as a direction and let your own test settle the question.
Also read: Positioning an AI Agent Product: Who It Is For and Who It Is Not For
How did we make these teardowns?
We reviewed each company’s live homepage on October 29, 2026, wrote down what a first time buyer could and could not tell, and rebuilt each hero as a concept. We used only public pages, did not contact the companies and have no inside knowledge of their products or results.
Three rules kept the work fair. We dated every capture, because live pages change. We labeled every rewrite as a Kraftbase concept. And we marked mockup numbers as sample data, since a concept cannot claim a real result. If you publish teardowns of your own, hold yourself to the same three rules.
Also read: AI Medical Scribe UX Teardown: What Abridge, Suki, Nuance DAX and Freed Get Right
Keep reading: Product Messaging for AI Startups: What It Is and When to Hire Help, Positioning an AI Agent Product: Who It Is For and Who It Is Not For, SaaS Website Messaging Audit: A 20 Point Checklist You Can Run in an Afternoon and AI Landing Page Design: Examples and Lessons From Three Pages We Designed
Which layer of your hero is failing right now?
Send us your homepage URL and we will run it against the Hero Stack and tell you where it breaks first. Get a hero teardown · See our work
AI homepage messaging FAQs
Skipping the mechanism. Many AI homepages promise an outcome and then never say what the AI reads, decides and does. Without that sentence, a buyer cannot tell the product from any other AI tool. Add one line with three verbs directly under the headline and the page becomes much easier to understand.
Short enough to read in one glance, usually under ten words. The headline should state the outcome for a named buyer, and the subhead can carry the mechanism in one sentence. If your headline needs a second line to make sense, move that line to the subhead and rewrite the headline.
Only when the category is defined by it, such as an AI notepad. Otherwise lead with the outcome and put the AI in the subhead as the mechanism. Buyers search for results, so naming the result in the headline keeps the first line useful to someone who has never heard of the product.
Yes. Kraftbase is a product messaging and UI/UX design studio for AI and B2B SaaS companies, working as a SaaS website design agency. A typical homepage project starts with the buyer and the message, then moves to the design and build, so the words and the layout are decided together.
One of three things: a named customer, a specific number with its source, or a view of the product working. A rating, a recognized award or a short logo strip also works. Choose the strongest one you can verify today, and label any demo figures as sample data.
It can be, if you label the work as a concept, state that you are not associated with the company, date the capture of the original page, and keep the claims factual. Avoid implying client work or inside knowledge. Publishing teardowns is common practice for design studios, and the label protects both sides.
Review it every quarter and whenever the product changes in a way a buyer would notice. AI products move fast, and a hero that describes last year’s features loses trust. Update the date on the page only when the content has changed in a meaningful way.
About the author
Aneri is a designer at Kraftbase, a product messaging and UI/UX design studio in Vadodara, India, that helps AI and B2B SaaS teams in the US, UAE and India explain and design what they’ve built.
Sources
Homepage captures: Engati, Intelmatix, Avaamo (Oct 29, 2026, Kraftbase concept teardowns); Granola (Nov 2, 2026)
Jakob Nielsen, “How Long Do Users Stay on Web Pages?”, Nielsen Norman Group, 2011
Hero teardown
Which layer of your hero is failing right now?
Send us your homepage URL and we will run it against the Hero Stack and tell you where it breaks first.
Most AI homepages fail in the same place: the first screen. A visitor lands, reads a headline about the future, and cannot tell what the product does or whether it is for them. We saw the same failure three times in a row while redesigning hero sections for Engati, Intelmatix and Avaamo as Kraftbase concepts.
Three AI company homepages, seven repeated mistakes. We reviewed each page on October 29, 2026, fixed each mistake in a concept rewrite and kept the method so you can run it on your own hero, with a five minute test at the end. None of these companies is a Kraftbase client, and we are not associated with them. The rewrites are our concepts, not their copy.
Key takeaways
The same seven mistakes appeared across three different AI products, which suggests they are habits of the category, not one company’s slip.
Every fix follows the Hero Stack: Outcome, Mechanism, Proof, Product, in that order.
The mistake that costs the most is skipping the mechanism, because the buyer never learns what the AI actually does.
All captures are dated. Live homepages change, and one of the three has already changed its headline.
You can score your own hero in five minutes with the test near the end.
What is the Hero Stack?
The Hero Stack is the order in which the first screen of an AI homepage should answer a buyer’s questions. It has four layers: Outcome, Mechanism, Proof and Product.
Layer | What it says | Where it sits | Quick check |
|---|---|---|---|
Outcome | What the buyer gets, in their units | Headline | Is there a result, not an adjective? |
Mechanism | What the AI reads, decides and does | Subhead | Does one sentence name three verbs? |
Proof | Why to believe it | Beside or under the headline | Is there a named customer, number or rating on the first screen? |
Product | The product working | Hero visual | Does the image show the product, not a mood? |
Add one primary button and one low commitment secondary, and you have a hero. The seven mistakes below are what happens when a layer is missing or out of order.
Also read: Product Messaging for AI Startups: What It Is and When to Hire Help
What are the most common AI homepage messaging mistakes?
The seven below came up across the three teardowns. Each includes the evidence from the page we reviewed on October 29, 2026.
Mistake 1: Is your headline a promise anyone could make?
A generic promise fits every competitor. Engati’s headline read “Acquire more customers, faster!” Any marketing tool could say that. It names no buyer and no mechanism, so it works as a slogan but not as an explanation. Our concept rewrite: “Turn every conversation into a customer, on any channel.”
Mistake 2: Does your subhead use jargon the buyer never uses?
The Engati subhead stacked terms such as “multi touchpoint” and “omni channel.” A buyer has to decode it before reading on. Our concept replaced it with one plain sentence: the AI reads each message, works out what the customer needs, and does it or passes it to the team.
Mistake 3: Does the headline use a metaphor instead of a value?
Intelmatix opened with “Empower Your Enterprise with our Digital Brain.” A digital brain is a metaphor. A buyer cannot tell whether it forecasts demand, answers questions or writes reports. Our concept headline: “One AI providing enterprise wide insights,” with the product named in the subhead.
Mistake 4: Is there a button in the hero?
On the Intelmatix page we reviewed, the hero offered a scroll cue and no call to action. A visitor who is interested has nowhere to go. Our concept added a primary button, “See EDIX in action,” and a secondary, “Read case studies.”
Mistake 5: Does the visual show the product?
Engati’s hero used an abstract funnel chart. Intelmatix used a dark abstract 3D image. The Avaamo version we reviewed used a still of a dancer from a video. None of them showed the product working. Our concepts replaced each with a product view: a live inbox with AI status tags for Engati, a tabbed product demo for Intelmatix, and a call player with Triage, Scheduling and Refills labels for Avaamo.
Mistake 6: Is the proof buried?
Intelmatix had a World Economic Forum Pioneer recognition for 2025 that the page did not use in its hero. Engati’s Meta award sat below the fold. Proof in section five is proof most visitors never see. We moved each to the first screen as a badge or a rating line.
Mistake 7: Is the headline about the future instead of the buyer’s day?
The older Avaamo version led with “Meet the AI contact center from the future.” Futurism is not an outcome. Our concept narrowed the buyer to health systems and the result to a number a manager cares about: “Resolve more patient calls without adding staff.” Avaamo has since changed its live headline, so treat our capture as a snapshot from October 29, 2026.
Mistake | Where we saw it | Hero Stack layer it breaks |
|---|---|---|
Generic promise | Engati | Outcome |
Jargon subhead | Engati | Mechanism |
Metaphor headline | Intelmatix | Outcome |
No hero button | Intelmatix | Product |
Mood imagery | All three | Product |
Buried proof | Engati, Intelmatix | Proof |
Future talk, no buyer | Avaamo | Outcome |
Pro tip: If you can swap your competitor’s name into your headline and the line still works, the headline is not doing its job.
What did the fixed heroes have in common?
Each fixed hero chose one buyer, one outcome and one verb phrase for the AI, then showed the product and one proof element above the fold. The look matters less than that order, which makes the three concepts handy AI SaaS homepage examples for any team starting a rewrite.
The three concepts also shared a visual system: warm light neutrals, tight editorial display type, dark brown primary buttons and a logo strip. That was a design choice we made for consistency across the set, not a requirement of the method. You can apply the Hero Stack in any visual style.
A few limits are worth stating plainly. Our concepts use sample data in the mockups. A real project would replace it with the company’s own numbers, and the proof lines would come from clients, not from us. Our rewrites also reflect our reading of each company’s product from public pages, not a conversation with their teams. Treat them as method demonstrations.
To see how we work, read our ORYN AI agent monitoring landing page and Simora AI simulation landing page case studies, or browse all of our case studies.
What does a strong AI homepage look like?
A strong AI homepage tells you what the product is and when you would use it in the first line, and answers the first objection in the second. Granola’s hero on November 2, 2026 did this with “The AI notepad for back-to-back meetings,” followed by a subhead that said notes, actions and memory, with no meeting bot joining the call.
It does not do everything. The proof, a logo wall and an App Store rating, sits below the hero, so a visitor deciding quickly sees the promise before the evidence. That is a small gap in an otherwise clear page, and it shows that even good heroes can move one layer higher.
How do you fix your own AI homepage hero?
Work through the Hero Stack from the top to fix your AI startup hero section, and stop at the first layer that fails. This is also how to write homepage messaging for an AI startup from scratch: start with the outcome and add one layer at a time.
Outcome. Write the result in the buyer’s units. Calls resolved, hours saved, deals closed.
Mechanism. Write one sentence with three verbs: what the AI reads, decides and does.
Proof. Choose the strongest proof you can show today, and place it in the first screen.
Product. Replace mood imagery with a view of the product doing its job. Label demo numbers as sample data.
Calls to action. One primary button that matches the buyer’s next step. One low commitment secondary.
Pro tip: Write the mechanism sentence before the headline. If you cannot name three things the AI does, the headline has nothing to stand on.
Also read: How to Explain Your AI Product on Your Website
How do you test an AI homepage in five minutes?
Show the hero to five people in your buyer role for five seconds and ask two questions: what does this company do, and who is it for? Count how many get both right.
Score | What it means | What to do |
|---|---|---|
4 or 5 correct | The hero is clear | Move to testing the CTA |
2 or 3 correct | One layer is failing | Fix the first failing Hero Stack layer and retest |
0 or 1 correct | The page is not explaining the product | Rewrite the Outcome and Mechanism before touching design |
Run the test before you spend on an AI homepage redesign. It is cheap, it takes minutes, and it tells you whether the problem is words or visuals. Nielsen Norman Group’s analysis of page visits, led by Jakob Nielsen, found that visitors decide quickly whether to stay. The study is from 2011, so use it as a direction and let your own test settle the question.
Also read: Positioning an AI Agent Product: Who It Is For and Who It Is Not For
How did we make these teardowns?
We reviewed each company’s live homepage on October 29, 2026, wrote down what a first time buyer could and could not tell, and rebuilt each hero as a concept. We used only public pages, did not contact the companies and have no inside knowledge of their products or results.
Three rules kept the work fair. We dated every capture, because live pages change. We labeled every rewrite as a Kraftbase concept. And we marked mockup numbers as sample data, since a concept cannot claim a real result. If you publish teardowns of your own, hold yourself to the same three rules.
Also read: AI Medical Scribe UX Teardown: What Abridge, Suki, Nuance DAX and Freed Get Right
Keep reading: Product Messaging for AI Startups: What It Is and When to Hire Help, Positioning an AI Agent Product: Who It Is For and Who It Is Not For, SaaS Website Messaging Audit: A 20 Point Checklist You Can Run in an Afternoon and AI Landing Page Design: Examples and Lessons From Three Pages We Designed
Which layer of your hero is failing right now?
Send us your homepage URL and we will run it against the Hero Stack and tell you where it breaks first. Get a hero teardown · See our work
AI homepage messaging FAQs
Skipping the mechanism. Many AI homepages promise an outcome and then never say what the AI reads, decides and does. Without that sentence, a buyer cannot tell the product from any other AI tool. Add one line with three verbs directly under the headline and the page becomes much easier to understand.
Short enough to read in one glance, usually under ten words. The headline should state the outcome for a named buyer, and the subhead can carry the mechanism in one sentence. If your headline needs a second line to make sense, move that line to the subhead and rewrite the headline.
Only when the category is defined by it, such as an AI notepad. Otherwise lead with the outcome and put the AI in the subhead as the mechanism. Buyers search for results, so naming the result in the headline keeps the first line useful to someone who has never heard of the product.
Yes. Kraftbase is a product messaging and UI/UX design studio for AI and B2B SaaS companies, working as a SaaS website design agency. A typical homepage project starts with the buyer and the message, then moves to the design and build, so the words and the layout are decided together.
One of three things: a named customer, a specific number with its source, or a view of the product working. A rating, a recognized award or a short logo strip also works. Choose the strongest one you can verify today, and label any demo figures as sample data.
It can be, if you label the work as a concept, state that you are not associated with the company, date the capture of the original page, and keep the claims factual. Avoid implying client work or inside knowledge. Publishing teardowns is common practice for design studios, and the label protects both sides.
Review it every quarter and whenever the product changes in a way a buyer would notice. AI products move fast, and a hero that describes last year’s features loses trust. Update the date on the page only when the content has changed in a meaningful way.
About the author
Aneri is a designer at Kraftbase, a product messaging and UI/UX design studio in Vadodara, India, that helps AI and B2B SaaS teams in the US, UAE and India explain and design what they’ve built.
Sources
Homepage captures: Engati, Intelmatix, Avaamo (Oct 29, 2026, Kraftbase concept teardowns); Granola (Nov 2, 2026)
Jakob Nielsen, “How Long Do Users Stay on Web Pages?”, Nielsen Norman Group, 2011
Hero teardown
Which layer of your hero is failing right now?
Send us your homepage URL and we will run it against the Hero Stack and tell you where it breaks first.