PropTech · Marketplace · Research
Gidaly
A listing became a record, not a post.
- Role
- UI/UX Designer, solo
- For
- Gidaly, a client, 2025
- Designed for
- Renters, agents, admins; web and mobile
- Status
- Live at gidaly.net

- 6
- Interviews before design: 2 agents and 4 renters
- 3
- Sides, one designer: the public site, the agent dashboard and the admin console
- Live
- Launched at gidaly.netShipped
The problem
A listing was a post. Everything else was a WhatsApp chat.
In six interviews, two agents and four renters, people found property on Jiji or PropertyPro and talked to owners on WhatsApp. A listing on those sites is a post: a photo, a price and a number to call. Whatever the post left out had to be asked for, one message at a time.
The four renters shaped the property page. The two agents shaped the tools around it: saving, shortlisting and sharing.
Post or record
Five questions. One chat, or one page.
Send a question to the owner and it waits for a reply. The Gidaly record already has the answer, and shows you where.
Hello, it's available. Call or WhatsApp for details.

Ask a question in the chat.
The record shows where it already answers it.
Where a record comes from
Nine steps, so no listing arrives as a post.
Every property comes in through one form. Agents can list too, and each listing is verified before it goes live. Each step fills a part of the page renters and agents read: pick one to see where it lands.

Three sides
One record, three ways in.
No account needed to search. The property page answers what a renter would otherwise ask the owner.
Save and shortlist, send properties to leads and move them through a pipeline, list properties, and choose a plan. On desktop and phone.
Gidaly's team adds and verifies properties, adds agents after a BVN or NIN check, and reads the numbers.
The object map
Fifteen objects, with the property at the centre.
I mapped Gidaly's objects before designing any screen: what each holds, its states, how they connect and what renters, agents and admins can do with them. The board is redrawn from the final designs, and marks the few things the site promises that no screen covers yet.
- Property
- Developer
- Location
- Feature
- Property plan
- Details pack
- Due diligence request
- Agent
- Saved list
- Lead
- Alert
- Plan
- Invoice
- Payment method
- Report
Decisions
Four choices that made it a record.
A property is a record, not a post
- Chose
- A structured record: price, units available, size, year built, floor plans, location, the developer, and the documents behind it.
- Instead of
- The classifieds model: a photo, a price and a phone number.
- Why
- Every question an agent sent on WhatsApp was a field the post didn't have.
Exact prices, never rounded

- Chose
- The full figure, ₦590,989,000.00, next to the type, status, year and size.
- Why
- A rounded price is one more thing to confirm before a client hears it.
A table that stays filtered

- Chose
- City, property type, status and cost filters fixed above the table, with Available and Sold tags on every row.
- Why
- An agent works the same list all day. Status should read without opening a row.
Sign-up shows its rules

- Chose
- Password strength as you type, the rules listed under the field, and the phone number starting at +234.
- Why
- The rules show before an error does, and the country code is already Nigeria's.
What happened
Launched at gidaly.net.
My contract covered research and design, so I wasn't part of the launch or what came after. There are no numbers from the live product.
Visit gidaly.net







