Problem Interviews Template for AI SaaS (Copy This)

Copy this. Adapt the brackets. Run your first AI SaaS problem interview this week. Templates exist so you stop overthinking and start moving.

1. Outreach Message

Three sentences. Sent over LinkedIn or email. Notice it does not mention AI - that is intentional.

Subject: Quick research question on [workflow]

Body:

Hi [Name], I noticed [specific reason - their post, their role, their team size]. I am researching how teams handle [specific workflow] and I am not selling anything. Would you have 30 minutes in the next two weeks for a short call? Happy to share what I find.

Thanks,
[Your name]

2. Calendar Invite

Title: [Your name] x [Their name] - 30 min research chat

Description: Casual conversation. I am researching [workflow] and want to learn from your experience. No pitch, no sales. Looking forward to it.

3. The Opening (First Two Minutes)

Read this almost word-for-word the first few times. Notice the absence of AI in the framing.

"Thanks for the time. Quick context: I am researching how teams handle [workflow] right now. I am not selling anything today, I just want to learn from people who have actually lived through it. So I am going to ask mostly about your own experience and try to listen more than I talk. Cool if I record so I can focus? Happy to delete it after."

4. The Three Questions

The spine. Ask each, then follow up with "tell me more about that" until you have an actual story.

Q1 (Workflow story): "Walk me through the last time you did [specific task]. What were you trying to do, what did you actually do, what did the output look like?"

Q2 (Prior AI experience): "Have you ever tried an AI tool for this? What happened?"

Q3 (Trust boundary): "Where in this workflow do you check the output by hand? Why there specifically?"

5. The Deflect (When They Ask About Your Idea)

"Honestly, still figuring it out, that is why I am asking these questions. Can I keep poking at the workflow first and we can come back to my direction at the end if there is time?"

6. Notes Template

One doc per call.

Date: [date]
Name and role: [name, title, team size]
Audience filter match: [yes / partial / no]

Workflow story (Q1): [specific incident, with one direct quote]

Prior AI experience (Q2): [tools tried, why they stuck or did not, exact failure modes]

Trust boundary (Q3): [where AI is welcome, where human review is required, why]

Cost data: [time, money, contractor hours invested today]

AI vocabulary: [exact phrases they used about AI - hallucinated, cooked, etc.]

Surprises: [what I did not expect]

Private hypotheses: [model/architecture ideas - DO NOT share with interviewee]

7. Follow-Up Message (Within 24 Hours)

Hi [Name], thanks again for the time today, that was genuinely helpful. One favor: would you be open to a 15-minute follow-up if I have something concrete to show in the next month or two? No pressure either way.

Thanks,
[Your name]

8. Synthesis Block (Every 5 Calls)

New doc. Answer using only quotes and behaviors from the last five calls.

If those answers point in a clear direction after fifteen calls, you have warranted confidence. Pick a model and ship the smallest version that respects the trust boundary.