Losing a client to a cheaper competitor stings.
It stings more six months later when that client comes back because the cheaper option did not work out.
This happens more than you think. And how you handle it when they return determines whether you get the project or spend the conversation being right about how you warned them.
Why clients come back
Lower-priced developers often underdeliver. Not always. But enough that a significant portion of clients who leave for price reasons discover that the savings were not real when you factor in revisions, delays, miscommunication, and having to redo parts of the work.
When that happens, they often reach back out to the developer they felt confident about in the first place.
How to respond when they come back
With warmth, not with "I told you so."
The client already knows they made a mistake. Rubbing it in might feel satisfying for five seconds and will cost you the project.
The right response: "Good to hear from you. What are you working on?" Treat it like any new project inquiry.
How to price the returning client
At your current rates.
Not at a discount to win them back. Not at an inflated rate to punish them. At the rate you would charge any serious client today.
If they left because of price before, they may push back again. The conversation is easier now because they have context for what below-market rates actually deliver.
How to prevent losing them to price in the first place
The main reason price becomes the deciding factor is that the client does not see enough differentiation between options.
When all developers look similar on paper, price is the rational tiebreaker.
Your job is to create visible differentiation before the comparison happens. A specific positioning statement. A proposal that demonstrates you understood their problem. References from similar clients. A discovery process that shows you take projects seriously.
None of these eliminate price sensitivity. They all reduce it.
The honest version of losing to a cheaper competitor
Sometimes the client goes with the cheaper option and it works out fine. The project is simple enough that any competent developer would deliver it.
In those cases you did not lose because you were more expensive. You lost because the project did not justify the premium.
The fix is not to lower your rates across the board. It is to focus on projects where the complexity, stakes, or specificity of your expertise actually justify what you charge.
The Freelance Command Center includes a proposal system to help you differentiate before the price conversation. EUR 17.
Top comments (0)