For Property Developers

Leaky Pre-Sales: Why Secret Prices Don’t Belong in WhatsApp

A private property launch can lose control fast. Follow Myrto’s story to see how confidential prices spread beyond selected brokers through forwarded PDFs.

Leaky Pre-Sales: Why Secret Prices Don’t Belong in WhatsApp

Chapter 1: The Private Offer That Kept Moving

Myrto arrived at the office earlier than usual on Monday. In less than an hour, her team was due to open a private pre-sale for a new premium development in Limassol. Twelve brokers were on the guest list — people the developer had worked with before and trusted with the right kind of buyers. The project had not yet appeared on property portals, prices were absent from the developer’s website, and several of the most attractive units were being held back until the public launch.

The selected brokers would receive a separate presentation and a private price list. Across the first page of the PDF, in large letters, were the words CONFIDENTIAL — PRIVATE PRE-SALE. Myrto checked the unit list once more. The launch seemed carefully contained: a limited audience, preferential terms and a few days’ head start before the wider market saw the project.

“Did we check the final version?” she asked as the sales manager walked into the meeting room.

“Yes. Prices, availability, payment plan — everything is current.”

“And we’re sending it only to these twelve?”

“Only to them.”

“Then make sure the message says the materials aren’t to be shared.”

He nodded.

“Already done: Private release. Please do not distribute outside your team.”

Myrto closed her laptop.

“Good. Let’s go.”

The first few hours looked perfect

At 9:30, the materials started going out. Questions came back almost immediately: one broker wanted the penthouse floor plan, another asked about the payment schedule, and a third wanted to know whether a particular unit could be held for a buyer until the evening. It was exactly the activity Myrto expected from a private pre-sale — serious questions from a carefully selected group.

Around midday, one of the managers came over to her desk with his phone.

“Do you know Christos P.?”

Myrto looked up.

“No. Which agency?”

“That’s why I’m asking.”

He showed her a message:

“Hi, I received your private offer. Is Unit 504 still available at €685K?”

Myrto opened the private price list. Unit 504 was listed at exactly that amount. The figure had never been published anywhere and appeared only in the PDF sent that morning.

“He’s definitely not on our list?”

“I checked twice. He isn’t.”

“Then how does he have the presentation?”

Nobody had set out to leak it

Within minutes, replies started coming back from the brokers. One had forwarded the file to a colleague inside his agency. Another had shown it to someone on his team. A third had sent a couple of pages to a buyer who might be interested.

“I only shared it internally.”

“Just one colleague.”

“I sent the unit page to my client.”

Nobody was trying to damage the developer. Each person had done something ordinary in day-to-day sales: received useful information and passed it to someone who might need it.

“So someone got the PDF from a broker, who got it from another broker, and nobody thinks of that as a leak?” Myrto asked.

“Looks that way.”

“Can we tell how many people have the file now?”

“Not exactly.”

That morning, the list of twelve names had given Myrto a reassuring sense of control. Now it was clear that it recorded only the first step in the file’s journey.

Twelve recipients did not mean twelve viewers

A PDF cannot enforce the intended audience. Once it lands on someone’s device, it can be forwarded like any other document.

If the first broker sends it to a colleague, there is a thirteenth recipient. If that colleague sends a page to a client, there is a fourteenth. A few steps later, the developer may still call the launch private while having no clear idea who has seen the offer.

“So we know who we sent it to,” Myrto said, “but we don’t know who is reading it now.”

“Yes.”

“Excellent private launch.”

This time, the manager said nothing.

By the afternoon, it was a commercial problem

At 2:20 p.m., another message arrived from an agent Myrto’s company had never worked with. He already had the materials.

“Another one?” Myrto asked.

“Yes.”

“What does he want?”

“Can my buyer get the same private price?”

That morning, the price had been part of a limited pre-sale. Now an uninvited agent was treating it as a market price and using it to begin a negotiation.

Myrto opened the PDF again. CONFIDENTIAL still appeared across the first page.

“The word is still there,” she said. “The control isn’t.”

By the end of the day, the list no longer proved enough

Before leaving, Myrto reopened the spreadsheet with the twelve broker names. It showed who had received the document directly from her company. It could not show who received it afterwards, which units had been forwarded separately or how many buyers already knew the private price.

The manager stopped at the door.

“Tomorrow, do we try to find out who forwarded it first?”

