Why a customer interview guide matters
Most teams decide to talk to customers right before they change something important, such as the homepage, the pricing, or the product roadmap. That's the right instinct. The trouble is that customers are kind. Ask them whether they like your product or whether a new feature sounds useful, and most of them will say yes. You end the week with ten pleasant conversations and nothing you can act on.
A guide fixes that by deciding in advance what each conversation needs to find out. It turns vague curiosity ("what do customers think of us?") into specific questions about real events: why they started looking, what they tried first, who else was involved, and what nearly made them walk away. Those are the answers that tell you whether your messaging matches the reason people buy.
Writing a guide well takes more preparation than it looks. You need to know what you believe about your customers today, which of those beliefs are shaky, and who can tell you the truth about them. AI is well suited to this preparation, because it can read everything your company says about itself, notice which claims rest on assumptions, and draft questions that test them in neutral language.
Kite is an AI marketer. It researches your business, builds a growth strategy, and ships the work that brings you new customers. You can work with Kite in your browser or in Slack. Because Kite has already researched your company, it can write an interview guide that's specific to your business instead of a generic template. Here's how it works.
How Kite writes your customer interview guide
Kite builds the guide backward from the decision you're trying to make. It starts with what it knows about your business, lists the beliefs that decision depends on, and then writes the questions that would confirm or overturn each one.
That knowledge comes from your team's knowledge base, which Kite starts filling as soon as you sign up. It holds your ideal customer profile, your positioning and messaging, your products and pricing, your competitors, and any customer research Kite has already done, such as patterns in your public reviews. So when you say, "We're rewriting the homepage and want to interview customers first," Kite already knows what the homepage claims and who it says the product is for.
From there, Kite writes the guide, helps you recruit the right people, and gives you a version of the guide to use live. After the interviews, it reads your notes and tells you what changed. Each part is described below.
- Start with what you need to learn
- What questions should I ask in a customer discovery interview?
- How do I avoid leading questions in customer interviews?
- How do I prepare for customer interviews?
- Turn your notes into findings
Start with what you need to learn
The first section of every guide Kite writes is a short list of the things you need to learn, written as beliefs that could turn out to be wrong. This list keeps the interviews focused on the decision in front of you.
Kite drafts the list by comparing what your company says with what it can verify. Suppose your homepage says you help "busy restaurant owners save time on scheduling," but your reviews mostly come from multi-location managers who talk about labor costs. Kite might write three beliefs to test:
- The person who buys is the owner, not a general manager or an operations lead.
- The main reason people switch is saving time, not controlling labor costs.
- Buyers are switching away from spreadsheets, not from a competing scheduling product.
You review the list and change it. You might add a belief only you know about, such as "we think the free trial is too short," or remove one that doesn't matter to this decision. Once you agree on the list, every question in the guide traces back to one of these beliefs, so you can see why each question is there.
What questions should I ask in a customer discovery interview?
The best discovery questions ask customers to describe a specific moment from their own past. People are poor at predicting what they would do, and they are generous when asked for opinions, but they remember what happened last Tuesday. Kite writes the guide around those moments.
A typical guide from Kite moves through the customer's story in order:
- The trigger. "Think back to when you first started looking for something like this. What was going on that week?"
- The old way. "Before you used us, how were you handling it? What did that cost you?"
- The search. "What else did you look at? How did you hear about each one?"
- The decision. "Who else had a say? What made you pick this one over the others?"
- The doubt. "Was there a point where you almost didn't buy? What happened?"
- The result. "What's different now? If we disappeared tomorrow, what would you do instead?"
Kite adapts these to your business and your list of beliefs. For the restaurant example, the trigger question might become "Tell me about the last time a schedule went wrong. What happened?" It also adds follow-up prompts under each main question, such as "Can you walk me through that?" and "What did you do next?", because the useful detail usually comes in the second or third answer.
Different people need different guides. Kite can write separate versions for recent customers, customers who left, prospects who chose a competitor, and people who match your ideal customer but have never heard of you. Each version keeps the same beliefs, but the questions fit what that person has actually experienced.
How do I avoid leading questions in customer interviews?
A leading question is one that tells the customer which answer you're hoping for. The fix is to ask about what happened instead of asking for a reaction to your idea, and Kite checks every question in the guide for this before you see it.
Kite rewrites a question when it names your product's benefit, offers the answer inside the question, or asks the customer to imagine a future. Here are a few examples of the rewrites it makes:
- "Would faster setup be valuable to you?" becomes "How long did it take to get set up, and what happened during that time?"
- "Do you find our reporting easier than spreadsheets?" becomes "How did you put together your last report?"
- "Would you pay more for a mobile app?" becomes "When was the last time you needed to do this away from your desk? What did you do?"
Kite also keeps your own messaging out of the questions. If your positioning calls the product "the scheduling assistant for multi-location teams," the guide never uses that phrase. That way, if a customer describes the product in those words, you know the words came from them, which is exactly what you want to find out.
The guide also includes a short note for the interviewer. It reminds you to let silences run, to ask "why?" when an answer sounds rehearsed, and to save any demo or pitch until the end of the call.
How do I prepare for customer interviews?
Preparing for customer interviews means choosing the right people, inviting them in a way they'll accept, and knowing the guide well enough to follow the conversation instead of the script. Kite handles the first two and makes the third easier.
To choose the people, Kite works from your ideal customer profile and the decision you're making. If you connect your CRM, Kite looks through it for recent customers, customers who left, and deals you lost, and proposes a short list with a reason for each name. If you want to talk to people who have never bought from you, Kite can use its built-in research sources to find people who match your ideal customer by role, company size, and industry.
Next, Kite writes the recruiting email. It explains why you're reaching out, how long the call will take, and what the person gets for their time, and it's written so the recipient knows you want to listen rather than sell. Kite also writes a short screener of two or three questions that confirms each person fits before you book them. Kite shows you the email first. Approve it, and Kite sends it from your team's Kite email address or a connected email product, then tells you who replied.
Finally, Kite gives you two versions of the guide. The full version holds the beliefs, the reasoning behind each question, and the follow-up prompts. The one-page version holds only the main questions in order, so you can keep it open during the call without reading from it.
Turn your notes into findings
The interviews are only useful once you know what they changed, so Kite reads your notes after each round and writes up what you learned against the beliefs you started with. You run the conversations yourself. Kite does the preparation before and the analysis after.
You can share notes or transcripts by uploading them in the Kite web app, sharing them in a Slack thread, or pointing Kite to a folder in your connected Google Drive. Kite reads them and reports, belief by belief, whether the interviews supported it, contradicted it, or left it unclear. It also pulls out the trigger that sent each person looking, the objections they raised, the alternatives they considered, and the exact words they used, with each quote kept word for word and tied to the interview it came from.
Kite then saves the conclusions in your team's knowledge base, updating your ideal customer profile and messaging notes. Every page, ad, and email Kite writes afterward starts from what your customers actually told you. If the findings show that your homepage is telling the wrong story, Kite can draft the rewrite and show it to you before anything changes on your site.
What you get
A list of the beliefs you're testing
The assumptions your decision depends on, written plainly so you can agree on them before any interview is booked.
A full interview guide
The opening, the main questions in order, the follow-up prompts under each one, and a note on which belief each question tests.
A version for each group you're interviewing
Separate guides for recent customers, customers who left, lost deals, or new prospects, when you need them.
A recruiting plan
A proposed list of people to talk to with a reason for each, a recruiting email, and a short screener.
A one-page guide for the call
Just the questions, in order, for you to keep open while you listen.
Findings after the interviews
What the interviews showed about each belief, with the triggers, objections, alternatives, and customer quotes behind it, saved to your knowledge base for later work.
How to get started
Sign up with your company's website and choose whether to work in the Kite web app or in Slack. Kite researches your business on its own, so it already knows your positioning and customers by the time you ask. Then tell Kite what decision the interviews are for. You might say, "We're about to rewrite our homepage. Write a guide for interviewing ten recent customers," or "Help me understand why trial users don't convert."
Kite sends you the list of beliefs first. Change or approve it, and Kite writes the guide. If you want help recruiting, connect HubSpot or Salesforce so Kite can find the right customers, then approve the recruiting email before it goes out.
When the interviews are done, upload your notes or transcripts in the conversation and ask Kite what you learned.
Integrations used to write a customer interview guide
Kite writes the guide from its own research and what it knows about your business, so you can get a first draft without connecting anything. Connecting your CRM helps Kite choose who to interview, and connecting Google Workspace makes it easier to share the guide and bring in your notes.
Choose who to interview
Common questions
How many customer interviews do I need?
For one decision and one type of customer, five to ten interviews usually show the pattern. You'll know you have enough when new conversations stop surprising you. If you sell to several distinct groups, such as owners and managers, plan five or more for each group, because their answers rarely agree. Kite tracks which beliefs are still unclear after each round, so you can see whether a few more calls would settle them.
How long should a customer interview be?
Plan for 30 to 45 minutes. That's enough time to walk through one buying story in detail without tiring the customer out. Kite writes the guide to fit the length you choose and marks which questions to skip if the conversation runs long, so the most important beliefs always get covered.
What's the difference between a customer interview and a survey?
An interview tells you why, and a survey tells you how many. Interviews are the right tool when you don't yet know the reasons behind a behavior, such as why people switch or what nearly stops them. Once the interviews show you the reasons, a survey can measure how common each one is across a larger group. Kite can draft that follow-up survey from the interview findings.
Should I offer an incentive for a customer interview?
An incentive helps, especially with people who aren't customers yet or who have already left. A gift card or a credit on their account is common for a 30-minute call. Current customers who like the product often agree without one, but a small thank-you still raises the reply rate. Kite includes the incentive in the recruiting email when you tell it what you're offering.
What should I do with the findings?
Start with the beliefs that turned out to be wrong, because those are the places your messaging or roadmap is pointing in the wrong direction. Kite saves the findings to your ideal customer profile and messaging notes, so its later work reflects them. It can also check your website and ads for pages that still tell the old story and draft a rewrite for each one.