TL;DR
- Most "free moving quotes" products are lead-resale funnels. The customer's number becomes inventory.
- A useful comparison marketplace needs structured intake, a small matched set of suppliers, and replies people can compare in writing.
- In Dubai, the quote sits inside a larger dependency chain (building NOC, tenancy registration). Ignoring that produces quotes that cannot be used on the date the customer asked for.
- We ship a short form, match up to three vetted movers, and keep replies on email or WhatsApp text — no calls required.
Moving flats in Dubai has a familiar failure mode. You fill in a form. Your phone rings. Then it rings again. By evening you have numbers in WhatsApp threads, PDFs, and voice notes. One includes packing. One does not say. One is a single figure with "+ VAT" at the end. Nobody asked which floor you live on.
I am building a small quote-comparison service for movers in the UAE. This post is for people who build two-sided products, not for people looking for a truck. It is about the product decisions that matter before the matching algorithm gets interesting.
The quote is the product — and free text destroys it
A moving price depends on variables customers do not always know they need to share:
- Home size as a proxy for volume (even "2BR" varies a lot)
- Floor and lift access, including whether a service lift must be booked
- Packing scope
- Distance and route (JVC to Marina is not the same job as Marina to Abu Dhabi)
- Move date, including weekend and month-end lease turnover
- Building rules: most towers want a move-in or move-out permit (NOC) with time windows and often a deposit
A free-text "tell us about your move" box captures maybe two of these. The mover then either calls (your phone rings) or quotes high to cover unknowns. Either way, the customer cannot compare like with like.
So the first engineering job is intake design: turn a fuzzy request into a record a mover can price without a call.
What we ask today
We keep the form short. Every field costs completions. The live flow asks for:
- Name, origin area, destination area
- Home size from a fixed list (Studio, 1BR, 2BR, 3BR, Villa, Office) — not free text
- Move date
- A WhatsApp number and an email
- Optional notes
The fixed list for home size does more work than it looks like. It turns the biggest pricing variable into an enum, which means routing can prefer movers who actually handle that size of job.
The next product step — and the one I would push anyone in this space to take — is collecting access details as structured fields too: floor, service lift yes/no, NOC already booked yes/no. Each tap removes a reason for a call.
The W3C forms tutorial is still a good reminder that labels, grouping, and clear instructions matter as much as field count.
Lead resale is the default model — and the incentives show
Charging movers instead of customers keeps the service free for the person moving. That part is fine. We do the same: movers pay, customers do not.
The broken part is fan-out. If you earn per lead and the customer does not pay, every extra company that receives the lead is extra revenue. Leads get blasted wide. Customers get ten calls. Movers compete on who dials first, not who quotes best.
Moving is a rare, high-stakes transaction. People move infrequently. The job involves everything they own. There is little repeat purchase to win back if it goes wrong. Volume-first lead models fit poorly.
So we made two decisions that cost short-term revenue:
- Each request goes to up to three movers, chosen for fit. Three is enough to compare and few enough that each mover treats the job as winnable.
- Replies come by email or WhatsApp text. No calls needed. Written quotes leave a record, sit side by side, and can be forwarded to a partner. Many people moving in the UAE are juggling a job start, a lease, and a school search. A text they can answer at midnight is worth more than a call they missed.
Normalise the output or you are just forwarding messages
Even with good intake, quotes arrive in different shapes. Comparison needs a shared schema. The fields I think belong on a comparable quote:
| Field | Why it matters |
|---|---|
| Total price, VAT included or excluded | Most common "that's not what you quoted" fight |
| Packing scope (none / fragile / full) | Biggest hidden difference between "similar" quotes |
| Materials included | Often charged separately |
| Dismantling / reassembly | Commonly excluded by default |
| Crew size and vehicle | Proxy for duration |
| Insurance / liability terms | What happens if something breaks |
| Payment terms | Deposit vs balance on completion |
| Validity date | Quotes expire around month-end |
You do not need machine learning for this. You need a template movers can fill, plus patience to map free-text replies. Once quotes share a schema, "compare" stops meaning "read three WhatsApp threads."
Honest limitation: you can normalise what is written, not what is left out. If dismantling is not mentioned, the UI should say not stated — not invent "included" or "excluded."
Trust signals customers can check
"Vetted movers" is empty on its own. Trust only works if the customer can verify something, or if the platform states exactly what it checked.
What belongs on a mover profile, in my view:
- Licensing stated precisely (what was checked, when)
- Scope of work: residential vs office, local vs inter-emirate, packing in-house vs subcontracted
- Reviews tied to real jobs where possible, and labelled clearly where not
For search engines, the same honesty applies to structured data. schema.org has a MovingCompany type. Fill only what the page shows. Google's spam policies call out region/city doorway pages that funnel users to one URL. Area pages should exist where there is real coverage and something specific to say — for example, towers in an area known for tight lift booking windows.
The move is not only the truck
In Dubai, the quote sits inside a sequence. The new tenancy often needs registration through Ejari with the Dubai Land Department. Utilities need connecting. The building wants its NOC. If the NOC is not booked, the best quote in the world still cannot happen on the requested date.
A useful quote product nudges these dependencies at the right moment without trying to own every step. A short checklist beside the quote ("Have you booked your building's move permit?") prevents more failed moves than a slightly cheaper price.
Official Ejari fee figures are published by Dubai Land Department on that service page (registration plus knowledge, innovation, and partner fees depending on channel). We do not invent market averages; we point people at the authority and at the operational checklist.
What I'd tell anyone building a lead-gen marketplace
- Design intake for the supplier's pricing model, not for your CRM's vanity fields.
- Cap the fan-out. Fewer, better-matched leads produce better quotes and a customer who does not regret giving you a number.
- Normalise the output. Without a common schema you are a forwarding service.
- Make trust checkable. Say exactly what you verified.
- Respect the channel. Let people reply by text.
That is the thinking behind the flow at MoveWise UAE: one short form, up to three matched movers, replies by email or WhatsApp text. There is still more to build on the normalised comparison table. The hard part was never the code. It was deciding what not to do with the customer's phone number.
If you've shipped a marketplace with a "who pays" tension like this, how did you balance supplier revenue against customer experience?
About the author: Waqas Jawed builds MoveWise UAE, which helps people moving in Dubai, Abu Dhabi, Sharjah and Ajman compare quotes from vetted movers. Contact: cs@movewiseuae.com.
This post was drafted with AI assistance and edited and fact-checked by the author.
