“Yes” is an easy response when a client asks “Can you do this for us?”
Say yes, and figure it out later, right?
And sure, sometimes it works out in your favor and you get to explore.
Other times, that “yes” should have been a “no.” It can get you into sticky situations where you’re not able to deliver what you promised. If that happens during a discovery, let the prospect know you don’t have the specific experience they’re looking for. If you’re interested, let them know about other projects, even if you haven’t done the exact same thing.
It’s a pretty simple conversation:
Client: Have you done X before?
You: No, but I’ve done Y and Z, and here’s how the projects are similar. I wanted to make you aware that I haven’t done anything exactly like this.
The “yes” would gloss over the lack of experience, or tell the client that you have done the same type of project before (that’s stretching the truth). The “no” version is more honest: you might not be the right fit.
If the client really wants to work with you, the lack of specific experience won’t be an issue. They’ll see the potential based on your other work.
If the prospective client says, “Sorry, but we need someone with specific experience” then you’ve potentially avoided disaster. You could have ended up with a terrible project and an unhappy client rolled into one.
This tactic can also work with existing clients. One particular client hired me to do one type of work, but then assigned something different. I had to let the client know that the work was not in my wheelhouse by saying:
“Hey, I don’t think I’m the right fit for X, because my specialty is Y.”
Suddenly, the client was interested in Y.
I earned their trust by admitting that I didn’t feel good about the work.
It was a risk: I could have lost the client altogether. But the alternative for the client was losing a good writer and finding a replacement. Better that we keep talking, prepare ourselves, and find a way to work together.
Facilitator, consultant, coach & speaker on strategy, high performance and leadership.
1moWhy chasing revenue without strategy is bad for business: https://www.jamesallen.online/inside-track/why-chasing-revenue-without-strategy-is-bad-for-business