Five steps from a problem to its solution.

Help me design and build a first working prototype for this problem in Chennai, Tamil Nadu, India.

Problem: Chennai residents facing repeated power cuts can't see whether their local transformer is overloaded or when it will be upgraded.
Who it hurts: Households in older Chennai neighbourhoods such as Egmore, where apartments and offices have replaced independent houses on the same transformer.
The moment it hurts: The power goes off again for hours, the helpline sends a technician who replaces a cable, and the same fault returns days later.
What people do today: Residents call the helpline and send representations asking for a new transformer, without knowing its load or where their request stands.
Why it is still unsolved: Transformer load and upgrade decisions are tracked inside the utility, consumers don't know their transformer's capacity, and approvals and tenders take months with no public status.
What solved looks like: A neighbourhood outage log where residents record each cut, grouped by transformer, that turns repeated faults into a dated record to send to the executive engineer, and shows how long the request has been pending against the 90-day standard.
Where: Chennai, Tamil Nadu, 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.