OpenAI 2026 hackathon

WorthHours

A shift calendar that uses GPT-5.6 to turn natural language into structured work entries, while the app keeps pay calculations clear and consistent.

Solo project by Boris Nikolov · 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 #7,740 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

The company appears to be a solo project named WorthHours, built as part of an OpenAI hackathon. The author states it is a shift calendar app that uses GPT-5.6 for natural language input into structured work entries, with the goal of simplifying tracking of shifts, breaks, overtime, pay expectations, appointments, and notes.

The key change described is the integration of AI (GPT-5.6) to convert natural language into structured calendar data, while maintaining app logic for business-critical calculations like pay.

The single most important open question is: what is the actual commercial viability or traction potential of this tool?

The description provides no evidence of revenue, customers, usage metrics, or market adoption beyond the author's own claims. The project is self-reported and unverified, with no third-party corroboration of its functionality or business model.

Back to contents

What The Product Actually Is

  • The description states that WorthHours is a shift calendar app.
  • It allows users to track work shifts, breaks, overtime, expected pay, appointments, and notes.
  • Data entry occurs via two methods:
    • Direct calendar input (choosing date and adding shift, template, or note)
    • AI Quick Add: natural language input processed by GPT-5.6 into structured calendar drafts
  • The app uses Codex for development and is deployed on Vercel
  • A serverless endpoint calls the OpenAI API, using GPT-5.6 to return structured data (not final calculations)
  • After AI processing, the app applies its own logic for calculations, warnings, and saved calendar data

Back to contents

Positioning & Claim Evolution

  • The description states that WorthHours was inspired by a problem: shift workers know when they worked but struggle to track hours, breaks, overtime, pay expectations, appointments, and notes in one clean place.
  • The app is positioned as a small, practical shift calendar that feels fast on a phone and keeps important numbers visible.
  • The key claim evolution is the use of AI Quick Add to convert natural language into structured entries.
  • The author states that AI is useful for understanding flexible human input, but the app remains responsible for business logic (pay rules, warnings, calculations).
  • This positioning suggests a focus on usability and simplicity, with AI as an enhancement rather than core functionality.

Back to contents

Target Customer & ICP

  • The description states that WorthHours targets shift workers.
  • It is designed to help people track work shifts, breaks, overtime, expected pay, appointments, and notes in one clean place.
  • No specific customer segments or personas are identified beyond "shift workers."
  • There is no evidence of market research, user interviews, or segmentation beyond the stated problem.

Back to contents

Business Model & Pricing Evidence

  • The description does not provide any information about pricing models, monetization strategies, or business model details.
  • It mentions that "the AI layer can become the foundation for a future premium version", suggesting potential paid features.
  • There is no evidence of current revenue streams, pricing tiers, or customer acquisition costs.

Back to contents

Technical & Delivery Signals

  • The app is built with:
    • Codex (for development and testing)
    • React
    • TypeScript
    • JavaScript
    • CSS
    • Vercel (deployment platform)
    • Serverless endpoint calling the OpenAI API
  • The app uses GPT-5.6 to return structured data, not final calculations
  • The author notes that Codex helped build and test:
    • The serverless endpoint
    • Structured output schema
    • Preview flow
    • Warning logic
    • README
    • Submission materials
  • No evidence of scalability, infrastructure robustness, or technical architecture beyond the development stack.

Back to contents

Traction & Maturity Signals

  • The project was submitted to the OpenAI 2026 hackathon.
  • It is described as a "small, practical shift calendar" built during a short timeframe (Build Week).
  • There is no evidence of:
    • Revenue
    • Customers
    • Usage metrics
    • Product-market fit
    • Market traction
    • User feedback or adoption data

Back to contents

Competitive Context

  • The description does not mention any direct competitors.
  • It implies that the app addresses a gap in existing shift tracking tools, particularly for shift workers who struggle to manage multiple aspects of their work schedule.
  • No evidence of market analysis, competitive landscape, or differentiation from existing solutions.

Back to contents

Key Risks & Red Flags

  • Solo founder: The team size is listed as 1, which may indicate limited capacity for execution or scaling.
  • Unverified technology claims: The use of "GPT-5.6" is self-reported; there's no verification that such a model exists or is being used.
  • No commercial viability evidence: No revenue, customers, or traction data provided.
  • Unclear monetization strategy: While the AI layer may support future premium features, there's no current business model described.
  • Limited scope: The app is described as small and practical, which may limit its appeal or scalability.

Back to contents

Diligence Questions To Ask The Founders

  1. What specific problems do shift workers face that this tool solves?
  2. How does the AI Quick Add feature currently work in practice? Can you show an example of input/output?
  3. Are there any existing competitors in this space, and how is WorthHours differentiated from them?
  4. What is the plan for monetization beyond the potential premium version?
  5. How do you intend to scale or grow the user base?
  6. What are the technical limitations or constraints of using GPT-5.6 for this purpose?
  7. Is there any feedback from early users or potential customers?

Back to contents

Investment/Partnership Verdict

  • Not evidenced: There is no evidence of revenue, customers, traction, or commercial viability.
  • The project appears to be a proof-of-concept or prototype built during a hackathon.
  • It lacks clear business model, pricing strategy, or market validation.
  • The solo founder structure raises concerns about execution capacity.
  • The use of "GPT-5.6" is self-reported and unverified; no evidence that such a model exists or is being used.
  • Without further information on traction, market demand, or monetization plans, it's difficult to assess investment potential.

Confidence Level: Low

This analysis is based entirely on the author’s own description, which is unverified and self-reported. No external corroboration exists for any claims made about the product, its functionality, or its 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.