Arcadia Kost
A boarding-house platform that takes a tenant from browsing a room to booking, paying, and requesting maintenance — while staff manage occupancy and payments from one admin panel.
Background
Boarding houses usually run on chat threads and spreadsheets. Tenants ask whether a room is free, transfer the rent, send a photo of the receipt, and staff reconcile it by hand. Nobody has one shared record of which room is occupied, who has paid, or which maintenance request is still open.
Process
Requirements & data model
Mapped the actors — guest, customer, staff, and owner — into use cases and a product backlog, then turned them into a class diagram covering users, room types, rooms, bookings, payments, reviews, service requests, and chats.
Tenant application
Built the landing page and Breeze authentication, then the room catalog, booking flow, payment page, dashboard, reviews, service requests, and a customer–staff chat widget.
Operations panel
Implemented the Filament admin panel with role-based access: booking validation, room and room-type management, payment-proof review, service-request queues, review moderation, staff chat, and revenue reporting.
Testing & documentation
Wrote the product backlog, use-case specification, class diagram, and a black-box test plan covering authentication, booking, payment, and admin flows.
Gallery
Key Features
Specific-room booking
Tenants choose a physical room, a start date, and a 1–12 month duration. The price is calculated on the spot and the room is marked occupied immediately, preventing double bookings.
Payment proof workflow
A generated QR encodes the bank transfer details. The tenant uploads a receipt, the booking moves to review, and staff validate it from the admin panel.
Tenant dashboard
Shows the active stay, payment schedule, cleaning schedule, and recent activity, with actions to extend a booking or leave a review when the stay completes.
Service requests
Cleaning and repair requests carry a note and a scheduled date, and move through pending and completed states that staff manage from one queue.
Admin panel with roles
Filament resources for bookings, rooms, room types, users, reviews, and service requests, guarded by owner/staff/customer policies — plus revenue charts, a profit summary, and a customer tracker.
Customer–staff chat
An in-app chat widget keeps conversations attached to the account instead of a personal phone number, with message polling every few seconds.
The finished system covers the whole rental lifecycle — browse, register, book, pay, staff validation, active stay, extension, and review — with the staff side needed to operate it. The repository holds 10 models, 28 migrations, 6 Filament resources, and roughly 11k lines of PHP and Blade. It also ships with a product backlog, use-case spec, class diagram, and black-box test plan, which I now reuse as a planning template for larger builds.