Technical services and maintenance · Dubai and the UAE

The job happens on someone else’s site. Your system should still know what happened.

A technical services company lives or dies on two things: getting the right technician to the right site, and being able to prove afterwards what was done. WEBZAZA builds the system that holds both, from the first call to the paid invoice.

Book an Operations Review → See Call to Cash

Quotations · LPO tracking · Dispatch · Site sign-off · AMC schedules · VAT invoicing

Today’s board

Tuesday · 9 jobs

2 unassigned

AC not cooling · Unit 1204

Marina Heights · HVAC · LPO-4471

On site

Rashid · arrived 09:41

Quarterly AMC visit · Tower B

Business Bay · Planned · Visit 3 of 4

Scheduled

Imran · 13:00

Water leak · Ground floor

Al Quoz · Plumbing · No LPO on file

Unassigned

Reported 08:20 · nobody allocated

An illustration of the view a coordinator works from. The point is the third card: the job you have not allocated is visible before the client rings to ask about it.

What goes wrong off-site

You cannot see the work, so you manage it by phoning people.

⊗ A client asks where the technician is and the answer requires two phone calls.
⊗ A technician reaches a site without the part, the permit or the unit number.
⊗ Proof of completion is a photograph in a group chat that nobody can retrieve later.
⊗ Work is done, then the LPO never appears and the invoice sits in dispute.
⊗ A contracted maintenance visit is missed and discovered at renewal.
⊗ Nobody can say which clients and which trades actually made money last month.

What changes

One thread per job, from the call to the payment.

✓ Job status answers the client’s question without interrupting the technician.
✓ Access details and history travel with the job before anyone leaves the yard.
✓ Completion evidence is attached to the job, timestamped and retrievable.
✓ The LPO reference follows the work all the way onto the invoice.
✓ Planned visits are scheduled and counted against what the contract owes.
✓ Margin by client, trade and contract is visible without a month-end reconstruction.

Call to cash

Eight handovers. Every one of them is where a job goes missing.

A job in this trade changes hands repeatedly — caller to coordinator, coordinator to surveyor, surveyor to estimator, estimator to client, client to dispatcher, dispatcher to technician, technician to accounts. Software earns its place by making each handover carry the information the next person needs.

The technical services job lifecycle from first call to paid invoice
Handover	Where it breaks	What the system holds
01 Call	The enquiry is taken on a phone and repeated to whoever schedules. Details thin out on the way.	Client, site, unit, trade and the reported fault are captured once, against a record that survives the call.
02 Survey	A technician visits to price the work, then the findings sit in his head until he is asked.	Site findings, photographs and measurements attach to the enquiry so the quotation is priced from evidence.
03 Quotation	A quote goes out and nobody knows whether it was read, chased or lost.	Sent, seen and outstanding quotations are a list somebody owns, not a memory.
04 LPO	Work starts on a verbal approval and the purchase order never arrives.	The LPO number attaches to the job and follows it to the invoice. Work without one can be flagged before it starts.
05 Dispatch	The nearest available technician is a guess made by whoever is loudest in the office.	Jobs are assigned against trade, area and what each technician is already committed to that day.
06 On site	The technician arrives without the part, the access permit or the unit number.	The job carries access details, previous visits and the materials expected before he leaves the yard.
07 Completion	Proof of work is a photo in a WhatsApp group nobody can find in three weeks.	Checklist, photographs, materials used and the client signature close the job where it happened.
08 Invoice	Invoicing waits for someone to reconstruct the month from job sheets and messages.	The invoice is raised from the completed job, carrying the LPO reference the client needs to match it.

What we build

Nine parts of a service operation. Start with the one that is bleeding.

Nobody in this trade has a quiet quarter to roll out a platform. We build the piece that is costing you most, get it genuinely used by the coordinators and the technicians, and only then add the next.

Enquiry and site survey capture

Calls, WhatsApp messages and website enquiries into one queue, with the site, unit and trade attached before anyone is dispatched to look at it.

