What a first call tells you that a proposal can't
Proposals are theater. Everyone submits a polished deck: case studies chosen to flatter the brief, a timeline that looks confident, a scope section written to sound thorough without committing to much. By the time a proposal lands in someone's inbox, most of the useful information has already been smoothed out of it.
The first call is where the real information actually shows up. Not in what gets said, but in what the conversation reveals about how decisions get made on the other side — who's actually in the room, whether there's one decision-maker or a committee that hasn't agreed on anything yet, whether the brief in front of me matches what's actually happening inside the company.
There's a specific signal I listen for early: does the person on the call describe a symptom, or a diagnosis? "Our conversion rate dropped" is a symptom. "We need a redesigned checkout flow" is a diagnosis someone already reached — sometimes correctly, often not. The gap between those two tells me how much of this project is going to be design work, and how much is going to be figuring out what the actual problem is before any design work can start.
I also listen for how someone talks about budget and timeline. Vague budget paired with a hard deadline usually means the timeline was set before anyone scoped the work — which tells me more about the project's risk than anything in the RFP.
A good first call changes the proposal I end up writing. Sometimes it changes the price. Sometimes it changes the scope entirely. Occasionally it changes whether I write one at all.
