The Friday When the Conclusion Could Not Be Delayed Any Longer
On Friday morning, Alexis came into the office without the usual instinct to reopen the reports, search for an external reason, or convince himself the problem was temporary. Over the past four days, he had moved from irritation to uncomfortable clarity. On Monday, Andreas had introduced him to the word friction. On Tuesday, Alexis had seen for himself how buyer attention breaks when an agent has to search through files. On Wednesday, the team had finally accepted that stock does not become agent-ready just because the materials exist somewhere. On Thursday, they had stopped repeating the old line: “The agent will find it.”
Now Alexis had to do the thing he had been avoiding all week: explain to the board why Poseidon Residences was not losing because of the product, but because of the route to the product. That was harder than admitting the issue internally. The board was used to hearing the language of reports: budget, leads, viewings, conversion, sales. Alexis needed to explain that between “we have a good project” and “the agent showed it to a buyer,” there was an entire operational distance — and that was where they were losing speed.
He opened a blank document and typed the title: Better stock can still lose to easier stock. For a few seconds, he stared at the sentence, wondering if it sounded too blunt. Then he realised that was exactly why it worked. It left no space for polished excuses. If stock is hard to check, hard to explain, and hard to send, it can still lose — even when the actual property is stronger on paper.
A Manifesto Instead of Another Report
Alexis did not start the document with marketing, architecture, or commission. He started with the point the board would find hardest to accept: product quality no longer guarantees a place in the buyer conversation. A project can be known, well-presented, and commercially attractive, but if the agent cannot quickly access current price, live availability, unit details, and a ready property card, that project can still stay out of the conversation at the exact moment it matters.
He wrote the first paragraph, then deleted it almost immediately. Too soft. He tried again: “We thought we were competing only on product. In practice, we are also competing on speed of access to stock.” That was closer to the truth. He added a simple comparison: one route requires opening Drive, choosing a file, checking the version, comparing Excel, messaging a manager, and waiting for confirmation. The other route allows the agent to open stock, apply filters, see an available unit, open the card, and send a buyer-ready option.
Marina knocked and stepped into his office.
“Are you writing the board note?”
“Yes,” Alexis said, without looking away from the screen. “I’m trying to explain that we are losing in a place we were not measuring.”
She placed a short summary on his desk: repeated broker questions from the past two weeks. Alexis scanned the list: “Is this price current?” “Is this unit still available?” “Can I send this to a client?” “Is there a floor plan link?” “When will availability be updated?” It was all too familiar now.
“These are not broker questions,” he said after a pause. “They are symptoms of our system.”
Marina nodded.
“I see it that way now too.”
The Formula of the Week
By midday, the document no longer looked like a standard internal report. It had become something closer to a manifesto. Alexis wrote out the main formula of the week: better stock can still lose to easier stock. He made one thing clear: this did not mean quality no longer mattered. Quality mattered, but it only started working after the project entered the buyer’s field of attention. To get there, the agent needed to check the stock quickly and show it safely.
He added a section on agent behaviour. An agent is not there to prove loyalty to one developer while a buyer waits for a specific answer. Agents do not choose in a vacuum between “better” and “worse.” They choose in the moment between route A and route B. One route gives them ready information. The other forces them to check, assemble, wait, and risk sending something wrong. If the second route belongs to Poseidon Residences, that is not the broker’s problem. It is Poseidon Residences’ problem.
At the end of the document, Alexis wrote a short conclusion: “We can no longer treat folders, PDFs, and manual updates as a distribution system. They store information. But the market does not reward storage. It rewards readiness for action.” He read the line several times and left it unchanged.
When the document was ready, he sent it to the board without a long cover note. Just one sentence:
“This is the issue behind the numbers.”
The Sentence He Heard After Lunch
After lunch, Alexis walked through the sales department. He was not planning to interrupt anyone. He simply wanted to hear how the team was handling broker requests after everything they had discussed that week. The room was busier than usual: someone was answering emails, someone was on the phone, someone was checking a table on a second monitor.
Near the window, a young sales manager named Kirill was holding his phone against his shoulder while opening Excel and scrolling through a back-office chat. On the screen was unit C-804. Alexis stopped beside him, not because he wanted to control the call, but because he heard a familiar tone — the tone of someone about to say a sentence that sounded responsible but created delay.
“Yes, the unit could work,” Kirill said to the broker. “But wait, this apartment may no longer be available. I’ll check with the manager and get back to you in a couple of hours.”
Alexis felt his stomach tighten.
Kirill ended the call, looked up, and saw Alexis standing next to him.
“Is something wrong?”
Alexis did not answer immediately. He looked at the Excel file, then at the phone, then at the chat where the latest availability message had been sent the evening before.
“Do you understand what just happened?” he asked.
Kirill became cautious.
“I didn’t want to send wrong information. It is better to check.”
“You’re right,” Alexis said. “We cannot send wrong information. But the problem is not that you checked. The problem is that our system forced you to check in the exact moment when the broker needed an answer now.”
“I’ll Check” as the Point of Loss
Kirill pushed his chair back slightly, still unsure why an ordinary work phrase had become such a problem.
“But if I’m not sure the unit is available, what else am I supposed to say?”
“That is exactly the issue,” Alexis replied. “You do not have a reliable working status. The broker does not have a reliable working status. The buyer is interested now, and our system answers with: wait a couple of hours.”
Kirill looked at his phone.
“The broker said the client is still nearby. They are going for coffee after the viewing.”
“And in those two hours, he will show them something else.”
“Maybe.”
“Not maybe,” Alexis said. “Most likely.”
Kirill fell silent. Around them, phones kept ringing, someone laughed in the next room, and the printer continued pushing out documents. But for Alexis, all that noise narrowed into one sentence: “I’ll check and get back to you in a couple of hours.”
A month earlier, that line would have sounded normal. Careful. Professional. Even responsible. Now he heard something else in it: delay, uncertainty, and a lost buyer moment.
Why Live Data Was No Longer a Technical Detail
Alexis asked Kirill to join him in the small meeting room next to the sales floor. There was an empty coffee cup on the table, an uncapped marker, and an old lead generation diagram still on the board. Alexis picked up the marker and wrote:
“I’ll check” = delay
“Not every ‘I’ll check’ is bad,” he said. “Some questions genuinely need checking. But availability, price, and basic unit details should not be complex questions. They are core sales data. If they are not live, we put the agent on pause every time.”
Kirill sat across from him.
“But live data is more of a technical issue, isn’t it? Not just sales.”
“No,” Alexis said. “It is sales. Because when a broker asks whether a unit can be shown, live data decides whether the property gets shown or not. If we answer two hours later, we are not just working slowly. We are giving the buyer’s attention to whoever can answer immediately.”
Kirill nodded slowly.
“So the problem is not that I said ‘I’ll check.’”
“The problem is that our system left you with no better sentence.”
The Decision That Became Inevitable
By the evening, Alexis gathered a short meeting with the key team. No long strategy session, no polished presentation. Just Alexis, Marina, Nikos, Elena, Dimitris, and Kirill, who still looked as if he had accidentally become part of the final scene of the week.
Alexis started directly.
“Today I heard the sentence that explains why we do not need another presentation. We need a new operating system for stock.”
He repeated Kirill’s conversation with the broker. No one argued. After four days of discussion, everyone understood that this was not an isolated case. It was their normal working mechanism.
“We can keep improving visuals,” Alexis continued. “We can update PDFs more often. We can send more emails to brokers. But if, in the buyer moment, our answer still sounds like ‘I’ll check and come back later,’ we are not solving the main problem.”
Elena asked:
“You mean an MLS workflow?”
“Yes. I mean a system where stock does not sit in five different places, but works as one route. Where price, availability, unit details, property card, and broker access are connected. Where the agent does not wait for us to assemble the answer, but sees current information immediately.”
Nikos looked at Marina.
“That means finance has to be part of the update flow, not a separate Excel file at the end of the chain.”
“Yes,” Marina said. “And back office too. And sales. And marketing. Otherwise we end up with five sources for one unit again.”
Alexis nodded.
“Exactly. For us, MLS is not just another channel. It is a way to remove friction between an update and a showing.”
The Last Note in the Notebook
When everyone left, Alexis returned to his office. It was already getting dark outside, and the lights of the neighbouring development were reflected in the glass. He opened the notebook where he had written the key phrases of the week: friction, buyer attention, agent-ready stock, the agent has alternatives, do not make the agent search for what should be ready.
On a new page, he wrote:
“I’ll check with the developer” kills the buyer moment when the answer should already be live.
He looked at the sentence for a long time. There was no exaggeration in it. It was a simple operational truth. If the agent has to check basic information, the buyer waits. If the buyer waits too long, the moment weakens. If the moment weakens, another project can get there faster, even if it is weaker on paper.
On Monday, Alexis had thought the problem was the brokers. By Friday, he understood that Poseidon Residences was asking brokers to work against friction the project itself had created.
He closed the notebook, picked up his phone, and wrote to Andreas:
“Next week, I want to show you a different route.”
The reply came almost immediately.
“I hope so. Your project deserves better than PDFs.”
Alexis looked at the message and, for the first time that week, did not feel irritated. Andreas was right. The project did deserve a better route.
But Alexis now understood the main point: the market would not wait for them to build it.
In the buyer moment, the winner is not the one who promises to check.
It is the one whose answer is already ready.
Author
This material was written by Maria Vashchenko.
For questions, collaboration, or further discussion, feel free to contact me on LinkedIn.
