OpenAI 2026 hackathon

Writic

Turn your idea into a cited, journal aligned draft. Validate direction and spot risks before months of work.

Solo project by AT2018cow Song · 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,743 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

Writic is a self-reported AI-powered tool for academic researchers to generate early-stage paper prototypes aligned with target journals, incorporating literature review, traceable citations, and structured output. The author states it was built using Codex, GPT, Gemini, Supabase, Google Cloud, and Cloudflare. It was submitted to the OpenAI 2026 hackathon.

What changed: The project is described as a prototype launched in private beta, with early traction from researchers across disciplines. The author states that work supported by Writic has been accepted by conferences, research forums, and peer-reviewed journals. The team plans to expand functionality with features like Risk Radar, Validation Roadmap, and shared workspaces.

Key open question: Is there evidence of real user adoption or revenue generation beyond the private beta phase? The description does not provide any data on actual usage, customer base, pricing, or monetization.

Back to contents

What The Product Actually Is

The description states that Writic "turns a research idea into an early paper prototype with relevant literature, traceable citations, and a structure aligned with a target journal." It supports researchers in refining their ideas as they evolve, with the goal of helping them identify research gaps, evaluate feasibility, align with advisors, and choose publication direction.

Inference: The tool appears to be an AI-assisted writing platform for academic research, integrating natural language processing (NLP) tools like GPT and Gemini to generate structured content aligned with journal requirements. It is not evident whether Writic functions as a standalone application or integrates into existing workflows.

Back to contents

Positioning & Claim Evolution

The author states that Writic was inspired by the problem of late writing in academic research, where decisions are made before writing begins. The tool aims to make writing useful from the start of a project.

Inference: Writic positions itself as an early-stage research support tool, not a full writing assistant or editor. It is described as helping researchers validate direction and spot risks before investing months of work.

Back to contents

Target Customer & ICP

The description states that Writic was launched in private beta and attracted researchers from "several disciplines." The author also notes that the team learned researchers value early clarity over word count, and need help identifying research gaps, evaluating feasibility, aligning with advisors, and choosing publication direction.

Inference: The target customer is likely academic researchers, particularly those working on projects that require early-stage planning and journal alignment. The ICP appears to be researchers in disciplines where early validation and structured writing are critical.

Back to contents

Business Model & Pricing Evidence

The description states that Writic is in private beta and that the team is "continuing to test our pricing model." No specific pricing details, revenue streams, or monetization strategy are provided.

Inference: There is no evidence of a defined business model or pricing structure. The project appears to be in an early testing phase with no commercial traction.

Back to contents

Technical & Delivery Signals

The author states that Writic was built using Codex, GPT, Gemini, Supabase, Google Cloud, and Cloudflare. It supports AI features, database management, infrastructure, and application delivery.

Inference: The tool is built on a stack that includes generative AI models (GPT, Gemini), cloud infrastructure (Google Cloud), and backend services (Supabase). This suggests a modern, cloud-native approach to delivering AI-powered academic tools.

Back to contents

Traction & Maturity Signals

The description states that Writic was launched in private beta and attracted researchers from several disciplines. The author also claims that work supported by Writic has been accepted by conferences, research forums, and peer-reviewed journals.

Inference: There is no evidence of actual user numbers, revenue, or adoption metrics beyond the private beta phase. The claim of acceptance by journals and conferences is self-reported and not independently verified.

Back to contents

Competitive Context

The description does not provide any information about competitors or the broader marketplace for academic writing tools or AI-assisted research platforms.

Inference: No competitive analysis is evident in the provided description. It is unclear whether Writic competes with existing academic writing tools, AI platforms, or research management systems.

Back to contents

Key Risks & Red Flags

  • No revenue or monetization evidence: The project is described as being in private beta and testing pricing, but no data on revenue or customer base is provided.
  • Unverified claims: The author states that work supported by Writic has been accepted by journals and conferences, but this is not independently verified.
  • Limited team size: Only one team member is mentioned (AT2018cow Song), which may limit execution capacity.
  • No product-market fit validation: There is no evidence of user feedback loops or iterative improvements beyond the beta phase.

Back to contents

Diligence Questions To Ask The Founders

  1. What specific metrics define success for Writic in its private beta phase?
  2. How many researchers are currently using Writic, and what is their retention rate?
  3. What is the current pricing model, and how has it evolved during the beta period?
  4. What are the main challenges with citation reliability and discipline-specific support that you've encountered?
  5. Are there any partnerships or institutional users beyond those in the private beta?
  6. How do you plan to scale beyond the current team size?

Back to contents

Investment/Partnership Verdict

Not evidenced: There is no evidence of revenue, customer traction, or commercial viability beyond the private beta phase. The project is described as a prototype with early user feedback and self-reported success in journal submissions, but no data on actual usage, monetization, or scalability is provided.

The description is self-reported and unverified. It does not contain any information about funding rounds, headcount, or commercial performance that would support an investment or partnership decision at this stage.

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.