Ryndel Labs is building the coordination infrastructure the world never had. We map how capital, resources, and people connect across communities, model where the system breaks, and deploy capital and initiatives into what the model finds. Starting with philanthropy, because federal funding cuts made the need unignorable.

What we see

The world is stuck in
local maxima.

For the last year we have been inside the rooms where capital, resources, and decisions move. Philanthropy. Government agencies. Universities. Family offices. Venture capital. Private equity. Corporate R&D. Leaders of movements. Nonprofits working across all of them. Every conversation ended at the same place.

It is not that the introduction layer is missing. The incentives to build it do not exist. The world is complex enough that coordination is genuinely hard, and every actor inside it has a local reason to keep their piece of the picture to themselves. Intermediaries profit from gatekeeping. Platforms monetize scarcity. Information stays siloed because someone benefits from the silo. Each actor optimizes locally and gets stuck on a local maximum, and the whole system holds itself in place.

The result is that almost everything we care about at the systems level depends on serendipity. The nonprofit meets the right funder at a conference. The founder runs into the right investor on a flight. The researcher and the company that could commercialize her work find each other through a friend of a friend. A North Carolina partner said it to us directly, and we kept the line: serendipity is inefficiency. Our work is to systematically manufacture what the world currently waits to stumble into.

Why now, and why philanthropy first: federal funding cuts are forcing a reckoning with efficiency that the sector has been able to defer for decades. The nonprofit world is the most entrenched in systems stuck at local maxima, and also the one with the sharpest catalyst for change right now. We are building the infrastructure that turns that pressure into coordination instead of collapse.


The arc

A community foundation
for the world.

Where a community foundation coordinates a local ecosystem, we coordinate at every layer above it, driven by a model that learns from every deployment. We see the picture no single sector can see from inside itself. We bring together the data that makes the picture actionable. We deploy capital and initiatives into the gaps the model identifies.

Every product feeds the model. Every deployment generates new data. Every new geography makes the map denser. The institution gets sharper with every action it takes. There is no exit from that loop.

Where we are now

Two real partners. Real problems. Today.

We are in active development with two philanthropy connectors, one in Connecticut and one in North Carolina. The data being surfaced right now is the foundation the scalable product will be built from.

Community shock preparedness, Connecticut

Our Connecticut partner came to us with a direct concern. In their words: “We saw how Minnesota was not prepared for the ICE raids with the appropriate resources to address the impact on the community, and we are concerned we may not be too. We want to understand which resources, from which people or organizations, can be allocated in different ways across various scenarios. This will help us map the structure needed, identify any gaps, and ensure resources can go further through stronger collaboration and connections.” The same infrastructure that prepares a community for one shock prepares it for the next.

Scaling hyperlocal mapping, North Carolina

Our North Carolina partner has been manually mapping hyperlocal communities for years, with visible results, and hit the ceiling where manual work stops scaling. In their words: “Scaling to multiple hyperlocal communities has created a step change in harmony, but it is incredibly resource intensive. If you could build something that allows us to map hyperlocal communities at scale, that would be hugely helpful for us.”

Why coordination fails

Three failures. Every time.

People cannot find each other

A nonprofit and a funder whose missions match perfectly never meet. A founder and an aligned investor never connect. A researcher and the business that could scale her work never surface in the same room. The resources exist. The introductions do not.

Incentives reward the fragmentation

The actors best positioned to fix coordination failures often profit from their persistence. Intermediaries control access. Platforms monetize scarcity. You cannot appeal your way out of that structure. You need an architecture that makes the gatekeeping irrelevant.

Verification costs too much

Even when two parties find each other, the cost of trusting an unknown counterparty kills the collaboration before it starts. A data layer that makes entities legible — with their history, relationships, track record, and context — eliminates that friction and makes first contact viable at scale.

“Serendipity is inefficiency.”
A North Carolina partner
The platform

One map.
Three readers.

