Full stack Accommodation Booking and Management System

FULL-STACK TEAM — ACCOMMODATION BOOKING & MANAGEMENT PLATFORM

Budget: Approx. AUD $8,000 fixed price
Website Live: Within 14 calendar days
V1 Platform Target: 8 weeks
Initial Deployment: One property, multi-property architecture from Day 1

PROJECT

We require an experienced full-stack development TEAM to build Version 1 of a custom accommodation booking, property-management and resident-services platform.

This is NOT simply a website or WordPress project.

The immediate commercial priority is getting the first property's website LIVE and accepting real bookings/payments within 14 days, while development of the main platform occurs in parallel.

The complete resident lifecycle is:

Website → Room Availability → Booking → Stripe Payment → Resident Account → Room → Smart Access → Internet → Move-In → Condition Report → Occupancy → Payments/Services/Maintenance → Checkout → Access Removed → Internet Disabled → Cleaning → Condition Comparison → Approval → Room Ready

---

1. PUBLIC WEBSITE — LIVE BY DAY 14

The first property website must include:

- Homepage/property information
- Individual rooms/room types
- Professional photo galleries
- Pricing
- Availability
- Amenities/facilities
- Location/maps
- Nearby facilities/attractions
- FAQs/contact
- Direct booking
- Online payment

Management must be able to update rooms, photos, descriptions, prices and availability without a developer.

The site must be premium, fast, mobile-first, responsive and SEO-ready.

DAY-14 ACCEPTANCE

A genuine customer must be able to:

Visit → View Property → View Rooms → Check Availability → Select Room → Book → Pay → Receive Confirmation

The booking must also appear in management.

---

2. BOOKING ENGINE

Required workflow:

Dates → Availability → Room → Resident Details → Account → Terms → Payment → Confirmation

Must support:

- Nightly/weekly/monthly accommodation
- Minimum stays
- Deposits
- Booking status
- Extensions/cancellations
- Prevention of conflicting bookings

---

3. STRIPE PAYMENTS

Integrate Stripe for:

- Booking payments
- Deposits
- One-off charges
- Recurring weekly/monthly payments
- Receipts
- Refunds
- Failed-payment status
- Payment history

Raw card information must NOT be stored by our application.

---

4. MANAGEMENT PORTAL

Central management dashboard including:

- Properties
- Rooms
- Availability
- Booking calendar
- Residents
- Occupancy
- Arrivals/departures
- Payments/outstanding accounts
- Cleaning
- Maintenance
- Smart-access status
- Internet status
- Services
- Basic reporting

Management must be able to create/edit/extend/cancel bookings, move rooms, check residents in/out and manage room status.

---

5. RESIDENT PORTAL / PWA

Mobile-first resident portal/PWA containing:

- Accommodation/room
- Booking dates
- Payments/receipts
- Documents
- Smart-access information
- Internet
- Utilities where available
- Cleaning bookings
- Maintenance requests
- Property services

Native iOS/Android apps are NOT required for V1.

---

6. ENTRY CONDITION REPORT

Digital move-in condition report including:

- Configurable checklist
- Furniture/inventory
- Guided photographs
- Photos linked to individual checklist items
- Resident comments
- Additional resident photos
- Resident acknowledgement
- Historical record
- PDF report

Example:

Bed → Photo
Desk → Photo
Floor → Photo
Bathroom → Photo

The original report becomes the baseline for checkout/cleaning comparison.

---

7. CLEANER PORTAL & WORKFLOW

Restricted cleaner accounts.

Checkout → Room Cleaning Required → Job Created → Cleaner Assigned → Temporary Access → Original Condition Photos → Cleaning Checklist → Matching Completion Photos → Damage/Missing Items Reported → Management Review → Approved or Rectification → Cleaner Payment Approved → Room Ready

Management must see:

ENTRY PHOTO | CLEANER COMPLETION PHOTO

for corresponding room items.

Cleaner payment is approved only after management accepts the clean. Automated cleaner payout is NOT required for V1.

---

8. MAINTENANCE

Residents can lodge maintenance requests with:

- Category
- Description
- Photos
- Access permission

Management can review, assign and track requests.

Basic restricted contractor accounts are required.

---

9. SMART ACCESS — TTLOCK / TT HOTEL

Our environment uses TTLock / TT Hotel.

Target workflow:

Booking Activated → Room Access Scheduled → Access Active at Check-In → Booking Extension Extends Access → Checkout Removes/Expires Access

Temporary access is also required for cleaners/contractors.

Management must see provisioning status:

Pending / Successful / Failed

with manual intervention/retry where required.

Explain your TTLock experience or proposed integration approach.

---

10. INTERNET — MIKROTIK / UNIFI

Network environment:

