What changes about search and automation as my business grows?

People tend to assume that growing means doing something different. Mostly it means the same three things breaking in a new place. Knowing which stage you are at saves buying the fix for the next one.

One location, one team

Everything here is bought by being visible and by answering first. Nothing about the internal process is the constraint yet, because there is only one calendar and one person who knows what is in it.

• A page for each thing you sell and each area you cover, not one page listing everything
• A Google Business Profile, filled in completely. It is the only item here that works the same week
• Text that arrives in the HTML, and your name, hours and services in structured data
• One instant reply that answers the question and offers a booking, in Arabic and English
• A second message to anybody who went quiet

The last two are the whole automation at this stage, and they are usually built onto tools the business already pays for rather than anything new.

Several teams, branches or countries

The moment there is more than one calendar, answering fast is no longer enough, because a fast answer sent to the wrong branch is a slow answer. This is where the work turns into routing.

• Deciding from the enquiry itself which branch, team or specialist it belongs to, and sending it there
• A page per location, written for that location rather than the head office with the city swapped
• Arabic written rather than translated, because a machine-translated second site reads as a foreign one
• Quotes and invoices built from the enquiry instead of retyped, then chased when they go unpaid
• The enquiry landing in the CRM already filled in, so nobody copies it across a second screen
• A weekly report per branch that the owner reads without asking anyone for it

The failure mode at this stage is the same detail being typed three times, into WhatsApp, then a spreadsheet, then an invoice. Every copy is a chance to get it wrong, and none of it is work anybody wanted to do.

When the systems stop talking to each other

Past a certain size the bottleneck is rarely the enquiry any more. It is that the accounting system, the scheduling system and whatever the operations team actually uses were bought in different years for different reasons and have no interest in each other.

That work is integration, data and, when nothing off the shelf fits the process, an application built for the business and deployed to production. It is quoted per project rather than as a monthly product, because no two of these are the same shape. This is the ground the automation work is built for, and it is where solution architecture and cloud experience earn their price.

One rule holds at every size: the workflows run in your own accounts, under your own logins, with the data in your systems. There is no platform of ours in the middle, and if we vanished tomorrow it would keep running.

What stays the same at every size?

Be findable

A page per thing you sell, per place you sell it

Be readable

Text in the HTML, facts in structured data

Be answerable

First reply measured in minutes, at any hour

Be persistent

A second message to whoever went quiet

Be owned

Your accounts, your logins, your data

A business with fifty staff that fails the third line loses work to one with four staff that does not. Size does not protect you from any of these.

What does the running cost look like?

The part that scales with you is tool subscriptions, not fees. A system that reaches for a new product per workflow can cost more in subscriptions than in the work itself, which is why anything we design goes onto the accounts you already have, or is self-hosted, and anything unavoidable is billed at cost with the invoice attached.

For the market rate: UAE agencies quote AED 6,999 to 8,000 a month for the same three workflows, and Dubai automation firms AED 3,000 to 5,000 a month on top of AED 15,000 to 30,000 to build. Ours is quoted on enquiry, once we have seen how much arrives and where it arrives from. The pricing page sets out what each thing covers.

When is it too early to automate something?

When the work does not happen often enough to pay for watching it. A task that comes up twice a month and takes ten minutes is not worth a system that somebody has to keep alive through other people changing their APIs without warning.

We look at a month of the real thing first, and how often it happens is the number that decides. Sometimes the answer is that automating it is not worth the running cost, and it is better to hear that at the start than after it is built.

Questions people actually ask

Should I fix the website first or the follow-up first?

Whichever one is currently losing you work. If enquiries are arriving and going cold, fix the answering, because it is faster and cheaper and it pays immediately. If almost nothing arrives, no amount of answering speed helps and the visibility comes first.

Do we have to change the tools we already use?

Usually not. Most businesses are already paying for tools that could automate half of this and were never configured past their defaults. Often the work is wiring and configuration rather than anything new, and that is the cheaper outcome for everybody.

What happens when an integration breaks?

It will. Other people change APIs and expire tokens without telling anyone, and the failure is silent: the messages simply stop. Watching for it and fixing it inside a business day is what a monthly fee is for. An automation nobody is responsible for goes back to being done by hand within a year.

Can this be built without replacing our website?

Yes. The automation is built onto whatever the business already has, and a website is only added when there is nowhere for the enquiries to arrive through. See [what usually happens to enquiries](guides/enquiries-that-go-nowhere).