Inspiration

Air ticket booking is still chaotic. Prices vary wildly for the exact same flight across different agencies. Customers are forced to manually contact multiple agents, compare rates, and negotiate—often without clarity. We realized there’s no system putting the customer in control of this process. So we asked: What if the agencies competed for the customer's attention instead?

That idea became Biddly .


What it does

  • A customer registers and submits a flight request: trip name, destination, dates, passenger count, budget, and extra info.
  • All registered travel agencies see the request and place their bids with a price.
  • The customer receives these bids and can:
    • Accept the best offer
    • Reject a bid
    • Chat directly with the agency for negotiation

The current version is a working MVP with real-time interactions between customers and agencies.


How we built it

We built Biddly using modern, scalable tools with speed and collaboration in mind—perfect for the Bolt AI Hackathon environment.

  • ⚛️ Frontend: React for building a responsive, dynamic user interface.
  • 🛢 Backend & Database: Supabase for real-time PostgreSQL, authentication, and role-based access—made development fast and flexible.
  • 💬 Real-time Features: Supabase's built-in real-time capabilities power the bid updates and customer-agency chat.
  • Bolt AI: We leveraged Bolt AI tools to streamline our development process, brainstorm features, and accelerate rapid prototyping.
  • 🔐 Auth & Roles: Supabase's Auth system lets us easily manage separate flows for customers and agencies.

This tech stack helped us rapidly prototype a smooth, functional MVP with real-time interactions and a clean user experience.


Challenges we ran into

  • Managing role-specific access and ensuring clean data flow across the customer-agency interaction.
  • Chat implementation without breaking MVP constraints.
  • Designing a flexible database schema to allow future scalability to other services.
  • While Bolt AI accelerated prototyping, we occasionally faced limitations in fine-tuning real-time logic and multi-role workflows within its no-code/low-code constraints.

Accomplishments that we're proud of

  • We created a functional, role-based platform from scratch within the hackathon timeline.
  • Integrated chat communication for a smoother, user-friendly bidding and negotiation flow.
  • Built a customer-first solution that flips the traditional ticket booking model.

What we learned

  • The power of simplicity in MVPs: focusing on one core pain point can lead to a powerful product.
  • The value of a good schema and clean API architecture when building systems with multiple roles and actions.
  • Features like chat significantly improve user experience when integrated thoughtfully.

What's next for Biddly

  • 💳 Payment Gateway Integration for direct booking.
  • 🎟 In-app Ticket Confirmation, reducing dependency on chat.
  • 🌍 Service Expansion to other sectors: plumbing, electrician bookings, or car rentals.
  • 🗺 Map Integration to allow location-aware bidding and availability.
  • 📈 Analytics Dashboard for agencies to view demand trends and improve competitiveness.

Built With

Share this project:

Updates