“I’m not sure that’s the real question.”

“Then what is?”

“Why did we assume that sending a file to twelve people was the same thing as giving twelve people access?”

Myrto closed the laptop. The question remained.

Chapter 2: When the Private Price Lost Its Advantage

On Tuesday morning, Myrto came in determined to find out how far the presentation had travelled. The day before, two agents outside the private pre-sale list had already learned the price of Unit 504. She still hoped the chain was small enough to contain.

The sales manager opened a spreadsheet of enquiries received since the launch. Some names belonged to the twelve invited brokers. Others had appeared only after the PDF went out.

“How many new contacts?” Myrto asked.

“Seven who weren’t on the original list.”

“Seven in one day?”

“Seven that we know about.”

He scrolled further.

“One of the brokers we invited messaged this morning. His client received the same project from another agent.”

“At what price?”

“Our private price.”

The private price no longer felt private

The broker had been working with his buyer for several weeks. That was why he had been included in the first release: he had a client with the right budget, and the developer wanted to give him an advantage before the public launch.

But his buyer had received the same unit and price from someone else.

“I thought this was a limited pre-sale. My client has now received the same unit and price from another agent.”

The broker had presented early access as a benefit. A few hours later, the buyer saw identical terms from another source. The offer no longer looked limited. It looked like something that had not reached the public portals yet.

“If the buyer sees the same price from three agents, he won’t feel he has access to something rare,” Myrto said.

“He’ll probably start asking around.”

“That’s when yesterday’s forwarding becomes today’s commercial problem.”

Scarcity can disappear before a public launch

The value of a limited release lies in defined access: selected people can see certain units or terms before the wider market. Once the same information circulates freely, that advantage weakens even if the project never appears on a public portal.

Instead of asking whether they need to act quickly because access is limited, a buyer may ask why they should decide now if several agents can offer the same terms.

“I thought yesterday our problem was confidential information,” Myrto said.

“And today?”

“Today I’m wondering how exclusive our exclusive offer actually is.”

The buyer found a new negotiating argument

Closer to lunchtime, a buyer contacted the developer directly. He had seen Unit 504 through two agents and wanted the terms confirmed.

“I’ve been offered Unit 504 at €685K by more than one agent. Is there any flexibility if I proceed directly?”

Only a day earlier, €685K had been a private pre-sale price. Now its appearance through multiple sellers had changed how the buyer interpreted it. The conversation shifted from you have early access to I can get this from several people, so what else can you offer?

That did not mean the developer had to discount the unit. It did mean the original negotiating position had become harder to maintain.

VIP positioning could not survive uncontrolled circulation

That afternoon, Myrto displayed the presentation’s first page during a sales meeting: a polished render, minimal typography and the words PRIVATE PRE-SALE. Beside it were messages showing the same project circulating between agents and buyers.

“We spent months building the positioning for this project,” she said. “What does the buyer see now?”

“The same project coming from different people,” a manager answered.

Another team member objected. “Wide distribution isn’t necessarily bad. We want sales.”

“Public distribution isn’t bad,” Myrto replied. “But we haven’t launched publicly yet. We promised something different.”

The brokers were sharing opportunities as brokers normally do. The weakness lay in a process that tried to create scarcity through a freely transferable file.

Myrto stopped counting forwards

By Tuesday evening, identifying the first person who pressed Forward no longer seemed capable of solving the problem. The offer had reached other agents and buyers, and the private price was already part of negotiations.

Next to the original list of twelve brokers sat a second spreadsheet of new contacts, uncertain sources and buyers who had received the same offer from several sellers.

“So the problem isn’t that a thirteenth person saw the file,” the sales manager said.

“No. At some point, we stopped controlling who was part of the private launch but carried on acting as though it was still private.”

Chapter 3: Access Became Part of the Release

By Wednesday, Myrto had stopped trying to reconstruct the original PDF’s journey. The private price had reached uninvited agents, and the same offer was appearing through different brokers.

Another release was due in a few days. Eight more units would become available. Under the old process, the team would have exported another presentation and price list, then sent them with the same request: Please do not forward.

This time, Myrto opened the project in MLS RealtyHub.

“We’re not doing the same thing again.”

“No PDFs?” the sales manager asked.

“A PDF can still exist. I just don’t want the file itself to define access.”

“What should?”

“The person. A specific broker should be allowed to see a specific offer.”

