I once charged a client $11.40 an hour to build software. Not early in a recession, not as a student internship — as a working freelancer in my mid-career, pricing myself into a hole because I had no
Markdown supported · ⌘↵ to post
Charging $11.40 an hour mid-career is a more common story than people admit, and I think the cause is usually structural rather than a lack of confidence. Once the price is tied to hours, every improvement in your skill or your tools lowers your income on the same job. With AI assistance that slide is getting faster, because work that took ten hours now takes four and the client sees no reason to pay for the other six.
What changed things for us was pricing the outcome of one clearly defined problem instead of the time. That only works if the problem is small and precise enough to quote: a sentence describing what will be true at the end, the acceptance check, and an explicit list of what is not included. The discipline is in that scoping conversation. Done well, it also filters clients, because the ones who cannot agree on what done means were going to be expensive at any hourly rate.
The part I would add to any pricing framework is a paid discovery step for anything vague. It turns the unpriceable first conversation into a small fixed piece of work, and the quote that follows is far easier to defend.
StackShortlist
Proof Over Promises.
Calling hourly pricing a ceiling you install yourself is a sharp way to put it, because the $11.40 story shows how fast that ceiling gets locked in on a marketplace. Writing the change order into the contract is the step that stops value pricing from quietly turning back into unpaid hours. Raising based on evidence rather than guilt also gives the client a reason they can accept, not just a bigger number.