EXECUTIVE CASE STUDY • EDITORIAL OPERATIONS • MEDIA & PUBLISHING, DUBAI
How a UAE travel publisher moved editorial, partner and advertising operations into one self-hosted CRM
Running a travel publication means coordinating editors, contributors, advertising partners and publication deadlines at the same time. When each of those lives in a different place, nobody can see the real state of the pipeline. Vox Media International moved the full operation of Dubai Trip Guide into a self-hosted CRM installed on its own server, under a one-time licence with no per-user cost.
- Editorial pipeline with owners and stages
- Team output visible without status meetings
- Partner and advertising records in one account view
The publisher’s challenge
Editorial work spread across messages, files and separate records
Editorial coordination ran on messages and files passed between editors. An article in progress, a commitment made to an advertising partner and a placement sold for the same period were recorded in different places, by different people. The owner could not see the state of the pipeline without asking for it.
The cost was not one dramatic failure but a constant tax on attention. A self-hosted CRM was chosen over a subscription platform for two reasons: the data had to stay on the company’s own server, and the team had to be able to grow without the licence pricing every new contributor.
Status by asking
Content, partner commitments and advertising placements lived in separate places, so the state of the publication had to be reconstructed in conversation.
Status by looking
One pipeline with an owner and a stage per item, partner and advertising records on the account they belong to, and roles deciding who sees what.
Client testimony
“Coordinating editorial teams used to be a challenge, but Zarina CRM simplified our entire workflow. I can monitor content pipelines, track team output, and keep our data secure without any stress.”
A self-hosted installation built around the editorial workflow
The installation runs on the company’s own server in Dubai, with the modules the operation actually needs rather than a full suite bought for the sake of completeness.
Editorial work enters as records with stages, owners and deadlines. Advertising and partner activity enters against the account it belongs to, so the person who agreed a package and the person who publishes it read the same record. Access is decided by role, which matters for a publication that works with external contributors.
Modules in use
- Editorial pipeline — articles and content projects as records with stages, an assigned editor and a deadline, monitored in one view.
- Team coordination — output per editor and per period, so workload and delivery are tracked without separate spreadsheets.
- Partner relations — partner and advertiser accounts with their contacts, history and commitments kept against the account.
- Advertising packages — packages recorded and followed per client, from agreement to placement.
The same modules are sold separately, so an installation carries only what it uses.
See the pricingWhat changed in daily operation
The publication’s state became a view rather than a question. Content moves through one pipeline, team output is tracked without asking, and commercial commitments sit on the account they belong to. The data stays on infrastructure the company controls, which for a UAE publisher is a compliance answer as much as a technical one.
One-time licence
The platform and the active modules are paid once, not every month, for as long as the company uses them.
Unlimited users
Editors and contributors are added without a per-seat cost, so the licence never decides the size of the team.
Own infrastructure
The installation and the database sit on the company’s server, so the data stays where the company put it.
Related case studies
Other companies running on Zarina CRM
Sixteen deployments across eleven industries, each with the company named and the workflow described, so you can find one close to your own.
STRATEGIC PARTNERSHIP • ENTERPRISE
Move your operation onto a platform you own
The editions, the modules and the one-time licence are the same ones used in this deployment. The installation sits on your server, the users are unlimited, and the licence is paid once.
- Installed on your own server
- Unlimited users
- One-time payment