AceGenie

I’m building AceGenie to answer a simple question: What should I study next?

I'm building AceGenie, a test-prep platform currently focused on JEE and NEET.

The idea came from a pretty simple problem:

Mock tests tell students what happened. They don't always tell them what to do next.

You finish a test and get a score, rank, correct answers and incorrect answers.

Then comes the harder part:

• Which chapter is actually weak?

• Is this a one-off bad test or a recurring problem?

• Which topics keep costing marks?

• Should I revise or take another mock?

• What should I spend my next hour studying?

Students often end up answering these questions manually through spreadsheets, notebooks, or simply trying to remember what went wrong.

That's what we're trying to solve with AceGenie.

The core loop

Take a test → understand performance → identify weak topics → revise → test again

AceGenie tracks performance across chapters and topics over multiple attempts, so students can see patterns instead of treating every mock as an isolated score.

The product currently includes:

• Adaptive mock tests

• Quick drills

• Topic tests

• Timed sprints

• PYQ papers

• AI doubt solver

• Formula sheets

• 3D flashcards

• Topic Scorecard

• Mistake Notebook

• Favorites

• Analytics

• Daily dashboard

We're also taking a real-paper-first approach to the question system. At least 80% of every paper comes from a curated bank extracted from actual exam PDFs. AI is used where there are genuine gaps, rather than generating the entire test.

One thing we're intentionally doing differently on the business side:

Analytics stay free.

Paid plans increase the number of papers a student can attempt rather than putting deeper performance analysis behind a paywall.

We're currently focused on JEE and NEET, and the product is live.

Right now, I'm trying to figure out whether we're solving the right problem and, more importantly, which parts of the analysis students actually find useful after taking a test.

I'd love feedback from other founders, students, or anyone who's built products around education, testing, or analytics.

What do you currently do after finishing a mock test?

Do you maintain a mistake notebook? Track chapters manually? Use a spreadsheet? Or just move on to the next paper?

AceGenie: https://acegenie.ai

The primary product promise we're building toward is simple:

Know what to fix after every test.

AgenticGenie