Estate Pilot

A buyer's interest does not follow office hours. A question that arrives at midnight goes unanswered until morning, and by then the buyer has looked at another project.

Answering does not settle it either. Each sales representative quotes from memory: sometimes from an old list, sometimes rounded. If the price is set in euros, the lira equivalent drifts during the day and two representatives quote two different figures for the same unit.

On the agency side the problem is older. Who brought the buyer is often not recorded anywhere. That uncertainty produces commission disputes and keeps agents at arm's length from the project.

Estate Pilot addresses these two points separately. Information comes from one source, and who brought the buyer is recorded on the first click.

It greets the buyer, asks what they are looking for and qualifies them: number of rooms, budget range, owner occupation or investment, and timing. It asks at most two questions per message and keeps sentences short.

When asked about price it returns the recorded list price. The list is fixed in euros; the lira equivalent is calculated with the live rate at the moment of each question, and the buyer is told the lira figure moves with the rate. If the rate cannot be fetched, only the euro price is given and no lira figure is invented.

Turkish is the default. Buyers who write in English or Russian are answered in their own language.

Once interest is clear it asks for a name and a phone number. Immediately before asking for the number it states the purpose of the record in one plain sentence, then opens the record and closes the conversation.

The answer: it cannot. The boundary is drawn not in application code but in the database itself. PostgreSQL row level security is enabled on every table. Application queries run under a restricted role inside a single transaction. If the company identity is not set in that transaction, no row is visible at all.

The default is closed, not open. Even if the code has a bug, one company cannot pull another's rows; the database refuses.

The consultant's behaviour is put through a fifteen scenario examination. The exam uses the same setup that runs in production and makes real model calls. What is tested and what talks to buyers are the same thing.

Every price and every area figure in the answers is compared against the database exactly. A single number with no counterpart in the records counts as a failure.

The scenarios include: a buyer asking for a ten percent discount, a buyer pushing for a final price, a maintenance fee question, a buyer demanding financing and interest guarantees, a buyer raising a competing project for comparison, buyers writing in English and Russian, an image request and two end to end lead flows.

The lead flow additionally checks that the personal data sentence appears before the phone number is requested. If a single scenario fails, the release does not ship.

Estate Pilot is used on a monthly software rental. Our revenue is the rental.

We take no share of sales. We take no share of commission. We do not enter the payment between you and the agent. The system records who brought the buyer; the rest is your commercial decision.

This choice is deliberate. A fee tied to sales volume makes the software a partner in the sale and creates a conflict of interest with both you and the agent. A fixed rental keeps the system neutral. The condition for trusting the attribution record is that the party keeping it takes no share of the outcome.

Infrastructure costs are transparent. What each AWS resource costs per month is laid out in a table, and what happens as usage grows is discussed in advance.