Mountain Resort SaaS MVP Development

Hi,

I'm building a SaaS for mountain tourism complexes and I need a developer (or a small team) to build the MVP.

A mountain complex is one site with everything a mountain guest needs: hotel, chalets and huts, restaurants from valley to summit, gear rental, spa and sports, lifts, and transport. Most run each part on a separate system or on paper. A guest arrives by train, takes the shuttle up, rents skis, eats at the summit, books the sauna, and at checkout nobody has the full bill. When the wind closes the cable car, staff find out too late.

The MVP has to prove one thing: one platform can run a full day of a mountain complex, put everything on one guest bill, and warn staff before the weather hits. I'll pilot it with 2-3 real complexes, then build the full SaaS on top.

MVP SCOPE

1) Core
- Complexes (tenants), buildings with altitude (hotel, chalets, huts, lift stations), outlets, staff roles
- Winter and summer seasons with their own prices
- Multi-tenant from day one, no self-signup (I create complexes)

2) Hotel
- Rooms in different buildings, hut beds, season prices
- Board plans (B&B, half board, full board)
- Reservations, calendar, check-in / check-out

3) Guest folio
- One bill per stay, every outlet can "charge to room"
- Cash or card recorded (no gateway), split payment, printable invoice

4) Food, shop and rental
- POS for restaurants and huts, knows which meals the board plan includes
- Mountain gear shop
- Rental: skis, boots, helmets, bikes, e-bikes, with sizes, deposit, return, damage fee

5) Hotel services
- One booking engine for sauna, bath, spa, game room, sports, ski school and guided hikes: time slots, capacity, staff, price

6) Transport and lifts
- Types: shuttle bus, taxi, car, bicycle, motorbike, lifts (cable car, chairlift, funicular, elevator) and external (plane, train, metro)
- Own vehicles and drivers: schedules, routes on a map, bookings, no double-booking
- Lifts: open / closed / on hold, lift passes charged to room
- A guest's train or flight arrival creates a pickup

7) Weather (very important)
- Forecast per building and lift station, because valley and summit differ: wind and gusts, snow or rain, fog, temperature
- Limits per complex, warnings on affected lifts, trips and outdoor services
- "Cancel for weather" that fixes the guest bills
- Lobby TV screen: weather, lift status, avalanche level

8) Owner dashboard and reports

NOT IN THE MVP: online payments, guest portal, lift gate hardware, real train or flight ticket booking, offline mode.

Web platform only: everything runs in the browser on laptop, tablet and phone. No mobile apps.

HOSTING AND CI/CD
No domain yet, no Docker. Node.js, PostgreSQL and Nginx directly on my Ubuntu 24.04 VPS, which already runs other sites.
GitHub Actions: tests on every pull request, auto deploy to my VPS on merge to main, rollback if the new version fails.

TECH
Next.js + NestJS (or Laravel) + PostgreSQL. Free services only, no paid APIs or keys: weather from MET Norway, maps from OpenStreetMap.

WHAT I EXPECT
- You've built a multi-tenant SaaS or a hotel / booking / POS system and can show it running
- Code in my GitHub, CI/CD working from milestone 1
- Tests on the money parts
- README, server setup script, database backup script

5 milestones, about 12 weeks, details in the attached PDF. The list is long for an MVP and I've kept each part simple. If you think something should be cut, tell me.

IN YOUR BID, PLEASE ANSWER
1. A similar system you built (link or video).
2. A guest charges a summit lunch and a ski lesson to the room, the lesson is cancelled for wind, and they pay the rest half card, half cash. How would you model that so each outlet still sees its own correct revenue?
3. Your timeline, and the riskiest part.

Thanks.