Full-Stack Developer Needed: Operations System to Supabase + Custom Staff UI

# Full-Stack Developer Needed: Migrate Google Sheets / Apps Script Operations System to Supabase + Custom Staff UI We are looking for an experienced full-stack developer to help migrate an existing resort operations system from Google Sheets and Apps Script into a more robust Supabase/PostgreSQL database with a custom web-based staff interface. This is not a greenfield discovery project. The current working prototype already exists in Google Sheets and Apps Script. We need a developer who can understand the existing schema and business logic, migrate it into a proper database structure, and build a controlled MVP/pilot version for operational testing. ## Project Background We operate a scuba diving resort and dive center with complex daily operations including: * Guest records * Bookings * Group bookings * Room assignments * Dorm bed tracking * Dive schedules * Course schedules * Sipadan permit allocations * Boat/activity planning * Transfers * Passport/document tracking * Medical/waiver tracking * Staff views * Audit/history tracking The current prototype has been built in Google Sheets with Apps Script automation. It includes approximately 60 connected tables and a significant amount of working operational logic. The goal is to migrate this into a professional, secure, maintainable platform. Our preferred stack is: * Supabase / PostgreSQL * Custom web UI * React / Next.js preferred * TypeScript preferred * Role-based staff access * Clean documentation and handover We are open to recommendations on the best technical structure, but we want to stay close to Supabase/PostgreSQL unless there is a strong reason not to. ## What We Need Built We are looking for a developer to help with the following phases: ### Phase 1 — Review Existing System * Review the current Google Sheets schema * Review the Apps Script workflow logic * Understand existing booking, guest, rooming, permit, transfer, and scheduling logic * Identify what should be migrated directly and what should be improved during migration * Produce a short technical implementation plan before full build starts ### Phase 2 — Supabase/PostgreSQL Database Build a clean database structure for the main operational system, including: * Guest master records * Guest contact details * Bookings * Booking guests * Stays * Daily booking/activity schedule * Room assignments * Dorm bed assignments * Transfers * Dive/course activity records * Sipadan permit allocation and assignment logic * Identity/passport documents * Dive certifications * Medical and waiver records * Special requirements * Attachments/documents * Audit logs * User roles and permissions The database must be maintainable, well-normalized where appropriate, and designed for future expansion to other locations. ### Phase 3 — Staff Web Interface Build an MVP staff interface for operational use. Initial screens should include: * Booking creation / quick hold entry * Confirm hold * Release hold * Cancel booking * Guest search and guest profile * Booking profile * Room assignment view * Transfer view * Sipadan permit allocation view * Daily operations board * Guest timeline / forecast view * Document status view * Basic admin/settings pages The UI does not need to be overly fancy, but it must be clear, reliable, and easy for non-technical operations staff to use. ### Phase 4 — Business Logic Migrate or rebuild key workflow logic, including: * Booking status transitions * Hold / confirm / release / cancel workflows * Room overlap checks * Dorm bed tracking * Sipadan permit availability and assignment * Transfer generation * Daily schedule generation * Guest document status tracking * Duplicate guest prevention * Basic audit logging * Staff role restrictions ### Phase 5 — Migration / Backup Workflow We need help moving from the existing Google Sheets system into the new database. This may include: * One-time import from Google Sheets into Supabase * Data validation during import * Error reporting for failed rows * Optional export/sync back to Google Sheets during pilot as a backup * Clear instructions for future imports/exports ### Phase 6 — Testing, Documentation, and Handover This is very important. We need the system to be maintainable after the project is complete. Required handover items: * Database schema documentation * Explanation of core workflows * Setup/deployment instructions * Environment variable documentation * Admin guide * Basic user guide * Test cases for critical workflows * Recorded walkthroughs or live handover sessions * Clean, readable code * Code stored in a Git repository we control ## Ideal Developer You should have strong experience with: * Supabase * PostgreSQL * Row Level Security / permission design * React or Next.js * TypeScript * Database design * Operational systems or booking systems * Data migration from spreadsheets * API design * Authentication and user roles * Clear documentation Experience with Google Sheets and Apps Script is a strong bonus, because the current system is built there. Experience with hospitality, resorts, diving, tours, travel, logistics, or scheduling systems would also be helpful. ## Important Requirements Please only apply if you are comfortable with: * Reading and understanding an existing system before rebuilding it * Working from existing schema and operational workflows * Building a practical MVP, not just a nice-looking front end * Using milestone-based delivery * Providing clear documentation * Handing over the codebase properly * Explaining technical decisions in plain English * Building something maintainable by another developer later We do not want a black-box system that only the original developer can maintain. ## Suggested Milestones Please include your recommended milestones in your proposal. A possible structure is: 1. System review and technical plan 2. Supabase database schema and auth/roles foundation 3. Core booking and guest workflows 4. Rooming, transfers, activities, and permit workflows 5. Daily operations views and guest timeline 6. Migration/import tools 7. Testing, documentation, and handover We are open to your suggested structure. ## Proposal Instructions In your proposal, please answer the following: 1. Have you built a Supabase/PostgreSQL operational system before? Please describe it. 2. Have you migrated a system from Google Sheets, Airtable, Excel, or Apps Script before? 3. What stack would you recommend for this project? 4. How would you structure the database and permissions? 5. How would you approach the migration from the existing Sheets system? 6. What would you include in the MVP? 7. What would you need from us before giving a fixed quote? 8. What is your estimated timeline? 9. What is your estimated cost range? 10. How do you handle documentation and handover? Please include links to relevant previous work, especially database-heavy apps, booking systems, operations systems, dashboards, or Supabase projects. ## Budget We are currently gathering quotes and comparing options. Please provide either: * A fixed-price estimate broken into milestones, or * An hourly rate with an estimated range of total hours We are more interested in the right developer and a maintainable system than the lowest possible quote. ## Timeline We would like to begin with a review/planning phase first, then move into MVP development. Our goal is to have a testable MVP/pilot version within the next few months if realistic. ## Final Note This project is operationally important to our business. We are looking for someone reliable, detail-oriented, and able to build a system that staff can actually use every day. Please start your proposal with the phrase “Supabase Resort Ops” so we know you have read the full post.