The search that led to World Blood Organisation
An urgent search for a blood donor during engineering changed how Amarnath Maddireddy and I thought about building useful technology.
During engineering at KL University, a professor’s brother had a serious accident and urgently needed A-negative blood. I visited blood banks in Vijayawada and contacted potential donors. Over roughly twenty days of hospitalisation, we helped identify around sixteen units of blood.
The experience stayed with me because the difficulty was so specific. People wanted to help, but finding a suitable donor nearby, at the time someone needed one, involved a great deal of searching and coordination.
Understanding the gap between people
A list of names is not the same as a connection that works. Someone has to discover the list, reach the right person, explain the need, and find out whether help is possible. When time matters, every unclear step becomes part of the problem.
That gap led Amarnath Maddireddy and me to create World Blood Organisation, a free platform intended to connect patients with registered donors nearby. We were engineering classmates. We also started our first company, D4Devs, in Guntur during our second year at KL University.
The important shift in my thinking was from asking what we could build to asking which part of the process needed to become easier. A platform could help people discover and contact one another. It still had to fit the circumstances of the people using it.
A working application is a beginning
It is easy to measure progress through screens completed and features released. Those are necessary measures of engineering work. They do not tell the whole story of whether a service helps someone.
For a person looking for help, the questions are more direct. Can I understand what to do? Can I find the relevant information? What happens if the first attempt does not work? A product needs to account for the moments after someone presses a button.
This experience also taught me to be careful about the promises a platform makes. Connecting people is a useful contribution; it does not make every outcome something the software can control. Clear communication about the platform’s role is part of serving people responsibly.
The same habit appears in other businesses
Years later, the starting points for other products have often been close to home. My father and brother’s shops exposed the difficulty of managing stock across shops and godowns with accounting tools that demand training and a computer. That helped shape Dukanam.
Conversations with employees about their PG accommodation helped shape OnlyPGs. Some places had problems with food and maintenance. Others were good but difficult to discover. The opportunity was to make useful information visible to people who needed it.
The industries are different. The habit is consistent: spend time with the people doing the work or living with the problem, understand the steps they take, and identify where a practical intervention could help.
Keep the original question in view
As a product develops, there are more opinions about what it should become. New features, new markets, and new possibilities can all be worth considering. I find it useful to return to the original difficulty.
Who was struggling? What were they trying to do? What should become easier because this exists?
World Blood Organisation helped establish that way of thinking for me. The question remains useful whether we are building a community platform, business software, or a service for a small team.