What happens on the first call.

Process · 5 min read

Most people who book the call have been sitting on their idea for months. Some for years. They've finally decided to talk to someone about it, and now they're wondering what to expect. Will it be a sales pitch? Will I be judged? Do I need a document or a presentation? The answer to all three is no.

The first call is a conversation. That's it. You talk. I listen. I ask questions. And by the end, you'll have a clearer picture of where you stand, what the next steps look like, and whether working together makes sense. No pressure. No pitch. No commitment. Here's how it actually goes.

You tell me about your idea

I'll ask you to describe your app idea in your own words. Not in tech language. Not in a polished pitch. Just tell me the problem you've seen, who it affects, and what you think the solution looks like. Most people start with the problem, and that's exactly where I want you to start.

Don't worry about having all the answers. Half the people I talk to say "I don't even know if this is a good idea" within the first two minutes. That's fine. That's what the call is for. I'll help you figure out whether the idea has legs and what's realistic as a first step.

You don't need a spec. You don't need wireframes. You don't need a business plan. If you've got notes on your phone or a list in a notebook, that's more than enough. Some of the best conversations start with "I've had this idea for years and I've never told anyone."

I'll ask you some questions

I'll ask about your users. Who are they? How do they currently solve this problem? What makes your approach different? I'll ask about your industry. Are there compliance requirements? Is there specific terminology or workflow that the app needs to reflect? I'll ask about your goals. Is this a business? A side project? Something you want to eventually sell?

These questions aren't a test. They're how I figure out where your idea sits in terms of complexity and readiness. Some people come in with a clear vision and just need someone to execute it. Others come in with a gut feeling and need help shaping it into something buildable. Both are valid starting points. The questions help me understand which one I'm working with.

What you'll walk away with

By the end of the call, you'll know three things. First, whether your idea is ready for the design phase or whether it needs more homework first. Second, what the process looks like: the phases, the timeline, the deliverables. Third, a rough sense of investment, not a fixed quote, but enough to know whether this is in your range.

If I think your idea isn't ready, I'll tell you. I'll explain what I think is missing and what you should do before investing in design. That's not me turning you away. That's me protecting your money. A project that starts before it's ready costs more and takes longer than one that starts at the right time.

And if it's not the right fit, I'll say that too. Sometimes the scope is outside what I do. Sometimes the budget doesn't match the ambition. I'd rather have an honest conversation that saves you time than string things along hoping something works out. You'll always leave the call knowing exactly where you stand.

Sources
Stakeholder Interviews (Nielsen Norman Group) - Why discovery conversations produce better product outcomes.
Conducting User Interviews (Interaction Design Foundation) - The value of open-ended conversations in understanding user needs.

Related blog posts:

How to prepare for your first app design project →

Don't forget to do your homework →

How to validate your app idea →