Ridgeway
One system that staff, owners, tenants, and field crews all work in, each seeing only what is theirs.
Ridgeway gives a property business one web app and one mobile app, so staff, owners, tenants, and caretakers can all work from the same record. The interesting problems were who is allowed to see which rent, keeping repairs in a strict order, and making the mobile app actually usable on a site.
- Origin
- Studio product
- Platforms
- Web, iOS, Android
- What people open
- Staff, owner, tenant, field
- Role
- I designed it and I built it
- On this project
- Next.js · Expo · Convex · TypeScript
Why it matters
One mistake costs trust.
A property business runs on trust. If one owner can see another owner's rent, or a repair slips through with no record, people stop believing the system. So each person is only ever given what belongs to them, instead of being shown everything with some of it hidden, and every repair keeps a record of what happened to it.
Where it started
The buildings were fine. The way they were run wasn't.
Office staff lived in a spreadsheet. Owners asked for updates in chat and waited. Tenants reported a leak to whoever answered first, and caretakers carried paper and guessed which flat. Nobody ever saw the same picture of the portfolio twice.
I kept the brief narrow on purpose and only set out to fix the system the business runs on. The public site where people browse empty units stays as it is.
What I built
Four kinds of people, one shared record.
- 01
A staff website covering every building, flat, lease, tenant, open repair, and rent period, so the whole portfolio can be run from one screen.
- 02
Owner views locked to the buildings they own, showing occupancy, open issues, and rent collected against rent still due.
- 03
A tenant side, on the web and in the mobile app, to file a repair with a photo, follow it from received to done, read rent reminders, and report a payment for staff to confirm.
- 04
The same mobile app also serves the people on site, with the jobs assigned to them, status changes made on the spot, and a completion photo required before anything closes.
- 05
Repairs that move through the same steps every time (received, assigned, scheduled, done), and a repair that is never deleted once it has been logged.
Staff
The whole portfolio, from one screen.
In the build
The hard parts.
One owner never sees another owner's money
That's the mistake that would end a system like this, so the check is built into the system itself and runs every time any money figure is shown, not just on the screens that look sensitive.
Leases that expire
When a lease ends, the tenant can still sign in, but the flat, its repairs, and its rent are gone from their view. There's no stale home screen pretending they still live there.
One record, two editors
Two staff working on the same repair can't end up with two competing versions where one quietly overwrites the other. There is one job record and a history of who changed what. The history can be added to but never rewritten.
Built for a roof in the rain
The caretaker's app is a short list, a status control, and a camera. Anything more would just be noise when you're standing on a site with one hand free.
Owner
Only the buildings linked to them.
Next project
The desk a wholesale pharmacy runs its week on.