Rates: What Changed
The pressure is real. Clients have read that software is faster to produce, competitors are quoting lower, and platforms advertise that anyone can build an application by describing it.
The pressure is also mostly misdirected, and understanding why is the difference between defending a rate and discounting one. For the operational side of recording work and turning it into client-facing evidence, see wage percentage calculator.
What a rate actually prices
Not your typing speed. Four things, in rough order of what clients are paying for.
Judgement about what to build. Which features matter, what to leave out, where the real requirement differs from the stated one. Untouched by any of this.
Judgement about how to build it. Which approach survives contact with the next six months. An assistant will produce a confident answer to this and it has no stake in the outcome. Freelancer’s community material provides another perspective on independent project work See Freelancer Community.
The ability to tell whether something is right. The scarce skill, and it got scarcer relative to demand, because there is now far more output to evaluate.
Carrying the consequence. You are the one who is called when it breaks. That has not changed and it is a large part of what a client is buying, whether or not either of you names it.
Typing was never more than a fraction, and it is the fraction that collapsed.
What genuinely got cheaper
Be honest about this or the rest is not credible.
Work that was mostly production, in the cheap-to-verify bucket. If your rate has not moved at all on scaffolding, boilerplate and simple transformations, the client's suspicion is correct.
Ramp-up in unfamiliar ecosystems. Where the cost was your learning curve, not the problem.
Small isolated additions, where there is little to verify.
The right response is not a lower hourly rate. It is that those tasks now take less time, so they cost less at the same rate. That is the honest transmission mechanism, and it is why the rate itself should not be where the adjustment happens.
What got more expensive
Review and verification. More output, arriving faster, with subtler errors. This is now the majority of consequential work.
Judgement about which situation you are in. Knowing before you start whether a task is cheap or expensive to verify is a new skill with real commercial value, and it is what makes an estimate possible.
Being the person who is right about scope. Clients can now generate a plausible plan themselves. Someone who can say which parts of it are wrong is worth more, not less.
The competitor problem
Someone is quoting half your number. Three possibilities, and it is worth knowing which.
They are better than you. Occasionally true and it deserves a serious look.
They are pricing the production half. Most common. They have seen generation collapse, adjusted, and not noticed that verification did not. They will discover this on a project that goes badly, and it will not necessarily be visible to the client until after they have chosen.
They are competing on a different product. A prototype that demonstrates the idea is a legitimate thing to sell, and it is not what you are selling. The mismatch is in what "done" means.
Do not match the number. Ask what they understood about the scope that you did not — sometimes it is real. And where the difference is what "done" means, make that explicit rather than arguing about price: at that number you get something that works; at mine you get something that keeps working.
Whether to raise
Two arguments in favour, one against.
For: if the scarce input is judgement and review, and demand for those rose while supply did not, the market case for a higher rate is straightforward.
For: you are absorbing more risk than you used to. Wider variance on verification-heavy work means fixed prices carry more, and carried risk is priced.
Against: the number is visible and the reasoning is not. A rate rise announced without a change in what the client experiences reads as opportunism, however well-founded.
The practical route is to change what you sell rather than the number on it. Price outcomes rather than hours, so improvements in production accrue to you rather than being handed back automatically. That is a structural change rather than a rate change, and it does not require anyone to agree that you are worth more per hour.
The uncomfortable part
Some work genuinely is worth less than it was. A simple brochure site, a straightforward integration, a small internal tool — these are cheaper to produce and it would be strange if the price did not reflect it.
Pretending otherwise is a losing position, and it is also unnecessary, because the work that got cheaper is the work you should be least attached to. The commercial move is not defending the price of production. It is being demonstrably good at the part that did not get cheaper.
The short version
- A rate prices judgement about what to build, judgement about how, the ability to tell whether it is right, and carrying the consequence
- Typing was a fraction and it is the fraction that collapsed
- The adjustment belongs in hours taken, not in the rate — cheap-to-verify tasks now cost less at the same rate
- Competitors quoting half are usually pricing the production half, or selling a prototype under the same word
- Do not match the number; make explicit what "done" means at each price
- If you want the gains, change what you sell rather than the number on it