Guidely

The description states that Guidely is a travel marketplace connecting travellers with verified local guides. It is built as a cross-platform Flutter application powered by Supabase.

• Travellers can browse, search, filter and save tour packages.
• Guides can create profiles, publish packages, upload images, and manage bookings.
• Admins can review applications, moderate content, and manage support requests.
• The platform uses Supabase Auth for secure login, PostgreSQL with Row Level Security (RLS) for data protection, Supabase Storage for media, and Resend SMTP for email delivery.

Inference The product is a marketplace MVP with three user roles: traveller, guide, and admin. It includes basic booking request functionality and package management features, but lacks payments or live chat in the current version.

The author states that Guidely’s tagline is “Connect with verified local guides for unforgettable adventures.” The project description emphasizes:

• A marketplace connecting travellers and local guides.
• Secure booking workflow.
• Verified guide profiles.
• Cross-platform mobile application (iOS, Android).
• MVP built by a solo developer.

Inference The positioning appears to be a travel marketplace focused on authentic local experiences. The claim evolution suggests an early-stage MVP with a focus on foundational features like secure authentication and booking workflows, rather than monetization or advanced UI/UX.

The description states that Guidely targets:

• Travellers looking for tour packages.
• Local guides who want to offer their services.
• Admins who moderate the platform.

Inference The ICP appears to be a niche market of solo or small-group travellers in Nepal (specifically Pokhara) seeking local, authentic experiences. The author does not describe any segmentation strategy beyond user roles.

The description does not provide evidence of pricing or monetization models. It mentions:

• A booking request workflow.
• Future features like online payments and cancellation management.

Inference There is no evidence of a business model or pricing structure in the current version. Payments are listed as a future feature, suggesting the platform may be in an early stage of monetization planning.

The author states that Guidely was built using:

• Flutter for cross-platform mobile app.
• Supabase backend including Auth, PostgreSQL with RLS, Storage, and custom SQL functions.
• Resend SMTP for email delivery.
• Custom UI design with animations and responsive layouts.

Inference The technical stack suggests a modern, scalable architecture. The use of Supabase and RLS indicates an emphasis on secure data handling, which is a positive signal for platform integrity. However, no evidence of production deployment or scalability beyond MVP exists.

The description states:

• The project was built by one developer (Narayan Adhikari).
• It is an MVP submitted to a hackathon.
• Features include secure booking workflows and package management.
• Future plans include payments, notifications, and calendar scheduling.

Inference There is no evidence of traction or adoption. The platform is described as a solo-developer MVP with no revenue, customers, or user base mentioned. The maturity level is early-stage, focused on foundational features.

The description does not provide any information about competitors or market positioning beyond the general idea of a travel marketplace.

Inference No evidence of competitive analysis or differentiation strategy exists in the provided description. The author does not reference existing platforms like Airbnb Experiences, Viator, or local Nepali tour operators.

• Solo developer MVP: The project is described as built by a single person, which raises concerns about scalability and long-term maintenance.
• No traction or revenue: There is no evidence of users, customers, or monetization.
• Limited feature set: Payments, live chat, and notifications are listed as future features, suggesting the platform is not yet fully functional for real-world use.
• Unverified claims: All descriptions are self-reported and unverified.

Inference The biggest risk is that the project may not scale beyond MVP or prove viable in a competitive market without further development and validation.

1. What is the current status of user adoption or testing?
2. How do you plan to validate demand for local guides in specific destinations like Pokhara?
3. Are there any partnerships with local tour operators or travel agencies?
4. What are your plans for monetization beyond the booking request workflow?
5. How will you scale from a solo developer to a team or product development cycle?
6. What is the timeline and roadmap for implementing payments, notifications, and calendar features?