NEWNew: MnT AI Desk · MnT AI CRM · MnT Commerce India
MnT Future
Client project

RG Golden Palace

Wedding venue, Singampunari, Sivagangai

Not a venue website. The system the venue is run on.

Built by MnT FutureLive
rggoldenpalace.com
RG Golden Palace website
Why a website was not the answer01 / 04

What they would still have been doing by hand.

01

A wedding venue is a hotel business: rooms, bookings, guests, staff, stock and money, all on the same day.

02

Run on registers and WhatsApp, the answer to "is the 14th free" depends on who you ask.

03

Expenses and takings are reconciled at month end, from paper, by one person.

What their team does in it02 / 04

The part the public never sees.

Not a feature list. These are the jobs somebody at the client does in this system, on an ordinary day, without calling us.

Take and hold bookings

Rooms and dates in one system with payment through Razorpay, so availability is a fact rather than an opinion.

Run the front desk

Guests, a log book and a CRM, so what happened on a given day is recorded rather than remembered.

Manage staff

Employee management with roles and permissions: the cleaner and the manager do not see the same screens.

Track money

Expenses and financials in the platform, so month end is a report rather than an evening of paperwork.

Hold stock

Inventory, because a venue runs out of things and finding out on the day is expensive.

What is actually in there03 / 04

17 modules, read off the codebase.

Not a claim about what a site like this usually has. This is the list of sections and routes that exist in this project, which is the difference between a portfolio and an inventory.

bookingsroomsguestscrmemployeeManagementrolesAndPermissionexpensesfinancialsinventorylogBookhotelDetailshotel-datahotelColorsettingsweb-settingsauthemail verification

Seventeen modules including payroll-adjacent staff management, expenses and inventory. If any single project on this page proves the point, it is this one.

Built with
Next.js 14React 18MongoDBRazorpayAWS S3
How we work

We don't build websites. We build the system your business runs on.

The site your customers see is the front of it. Behind it sits the part your team actually lives in: prices, bookings, orders, enquiries, stock, staff. Changed by you, on the day you decide, not by us on a support ticket.

That is the whole difference. A website tells people you exist. A system runs the business, and it keeps running when you are not looking at it.

Next step

What would your team stop doing by hand?

Tell us the job somebody in your business repeats every week: the rate change, the booking register, the enquiry that gets written on paper. A senior consultant will map what running it properly would take.