Skip to content
Platform

Case study · Property management

Rental Management SaaS

Property operations, rent and tenants in one platform.

Category
SaaS platform
Industry
Property management
Platforms
Web platform
Technology
Laravel · Vue · M-Pesa · MySQL

01 · Project overview

What was built, and for whom.

A rental management platform designed to simplify property operations, tenant management, payments and day-to-day property administration. It is offered as a subscription, with each landlord or agency managing its own portfolio of properties and units.

Built for
Landlords, property managers and agencies
Type
Platform
Platforms
Web platform
Focus
property saas payments web

02 · Business challenge

The problem, as the business experienced it.

Landlords and agents managed units, tenants, rent, utilities and maintenance across ledgers, M-Pesa messages and phone calls — with no clear picture of who had paid and what was outstanding.

Rent is simple until you have thirty units, three caretakers and a hundred M-Pesa messages a month. The work was not hard — it was scattered, repetitive and easy to get wrong.

  • Rent tracked in ledgers and M-Pesa message threads
  • Invoices and receipts written by hand
  • Utilities and maintenance handled by phone with no record
  • Owners unable to see property performance without asking

03 · Our approach

How we got from the problem to the system.

A subscription platform covering properties, units, tenants, rent invoicing with M-Pesa payments, utilities, maintenance requests, payroll and role-based access for owners, managers and caretakers.

  1. 01

    Understand

    We worked through a month in the life of a property manager — invoicing, collection, utilities, repairs and owner reporting.

  2. 02

    Architect

    Properties → units → tenancies as the core model, with subscriptions, roles and permissions built in from the start.

  3. 03

    Build

    Units, tenants and rent invoicing first; utilities, maintenance, payroll and reporting followed in phases.

  4. 04

    Integrate

    M-Pesa STK Push and PayBill payments matched automatically to tenant invoices.

  5. 05

    Deploy & support

    Launched as a subscription platform, with ongoing support and improvements driven by the managers using it.

04 · Solution architecture

Layers of the system.

Clients at the top, the core application in the middle, integrations and data underneath. Green marks the integration layer where the system meets the outside world.

05 · Key features

What the system does.

Properties, units & tenants

The full portfolio with every unit, tenancy and contact in one place.

Rent & invoicing

Invoices generated on schedule; payments matched automatically.

M-Pesa payments

Tenants pay via STK Push or PayBill against their own invoice.

Utilities & maintenance

Utility bills and maintenance requests tracked to each unit.

Roles & permissions

Owners, managers and caretakers each see what they need.

Subscription management

Plans, billing and access for each landlord or agency on the platform.

06 · Technology

The stack behind it.

Chosen for the job — mature, supportable and straightforward to host and staff for in Kenya.

Backend
PHP Laravel
Frontend
Vue Tailwind CSS
Data
MySQL Redis
Integrations
M-Pesa SMS

07 · Business impact

What changed for the business.

Outcomes are described qualitatively. Figures are published only when verified by the client and approved for release.

  1. 01

    Reduced manual rent tracking and receipting

  2. 02

    Tenants pay via M-Pesa against system-generated invoices

  3. 03

    Utilities and maintenance handled in the same system as rent

  4. 04

    Owners and managers see property status according to their role

08 · Screens

Interface illustration.

A representative illustration of the interface, not a live screenshot — no client data is shown.

Similar problem?

Have a process that looks like this one?

Tell us how it runs today. We will tell you what a system built for your operation would involve.