A Dubai service business needs six pipeline stages: New enquiry, Qualified, Quoted, Agreed, Paid and Delivered, plus a Lost bucket that demands a reason. The split that matters most is between Agreed and Paid. Most CRM templates stop at Closed Won, and in a WhatsApp-first market a yes in the chat and money in the account are often several days apart. Sometimes they never meet.
Every stage below has a binary entry rule, a binary exit rule and a time limit. If you cannot name the event that moves a deal out of a stage, that stage is a parking lot.
Why the standard sales pipeline template breaks for service businesses
The templates that rank for this search come from B2B software: Prospecting, Qualification, Discovery, Proposal, Negotiation, Closed Won. They assume a sales cycle of weeks or months, a demo, a procurement step and a signed contract.
A clinic in Jumeirah or a photo studio in Al Quoz sells differently. The enquiry arrives on WhatsApp from an Instagram or Google ad, the whole conversation happens in one thread, and the decision takes anywhere from twenty minutes to two weeks. Nobody negotiates in a separate stage, and nobody signs a contract for a 90-minute appointment. What people actually do is say yes and then go quiet before paying the deposit.
Copying the software template into that business causes two problems. Discovery and Negotiation sit empty or turn into dumping grounds, because the real work happens in a single chat. Worse, Closed Won gets read as revenue, so the board looks healthy on the same day the bank account says otherwise.
The six-stage template
1. New enquiry
A deal enters New enquiry the moment a message, form or missed call arrives from a number with no open deal. It creates itself; nobody types it in. The source tag (which ad, which page, which channel) is attached at creation, because after the first reply nobody remembers where the lead came from.
It leaves when the contact answers the qualification questions, or when it goes to Lost. Time limit: 72 hours, with one nudge at 24 hours, then Lost with the reason No response.
The automation that matters here is the first reply. An agent that answers inside a minute at 2am on a Saturday gives every lead the same start as a lead that arrives on Monday morning, and it asks the questions a tired coordinator skips.
2. Qualified
Enters when you know what the client wants, roughly when, and that the ticket size fits. For a studio that means shoot type, date and hours. For a clinic it is the treatment and a preferred day.
Leaves when a price has been sent. Time limit: 48 hours. A qualified lead that has gone two days without a price is a lead someone on your team decided was weak, and that decision is almost never written down.
One rule we learned on our own bot: a returning contact whose last conversation is more than 48 hours old goes back through qualification. Old answers about dates and group size turn out wrong more often than right.
3. Quoted
Enters when the price is in the chat, in writing, with what it includes. A price mentioned on a call does not count.
Leaves on one of two events: the client agrees, or the quote expires. For small tickets we set expiry at 7 days. Follow-ups go out on day 1 and day 3, and each one answers a likely question (availability, what to bring, parking) instead of a just checking in. On day 8 the deal moves to Lost with a reason from a short list: price, timing, chose someone else, no response.
Large tickets are the exception. A fit-out or a six-month retainer can carry a Discovery stage between Qualified and Quoted, with a site visit or a call as its exit event, and a 14-day quote window.
4. Agreed (what most CRMs call Won)
Enters when the client says yes to a specific price and a specific date or scope. A thumbs-up on the quote counts. Let me think does not.
Leaves when money arrives, and Lost is the only other exit. The payment link goes out in the same thread within a minute of the yes, generated for this deal and this amount, so the client never has to ask how to pay. A reminder follows at 24 hours. At 72 hours a person calls, because by then the blocker is usually something automation cannot see: a card that failed, a partner who has not approved, a date that clashed. At 7 days the deal goes to Lost with the reason Agreed, did not pay.
That Lost reason is the most useful number in the pipeline. It measures the gap between yes and money, which we break down in the lead-to-payment gap in Dubai.
5. Paid
Enters only on proof: a confirmation from the payment gateway, or a bank transfer matched to the deal by a person who checked the account. A screenshot from the client moves nothing. Our own agent is not allowed to mark a deal paid from a chat message, because a screenshot of a pending transfer looks exactly like a completed one.
The amount field holds what actually arrived, not what was quoted. If the client paid a deposit, Paid records the deposit, and the balance sits in its own field until it lands.
Leaves when the service has been delivered.
6. Delivered
Enters when the appointment, shoot or job is done. This is the stage that fires the handoff work: the review request (ours goes out the morning after a shoot), the balance invoice if one is open, and a rebooking prompt timed to how often the service repeats. A salon client might get that prompt at four weeks. A one-off event client may never need one.
Lost, with a reason
Lost sits outside the flow, since a deal can fall into it from any stage. Without a mandatory reason field it tells you nothing. Keep the list to five or six options, because a free-text reason field fills up with not interested inside a month.
The template deliberately has no On hold, Stalled or Follow up later stage. Deals rot there, since the stage has no exit event and nobody owns the clock. If a deal is genuinely paused, give it a date and leave it in its real stage.
Why Won and Paid must be separate stages
Won is a promise. Paid is money on the account. In a business that takes deposits, the two can land in different weeks, and some Won deals never reach Paid at all.
We run this pipeline on our own photo studio, and the split is now the rule for every business in our group: revenue counts only from deals that reached Paid, dated by the day the money arrived. We got there after the CRM kept telling a better story than the bank. Deals marked Won included prepayments for shoots weeks away, and one daily report booked a full shoot price where the client had only paid half as a deposit. The cause was structural. The pipeline had no stage that meant money, so people used the closest one.
The same numbers taught us two more things. The payment gateway does not see all the money, because part of it arrives by bank transfer and some in cash, so Paid needs a second entry path confirmed by a person or your revenue view undercounts. And revenue needs a companion figure for work actually delivered, so that a month heavy with prepayments does not pass for a month heavy with work.
What to measure at each stage
Three numbers per stage are enough:
- Conversion to the next stage over a rolling 60 to 90 days. A single week in a small business swings too hard to act on.
- Median time in stage. A creeping number in Quoted usually means follow-ups stopped. In Agreed it usually means the payment link is not going out on the yes.
- Lost reasons by stage, as a share of all Lost deals.
We do not publish benchmark conversion rates for these stages, and I would treat the ones you find with care. The widely quoted figures come from B2B software funnels with different stage definitions, so a Proposal-to-Won rate from a software vendor tells you nothing about a salon in JLT. Take four to eight weeks of your own data as the baseline, then flag any stage whose conversion drops by more than a quarter against it.
Time in stage is also where staff quality shows up. Once every deal has an owner, the CRM shows which coordinator lets quotes sit for four days and which one sends the payment link in the same minute. You see the difference within weeks, without listening to a single call.
The automations that hold the stages in place
A pipeline with good definitions and no automation decays within a month, because every rule depends on someone remembering it at 11pm. This is the minimum set we wire in:
- Deal created with a source tag on the first message (New enquiry).
- First reply and qualification questions inside a minute (New enquiry to Qualified).
- Follow-ups on day 1 and day 3, then automatic Lost after day 7 (Quoted).
- Payment link on the yes, reminder at 24 hours, alert to a person at 72 hours (Agreed).
- Stage move on gateway confirmation, plus a manual confirm button for transfers (Paid).
- Review request and balance invoice on completion (Delivered).
The first two are the job of a WhatsApp AI sales agent working inside the thread. The rest is connection work between your CRM, WhatsApp and the gateway you already use, which is what our single-process automation setup covers: from AED 6,000 to build and from AED 1,200 a month to run and monitor. If the stages already exist but the records inside them are duplicated or untagged, fix that first, in the order laid out in our CRM data hygiene guide.
If you want your current sales pipeline stages mapped against this template, with an AED figure on each leak before anything gets built, that is the growth audit, from AED 3,000.
Artur Gall, founder of slgo.ai. I run these pipeline stages on our own studio bookings before recommending them to anyone.
