Founders often hesitate to book a free call because the format is unclear โ is it a sales pitch in disguise, a real conversation, or something else? Here’s exactly what happens, removing the guesswork, since knowing this in advance makes the actual call more useful for both sides.
What it’s not
Not a scripted sales pitch working toward a predetermined close. Not a generic “tell me about your idea” conversation that could apply to any founder. Not a technical interview testing whether you deserve help. It’s closer to a working session โ genuinely trying to get useful clarity in 30 minutes, whether or not it leads to working together afterward.
The actual structure, minute by minute
First 5-10 minutes: understanding the real problem, not the pitch version of it. Most founders arrive with a solution already in mind; the first part of the call is often gently working backward to the actual problem being solved, since the stated solution and the real underlying problem don’t always match.
Middle 10-15 minutes: the core of the call โ a direct, honest read on what’s actually needed. This might mean telling a founder their idea needs more validation before any building starts, that their budget doesn’t match their stated scope, or that the specific approach they’re planning has a specific, fixable flaw. This is the part that’s most valuable and also the part some founders find uncomfortable, because it’s not automatic validation of the existing plan.
Final 5-10 minutes: concrete next steps, whether or not that involves working together. If it makes sense to build something, what that would actually look like โ rough scope, realistic budget range, realistic timeline. If it doesn’t make sense yet (more validation needed, wrong stage, wrong fit), saying so directly rather than pushing toward a sale that wouldn’t actually serve the founder.
What determines whether it turns into paid work
Genuine fit โ a validated-enough idea, a realistic budget for the actual scope, and alignment on how the relationship would work (the selective-client-intake piece covered elsewhere on this site is relevant here). Roughly a third of these calls conclude with “here’s what to go figure out first, come back after,” which is a genuinely good outcome for the founder even though it’s not an immediate engagement.
What to bring to get the most value
A specific description of what’s being built and for whom โ not a polished pitch, just clarity on the actual problem and who has it. Any validation work already done, even informal. A real budget range, even an uncertain one โ “I don’t know” is a fine answer, but having thought about it at all helps the conversation move faster to something useful.
What happens after the call
If it’s a fit: a follow-up with a rough scope document and realistic estimate within 24 hours, not a high-pressure immediate close. If it’s not yet a fit: specific guidance on what to do next, and an open door to come back once that’s done. No pressure either direction โ the call is genuinely trying to be useful regardless of whether it converts to paid work.
Want an honest read on where your project actually stands? Send me a few lines about what you are building. Free 30-minute call, no pitch, no obligation. Available for founders in India and Australia. Book a Free Call →
Frequently asked questions
Is a free MVP clarity call actually a sales pitch?
No โ it’s structured as a working session focused on getting the founder useful clarity, whether or not it leads to paid work. Roughly a third of these calls conclude with guidance to go do more validation first, not a sales push.
What should I prepare before a startup discovery call?
A clear (not polished) description of the problem and who has it, any validation already done even if informal, and a rough budget range if you have one โ “I don’t know” is fine too.
How long does a typical MVP clarity call take?
About 30 minutes, structured roughly as: understanding the real problem (5-10 min), honest assessment of what’s actually needed (10-15 min), and concrete next steps (5-10 min).
What happens if my idea isn’t ready for a full MVP build yet?
You’ll be told directly, with specific guidance on what to validate or clarify first, rather than being pushed toward a build that wouldn’t actually serve the idea at its current stage.