<style> .reveal { opacity: 1 !important; transform: none !important; } </style>
All work
2025 — 2026Proptech

Maydon Rent

A rental platform inside Maydon Group’s proptech ecosystem. I led a team of three and built four services from zero: identity, real-estate management, the listing marketplace, and notifications.

Applications board, with the conversion funnel from new enquiry through to signing

Applications board, with the conversion funnel from new enquiry through to signing

1 of 5

The problem

A rental product needs the lease, the documents, the money and the people to agree with each other at all times. Splitting that across services early buys distribution problems before there is any distribution to justify them — but leaving it as one undifferentiated application makes every later change risky.

What I built

A modular monolith with clear boundaries, and four services written from scratch.

  • Identity service: role-based access control, thin JWTs, Redis-backed sessions and multi-account access.
  • Real-estate management service.
  • Listing marketplace.
  • Notification service.
  • Lease and contract workflows: digital signing, PDF generation, idempotent invoicing and resilient webhooks.
  • Asynchronous workflows on MediatR pipelines with a transactional outbox, so nothing publishes unless the transaction commits.
On AI-assisted delivery

This is the codebase where I worked out how to use AI properly. Claude Code drafted, I owned the architecture, the security model and the review. Every suggestion went through the same tests and pipeline as anything hand-written — the failure mode is not bad code, it is plausible code nobody thought about carefully.

OutcomeFour services delivered from zero in a three-engineer team, with lease and payment state that recovers on its own rather than needing manual repair.