Where a community foundation coordinates a local ecosystem, we coordinate at every layer above it. The same dataset that gives a philanthropy connector resolution over its ecosystem becomes deal flow, operator intelligence, and gap modeling for the capital allocators and institutions that read it at scale.

Architecture

Built where no one else will go.

Hyperlocal entity data is the hardest data in the world to collect. It is undigitized, heterogeneous, politically complex, and requires genuine institutional trust — not just public scraping. Every serious data company surveyed this problem and chose something easier. No existing vendor covers what we are building. That is not a gap in the market. That is structural difficulty, which is exactly why the data is worth something once collected.

Community foundations are the entry point because they already hold the trust and the relationships that make real coordination possible. A connector does not hold all of the information about its community; the community itself holds it, distributed across every organization and person inside. What the connector has is legitimacy. What we bring is the network layer that turns legitimacy into structure.

At Layer 3, the map meets the model. Every mapped entity, every identified gap, every tracked coordination failure flows into the Underlying Inefficiency Model. Capital deployed by that model generates new entity data. The loop does not end. The institution gets sharper with every deployment and more valuable with every new geography mapped.

‡ The hardest data to collect is the most defensible once you have it. That is the only reason to start there.

The layers
Where we start

Communities are where every network intersects.

A community is not a silo. It is the ground floor where venture capital, government, universities, philanthropy, nonprofits, and local enterprise all touch. Map what is happening inside one community and you are mapping a cross section of every network that runs through it.

Philanthropy connectors are our first partners because they already hold the trust and the relationships that make real coordination possible. What the connector has is legitimacy. What we bring is the network layer that turns legitimacy into structure. Together we surface the connections that already should have happened, and the ones that will become critical as the community changes.

The value compounds with scale. One mapped community is useful. Ten connected communities change what is possible for every nonprofit, funder, researcher, and operator inside them.

Both sides of every connection

Most of the conversation in capital allocation focuses on the allocators. We are building for everyone on the other side of the table too.

A nonprofit looking for a funder whose thesis fits their work

A founder looking for capital aligned with their specific problem rather than their zip code

A researcher trying to reach the business that can take her work out of the lab

An operator in an underserved market who has been invisible to every standardized database

Our job is to make people findable to the people who should be looking for them. Coordination runs in both directions.

Who reads the map

The same dataset serves both ends of every connection — the organizations closest to communities, and the capital looking to find them.

The map is the same. The resolution of what you find in it depends on which side of the table you sit on.

The model

Mapping is the input.
The model is the product.

The map tells us what exists in a community and how it connects. The model tells us why coordination is failing, which connections would produce the most impact, and where the next inefficiency is about to emerge. Mapping is necessary. The model is what turns it into infrastructure.

The argument

Coordination failure has a repeatable structure.

We are building the model on real theoretical grounding rather than product intuition. Asset-Based Community Development for the mapping taxonomy. Burt’s structural hole analysis and Barabási network science for the algorithmic gap detection. Pfeffer and Salancik’s resource dependence theory for why the gaps persist. Banerjee and Duflo’s causal inference methodology for measuring whether facilitated connections actually produce impact.

The long-term ambition is something closer to a research institution in the tradition of Santa Fe Institute or Bell Labs, but more directly connected to capital allocators. Sector-agnostic research on system inefficiency, subsidized by the allocators who benefit from the findings, feeding the model that directs our own deployments and initiatives. Every iteration of the map sharpens the model. Every deployment generates new data. The model becomes more accurate with every community mapped and every action taken.

The same three structural failures appear in every broken system we have studied — in different combinations and severities. If they are enumerable and measurable, then coordination failure is not intractable. It is a pattern problem. Pattern problems have pattern solutions that generalize across domains without reinvention.

Compounding flywheel
Traditional vs Ryndel

Traditional

Ryndel

Root causes

Visibility failure

