A purpose-built, multi-tenant mobile & web platform that runs front office, housekeeping, dining, banquets, and franchise operations across JMC Hotels & Resorts, Mint Tree, and Deotel — as one system, not thirty spreadsheets.
Before proposing an architecture, here's our read of how JMC Hotels & Resorts Group actually operates today — based on the current site, portfolio, and service lines.
The core, high-volume chain — comfort-first, business and leisure traveller focused, the widest geographic spread of the three brands.
The elevated tier — refined design and service standard, positioned above the core chain for guests seeking more polish.
Nature-blended, full-service resorts and heritage stays — banquets, gardens, and destination properties sit largely here.
25+ live properties spanning industrial belts, highway towns, temple towns, and one wildlife-tourism resort — not a single-city chain.
Every JMC property already reports up through a brand into the group. The platform mirrors that exactly — so a request to add hotel #151 is a form, not a re-engineering effort.
Every module below is grounded in a real service line JMC already offers, from the family-tree staff philosophy to the ShriG kitchens.
Group Owner's control room. Onboard hotels, assign brand identity, monitor every property's live status from one screen.
Express check-in/out, room availability, and housekeeping status in sync — the daily engine room of every property.
Covers ShriG, Star N Sky, the Restro Café, Utsav Banquet Hall, and JMC's 30-year catering business — as bookable, trackable venues.
The services that make JMC "family": doctor-on-call, travel assistance, laundry — logged and time-stamped per guest.
A structured record for the 24×7 surveillance and safety commitments JMC already advertises to guests.
Digitises the two inquiry funnels already on jmchotels.com — corporate accounts and franchisee partners.
JMC's own stated philosophy — staff trained to grow into managers and shareholders — modelled as a real career-progression record.
Roll up occupancy, service requests, and banquet revenue from a single property to the full 150-property group view.
Both share the same multi-tenant backend and role system — they're two faces of one platform, not two separate products.
For the Group Owner, brand admins, and GMs. Switch between any of 150 properties, monitor every department, approve franchisee requests, and see the whole group at a glance.
For department teams on the ground — front office, housekeeping, dining, and guest services — built to keep working through the connectivity gaps common in industrial-belt and highway-town properties.
| Mobile & Admin App | Flutter — a single codebase for JMC Command and JMC Floor across Android and iOS, with an offline-first local cache that syncs when connectivity returns. |
| Backend | Node.js / NestJS with a multi-tenant data model (brand_id + property_id on every record) — designed from day one to isolate data cleanly across 150+ tenants. |
| Database | PostgreSQL with row-level tenancy and indexed property scoping, plus Redis for real-time room-status and dashboard caching. |
| Admin Web Dashboard | Next.js — the same control surface as JMC Command, for HQ staff who prefer a desktop view of the full group. |
| Notifications | Firebase Cloud Messaging for real-time alerts — security incidents, franchisee inquiries, and escalations reach the right role instantly. |
| Access Control | Role-based permissions cascading Group → Brand → Property → Department, with a full audit trail on every sensitive action. |
| Hosting | Cloud infrastructure (AWS/GCP) sized to scale from 25 to 150+ tenants without a re-architecture — horizontal scaling built in from Phase 1. |
Multi-tenant backend, role hierarchy, and JMC Command core — piloted on a small cluster of JMC-brand properties (e.g. the Indore & Pithampur cluster) before wider rollout.
Onboard Mint Tree and Deotel as brand tenants, ship the Dining/Banquet/Catering module, and roll JMC Floor out to all currently live properties.
Corporate/franchisee pipeline, staff & family-tree module, group-wide analytics — the tools that support scaling the portfolio itself.
Infrastructure hardening, load testing at scale, and a self-serve onboarding flow so each new franchisee property can be added without engineering involvement.
Indicative ranges for scoping this conversation — the final quote is fixed after a discovery session confirms exact module depth and integrations.
All figures are indicative planning ranges in INR, not a binding quote. Ongoing hosting, third-party APIs (SMS/WhatsApp, payment gateway if added later), and annual maintenance are scoped separately once Phase 1 requirements are locked.
One codebase serving 150 properties correctly is a different engineering problem than 150 copies of one app — that's the architecture we design for from day one.
A single mobile codebase for every role — GM, housekeeping, front office — keeps the app consistent and maintainable as the portfolio grows.
Built assuming a highway-town or industrial-belt property, not a metro flagship with fibre broadband.
You see the platform working on your existing 25 properties before a single rupee goes toward scaling to 150.
A 45-minute discovery call is enough to confirm module depth, pick the pilot cluster, and lock the Phase 1 quote.