TrackMyPG

TrackMyPG is a live SaaS product we own and ship. The brief was practical: Indian PG and hostel operators were running occupancy, rent and deposits across notebooks, Excel and chat. We built a single operations layer — operator dashboard plus tenant-facing portal — covering the full stay: enquiry to move-out.

• Operator tools for tenants, rooms, invoices, payments, deposits and tickets
• Tenant portal for invoices, payments, profile updates and support requests
• Multi-property plans so an owner can run one PG or several from one account

TrackMyPG sits on the supply side of rental operations. Operators manage beds and rooms, assign tenants, generate monthly invoices (rent, utilities and other charges), track collection across UPI, bank transfer, cash and online gateways, settle security deposits at move-out, and handle maintenance through a shared ticket timeline. Indian PG and hostel work is high-churn and cash-heavy — operators need bed-wise pricing, stay status and bulk monthly billing, not a generic hotel PMS. The product is public at trackmypg.com with a free trial path for new operators.

TrackMyPG serves the property management and PropTech space — specifically Indian PG, hostel and co-living operators who need SaaS for occupancy, rent and tenant operations rather than a generic hotel PMS.

Scattered tools made the same data wrong in three places. Rent reminders lived in chat. Deposit history was tribal knowledge. Tenants had no clean way to see dues without calling the manager. We needed software that reflected real workflows — not a CRM with “property” renamed — and that stayed usable on phones during evening collections.

• One source of truth for rooms, beds, tenants and stay status
• Billing that can run monthly in bulk without losing review control
• A tenant surface that does not expose the full operator dashboard

We mapped operator days: check-ins, room changes, invoice generation, payment logging, notice approval and deposit refunds. Edge cases mattered early — partial months, shared amenities charges, move-out while dues remain, and tickets that mix maintenance with billing questions. Those journeys drove the data model and permission boundaries before UI polish.

The system is a web application with a React/Next.js client and a Node.js API layer over MongoDB. REST endpoints own tenant, room, invoice, payment and ticket domains. Role-based access separates owner, staff and tenant sessions. Multi-PG accounts share infrastructure while scoping data to the properties an operator is allowed to see.

The product surface covers the operational loop end to end — not a demo of two screens.

• Tenant profiles, documents, room assignment and stay status
• Room and bed occupancy with amenities and capacity views
• Auto invoicing with review, send and bulk generation
• Payment tracking and gateway-ready digital collection
• Security deposit ledger and refund settlement at move-out
• Financial reports and filtered exports for audits
• Bulk import/export for rooms and tenants via Excel-friendly flows
• Tenant portal and support tickets with comments and attachments

We chose a TypeScript-first stack so product and API contracts stay aligned as modules grow. Next.js and React power the dashboards; Express-style Node services expose REST APIs; MongoDB stores operational documents that change shape as plans expand. Auth and RBAC gate every sensitive action. Deployment uses CI/CD onto Vercel-friendly hosting for the web surface, with API and data services structured for the same delivery cadence.

Operator UI prioritises density where managers work (lists, filters, status chips) and calm clarity where tenants pay and raise tickets. We avoided generic “SaaS empty states” that hide the next action. Move-out and deposit flows are stepwise so money and vacancy stay linked. Mobile-responsive layouts matter because collection and ticket replies often happen away from a desk.

List and report views are built around filtered queries rather than loading entire property histories into the browser. Auth sessions and RBAC keep tenants out of operator mutations. Sensitive tenant documents and payment metadata are treated as restricted resources. We favour predictable API responses and guarded writes over clever shortcuts that break under concurrent staff use.

Multi-PG plans assume an operator’s portfolio grows. Property scoping, plan tiers and bulk operations (import, invoice generation, exports) are first-class so the product does not force a spreadsheet escape hatch when room counts climb. The architecture keeps room for additional payment gateways and marketplace-adjacent collection without rewriting the core ledger.

TrackMyPG is live in production at trackmypg.com. Operators can trial the product publicly. We do not publish fabricated occupancy percentages or revenue multiples here — the honest outcome is a working system of record for PG operations, owned and iterated by BuildsInfinity, with a clear path from signup to day-to-day use.

This is not a brochure site dressed as a case study. TrackMyPG is our own SaaS bet on a messy vertical: bed-wise occupancy, Indian payment habits, deposit discipline and a tenant portal that respects role boundaries. The standout is operational honesty — features match how hostels run, not how pitch decks describe “PropTech.”