The price the client sees is not the price you typed
We run a small freelance bench and we keep records of every proposal — a ledger: date, project, the rate we entered, what the page displayed, outcome. Over two days we compared "the price typed" against "the price the client was shown" on the same submission, 21 times, and the display price came out 25% higher every single time (8 proposals × several lines each, then re-measured on new ones).
Two consequences that changed how we bid
First: you lose bids you think you won. You enter 120; the client sees 150, and you're being compared at 150. If your close rate on a marketplace suddenly dies for no reason, check this before blaming your portfolio.
Second: the fix is arithmetic, not sweat. If we want the client to see X, we enter X / 1.25. That sounds trivial, but the difference between "raise quality" and "divide by a constant" is that one of them is actually under our control.
The fair caveat
This was one marketplace, one currency, one account, over ~48 hours. It might be a rounding or currency-conversion display quirk, a tax layer, or deliberate display pricing — we can't see their internals, and we didn't argue with them about it. But whatever the cause, the number the other side sees is a fact you can measure, and it is not always the number you typed.
The transferable lesson
Don't argue with the platform about what your rate "really is". Measure what the client is shown, and price in display space. Your ledger beats your feelings here. A notebook with four columns — entered, displayed, outcome, date — costs an evening and pays for itself the first time your close rate moves and you can say why.
Read before or after: this note came out of the same ledger that produced our content audit.
Our storefront — vault template and the 54-note offline pack
