Fiscal-sponsorship data infrastructure at Candid

The problem

Fiscal-sponsorship projects (small initiatives operating under the legal and financial umbrella of a 501(c)(3)) were largely invisible in the social sector’s data layer. Funders couldn’t find them. Researchers couldn’t count them. The projects themselves had no canonical record of existence outside their sponsors’ internal books.

This is a meaningful gap. A non-trivial portion of social-sector activity happens through fiscal sponsorship, and treating it as invisible distorts every downstream decision built on sector data. Funders miss emerging work. Researchers undercount actual activity. The projects themselves lose access to visibility, credibility, and the data infrastructure that makes grant applications easier.

It was also a product problem, not just a data problem. The projects existed. The sponsors knew who they were. What was missing was a structured, consented pathway to move that data into the places that people in the sector actually rely on.

Who it serves

Funders looking for emerging work that doesn’t fit the standard 501(c)(3) profile. Researchers studying actual sector activity rather than just registered entity activity. Fiscal sponsors whose project rosters become legible to the philanthropic data infrastructure for the first time. Smaller, mission-bound projects that don’t have the resources to register independently but deserve to be findable, citable, and counted.

How it helps

A data-acquisition and integration program that surfaces fiscally-sponsored projects into national philanthropic data infrastructure, with consent and governance designed alongside the sponsors rather than imposed on them.

The product surface isn’t the database. The product surface is the trust relationship with each sponsor. Getting a sponsor to share their roster isn’t primarily a technical challenge. It’s a partnership design challenge: what do you need to know, how will it be used, who controls the update process, and what happens when you want to remove a project? Those questions have to be answered before anything flows.

What it does

Brought hundreds of fiscal-sponsorship projects online that were previously invisible in sector data. Cross-functional product work spanning data partnerships, governance, and integration design.

The work required coordination across data engineering, partnerships, legal, and design. Most of the actual surface area was in the governance conversation: co-designing the consent framework with sponsors meant understanding their obligations to their projects, their concerns about data being used in ways they couldn’t control, and their capacity to maintain accuracy over time.

Sustainment is harder than ingestion. Ingestion is a moment. Sustainment is an ongoing relationship with a data source that has its own governance pressures, personnel changes, and shifting project rosters. The product design has to account for all of that, not just the initial import.

What I learned

The technical part was straightforward. The trust architecture wasn’t.

Convincing fiscal sponsors to share their project rosters required co-designing the consent and governance model with them, not for them. That’s a meaningful distinction. When you design consent for someone, you optimize for coverage. When you design consent with someone, you optimize for durability: a model they’ll actually maintain, update, and believe in. One approach gets you the data faster. The other keeps the data accurate longer.

The lesson generalizes past philanthropy: in mission-bound spaces, the product is partly software and partly trust. The software can be excellent and still fail if the trust architecture is fragile. Most vendor pitches in data are about the ingestion. The harder question is always sustainment: who updates this when someone leaves, when a project closes, when the sponsor changes their mind?

Those questions don’t get answered in the contract. They get answered in the relationship.

Status

Active, ongoing. The program continues to grow as new sponsors are onboarded and the governance model matures.