Skip to content
Founder Workflows
Browse
Browse by stage

Prepare, synthesise and rehearse customer discovery interviews with Claude without letting it do the thinking

A field guide on using Claude before and after customer interviews: drafting hypothesis-testing questions, synthesising notes across calls, and role-playing a skeptical buyer.

Evidence: The author reports this. We have not checked it beyond reading the source.

The business problem

Founders testing an idea often ask leading questions and drown in unstructured interview notes, so they miss patterns across conversations.

What was tried

Before interviews, the founder gives Claude their role, hypothesis and suspected problem and asks for about ten open-ended behavioural questions. They run the interviews themselves, without AI present, and write rough notes within ten minutes. Afterwards they paste redacted notes into Claude to find recurring complaints and questions they should have asked, then have it organise rough insights into a shareable summary. An optional step has Claude play a customer to push back on leading questions before real calls.

What was reported (not reported)

The guide reports no measured results or case studies. It claims synthesis saves about two hours of sorting notes, without evidence.

Limitations

The guide has no stated author or publication date and shows no results. It says Claude cannot tell whether a hypothesis is true, simulated customers reflect general patterns rather than your actual customers, and it cannot reveal blind spots you do not already have. Notes should be redacted of sensitive information before pasting.

What you need

A testable hypothesis, access to real potential customers, and your own interview notes. The Claude plan or model is not stated.

Sources

Source published: unknown. Last reviewed here: October 11, 2026. Spot a mistake? Tell us.

Tools in this workflow

Related workflows