Travel CRM and Flight Ops Platform

I’m building a single web platform that lets a small travel team handle the entire customer journey—from the very first lead to the final flight payment—without yet tying into Amadeus or any other external GDS. For now every booking will be logged manually, but the data model must stay flexible so an API connection can be added later. Core workflow I need: A lead arrives through a form or quick-add panel, lands in an “unassigned” queue, and stays there until I (the admin) pick the right sales agent. Inside the CRM the agent moves that prospect along a visual pipeline, sets follow-ups, and tracks tasks. Each contact grows into a full customer/passenger profile that links to every quote, PNR, payment, and note. Once a seat is confirmed, a flight-operations area lets a booking agent record carrier, segments, fares, and PNR. The interface has to show each agent only their own bookings while giving me an admin “control tower” view of everything—status, commissions, and any locks in place to prevent two people editing the same record. For payments I need a secure Stripe checkout in USD. The passenger fills billing details, pays, and the app automatically updates booking status. Failed or pending payments must hold the record in a locked state until resolved. Role-based access is mandatory: • Admin, sales agents, and flight-booking agents each see only the screens and fields relevant to them. Tech stack preference is MongoDB for data, so schemas for leads, customers, flights, and payments should be designed accordingly, with clean REST or GraphQL endpoints and an extensible permission model. Deliverables that will let me launch Phase 1: • Responsive web app (desktop first; mobile friendly) deployed to my cloud account • Source code and database schema (MongoDB) with basic seed data • Stripe USD checkout integrated and tested in live mode • Admin dashboard with real-time lead, booking, and payment monitoring • Documentation covering local setup, env variables, and future GDS integration points Hand-off is complete when I can create a lead, assign it, convert it to a booking, charge a card, and view the result in reports without touching the code.