They started with the audience

The first decision was which brokers would be included in the new private release.

“How many?” the manager asked.

“Nine for the first group. Remove two from Monday’s list and add three from the international team.”

“One group?”

“No. Put brokers working with international buyers in one group and those serving high-budget local clients in another.”

On Monday, the list of names had been a mailing list. It recorded who received the PDF first. Now the selected brokers formed part of the access setup for the release itself.

“This tells us who we’re opening the offer to,” Myrto said, looking at the first group. “Monday’s spreadsheet only told us who we sent something to.”

Then they chose which units each audience could see

The new release included eight units, but Myrto did not want every broker to see all eight. Four apartments suited international buyers. Two higher-value units were intended for brokers working with local clients. The remaining stock was not part of this stage.

“Open Units 504, 506, 611 and 702 to the first group,” she said.

“And the other four?”

“Not yet.”

The manager checked the group’s view. It showed the four selected units, current prices and related materials. The other units remained outside its scope.

“We kept treating the project as either private or public,” Myrto said. “What we need to decide is who sees which part of the stock.”

Audience and offer scope were now separate choices. A broker could know about the development without having access to every private unit and term.

A request tested the new process

Around lunchtime, a broker in the first group asked about Unit 708. He had heard about it during a project presentation but could not see it in his release. He said he had a buyer ready to discuss a reservation.

“Check the buyer’s budget and timing first,” Myrto told the manager.

The details fitted.

“Then give that broker access to 708.”

“To the whole group?”

“Why would we expand the offer for everyone because one broker has a relevant buyer?”

The manager adjusted the access. That broker could now see Unit 708; the rest of the group could not.

Instead of sending a page, screenshot or new presentation, the team changed the scope of the offer for the person who needed it.

An update no longer required another file round

Later that afternoon, information about one unit changed. Under the old process, the team would have exported another PDF, sent it to every recipient and asked them to ignore the previous version.

Old copies would still have remained in inboxes and chats.

Myrto’s team updated the project information in MLS RealtyHub and reviewed who had access to the affected unit. The change still required care, but it did not require another independent version of the entire private offer.

“So what stops a broker taking a screenshot?” the sales manager asked.

“Nothing makes screenshots physically impossible,” Myrto replied. “Today we solved a different problem. We decided who could access private stock and what they could see. How we respond to copying is tomorrow’s question.”

Chapter 4: The Screenshot

By Thursday morning, the sales manager had returned to that question.

“If a broker can still screenshot the price and send it to someone else, haven’t we built a more sophisticated version of the same problem?”

“No,” Myrto said. “But not because screenshots disappear. The difference is that we now have a defined starting audience, a limited offer scope and decisions we can make afterwards.”

The first test came before lunch

At 10:40, a broker called the sales team. A screenshot of Unit 708 had appeared in a WhatsApp group. It showed the unit number, private price and part of the payment terms. There was no visible name and no clear way to identify who had taken it.

The sales manager brought the image to Myrto.

“Can we prove who made this screenshot?” she asked.

“No.”

“Can MLS RealtyHub detect someone pressing the screenshot button?”

“No.”

“Then we won’t claim that it can.”

They opened the private release. The access setup showed which brokers had been granted access to Unit 708 and during which part of the release. That information offered a starting point for follow-up. It did not prove who created the image.

They could define the initial exposure

On Monday, an uninvited broker had appeared with the private price, and the team had no meaningful way to establish how large the audience had become after the PDF was sent.

Thursday was different.

“Who could see Unit 708 in this release?” Myrto asked.

“Five brokers.”

“Was it visible to the second group?”

“No.”

“So we know the initial access group. We still don’t know where the screenshot went afterwards.”

“Right.”

Myrto did not minimise the problem. Once copied outside the system, the image could not be recalled from every phone. But the team knew which offer it came from, which unit it concerned and who had originally been granted access.

They responded without accusing five people

“Do we remove all five brokers?” the manager asked.

“No. One screenshot isn’t a reason to accuse five people.”

“Then what do we do?”

“Confirm what information has moved outside the group. Speak to the brokers with access. Then decide whether this part of the release should remain open as it is.”

Future participation could be reconsidered if there was a sound basis for concluding that someone had ignored the agreed rules. That was an operational consequence, not a claim that the screenshot could be erased.

The team changed what it could still control

