A Screenshot From Two Weeks Ago
The client sent the screenshot before he even said hello.
"You sent me this price yourself! Why is it different now?"
Marina recognized the file immediately — the same price list she'd sent him two weeks earlier, on the first day of their conversation. The numbers had been right then. Not anymore: the developer had raised the price by 15 percent after two units on the lower floors sold.
She didn't answer right away. Not because she didn't know the current price — the fresh list was sitting open in the next tab. It was because she knew the real explanation wasn't "here's the new number." It was "here's why the old number was still on your phone at all."
Updating Your Copy Doesn't Update Everyone Else's
She remembered the developer sending an updated price list the week before. She'd opened it, checked it against the old one, saved it — a routine action that felt like closing a loop: update received, file replaced, everything current.
Except "current" only applied to one copy — the one sitting on her computer. The file she'd sent that client earlier kept living its own life: in his photo gallery, in the thread, possibly forwarded to his wife to "take a look." She'd updated the price list on her end. She had no way of updating it on his.
The same thing had happened with three other clients she'd sent that file to over the past month. Somewhere out there, it's still sitting untouched, waiting for someone to open it again and mistake it for the truth.
The Same Question, Over and Over
Over the course of a week, Marina fielded some version of the same question six times. Different clients, different units, the same underlying line: "Why does this show a different price?" "Is this actually the latest version?" "I got sent a different file — which one do I believe?"
Each time, the answer wasn't a five-second reply — it was an explanation: the file's outdated, here's the current one, sorry for the confusion. Each time, the client hesitated for a second — not about the price, but about whether the information he was getting could be trusted at all. And once that doubt sets in, it doesn't just disappear. Some clients simply go quiet after a moment like that and keep talking to another agency instead, one that seems, at least, to have "fresher numbers."
Every repeated WhatsApp question is margin leaking out in small pieces.
Not a One-Off Mistake — a Constant Leak
Marina started counting. Six repeat questions in one week, each costing at least five minutes to explain and re-send the file. Thirty minutes. Not a disaster, if it were a one-time thing. But she knew it wasn't — this happened every week, to her and to every colleague on her team. No one had ever bothered to add it up.
The problem was never that someone forgot to update a file on time. It was that updating the file at the source — with the developer, with her — has nothing to do with what happens to the copies already out in the world. A PDF, once sent, has no way of knowing it's gone stale. It just keeps existing, looking exactly as convincing as it did the day it was sent.
The Cost of Trust, Not Just Time
She answered the client — politely, with an explanation, attaching the current price list. He took it in stride, no irritation. But the residue stayed with Marina: she'd spent time again not on selling, but on justifying information she'd handed over in good faith, back before it had a chance to go out of date.
The team's expensive time doesn't just disappear into tracking down the current numbers. It disappears into constantly explaining why the old numbers are still floating around in clients' hands. That's the hidden half of the same cost — it just doesn't show up at the moment of checking. It shows up at the moment a client's confidence quietly slips.
What This Story Is Really About
The problem was never a forgotten update. It's that a file, once it leaves its source, has no way to tell the person holding it: I'm out of date — stop trusting me. Updating one copy doesn't recall the rest. They keep circulating through chats, inboxes, and photo galleries, generating questions that have nothing to do with an agent's competence — and everything to do with the time it takes to answer them.
Author
This material was written by Maria Vashchenko.
For questions, collaboration, or further discussion, feel free to contact me on LinkedIn.
