By Touchbase Technologies · Published 2026-11-04

A First-Customer Interview Notes Template You Can Use

A useful customer interview can become a weak product decision if the notes blur what someone said with what the founder wanted to hear. “They described a difficult handoff” and “they want our platform” are different statements. A clear notes template helps you keep that difference visible after the conversation ends.

Record the situation and task; Capture the actual evidence; Label your interpretation; Choose the next question.

Use the template below for an early conversation about a product or service. It is an original working tool, not a scoring system that predicts purchases. The worked example is fictional. Adapt the fields to your task and collect only the information you need to understand the problem and the agreed next step.

Write the research question before the call

Begin with the decision you are trying to inform. For example: “We want to understand how a small service team assigns an incoming request.” That is more useful than “We want feedback on our idea,” because it identifies a process you can investigate.

Record the hypothesis separately. You may suspect that a team loses context when a request moves between people. The interview should let you find out whether that happens and what it means to the participant. If their process works well, preserve that finding rather than treating it as a disappointing answer to rewrite.

Choose the participant because they know the task, not simply because they are available. A person who sees only the final report may have a different perspective from the person performing the handoff. Both can be useful when you identify the perspective in the notes.

Use one structured page for each conversation

Keep the record easy to scan. A concise, accurate page can be more useful than a long transcript nobody reviews. Include enough context for a colleague to understand which process and perspective the conversation represents.

Field	What to record	Example prompt
Research question	The decision the interview should inform	What do we need to understand?
Participant context	Role and relevant working situation	Which part of the task do they know?
Recent example	A specific event described in sequence	What happened last time?
Evidence	Exact words or clearly identified observations	What was actually said or shown?
Interpretation	Your explanation or hypothesis	What might this mean?
Unknowns	Information still missing	What should we ask next?
Next action	An agreed step with an owner	Who does what after the call?

Do not turn an uncertain field into a complete-looking answer. “Not discussed” can be more valuable than an invented estimate. It tells the next interviewer where the evidence stops.

Capture a recent example in sequence

Ask the participant to walk through an ordinary recent task. Record where it began, what information was available, who took the next action and what happened after that. Keep the order clear enough that someone can reconstruct the handoff.

If you lose a step, ask a clarifying question. “What happened between receiving that message and assigning the task?” can be more useful than asking whether the process is inefficient. A participant may describe a sensible reason for a step you initially considered unnecessary.

Separate the tools used from the problem experienced. A spreadsheet, email thread or manual note is not automatically evidence of a bad process. Record what the person needed to accomplish and where, if anywhere, the existing approach became difficult.

Keep direct words distinct from your summary

Use quotation marks only for words you captured accurately. If you are summarizing, label the statement as a summary. This prevents a polished note from acquiring more authority than the original conversation supports.

For example, a participant might say, “I check the shared list before asking who has it.” Your summary could be: “The coordinator checks a shared list to find responsibility.” Your interpretation might be: “A clearer owner field could help.” Those are three related records with different levels of certainty.

If you record or retain a fuller conversation, use an appropriate process with the participant. The notes template can still be useful without a recording. A short clarification after the call may be enough to correct an ambiguous point.

A worked example

Imagine a founder interviewing a fictional design-studio coordinator about feedback on deliverables. The research question is how feedback reaches the person responsible for revising a design. The coordinator describes receiving comments in a client email, adding them to a task and asking a colleague whether the latest file has been attached.

The evidence note should preserve that sequence. A suitable interpretation could be: “The handoff depends on identifying the current file before the revision begins.” An unknown is whether the same issue occurs regularly or only in this particular example.

A weak note would say: “Design studios need our all-in-one review tool.” That conclusion skips several decisions. The founder still needs to learn whether the issue matters enough to change a process, whether the product supports the required workflow and who would evaluate it.

A useful next question could be: “Can you show, with a sample file, how the next reviewer identifies the current version?” That question follows the evidence instead of asking the participant to approve a product vision.

Review patterns without flattening the differences

After several conversations, compare the task, the consequence and the conditions. Two participants may use the same word for different problems. One person's “follow-up” might mean asking for missing information; another's might mean confirming that a customer received an answer.

Group observations by a clear definition and keep links to the underlying notes. Record exceptions too. A team that solved the problem with an existing process may teach you about an alternative or an adoption constraint.

The SBA business-planning resources include guidance on direct customer research. Use such resources to choose a suitable method, while keeping your own conclusions tied to the evidence you actually gathered.

Turn the notes into a product or market decision

Choose a next action that matches what you know. You may need another interview, a clearer positioning statement, a focused demo or a limited pilot. A positive conversation does not require you to immediately add the person to a sales sequence.

If the participant agrees to evaluate something, write down the task, the owner and the review question. The rental-software pilot guide shows how to make that evaluation concrete. Its structure can be adapted to a different product when you change the actual workflow and requirements.

Use the findings to improve your Touchbase product context and prospect research. A specific audience and task can make the next introduction more relevant. Review the match and prepare outreach from checked information rather than treating an interview note as proof of buying intent.

Keep the commercial handoff accurate

If a conversation becomes a sales opportunity, preserve the participant's words, the proposed next action and any unresolved requirements. The CRM handoff checklist helps a teammate continue without upgrading an observation into an unsupported promise.

Start with Touchbase Free or compare plans to connect product context, research, reviewed messages and follow-up. The value of the notes is the decision they support, not the number of fields you fill in.

Questions about interview notes

Should every interview produce a sales lead?

No. An interview can reveal a useful constraint, a working alternative or a poor audience fit. Keep research learning separate from a prospect's agreement to a commercial next step.

What if I cannot remember the exact words?

Write a clearly labeled summary and note the uncertainty. Ask for clarification when it matters. Avoid presenting a reconstructed sentence as a direct quote.

Prepared with AI assistance and checked against the sources linked in this guide.