Property Manager
Properties, bookings and operations together in one view.
The problem
A small rental business was running its properties from messages, a shared calendar and a spreadsheet. Double bookings were a real risk, and guests asked the same questions every week.
Before writing any code, I broke the project down into features and phases with a cost and time for each, so the client could choose what mattered most first.
What it does
- Accounts & sign-inPeople sign up, log in and reset their password.
- Admin panelEdit pages, items and settings without a developer.
- Image uploadsUpload, resize and order photos and files.
- Bookings & calendarAvailability, reservations and a shared calendar.
- Email notificationsConfirmations, reminders and updates by email.
- Dashboard & reportsKey numbers and lists at a glance.
- Multiple languagesThe site in more than one language.
Decisions along the way
i thought aboutA fixed price for everything at once is a risk for both sides.
so i builtThe work was split into phases, each one useful on its own, so the client could start small and add the rest later.
i thought aboutDouble bookings are the most expensive mistake.
so i builtOne calendar is the source of truth for availability, and every booking goes through it.
i thought aboutThe owner is not technical and should not need me for small changes.
so i builtAn admin panel to edit properties, photos, prices and text without a developer.
How the work was split
- phase 1
Foundations
Properties, photos and content, editable by the owner.
~9–18 days
- phase 2
Bookings
One shared calendar, with confirmation emails.
~6–13 days
- phase 3
Operations
An overview of the week, and the site in a second language.
~5–11 days
An example breakdown: effort is in working days, before design and launch.
What I'd do next
Looking for a quote for your project?
Start from the features Property Manager uses, switch off what you don’t need and add what you do.
Start from Property Manager