Five steps from a problem to its solution.

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

Problem: Households in Delhi can't easily tell what they must do, or by when, to keep their electricity subsidy now that Aadhaar is mandatory.
Who it hurts: Domestic power consumers across Delhi's five distribution areas, especially tenants, older people and families whose bill is in someone else's name.
The moment it hurts: Hearing that the subsidy now needs Aadhaar, and not knowing whether an existing connection is already covered, where to submit the number, or what happens if they don't.
What people do today: The rule sits in a Power Department notification; consumers depend on their discom and word of mouth to learn about it, with no single place that confirms whether their own connection is linked.
Why it is still unsolved: The subsidy runs through five separate discoms, and the notification sets no deadline or separate procedure for people who already receive the benefit, so the steps differ by provider and stay unclear.
What solved looks like: A plain-language checker where a Delhi consumer picks their discom, enters their account number, and learns whether Aadhaar is linked for the subsidy, how to link it (or use an Aadhaar Enrolment ID), and where to get help, with reminders if a deadline is announced.
Where: New Delhi, Delhi, 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.