Designing the trust layer for modern real estate.
Design delivered · Client owns the build
- Role
- Sole product designer
- Timeline
- 8 weeks
- Team
- 2 Developers1 Designer (Me)
- Skills
- Trust & Verification UXDesign Systems
Overview
How do you make trust visible before a buyer ever picks up the phone?
Sole product designer on a 3-person team, 8 weeks, mid-build engagement.
Impact
8
weeks, solo designer, from vague brief to full flow
5
steps that make verification visible
3
regulatory credentials checked (license type, LASRERA permit, ESVARBON registration)
Problem
Unverified agents make every listing a gamble. Buyers hesitate, deals slow, and the marketplace loses its one real advantage: confidence. Verification had to sit underneath every other feature: search, listings, agent profiles, so buyers could trust the platform before they trusted any individual agent.
Zenvyra’s entire value proposition rests on verification. Without it, listings compete on price. With it, they compete on trust.
Constraints
Time: school and classes took most of my week.
No budget.
No user access, so research was a quick survey, not interviews.
The client's brief was vague, so I had to define the problem myself.
Research
Eight answers, enough to point the design at trust
With no user access and no budget, I ran a short survey in early June 2026. Eight people answered, across Lagos, Abuja, Kaduna and Port Harcourt. It is directional, not proof, but the pattern was clear.
4 of 8
had lost money to a real estate scam, or knew someone close who had
6 of 8
named hidden fees as a top frustration with listings
5 of 8
ranked verified agents or pre-verified documents as the most important feature
That pointed me toward verification as the foundation under every other feature.
Final screens
Verification built on real regulatory credentials.
Designed for Lagos, where agents are licensed and regulated: license type, LASRERA permit, and ESVARBON registration separate a real agent from a listing name. The same flow adapts to any market that licenses its agents.
Document upload, one step at a time
The verified badge on the live profile
Verification starts before you click a single listing.
Most platforms verify agents after a buyer has already fallen for a listing, when trust is no longer optional but urgent. Zenvyra moves it earlier.
The Verified Only toggle sits inside the primary search bar itself, next to the price, beds and type filters, so a buyer can filter out unverified listings before they see a single photo. Trust becomes something buyers can act on at the very start of their search.
The badge means nothing if you can’t find the agents who earned it.
A verification badge on one profile is a promise. A directory of verified agents, searchable by location, specialty, and rating, is proof the promise holds at scale. Each card shows active listings and a verified rating up front, so a buyer can judge an agent’s track record before ever opening a conversation.
Listing a property should feel as considered as browsing one.
A marketplace only works if both sides trust it. The agent-facing listing flow walks through media, property details, and location in the same clear, unhurried steps as the buyer experience, with a live preview panel so agents see exactly what a buyer will see before they publish. Nothing goes live without the agent knowing what it looks like first.
- Step 1: Create a listing
- Step 2: Submit for verification
- Step 3: Get approved
- Step 4: Reach buyers & renters
- Step 5: Manage and update
Five steps, so “verified” stops being a buzzword
A badge earns trust only if people understand what it took to get there. The How Listing Works page breaks the verification process into five visible steps, from submission, with a target of approval within 24 hours, and a short FAQ underneath for the questions that come right after: how long does this take, is it free, can I edit a listing later. The process becomes the proof.
Outcome and status
Fully designed and delivered
- Complete verification flow
- Status states and review hierarchy
- Verified profile pattern
- Reusable trust components
Not part of my scope
- Development handoff and production validation
- The client did not request a handoff after delivery.
What I would do differently
I would follow the survey with a handful of interviews, since eight answers showed what worried people but not why. I would also draw a user flow before any screens, to avoid the confusion the client's vague brief caused me.
