OpenAI 2026 hackathon

Yo te Llevo

Your next trip, your way.

Solo project by Joel Cortes · 1 likes · 0 comments

Archive position — measured, not model output

1 like on Devpost

506 of the 7,856 archived projects have more likes, and 1,758 share exactly 1 — so this project's #2,252 place in the like-ranked listing is a tie-break inside that group, not a ranking.

Projects (log scale)

1
10
100
1k
10k
05,592
11,758
2285
3–4132
5–975
10+14

Likes on Devpost. ▲ marks this project's group.

Show the figures
LikesProjectsShare of archive
05,59271.2%
11,75822.4%
22853.6%
3–41321.7%
5–9751.0%
10+140.2%
Devpost like counts for all 7,856 archived projects, captured when this archive was built.

Executive Summary

What the company appears to be

Yo te Llevo (translated as "I'll give you a ride") is a self-reported peer-to-peer ride-hailing platform built by one individual developer, Joel Cortes, for the OpenAI 2026 hackathon. The project is described as a platform connecting passengers with drivers, using PHP and SQL technologies.

What changed

The project was submitted to a hackathon, indicating it is in an early development or prototype stage. No commercial traction, revenue, or customer data is evident.

Single most important open question

Is this a functional product or a proof-of-concept? The description does not indicate whether the platform has been tested with real users or deployed for actual ride-hailing services.

Back to contents

What The Product Actually Is

The description states:

  • “Connects people with drivers”
  • Built using PHP, SQL, CSS, JavaScript, and Spanish language support
  • Developed with help of Codex and ChatGPT

Inference The product is a web-based platform intended to function as a ride-hailing marketplace. It is not evidenced whether it has a mobile app or a live deployment.

Not evidenced

  • Whether the platform supports real-time matching, payment processing, or driver/passenger verification
  • Whether it includes features like trip tracking, ratings, or geolocation services

Back to contents

Positioning & Claim Evolution

The description states:

  • Tagline: “Your next trip, your way.”
  • Inspiration came from wanting to avoid Uber InDrive’s cut of profits
  • The author is proud of creating something useful for passenger transport workers

Inference The positioning appears to be a low-cost alternative to existing ride-hailing platforms, targeting drivers and passengers who want to avoid platform fees. It is not clear if the product is intended for broader market adoption or just personal use.

Not evidenced

  • No evidence of branding, marketing strategy, or user personas
  • No indication of how it differentiates from other platforms like Uber or Lyft

Back to contents

Target Customer & ICP

The description states:

  • “I’ll give you a ride” is for people who work in passenger transport
  • The author wants to help drivers and passengers

Inference The primary users are likely drivers and passengers in the ride-hailing space, particularly those seeking an alternative to traditional platforms.

Not evidenced

  • No customer segmentation or ICP definition
  • No evidence of user research or feedback from target audience
  • No indication of geographic scope or market focus

Back to contents

Business Model & Pricing Evidence

The description states:

  • The author wants to avoid Uber InDrive’s cut of profits
  • No pricing model is mentioned
  • No revenue streams are described

Inference The business model appears to be based on avoiding platform fees, but it is unclear if the product will charge users or drivers for using the service.

Not evidenced

  • No pricing structure, fee model, or monetization strategy
  • No evidence of subscription plans, transaction fees, or advertising

Back to contents

Technical & Delivery Signals

The description states:

  • Built with PHP, SQL, CSS, JavaScript, and Spanish language support
  • Developed using Codex and ChatGPT
  • Submitted to a hackathon

Inference The platform is likely a basic web application built quickly in a short timeframe. It may not be production-ready or scalable.

Not evidenced

  • No evidence of backend architecture, API integrations, or scalability
  • No mention of security features, data privacy, or user authentication systems
  • No indication of deployment environment or hosting

Back to contents

Traction & Maturity Signals

The description states:

  • Submitted to the OpenAI 2026 hackathon
  • Built by one developer (Joel Cortes)
  • “My greatest achievement is knowing that I did something that was only in my mind”

Inference This is a prototype or proof-of-concept, not a product with traction or user adoption.

Not evidenced

  • No evidence of users, customers, or active usage
  • No data on performance metrics, retention, or growth
  • No indication of product maturity or roadmap

Back to contents

Competitive Context

The description states:

  • Inspired by Uber InDrive’s fee structure
  • Aims to avoid platform fees

Inference It is positioned as a competitor to traditional ride-hailing platforms like Uber and Lyft, but with a focus on avoiding intermediary fees.

Not evidenced

  • No evidence of competitive analysis or market research
  • No indication of how it would compete in terms of features, pricing, or user experience
  • No mention of existing competitors or their market share

Back to contents

Key Risks & Red Flags

The description states:

  • Built by one person
  • Submitted to a hackathon
  • Uses AI tools like Codex and ChatGPT for development

Inference

  • Risk of limited functionality, scalability, or security due to single-person development
  • Risk of lack of product-market fit or user adoption
  • Risk of technical debt or incomplete features due to rapid prototyping

Not evidenced

  • No evidence of legal compliance, insurance, or safety protocols
  • No indication of regulatory or licensing considerations for ride-hailing services
  • No mention of data governance or privacy practices

Back to contents

Diligence Questions To Ask The Founders

  1. What is the intended user experience and how does it differ from existing platforms?
  2. Is this a prototype or a working product with real users?
  3. How does it plan to handle driver verification, trip safety, and payment processing?
  4. Are there any legal or regulatory considerations for operating a ride-hailing platform?
  5. What is the long-term vision for the product beyond the hackathon?
  6. Has the platform been tested with real users or drivers?

Back to contents

Investment/Partnership Verdict

The description states:

  • This is a hackathon submission by one developer
  • No evidence of traction, revenue, or customer adoption
  • The author’s goal was to create something useful for passenger transport workers

Inference This is not a commercial product with demonstrated market demand or viability. It is a self-reported prototype with no evidence of business maturity or scalability.

Not evidenced

  • No financials, revenue model, or customer data
  • No indication of team expansion or product development plans beyond the hackathon
  • No evidence of partnerships, funding, or commercial interest

Verdict Not suitable for investment or partnership at this stage. This is a self-reported idea with no demonstrated traction or business model.

Back to contents

Source

Submitted to the OpenAI 2026 hackathon on Devpost. Project home on DevPost.

The analysis above was generated by a language model from the project's own one-line description. It is not independent research and contains no verified traction, revenue or customer data.