Saudi Arabia · Convergent Technology
Five Business Units, each deep enough to be contracted on its own — and one Group that coordinates the points where their scopes meet.
DESIGN-PROOF MEDIA — FINAL MEDIA REQUIRED. Controlled preview assets from the CT design pack. Not photographs of a Convergent premises or project.
The premise
Technical work on a building is bought discipline by discipline: a facilities contractor, a network contractor, an audiovisual contractor, a landscape contractor, a production supplier. Each is competent in its own field. Each prices a defined scope. Each scope stops at its own boundary.
What no one prices is the boundary itself — the point where one discipline hands something to another and both sides reasonably assume the other is carrying it. Those points are where programmes slip and where the discussion starts after handover, and they are almost never a line item in anybody's bill of quantities.
Our Business Units
What changes
These are not services, and they are not extras. They are the decisions that sit between services — the ones a client usually ends up making alone, late, and without the information to make them well.
Every contract states what it includes. Far fewer state what happens at the edge of it, so two competent scopes can both stop short of the same joint without either being in breach.
Where a requirement spans more than one Convergent Business Unit, the interface can be coordinated within one Group rather than left between separate suppliers.
Systems are commissioned individually and accepted individually. The first time two of them are exercised together is often the first time somebody actually needs them to work together.
Where two Convergent scopes meet, testing and commissioning can be coordinated across the interface through one Group.
A programme is assembled from each contractor's own durations. The dependencies between them are inferred rather than agreed, so one late predecessor quietly becomes somebody else's delay.
Dependencies between Convergent scopes can be identified and coordinated within one Group instead of being negotiated across separate suppliers.
Each package hands over its own documentation in its own format. What is missing is the set that describes how the packages relate — which is the set an operator reaches for first.
Where two Convergent scopes meet, the handover can be coordinated through one Group rather than split between separate suppliers.
Support is bought per system. When a fault sits between two systems, the client becomes the integrator — usually while the fault is still live.
Where the work crosses our own disciplines, the enquiry has one route in. Which unit resolves it is our problem to work out, not the caller's.
One Group
When a requirement genuinely crosses disciplines, the Group coordinates the points where those specialist scopes meet — giving clients clearer visibility between technical requirements, delivery activities and operational outcomes, without diluting the expertise behind each solution.
Start with the requirement
Tell us what you are planning, where the scope sits and the outcome that matters. We will direct your enquiry to the right Convergent Business Unit.
