OpenAI 2026 hackathon

SortaSmart

“Automatically analyses Outlook emails, ranks likely project candidates from addresses, participants and filing history, then files, indexes and retrieves correspondence across project archives.”

Solo project by Ben B · 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 #6,866 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

SortaSmart is a self-reported email management tool built for project managers, consultants and accountants who handle large volumes of correspondence across multiple clients. The author states it automatically analyzes Outlook emails to identify likely project candidates based on email content, participants and filing history, then files and retrieves those emails into project archives. It was built using Office.js and other web technologies by a single developer (Ben B) in the context of an OpenAI 2026 hackathon.

The tool is described as faster than a legacy system (Mail Manager) it replaces, but lacks evidence of actual use or adoption. The author claims to have departed from big tech and reduced subscription costs, though no commercial traction or revenue data is provided. The project appears to be in early development with limited customer validation.

The single most important open question

Is there any evidence that the described functionality has been tested at scale or validated by actual users beyond the developer?

Back to contents

What The Product Actually Is

The description states that SortaSmart "automatically analyses Outlook emails, ranks likely project candidates from addresses, participants and filing history, then files, indexes and retrieves correspondence across project archives."

It is built using:

  • CSS
  • HTML
  • JavaScript
  • Next.js
  • Node.js
  • Office.js

The author reports that it was built by passing existing code into Codex, with some manual adjustments for layout and functionality.

Inference The tool appears to be a browser-based Outlook add-in leveraging Microsoft's Office.js API, designed to automate email filing and project candidate identification within an organization’s email system.

Back to contents

Positioning & Claim Evolution

The author states that SortaSmart was inspired by dissatisfaction with a legacy service (Mail Manager) that they no longer wanted to pay for. The tool is positioned as an alternative to proprietary systems like Synergy, which the author claims locked users into their platform and prevented access to original emails.

The product is described as:

  • Not proprietary
  • Faster than previous versions of Mail Manager
  • More intelligent in identifying project candidates than its predecessor

Inference The positioning appears to be a niche solution for professionals managing large volumes of client emails, with emphasis on avoiding vendor lock-in and improving speed over legacy systems.

Back to contents

Target Customer & ICP

The author describes the target user as:

  • Project managers
  • Consultants
  • Accountants
  • Anyone who has "multiple clients and long-standing clients where they might be running hundreds or even thousands of projects"

These users are said to need help filing emails away, which is described as "cumbersome" and "too much to file."

Inference The ICP seems to be small-to-medium businesses or individuals managing high-volume email workflows across multiple clients, with a focus on reducing manual filing tasks.

Back to contents

Business Model & Pricing Evidence

There is no evidence provided in the description regarding pricing, monetization strategy or business model. The author mentions that they previously paid for Mail Manager and wanted to avoid recurring costs, but does not elaborate on how SortaSmart would be monetized.

Inference No commercial model is evident from the self-reported description.

Back to contents

Technical & Delivery Signals

The tool was built using:

  • Office.js (Microsoft's API)
  • Next.js
  • Node.js
  • HTML/CSS/JavaScript

The author notes that Office.js was a major challenge, describing it as "absolute rubbish" and difficult to work with due to manifest loading issues.

The system is said to analyze:

  • Aliases
  • Recent activity
  • People's names
  • Grouping of people's names
  • Addresses
  • Body content of emails

It operates on sending and receiving emails.

Inference The tool is a client-side Outlook add-in that uses Microsoft’s Office.js API for integration, with some AI-like functionality inferred from the use of Codex in development.

Back to contents

Traction & Maturity Signals

The project was submitted to a hackathon (OpenAI 2026), suggesting it is early-stage. The author states:

  • It was built by one person
  • It handles about 25,000 emails
  • It runs fast even at that volume
  • It’s not yet marketed or sold

There is no evidence of revenue, customers, user adoption or product-market fit.

Inference No traction or maturity signals are evident beyond the developer's own use and internal testing.

Back to contents

Competitive Context

The author mentions a legacy system called Mail Manager (ten years old) that they replaced. They also reference proprietary systems like Synergy as competitors, which allegedly locked users in and prevented access to original emails.

No other direct competitors or market analysis is provided.

Inference The competitive landscape includes older, expensive systems and potentially proprietary tools, but no clear market positioning or competitive differentiation beyond avoiding vendor lock-in.

Back to contents

Key Risks & Red Flags

  • Single developer: The entire project was built by one person (Ben B), raising questions about scalability and long-term maintenance.
  • Unverified claims: All functionality is self-reported without independent validation or data.
  • Technical limitations: Office.js integration is described as extremely difficult, which may limit performance or future development.
  • No commercial traction: No evidence of users, revenue, or market demand beyond the developer’s own use case.
  • Hackathon origin: The project was built for a hackathon, suggesting it is experimental and not yet mature for commercial deployment.

Back to contents

Diligence Questions To Ask The Founders

  1. What specific email volume or project count has been tested with SortaSmart?
  2. Has the tool been used by any third parties beyond the developer?
  3. How does the system handle data privacy, especially in enterprise environments?
  4. What are the actual technical limitations of Office.js that impact performance or scalability?
  5. Is there a plan to monetize this tool, and if so, what is the pricing model?
  6. What features are planned for future development beyond email filing?

Back to contents

Investment/Partnership Verdict

Not evidenced.

The description provides no evidence of revenue, customers, traction, or validated market demand. The project appears to be a personal solution built in a hackathon environment with no commercial validation. It is unclear whether the tool has moved beyond prototype stage or been adopted by any users outside of its creator.

Inference This is an unproven concept with no demonstrated commercial viability or product-market fit. Any investment or partnership would require further evidence of traction, user validation and scalability.

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.