All case studies

Fintech Web App · Full Stack

Rent financing, from first quote to final instalment

A rent-finance platform that quotes a renter in seconds, underwrites them, pays the landlord upfront and collects the instalments back.

flexirent.io
Industry
Fintech · Proptech
Timeline
Ongoing
Year
2026

What it supports

Instant quotes

A renter enters their rent and move-in date and sees the upfront amount, the monthly figure and the full dated schedule.

Identity & affordability

National ID, bank or mobile statements and an income declaration, with documents purged once they are no longer needed.

Underwriting decisions

Recorded decisions against the evidence, so an approval can be explained months later.

Instalments & payouts

Landlord paid upfront, renter repays on schedule; payments, declarations and proof all held against the lease.

Extensions & settlements

Renters can ask for more time and staff can settle a running tenancy from the console, with the paperwork to show for it.

Marketing site & intake

The public site captures the enquiry, emails the personalised plan and hands the applicant straight into the portal.

The challenge

Tanzanian landlords ask for six or twelve months of rent in advance. Renters who can comfortably pay monthly cannot raise a year at once, so they borrow badly or move somewhere worse. Financing that gap means underwriting strangers on thin documentation, paying a landlord upfront, and collecting for months afterwards — with every figure quoted, emailed and charged having to agree, or trust goes first and the money follows.

How we built it

The decisions that shaped the product, in the order we made them.

  1. 01

    One pricing engine, everywhere

    The public quote on the marketing site is computed by the same code that builds a real signed lease. A figure a prospect sees cannot drift from what they are later charged, because there is no second formula to drift from.

  2. 02

    Qualified people before properties

    The journey proves identity and affordability first, and only then asks about a landlord — so nobody assembles a whole application to be declined at the end.

  3. 03

    Derived the progress, never stored it

    Which step a renter is on is read from the facts — ID given, statement uploaded, agreement signed — not from a status column. A stored step drifts from the documents, and then the staff funnel reports on the drift.

  4. 04

    Made the schedule the source of truth

    Terms are snapshotted at signing and the instalment schedule is dated from the move-in day, so editing a property's rent next year cannot rewrite an agreement already running.

  5. 05

    Gave staff a console for the awkward days

    Payments, landlord payouts, extension requests and settling a running tenancy are operations someone can actually perform, with the evidence attached.

What it's built with

Named in full, because the question behind it is usually whether your own team could take this over.

  • Django + DRFmoney engine and API
  • PostgreSQLorg-scoped, exact decimals
  • Celery + Redisreminders and retention sweeps
  • React + TanStack Startportal, console and site
  • Google sign-in + JWTrenter accounts
  • S3-compatible storageKYC documents
  • Brevoplans, reminders, receipts
  • Docker + Caddyautomatic TLS

Results

1 engine

Quote, email and invoice cannot disagree

Qualify first

No application assembled only to be declined

Full trail

Every payment carries its evidence