Five steps from a problem to its solution.

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

Problem: Pregnant women in Gujarat lose maternity benefits to document mismatches and rejected applications they can't see the reason for.
Who it hurts: Pregnant women, many in tribal districts such as Dahod, Panchmahal, Sabarkantha and Banaskantha, and the ASHA, ANM and Anganwadi workers who file their applications.
The moment it hurts: An application under PMMVY or JSY is rejected, or stalls, because of an outdated Aadhaar, a bank account problem or a name spelled differently on two documents.
What people do today: Frontline workers fix problems case by case, between OTP failures, poor connectivity and server downtime, and rejections come without a clear reason.
Why it is still unsolved: Eligibility depends on several documents matching each other, and the online process does not show women or workers why an application failed or how to fix it.
What solved looks like: A pre-check for frontline workers, offline-capable, that compares a woman's Aadhaar, bank and other document details before filing, flags mismatches with the exact fix, and keeps a simple record of each application's status and any rejection reason.
Where: Dahod, Gujarat, 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.