Feature lists do not separate vendors. Nine criteria that do — product ownership, data location, integration delivery, and what happens when something breaks.
Every vendor shortlist starts the same way: a feature comparison spreadsheet. And every such spreadsheet ends the same way — with ticks in almost every box for almost every vendor, and no clearer decision than before.
Feature lists do not separate vendors because mature products converge on features. What separates them is who controls the product roadmap, where the data physically sits, who delivers the integration, and what happens the first time something breaks at 8am. This guide gives you nine criteria that surface those differences.
| Vendor type | Product origin | Strength | Risk |
|---|---|---|---|
| Local developer | Builds the product in-Kingdom | Fast customisation, regulatory fluency | Maturity varies — verify it |
| Reseller of a global product | Sells a foreign product, localised UI | Mature product, broad roadmap | No control over development timing |
| Security systems integrator | Visitor module within a wider offering | Ready integration with cameras and gates | Visitors are not the core product |
None is inherently superior. If your project is fundamentally gates and cameras with a light visitor layer, the integrator makes sense. If visitor and contractor management is the core need, a specialist product serves you better than an add-on.
| Criterion | Suggested weight | What you are measuring |
|---|---|---|
| Functional fit to your case | 25 | Your scenario demonstrated live, not a feature list |
| Hosting and compliance | 15 | Data location, audit trail, PDPL alignment |
| Delivery and integration capability | 15 | Who delivers, with what precedents |
| Support and service level | 15 | Contracted response times, not verbal promises |
| Three-year total cost | 15 | Including expansion and hardware |
| Vendor stability and references | 10 | Comparable customers and operating history |
| Exit flexibility | 5 | Data ownership and export format |
Cost carries 15 points — not because budget is unimportant, but because a price gap rarely compensates for a functional failure discovered after go-live.
The familiar local-versus-global debate obscures the sharper question: does the vendor own the product? A local developer who owns the code can add a field in two weeks; a reseller may need months, or may simply be unable to. Equally, a local developer with a very small team carries real continuity risk.
The practical test: request a small modification during evaluation and watch the response. Anyone who says "we will raise it with the manufacturer" has told you their position in the chain without meaning to.
Haseen is a Saudi-built system rather than a translated product, which means customisation decisions sit internally and do not route through a foreign manufacturer. Data is hosted inside the Kingdom, the interface is Arabic-native rather than localised afterwards, and contractor management is a core module — company files with contracts and authorised zones, individual records with per-document expiry, and work permits that lapse automatically.
Demos run on your scenario rather than a generic script. See the Haseen visitor management system, contractor management, and the cost guide.
It depends on your deciding criterion. Government entities prioritise sovereign hosting and tender eligibility; industrial facilities prioritise contractor management and permits; multi-branch organisations prioritise central governance. Identify your deciding criterion first, then score vendors against it with a weighted matrix.
The decisive factor is not nationality but product ownership. A vendor who owns the code can customise; a reseller cannot, however strong the product. Test it during evaluation by requesting a small modification and observing the response.
Three steps: speak to a current customer of similar size and sector, request a pilot on one gate with pre-agreed success criteria, and ask for a small modification during evaluation to measure actual responsiveness rather than promised responsiveness.
To varying degrees. Test rather than accept: register a compound Arabic name, print the badge, then export a report and open it. Failures cluster in exported reports, printed badges and Hijri date handling rather than the main interface.
Ask specifically whether support comes from the reseller or the manufacturer, and which tier each handles. In a reseller model the local partner typically handles first-line only and escalates the rest — which is where waiting time actually begins.
Consolidation reduces failure points and contract count, and is preferable when one vendor covers all three well. But do not consolidate at the cost of a clear weakness in any component — particularly contractor management, which is most often offered as a thin add-on.
Identify your deciding criterion, then evaluate at most three vendors against the matrix. More than three lengthens the decision without improving it.
A written proposal and a demo built on your own scenario — then place it beside any other vendor.