A UAE-based group operating across corporate services, business centres and mobility had expanded into the Philippines and Turkey. The technology supporting that growth had been assembled piece by piece.
The day-to-day file environment was built around a Synology NAS accessed mainly through its web portal. With more than forty people depending on shared data, that had become a serious operational constraint.
Employees spent unnecessary time navigating folders and hunting for documents. Search was limited. Permissions were difficult to manage at scale, and assigning someone to a folder often meant exposing everything inside it. Performance degraded as concurrent use increased.
There was no single source of truth
Some files were stored against customers and records inside Zoho CRM. Another copy sat on the NAS. Sometimes one was updated and the other was not. Sometimes people knew a document existed but could not tell which location held the current version.
What initially looked like a storage problem was in fact a much larger issue spanning identity, access, performance, remote working, information governance and business applications.
Rebuilding the foundation
The infrastructure was redesigned around two physical servers running Proxmox virtualisation, with dedicated virtual machines for the organisation’s core services.
- Active Directory
- Central file server
- Terminal server and remote desktop
- Supporting application and backup workloads
The wider environment was rebuilt around a FortiGate 101F firewall, three managed switches and managed wireless, with central user and device administration, Active Directory policies, controlled folder permissions, restricted user environments, VPN-based remote connectivity and central backup processes. The Synology NAS was retained inside the wider storage and backup architecture.
Operational data was then migrated from the NAS into the new central file-server structure. That was not simply copying files. The migration had to preserve business continuity while restructuring how people reached shared information and how permissions were controlled.
Then the business layer
With the foundation in place, the same philosophy was applied to the applications. A broad Zoho One ecosystem was implemented across CRM, Books, Projects, SalesIQ, Social, FSM, Forms, Sign and Contracts.
That involved far more than standard module configuration: custom workflows, CRM pipelines, blueprints, approval logic, custom modules and fields, Deluge functions, application-to-application integration, CRM and Books synchronisation, form and document workflows, and operational automation.
Rather than asking employees to move information between applications, processes were redesigned so the systems could exchange it themselves.
Then a layer nobody asked for by name
One recurring task sat outside any standard module: building client proposals. It was manual, inconsistent between staff, and slow to turn around. Rather than force it into a generic template, a custom employee portal was built for creating proposals, connected directly to CRM, so a proposal drew on live record data instead of being assembled from scratch each time.
It is a small detail with a larger point. The infrastructure work and the business-systems work were never separate projects handed to separate vendors. The same relationship that rebuilt the servers also built the software layer sitting on top of them: one partner, accountable for the parts and the joins between them, including the parts nobody had put in a scope document.
What changed
Users gained faster, more structured access to business files. Management gained control over who could reach what. Remote employees worked through a controlled server environment. IT gained central visibility over identities, policies, devices and access. And the applications began operating as one ecosystem rather than a set of separate subscriptions.
The strongest outcome was not a new server or a new CRM. It was a technology foundation capable of carrying the group as it kept growing.