A Morning That Always Starts the Same Way
Marina's coffee went cold before she'd even opened her first chat.
Monday, 9:14 a.m. Three WhatsApp threads, the developer's spreadsheet in one browser tab, her inbox in another. Two years into the job, she'd settled into a ritual: skim the overnight messages first, then the fresh inquiries, and only after that, the coffee — cold by now, but a habit she wasn't ready to break.
The message came from a client she'd spent a week and a half building trust with: photos, a video walkthrough with the sea view, long voice notes answering questions about the neighborhood. The kind of client worth the time already invested. And now, finally, a concrete question.
"Hi! Is unit 4B still available?"
Five seconds — that's what the answer should have taken. Marina knew the unit. She remembered the floor, the view from the window. The only thing she didn't know for certain was whether the listing status still held.
The Check That Eats the Minutes
She opened the file the developer had sent the week before. Wrong one — it still had the old building numbering, from before the last update. She scrolled through her inbox, found an email marked "final price list," opened the attachment. The numbers didn't match what she remembered from Friday's call with the developer's sales manager.
She messaged a colleague: "Do you have the current price list for Building B?" — "Checking now," he replied, then vanished into his own threads, apparently untangling a similar question from his own client.
Marina opened a third file — a PDF the client himself had sent back to her. It was a screenshot she'd sent him two weeks earlier, before the last price update. He was working off numbers that were already stale by the time he was ready to decide.
Three sources. Three different answers to the same question — is it still available? — and not one of them marked as the one to trust.
While You're Checking, Someone Else Decides
Seven minutes passed. She messaged her colleague again — silence. She checked the team's shared chat; someone else was asking about Building B there too, and someone else was answering, "not sure, ask the developer directly."
At minute eight, a new message arrived from the client:
"Thanks, I figured it out — bought through another agency."
Not because Marina was slow. Not because she wasn't paying attention. It was because while she spent seven minutes simply trying to find the truth, someone else had already closed the question for him. The other agency's data may not have been more accurate — just faster to arrive.
Marina closed all three files, one after another. Not because she'd found the answer, but because it no longer mattered.
The Hidden Cost of One Question
She leaned back and, almost without thinking, glanced at her desktop. Lined up in a row sat the files: FINAL.pdf, FINAL_v2.pdf, FINAL_UPDATED.pdf, FINAL_FINAL_UPDATED.pdf.
It struck her that this wasn't an isolated incident. Over the past month, some version of this scene had played out almost daily — a different client, a different unit, but the same ending: seven minutes here, twelve there, a colleague who didn't know either, an email to the developer that wouldn't get a reply for two hours.
On its own, each check looks trivial. Add them up over a week, though, and they become hours that never went toward calling new clients, prepping showings — the work she was actually hired to do.
FINAL_FINAL_UPDATED.pdf isn't a system. It's a warning sign.
Not a Motivation Problem — an Architecture Problem
Marina wasn't a bad agent. She answered fast, knew every unit by heart, and had a way of talking to clients that earned their trust from the first call. She was consistently among the top performers on her team for showings booked. She just spent a good part of her day on something else entirely: making sure the number in front of her was still true, and not simply what had been true three weeks ago.
It wasn't about her speed, and it wasn't about her attention to detail. It was that the answer to a simple question — is it still available? — had nowhere to live as a single, final truth. Every file, every chat thread, every version of the price list carried on with a life of its own, and nothing recalled the old ones when a new one appeared.
She closed her laptop a little harder than usual and thought, not for the first time that month, that she'd been hired to sell. Not to babysit PDFs.
What This Story Is Really About
Marina isn't an outlier, and this isn't a case of poor organization. It's what a normal day looks like for an agent on any team where up-to-date information has no single source: the checking eats minutes, the minutes add up to hours, and those hours aren't an abstract inefficiency — they're specific lost deals and clients who found their answer somewhere faster.
The problem was never that someone wasn't quick enough or careful enough. It's architectural: as long as pricing, availability, and unit details live scattered across files and chats, every update on the developer's side inevitably turns into a question on the agent's — and every one of those questions costs time that could have gone toward a sale.
Author
This material was written by Maria Vashchenko.
For questions, collaboration, or further discussion, feel free to contact me on LinkedIn.
