Recognition can be encouraging, but for me it also creates a useful moment for reflection. Being associated with Geo100 is not only something I value personally. It also makes me think more clearly about the kind of work I want to build, the kind of founder I want to become, and the kind of climate-tech platforms I believe are still missing.

Over the years, my work has moved across geospatial engineering, drought monitoring, environmental data systems, and decision-support tools. I have worked on projects with international organisations, public-sector programmes, and technically demanding climate and geospatial workflows. That experience gave me a strong technical foundation, but it also pushed me toward a larger question.

What should all of this experience lead to?

For me, the answer is increasingly clear. I do not only want to contribute to climate-tech. I want to build climate-tech ventures and products that are genuinely useful, scalable, and relevant in the real world.

Recognition Matters Most When It Clarifies Direction

One of the most valuable things about recognition is that it can act as a mirror. It makes you step back and ask what people are really seeing in your work.

Are they seeing technical competence?
Are they seeing project delivery?
Are they seeing innovation?
Are they seeing leadership?
Are they seeing founder potential?

These questions matter because they shape the direction you choose next.

For me, recognition is most meaningful when it reinforces not only what I have done, but what I want to build from here. I want my work to be seen not simply as a series of technical outputs, but as part of a broader effort to create better climate-tech products and better geospatial platforms for real users.

That means building with more intention around product, usability, vision, and long-term value.

From Technical Work to Founder Work

My background is deeply technical. I care about geospatial systems, drought indicators, environmental data pipelines, spatial indexing, analytics, and modern infrastructure. Those things are still central to how I think and how I build.

But over time, I have become more interested in what sits beyond the technical layer.

I have become more interested in questions like:

Who is this product really for?
What decision does it help someone make?
Why is the current market not serving that need well enough?
What would it take to build something better?
How do we turn strong technical capability into something that people actually use?

That shift is important to me because it represents the move from technical work to founder work.

Technical work asks whether something can be built.
Founder work asks whether something should be built, who it serves, how it evolves, and why it matters.

That is the direction I want to keep moving toward.

The Kind of Climate-Tech I Want to Build

The kind of climate-tech I want to build is practical, decision-oriented, and grounded in real-world use.

I am less interested in building technology for its own sake. I am more interested in building platforms that reduce friction between data and action. In climate and environmental work, that gap remains large. Data may exist, models may be sophisticated, and visualisations may be impressive, but many users still struggle to turn that information into confident decisions.

That is where I see the opportunity.

I want to build products that make complex environmental data easier to interpret, easier to explore, and easier to use in operational settings. That includes work around drought, climate risk, weather intelligence, spatial decision support, and market-facing platforms that help users navigate uncertainty more clearly.

In simple terms, I want to build products that do not stop at showing information. I want to build products that help people think better, plan better, and act earlier.

Why Geospatial Thinking Still Matters

Geospatial technology remains at the centre of my thinking, not as an isolated technical field, but as a powerful way to structure climate intelligence.

So many climate and environmental decisions are spatial by nature. Risk is not evenly distributed. Drought does not affect every place the same way. Forecast value changes by geography. Infrastructure exposure changes by location. Agricultural conditions vary across landscapes. Water stress is local long before it becomes a headline.

That is one reason geospatial thinking remains so important in the work I want to lead.

I believe some of the most useful climate-tech products of the coming years will be built by combining climate intelligence with strong spatial reasoning. Not just maps for display, but spatial products that help users understand local variation, compare nearby conditions, and interpret what environmental change means in context.

That perspective shapes how I think about both current ventures and future ones.

Building Products, Not Just Systems

One lesson that has become more important to me over time is the difference between systems and products.

A system can be technically strong, useful, and important. But a product goes further. A product has a clearer relationship with users, a stronger sense of continuity, and a better chance of growing into something scalable and widely useful.

I want to build products.

That means thinking beyond delivery and toward adoption. Beyond implementation and toward usability. Beyond functionality and toward identity.

