OpenAI 2026 hackathon

myBud

myBud is an all-in-one cannabis tracking app that scans receipts, logs sessions, and turns usage and spending into personalized insights—helping everyday users buy smarter and find what works best.

Solo project by Jordan Fortin · 0 likes · 0 comments

Archive position — measured, not model output

0 likes on Devpost

2,264 of the 7,856 archived projects have more likes, and 5,592 share exactly 0 — so this project's #5,448 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

The description states that myBud is an all-in-one cannabis tracking app designed for everyday users. It scans receipts, logs sessions, and turns usage and spending into personalized insights. The author describes it as a full-stack web application built with Next.js, React, Node.js, Express, and PostgreSQL.

What changed

The project began as a proof of concept and evolved into a larger idea aimed at solving real-world problems for cannabis users. It includes features like receipt scanning via OCR and AI, session logging, analytics, and subscription-based access to premium features.

Single most important open question — the commercial due-diligence read

Is there evidence of user demand or market traction beyond the author’s own development efforts? The description does not indicate any revenue, customers, or adoption metrics. There is no indication that myBud has moved beyond a solo developer prototype.

Back to contents

What The Product Actually Is

The description states that myBud is a full-stack web application built with Next.js, React, Node.js, Express, and PostgreSQL. It allows users to upload cannabis receipt images, which are processed using OCR and AI to extract structured data such as dispensary name, purchase date, strain names, product quantities, taxes, discounts, and total amounts.

It also includes:

  • Cannabis session logging
  • Saved session history
  • Purchase and spending tracking
  • Usage analytics
  • Favorite brand/product insights
  • Most-used and highest-spending dispensary insights
  • Public/private profiles
  • Customizable profile themes
  • Subscription plans with feature restrictions
  • Privacy controls (including self-hosting toggle in development)

The system synchronizes data across multiple database tables, including a ledger for active purchases and summary tables for long-term analytics.

Evidence Author’s own write-up

Inference The app functions as a personal dashboard for tracking cannabis use and spending, with some AI-driven automation in receipt processing.

Back to contents

Positioning & Claim Evolution

The author claims that myBud fills a gap between medical and everyday users by helping them understand their purchases, spending, usage, and experiences. It aims to help users make smarter purchasing decisions, manage spending, and discover what works best for them.

It positions itself as a tool that turns raw data into personalized insights rather than just storing information.

Evidence Author’s own write-up

Inference The app is positioned as a utility for personal cannabis consumption tracking with an emphasis on usability and insight generation.

Back to contents

Target Customer & ICP

The description states that myBud targets "everyday users" who want to better understand their cannabis habits, spending, and product preferences. It also mentions a need for better tools for both medical and everyday users.

It does not specify demographic details or segmentation beyond general user types.

Evidence Author’s own write-up

Inference The target customer is likely individuals who use cannabis regularly and are interested in tracking their consumption and spending behavior.

Back to contents

Business Model & Pricing Evidence

The description indicates that myBud offers subscription plans with different levels of access to features. Premium users can activate a "Privacy Mode" toggle, which moves user data to device files for self-hosting (a feature still in development).

There is no mention of pricing tiers or monetization strategy beyond subscriptions.

Evidence Author’s own write-up

Inference The business model appears to be subscription-based with tiered access and a privacy-focused premium offering.

Back to contents

Technical & Delivery Signals

The app was built as a full-stack web application using:

  • Frontend: Next.js, React
  • Backend: Node.js, Express
  • Database: PostgreSQL
  • Authentication: JWT
  • OCR/ AI processing for receipt parsing
  • REST API endpoints
  • Mobile-first design principles

It includes debugging systems for tracking data flow and error handling.

Evidence Author’s own write-up

Inference The technical stack suggests a modern, scalable architecture suitable for full-stack development. However, the app is currently in early-stage development and lacks independent validation or production deployment signals.

Back to contents

Traction & Maturity Signals

The description does not provide any evidence of traction, revenue, customer base, or adoption metrics. It is described as a solo developer project submitted to a hackathon.

Evidence Author’s own write-up

Inference No evidence of market traction or user engagement beyond the author's own development efforts.

Back to contents

Competitive Context

The description does not mention any competitors or direct market comparisons. The author notes that they want to “compete with major companies,” but no specific competitive landscape is described.

Evidence Author’s own write-up

Inference No clear understanding of existing players in the cannabis tracking space, if any.

Back to contents

Key Risks & Red Flags

  • No traction or revenue: The project has not demonstrated any user adoption or monetization.
  • Solo developer prototype: Built by one person; no team structure or operational history.
  • Unverified claims: All features and functionality are self-reported without external validation.
  • Privacy mode in development: A key feature is still under construction, suggesting incomplete product maturity.
  • Lack of market data: No indication of demand, user feedback, or competitive positioning.

Evidence Author’s own write-up

Inference The lack of verified traction and operational history raises concerns about scalability and viability as a commercial venture.

Back to contents

Diligence Questions To Ask The Founders

  1. What is the current status of the receipt scanning accuracy? Has it been tested with real-world data?
  2. Are there any existing users or beta testers for myBud?
  3. How does the app plan to scale beyond a solo developer prototype?
  4. What are the legal and regulatory considerations around handling sensitive user data in the cannabis industry?
  5. Is there a roadmap for monetization beyond subscriptions, such as partnerships with dispensaries or brands?
  6. What is the timeline for launching the privacy mode feature?

Back to contents

Investment/Partnership Verdict

The description states that myBud is an early-stage prototype built by a single developer and submitted to a hackathon. There is no evidence of revenue, customers, or traction beyond the author’s own development work.

Verdict Not evidenced as a viable commercial opportunity at this stage. The project lacks measurable impact, market validation, or team structure necessary for investment or partnership consideration.

Confidence Level Low — based entirely on self-reported information with no external corroboration.

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.