Customer focus is not the same as servility.
A common mistake made by entrepreneurs, consultants, freelancers and, in general, anyone who deals with end customers is running their business on the premise that “the customer is always right,” justified by having a customer-oriented culture, so they tend to blindly satisfy whatever the customer asks for.
This is a serious mistake that will cost you dearly: in money, in growth, in the development of new business and in opportunity cost. You will destroy the value of your company if you keep doing this.
If it is so harmful, why do so many make this mistake? Because it is not obvious at first, when what you “think” you are selling is services, and university doesn’t teach you this. And if it does, like most things taught at university, when you don’t put them into practice, you learn them without understanding what they really mean or how they apply in practice.
The customer is not always right. On the contrary, they generally aren’t. But the real problem arises when you yourself are not clear about what your product’s value proposition is.
This goes beyond defining the initial scope of a project. It is about which things you decide to accept within that scope in the first place, and this depends on how clearly you have defined your value proposition.
Take the example of a tangible product, where the difference is easier to see. Suppose you sell a line of shampoos against hair loss, and a customer comes into your store and asks you to reformulate it because they need a shampoo against dandruff. Does it make sense to change the shampoo’s formula to meet that customer’s need? Or is your product’s value proposition NOT aimed at that customer?
Don’t get me wrong: I am not saying the value proposition never changes. It keeps iterating in response to market feedback and continuous improvement. What I am saying is that the value proposition doesn’t change because one customer asks for it; it changes when, after a thorough evaluation, you decide on that change for your market, not for a single customer. In this shampoo example, the company’s answer may not be to change the formula, but to create a new anti-dandruff shampoo line with a different value proposition.
It would be different if your value proposition were producing and selling shampoos customized to each person’s needs, but even under that model, your value proposition has to be bounded in some way.
If we agree on everything said so far, answer me this: why, if a customer asks you to present 3 proposals instead of one, as your work process establishes, do you accept? Why, if a customer asks you to modify how your system works, do you accept? Why, if a customer doesn’t send you the information within the agreed time, don’t you call their attention to it right away?
The provider of the product or service is the one who knows its value proposition better than anyone, so the immediate answer should be a firm, confident “NO” whenever you are asked for something outside its scope. It is the most powerful two-letter word there is, and you must learn to use it.
When you start saying “NO” more often, you will do your customer a huge favor, and your business’s cash flow too. By staying aligned and within the limits of your value proposition, you will deliver a better service.
Here is a story that illustrates the problems of not knowing how to say “NO.”
We will understand it better through the story of Jurgen, a project manager at a software company that implements a payroll system he himself developed (the case can be extrapolated to any software). He has just started his business and is working hard to win his first customers.
Jurgen is contacted by APU S.A., a company that has reviewed the payroll features of Jurgen’s system and is very interested in acquiring it. However, this prospect requires the system to change the logic it uses to record cost centers per employee, so that it matches the way APU S.A. calculates them. To keep the client happy, Jurgen agrees to make that change for them: he does a quick mental estimate, concludes it will only take a few hours, and decides it is worth it to avoid losing the client.
The prospect, APU S.A., noticing that Jurgen is very flexible about changes to his proposal, takes the opportunity to ask him to also handle the import of their historical data from the previous year into the new payroll system, arguing that it is very important for them to see everything in the same system. Jurgen accepts, but negotiates an additional fee for that data migration.
Before accepting the proposal, APU S.A. tells Jurgen they have one final request: meetings must be in person, not virtual. Jurgen agrees in order to secure the deal.
Where is the problem in this?
The client, APU S.A., accepts the proposal. When Jurgen arrives at their office, he celebrates with his two employees, unaware of the big problem he has just gotten himself into.
The project starts, and Jurgen attends the first kickoff meeting, which he would normally hold virtually but which for this client will be in person. Since the meeting is on Monday at 10:30 a.m., he has to cancel the meeting he holds with his team every morning so he can make sure to arrive on time despite traffic. Near the client’s office, he asks Guillermo, the new analyst who is accompanying him as part of his training, to contact the client to check whether parking is available. Unfortunately, the client says there is no parking. Jurgen thinks to himself that at least they are arriving early and will have time to find a spot.
At the client’s offices, the meeting goes smoothly, except for an incident at the start: Jurgen was not prepared to record the presentation. The virtual room he usually uses already includes a recording system, so he had not bothered to find another recording system that would work for an in-person meeting. Jurgen had been implementing recordings because they replaced meeting minutes, and all the conversations in the virtual chat were recorded as well. After each meeting, the recordings were shared with the client, which improved the support experience: the client had that digital resource to consult, and it reduced support requests in the future.
Back at the office, Jurgen realizes that travel and parking search alone have cost them almost three hours, not just for him but also for Guillermo. And because they missed the usual morning meeting with the team, the team has some doubts about definitions that kept them from moving forward during those three hours. Fortunately, he has a proactive team that does not waste time and always finds something productive to do, but there are priorities to attend to, and attending the meeting with the new client caused a significant delay for his team.
Jurgen starts developing the system change to include the cost center logic the client requested. As he had estimated, that change took less than two hours of work. But now he has to automate the tests and run integration and functional testing, which will require at least 10 additional hours that he had not factored in at the outset. Moreover, every future development will now have to go through an additional integration test, which will permanently increase the maintenance cost of the entire payroll system, potentially meaning thousands of dollars in extra costs down the line.
To move forward with migrating the prior-year data the client requested, Jurgen decides to hire a new temporary support employee. His payroll system was designed so that imports can be done very easily from a user interface, so no technical knowledge is required and any user could update information in bulk. However, since he has to hire new staff, he still has to train them in the fundamentals of the system.
Luis, the new support assistant, is very skilled, so after his two-hour induction he is ready to start the imports. But since the data covers a full year of payroll across many different tables, he still turns to Jurgen for help several times during the week the data import lasts.
Jurgen is very pleased with Luis’s hiring, because he learns quickly and has a good attitude. That is why he regrets that, once the APU implementation is over, he will not be able to renew Luis’s contract, since the import service is not recurring. All the time invested in developing that talent will therefore not be rewarded as it should, because the company will not be able to keep him once the implementation ends.
The implementation is completed after two months of work, meeting the promised deadlines, although costs and expenses have greatly exceeded the budget due to travel time. While Jurgen is developing an improvement for his product, he thinks that although he has lost money on this implementation, at least he has gained a client who will pay off over time. Then Pedro, who is part of the support team, walks into his office
Do you have two minutes?
Yes, tell me, Jurgen replies.
The APU client has called and has a question about their cost center calculation, but in this client’s case it works differently, and I can’t find it in the manuals. Can you explain how it works?
Just then Roberto, from the DevOps team, arrives and says, regarding the APU support request:
We deployed some improvements in the early hours of the morning, but they are affecting APU, because the cost center logic was modified for them. We must make an additional development to extend the improvement to APU, and we will upload the solution in the afternoon.
At that moment Jurgen understands that this client, far from being profitable in the future, will cause him permanent losses.
APU S.A. will also lose a lot, because the level of support is not what they expected and bugs appear regularly. But above all, because the entire APU team invested a lot of time overcoming a learning curve to adopt the new system. If Jurgen cannot absorb the losses from having underquoted, and they don’t agree on a fee that lets Jurgen keep providing support for the software, then they will have to invest in implementing another software.
In this short story, we can see how a small, innocent acceptance of whatever the client asks for, out of not knowing how to say “NO,” can cause a huge loss in the value of your company. Below I will summarize the 3 main factors that are destroying the value of Jurgen’s company:
Extra time (travel, fuel, parking, training, support)
By accepting the travel, which was not part of the standard support process Jurgen offered, he did not consider how it would impact his company’s costs, and the result was a direct hit to results and cash flow, because he devoted far more resources to the project than budgeted. But the main problem here is not that he underquoted, since he could have thought it through better and included all the additional cost in his budget. The real problem is that his value proposition, and the reason clients seek him out, is that he offers quality software at an accessible price, which requires using the standard methodology he follows. It was therefore the client who should have accepted Jurgen’s methodology, which only considers virtual meetings.
The additional expenses are not limited to Jurgen’s time. They also include the time of Guillermo, the analyst, who had to travel with Jurgen. And as with everything in which you invest resources (time is the main economic resource), you have to evaluate the very high opportunity cost this implies: losing focus on your value proposition.
Poor customer experience and service deterioration.
If incurring high additional costs is not enough to justify the statement “Jurgen is destroying the value of his company,” then with this and the factors below, we begin to see how the destruction of value is actually systematized.
From the very start, because he was not ready with the recordings that were part of his standard service, the level of service drops, since he cannot send recordings to the client. This also creates more support requests in the future.
Later, by developing features at the client’s request, the controls needed in production and future deployments will require much more maintenance time. And since he is not prepared to absorb that cost, more bugs will slip through, which triggers customer discontent and dissatisfaction with Jurgen’s brand. The result is not only the loss of good references for his system, but also a client who becomes a permanent ambassador of the bad experience they had with Jurgen.
Huge opportunity cost
All the time Jurgen has devoted to activities that do not help perfect his value proposition, such as training staff he will not be able to keep in the medium term, traveling to the client’s office, developing products that will not scale to a reasonable number of clients, reorganizing processes that depended on him, and disrupting his team’s workflow. In general, all the activities that take him off focus affect the development of his product and service. And since his software business is based on achieving scalability, he is losing hundreds of thousands of dollars because it slows down his product and business development.
Start saying “NO” and don’t destroy your company’s value.