Two brokers were actively working with qualified buyers for Unit 708. The team retained their access while it reviewed the situation and temporarily removed the unit from the others’ view. Access to unrelated units remained as it was.

“The screenshot still exists,” Myrto said, “but we’ve changed what happens next.”

Later, another broker asked to see Unit 708 for a qualified buyer. The team decided to review the request rather than expand the audience immediately.

“On Monday, once the PDF was out, people could effectively join the release by forwarding it,” the manager said.

“Exactly. Now adding someone is our decision.”

What control meant

The sales director was unconvinced.

“The information leaked. We couldn’t stop it. Where is the control?”

“On Monday, we sent one file to twelve people and lost sight of the audience after that,” Myrto said. “Today, we know which brokers were given access to this unit. We can review that access, change who continues to see the offer and decide how future releases are handled.”

“But the screenshot is still out there.”

“Yes. Controlled risk does not mean zero risk.”

MLS RealtyHub could not make manual sharing impossible. It gave the developer a structure for deciding access before a release and responding when information moved beyond the intended audience.

Chapter 5: Private Became a Set of Decisions

Myrto walked into Friday’s meeting with her laptop. The next private release was due on Monday, but she had decided not to begin by preparing another presentation.

“Are we reviewing Monday’s materials?” the sales manager asked.

“Not yet. We’re reviewing the launch.”

“I thought that was what I meant.”

“You meant the files. That’s the habit we need to change.”

The presentation was only one part of a private release. The audience, selected stock, timing and response rules determined how the release worked.

They chose the brokers first

Twenty-three brokers had shown interest during the week. Some had contacted the developer directly; others had heard about the project through the earlier circulation.

“How many do you want for Monday?” the manager asked.

“How many have relevant buyers now?”

“Eight for certain. Maybe two more.”

“Then start with eight.”

“That’s smaller than the first launch.”

“That’s fine. The private phase isn’t about maximising reach.”

The other brokers were not rejected. They could be considered for a later stage. The initial audience was a commercial decision made before the release began.

Then Myrto limited the stock

The manager opened the twelve units available for the next phase.

“We’re opening five,” Myrto said.

“Only five? The others are available.”

“Available does not have to mean visible to every audience at the same time.”

Two units were set aside for a wider broker release. Another would remain outside the offer until the team reviewed Monday’s response.

The selected group could see five units, their current prices, plans and related materials. Requests for other units would be considered individually.

“That creates more decisions for us,” the manager observed.

“Yes,” Myrto said. “That’s managing the launch.”

They gave the private phase a review point

The first pre-sale had started at 9:30 on Monday, but the team had never clearly defined when to reconsider its audience. Information spread faster than the company’s planned release schedule.

This time, the brokers would receive access on Monday morning. The team would review buyer activity on Wednesday afternoon and decide whether to widen distribution. Thursday was a possible next stage, not an automatic public release.

They agreed on a response before they needed one

“Assume a private price is shared again,” Myrto said.

The manager sighed. “You want to plan for another leak?”

“I want to plan our response.”

They agreed on a sequence: identify the affected unit, review the access granted, speak to the relevant brokers and decide whether the offer or future participation should change. Nobody would be accused without evidence, and nobody would promise to retrieve every copied image.

Monday’s launch looked different

The manager reopened the original spreadsheet of twelve broker names. Four days earlier, it had felt like a complete plan. Now it showed only who had received a document directly from the developer.

Beside it, he opened the next release in MLS RealtyHub. The team had defined who could enter the private phase, which five units they could see, when the release would be reviewed and how an incident would be handled.

“So what do we call Monday’s launch?” he asked.

“Private.”

“We called the last one private too.”

“That was the problem. Last time, private was a label. This time, it’s a set of decisions.”

A confidential stamp could not answer who had access, which offer they could see or when that access should change. Those answers belonged to the process behind the release.

Frequently asked questions

Does a confidential PDF keep a developer’s pre-sale private?

No. It tells recipients how the document should be treated, but the file can still be forwarded or copied. A private release needs defined access and clear rules for the people involved.

Can controlled access prevent screenshots?

No. A person may still photograph a screen or share information manually. Controlled access helps the developer define the initial audience and offer scope, review the access granted and decide how to respond.

What should a developer decide before a private release?

Define who receives access, which units and terms each audience can see, when the release will be reviewed or expanded, and how the team will respond if information moves beyond the intended group.