The Spec That Wasn't Worth What He Thought

Roy called me after his sales agent sent him an email he didn't know how to answer.

"Ilan, I need you to help me think. Not legally. Business-wise."

Roy is a developer. He built two projects in Israel before he went to Bucharest. He takes pride in quality. When he builds, he doesn't compromise: real hardwood, not laminate. German taps. Kitchens that look like they came out of a design magazine. That's what brought him clients in Israel, and that's what he brought with him to Romania.

He priced the project by the same philosophy. "If it's worth more, it costs more," he told me when we spoke before the launch. "I don't build junk."

The problem started to show gradually. Not all at once.

In the first month of sales, the pace was slower than expected. Roy put it down to the season. In the second month, slower still. He started checking what was happening at competing projects within the same radius.

What he found surprised him. Projects with a standard spec, nothing special, were selling for significantly less than his price, and they were full. Local buyers, and even some of the foreigners who bought there, weren't looking for what Roy thought they were looking for. They were looking for a good apartment, in a good location, at a price that fits the local market. Not imported flooring.

His sales agent in Bucharest was sharp and clear: "Lower the price. The market here won't pay for this finish. I'll sell your whole project within a month."

Roy didn't know where to go with that. Lowering the price means hitting profitability directly, on every unit sold. Lowering the spec means building something cheaper, but it also means changing, midway, what he had promised.

And that's exactly where I came in.

I asked to see the sale contracts already signed with the first buyers. Not many, eight units, from the first wave. I read them slowly.

The technical specification was written there explicitly. The type of flooring, the tap manufacturer, the quality of the kitchen. It wasn't a vague marketing promise; it was a contractual obligation. I told Roy plainly: you can't downgrade those eight units. If you lower the spec on what's already signed, you expose yourself to a breach-of-contract claim, no matter how much it would help your cash flow.

But the second question Roy asked me was harder. "So I lower the price on the next units. What does that do to the eight who already bought?"

I explained it to him simply. If he now sells a similar unit for less, the first eight buyers will find out. They always find out; neighbors talk. They'll feel they paid a sucker's price. Some of them will check their contract, and if there's a price-protection clause, they'll demand compensation or a refund. Even without such a clause, it's a serious blow to trust, and that translates into negative reviews, worries about the next installments in the payment plan, and a reputation that follows him to his next project.

There's also a quieter problem, but no less dangerous. The moment a unit sells for less, that price becomes a comparable for every future deal in the area, including bank valuations for the next buyers who want financing. One low price can drag down the perceived value of the entire project, not just the discounted unit.

"So what, I'm stuck?" he asked.

Not stuck. You just need to sell two different products, not the same product at different prices.

I suggested he split the remaining units into two defined spec levels: one close to what he had built, at the price he wanted, and one simpler, at a price the local market recognizes. It sounds like a technical difference, but it's fundamental: a buyer who paid for a premium spec can't claim he was wronged, because the cheaper unit is simply a different product, with a different spec, written into a different contract. That keeps him consistent with the first buyers and gives him real flexibility in the market without hurting them.

It worked. Not because the numbers turned magical, but because he was finally selling people what they actually wanted to buy, without hurting those who had already believed in him.

I think about this a lot when Israeli developers go abroad. The most common mistake isn't in the construction or the pricing. It's in the quiet assumption that what worked in Israel will work just as well somewhere else. The local market doesn't know, and doesn't need to know, what worked for you in Petah Tikva.

And if you've already signed contracts with an explicit spec, remember that this obligation doesn't move because the market is struggling. And a price cut never stays secret in a single project. Talk to a lawyer before you change course, not after the first buyers have already found out.

I think about these two stories together, because they're the same mistake in opposite costumes. Oren believed a number someone else put together for him. Roy believed a number he put together himself, from experience that had proven itself somewhere else. In both cases, the number wasn't false; it just wasn't checked against the reality in front of them. In international real estate, the most dangerous number isn't the one someone lied to you about. It's the one nobody bothered to check, including you.