Two People, One Capability — Summary

Arjun checks the weather by reading the sky, then checks his phone, because the phone is what the buyer will cite about the price. He farms four acres of cotton in Warangal district. His brother Ravi left for Hyderabad at nineteen and now works in enterprise software in HITEC City, summarizing contracts and drafting emails with free AI tools that were built for someone like him.

Hand them the same AI and it becomes two different things. For Ravi, it folds into a life already saturated with capable tools, answering in fluent English about problems the system was trained to understand. For Arjun, it answers in textbook Telugu that is technically correct and subtly wrong, knows agriculture the way a university knows it rather than the way a farmer does, and assumes connectivity his village has only sometimes. If the tool reaches him in his language, for his crop, on his signal, it delivers something real. If it does not, it delivers nothing.

The difference is not a gradient. For the person the tool was built for, value diminishes smoothly. For the person it was not, it vanishes. A tool that is eighty percent of what Ravi needs is still useful. A tool that is eighty percent of what Arjun needs, where the missing twenty is the language and the crop and the network, is a brick. The thresholds differ because the lives differ, and below Arjun’s threshold the value does not shrink. It drops off a cliff. The cliff is not anyone’s cruelty. It is what happens when capability is built by people who have to justify the cost to someone, and the someone is always closer to Ravi than to Arjun.