Created on 2026-02-02 15:36
Published on 2026-02-02 16:58
For Christmas, my wife received a bonsai tree. In the true nature of the gift, it has also brought me to time of contemplation on the next phases of Humanity Link....some small notes below.
For a long time, my default mode as a startup CEO was simple: survive, ship, repeat.
If you’ve built anything from scratch, you know the rhythm. You’re the product person, the salesperson, the customer support desk, and the ops lead. You’re trying to save money, get the product out, and keep a team moving forward while everything changes—priorities, timelines, staffing, expectations. Some weeks you’re building. Some weeks you’re selling. Some weeks you’re patching gaps at 11pm because there isn’t anyone else to do it.
In the early stage, that mindset isn’t a flaw. It’s necessary.
But if you stay there too long, it becomes a ceiling.
At some point you feel a shift—not because you suddenly “made it,” or raised a big round, or found stability. You feel it because you realize something uncomfortable:
You can’t build something that lasts with survival instincts alone.
In a typical startup, the cost of chaos is missed deadlines, churn, technical debt, and a tired team.
In humanitarian and social impact work, the cost can be human.
We’re living in a moment where technology can fundamentally reshape how we assist people in crisis. From AI-driven information systems to digital ID, secure cash delivery, early-warning tools, and cloud-based communication platforms, the capability exists—today—to move faster, reach further, and deliver aid with more accuracy than at any point in history.
But there’s a problem.
A huge portion of the non-profit and humanitarian sector either doesn’t know these tools exist, doesn’t know how to use them, or doesn’t have the technical capacity, funding structure, or internal culture to adopt them even if they do understand them.
The result is something I’ve seen repeatedly over two decades in emergencies:
Communities are ready. The technology is ready. But the system isn’t.
And when those three pieces aren’t aligned, people wait longer for the help they need.
That gap—the “capability-awareness” gap—is one of the biggest preventable barriers in humanitarian action today. It’s also exactly why we built Humanity Link: to help close the distance between what’s possible and what’s actually happening on the ground.
When you’re early, “lean” becomes a badge of honor. You stretch every euro. You do more yourself. You keep headcount low. You move fast.
Some of that is discipline. Some of it is survival. And some of it—if we’re honest—is fear.
Because it’s easier to keep carrying everything than to build systems that let other people carry it with you. It’s easier to stay in firefighter mode than to step back and design the structure.
But longevity asks a different question than runway:
Is this making the company stronger—or just cheaper?
Cheaper can keep you alive. Stronger is what keeps you around.
And in social impact, “around” matters. The sector doesn’t need another short-lived pilot. It needs tools that hold up under pressure—tools that still work when networks drop, when teams rotate, when crises evolve, and when accountability requirements tighten.
The shift I’m talking about is moving from “get it out the door” to “build it so it can carry weight.”
In our world, weight looks like:
crisis environments where conditions change daily
compliance and data protection that are non-negotiable
partners who don’t have engineering teams sitting around
donor reporting that demands traceability and proof
communities who deserve dignity, speed, and accuracy
Longevity is building a company and product that can operate inside that reality without requiring heroics every day.
Here are four ways that mindset shows up in practice.
If the company only works when you’re “on,” it’s not a company yet—it’s a constant rescue mission.
Longevity is when decisions don’t live in someone’s head, onboarding isn’t tribal knowledge, and support isn’t a fire drill. It’s when the product doesn’t break because one person took a week offline. It’s when the organization is resilient enough to absorb change without collapsing into chaos.
That isn’t bureaucracy. It’s durability.
A lot of social impact solutions die after the pilot—not because the concept was wrong, but because deployment was too hard to repeat.
Most non-profits don’t have dedicated engineers, solution architects, or data teams. Staff are stretched, often responding to multiple crises at once. If adopting your tool feels like “one more thing,” it won’t happen—even if the value is obvious.
Longevity means building for reality: modular components, clear integrations, simple deployment paths, and workflows that fit how non-profits actually operate.
We’ve seen this firsthand at Humanity Link supporting operations in places like Libya, Venezuela, and Ukraine. When organizations realize they don’t need a full engineering team to deploy advanced communication systems—when they see platforms can be modular, automated, and integrated into existing workflows—something shifts.
They start imagining what’s possible again.
Early teams are fluid. They have to be. But longevity means moving from “whoever can do it” to “here’s how we do it.”
Clear roles. Clear ownership. Clear decision-making. Clear priorities.
In mission-driven startups, clarity is kindness. People will do hard work if the work is coherent. What burns teams out isn’t just workload—it’s thrash. Constant redefinition. Unclear expectations. Priorities that reset every week.
Longevity is building the kind of internal structure that lets people contribute without living in permanent uncertainty.
Startups love speed. But speed without pace is burnout—personal and organizational.
Longevity is sustainable execution: fewer thrash cycles, tighter feedback loops, shipping improvements that compound, and building trust with partners over time rather than in bursts. It’s being able to say “no” to good ideas so you can deliver consistently on the right ones.
And in social impact, consistency matters. Because our partners don’t need a flashy demo. They need reliability when the situation is messy.
This transition isn’t mainly operational. It’s personal.
When you’ve been the jack-of-all-trades CEO, your identity gets tied to being needed everywhere. Letting go can feel like losing relevance.
But the goal isn’t to be essential to every function. The goal is to build something that can outgrow you—because that’s what makes it last.
I still care about shipping. I’m still scrappy. I still watch runway.
But I’m paying more attention to a different set of questions:
Are we building something that can be maintained, not just launched?
Are we reducing friction for non-profits who don’t have technical teams?
Are we strengthening accountability and feedback loops with communities?
Are we building systems that hold up in crisis conditions?
Are we creating a team culture people can stay in—not just survive?
Because the work isn’t just to build a company. It’s to build something durable enough that when the next crisis hits—and it will—organizations can move faster, communicate better, deliver assistance more securely, and do it with dignity.
The technology is here. The need is here. The opportunity is here.
Longevity is making sure we’re still here too—closing the capability-awareness gap, building tools that hold up under pressure, and helping the people doing the hardest work in the world do it better.