Aadhib

Visitor Management · SaaS · Active

Aahlan

A B2B visitor-management and identity platform — reception, security, hosts and guards working from one record of who is on site.

Role
Founder · Product · Engineering
Category
Visitor Management · SaaS
Status
Active
01

The problem

Reception desks run on paper books, spreadsheets and a guard's memory. That works until somebody asks who was on site last Tuesday, or until a visitor arrives for a host nobody can find, or until fifty people turn up at once for the same meeting.

02

Approach

Build one record of presence that every role reads differently. A receptionist needs speed at the desk. A guard needs certainty at the gate. A host needs to know their visitor arrived. A supervisor needs the trail afterwards. The same visit, four jobs — so the data model is shared and the interfaces are not.

03

What it does

01
Registration for how people actually arrive
Individual visitors, group visitors and vehicles are separate flows, because a coach of forty and one contractor with a van are not the same problem at a desk.
02
Roles as first-class design
Guards, receptionists, hosts, supervisors and admins each get an interface shaped around their task rather than one screen with permissions bolted on.
03
Visitor categories that reflect reality
VIP and client visits carry different handling to a standard visit — the software recognises the distinction rather than forcing everyone through one path.
04
Passes and scan indicators
Visitor passes with scan feedback clear enough to be read at a gate in daylight, by someone not looking at the screen for long.
05
Blacklist workflows
A controlled process for barring entry, with the record of who set it and why, rather than a name remembered by whoever is on shift.
06
Arabic and English throughout
Full RTL support, with Arabic treated as a first-class interface language rather than a translation layer over an English product.
04

The hard parts

01
Five roles, one visit
The hardest part is not any single screen. It is keeping one shared model of a visit coherent while five roles read and write it for different reasons at different moments.
02
The desk is a real-time system
Anything that adds seconds at reception gets abandoned. The interface has to be faster than the paper book it replaces, on the worst morning of the month.
03
Arabic is not a translation pass
Direction, terminology, field order and layout all change. Doing it properly means designing bilingually from the start, not retrofitting a language toggle.

Detail

Where it came from

I started Aahlan under the name Nexora and grew it into a visitor-management and identity platform aimed at organisations where the front desk is a security function rather than a courtesy.

What it covers

I built the platform to span the whole visit rather than the moment of arrival: registration at reception, host notification, the pass a visitor carries, the scan at the gate, and the reporting that makes the whole thing auditable afterwards. A security portal gives the people responsible for the site a view that a receptionist does not need, and mobile components put parts of the flow where the work actually happens.

Status

Active and in continued development. I deliberately don't publish adoption figures here — the same rule I hold everywhere on this site: if I cannot verify a number, it does not appear.

Stack

Product
Reception workflowsSecurity portalMobile components
Access model
Role-based accessBlacklist workflows
Localisation
EnglishArabicRTL

Case studies

The decisions behind the build

CS-01Building an enterprise visitor management system for Saudi operationsCS-02Designing an Arabic-first visitor management experience
ARTICLEWhy Arabic-first software is more than translating an English UISYSTEM NOTEBuilding software for receptionists, guards, hosts and admins at the same timeFOUNDER NOTEWhat building visitor management software taught me about physical operations
All work