A situation everyone in services faces: a client wants work at a high standard, on a budget that does not even cover the cost.
And when you say that is not possible, the reply comes: "so you're not going to work?" As if refusing the price were refusing the work.
The truth is that proper work has a cost, and that cost is neither exaggeration nor greed — it is people's time, skill, tools, and responsibility for an outcome.
Why does a small budget hurt both sides?
If you accept work below its cost, the outcome is predictable: you give it less time, or assign someone less experienced, or push it to the bottom of your priorities.
So the client does not get the result they wanted, you lose time and goodwill, and the relationship ends in a dispute. Accepting here does nobody a favour.
Make clear that price is tied to scope
Most of the discussion becomes about the number because the scope is unclear. Once you define exactly how many pieces of content, how many revisions, how many reports and what timeline, the number becomes understandable.
And then the conversation changes from "the price is high" to "what can we reduce?" — a healthy conversation both sides win.
Offer alternatives instead of saying no
When the budget is below what is required, you have four respectable options:
- Reduce the scope. The same standard with less work. The best option, because it protects quality.
- Change the shape of the service. Instead of full delivery, advice and a plan their own team executes.
- Start with a first phase. A small defined piece of work, and if it succeeds we continue.
- Refer them to someone better suited. Even if it means losing the job, it builds respect that comes back to you.
Accepting the same scope at a lower price is the only option with no good ending.
"We'll work cheap now and raise it later"
The most common line in the market, and wrong in most cases. The first price sets the client's expectation permanently, and any later increase looks excessive however logical.
If you want to give an introductory price, make it clearly temporary with a reason: a launch offer, a first project, or in exchange for using the work as a case study. That context protects your standard price.
Know your cost so you can say no
Most people who accept unsuitable prices do so because they do not know their true cost.
Work out: how many hours will this take, what is your hour worth, what are the direct expenses, and how many projects can you take a month. Those numbers give you a clear floor, and make refusal a calculation rather than a mood.
The client comparing you to someone cheaper
There will always be someone cheaper, and that is not a benchmark. The benchmark is: is that offer the same thing?
Ask the client: what exactly did they offer you? You will usually find large differences in scope, experience or timeline. Make the difference clear without running anyone down, and leave the decision to them.
And if they choose cheaper, that is their right. In many cases they come back months later, understanding the value from experience rather than from argument.
Free work and portfolio projects
If you are still starting out, working at a token price or free can be the right call — with conditions: a specific, short project, an agreement that you may use it as a case study, and a defined end point.
The danger is entering a cycle of continuous free work, which happens when there is no agreed ending.
The difference between expensive and costly
There is a difference between a service with a high price and a service that costs the client. What genuinely costs them is paying and getting no result, however small the price was.
When I explain this to a client I say: money spent on work that produced nothing is not cheap, it is entirely lost. Money spent on work that brought customers is not expensive, it is an investment that returned.
The right comparison is not between two prices, it is between two outcomes against their cost.
Document the agreement however simple
Most price problems are not about the number, they are about what was not understood. The client thinks the price includes things; you think it does not.
A small page with the scope, the timeline, the number of revisions, the payment terms, and what is outside the agreement solves ninety percent of disputes before they happen. It needs no lawyer, only writing down what you agreed in clear language.
Respecting your price starts with you
If you are not convinced by your own price, it will show in your voice and you will drop it at the first pressure.
That conviction comes from two things: knowing your cost exactly, and being able to explain the outcome the client will get. When both are clear, you state your number calmly — and that alone changes the other side's reaction.
In short
Proper work has a cost, and there is no way to deliver it for less without someone losing.
Clarify the scope, offer alternatives instead of a flat refusal, know your cost so you know your floor, and do not accept a price that forces you to deliver work you are not proud of.
Refusing here is not arrogance — it protects the client before it protects you.
This is part of a series on working in digital marketing — which also covers the jobs in the field, and how to use AI in marketing.