Property-management automation for small landlords
“Software that automates tenant communication, maintenance scheduling, and rent reminders for landlords with 5–50 units.”
Solid demand in an underserved middle — too big for spreadsheets, too small for enterprise PM software.
Fatal flaw: Landlords are price-sensitive and slow to switch; you must save real hours in week one or they revert.
- AppFolio / Buildium. Win on simplicity and price for the 5–50 unit owner they over-serve.
- Spreadsheets + texting. Replace the manual chase with automated reminders and a maintenance inbox.
The blueprint
LedgerKey
The quiet operations layer for small landlords.
Wedge & Positioning
Owners of 5–50 units who self-manage. Lead with the single most hated task: maintenance coordination.
Monetization
$2–$4 per unit / month. A 20-unit landlord pays ~$60/mo — cheap vs the hours saved.
Architecture
Next.js + Supabase + a messaging provider (email/SMS). Maintenance inbox, scheduling, automated rent reminders.
Data Model
owners, properties, units, tenants, leases, maintenance_tickets, reminders.
Agent Team & Tool Policies
An assistant drafts tenant replies and schedules; the owner approves before anything sends.
Launch Plan (guarded)
Onboard 15 landlords locally. Approval gate before any tenant message or charge goes out.
Growth Loop
Tenants experience the polished flow and recommend it to their other landlords.
Risks & Approval Gates
Biggest risk: switching inertia. Import their unit list in minutes. Human approval before messages and charges.
The build pack
Problem
Small landlords coordinate maintenance and rent over scattered texts and email — it's error-prone and time-consuming.
Target user
Self-managing owners of 5–50 units.
Core jobs
Track units, handle maintenance requests, and chase rent automatically.
Success metric
Maintenance tickets resolved per week without manual chasing.
Build "LedgerKey", a property-management tool for small landlords, with Next.js + Supabase. Screens: (1) Portfolio (properties → units → tenants); (2) Maintenance inbox (tickets with status open/scheduled/done); (3) Rent reminders schedule; (4) Auth (email). Data: owners, properties, units, tenants, maintenance_tickets (see fields), RLS so an owner sees only their data. Per-unit pricing via Stripe ($3/unit/mo). Calm, dense, operator-friendly UI. Wire real Supabase queries, no mock data.
create table owners (id uuid primary key, email text); create table properties (id uuid primary key, owner_id uuid references owners(id), address text); create table units (id uuid primary key, property_id uuid references properties(id), label text); create table tenants (id uuid primary key, unit_id uuid references units(id), name text, contact text); create table maintenance_tickets (id uuid primary key, unit_id uuid references units(id), status text default 'open', detail text, created_at timestamptz default now());