FIXED BUDGET $500 — Build Airport Operations Platform + Partner Portal from Scratch

# FIXED BUDGET $500 — Build Airport Operations Platform + Partner Portal from Scratch We are looking for a strong full-stack React / Supabase developer to build a working MVP from scratch. Fixed budget: USD 500. This is not a design-only project. We need a real working web application with: - authentication; - partner accounts; - operational workflows; - QR tracking; - financial settlement; - invoices; - KPI and ROI reporting; - live flight information; - a focused AI feature. The application will support an airport-based service used in combination with international car-rental companies. The goal is simple: A customer books a rental car and a child seat through the rental company. Our platform then manages the entire operational process behind that child-seat booking. --- # WHAT THE PLATFORM NEEDS TO DO The full workflow should be: Booking received → correct seat category identified → physical seat allocated → seat prepared → cleaning and inspection verified → technician assigned → flight monitored → seat delivered → QR scanned → installation confirmed → vehicle marked ready → rental active → seat returned → cleaning and inspection → seat available again → financial settlement → partner reporting Every important action must be stored with: - timestamp; - user; - booking; - seat; - status; - notes where relevant. The system must not be a collection of static dashboards. The workflow must actually work from beginning to end. --- # USER TYPES The MVP needs four user roles: 1. Super Admin 2. Operations Manager 3. Technician 4. Partner Admin The application must be multi-tenant. A rental partner may only see its own: - bookings; - invoices; - financial data; - performance; - ROI information. This separation must be enforced in the backend/database, not only in the frontend. --- # 1. INTERNAL OPERATIONS DASHBOARD Our operations team needs a command centre showing what requires attention. Show: - today's arrivals; - upcoming bookings; - seats requiring allocation; - seats being prepared; - installations due; - active rentals; - returned seats; - cleaning queue; - inspection queue; - damaged/quarantined seats; - available stock by category; - technician assignments; - overdue tasks; - operational incidents; - delayed or early flights. Main workflow statuses: New → Allocated → Preparation → Ready → Technician Assigned → En Route → Installed → Family Ready → Active Rental → Returned → Cleaning → Inspection → Available --- # 2. RESERVATION MANAGEMENT Each reservation should include: - partner; - location/airport; - external booking number; - pickup date/time; - return date/time; - flight number; - scheduled arrival; - estimated arrival; - seat category; - child age band; - optional child height; - vehicle; - vehicle bay/handover point; - assigned seat; - assigned technician; - daily retail price; - paid rental days; - revenue split; - booking status; - incident status; - notes. The user must be able to: - create; - edit; - search; - filter; - assign seats; - assign technicians; - change status; - view complete history. For the MVP, support: - manual booking entry; - CSV import; - one test/demo webhook endpoint. --- # 3. SEAT INVENTORY Every physical child seat must have a permanent digital record. Fields: - seat ID; - QR token; - manufacturer; - model; - category; - safety certification; - manufacture date; - purchase date; - current airport/location; - current warehouse position; - status; - rental cycles completed; - maximum rental cycles; - last cleaning date; - last inspection date; - current booking; - damage history; - quarantine history; - retirement status. Possible seat statuses: - Available - Reserved - Preparation - Ready - Assigned - Installed - Active Rental - Returned - Cleaning - Inspection - Quarantine - Retired --- # 4. PERMANENT QR CODE Every seat must receive one permanent QR code. The QR should remain with the seat for its complete lifecycle. Do not create a new QR code after every rental. The QR should link to a random public token. Example: domain.com/seat/7fj39sk28 Do not expose internal database IDs. ## Internal QR view Authorised staff should see: - seat information; - current status; - current booking; - complete history; - cleaning records; - inspection records; - rental cycles; - damage; - quarantine; - photos. ## Public customer QR view Customer sees only: - seat category; - seat model; - applicable safety standard; - last cleaned; - last inspected; - prepared for use; - inspection passed; - quality-assured status. No customer data. No employee information. No internal financial data. --- # 5. CLEANING AND INSPECTION Returned seats should enter a controlled workflow: Returned → Initial Inspection → Cleaning → Drying → Reassembly → Final Inspection → Available or: → Quarantine Every step should record: - employee; - timestamp; - checklist; - pass/fail; - notes; - photo evidence where required. A failed seat may not automatically return to available inventory. --- # 6. TECHNICIAN MOBILE WORKFLOW The technician interface must work well on mobile. Technician sees: - today's jobs; - booking deadline; - partner/location; - vehicle; - required seat; - assigned physical seat; - flight status; - job status. Installation workflow: 1. Open job. 2. Scan seat QR. 3. System verifies correct category. 4. Complete installation checklist. 5. Upload installation photo. 6. Enter vehicle location/bay. 7. Mark installation complete. 8. Mark vehicle Family Ready. The completion time must be stored. --- # 7. PARTNER PORTAL This is one of the most important parts of the platform. The rental partner should use the portal mainly for: - management; - finance; - transparency; - KPI monitoring; - ROI; - invoices. They should not need to run the daily fulfilment operation from this dashboard. ## Partner overview Show: - rentals today; - active rentals; - upcoming reservations; - Family Ready vehicles; - correct-seat fulfilment rate; - on-time readiness; - incidents; - completed rentals; - gross child-seat revenue; - partner revenue share; - amount payable; - open invoices; - outstanding invoice value; - launch-credit balance. --- # 8. PARTNER RENTALS Partners should see all relevant bookings. Include: - booking ID; - pickup date; - return date; - location; - flight; - seat category; - seat ID; - vehicle; - preparation status; - installation status; - Family Ready time; - return status; - paid days; - daily rate; - gross revenue; - partner share; - platform share; - invoice period; - incident status. Clicking a rental should open a full event timeline. --- # 9. FINANCE AND INVOICES Partners must be able to see: - gross child-seat revenue; - partner share; - platform share; - refunds; - adjustments; - chargebacks; - monthly settlement; - onboarding credits; - annual programme fee; - VAT fields; - invoice amount; - due date; - payment status. They should be able to: - download invoice PDF; - download booking-level statement; - export CSV; - view invoice history. Payment terms are generally 14 days. For the MVP, payment does not need to be automated. Invoice payment status may be updated manually. --- # 10. REVENUE SHARE LOGIC Commercial terms must be configurable per partner. Default model: - Partner: 30% - Platform: 70% There is also a temporary launch arrangement: - Partner: 50% - Platform: 50% During this temporary period, the extra 20 percentage points received by the Partner should accumulate toward a configurable launch-credit amount. When that target is reached, all future completed rentals automatically change to: 30% Partner / 70% Platform This calculation must work automatically. --- # 11. SIX-DAY CHARGING CAP A customer may keep the seat longer than six days, but only the first six days are charged. Formula: Paid days = minimum(actual rental duration, 6) Gross seat revenue = paid days × daily retail rate Support: - normal rental; - early return; - cancellation; - no-show; - partial refund; - full refund; - manual adjustment; - chargeback. --- # 12. LIVE FLIGHT DATA We want live flight information included in the MVP. Preferred provider: Flightradar24 API or another reliable flight-data API if there is a technical reason. When a reservation includes a flight number, retrieve: - flight number; - scheduled arrival; - estimated arrival; - actual arrival; - delay; - early arrival; - landed; - cancelled; - diverted; - terminal where available. The important requirement: ## Flight changes must affect operations. Example: Scheduled arrival: 18:40 Updated arrival: 17:55 System should automatically generate: ### ARRIVING 45 MINUTES EARLY and increase priority for preparation and installation. A large delay should move the operational deadline accordingly. If live production credentials are unavailable during development: - build the full integration architecture; - connect test/sandbox data; - provide a flight simulator; - switching to production credentials later must not require a rebuild. --- # 13. KPI DASHBOARD Partners should see at least: 1. Correct-seat fulfilment 2. Family Ready on time 3. Cleaning/inspection traceability 4. Operational incidents 5. Commercial performance Additional useful KPIs: - seat utilisation; - average rental duration; - available inventory buffer; - replacement rate; - average preparation time; - installation time; - refunds; - customer complaints; - monthly partner revenue. --- # 14. ROI DASHBOARD We want the partner to see not only what the service costs but also what it creates in value. Separate the dashboard into: ## Verified results Based on actual platform data: - completed rentals; - child-seat revenue; - partner revenue; - average price; - fulfilment; - on-time readiness; - incidents; - refunds; - complaints. ## Estimated business value Partner can enter baseline inputs such as: - current seat purchase cost; - current inventory size; - cleaning cost; - storage cost; - staff handling minutes; - hourly employee cost; - annual seat replacement cost; - refunds; - compensation; - current child-seat price; - estimated family booking conversion; - average vehicle-rental contribution. Calculate: Partner child-seat revenue + avoided seat purchases + avoided replacement costs + avoided cleaning costs + avoided storage + avoided labour + avoided refunds + premium price uplift + estimated additional vehicle-rental contribution − onboarding fees − annual fees = # TOTAL PARTNER VALUE CREATED Show: - current month; - year to date; - trend; - breakdown. All estimates must be clearly marked as estimates. --- # 15. AI PARTNER INTELLIGENCE We want one impressive AI feature. Do not build a generic chatbot. Build an: # AI PARTNER INTELLIGENCE ASSISTANT It should use the logged-in partner's authorised data. Example questions: - How much value did the service create this month? - Which seat category has the highest demand? - Why did our readiness score drop? - When are our busiest arrival periods? - Which days have the highest inventory pressure? - Are we likely to run short of toddler seats? - How many incidents occurred this month? - Compare this month with last month. - Create a management summary. - What should management pay attention to? The AI must not invent numbers. It should use real database data. Where useful, it should also return: - charts; - trends; - KPI comparisons; - tables; - concise recommendations. For this MVP, it is acceptable to support a defined list of high-value questions rather than unlimited analytics. --- # 16. DATABASE AND TECH STACK Preferred stack: ### Frontend - React or Next.js - TypeScript - Tailwind CSS - shadcn/ui or equivalent ### Backend - Supabase Postgres - Supabase Auth - Supabase Storage - Supabase Row Level Security - Edge Functions where required ### Deployment - Vercel or similar ### Code - GitHub We require full ownership of all code, database and deployment accounts at handover. --- # 17. SECURITY Partner A must never be able to access Partner B data. This includes: - bookings; - invoices; - revenue; - ROI; - seats; - performance. Use proper database-level security, preferably Supabase Row Level Security. Do not rely only on frontend filtering. No service-role key may be exposed client-side. --- # 18. REALISTIC DEMO DATA The MVP should not be delivered empty. Include: - DXB airport; - 2 rental partners; - 40 seats; - 4 seat categories; - 20 bookings; - 3 technicians; - cleaning records; - inspection records; - installation records; - returned seats; - 2 invoices; - several incidents; - early-flight scenario; - delayed-flight scenario; - financial settlement data. The system should immediately feel alive during a demonstration. --- # DEFINITION OF DONE The project is complete only when: - application is deployed; - authentication works; - roles work; - partner separation works; - reservations persist; - seat inventory persists; - QR codes work; - public QR passport works; - technician workflow works; - cleaning workflow works; - inspection workflow works; - operational statuses work; - booking timeline works; - live or test flight-data integration works; - flight changes affect operational priorities; - six-day charging cap works; - revenue-share calculation works; - launch-credit calculation works; - invoices work; - PDF downloads work; - settlements work; - KPI dashboard works; - ROI dashboard works; - AI Partner Intelligence works for agreed questions; - the application works after browser refresh; - no major buttons are fake; - no critical console errors; - mobile technician view works; - code is transferred to our GitHub; - database migrations are included; - setup documentation is included; - environment variables are documented; - short Loom handover video is provided. --- # FIXED BUDGET ## USD 500 TOTAL This is a fixed-price MVP. Please only apply if this scope fits your workflow and you are comfortable delivering the agreed MVP within the fixed budget. --- # MILESTONES ## Milestone 1 — $75 Foundation - new codebase; - database architecture; - authentication; - roles; - RLS; - seed-data structure. ## Milestone 2 — $200 Operations - reservations; - seat inventory; - QR system; - cleaning/inspection; - technician workflow; - internal dashboard. ## Milestone 3 — $175 Partner portal - partner dashboard; - rentals; - finance; - invoices; - settlement; - KPI; - ROI; - flight-data functionality. ## Milestone 4 — $50 AI, QA and handover - AI Partner Intelligence; - final testing; - bug fixing; - deployment; - documentation; - GitHub/database handover; - Loom handover video. Milestones are released against working deployed functionality. Screenshots are not considered delivery. --- # PLEASE ANSWER THESE QUESTIONS 1. Show one React/Supabase application you have built. 2. Show one multi-tenant application where different companies could only access their own data. 3. Explain how you will secure partner data using Row Level Security. 4. Explain how you would build the permanent QR lifecycle. 5. Explain how you would implement the 50/50 launch-credit logic and automatic switch to 30/70. 6. Explain how you would connect flight data to operational deadlines. 7. Explain how you would prevent the AI assistant from inventing financial data. 8. Confirm every core workflow will save real data to the database. 9. Confirm the fixed budget of USD 500. 10. State your realistic delivery time. 11. State what access/information you need before starting. Start your application with: AIRPORT OPS