
Acad AI
Know exactly what companies are hiring for instantly
I graduated October 13 2024, and almost for a year I hunted jobs, submitting well over 3000 job applications, appearing for over 40 interviews but still couldn't land a single one. And most of the time I got the same answer, "Your skill set isn't aligned with what your company needs at this moment" and this frustrated me like anything.
That's when an idea came to my mind, what if I could build something that could tell me the most in-demand skills in frontend at current market. I set out to build a simple page, that will just give me a list of skills and topics I needed to cover, to get hired in frontend. In about 16 hours of trial and error I built the first version of this and was extremely pleased with myself to have built something like this.
I told my friend about this and at first he didn't say anything, but then he told me to make it into a proper platform. He made me see that it wasn't such a unique problem that I faced. It was a very common issue faced by every student in tech out there. So lo and behold, Acad AI was born on September 22nd, 2025, about 2 weeks after my friend convinced me.
Since then we have had a steady increase of users, currently the platform has over 300 organic users. I didn't exactly have the budget to spend on marketing because I was footing the API costs of the platform while keeping the platform free.
Now the platform is open with a commercial launch after I introduced weekly learning resources, Hyper-personalization and AI mentor. The subscriptions are being localized, in the sense that I'm trying to make it into geo-pricing—a pricing depending on the country.
About
I was rejected for after submitting over 3000 job applications and that's how this project started. A way to know exactly what the most in-demand skills are in any domain so that people could land jobs easier.

2 Comments
Geo-pricing is the right call. One thing to watch: if you're relying on IP detection for country, users with VPN will game it. Better to tie it to the App Store country (Apple handles this natively via storefront).
Also the painful part hits later, when you need to update prices across 50+ countries at once, App Store Connect becomes a nightmare. Curious what stack you're using to manage the localization logic?
Congrats on the launch, looks solid. How are you currently thinking about acquiring early users and gathering feedback?