2026 · Estate access & security
QRCL
One visitor pass. An entire estate working behind it.
Visit live productAccess is a shared decision
I led QRCL’s product experience across 5 core applications, connecting residents, security teams and administrators. The project’s 2027 plan targets 200,000+ onboarded users and ₦20 million+ in projected income, supported by the product architecture, identity and design system I built.
Onboarding and income figures are project forecasts for 2027.
- 200,000+
- 2027 user onboarding target
- ₦20 million+
- 2027 projected income
- 5 core applications
- Resident, sub-resident, security, estate admin and super admin
Inside this case study
Follow the pass, not just the screens
Create access
A resident gives a visitor permission to enter.
Verify at the gate
Security checks whether that permission is valid now.
Keep the record
Administrators can follow the entry and exit trail.
A QR code was only the starting point
Estate access was coordinated through logbooks, messages and manual checks. Putting a QR code on a phone would only address one moment. The product needed to connect the person granting access, the guard making a decision and the administrator responsible for what happened afterward.
I led the experience across five core applications, defining how their responsibilities fit together before treating them as separate interfaces. The goal was a traceable access journey with a clear next action for each role.
The boundary between convenience and control
Residents need an easy way to invite someone. Security needs to know whether the invitation is valid at the point of entry. Administrators need an account of what occurred. I used those different responsibilities to shape permissions, information hierarchy and the connection between applications.
A shared system could provide familiar patterns across the estate while keeping each person’s available actions relevant to their role. Sub-residents also needed their own access within permissions set by the resident.
Designing for the moment a visitor is waiting
At the gate, an ambiguous result creates a practical problem: a guard still has to decide what to do. I designed distinct scan outcomes and an escalation path for invalid or flagged passes, making the result and next action part of the same experience.
Time-bound access also changes after a pass has been created. Expiry and revocation needed to make sense in the verification flow, while entry and exit events needed to feed the administrator’s audit trail. The task was to make that behaviour understandable under pressure.
One system across the estate
I built a component-based design system for the connected applications. Reusable forms, navigation and status patterns establish common behaviour, while role permissions determine which controls appear.
That distinction mattered: a resident creating a pass and a guard verifying it are participating in the same journey, but need different interfaces. I used shared foundations to connect the experiences without giving every application the same information density or actions.
Brand foundations with a practical purpose
I developed the resident QRCL and Security Scanner identities alongside the product. The orange-led palette, semantic colours and Outfit typography hierarchy carry the identity into mobile and desktop interfaces.
Brand and feedback have different jobs here. The identity makes the product recognisable; the hierarchy and semantic states help people read information and understand the result of an action. The colour and type boards below document those foundations.
I found a missing product inside the product
While defining the ecosystem, I identified a gap between residents and landlords. I independently scoped the resident–landlord sub-application and took it through design and implementation.
This extended my ownership beyond the original feature list. I also published functioning interface references to Vercel and worked with developers during API integration, using working behaviour to support the handoff.
The scale we are planning for
QRCL’s 2027 plan targets more than 200,000 onboarded users and more than ₦20 million in income. These are project forecasts guiding the next stage of the product.
My contribution is the connected experience and shared design foundation across the resident, security and administration applications. As onboarding progresses, the forecast can be assessed against actual adoption and income.
What I delivered, and what it proves
The work established the product architecture, connected journeys, brand identities and reusable design foundation across five core applications, alongside the resident–landlord extension. My contribution continued into implementation references and engineering collaboration.
The strongest evidence here is the breadth of ownership and the connected product decisions. The founder’s account at the end adds a collaborator’s perspective on working with me.
Where I took ownership
- Led design and owned the product experience across the resident, sub-resident, security, estate admin and super admin applications, defining how each role fits into the wider system.
- Defined the product structure, permissions and connected workflows, from creating a visitor pass to gate verification and the administrative audit trail.
- Built the shared design system and shaped the brand identities, giving each application a clear purpose while keeping the ecosystem consistent.
- Identified an unmet need between residents and landlords, independently scoped the missing product, and took it through design and implementation.
- Carried ownership into delivery, building working interface references and collaborating with developers during API integration to preserve the intended experience.