Captain’s log, stardate 20220305
Buyers who are working with limited knowledge will often self-diagnose and prescribe the only solution that they are aware of.
Then, they reach out to sellers who provide this solution and ask for it directly.
“Hey doc! My chest has been hurting. I Googled around and apparently I need a triple bypass. When can we start?”
The issue here is not that there is actually only one solution to the client’s problem, it’s that the client is only aware of one solution and is asking for it directly.
A doctor would never accept a client’s self-diagnosis and neither should you.
Your clients don’t really want hours or words or revisions or code or features or websites or photos or videos or illustrations or contracts or blueprints or any other sort of inputs or deliverables from you.
What clients REALLY want are benefits.
Unfortunately, prospective clients almost never spontaneously share their desired business outcomes with you in a sales interview.
So how do you find out what your clients REALLY want?
At some point in your initial meeting with a prospective client, they will brain dump about the proposed project for about 20 minutes.
There might not be much useful information in this monologue, but you have to let them get it off their chest before you can get down to the heart of the matter, which is this:
Why they want to do the project at all?
Questioning the premise of the project before they do the dump will frustrate or confuse them. They will gloss over the answer so they can jump to the dump.
So... you have to let them get it out of their system. Keep your mouth shut and let them vent. When they finally come up for air, you say:
“Thanks for that. Lots of helpful information here. Can we back up for a sec?”
Good clients will say, “Sure!”
And then you ask some variation of this:
“Why is this project becoming a priority now? Has something changed?”
Typically, they’ll have shared something in the dump that you can use to make this question more specific, like:
Once you’ve started asking these sorts of “Why” questions, you keep doing it...
Don’t stop asking Why questions until you are convinced that you are - or are not - a good fit for the project.
The Why Conversation
For obvious reasons, I refer to this as the “Why Conversation”. Having a Why Conversation sort of feels like trying to talk the prospect out of hiring you, because... well, you kind of are trying to talk the prospect out of hiring you.
If you CAN talk them out of hiring you, then they didn’t need you that badly (i.e., the perceived value of your engagement was low, which means you couldn’t have charged much).
If you CAN NOT talk them out of hiring you, then as they answer each Why question, one by one, they’ll be convincing themselves that you are the best option.
By the end of a successful Why conversation, you’ll have something to base your fee on because you’ll have learned:
Once you have this info, you can start to wrap the meeting and go write a proposal that is focused on what the client REALLY cares about.
P.S. Do you dread writing proposals? Does it take you forever? Do you always feel like you’re winging it? Are you just making stuff up, trying to sound professional?
The entire first week of The Pricing Seminar is devoted to learning, once and for all, how to write killer proposals in record time.
The 9th session of TPS is launching very soon, so add your name to the announcement list for a shot at the early bird pricing:
Get Notified »
I hope to see you there!