Most B2B software founders want two things from their homepage:
1. For visitors to understand the product fully 2. For visitors to request a demo
Those two goals are in conflict.
The homepage that tries to give visitors a full understanding of the product is the homepage that fails to earn the demo. Rob Kaminski from Fletch has a precise framework for why - and it reframes what the homepage is actually for.
What the homepage is actually for
"The way we use the homepage - we use it as like this visible testing ground of where we think the positioning should live. We are looking for the pieces, the arguments that are the simplest to understand and the most memorable," Rob said on Youroast Ep1. "Rather than trying to articulate this big narrative of why you're valuable, you're really just trying to say like the sharpest thing. Hey, this is the thing we're doing that we think we're better than anybody. And here's like the three reasons why. That earns you the meeting." [Ep1, 11:00]
The homepage's complete job:
- A visitor reads the hero
- Understands the claim
- Believes you solve their problem
- Requests a demo
That is it. Everything else - the feature comparison table, the integration list, the detailed use-case breakdowns - is supporting proof for a visitor who is already interested. Not the persuasion mechanism for a visitor who is not yet convinced.
The homepage is not trying to close the deal. It is trying to earn the conversation. Thirty minutes with the right buyer is a successful homepage conversion.
What the sales conversation adds
The sales environment does something the homepage cannot: it creates a two-way conversation.
"When you get into a sales environment, we get to ask each other questions. I get to be like, what's your situation? What are you working on? You have that platform. Suddenly I can start to dynamically position," Rob said. "If you have that competitor, well now my argument is gonna change. And also I'm gonna show you all the subtext underneath the hood." [Ep1, 12:00]
The 3D sales conversation allows the salesperson to:
- Identify which of the three hero reasons matter most to this specific buyer
- Understand which competitors they are evaluating
- Address the objections specific to their situation
- Demonstrate depth calibrated to their existing knowledge level
None of those things are knowable from the homepage visit. The homepage makes the case for the category of buyer. The sales conversation makes the case for this specific buyer in this specific context.
The content of both is deliberately different - and it should be.
The baby problem
Rob names the mechanism that causes founders to over-explain in the hero. He calls it the baby problem.
"That's very uncomfortable, especially for founders and product folks, because they spend years often building these products. It's like it's their baby. And they all they want to do is talk about their baby and all the cool things it does. And it's like - nobody cares. You put all the blood, sweat, and tears into it. But your audience, like, they don't know you, they don't trust you. And so you really do have to have that five to ten second piece." [Ep1, 12:40]
The cold homepage visitor has two to three seconds before the pattern recognition fires: "this looks like everything else in this category" - or it does not.
The claim has to land in that window. Everything else is supporting evidence for a visitor who is already interested.
The baby problem manifests as:
- A hero section with four different claims
- A subheading that lists seven features
- A video that runs ninety seconds before the CTA appears
- A tagline that could belong to any company in the category
The founder is writing for a visitor who already cares about the product. The visitor does not care yet. The homepage has to earn that caring in ten seconds before it earns the right to explain anything.
What this means when briefing a design sprint
The 2D versus 3D distinction is the most important framing to bring into a homepage brief.
The question is not: how do we show everything the product does?
The question is: what is the single sharpest claim that earns the meeting, and what are the three reasons a skeptical buyer should believe it?
Everything else - the feature comparison table, the integration list, the pricing FAQ, the detailed use-case breakdowns - belongs below the fold or on dedicated pages. The hero is the 2D claim. The rest of the page is supporting proof that a visitor who is already interested reads to confirm their initial judgment.
The stranger test applied here: cover the logo, give someone thirty seconds, ask them to explain the product. If the 2D claim is working, they can do it. If it is not, the hero is carrying too much - or not enough of the right thing.
When the 2D claim is locked and the hero passes the stranger test, the homepage is ready for a Signature Design Style sprint. Read website redesign prerequisites for the full checklist.
What to do next
Run the stranger test on your current hero. Cover the logo. Give someone thirty seconds. Ask: what does this company sell and who buys it? If they cannot answer accurately, the hero is not ready for a design upgrade - it is ready for a copy rewrite.
Read the companion articles:
- Three litmus tests to check your B2B software positioning - including the full stranger test protocol
- Fix positioning before you redesign - the framework before any design spend
- Why one ICP outperforms multiple segments for B2B software companies - how ICP clarity connects to the 2D claim
Watch the full episode: Youroast Ep1 with Rob Kaminski.