Quotations that get followed up

Priced from survey findings, sent as a document the client can act on, and visible as a list of what is outstanding rather than a folder of PDFs.

LPO and approval tracking

The purchase order number attaches to the job and travels with it to the invoice, so accounts are not chasing a client who cannot match the two.

Dispatch and scheduling

Assignment by trade, area and existing commitments, so a same-day promise is made against a real day rather than an optimistic one.

Technician job view

On a phone, in a plant room: the job, the access details, the checklist, the photographs, the materials used and the signature. Nothing that does not help him finish.

Materials and van stock

What went onto the job and what came off the van, so consumables reach the invoice and the stores know what to replenish.

AMC contracts and planned visits

Contract value, sites covered, the visit schedule, visits used against visits owed, exclusions and the renewal date, all visible before renewal season.

Completion evidence and client reporting

Timestamped status changes and photographic proof against each job, in a form you can hand an FM client without rebuilding it by hand.

Owner dashboard

Jobs open, quotations outstanding, AMC visits due, invoices unpaid, and which trades and clients are actually contributing.

The contract side

Reactive work pays this month. Contracts pay next year.

An annual maintenance contract is the most valuable thing a technical services company owns and the easiest to quietly lose. Reactive call-outs are loud and urgent, so they win the schedule; planned visits are neither, so they slip. The client notices at renewal, when they count the visits they paid for against the visits they received.

What the contract covers

Sites, units, equipment and the exclusions that decide whether a call-out is chargeable or already paid for.

Visits owed against visits used

A running count that makes a shortfall visible in month four rather than month twelve.

Renewal in view

Contracts approaching their end date, with the service record you would want in the room for that conversation.

Chargeable extras

Work outside scope identified as it happens, quoted separately, rather than absorbed and forgotten.

Two kinds of work

A system that only understands call-outs will starve your contracts.

Reactive jobs arrive, get done and get invoiced. Contracted work has to be planned months ahead, scheduled around the reactive load, and evidenced at the end of the term. They are different shapes and a single job list treats them as the same thing.

If your planned visits are currently held in a spreadsheet that one person maintains, that is usually the first thing worth fixing.

Talk through your contract book →

Trade by trade

An AC contractor and a fit-out firm do not need the same screens.

One runs hundreds of short visits against contracts. The other runs a handful of long jobs billed in stages with variations along the way. The scheduling, the evidence and the invoicing all differ.

Tell us how yours runs →

HVAC and AC maintenance

Seasonal peaks and heavy AMC volume, where a missed planned visit is only discovered when the client counts them at renewal.

Plumbing and sanitary

Reactive call-outs where response time is the product and the client remembers how long they waited, not how well it was fixed.

Electrical contracting

Certification and completion evidence matter as much as the work, and both need to be retrievable long after the job closed.

Multi-trade and handyman services

One enquiry can need two trades on the same visit, so scheduling has to think in skills rather than in people.

Fit-out and civil works

Longer jobs billed in stages, where progress and variations need a trail the client agreed to at the time.

FM subcontractors

You are held to someone else’s response times and reporting format, so proof and timestamps are the deliverable alongside the work.

Where the next job comes from

Two different customers, found two completely different ways.

This trade sells into two markets at once, and most websites in it are built for neither. A resident with a leak searches on a phone and calls whoever looks credible and close. A facilities manager awarding a contract is not searching at all — they are checking whether you look like a company they can put in front of a building owner.

The urgent search

Someone with a problem right now

✓ Pages for the specific faults and areas you cover, not one page listing every service.
✓ A Google Business Profile that is accurate on hours, location and what you actually do.
✓ A phone number and WhatsApp reachable in one tap, above the fold.
✓ Reviews that keep arriving from completed jobs rather than only from complaints.

The contract decision

Someone deciding whether to trust you

✓ Evidence of capability: trades covered, team size, the kinds of buildings you work in.
✓ Credentials and approvals presented plainly, where a procurement team will look.
✓ A clear route to request a survey or a tender response, not just a contact form.
✓ Reporting you can show, because an FM client is buying your paperwork as much as your work.