- MikroTik
- Ubiquiti / UniFi Wi-Fi APs

Target workflow:

Resident Activated → Internet Provisioned → Network Profile Applied → Resident Receives Access → Checkout → Internet Disabled

Management requires status and manual override/retry.

Explain your MikroTik and UniFi experience.

---

11. AUTOMATED MOVE-IN / MOVE-OUT

MOVE-IN

Booking → Payment → Resident Account → Room → Smart Access → Internet → Instructions → Condition Report → Active Resident

Management should see whether each activation step succeeded.

MOVE-OUT

Checkout → Access Removed → Internet Disabled → Cleaning Required → Cleaner Job → Temporary Access → Original Photos → Clean → Completion Photos → Management Approval → Room Ready

---

12. RESIDENT SERVICES

The resident portal must support property-branded services including:

- Cleaning
- Internet
- Transport
- Food delivery
- Laundry
- Airport transfer
- Car/bike services
- Parking/storage
- Future services

Management can configure services and pricing.

The system must support property-specific:

- Percentage markup
- Fixed markup
- Percentage + fixed markup

and record supplier/base cost, markup and resident charge.

---

13. TRANSPORT / FOOD ORDERS

Direct Uber/Uber Eats API integration is NOT mandatory for V1.

V1 requires:

Resident Requests Service → Property Price/Markup → Resident Pays → Paid/To Be Booked → Operator Places External Order → Reference Entered → Resident Confirmation

The architecture should allow greater automation later.

---

14. UTILITIES

Architecture must support resident utility information including:

- Electricity
- Hot water
- Cold water
- Gas
- Internet
- EV charging

We have existing utility systems/APIs. Detailed requirements will be supplied to the selected team.

---

15. MULTI-PROPERTY ARCHITECTURE

V1 launches with one property, but the platform MUST be multi-property from Day 1.

Future properties must support separate:

- Branding/domain
- Rooms/residents
- Staff
- Pricing
- Smart-lock configuration
- Network configuration
- Services/markups

We must be able to add Property 2 without rebuilding the platform.

---

16. TECHNICAL EXPECTATIONS

We expect:

- Modern frontend/backend
- API-first architecture
- Relational database
- Secure authentication
- Role-based permissions
- Secure photo/document storage
- Cloud hosting
- Git/version control
- Development/staging/production environments
- Backups
- Logging/error monitoring
- Integration failure/retry management

We require access to the Git repository throughout development.

We are NOT looking for the core platform to be assembled from WordPress plugins.

---

DELIVERY

Day 4: Initial website UX/UI
Day 7–10: Functional staging website
Day 14: Production website live + bookings + payments
Week 3: Management/resident core
Week 4: Condition reports/cleaning/maintenance
Week 5: Smart access
Week 6: Internet + lifecycle automation
Week 7: Services/utilities/reporting
Week 8: QA, integration, production and handover

Development must occur in parallel.

---

BUDGET & COMMERCIAL TERMS

Target fixed V1 budget: approximately AUD $8,000.

The shortlisted applicant will receive our detailed Controlled V1 Scope & Acceptance Specification before engagement.

The final agreement will contain:

- Fixed milestones
- Objective acceptance tests
- Client testing periods
- Source-code ownership
- Git access
- Change-control procedure
- Developer-delay provisions
- Late-delivery adjustment
- Final end-to-end acceptance test

Payment will be milestone-based against demonstrated working functionality.

All project-specific source code, database/schema, UI/UX source files, integration code, documentation and deployment configuration must be handed over as agreed.

---

WHO WE WANT

Preferably a small experienced TEAM with demonstrated capability in:

- SaaS/custom software
- Booking/PMS systems
- Stripe/recurring payments
- API integrations
- Smart locks/IoT
- MikroTik
- UniFi
- Workflow automation
- PWA/mobile web
- Cloud/DevOps
- QA

This project is NOT suitable for someone whose primary experience is basic website design.

---

HOW TO APPLY

Start your response with:

ACCOMMODATION PLATFORM

Then provide:

1. Team size and roles.
2. Examples of similar systems you personally built.
3. Recommended technology stack.
4. How you will achieve the Day-14 live website.
5. Confirmation you can target V1 within 8 weeks.
6. Approximate fixed price.
7. Stripe/recurring-payment experience.
8. TTLock/smart-lock experience.
9. MikroTik/UniFi experience.
10. Multi-property architecture approach.
11. Availability to commence.
12. Anything in this scope you believe cannot realistically be achieved within the budget/timeframe.

Do not send a generic proposal.

Shortlisted applicants will receive a detailed technical questionnaire and the full Controlled V1 Scope.

We are looking for a development partner who understands the platform as one integrated accommodation operating system, not a collection of unrelated pages and plugins.