Voice of customer interview questions before a homepage rewrite

Gabriel Espinheira
Voice of customer interview questions should capture the buying moment, failed alternatives, real stakes, and decision language before anyone rewrites your homepage. Ask customers what copy they like and you will get compliments, not a brief.
That distinction matters when the current page feels vague but nobody can agree on why. The founder wants it to sound more premium. Sales wants more proof. The writer wants a clearer audience. Five transcript tabs later, everyone has highlighted a different sentence and the old homepage is still live.
The interviews are not the output. The output is a set of page decisions that a writer can ship without asking the founder to choose between twenty adjectives.
TL;DR: Start with five well-chosen interviews. Ask about the buying trigger, old workaround, frustration, alternatives, doubts, decision criteria, and desired change. Then map repeated language to the homepage hero, problem, proof, objections, and CTA. Check the pattern against CRM and website behaviour before you rewrite.
What voice of customer interview questions need to uncover
Your interview needs a buying sequence, not a satisfaction score. The useful evidence is what happened before the customer searched, what they tried, what made the problem urgent, what they compared, and what finally made a decision feel safe.
Internal certainty is a poor substitute. In PwC's 2025 Customer Experience Survey, about nine in ten executives said loyalty had grown in recent years, while only four in ten consumers said the same. The study covered 5,511 US consumers and 406 executives, so it is not a proxy for every European market. It still exposes a familiar problem: businesses can feel confident about a customer experience that customers describe very differently.
For homepage copy, listen for four things:
The trigger that turned a tolerated problem into an active search.
The workaround the buyer had already tried and stopped trusting.
The consequence that made waiting feel expensive or embarrassing.
The evidence and terms that made the final choice feel safe.
That is where lines such as "I've been burned before" and "I want results, not reports" earn their place. They are not decorative quotes. They tell you the page must address trust, visibility, and proof before it asks for a call.
Who should you interview before a homepage rewrite?
Five conversations are a sensible first batch, not a declaration of market truth. Contentsquare recommends interviewing at least five people to get a broader range of viewpoints. For a small owner-operated business, the mix matters more than pretending the sample is statistically representative.
Start with people who can describe a real decision:
Two recent customers who fit the work you want more of.
One customer who almost did not buy.
One qualified enquiry or lost deal that chose another route.
One ideal-fit prospect still living with the problem.
Do not fill the list with your happiest customers. They are useful for proof, but praise alone will hide the friction your homepage needs to answer.
Picture the CRM after a quiet month. One opportunity closed, two stalled after the proposal, and another chose to keep managing three separate suppliers. Those four records contain different parts of the buying decision. Interviewing only the closed account would make the page sound easier to buy from than it really is.
Five calls can agree for the wrong reason. If every participant came through the same referral partner, they may share language the wider market never uses. Record the acquisition source beside each transcript and keep the conclusion narrow until searches, sessions, sales notes, and actual enquiries support it.
Seven questions that produce usable homepage copy
A loose discussion guide beats a rigid script. You need enough structure to compare answers, with room to follow a detail the customer did not expect to mention.
"What was going on when you started looking for help?" This finds the trigger. One founder on Indie Hackers asks, "What was going on in your world when you started looking for something like this?" It is stronger than asking why someone bought because it starts with a scene, not a polished explanation.
"How were you handling this before?" The answer reveals the old workaround: a freelancer, a spreadsheet, an internal hire, disconnected tools, or simply putting the problem off.
"What was frustrating about that approach?" Ask for the last specific example. "Communication was bad" is weak evidence. "I had to explain the same brief to a new account manager three times" can shape a section.
"What happened when the problem was left alone?" This uncovers the stakes without inventing urgency. The answer might be missed enquiries, an empty sales pipeline, a page the founder avoids sharing, or time lost coordinating suppliers.
"What else did you consider?" Alternatives tell you which category the page must win against. Sometimes the alternative is not another provider. It is doing nothing, hiring internally, or keeping the current mess for another quarter.
"What made you hesitate?" Do not rush to defend the business. The hesitation belongs in the proof, FAQ, terms, or call expectation section. If three people worry about ownership after cancellation, a vague testimonial will not fix the page.
"What made the decision feel safe enough to take the next step?" This identifies the trust mechanism: direct access to the senior person, visible weekly work, a clear exit, a concrete process, or a useful first call.
The best follow-up is usually shorter than the main question: "What happened next?" or "Why?" Stay with the past. A promise about what someone might buy next year is weaker than the workaround they paid for last month.
Turn interview answers into homepage decisions
This is where research usually goes to die: a colour-coded quote board with no decision attached. Five transcripts can become one in about ten minutes. Resist it. A strong sentence only survives when it changes the page.
Most interview guides stop at themes and quotes. The homepage still needs a decision. Customer words are evidence. Page decisions are the work.
At SharpHaw, a conversion-first website has to move one recognisable buyer towards one clear next step. That means good interview language may still get cut. If a quote sounds sharp but does not clarify the buyer, problem, proof, or action, it belongs in the notes.
The same rule protects the writer. Instead of receiving "make it bold, premium, and human", the writer gets a trigger, three exact phrases, the old workaround, the main doubt, the proof that answers it, and the CTA. That is a brief they can use.
The questions that make customer research worse
Polite answers can look like insight when the question has already written half the response. "How much do you like our service?" assumes the customer likes it. "Would clearer copy make you book?" asks them to predict behaviour in a fictional future.
Contentsquare's interview guidance warns against leading questions and recommends open questions when you need to understand how or why someone thinks as they do. Community practice says the same thing more bluntly. One founder admitted, "I was asking too many closed or very hypothetical questions" before switching to a discussion guide.
Four traps do the most damage:
Asking customers to write the page for you. They know their situation, not your information architecture.
Asking whether they would pay. Stated intent is not the same as an invoice being paid.
Selling when the answer feels uncomfortable. The interview is not a discovery call.
Treating one vivid quote as a market pattern. Memorable is not the same as repeated.
Silence helps. Give the customer a few seconds to remember the last real event. The useful detail often arrives after the polished first answer.
Check the transcript against what buyers actually did
Now put the transcript beside the artefacts. Open the CRM, Search Console, session recordings, and the current homepage. The job is to see whether the words and behaviour point to the same problem.
A customer says pricing was not the issue, but three qualified opportunities stalled after visiting the Plans page. Search Console shows the homepage attracting informational queries while the hero asks for a sales call. Session recordings show people opening the FAQ and returning to the ownership section. None of those signals is conclusive alone. Together, they tell you what the next page draft must resolve.
Contentsquare calls this triangulation: check confusing or contradictory interview findings against other feedback and behavioural sources. For a founder, that can stay simple:
Compare repeated phrases with sales-call notes and lost-deal reasons.
Check whether the named problem appears in the queries bringing people to the page.
Watch whether visitors reach the proof and CTA or leave before either appears.
Re-read form submissions for the words people use before anyone on the team replies.
If you record or transcribe interviews, treat that file as customer data, not disposable research material. The European Commission explains that collecting, recording, storing, using, and deleting identifiable personal data are all processing operations. Tell participants what you are collecting and why, limit access, keep only what the stated purpose needs, and follow the lawful basis and retention rules that apply to your organisation.
Brief the writer with evidence, not adjectives
The working brief can fit on one page. It should name the buyer, the moment that started the search, the workaround that failed, the outcome they wanted, the objection that nearly stopped them, and the proof the page can honestly show.
Then attach the evidence:
Three to five exact phrases with transcript references.
The repeated pattern and any important contradiction.
The CRM, search, or behaviour signal that supports it.
The hero decision, proof obligation, and primary CTA.
The claims the writer must not make.
End the brief with the claims the page cannot make. Voice of customer research does not give a business permission to publish every result, implied promise, or enthusiastic remark. The page still needs verified proof.
SharpHaw's Content Engine uses the same discipline: research first, claim control next, then the draft. The order feels slower until you compare it with rewriting the same vague page three times.
Frequently asked questions
What is a voice of customer interview?
A voice of customer interview is a structured conversation that captures how a customer experienced a real problem, searched for help, compared alternatives, made a decision, and judged the outcome. For website copy, the useful material is exact buying language and repeated decision patterns, not general satisfaction scores.
How many customer interviews should you conduct?
Start with five well-chosen interviews to find a directional pattern, then test it against behaviour and add interviews until new calls stop changing the decision. Five is a practical first batch, not a representative market sample. Mix recent buyers with a hesitant buyer, a lost deal, and an ideal-fit prospect.
What questions should you ask in a voice of customer interview?
Ask about the trigger, previous workaround, frustration, consequence, alternatives, hesitation, decision criteria, and desired change. Keep questions open and anchored in past events. Follow useful answers with "What happened next?" or "Why?" Avoid asking customers to predict future purchases or write your homepage for you.
Can AI analyse customer interview transcripts?
AI can cluster repeated phrases, tag objections, and compare transcripts, but it should not decide the page alone. A person still needs to check context, bias, privacy, and proof. Use an approved system, minimise personal data, review every quoted line, and validate themes against CRM and website behaviour.
Digital work that compounds. That is the standard: customer evidence changes the brief, the brief changes the page, and the page keeps improving after it ships.
Plan. Build. Iterate.
Ready to stop guessing what your homepage should say? Book a 30-min call and get an honest read on your digital growth, or see how the subscription works.
Read more
Internal linking strategy: connect every post to the offer
Build an internal linking strategy that helps Google find pages and guides buyers from useful content to the right offer, proof, or next step. See the system.
Call tracking only works after the phone rings
Call tracking is not a call counter. See the five-field handoff that connects Google Ads, phone enquiries and real sales without recording every call.
Content distribution checklist: stop shipping posts into silence
Content distribution checklist for founders: turn every post into email, social, sales follow-up, links, and measured next actions.

