Five steps from a problem to its solution.

Help me design and build a first working prototype for this problem in India.

Problem: Train passengers in India can't tell how likely their waitlisted ticket is to be confirmed.
Who it hurts: People booking Indian Railways tickets who get a waiting-list number instead of a confirmed berth.
The moment it hurts: Deciding at booking whether to hold a waitlisted ticket, book another train or find another way to travel.
What people do today: Passengers look at the waiting-list number alone, though the waitlist type and quota change how likely it is to clear.
Why it is still unsolved: The waitlist codes stand for different quotas and pools of seats, and how they move depends on cancellations and quota release, which passengers cannot see.
What solved looks like: A free checker where a passenger enters train, class, date, station pair and waitlist code and number, and gets a plain likelihood of confirmation with the reason, built from public rules and, with consent, crowd-reported outcomes.
Where: India

First, list what you would need to learn from the people affected before building, as interview questions.
Then propose the simplest version that would help, the screens or messages it needs, and the data it would use.
Keep it cheap to run, accessible, and respectful of people's privacy. Flag anything you are unsure about instead of guessing.