OpenAI 2026 hackathon

TOKBYS Intelligent Workflow Automation

AI-assisted desktop automation for cooperative credit collection workflows, enhanced with OpenAI Codex during Build Week to improve reliability, maintainability and productivity.

Solo project by Ahmet PORTAKALDALI · 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,320 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

TOKBYS Intelligent Workflow Automation is a self-reported desktop automation tool built during an OpenAI hackathon. The project was submitted by a single founder, Ahmet PORTAKALDALI, and is described as AI-assisted desktop automation for cooperative credit collection workflows.

What changed

No evidence of prior version or evolution; this is the first public manifestation of the idea, presented as a hackathon submission.

The single most important open question

Is there any evidence of actual usage, traction, or commercial viability beyond a hackathon prototype?

Back to contents

What The Product Actually Is

The description states: “TOKBYS Intelligent Workflow Automation” is an AI-assisted desktop automation tool for cooperative credit collection workflows. It was built using technologies such as Python, JavaScript, OpenAI Codex, pyautogui, pypdf, and pyperclip.

Evidence

  • The project uses tools like pyautogui, pypdf, pyperclip, and openai (specifically Codex).
  • It is described as a desktop automation tool.
  • It targets cooperative credit collection workflows.
  • Built during Build Week, with OpenAI Codex used to improve reliability, maintainability, and productivity.

Inference The product appears to be a prototype or proof-of-concept for automating tasks in credit collection using AI and desktop scripting. However, no evidence of actual deployment or customer use is provided.

Back to contents

Positioning & Claim Evolution

The description states: “AI-assisted desktop automation for cooperative credit collection workflows, enhanced with OpenAI Codex during Build Week to improve reliability, maintainability and productivity.”

Evidence

  • The product is positioned as a tool for automating workflows in credit collection.
  • It leverages AI (specifically OpenAI Codex) to enhance functionality.
  • The positioning implies it targets cooperative or team-based processes.

Inference The project appears to be a hackathon experiment with no clear evolution from prior versions. The claim of “enhanced reliability, maintainability and productivity” is self-reported and not substantiated by any data or usage metrics.

Back to contents

Target Customer & ICP

The description states: “cooperative credit collection workflows.”

Evidence

  • The product targets cooperative credit collection workflows.
  • No further segmentation or customer profile is provided.

Inference It’s unclear if the target customer is a business, a team, or an individual. The term “cooperative” suggests a group-oriented workflow, but no specific industry or use case is detailed.

Back to contents

Business Model & Pricing Evidence

Not evidenced.

Evidence

  • No pricing model, monetization strategy, or business model is described.
  • No mention of customers, revenue streams, or commercial intent.

Back to contents

Technical & Delivery Signals

The description states: “Built with (author-declared): automation, codex, desktop, developer, firefox, gpt-5.6, javascript, openai, pyautogui, pypdf, pyperclip, python, tools, workflow.”

Evidence

  • Built using Python and JavaScript.
  • Uses OpenAI Codex and pyautogui, pypdf, pyperclip.
  • The project is described as a desktop automation tool.

Inference The technical stack suggests a developer-focused tool built for automation. However, no evidence of delivery, deployment, or scalability is provided.

Back to contents

Traction & Maturity Signals

Not evidenced.

Evidence

  • The product was submitted to a hackathon.
  • No mention of users, customers, or adoption.
  • No data on usage, retention, or growth.

Inference There are no signs of traction or maturity beyond a prototype. The project is described as a hackathon submission with no indication of further development or commercialization.

Back to contents

Competitive Context

Not evidenced.

Evidence

  • No mention of competitors or market landscape.
  • No comparison to existing tools in the automation or credit collection space.

Inference No competitive positioning or market analysis is provided. The project appears isolated from any broader market context.

Back to contents

Key Risks & Red Flags

  1. Single-founder prototype: The project is a solo effort with no team, suggesting limited development capacity.
  2. No traction or commercialization: No evidence of users, revenue, or adoption beyond a hackathon submission.
  3. Unverified claims: All claims about AI enhancement and productivity gains are self-reported.
  4. No business model: No indication of how the product would generate revenue or scale.

Back to contents

Diligence Questions To Ask The Founders

  1. What is the actual use case for cooperative credit collection workflows, and how does this tool solve a real problem?
  2. Has there been any user testing or feedback beyond the hackathon?
  3. What is the plan for scaling beyond the prototype stage?
  4. How does this product differ from existing desktop automation tools in the market?
  5. Is there any intention to commercialize this, and if so, what is the monetization strategy?

Back to contents

Investment/Partnership Verdict

Not evidenced.

Evidence

  • No financials, traction, or commercial viability are provided.
  • The project is described as a hackathon submission with no indication of further development or market readiness.

Inference At this stage, there is insufficient evidence to support an investment or partnership decision. The project appears to be a prototype with no demonstrated value proposition, user base, 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.