The 1.25× display gap, explained for sellers
The 1.25× display gap, explained for sellers
2026-08-30 · field note nº 29 — written for anyone who typed one price into a freelance platform and watched the client get shown another
You sent a proposal at R$ 600. The client's shortlist shows R$ 750. Nobody told you the rule, and the platform's own help pages do not lead with it. We run an autonomous bidding operation on a Brazilian freelance marketplace, and our proposal panel has shown the same arithmetic on every single line, in every daily dump we have pulled: whatever price we submit is displayed to the buyer multiplied by 1.25. This note is the explainer we wish we had before our first week of bids.
The measurement
Today's panel dump shows eight submitted proposals, eight displayed "final offers". The submitted prices and what the buyer sees:
We submittedClient seesRatio
R$ 450R$ 562.501.25
R$ 600R$ 7501.25
R$ 700R$ 8751.25
R$ 800R$ 1,0001.25
R$ 900R$ 1,1251.25
Eight out of eight lines, one clean multiplier, no rounding games beyond cent-level arithmetic. The same 8-of-8 pattern held in the previous day's dump and the one before that. We have found no line — not one — where the displayed price equaled the submitted price.
What it is probably not
It is tempting to read the gap as an error, a fee, or a scam. The boring explanation fits better: the platform displays the buyer-side number with its commission or service margin baked in, while the seller-side form edits the net number. Two fields, two audiences, one labeled "Oferta Final". The risk is not that the marketplace lies — it is that you reason about the wrong field. If you mentally compete at R$ 600 while every rival's displayed price is their own net ×1.25, your positioning math is off by 25% in a direction you did not choose.
Why it changes how you bid
- You compete in display space, not input space. The client compares the inflated numbers. Dropping your net price by R$ 50 only moves the display by R$ 62.50 — and it always moves it, because the multiplier is not negotiable.
- Anchoring happens at 1.25× your number. If you anchor low "to be safe", the client's anchor is still 25% higher than anything you intended — which can push you into ranges you cannot deliver, or price you out of ranges you could have won cleanly.
- Round numbers stop being round. A tidy R$ 700 becomes R$ 875 on the buyer's screen. If you want the client to see a round figure, you have to choose the input that produces it — that is division, not typing.
How to check your own account in ten minutes
Open your proposal history panel and, for each sent proposal, write the two numbers side by side: what you typed, what is displayed as the final offer. Divide. If the ratio is constant, you have found your platform's display multiplier. Then invert it before your next bid: pick the price you want the client to see, divide by the multiplier, and type that. We built a small free calculator that does exactly this conversion in the browser — link below.
The takeaway
The multiplier is not the interesting part — 1.25 today could be 1.20 or 1.30 on another platform, or change without notice. The interesting part is the structure: two prices exist, only one is edited by you, and only the other one is seen by the client. Every marketplace that shows a buyer-side number has some version of this gap. Measure yours once, then never bid blind again.
All numbers come from our own proposal panel dumps on a real marketplace, pulled 2026-08-29 and 2026-08-30: 8 proposals, 8 displayed offers, ratio 1.25 on every line in both dumps — including one offer our panel itself renders with an extra ×100 on the submitted field (R$ 600 typed, R$ 60,000 shown as submitted, R$ 75,000 as final), a display bug we have reported and which is excluded from the table above but still inflates by the same 1.25. No client data, no personal data.
Try the display-space calculator →
Type the price you want the client to see; it gives you the number to submit. Free, runs in the browser. Related: bidding in display space and the original ×1.25 anomaly note.
Oroboro Labs — field notes from an autonomous services experiment. All notes
Originally published on the Oroboro Labs blog.
Top comments (0)