We do not promise rankings, and any agency that does is guessing. What we can do is build a site that answers both of those visitors properly instead of splitting the difference and convincing neither.

How we deliver it

We follow a job to site before we design a screen.

Ride along

We sit with a coordinator for a morning and go out on a job, and note every time information is repeated, chased or written down twice.

Pick the bleeding step

We agree the one handover worth fixing first and what good looks like when it is working, rather than starting from a feature list.

Test it in a plant room

The technician screens are tried on site, on the phones your team carries, before the build is called finished.

Hand over properly

Training for coordinators and technicians separately, documentation, backups, secure access and a named route back to us.

Two things reliably surprise people. Existing contract and client data is rarely as tidy as remembered, and technicians adopt a new tool at very different speeds. We plan for both rather than discovering them at launch.

Questions service companies ask

Straight answers before you commit to anything.

What does job management software do for a technical services company?

It holds the thread from the first call to the paid invoice. The enquiry becomes a quotation, the approved quotation becomes a scheduled job with a technician and a time, the technician closes it on site with photos and a signature, and the invoice is raised from what was actually done. The value is not any single screen; it is that nobody has to reconstruct what happened on a site three weeks ago from a WhatsApp thread.

Can it handle annual maintenance contracts?

That is usually the reason to build one. An AMC needs the contract value, the sites and units covered, the visit schedule, how many visits have been used, what is excluded and when it is due for renewal. Without that in a system, planned visits get missed when reactive work is busy, and the miss is discovered at renewal when the client asks why they paid for twelve visits and received nine.

Can it track LPOs against jobs and invoices?

Yes, and for UAE B2B work it matters more than most features. The LPO number attaches to the job, follows it to completion, and appears on the invoice, so your accounts team is not chasing a client who cannot match your invoice to their purchase order. Work done without an LPO on file can be flagged before it becomes an argument at payment.

Our technicians work across several emirates. Does it work without signal?

Basements, plant rooms and lift shafts have no signal, so a technician app that assumes connectivity will fail exactly where the work happens. Offline capture with sync on reconnect is possible and we build it where the work genuinely needs it, but it is real engineering effort rather than a checkbox, so we scope it deliberately instead of promising it by default.

Will technicians actually use it?

Only if it is faster than what they do now. On site, in a hurry, often in heat, the app has to do a small number of things well: see the job and the access details, tick off a checklist, photograph the work, capture a signature, note materials used. If it asks for anything that does not help them finish and leave, they will stop using it and you will be back to phone calls.

How much does a system like this cost in Dubai?

It depends on what you bring into it. Quotations, scheduling and job completion is a much smaller build than one that also covers AMC schedules, van stock, offline capture, client portals and multi-emirate teams. We scope the first phase against the workflow costing you the most, price that clearly, and treat later phases as separate decisions.

How long does it take to build?

A first phase covering enquiries, quotations, scheduling and completion is usually a matter of weeks. AMC management, offline technician capture, client-facing portals and reporting add time, and the honest schedule depends on how quickly decisions and existing data come from your side. We agree stages and decision points before development starts.

We subcontract for facilities management companies. Does that change anything?

It changes what the system has to prove. An FM client will hold you to response times and will want completion evidence in their format, not yours. That pushes the design toward timestamped status changes, photographic proof against each job and reporting you can hand over without reformatting it by hand every month.

Start with one handover

Which step loses you the most jobs?

Quotations that go quiet, dispatch that runs on phone calls, completion evidence you cannot find, or contracts you are not sure you are delivering. Tell us where it hurts and we will tell you what is worth fixing first — including when the answer is that software is not your problem.

Book an Operations Review →

Keep exploring

Different trade, same broken handover.

Most of what makes a service operation work — one thread per job, evidence captured where the work happens, a status the client can see without phoning — turns up in every business that sends people out or takes work in.

Industry