The Brand Coffee Chat is rarely where people hesitate.
It’s free, it’s an hour, and there’s no obligation attached to it — which makes it a genuinely easy thing to say yes to. Most people leave the call having enjoyed it. The hesitation, when it comes, arrives later. Usually a few days after, once the proposal’s landed and there’s an actual decision to make.
That gap deserves more honesty than it usually gets, on both sides.
What “let me think about it” is actually asking
There are really two different questions hiding inside that sentence, and they call for completely different responses.
The first is about timing. Is this genuinely the right moment — budget, priorities, everything else going on in the business right now. That’s a legitimate question, and the honest answer is sometimes no, not yet, and that’s fine.
The second is about trust. Not “is now the right time” but “am I sure about this person, this way of working, this specific relationship.” That one’s harder to say out loud, because it can feel like a personal judgement rather than a practical one. But it’s just as legitimate, and pretending it’s really the first question when it’s actually the second doesn’t help anyone get to a clear answer.
What a good proposal is supposed to do
A proposal that’s done its job removes the first kind of hesitation almost entirely. Clear scope, a price that’s the price, no vague language doing the work that a specific commitment should be doing. If a change comes up later, that’s a conversation before it’s a cost, not an invoice that arrives with a surprise attached to it.
That standard matters more than it might sound like it does. A vague proposal doesn’t just risk a dispute later. It creates a specific kind of anxiety in the gap before someone decides — a nagging sense that the real scope, the real cost, hasn’t quite been said out loud yet. That anxiety gets misread as hesitation about the project itself, when it’s really just a reasonable response to an unclear document.
What a proposal can’t do is manufacture trust that isn’t there yet. That’s not a flaw in the proposal. It’s just not what proposals are for. Trust comes from the call, from the reputation, from a conversation with a past client if that’s what’s needed — not from a document, however well it’s written.
The three conversations underneath a yes
Long before any of this reaches a proposal, there are three things worth being honest about, with yourself as much as with anyone else: ambition, doubt, and truth. What you actually want the business to become. What you’re genuinely unsure about, including whether now is the right time at all. And what’s actually true about where things stand, rather than the version that sounds better in a meeting.
A yes that skips past any of those three tends to surface again later, usually at a more expensive point in the project than if it had been said plainly at the start. I’d rather have the doubt conversation on the phone, before anything’s signed, than watch it show up three weeks into a project as a client who’s quietly disengaged and can’t quite say why.
Why “not yet” is a perfectly good answer
Not every Brand Coffee Chat is supposed to end in a project. Sometimes the honest outcome is that the timing’s wrong, or the fit isn’t quite right, or there’s a more urgent problem to solve first. None of that is a failure of the call. Saying “not yet” clearly is a far better use of everyone’s time than a slow, unspoken drift away from a maybe that was never going to become a yes.
If you’re currently sitting with a proposal and a “let me think about it” you haven’t quite examined, it might be worth asking yourself honestly which of the two questions you’re actually stuck on. The answer to that usually tells you more than another few days of thinking about it in the abstract.
More on what that first conversation actually covers at pattendesign.co.uk/services/.
