Cost

What a property bot costs a brokerage

A brokerage bot is ten to eighteen delivery days. Showing listings is quick; the cost is ingesting portal feeds, deduplicating the same unit listed by three agents, and matching a buyer's brief to new inventory fast enough to matter in a market where the first call wins.

What a property bot costs a brokerage: effort, cost and what moves it

Fixed price: $6,720 USD
Delivery: Awaiting sign-off

Effort: 16 delivery days
Biggest cost driver: Feed ingestion and deduplication across portals
Commercial basis: Fixed price agreed before work starts; scope changes quoted separately
Year one, beyond the build: Support retainer, Managed hosting, plus portal subscriptions, image storage and delivery

As of 2025-10-01, Telegram Bot API 13.4

Why this costs what it costs

Dubai brokerages already have their inventory somewhere — a CRM, a portal back office, a spreadsheet, usually all three disagreeing. The bot is rarely the place inventory should live, and a project that starts by asking the brokerage to maintain listings in a fourth system fails within a month. So the first architectural decision is which system is authoritative, and the answer is almost never the bot.

From there the expensive problem is duplication. The same apartment appears from three agents with different photographs, different descriptions, sometimes a different asking price, and a buyer who receives the same unit three times stops reading the bot. Deduplicating across sources needs rules about what identifies a unit — building, floor, unit number where available, size, and a similarity judgement where it is not — plus a decision about which listing wins. That work is invisible in a demo with ten listings and unavoidable at portfolio scale.

The feature that actually earns the fee is matching. A buyer describes a brief once — two bedrooms, Marina, under a number, ready or off-plan — and receives new matching inventory the moment it lands. In a market where the first agent to call frequently wins the deal, minutes matter, and a bot that pushes a match instantly is worth more than one that presents a searchable catalogue. Building this well means storing briefs as structured criteria rather than as free text, and running new inventory against every open brief as it arrives.

The last piece is compliance, and it is specific here. Property advertising in Dubai carries requirements about permits and listing details, and the exact obligations depend on how you advertise and what you are advertising. That is a question for your compliance function rather than for us, but it changes the build: whichever identifiers must appear on a listing become required fields, and a listing missing them should not be publishable by the bot at all. Building that rule in is cheap; retrofitting it after a warning is not.

The breakdown

Work	Days	Cost	What it covers
Inventory source design	2	$840	Which system is authoritative, how listings reach the bot, and what happens when two sources disagree. The decision that determines whether this works at all.
Feed ingestion	3	$1,260	Pulling from portal back offices or your CRM, normalising fields, handling images, and coping with a feed that changes shape without notice.
Deduplication	2	$840	Identifying the same unit across sources and agents, choosing which listing wins, and keeping the decision stable so a buyer does not see it reappear next week.
Search and browse	2	$840	Filtering by area, bedrooms, price and status inside a chat, with results sized for a phone and photographs that load on a weak connection.
Buyer briefs and matching	3	$1,260	Structured criteria captured once, then run against new inventory as it arrives, with an instant push to the buyer and the agent. The feature that pays for the project.
Viewing scheduling	2	$840	Booking a viewing against an agent's real calendar, with confirmation, reminder and reschedule, because the whole point is a viewing rather than a browse.
Agent surface	1	$420	What agents use daily: incoming enquiries, whose lead it is, brief details, and the ability to send a listing directly into a buyer's chat.
Compliance fields and handover	1	$420	Required listing identifiers enforced as mandatory fields, so an incomplete listing cannot be published, plus deployment and a session with the sales floor.
Total	16	$6,720	Fixed on signature. Scope changes are quoted separately, never absorbed silently.

What moves the number

Portal feeds change shape without notice and without versioning.

Ingestion must validate at the boundary and fail loudly rather than silently importing a field into the wrong column. A feed change that goes unnoticed corrupts inventory slowly, which is the hardest kind of failure to unwind.

The same unit is routinely listed by several agents on several portals.

Deduplication is a core requirement rather than a refinement, and its rules are brokerage-specific. A buyer who receives one apartment three times stops opening the bot, and that is unrecoverable.

Property advertising in Dubai carries permit and listing detail obligations.

Whichever identifiers your compliance function requires become mandatory fields the bot enforces before publishing. Confirm the current requirements with your own compliance team; they change and we do not advise on them.

Telegram captions are limited to 1,024 characters and media groups to ten items.

A listing with twenty photographs and a long description must be paginated deliberately. It is a small constraint that shapes the whole presentation layer, and discovering it late means redesigning it.

Off-plan and ready inventory behave differently at every stage.

Payment plans, handover dates and developer information apply to one and not the other. A brokerage handling both is modelling two products, and saying so up front is cheaper than a mid-build discovery.

Lead ownership rules are a brokerage policy, not a technical default.

Who owns a buyer who arrived through the bot, and what happens when two agents both have a claim, must be decided by management before launch. It is the single most reliable source of internal conflict in these projects.

What year one actually costs

Running cost	Year one	Detail
Support retainer	$3,480/yr	Portal feeds change, and a brokerage bot depends on several of them. This is the category where an unmaintained integration degrades quietly into wrong inventory.
Managed hosting	$660/yr	Runtime, listing data and buyer briefs, with backups. Brief history is genuinely valuable — it is the record of what your market has been asking for.
Portal subscriptions	billed by the provider	Property Finder, Bayut and similar listing fees stay on your own contracts at your own negotiated rates. The bot reads what you already pay for.
Image storage and delivery	billed by the provider	Property photography is the largest data a brokerage bot handles. Cost is driven by portfolio size and by how disciplined the image pipeline is.

Buying the same thing elsewhere

Where you buy it	What the money buys	What you carry
Portal lead forms only	Leads arriving from Property Finder and Bayut with no technology of your own, using channels buyers already trust. This works and most brokerages start here.	Every lead is shared with whoever else pays for the position, response speed is your only differentiator, and you own no relationship with the buyer after the enquiry.
A property CRM's own client portal	Already holding your inventory and your agent structure, with matching features that work and nothing to reconcile.	Buyers must register and log in, and portal login rates are low enough that the matching feature rarely reaches the person it was built for. The bot exists mostly to remove that login.
WhatsApp broadcast lists	Immediate reach into the channel most Dubai buyers actually use, with no build cost and no learning curve for agents.	Manual, unstructured, and impossible to match against a brief. It also degrades into spam quickly, and per-conversation pricing on the business API makes broadcasting at scale expensive.

Questions about the money

Where does the inventory come from?

Whichever system is already authoritative for you — a property CRM, a portal back office, or a feed. Asking a brokerage to maintain listings in a new system is how these projects die, so the bot reads and never becomes the master copy.

How does it stop sending the same apartment three times?

Deduplication rules agreed with you: building and unit where available, size and location similarity where not, and a stable decision about which listing wins so the same unit does not resurface under a different agent next week.

Can buyers book viewings directly?

Yes, against the agent's real calendar with confirmation and reminder, because a viewing is the actual objective. It uses the same holds-and-sync approach as the booking builds, which is why that line is two days rather than one.

Does it work for off-plan as well as ready property?

Yes, and they are modelled separately because payment plans, handover dates and developer details apply to one and not the other. A brokerage doing both should say so at kickoff, since it affects the data model rather than just the copy.

Who gets the lead?

Whoever your rules say, and the rules are yours to set before launch — listing agent, round robin, first responder, or area ownership. We will implement any of them and we will not pick for you, because this is the decision most likely to cause an argument on the sales floor.

What about the permit numbers on listings?

Whichever identifiers your compliance function requires are enforced as mandatory fields, so an incomplete listing cannot be published through the bot. Confirm the current obligations with your own compliance team — they change, and we do not give regulatory advice.

Can it work in Russian and Arabic as well as English?

Yes, and in this market that is often the point. It adds roughly a day per language for the conversational surface; listing content itself is whatever your source system holds, which is usually English only and worth knowing before you promise otherwise.