When people look at climate-tech from the outside, they often focus on the visible parts: the product, the pitch, the website, the demo, or the technical stack. But the deeper change often happens earlier. It happens in how you think, how you frame problems, how you evaluate opportunities, and how you begin to see yourself not only as a builder, but as a founder. For me, Carbon13 became an important part of that shift.

Before joining Carbon13, I already had years of experience in geospatial systems, drought monitoring, environmental data, and technical product building. I had worked on meaningful projects, built complex systems, and spent a long time close to real-world climate and drought problems. But there is a difference between building strong technical solutions and building ventures.

That difference became much clearer to me through Carbon13.

Moving From Technical Capability to Venture Thinking

One of the most valuable things Carbon13 changed for me was the way I framed my own work.

Before that, much of my thinking was still naturally shaped by delivery, implementation, technical architecture, and applied problem solving. Those things remain important, and they are still part of how I work. But Carbon13 pushed me to think in a broader and more entrepreneurial way.

Instead of asking only whether something could be built, I found myself asking different questions:

Who is this really for?
What urgent problem does it solve?
Why now?
Where is the market gap?
What makes this venture scalable?
Why would someone choose this instead of doing nothing?

Those are founder questions, not just builder questions.

That shift matters because climate-tech needs more than technical skill. It also needs product judgment, timing, business clarity, and a better understanding of how innovation moves from idea to company.

Why Cambridge Was the Right Environment for That Shift

Cambridge has a particular kind of energy when it comes to science, deep tech, climate, and entrepreneurship. It brings together people who are technically serious, intellectually ambitious, and often motivated by large real-world problems. For climate-tech, that combination is powerful.

Being in that environment made a difference to me.

It did not just provide proximity to startups or innovation in an abstract sense. It created a context where venture building felt more tangible, more immediate, and more worth pursuing deliberately. It made it easier to see that climate-tech is not only about research or implementation. It is also about creating companies and products that can survive, grow, and matter.

Carbon13 amplified that effect by creating a focused founder environment inside that broader Cambridge ecosystem.

Carbon13 as a Founder Environment

What made Carbon13 important for me was not simply that it was a programme about climate. It was that it was a venture-building environment with climate at the centre.

That is an important distinction.

There are many technical communities where you can learn tools, discuss infrastructure, or go deeper into engineering topics. There are also many climate communities where people talk about urgency, impact, and mission. Carbon13 brought together a different combination: climate ambition with startup discipline.

That combination forced a more complete kind of thinking.

You could not stay only in the comfort of technical excellence. You had to think about venture logic, market pain, user need, business model, team dynamics, positioning, and the practical reality of building something people would actually adopt.

That helped move me further away from the mindset of a solo technical builder and closer to the mindset of a founder operating inside an ecosystem.

It Changed How I Think About Problems

Another important change was how I think about problem selection.

Before, I often focused on whether a technical solution was interesting, elegant, or useful. Carbon13 pushed me to focus much more sharply on whether the problem itself was painful enough, clear enough, and important enough to justify venture-scale effort.

That sounds simple, but it changes everything.

A founder cannot only fall in love with the solution. A founder has to be much more honest about the problem. Is it real? Is it costly? Is it urgent? Is there willingness to adopt a better approach? Is the current market actually failing in a meaningful way?

This way of thinking has influenced how I now talk about products like Drought.UK and Climingo. It has helped me move from describing technical features toward articulating why the problem exists, why the current alternatives are insufficient, and why a better product should exist.

That is one of the most useful founder habits I took from the experience.

It Made Entrepreneurship Feel More Intentional

There is also a psychological difference between building something on your own and building something within a founder programme.

On your own, it is easy to remain partly in builder mode. You can keep refining, experimenting, and improving without fully stepping into founder identity. You can stay close to the technical layer because that is where you feel strongest.

A programme like Carbon13 changes that.

It places you in an environment where venture creation is expected, discussed, and normalised. You are surrounded by people thinking about startups, teams, investment, market direction, and climate impact in a more structured way. That creates pressure, but also clarity.

For me, that made entrepreneurship feel less like a side possibility and more like a deliberate direction.

It pushed me to take my own venture ambitions more seriously.