Organizations that could solve a problem do not know it exists. The people with the problem do not know those organizations exist. Without a deliberate data layer connecting them, the match rate on any coordination opportunity approaches zero — not because the resources are absent, but because they cannot see each other.

Incentive misalignment

The actors best positioned to fix coordination failures often profit from their persistence. Intermediaries control access. Platforms monetize scarcity. Incumbents benefit from the friction that keeps competitors out. The only path is an architecture that makes their structural advantage irrelevant.

Trust infrastructure gap

Even when parties find each other, the cost of verifying an unknown counterparty creates enough friction to prevent coordination. A data layer that makes entities legible — their history, relationships, and context — eliminates that friction and makes first-contact coordination viable at scale.

Open questions

Where we are
looking next.

Parallel research probes across the sectors where fragmentation costs the most. Each tests the same hypothesis from a different angle. Findings feed the model. The model sharpens the next probe.

Where we are going

Honest about
the horizon.

Long-term work deserves long-term honesty. This is what we are building toward and when.

The timeline

How we are building this

For-profit for scale. Mission at the core.

Our goal is to make the largest physical impact possible on the world, measured in real outcomes across real communities. That goal dictates the structure.

A nonprofit can do meaningful work but cannot compound at the speed the problem requires. A standard for-profit can scale but usually drifts from the mission under the pressure of quarterly capital. We are building Ryndel as a for-profit institution because scale is the only thing that matches the size of what we are fixing, with the values, incentives, and governance designed from the start to hold mission in place as the institution grows.

The focus is mapping and modeling. Everything else is downstream of that. As the model finds inefficiencies worth filling, we stand up the funds, initiatives, and partnerships that fill them. Sometimes that is a coalition of existing funders. Sometimes it is a standalone fund built around a specific hole. Sometimes it is a direct initiative we operate ourselves. Every deployment feeds new data back into the model. Scale and mission are the same loop.

Team

Two founders.
One problem.

Ryan Pool
Co-Founder

Ryan has spent his entire life studying how the world works at the system level and then diving into the specifics, watching how the threads connect. Fourteen years inside the startup ecosystem. Founded seven companies. A year inside venture capital. Over a decade mentoring and facilitating inside a startup accelerator, sitting at the exact point where founders and resources fail to find each other. TEDx speaker on neurodiversity and reframing struggle.

He is driven by a refusal to accept that broken systems have to stay broken. Most of what looks like dysfunction is a design problem that has not been solved yet.

Systems designVenture capitalStartup ecosystemsTEDx
Hoshita Undella
Co-Founder

Thirteen years of cross-domain research across renewable energy, biomedical engineering, and fintech. Presented at national conferences. Published in the Library of Congress. Built and scaled thirty robotics education initiatives across nine countries, reaching over seven thousand people, including twenty five hundred children with a particular focus on girls.

Hoshita works at the intersection of design thinking and systems research. Every domain she has worked in had a different vocabulary for the same underlying coordination problem. Ryndel is the structural answer.

Cross-domain researchBiomedical engineeringFintechGlobal operations
What we believe

Load-bearing assumptions.

¶ These are not values statements or brand pillars. They are structural assumptions baked into how Ryndel Labs is designed. If any of them turns out to be wrong, the institution reconfigures around the correction — not the other way around.
Get involved

The right people
make this work.

We are building something designed to outlast any single founder, fund cycle, or market condition. If you recognize yourself below, reach out directly. Ryan or Hoshita responds personally to every message.

Who we are looking for
Reach us

Tell us what you are working on.

Ryan or Hoshita responds personally, usually within 48 hours. No intake process. A direct conversation about whether there is real fit.

Community foundations & connectors

The entry point for the map. Phase 1 cannot exist without foundation partners willing to map their ecosystem. If you are a community foundation or philanthropy connector, we want to talk to you first.

Response time

Usually within 48 hours. Ryan or Hoshita responds personally.

What happens next

A direct conversation. No pitch deck, no intake form. We want to understand what you are working on and where the overlap might be.