Skip to content
All work

Multi-Tenant SaaS / Accommodation Management

TenancyCo

TenancyCo is an accommodation management platform designed to help operators manage properties, residents, applications, leases, payments, maintenance, and everyday operations in one place.

Role
Founder & Software Product Builder
Period
May 2026 – Present
Status
Pre-launch

01 — Founder story

Why I started building TenancyCo

After working on production software in fintech and enterprise environments, I wanted to own a product end to end — from understanding a problem to designing, building and refining the solution.

Accommodation management stood out because the operational work is real, repetitive and spread across too many tools. TenancyCo is where I combine software engineering with business discovery and full product ownership.

02 — The problem

Operations scattered across disconnected tools

Accommodation operators often rely on disconnected software, spreadsheets, manual records, and messaging applications to manage important operational activities.

That fragmentation makes it hard to see the state of a property, follow an application through to a signed lease, or know which maintenance request is still waiting.

03 — Target users

Three groups, three different jobs

The product is designed around separate workflows for each group that touches an accommodation business.

  • Landlords and operators — oversee properties, finances, occupancy and reporting.
  • Staff — handle day-to-day work: applications, inspections, maintenance and resident requests.
  • Residents and applicants — find accommodation, apply, sign documents, pay and log requests.

04 — The solution

One centralised, multi-tenant platform

A centralized, multi-tenant application with separate workflows for landlords, staff, and residents.

Each operator works inside its own isolated organisation, with roles that decide what every person can see and do.

Key workflows — diagram

Find & apply

  1. 1Public listing
  2. 2Application
  3. 3Review
  4. 4Onboarding

Lease & move in

  1. 1Lease documents
  2. 2Deposit
  3. 3Inspection
  4. 4Move-in

Day-to-day living

  1. 1Rent
  2. 2Maintenance
  3. 3Electricity
  4. 4Shuttle

Architecture & technical decisions

One application, isolated organisations

A simplified view of how the pieces fit together. TanStack Start renders pages on the server and keeps sensitive work in server functions; Supabase provides authentication, data and storage, with row-level policies enforcing that each operator only reaches its own records.

Landlord workspace

Role-based views

Staff workspace

Role-based views

Resident portal

Role-based views

TanStack Start application

Server rendering · server functions · role checks

Supabase

Auth · data · storage · row-level isolation per organisation

PayFast

Rent, deposits & subscription payments

Resend

Transactional email

05 — Development challenges

Where the hard engineering lives

Most of the difficulty is not individual screens, but making many workflows stay correct together.

  • Keeping each operator's data isolated while sharing one application.
  • Designing roles so landlords, staff and residents get the right access — no more, no less.
  • Payment and subscription flows that must handle incomplete or failed payments gracefully.
  • Keeping long workflows (application → lease → move-in) understandable for non-technical users.

06 — Product discovery

Learning from operators before scaling the build

I've been speaking with accommodation operators to understand how they currently work, translating that feedback into product requirements, and preparing product demonstrations to test whether the workflows match their reality.

These conversations are discovery — they shape priorities, and they're not presented here as signed customers.

07 — Testing & validation

Checking the product before it meets real users

Validation work so far has focused on correctness and resilience ahead of launch.

  • QA passes across each role's core workflows.
  • Evaluating multi-tenant security and access boundaries.
  • Load-testing exercises to understand behaviour under heavier use.

08 — Lessons learned

What building it has taught me

Talking to users early changes the priority list more than any technical idea. Access control and data boundaries need to be designed first, not added later. And a product with many features is only useful if each workflow is easy to follow.

09 — Current stage

Pre-launch, and where it's heading

TenancyCo is pre-launch. The focus now is refining core workflows through discovery and demonstrations, hardening security and reliability, and preparing for first real usage.

At a glance

Relevant capabilities

  • Property and unit management
  • Tenant and applicant management
  • Public accommodation listings
  • Applications and onboarding
  • Lease and document workflows
  • Rent and deposit management
  • Maintenance management
  • Inspections
  • Electricity requests
  • Shuttle-related workflows
  • Billing and subscriptions
  • Role-based access
  • Multi-tenant data isolation
  • Operational reporting

My role

What I'm responsible for

  • Identifying operator workflow challenges
  • Conducting customer discovery
  • Translating feedback into product requirements
  • Designing frontend workflows
  • Developing application features
  • Integrating authentication and backend services
  • Building payment and subscription workflows
  • Evaluating multi-tenant security
  • Performing QA and load-testing exercises
  • Preparing and delivering product demonstrations