In a recent client website review, I put 32 homepage messages in front of the team. They were grouped around different audiences, pain points, and ways to explain the product's value.
The interesting part was the spread of reactions. People were looking for different things from the same page.
We were discussing how prominently to lead with AI, whether to name a category in the headline, and how to guide different buyers through the site. Each question sounded like a copy decision. Together, they revealed how much the team still needed to agree on before a headline could do its job.
What the headline is being asked to do
A homepage can be asked to explain today's product, introduce a broader vision, reassure an existing buyer, and attract a new one. Those are reasonable ambitions. They also compete for the same few seconds of attention.
Take the AI question. If we lead with AI, what does that help a prospect understand? Does it explain a capability they care about? Does it distinguish the product from an alternative? Or does it make a familiar problem harder to recognize because the visitor now has to decode our new description?
I don't think there's a universal answer. The useful answer depends on the buyer and the work the product does for them. That's why a vote on which headline sounds best only gets us so far.
In that review, putting actual messages on the screen made the disagreement easier to discuss. People could point to a choice and explain what they were trying to preserve. That was more useful than another conversation about whether the messaging felt clear.
Give the options different jobs
If I were setting up this exercise again, I'd ask the team to describe the job of each candidate before judging the wording. One might be written for someone who already understands the category. Another might help a buyer recognize a problem they haven't named yet. A third might explain why the product can handle a broader set of needs.
For example, one candidate could lead with a task the product handles today, while another leads with the larger category we want to enter. Those are different bets. I’d write the assumed buyer and the proof each version needs underneath it. If we can’t show that the product delivers the broader promise, choosing more ambitious language won’t close the gap.
Then I'd ask what evidence we have that this is the visitor we need to serve. Recent prospect conversations, the questions sales keeps answering, and the paths people take into the site are all useful inputs.
That doesn't eliminate judgment. It makes the judgment visible. We can discuss whether the homepage should prioritize an immediate use case or the broader offering, instead of arguing endlessly about two adjectives.
The navigation is part of the message
The same issue showed up in navigation. Should it use product names or organize around the jobs buyers need to do?
A product name can work well for someone who already knows what they want. A new visitor may need help recognizing which product applies to them. More menu items don't automatically solve that problem; they can just move the work of understanding the company onto the visitor.
I'd evaluate the headline and the next click together. After reading the opening, can the intended buyer explain what the company does and choose a sensible path? If they understand the sentence but can't find the relevant offering, the page still has work to do.
Take the disagreement to buyers
The next useful step is to test the assumptions underneath the options. That's where prospect interviews and tools such as Wynter can help. I'd ask people to explain what they think the company offers, who they think it's for, and what they'd need to see next.
I would pay particular attention to interpretations the internal team didn't expect. A message can be well liked and still communicate the wrong thing. A less polished option can reveal language buyers recognize immediately.
Buyer feedback also needs judgment. A handful of interviews won't determine the entire company's strategy, and a message test won't establish the revenue impact of a redesign. It can expose confusion before the team spends weeks building around it.
The 32 messages were useful because they made the choices visible. They didn't produce a final answer by themselves. If your homepage keeps cycling through rewrites, ask what decision the team is trying to make through the copy. Give that decision a name before commissioning version 33.