This is a significant part of how I now see my work. I do not want to only contribute technical capability to other organisations’ systems. I want to lead the creation of ventures and platforms with their own vision, their own users, and their own long-term path.

That is part of what platforms like Global Drought Map, Drought.UK, and Climingo represent for me. They are not only outputs. They are steps toward the kind of founder-led climate-tech work I want to keep building.

The Kind of Company I Want to Be Part Of

I also think a lot about the kind of company I want to help create.

I want to build or lead a company that is technically credible, but not trapped in technical language. A company that understands data deeply, but does not assume the user should have to do the same. A company that treats design, interpretation, and usability as core parts of climate-tech value rather than secondary polish.

I want to work in a way that combines rigorous infrastructure with real-world accessibility.

That means building a company that can speak to both technical and non-technical audiences. A company that understands the quality of the data pipeline, but also understands the importance of trust, clarity, and product experience. A company that is modern in its engineering choices, but practical in how it solves problems.

Most of all, I want to be part of building a company whose products make difficult climate and environmental questions easier to navigate.

Climate-Tech Needs Better Product Leadership

One reason I feel strongly about this direction is that climate-tech still has many product gaps.

There is no shortage of important datasets. There is no shortage of scientific work. There is no shortage of climate language, models, and reporting. But there is still a shortage of tools that genuinely help people move from information to action without unnecessary friction.

That is where product leadership matters.

Climate-tech needs more founders and teams who are willing to focus not only on technical novelty, but on usability, clarity, and trust. It needs products that respect scientific depth without overwhelming the user. It needs platforms that connect specialist knowledge with practical decision-making.

This is the kind of work I want to lead. Not climate-tech that looks sophisticated from a distance, but climate-tech that is actually useful when someone needs to make a real choice.

The Role of Vision in Founder Work

As I think about the future, I have become more aware that founder work is partly about choosing what kind of problems you want to spend years with.

For me, those problems are increasingly clear.

I care about drought and water risk.
I care about local climate interpretation.
I care about spatial decision support.
I care about climate-data usability.
I care about market gaps where important information exists but usable products do not.

These themes connect much of the work I have done so far, but they also point toward the work I want to do next.

Founder vision is not only about ambition. It is also about consistency. It is about being clear on what kind of value you want to create and why. Recognition becomes more useful when it helps sharpen that clarity.

What I Want My Work to Stand For

When I look ahead, I want my work to stand for a few things.

I want it to stand for technical depth, but not technical isolation.
I want it to stand for geospatial thinking that leads to better decisions.
I want it to stand for climate-tech products that are accessible and credible.
I want it to stand for venture-building that begins with real problems, not just interesting tools.
And I want it to stand for building platforms that people can return to because they are genuinely useful.

This matters to me because I do not want to build products that are briefly interesting and quickly forgotten. I want to build products that earn trust over time.

Looking Ahead

The next stage of my work is less about proving that I can build technical systems and more about building ventures that bring those capabilities together in a stronger product form.

That means continuing to develop climate-tech platforms with clearer market relevance. It means refining products around actual user pain points. It means balancing technical depth with founder discipline. And it means thinking carefully about where geospatial innovation can create lasting value in climate resilience, drought intelligence, and environmental decision support.

I see this as a long-term direction, not a short-term experiment.

Recognition is encouraging, but the more important question is what comes next. For me, what comes next is deeper founder work, stronger product thinking, and a more deliberate effort to build climate-tech ventures that can grow, matter, and endure.

Closing Thoughts

Geo100 is meaningful to me not only because it reflects past work, but because it connects to future direction.

It reminds me that the work I want to do is not only about technology. It is about leadership, product vision, and building better climate-tech platforms for the years ahead. It is about creating ventures that combine geospatial intelligence, modern infrastructure, and real usability in ways that matter to real users.

That is the kind of work I want to build.

And that is the kind of founder I want to become.