Most advice on customer discovery calls is impractical for solo founders. Books tell you to schedule 45-minute philosophical interviews with 30 target executives to explore their “daily workflows.”
In reality, busy decision-makers do not have 45 minutes to chat with an unproven founder about abstract theories.
Even worse, founders often fall into the “politeness trap”: they pitch their product idea, the interviewee says “That sounds really cool! I’d definitely use that!”, and the founder walks away believing they validated a winning startup idea.
Six months later, when the product launches and the founder asks for a credit card, those same enthusiastic interviewees disappear completely.
The goal of a discovery call is not to hear compliments; it is to uncover existing commercial pain and current software budgets.
Here is the tight, 15-minute customer discovery script I use to separate polite lies from real commercial demand.
The 15-Minute Rule: Why Short Calls Win More Meetings
When asking for discovery calls via LinkedIn or email, never request 30 or 60 minutes. Request 15 minutes flat:
“Hi [Name], I’m researching how independent law firms manage document redaction bottlenecks. I’m not selling any services. Do you have 15 minutes this Thursday for a quick, tightly focused chat? I promise to keep strictly to 15 minutes.”
People agree to 15 minutes because it fits between meetings. It demonstrates that you respect their time.
The 4-Question Discovery Framework
Spend zero time showing slides or demoing wireframes. Open a scratchpad and ask these four specific questions:
1. “What is the hardest part of [specific process] today?”
Keep it open-ended. Let them vent about their actual friction points rather than leading them toward your preconceived software solution.
If they respond with mild, cosmetic annoyances, their pain is low. If they sigh and launch into a story about staying late until 9:00 PM fixing broken CSV files, you have found real operational friction.
2. “When was the last time this happened, and how did you resolve it?”
Validate whether the problem is frequent and recent. If the last time they faced this issue was eight months ago, it is not an urgent, top-of-mind priority.
Ask what workaround they used. Did they write an internal spreadsheet? Pay a contractor? Spend four hours manually copy-pasting? Workarounds prove the problem is acute enough to force action.
3. “What tools or solutions have you actually paid money for to fix this?”
This is the most critical question in the entire call.
If an operator tells you a problem is terrible, but admits they have never spent a single dollar or dedicated an hour searching for software to fix it, they will not buy your product either.
Willingness to pay is demonstrated by past behavior, not future promises. Look for active subscriptions: “We currently pay $150/month for Tool X, but it doesn’t support batch exports.” That is a qualified buyer with an active budget line item.
4. “If a dedicated tool solved this exact problem tomorrow, whose corporate credit card would approve the $49 to $99/mo charge?”
Identify whether the person you are speaking with is the economic buyer.
If they say: “Oh, our IT procurement committee reviews new software once a year in November”, you are dealing with enterprise procurement hurdles.
If they say: “I have a $500 monthly discretionary expense limit on my corporate card”, you have an immediate self-serve path to market.
Wrap-Up and Next Steps
At the 14-minute mark, deliberately pause the call:
“We are at 14 minutes and I promised to keep this to 15. This was extraordinarily helpful. We are building a lightweight solution specifically to solve that CSV export issue you mentioned. May I email you when our private beta is ready so you can test it on real files?”
If they enthusiastically agree, you have not just validated a concept—you have secured your very first beta prospect.
Related Operational Guides
For more idea validation and micro-SaaS framework blueprints, read: