惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

宝玉的分享
宝玉的分享
J
Java Code Geeks
S
SegmentFault 最新的问题
L
LangChain Blog
M
MIT News - Artificial intelligence
Stack Overflow Blog
Stack Overflow Blog
IT之家
IT之家
量子位
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
雷峰网
雷峰网
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
The Cloudflare Blog
MongoDB | Blog
MongoDB | Blog
Microsoft Security Blog
Microsoft Security Blog
腾讯CDC
H
Help Net Security
阮一峰的网络日志
阮一峰的网络日志
Jina AI
Jina AI
N
Netflix TechBlog - Medium
A
About on SuperTechFans
博客园 - 叶小钗
美团技术团队
人人都是产品经理
人人都是产品经理
D
DataBreaches.Net

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
I Built 13 AI Tools for Dubai Real Estate Agents in 3 Wee...
Amar Kovacev · 2026-05-16 · via DEV Community

Amar Kovacevic

Most "AI for real estate" tools fail for the same reason: they wrap GPT-4 around a generic prompt and ship it. An agent in Dubai Marina tries it, gets a description that says "stunning waterfront property" and "unparalleled luxury", and uninstalls in 90 seconds. Because every listing on Property Finder already says that.

I spent three weeks building AgentsAI — 13 AI tools and a CRM aimed at UAE real estate agents. The Dubai market is brutal: ~50,000 licensed agents, ~85% churn within 24 months, and tools that don't know the difference between Arabian Ranches and JVC die fast.

Here is what actually mattered, and what I'd do differently.

1. Vertical AI lives or dies on market-specific tokens

The single biggest unlock was building a UAE-specific prompt vocabulary. Generic LLMs don't know:

  • The pricing convention is AED per sqft (not USD per sq ft, not AED per sqm — getting this wrong instantly outs you as a foreign tool)
  • BUA vs plot size — for villas this is a make-or-break listing field
  • Freehold vs leasehold by zone (Marina = freehold, parts of Sharjah = leasehold)
  • DLD/RERA permit numbers are mandatory on portals
  • The cultural tone shift between "luxury" and "family-friendly" listings — "stunning view" sells in Marina, "close to British school" sells in Mirdif

I built a 300-line system prompt that bakes this in. The output went from "this could be anywhere" to "this is clearly Dubai" in one prompt revision. Agents started using it for hours, not seconds.

SYSTEM: You are a senior UAE real estate copywriter.
- Use AED (never USD)
- Distinguish BUA (built-up area) and plot
- Reference RERA permit if provided
- For Marina/Downtown/Palm: target HNW, lead with view + lifestyle
- For Mirdif/Arabian Ranches: lead with schools + community
- For JVC/Discovery Gardens: lead with affordability + commute
- Never use: stunning, breathtaking, unparalleled, nestled, oasis

Enter fullscreen mode Exit fullscreen mode

That last line — banning AI-detector words — alone made the copy feel more human than 90% of agents writing it themselves.

2. Speed is the actual feature

I assumed agents would care about quality. They cared about time-to-first-listing.

The benchmark from agents I interviewed: 18–25 minutes to write a good listing manually. Including the back-and-forth on tone with their broker.

Initial AgentsAI version: ~12 seconds with grok-4-1-fast-non-reasoning. Agents loved it but it was still on the "magical" side of the line — they didn't trust it yet.

After watching screen recordings, I realized agents needed to see it appear. Streamed tokens, even fake streaming on cached results, made the perceived quality jump. Same content, 3x retention.

const stream = await xai.chat.completions.create({
  model: 'grok-4-1-fast-non-reasoning',
  stream: true,
  messages: [...],
});
for await (const chunk of stream) {
  res.write(`data: ${JSON.stringify(chunk.choices[0].delta)}\n\n`);
}

Enter fullscreen mode Exit fullscreen mode

3. The CRM was the secret weapon

I almost didn't build it. Agents already have Bayut CRM, Property Finder CRM, sometimes Salesforce.

But after talking to 12 agents, none of them actually used those CRMs. They lived in WhatsApp + notes app + a spreadsheet. The portals' CRMs were too heavy for the day-to-day "Imran called about the 2BR Marina, budget 2.4M, wants viewing Friday" workflow.

So I built a 4-stage pipeline (Lead → Qualified → Viewing → Offer → Closed) with one rule: adding a lead must take under 15 seconds on mobile. Just name + phone + intent + budget. Everything else is optional.

This is the part agents actually return to daily. The AI tools are what got them in the door; the CRM is what made AgentsAI sticky.

4. Pricing: I sold credits, not seats

The default SaaS playbook says per-seat. For agents, per-seat is a non-starter — they're 100% commission, no budget authority, and they hop brokerages every 11 months.

I went with monthly generation credits: Free (5/mo), Starter (100/mo, $29), Pro (500/mo, $79), Team (2000/mo).

This:

  • Killed the "but I won't use it much" objection — they can try free
  • Made upgrades natural (you hit 5, you upgrade)
  • Made the tool poach-proof — credits transfer with the agent, not the brokerage

Conversion to paid was ~12% in week one, way better than I expected for a cold launch.

5. The non-AI features that mattered most

Three "boring" features that drove more retention than the AI did:

a) Virtual staging. Upload empty room photo → AI furnishes it. Agents go nuts for this because professional staging photos cost AED 800–1500/room from a photographer. We do it for one credit.

b) PDF brochure templates. Four pre-built print-ready layouts (Luxury, Minimal, Classic, Investor). Agents share these on WhatsApp constantly. Branded PDF = professional credibility for an agent who's 6 months in the industry.

c) WhatsApp templates. Not the AI generation — the categories. "First outreach", "Viewing confirmation", "Offer made", "Price drop". Agents told me they were tired of staring at a blank chat. Naming the scenario was the unlock.

6. What I'd do differently

  • Charge from day one. I had a free tier from launch. Some agents abused it (5 burner emails for 25 free generations). Should have required card on file from week two.
  • Skip the desktop sidebar on mobile. Built it lg-only at first. 70% of usage is mobile (agents in cars between viewings). Took two iterations to get the horizontal-scrolling chip nav right.
  • Don't build a blog index page. Build 200 landing pages. I wrote 199 SEO-targeted blog posts ("How to Write an Arabian Ranches Villa Listing for Family Buyers" etc) and that's now driving 60% of organic traffic. Should have started with content, not the tool.

The stack, for the curious

  • Next.js 14 App Router on Vercel-equivalent VPS (PM2)
  • PostgreSQL for everything (users, generations log, leads, blog cache)
  • xAI Grok for text (grok-4-1-fast-non-reasoning) + vision (grok-4.3) + image (grok-imagine-image)
  • NextAuth with Credentials + bcrypt
  • Stripe for subscriptions (live mode, signed webhooks)
  • Tailwind v3 + Cormorant Garamond serif headlines for editorial brand

Total cost so far: ~$40 in xAI API + $7/mo VPS slice. Revenue trajectory makes that look ridiculous.

TL;DR

Vertical AI works when you go deep on one industry's vocabulary. Generic prompts produce generic output. Speed beats quality. Build the boring CRM. Price for the user, not the buyer. And start with content if you want compounding traffic.

If you're a UAE agent reading this — try AgentsAI free. 5 generations a month, no card needed. Let me know what's broken and I'll fix it the same day.