Real estate marketing + CMS (GT Estates)
Real Estate Management System
GT Estates—Next.js marketing site with GSAP/Lenis, staff CMS dashboard, and Express/MongoDB API for properties, gallery, inquiries, and careers.
Background & Context
real-estate is the GT Estates (gtestates.com.pk) three-package presence—not NestJS/PostgreSQL as older case-study metadata implied. Packages: Next.js ^16 marketing website/ (GSAP + Lenis desktop hero, Framer Motion, Swiper), Next.js 14 dashboard/ on port 3001, and Express gt-estate-api on MongoDB. There is no booking, payments, MLS, AI matching, VR tours, smart-home, or blockchain layer—despite older README marketing claims that docs explicitly reject.
Staff manage properties and gallery; visitors browse projects/gallery and submit inquiries or career applications with CV upload. JWT gates dashboard routes without fine-grained role ACL. News UI stubs call /news with no backend model. Careers API exists; dashboard careers UI does not.
The Challenge
A Pakistani real estate brand needed a premium public presence and staff tools for catalog, gallery, and lead triage—without a transactional marketplace. Without a coherent real estate marketing + cms (gt estates) foundation, Real Estate Management System stakeholders faced fragmented tools, slow handoffs, and limited visibility—classic failure modes Tekvers designs against.
The Solution
Real Estate Management System: GT Estates—Next.js marketing site with GSAP/Lenis, staff CMS dashboard, and Express/MongoDB API for properties, gallery, inquiries, and careers. Cinematic brand site with staff-owned property/gallery inventory. Tekvers delivered a maintainable real estate marketing + cms (gt estates) system for Real Estate Management System using Next.js, Express, MongoDB, Mongoose, with phased rollout, operator workflows, and documentation suited to long-term ownership.
Our Approach
Marketing motion + catalog reads
Desktop (≥1024px) `HeroLenisGsap`; pages for about, projects, gallery, team, what-we-do, contact, careers; public property/gallery reads from API.
Lead and careers intake
Public inquiry create + optional SMTP; career applications with multipart `cv`; dashboard inquiries UI exists but is not sidebar-linked.
Reject false claims
Portfolio docs forbid AI/VR/IoT/blockchain/booking claims; stack corrected to Express/MongoDB.
What We Delivered
- Next.js marketing site with GSAP/Lenis/Framer Motion
- Next.js admin: login/register, properties CRUD, gallery CRUD, overview charts
- Express API: auth, properties, gallery, inquiries, careers applications
- MongoDB models: User, Property, GalleryItem, Inquiry, CareerApplication
- Static `/uploads/{properties,gallery,careers}`; remote upload helper URL config
- Explicit non-features: payments, MLS, news backend, role-based ACL, dashboard careers UI
Outcomes & Impact
- Cinematic brand site with staff-owned property/gallery inventory
- Lead and career pipelines into MongoDB
- Defensible portfolio story that rejects inflated README claims
GT Estates presents developments with motion-led marketing while staff maintain inventory and triage inquiries—positioned as catalog + CMS, not a property marketplace.
Technology Stack
Services Delivered
Related Case Studies
Guides & articles from this niche
Planning a similar platform? Share your scope and we will map architecture, delivery phases, and a realistic timeline.