This line sits in half the company profiles in Egypt: "the best quality at the lowest price." It is one of those rare phrases that does more harm than good.
It asks the customer to believe two contradictory things at once. And if he does believe them, something does not add up: how are you giving me the highest quality and taking the least money? What is being sacrificed?
The customer's mind answers that question on its own, and the answer is usually not in your favour.
Why the double promise loses
Every business runs on limited resources: time, people and money. Saying highest quality means more time and better people, and that costs. Saying lowest price means you are cutting cost somewhere.
A sharp customer asks: where was it cut? The materials? The time? The person who will actually work with me? And if you have no clear answer, he assumes the worst.
Big companies choose — and you should more
Look at any market you know and you will find the successful companies have chosen their promise clearly. Some say "I am the cheapest, you will wait and you will serve yourself." Others say "I am the most expensive and everything will be ready for you." Each is built completely differently on the inside, not just in the advertising.
The one in the middle — not cheap enough, not distinctive enough — is the one that struggles.
Pick one promise and build it
The promise is not a slogan, it is an operating decision. If you pick price, you have to work on cost: simpler operations, a standard service, limited revisions, tools instead of people. If you pick quality, you have to work on the outcome: more time per customer, fewer customers, and a price that covers it.
- If your promise is price: state the limits honestly. "This package covers exactly this; anything extra has a price." That clarity protects you from a customer expecting premium service.
- If your promise is quality: explain what takes the time and the money. Customers pay comfortably when they understand what they are paying for.
- If your promise is speed: that is a perfectly legitimate third option and plenty of people will pay for it — but you have to actually be faster, not just promise it.
How to respond when a customer compares you to someone cheaper
Do not get into a line-by-line comparison, and do not run the competitor down. The best response starts with a question: "What exactly did they offer you?"
Most of the time you will discover the two offers are not the same thing at all — a different quantity, a different duration, or something missing. Your job is to make that difference clear without implying the other guy is cheating.
Then state your promise in one sentence: "We are not the cheapest. We work with a limited number of clients so each one gets enough time." That sentence filters customers, which is a good thing.
The loss that is in your favour
When a customer leaves because he found cheaper, that is not always a loss. Some customers cost you more than they return: endless revisions, late payment, comparison at every step.
If your promise is clear, that type never reaches you in the first place — and that is half the benefit.
Try this exercise
Write one sentence about your work without using the word "quality" or the word "best." If you cannot find anything to say, your promise does not exist yet — you have been using generic language in its place.
A good sentence contains: who you work with, what you solve, and what is different about your method.
The promise has to show up in every detail
If you say you are the fastest, that has to show in how quickly you answer the first message, in the delivery time written in the proposal, and in someone following up without the customer having to think about it.
A promise that lives in the advertising and breaks in delivery does more damage than making no promise at all, because the customer feels deceived — and people talk about that feeling far more than they talk about an ordinary experience.
Quality is a word; a specification is a number
When you say high quality, the customer cannot do anything with it. Turn it into specifications he can compare:
- A named material instead of "the finest materials."
- A number of revisions written into the contract instead of "unlimited revisions" that nobody honours.
- A clear warranty period, with what is covered and what is not.
- The name and level of the person who will work on the project, not "a professional team."
These details are what make your price make sense. Without them any number looks arbitrary, and any cheaper competitor looks logical.
Three moments that test your promise
A promise is not defined in the proposal, it is defined in the hard moments:
- When you make a mistake. If your promise is quality, the mistake gets fixed at your cost without a long argument. That is the price of the promise.
- When the customer asks for more. If your promise is a low price, you have to say no or charge for the extra. Saying yes for free eats your margin and corrupts expectations.
- When you are overloaded. If your promise is speed, the right decision is to refuse new work temporarily rather than be late for everyone.
Anyone who breaks their promise in those moments goes back to zero and has to rebuild trust from scratch.
This is not a call to be expensive
Some people read this as an invitation to raise prices. That is not the point.
The point is that price should be the result of a clear decision: who you serve, what you promise them, and what costs you carry. You may well end up being genuinely the cheapest — but then you will be the cheapest on purpose, with a business designed so you can live at that price, not because you were afraid to say a higher number.
In short
Do not say you are the cheapest and the best. Pick one, build your business around it, and explain it clearly.
That choice is not selling yourself short; it is what lets a customer understand who you are and why they should pay you. Language that tries to please everybody reaches nobody.
This is part of a series on pricing and competition — which also covers why not to compete on price, and why not everything your competitor does needs copying.