What will this
actually cost you?
Most agencies answer that with a form. Here is the real model instead. Tell it how your leads arrive and what they need to reach, and it prices the build in front of you, showing the workflow you would be paying for as it assembles.
Show how that is worked out
| Line | Amount |
|---|---|
| Base buildDiscovery, the core workflow, error branches, retries and run logging. Every build has this. | $400 |
| Each extra lead sourceThe first is in the base. Every additional one is a different payload shape to parse and dedupe against. | $150 |
| Each system connected (2)Auth, field mapping, and handling what happens when that system is down. | $240 |
| AI reply classificationReading what a lead actually said, deciding what it means, and routing on it. Includes the prompt work and the fallbacks. | $400 |
| Volume at around 300 a monthHigher volume does not cost per lead. It forces real retry, queueing and error handling, which is build time. | x 1.16 |
| Estimate | $1,150 to $1,650 |
The band is real uncertainty, not padding. It narrows to a fixed number after the audit call, once we have seen the actual payloads and the actual CRM. We do not start work on an estimate.
Three things, and none of them is your size.
We do not price off your revenue or your headcount. We price off how much irregular work the system has to absorb, because that is what takes the time to build.
How many shapes the input arrives in
One web form is a solved problem. Bayut, Property Finder and Dubizzle notification emails, a webhook and a WhatsApp message are four different parsing jobs, and the same buyer often appears in all of them within a minute. Deduplication is usually the fiddliest part of a lead build, and it scales with sources, not with volume.
Whether anything has to make a decision
Moving data is cheap. Judging it is not. The moment the system has to tell "send me the floor plan" apart from "not interested" apart from "call me at 4", you are into prompt work, fallbacks for when the model is unsure, and a rule for what happens when it gets it wrong. That is the single biggest line item, and it is often worth it.
What happens when something breaks
The difference between a demo and a system you can rely on is almost entirely error handling: retries, dead letter queues, alerts to a human, and a log you can query when someone asks whether a lead ever got a reply. It is unglamorous, it is most of the engineering, and skipping it is how automations quietly lose leads for a month.
The costs that are not ours.
Quoting a build without naming these is how a project ends up over budget on someone else's invoice. All of them are paid directly to the vendor, not to us.
- Your automation platform. n8n Cloud, Make or Zapier bill you directly, and self hosted n8n needs a server. Which one is right for you is a real decision, covered in our comparison of the three.
- WhatsApp Business API messaging fees, billed by Meta per conversation. Approval is usually the slowest part of a WhatsApp build, and it is out of our hands.
- AI model usage, if the build classifies replies. Real world lead volumes put this in single digit dollars a month, but it is metered and it is yours.
- Your CRM, your calendar, your phone system. We connect what you already pay for, and we will tell you when the honest answer is that your CRM is the actual problem.
The ones people actually ask.
How much does business automation cost?
For a single lead source feeding one system, a build is usually 450 to 600 dollars one time, plus around 130 dollars a month to run. A full lead pipeline with several sources, a CRM, AI reply handling and follow up sequences typically lands between 1,400 and 2,400 dollars, plus 250 to 400 a month. The estimator on this page works out where your own setup sits, and shows the arithmetic.
Why do you not publish fixed packages?
Because fixed packages are almost always wrong in one direction or the other. Two agencies both saying they want WhatsApp follow up can differ by a factor of four once you look at how their leads actually arrive. A package either overcharges the simple case to cover the complex one, or underquotes the complex one and turns into an argument later. A range tied to your inputs is more honest, and the audit call turns it into a fixed number before any work starts.
What is the monthly fee actually for?
Hosting, monitoring and repair. Portals change their email format without warning, WhatsApp templates get rejected, APIs deprecate endpoints. Something in a live automation breaks every few months, and the question is only whether someone notices before your leads do. The monthly covers us watching the run logs, fixing breakages, and small changes. It is not a licence fee, and you own the workflows either way.
Do you charge for the audit call?
No. Twenty minutes, we map how the work happens today, and you get a straight answer about what is worth automating first, including the parts we think you should leave alone. If the honest answer is that a spreadsheet and a habit would fix it, we will say so. There is no deck.
What if the real build costs more than the estimate?
The estimate becomes a fixed quote after the audit, once we have seen the real payloads and the real CRM, and that quote is what you pay. If we underscoped it, that is our problem and we absorb it. The only thing that changes the price after that is you asking for something that was not in the scope, and we will tell you before we build it, not after.
Do you only work with Dubai real estate?
That is where most of our lead response work is, because the volume and the WhatsApp habit make it the clearest fit. The same systems run for visa and immigration firms, clinics, and any business where enquiries arrive faster than a small team can answer them. The pricing model on this page is not property specific.
Turn the estimate into a number.
Twenty minutes on a call, we map how your leads actually arrive today, and the range above becomes a fixed quote. If the honest answer is that you do not need us yet, you will get that instead.