Price Approximate Meant Budget

The spreadsheet looked like it had survived three different admins.

One column said `Client Name`. One said `Project??`. One had phone numbers with and without `+20`. And in the middle there was a header that read: `Price (approximate)`.

At first glance, that sounds like inventory data. Unit price. Asking price. Something copied badly from a portal export.

But the rows didn't behave like unit prices.

`3,200,000` `2,750,000` `4,000,000`

Next to them were notes like `New Cairo`, `ready`, `2 bed maybe`, `call after 10`. The numbers looked too clean, too buyer-shaped. Not exact like a developer price list. More like the way someone answers a rep on WhatsApp when they don't want a long conversation yet.

So I stopped reading the sheet like a CRM and started reading it like chat residue.

One row stayed with me.

Name: `M. Adel` Source: `referral` Project: `blank` Price (approximate): `3.5` Last note: `asked for location`

That `3.5` could have meant anything if you trusted the header. Three and a half what. Million? Cash? Down payment? A unit he had seen somewhere else?

Then I found the thread.

10:58 PM `مساء الخير، عندكم حاجة في المستقبل أو التجمع؟`

11:01 PM `في يا فندم، حضرتك بتدور على كام أوبتو؟`

11:04 PM `في حدود ٣ ونص كده. مش عايز أبعد قوي.`

That was the column.

Not price. Not approximate listing value. _Budget, in the loose Egyptian way people actually state it._ A number dropped in the middle of a chat, rounded, casual, carrying more truth than a formal form ever gets.

The next part is what made the row useful.

The rep didn't answer with a brochure wall. He sent two options and kept both inside the number the buyer had casually thrown out.

11:09 PM `عندي اوبشن 2 bed في حدائق المستقبل داخلين في الرينج ده، وواحدة أهدى شوية ناحية المستثمرين.`

11:10 PM `ابعتلي اللوكيشن`

That message usually tells you more than the sheet does. Not "send details." Not "what are your payment plans." A location pin request in Cairo real estate is often the first honest filter. The buyer is checking commute, family distance, school run, whether the area is real to him or just ad language.

The spreadsheet only preserved the ugliest version of that moment: `Price (approximate): 3.5`.

But what happened in the chat was clearer. He had already priced himself. He had already ruled out whole areas. The number was not a unit field. It was a boundary.

Later in the thread, at 11:22, after the pin and one plan, he asked the real question:

`والكاش فيه كلام؟`

That was the confirmation. When Egyptian buyers say a number early, they usually don't mean "show me units priced exactly here." They mean: show me what my life can reach from here, and then tell me if cash can move it a bit.

Messy exports hide this all the time. Headers come out wrong. Columns drift. Humans type half-notes. Still, a row can tell the truth if you read it in the language it was born in.

Sometimes `Price (approximate)` is just the budget. And sometimes that one badly named column is the only honest thing in the whole sheet.