← Back to the problem

The builder's path

Five steps from a problem to its solution.

For: Kochi can't tell which of its public taps are used, working or legal, so it pays for all of them and risks cutting off families who rely on one.

“The true creator is necessity, which is the mother of our invention.”
Plato · Republic II, 369c (tr. B. Jowett)

Routes to a solution

Six ways to take this forward

Each route is a different kind of journey, with real people and organisations to contact at each step, starting with those in Kerala.

  1. Step 1

    Join an incubator or startup mission

    They connect you to schemes and officials.

    • Kerala Startup Mission ↗

      Kerala's startup agency: grants, incubation and government procurement routes.

    • DST NIDHI ↗

      Department of Science and Technology support from idea to startup, through technology business incubators.

    • NASSCOM ↗

      The tech industry body; startup programmes and a route to industry partners.

    • Villgro ↗

      Incubator for social enterprises in health, agriculture and livelihoods.

  2. Step 2

    Win a seed grant

    Prove the idea works with a small, funded prototype.

  3. Step 3

    Pilot with a public body

    A district, city or department tries it with real people.

What this problem needs

Ideas, sources and tools for this problem, from first interviews to funding.

  • Maps
  • Mobile
  • Forms and documents
  • Open data

Ideas to explore

  • Idea 1Tap survey appA phone form for survey teams: photo, GPS, working or not, metered or not, and roughly how many households use it, synced to one shared map.
  • Idea 2Resident flagLet residents mark a tap as one their family depends on, by phone or WhatsApp, so it is reviewed before removal.

Specific to this problem

Talk to first

Starter prompt

Built from this problem's brief. Paste it into Claude or any AI assistant.

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

Problem: Kochi can't tell which of its public taps are used, working or legal, so it pays for all of them and risks cutting off families who rely on one.
Who it hurts: Kochi Corporation, which pays the water bill for public taps, and families in colonies without household connections who depend on them.
The moment it hurts: Deciding which taps to keep or remove, without a list of where they are, whether they work or who uses them.
What people do today: The Corporation pays a monthly charge based on a tap count from the Kerala Water Authority, and is now sending health inspectors and councillors to survey each division.
Why it is still unsolved: No one holds a shared, current map of the taps: the water authority has not answered the Corporation's requests and the new private operator has not collected tap data.
What solved looks like: An open, geo-tagged register of every public tap in Kochi, filled in by survey teams and residents, showing whether each tap works, is metered and which households rely on it, so no tap a family needs is removed.
Where: Kochi, Kerala, 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.
  1. Understand it

    Talk to the people who live it before you build.

    “The unexamined life is not worth living.”

    ὁ δὲ ἀνεξέταστος βίος οὐ βιωτὸς ἀνθρώπῳ

    Socrates · Plato, Apology 38a
  2. Prototype with AI

    Get a working version in front of people fast.

    Using AI is not cheating. Every tool carries the work of the people who made it, and using it well is how knowledge has always moved forward. The thinking, the care for the people who live the problem, and the judgement are still yours.

    “The Analytical Engine weaves algebraical patterns just as the Jacquard-loom weaves flowers and leaves.”
    Ada Lovelace · Notes on Menabrea's Sketch of the Analytical Engine, Note A (1843)
  3. Find the data

    Open data that fits this problem.

    “When you know a thing, to hold that you know it; and when you do not know a thing, to allow that you do not know it: this is knowledge.”
    Confucius · Analects 2.17 (tr. J. Legge)
  4. Build it

    Tools matched to what this problem needs.

    “The things we have to learn before we can do them, we learn by doing them.”
    Aristotle · Nicomachean Ethics II.1 (tr. W. D. Ross)
  5. Launch and get support

    Ship it responsibly, and find help and funding.

    “Your right is to the work alone, never to its fruits.”

    कर्मण्येवाधिकारस्ते मा फलेषु कदाचन

    karmaṇy evādhikāras te mā phaleṣu kadācana

    Bhagavad Gītā · 2.47

Kit written for this problem from its brief; every link was checked. Links go to each provider's own site. Zetema is not paid for any listing.