I'm a solo founder developing a SaaS tool for freelance graphic designers, and I've built an MVP based on my own pain points, but I know I need proper market validation before investing further. I'm planning to conduct interviews with potential users, but I'm unsure how to structure the conversations to get beyond polite feedback and uncover genuine needs and willingness to pay. For other founders who have gone through this early stage, what interview questions or validation techniques yielded the most honest and actionable insights, and how did you differentiate between a "nice-to-have" feature and a true problem worth solving?
Great idea. I’d run a two-phase interview: (1) discovery to map their current workflow and pain points, then (2) a lightweight validation step where you demo or simulate the MVP in a hands-off way if possible. Here’s a concise question set you can adapt for 25–40 minute calls:
- Tell me about your typical design workflow from brief to delivery. What are the bottlenecks?
- Which task takes the most time or causes the most back-and-forth with clients?
- How do you currently organize briefs, revisions, and asset handoffs? What would a perfect system do better?
- What tools do you rely on now, and what do you wish they did that they don’t?
- What’s the biggest frustration you’d want solved in the next 6–12 months?
- Have you tried any automation or templates? What actually saved time, and what didn’t?
- If a tool could reduce your rework by a noticeable amount, what would that translate to in hours per project?
- What would be the minimum features that would make you consider replacing a current tool?
- How much would you be willing to pay monthly for a tool that reliably saves you time on client work? a rough range is fine.
- Who would need to approve a new tool, and what would their risk concerns be?
- What would push you away from adopting a new platform (security, onboarding time, compatibility, data ownership)?
- If I offered a 14‑day free trial, what would you need to see to decide it’s valuable?
Tip: keep a short “non-judgmental” baseline for notes and save audio if they agree, so you don’t bias answers when you transcribe.
If you want, I can tailor this to your target user segment (graphic designers vs studios) and provide a ready-to-record script.
2) Validation techniques you can try with limited resources:
- Concierge MVP: do the work for them yourself behind the scenes for a sample project (same three-to-five steps) and measure interest and outcomes.
- Landing page with a value proposition and a waitlist sign-up to gauge demand and willingness to wait/pay.
- Paper prototype or screencast: walk through the flow with screenshots and ask where it’s clear or confusing.
- Wizard of Oz: promise functionality that’s mostly manual behind the scenes to test perceived value.
Choose one approach and run a 2–3 week test to quantify interest (signups, time saved, willingness to try, etc.).
3) How to differentiate a nice-to-have from a must-have:
- Ask for a concrete outcome: “If this feature existed, how many hours would it save you per project?” and “Would you switch away from your current tool because of it?”
- Track willingness to pay against estimated time saved; features tied to measurable outcomes (time, revenue per project) tend to convert.
- Score each feature on: urgency, frequency, monetary impact, and effort to use.
If you want, share a bit about your target customers (solo designers, small studios, geographic markets) and I’ll draft a tight starter interview guide and a one-page validation plan you can run this week.