PropTech
re:current is a full-stack property management platform for landlords, property managers, shortlet hosts, and realtors. It consolidates tenant onboarding, rent collection, invoicing, bookings, and identity verification into one dashboard. I built the frontend: the route group architecture, the booking calendar, PDF agreement and invoice generation, and the real-time dashboard layer.
Context
Landlords and property managers were running their operations across disconnected tools — separate invoicing software, manual KYC, paper tenancy agreements, and no unified view of bookings or payments. re:current consolidates the full property workflow into one platform, from tenant onboarding and verification to rent collection, short-let bookings, and digital agreements.
Constraints
Role & Team
Process
01
The platform serves two fundamentally different users — landlords managing their portfolio and guests booking short-lets. I separated these into distinct route groups: (landlord) for the authenticated operator dashboard and (public) for guest-facing property listings and booking pages. The split gave each surface its own layout, auth logic, and data loading strategy without the two leaking into each other.
02
Short-let and hotel bookings require per-unit availability tracking across multiple days, with OTA channel sync to prevent double-bookings. I built the calendar view on Schedule-X, wiring it to the booking state layer. Each day cell reflects which units are available, occupied, or pending — without the operator needing to cross-reference a separate list.
03
Tenancy agreements and invoices aren't just exports — they're legally binding documents tenants sign and landlords store for years. No single PDF library handled both structured agreement layout and invoice snapshot fidelity well, so I used react-pdf/renderer for agreements and jspdf + html2canvas for invoices. The output matches exactly what's on screen.
Outcome
Property businesses on the platform
Concurrent users online at peak (live)
Property modes: rentals, short-lets, sales
Lessons
Building re:current taught me that real operational workflows are rarely linear. Payments, agreements, bookings, and verification all interact in ways that create edge cases quickly. The challenge was not building the happy path but creating a system that stayed understandable when those exceptions appeared. It made me more intentional about designing for clarity, flexibility, and change.
