From Projects to Products: Why I’m Building Climate-Tech Ventures

For years, I worked on drought and geospatial systems for international organisations and public-sector programmes. Those experiences were valuable, but they also revealed a recurring pattern: powerful data existed, yet usable products were still missing. That realisation pushed me from project delivery toward venture building.

My professional path has been shaped by geospatial technology, climate data, drought monitoring, and decision-support systems. I spent years working on real-world problems where environmental data needed to be transformed into something useful for institutions, programmes, and decision-makers. That work gave me deep technical experience, but it also gave me something else: a clearer view of what was still not working.

Again and again, I saw the same gap.

The science was often strong. The datasets were often rich. The need was certainly real. But between the data and the decision, there was often a missing layer: usable products.

That gap is one of the main reasons I am now building climate-tech ventures.

What Project Work Taught Me

Working on climate and drought-related systems for organisations such as UNICEF, UNDP, and national-scale public programmes gave me direct experience with important and meaningful challenges.

These were not abstract problems. They involved drought risk, early warning, mapping, environmental monitoring, vulnerability, and the need to communicate conditions in ways that could support action. In those settings, geospatial systems were not just technical exercises. They were meant to help real institutions make better decisions.

That experience mattered a great deal to me. It helped me understand how climate data is gathered, processed, visualised, and interpreted in operational settings. It also showed me how much effort is often required to turn raw information into something decision-makers can actually use.

But just as importantly, it exposed a recurring limitation.

Many systems were built as projects. Fewer were built as products.

The Difference Between a Project and a Product

A project can be valuable, impactful, and technically strong. It can solve an immediate need for a specific client, institution, or programme. But a product is different.

A product is designed to live, evolve, and serve a broader group of users over time. It is not only a response to a one-time requirement. It is an ongoing tool shaped by usability, repeatability, scalability, and long-term relevance.

That distinction became increasingly important in my thinking.

I realised that many environmental and drought-related systems were still too dependent on one-off delivery models. They often served a narrow implementation need, but they did not always become accessible, reusable, or adaptable products in their own right. In some cases, the data was excellent but the interface was too technical. In others, the analysis was strong but the system was too hard to extend. Sometimes the result was useful to experts, but not especially usable for wider audiences.

That was the pattern I kept noticing: strong data, important need, incomplete product layer.

The Missing Product Layer in Climate-Tech

Climate-tech is often discussed in terms of models, sensors, forecasts, and scientific datasets. Those things matter enormously. But data alone is not the product.

In many parts of the climate and environmental space, the real bottleneck is no longer just whether information exists. The bigger question is whether that information can be turned into something usable, clear, and practical.

A platform that only specialists can navigate may still be technically impressive, but it leaves a large part of its potential unrealised. A dashboard that displays layers without helping users interpret them may still be useful, but it stops short of becoming a true decision-support product.

This is where my own motivation started to shift.

I became less interested in simply delivering technical outputs and more interested in building products that could stand on their own: tools with a clearer identity, a more defined audience, and a stronger connection between data and action.

What UNICEF, UNDP, and National Drought Work Revealed

My work across different countries and programmes helped me see that drought and climate-risk challenges often share a common structure, even when the geography is different.

In Madagascar, the context was different from Somalia. National-scale drought work in Turkey had its own structure, priorities, and institutional setting. But across these environments, I kept seeing similar product challenges:

Data was available, but interpretation remained difficult.
Monitoring existed, but accessibility was uneven.
Systems could support experts, but wider usability was still limited.
Important information was present, but product design often lagged behind.

These experiences shaped how I think today.

They did not push me away from climate and geospatial work. They pushed me deeper into it, but with a different goal. I did not want to stop at technical implementation. I wanted to help build the next layer: the venture-backed, product-oriented layer that makes climate intelligence more usable and more scalable.

Why Entrepreneurship Became the Next Step

At some point, I realised that the kind of systems I wanted to create would be difficult to pursue fully if I stayed only in project-delivery mode.

