Back to selected work

Case study

RentHub is a trust-first rental marketplace designed to replace agent friction with verification, direct connection, and escrow-backed transactions.

The project is much more than a property listings site. The monorepo shows a multi-role rental platform built around search, property management, tours, messaging, reviews, verification, and transaction protection for both tenants and landlords.

Visit live project
Category: Rental trust platform

Project snapshot

2

primary app surfaces inside the monorepo: web experience and API

43

backend source files covering properties, tours, messaging, transactions, reviews, uploads, and verification

68

web source files across marketplace, dashboard, resources, onboarding, and payment flows

14

database models documented for users, properties, tours, transactions, reviews, favorites, and more

What NEXGEN built

A property marketplace shaped around trust infrastructure instead of middlemen.

Property marketplace with search, filtering, listing creation, featured properties, and landlord-managed inventory.

Trust layer built around physical property verification, ID and document upload flows, landlord credibility signals, and verified badges.

Direct communication system with property-linked conversations, inbox management, and dashboard messaging instead of agent-mediated contact.

Tour scheduling and rental transaction workflows that move from property discovery to inspection booking, payment, escrow, and release.

Tenant and landlord support surfaces including receipts, reviews, trust-and-safety resources, onboarding, and monetization tools.

Product framing

The strongest design decision is making trust visible at every stage of the rental journey.

RentHub’s differentiation is not just direct landlord access. It is the way the platform combines discovery, verification, communication, tours, and payments into one coherent flow.

Trust as product design

RentHub is framed around a real market failure in Nigerian rentals: fragmented discovery, weak accountability, and exploitative agent fees. The repo reflects that by treating verification, escrow, and reviews as core platform features rather than optional extras.

Landlord and tenant workflows both matter

The product is not just a browse-and-contact interface. There are landlord tools for listings, monetization, approvals, and property management alongside tenant flows for search, tours, payment, and protected communication.

Payments are operational, not decorative

Escrow status tracking, gateway handling, transaction history, receipts, and release logic make the marketplace feel much more serious than a listing site with a pay button attached at the end.

Education and safety are built into the platform

Resources for tenant rights, inspection checklists, scam awareness, verification, escrow, landlord legal templates, and photography guidance show a broader product strategy around trust and conversion.

Architecture

A modern marketplace stack with clear separation between customer experience and platform operations.

Turborepo monorepo with a Next.js web app, Express TypeScript API, and shared type-safe backend patterns
Prisma and PostgreSQL foundation for users, properties, tours, transactions, reviews, conversations, favorites, notifications, and verification-related entities
Clerk-based identity layer with onboarding, role-aware flows, protected dashboard sections, and verification-oriented profile tooling
Marketplace infrastructure connected to Cloudinary uploads, Mapbox map flows, SMS notifications, escrow-capable payment gateways, and Redis/BullMQ operational support

Technology stack

Next.js 16
React 19
Express 5
TypeScript
Prisma
PostgreSQL
Clerk
Tailwind CSS
Mapbox
Cloudinary
Paystack
Flutterwave
Termii
BullMQ
Redis

Why it stands out

RentHub stands out because it treats local rental friction as a systems problem. Listings, tours, verification, payments, resources, and reviews all work together to reduce the trust gap that normally pushes people back to informal agents.

System breakdown

The repo shows a marketplace built around real rental workflows, not just posting inventory.

Property and search layer

The marketplace supports listing creation, rich property metadata, image handling, search filters, favorites, featured listings, and route-level pages for browsing, property detail, and rental initiation.

Messaging and tour coordination

The backend includes conversation and messaging services tied to properties, while the frontend includes inbox management and tour-request pages. That creates a stronger bridge from discovery to real-world inspection.

Escrow and transaction flow

Transaction services calculate fees, track gateway references, move payments into escrow states, and support release to landlords. The dashboard UI also includes escrow status and transaction history views.

Verification and review systems

Document upload, verification controllers, verified reviewer support, multi-dimensional ratings, and trust score UI components show a serious attempt to model rental reputation rather than relying on bare listings.

Repo evidence

The implementation backs up the trust-first positioning.

The root README explicitly positions RentHub as a platform built to remove the 'agent tax' through verified listings, escrow protection, and direct landlord-to-tenant connection.
The progress tracker shows core phase completion across messaging, tours, escrow payments, reviews, verification workflows, and monetization features.
The web app includes dedicated routes for search, onboarding, support, community, resources, landlord guides, trust-and-safety education, property creation, tours, rent flow, payment verification, and dashboard messaging.
The API is separated into controllers and services for properties, users, tours, favorites, payments, transactions, reviews, messages, uploads, service transactions, and verification.