RENTTER
Rental operations prototype, December 2025. Built with n8n and MCP after four landlord and tenant interviews. No users yet.
Rentter is a rental operations prototype built from four landlord and tenant interviews. It connects discovery, a PRD and user stories to five working automations.
Challenge
Rentter explores the recurring follow-up involved in rental operations: rent reminders, payment receipts, rent increases, lease expiry and missed payments.
Opportunity
The prototype tests whether these recurring steps can be handled through connected automations. The goal is to make follow-up more consistent; that benefit still needs validation with users.
My Role
I interviewed four landlords and tenants, wrote the PRD and user stories, and built the n8n and MCP automations.
Scope
I kept the build focused on five specific workflows: rent reminders, receipts, rent-increase notices, lease-expiry notices and missed-payment alerts. This gives the prototype a concrete scope to test with users.
Current status
The five automations run end to end. Rentter remains a prototype with no users, so I am not claiming adoption, time savings or business outcomes.
Rentter is a prototype with no users yet. The automations run end to end; their impact on day-to-day rental operations has not been measured with users.