Bedspace Manager
We didn't just design Bedspace Manager for a client — we built and operate it ourselves. It's the clearest proof we have that we understand multi-tenancy, subscription billing, and production SaaS operations from the inside, not just from a proposal deck.
The problem before Bedspace Manager
Operators running bedspace, PG (paying-guest), and shared-room rental portfolios were managing everything — tenant records, rent collection, maintenance requests, occupancy across multiple properties — with spreadsheets, paper ledgers, and ad hoc WhatsApp messages. As soon as an operator grew past one or two properties, that approach stopped scaling.
The existing workflow
A typical operator tracked tenants and payment due dates in a spreadsheet per property, collected rent in cash or via ad hoc bank transfers with no automated reconciliation, and fielded maintenance requests through WhatsApp messages that were easy to lose in a crowded chat thread. There was no single view across properties for an owner managing more than one site, and no audit trail for who paid what, when.
Problems encountered
- −Double-booked beds because occupancy wasn't tracked in one place
- −Missed or late rent collection with no automated reminders
- −No portfolio-level visibility for owners running multiple properties
- −Maintenance requests lost in WhatsApp chat history with no ticket status
- −Manual, error-prone invoice generation at the end of every billing cycle
A dedicated multi-tenant SaaS product for bedspace operators
Bedspace Manager gives each property management company its own isolated workspace, with role-based access for owners, property managers, on-site staff, and tenants. Rent invoicing, maintenance workflows, and occupancy tracking are centralized and automated instead of scattered across spreadsheets and chat apps.
Multi-tenant architecture built for a portfolio business
Every property management company that signs up gets a fully isolated tenant workspace, with data partitioned so one operator's tenants, invoices, and maintenance history are never visible to another. Within a workspace, role-based access control separates what an owner, a property manager, on-site staff, and an individual tenant can see and do.
- Tenant-isolated data model so each operator's portfolio is fully separated
- Role-based access control across owner, manager, staff, and tenant roles
- Subscription billing for the SaaS itself, alongside automated rent invoicing for the operator's own tenants
- Cloud infrastructure sized to handle bursty rent-cycle traffic at the start of each month
Major features shipped to production
Multi-property portfolio management
A single dashboard for owners running several properties, with occupancy, rent status, and maintenance activity rolled up across the whole portfolio.
Automated rent invoicing
Recurring invoices generated automatically on each tenant's billing cycle, replacing manual, error-prone spreadsheet-driven invoicing.
WhatsApp integration
Rent reminders and maintenance updates sent over WhatsApp — the channel operators and tenants were already using — instead of an app tenants have no reason to open.
Maintenance workflows
Maintenance requests become trackable tickets with a status and an owner, instead of messages that get lost further up a WhatsApp thread.
Reporting for owners
Occupancy, collections, and maintenance-response reporting so an owner can see the health of a property without calling the on-site manager.
Mobile applications
A mobile experience for on-site staff and tenants, built for people who are managing or living in the property day to day — not sitting at a desktop.
Integrations:
WhatsApp Business APIPayment gatewayCloud object storage for documents and photosHow it was built
Discovery
Mapped the actual day-to-day workflow of a bedspace operator — how rent gets collected today, how maintenance requests currently travel, and where a portfolio owner loses visibility.
Architecture
Designed the multi-tenant data model and role-based permission structure before writing product code, so adding new operators later wouldn't require re-architecting the core.
MVP build
Shipped tenant management, invoicing, and maintenance ticketing first — the three workflows that were causing the most operational pain.
Iteration
Added WhatsApp integration, reporting, and mobile apps once the core workflows were validated in real day-to-day use.
What was genuinely hard about this
Getting the multi-tenancy model right before scaling operators
Because Bedspace Manager serves multiple independent property management companies, the tenant-isolation strategy had to be correct from the first schema design — retrofitting isolation after operators are live is far more expensive than designing it up front.
Designing around WhatsApp Business API constraints
WhatsApp's messaging templates, rate limits, and approval process shape what an automated reminder or maintenance update can look like — the notification system had to be designed around those constraints, not against them.
Building for on-site staff, not just office admin
On-site staff are moving around a property, sometimes with inconsistent connectivity, so the mobile experience had to stay usable when a WiFi signal wasn't guaranteed.
What changed
- Rent collection and reminders became a scheduled, automated process instead of a manual monthly scramble
- Owners running multiple properties gained a single view of occupancy and collections instead of stitching together separate spreadsheets
- Maintenance requests became trackable tickets with clear ownership instead of messages buried in chat history
Full walkthrough, screenshots, and further detail available on a discovery call.
Tech stack
Lessons learned
- →Multi-tenant billing logic is easiest to get right when it's designed alongside the core data model, not bolted on after the first operator signs up
- →Meeting operators and tenants on WhatsApp drove far higher engagement than expecting them to check a separate app
- →Field-usable mobile UX for on-site staff needs to be designed for intermittent connectivity from day one, not patched in later
Questions about this project
Is Bedspace Manager a product Sword Tech Labs built for a client, or one it operates itself?
We built and operate it ourselves. It's a live proof point for the multi-tenant architecture, subscription billing, and RBAC patterns we design into every SaaS engagement — not a hypothetical case study.
Why is a WhatsApp integration significant from an engineering standpoint?
It means designing notification and workflow logic around a third-party messaging platform's template approval process and rate limits, rather than a fully open channel — a common constraint in SaaS products built for markets where WhatsApp is the primary communication channel.
Can you share detailed metrics or a live walkthrough?
Yes — a full walkthrough, screenshots, and further detail are available on a discovery call. We keep published metrics conservative here and go deeper live rather than publishing numbers without context.
Want SaaS built with this level of care?
The engineers who built Bedspace Managerare the same senior engineers who'll scope and build your SaaS product.