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,770 place in the like-ranked listing is a tie-break inside that group, not a ranking.
Projects (log scale)
Likes on Devpost. ▲ marks this project's group.
Show the figures
| Likes | Projects | Share of archive |
|---|---|---|
| 0 | 5,592 | 71.2% |
| 1 | 1,758 | 22.4% |
| 2 | 285 | 3.6% |
| 3–4 | 132 | 1.7% |
| 5–9 | 75 | 1.0% |
| 10+ | 14 | 0.2% |
Executive Summary
What the company appears to be
The description states that yhteishaku.app is a tool for Finnish higher-education applicants to explore joint application programmes, review historical admission scores and applicant numbers, compare programs, and save options of interest. It was built by one developer (Miko Kortelainen) as an MVP for the OpenAI 2026 hackathon.
What changed
The author reports launching a public-facing site after building it in a hackathon context. The project evolved from a personal solution to a shared tool used by students and educators.
Single most important open question
Is there evidence of user traction or adoption beyond the initial developer’s use case, and what is the path to sustainable growth or monetization?
What The Product Actually Is
The description states that yhteishaku.app is a website where users can:
- View applicant numbers by programme and institution
- Compare two programmes
- Review admission score requirements from previous years
- Browse programmes available in the current or upcoming joint application
- Save and revisit programmes of interest
It is described as a centralized tool for people applying to Finnish higher education through the joint application system.
Evidence
- The author states the site helps applicants explore joint application programmes.
- Features are listed directly from the description.
Inference The product appears to be a data visualization and comparison tool, not a platform for submitting applications or managing user accounts beyond saving preferences.
Positioning & Claim Evolution
The author claims that yhteishaku.app was built to solve the problem of navigating multiple pages and complex reports when searching for admission score requirements and applicant numbers. It is positioned as a helpful tool for applicants who are unsure about what or where to study.
Evidence
- The author says they were frustrated with the existing process and decided to build a centralized site.
- The tagline: “A helpful tool for people applying the Finnish higher-education joint application for Universities.”
Inference The positioning is rooted in user pain points, not market demand or commercial traction. It is framed as a utility for students and educators rather than a scalable SaaS product.
Target Customer & ICP
The description states that yhteishaku.app is intended for:
- Prospective higher-education applicants in Finland
- Students using the joint application process
- Upper-secondary school staff who support students with the application process
Evidence
- The author mentions targeting people applying to Finnish higher education.
- Feedback from upper-secondary school staff is cited as a positive signal.
Inference The ICP appears to be narrow: Finnish high school students and educators involved in university admissions. No evidence of broader or international appeal.
Business Model & Pricing Evidence
There is no evidence in the description of any pricing, monetization strategy, or business model. The project was built as a hackathon submission and launched publicly without indication of paid features or revenue streams.
Evidence
- The author states it was built for public use.
- No mention of subscriptions, ads, or fees.
Inference The product is likely free to use, with no commercial model evident in the description.
Technical & Delivery Signals
The project was built using:
- Frontend: React, TypeScript, Chakra UI, Vike
- Backend: Go
- Data pipeline: AI tools (Codex), third-party data from Vipunen (EDUFI statistics service)
- Hosting/infrastructure: Cloudflare
Evidence
- The author describes the tech stack and development process.
- Data was transformed using Codex and converted into JSON for frontend use.
Inference The technical approach suggests a minimal viable product with data-driven functionality. No evidence of scaling, API integrations, or enterprise-grade infrastructure.
Traction & Maturity Signals
There is no evidence of user traction, adoption metrics, or growth indicators beyond the author’s own feedback and a few mentions of positive reactions from educators. The project was launched as part of a hackathon and has not been described as having reached a significant user base or revenue.
Evidence
- The author reports receiving positive feedback.
- Upper-secondary school staff said they plan to use it.
- No mention of users, usage statistics, or retention.
Inference The product is in an early stage with no measurable traction. It is not evident that the tool has been adopted widely or used at scale.
Competitive Context
There is no evidence of competitors mentioned or described in the project description. The author does not reference similar tools or platforms, nor does the description indicate a competitive landscape.
Evidence
- No competitor names, products, or market analysis provided.
Inference The competitive context is unknown. It is unclear whether this is a unique solution or if similar tools exist in Finland or elsewhere.
Key Risks & Red Flags
- Single-founder model: The project is built and maintained by one person (Miko Kortelainen), which raises questions about scalability, long-term maintenance, and team capacity.
- No monetization strategy: No evidence of a path to revenue or commercial viability.
- Dependency on third-party data sources: Reliance on Vipunen for data introduces risk if the source changes or becomes unavailable.
- Limited scope: The tool is narrowly focused on Finnish higher education, which may limit its long-term growth potential.
Inference The project lacks a clear path to commercialization and is heavily dependent on one individual’s effort. It also has limited appeal beyond its niche use case.
Diligence Questions To Ask The Founders
- How many users are actively using the platform, and how do you measure engagement?
- What is your plan for monetization or scaling beyond the current scope?
- Are there any legal or data access issues with relying on Vipunen for information?
- How do you intend to grow the user base beyond initial feedback from educators?
- What are the long-term plans for maintaining and updating the tool, especially as admission requirements change?
Investment/Partnership Verdict
The description states that yhteishaku.app is a tool built by one developer for Finnish applicants to higher education. It is not evident that it has reached any level of traction or commercial viability.
Evidence
- No revenue, customers, or adoption metrics are provided.
- The project was launched as part of a hackathon and lacks evidence of ongoing development or user growth.
Inference At this stage, the product is a personal solution with limited commercial potential. It would require significant additional development, traction, and a clear monetization strategy to be considered for investment or partnership.
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.