Frequently Asked Questions

This page is written like a real product FAQ, but it also doubles as a way to explain the FlyLoop subscription concept clearly to anyone viewing your portfolio or CV.

Is FlyLoop live right now?
No. FlyLoop is currently a concept and portfolio piece that shows how a subscription-based travel service could look and feel. It’s meant for user testing, business planning and investor or recruiter conversations rather than real bookings.
Would flights and hotels actually be included?
In a real version, yes. Each plan would include flights, hotels, basic transfers and curated suggestions, negotiated using wholesale travel rates and partner agreements. This site shows what that user experience could look like before connecting a real booking engine.
How would the three plans work?
The concept has three core tiers:
  • Basic Loop – 1 trip / year to closer destinations.
  • Standard Loop – 2 trips / year, more date flexibility.
  • Premium Loop – 3 trips / year and access to higher-end stays.
Each tier would have rules about how soon you can travel after joining, how many guests you can bring and which destinations are unlocked.
How do you stop people from joining, traveling once, and cancelling?
Travel subscriptions usually rely on:
  • Minimum membership terms (e.g. 3–6 months before first use).
  • Trip credits that accumulate over time before redemption.
  • Loyalty rewards for long-term members.
  • Pause options instead of full cancellation.
Those same ideas can be built into FlyLoop’s model and tested using this concept site before coding a full backend.
Can this model be profitable?
Profit could come from negotiated rates, group departures, breakage (not everyone uses all trips), and upsells like extra nights, room upgrades or local tours. For a deeper portfolio piece, you can extend this FAQ with simple unit economics or example P&L scenarios.
What would need to exist for FlyLoop to become real?
At minimum:
  • Real authentication (sign-up, login, password, user accounts).
  • A database for users, memberships, trips, and bookings.
  • Payment integration (e.g. Stripe) for recurring billing.
  • A basic admin panel to manage destinations and inventory.
This FAQ plus the “How it works” page basically functions as a lightweight product spec you can show to devs, mentors or investors.