Team, Conversations, and Founder Maturity

Another thing Carbon13 changed was the quality of conversations around the work.

When you are mostly in technical communities, the conversation often stays close to implementation: architecture, stack choices, performance, integration, and engineering trade-offs. Those conversations are useful, but they are incomplete if your real goal is venture building.

In a founder environment, the conversation widens.

You start talking more about user pain, adoption risk, trust, differentiation, commercial pathways, founder-market fit, and long-term positioning. You start getting feedback that is not only about whether the product works, but whether the venture makes sense.

That kind of feedback helps mature both the idea and the founder.

It also helps you become more comfortable discussing your work in the language of value creation rather than only technical execution. That has been an important shift for me, especially because my background is deeply technical and product-led.

Carbon13 and the Transition From Projects to Ventures

A major theme in my own journey has been the move from project-based work to venture building.

I spent years working on drought and geospatial systems for international organisations and public-sector programmes. That experience gave me technical depth and domain credibility, but it also made me aware of a larger pattern: many important systems existed as projects, while too few became lasting, reusable, and accessible products.

Carbon13 helped me sharpen that insight.

It gave me a stronger framework for turning repeated project pain points into venture opportunities. It helped me think not just about what had been built before, but about what still needed to exist as a company, as a platform, or as a product with its own long-term path.

That is a major reason why I now describe my direction much more clearly in terms of climate-tech ventures, not only technical work.

Why This Matters for Climingo and My Broader Direction

This shift has been especially relevant for Climingo, where the challenge is not only technical but market-facing.

The problem Climingo is trying to solve sits in a space between weather and climate data providers, procurement decisions, benchmarking, and trust. That kind of venture requires more than technical credibility. It requires ecosystem understanding, founder discipline, and a better ability to define the real market gap.

Carbon13 helped strengthen that mode of thinking.

More broadly, it also changed how I think about my role in climate-tech. I do not want to only contribute technical systems to other initiatives. I want to help build ventures and products that define their own direction, respond to real market problems, and create lasting value in areas like drought, climate intelligence, and geospatial decision support.

It Changed How I Present My Work

One more subtle but important shift is how I present what I do.

A deeply technical background can sometimes lead you to explain everything through stack, architecture, and implementation detail. That can be useful in engineering circles, but it can hide the larger entrepreneurial story.

Carbon13 helped me pull that story forward.

It encouraged me to articulate not only what I have built, but why it matters, who it serves, what market gap it addresses, and what kind of company or platform it could become. That has influenced how I now write, pitch, and frame my work publicly.

This matters because founder identity is not only built through what you create. It is also built through how clearly you explain your direction.

What Carbon13 Did Not Change

It is also worth saying what Carbon13 did not change.

It did not replace the technical foundation of my work. I still care deeply about drought systems, geospatial platforms, data infrastructure, H3, DuckDB, forecasting, and climate-risk tools. Those remain core strengths and interests.

What changed was the layer above them.

Carbon13 helped me see those technical capabilities less as endpoints and more as ingredients for venture creation. It pushed me to ask how those capabilities could support products, companies, and markets rather than only projects or technical outputs.

That distinction has stayed with me.

What I Carry Forward

The most important thing I carry forward from Carbon13 is probably this: climate-tech entrepreneurship needs both substance and structure.

Substance means real domain knowledge, technical credibility, and a meaningful problem worth solving. Structure means venture discipline, founder clarity, better problem framing, and the willingness to think beyond the build itself.

For me, Carbon13 helped connect those two.

It helped me feel more embedded in venture building, more confident in founder language, and more deliberate about the kind of climate-tech work I want to lead from here.

Closing Thoughts

Building climate-tech in Cambridge has been important to me not only because of the city’s wider innovation ecosystem, but because Carbon13 helped turn that environment into something more personal and more directional.

It helped me shift from technical capability toward venture thinking. It helped me frame problems more sharply, speak more clearly about market gaps, and take entrepreneurship more seriously as a long-term path.

Most of all, it helped me see that the kind of work I want to build is not just technical, and not just climate-related. It is founder-led, product-driven, and deeply connected to real-world climate problems that still need better tools.

That change in perspective has stayed with me.

And it will continue to shape the ventures I build next.