Projects are often defined by fixed scopes, fixed timelines, and institution-specific requirements. That model can produce valuable outcomes, but it does not always create the freedom needed to build broader products with their own long-term roadmap.

Entrepreneurship offered a different path.

It made it possible to think not just about delivery, but about product vision. Not just about technical implementation, but about market need, adoption, usability, and long-term relevance. It created room to ask bigger questions:

What kind of climate-tech tools are still missing?
What problems remain unsolved across organisations and sectors?
What could be built once and improved continuously, instead of rebuilt repeatedly in different project contexts?

That is the shift I have been making: from solving problems only inside projects to building products and ventures that can solve similar problems more broadly.

Building My Own Climate-Tech Platforms

That shift is reflected in the ventures and platforms I am building today.

Global Drought Map grew from the idea that drought information at global scale could be made more accessible, more interactive, and easier to explore through modern geospatial infrastructure.

Drought.UK came from a different but related insight: that drought in the UK is often underestimated, and that local drought interpretation remains weaker and less practical than it should be for many users.

Climingo emerged from another clear gap: organisations increasingly rely on weather and climate data providers, but comparing and selecting those providers is still harder and less transparent than it should be.

These are different products, but they come from the same broader direction. Each responds to a practical problem where strong data exists, but product quality, usability, or decision-readiness still needs improvement.

From Technical Builder to Venture Builder

My technical background remains a central part of how I work. I still care deeply about data pipelines, geospatial architecture, drought indicators, spatial indexing, and analytical systems. But I no longer see technology as the endpoint.

Technology is the enabler.

What matters more to me now is how that technical capability can support products that are useful, scalable, and relevant in the real world. That means thinking not only about how to process data, but also about how to shape user experience, platform direction, product-market fit, and long-term value.

In that sense, the journey from projects to products is not a rejection of technical work. It is an expansion of it.

It is the move from being only a system builder to becoming a venture builder.

Why This Matters in Climate-Tech

Climate-tech needs more than data pipelines and impressive models. It needs products that people can actually use.

That is especially true in areas such as drought, resilience, adaptation, environmental planning, and risk communication. These are spaces where the gap between technical possibility and practical usability is still very visible.

A product-oriented mindset can help close that gap. It forces clearer thinking around who the user is, what decision they are trying to make, what information they actually need, and how that information should be presented.

This is one of the reasons I believe climate-tech entrepreneurship matters so much. It creates space to move beyond isolated tools and one-off solutions toward products that can improve, scale, and reach broader audiences.

The Kind of Ventures I Want to Build

The ventures I want to build are not just about presenting environmental data. They are about making climate intelligence more understandable and more actionable.

I am especially interested in products that sit at the intersection of:

• climate risk
• geospatial analytics
• decision support
• usability
• scalable digital infrastructure

In practical terms, that means platforms that help users explore, compare, understand, and act. It means tools that reduce the distance between technical data and real-world use. It means building systems that are modern underneath, but accessible on the surface.

That is the direction I see for my work going forward.

Looking Back, and Looking Ahead

Looking back, I am grateful for the years I spent working on drought and geospatial systems in institutional and international contexts. Those experiences gave me technical depth, domain understanding, and a close view of how environmental intelligence works in practice.

But they also made something very clear to me: too many important systems still stop short of becoming products.

That insight changed the direction of my work.

It is why I now focus more deliberately on building ventures, not only delivering systems. It is why I think more about platform design, product usability, and scalable climate-tech infrastructure. And it is why I believe entrepreneurship is not separate from my past work, but a natural continuation of it.

Closing Thoughts

The journey from projects to products has been shaped by a simple but important lesson: powerful data is not enough on its own.

If climate and drought intelligence is going to make a bigger difference, it needs better product thinking around it. It needs ventures that can build, refine, and scale tools that connect technical capability with real-world use.

That is the path I am now following.

My earlier work taught me how these systems function. My current work is about building the kinds of climate-tech products I believe are still missing.

You can explore some of that work through Global Drought Map, Drought.UK, and Climingo.