Customer Interview Template for Indie Builders

Most indie builders skip customer interviews because they feel awkward, unstructured, or like a waste of time. A solid customer interview template fixes that. It gives you a repeatable script so you can walk into every conversation knowing exactly what to ask and walk out with insights you can actually use.

This template is built specifically for solopreneurs and side project makers. No corporate jargon, no 60-minute marathon sessions. Just the questions that matter.

Before the Interview

Prep takes 5 minutes. Do it every time.

• Pick one goal per interview. Are you validating a problem, testing a solution idea, or understanding a workflow? Don't try to do all three.
• Find the right person. Talk to people who already experience the problem, not friends who will be nice to you.
• Keep it short. 15 to 20 minutes is plenty. Respect their time and you'll get more honest answers.
• Record it (with permission). You'll forget the best stuff otherwise. Otter.ai or your phone's voice recorder works fine.

The Customer Interview Template

Here are the exact questions, grouped by phase. Copy them into a doc and bring them to every call.

Opening (2 minutes)

• "Tell me a bit about what you do day to day."
• "How does [topic area] fit into your work right now?"

These warm-up questions get them talking without leading them anywhere specific.

Problem Discovery (8 minutes)

• "What's the hardest part about [problem area] for you?"
• "Walk me through the last time you dealt with this. What happened?"
• "What did you try to solve it? How did that go?"
• "How often does this come up?"
• "What happens if you just ignore it?"

This is where the gold is. Listen for emotion, frequency, and failed solutions. If someone tried to solve it and couldn't, that's a real problem. If they shrug and say it's fine, move on.

Current Solutions (5 minutes)

• "What tools or workarounds are you using today?"
• "What do you like about your current approach?"
• "What's frustrating about it?"
• "Have you paid for anything to solve this? How much?"

The last question is critical. Willingness to pay (or already paying) separates real pain from mild inconvenience.

Closing (3 minutes)

• "If you could wave a magic wand and fix one thing about this, what would it be?"
• "Is there anyone else you know who deals with this same problem?"
• "Can I follow up with you when I have something to show?"

That second question is your referral engine. One good interview often leads to two more.

What to Do After the Interview

Don't just file your notes away. Within 24 hours:

1. Pull out the top 3 insights. Write them as direct quotes when possible.
2. Tag the pain level. Score it 1 to 5 based on how much they cared.
3. Look for patterns. After 5 interviews, you'll start hearing the same problems repeated. That's your signal.
4. Update your positioning. Use their exact words in your landing page copy. The phrases real users say will always outperform what you'd write on your own.

Common Mistakes to Avoid

• Pitching your idea. This isn't a sales call. If you're talking more than 30% of the time, you're doing it wrong.
• Asking yes/no questions. "Would you use a tool that does X?" always gets a yes. It tells you nothing.
• Interviewing only one type of person. Talk to power users, casual users, and people who quit. The quitters often teach you the most.
• Waiting until you have a product. Run interviews before you write a single line of code. Five conversations can save you months of building the wrong thing.

From Interviews to Distribution

A customer interview template helps you build the right product. But building the right product is only half the battle. You also need to show up where your users already hang out, using language that resonates with them.

That's the part most indie builders get wrong. They build something great, then post it in the wrong places or describe it in ways that don't connect.

Want to find out where YOUR users actually are? Try the free Stride audit