First calls are not auditions. I am not there to impress you with stack names. I am there to learn whether I can help, and whether we would work well together across time zones and async messages.
These are the questions I keep coming back to. They save everyone months.
What breaks today?
Not "what do you want in version two." What fails now. What costs hours. What makes someone stay late. What customers complain about. What the owner has stopped trusting.
If the pain is fuzzy, we sharpen it before we talk frameworks. Vague pain becomes vague software.
Who uses this, and who decides?
A tool for five staff members is not a tool for five hundred. The person who approves budget is not always the person who clicks the buttons. I need both pictures.
I also ask who will maintain the thing after launch. If the answer is "you, forever, with no documentation," we talk about scope differently.
What systems already exist?
Almost every business has something: a store, a CRM, a shared drive full of exports, a SaaS subscription someone forgot the password to.
I want the map before I propose a new island. Sometimes the right move is connect. Sometimes replace. Sometimes do nothing for six weeks and fix the process first.
What does success look like in plain language?
"I want AI" is not a success metric. "Cut invoice prep from two hours to twenty minutes" is. "Stop losing orders when inventory sync fails" is.
We write that down. We refer back when scope creeps. Creep will happen; a shared sentence helps.
What are you willing to change?
Software cannot fix a workflow everyone insists must stay identical except faster. Real projects change habits - a field gets required, a manual step goes away, a report replaces a chat thread.
If change is off the table, I say so early. That is not a moral judgment. It is a forecast of failure.
How we work after the call
If we move forward, you get clear written next steps: proposed slice, rough timeline, what I need from you, what can wait. No trap RFP. No forty-slide response.
If we do not move forward, you still leave with a sharper picture of the problem. That is a good outcome too.
Reach out if you want that conversation. I would rather spend thirty honest minutes than six months on the wrong build.