Airtable Donor Tracking With Partner-Level Privacy for an International Nonprofit Accelerator

Situation

This client is a nonprofit organization that supports early-stage social impact initiatives through program design, operational support, and funding coordination. They support multiple partner organizations and manage a shared pipeline of donor outreach and opportunities. Their tracking lived in a shared spreadsheet, which created two persistent issues.

Privacy: partners needed to see their own pipeline activity, but not other partners’ donor activity

Coordination: staff needed a live view of who was approaching which donor and when, so donors were not double-contacted

In order to keep partners separated in spreadsheets, they would have needed roughly 25–30 separate sheets plus ongoing manual syncing.

ProsperSpark created one system for the full portfolio, with partner-by-partner privacy built in, so coordination stayed visible and donor outreach didn’t collide.

Solution

ProsperSpark built and refined an “umbrella” Airtable base that let internal staff manage the full portfolio in one place, while still giving each partner nonprofit a locked-down view of only their own records. The point wasn’t just to move data out of a spreadsheet. It was to create a system where privacy was built in, coordination was visible, and the workflow could scale as partners and programs changed.

Here’s what that looked like in practice.

Data structure and migration
We started by getting the foundation right so reporting could be trusted and relationships could be tracked cleanly.

• Copied and reviewed the existing structure, then made structural updates
• Migrated data into Airtable
• Connected donors to initiatives and added fields for donor interests and funding criteria
• Completed discrepancy reviews to improve confidence in rollups and reporting outputs

Donor outreach workflow
Next, we rebuilt the outreach workflow so ownership and timing were visible across the team.

• Added donor assignment so teams could build outreach lists and create opportunities tied to specific programs
• Added a donor “claiming” workflow so staff could mark who is approaching a donor and when

Initiative tracking that matches real life
Because program work isn’t always tidy, the system needed to handle edge cases without breaking reporting.

• Supported initiatives that weren’t yet in the master initiative list by allowing manual creation, then later linking once standardized
• Supported tracking categories that would never have a masterlist record (example: portfolio-level or org-level prospects)

Formulas and reporting logic
We tightened the logic so the team wasn’t arguing about what a status meant or whether a report was accurate.

• Built and refined formulas for Prospect vs Active donors
• Added a probability concept for opportunities
• Updated formulas as new sources were added and data synchronization needs evolved
• Addressed naming inconsistencies that created false duplicates in rollups

Role-based interfaces and permissions
To support partners without cross-visibility, we relied heavily on interfaces and permissions design.

• Built an internal admin interface for a full portfolio view
• Built partner-specific interface pages so each nonprofit saw only their own slice
• Created templates for repeatable partner views and admin selection control
• Updated access controls for additional internal roles (example: team leads and regional coordinators)

Workflow guardrails and automation
The goal here was to enforce rules with the system, not with reminders and manual cleanup.

• Added an automation to decline non-awarded opportunities when a partner is marked inactive
• Supported enhancements like communication logging and an initiative “voting” process with rollups

Adoption and support
This wasn’t a “build it and disappear” system. It needed to be usable and maintainable, so we provided permissions guidance and a documentation starter, and continued support and enhancements into 2025.

Results

They moved from spreadsheet coordination to a controlled system where privacy and visibility could exist at the same time. Instead of relying on separate files, manual syncing, and side conversations to confirm “who’s doing what,” teams could work from one source of truth, with access segmented by role and partner organization. That made the workflow easier to run day-to-day and easier to trust when leadership needed an accurate view of the pipeline.

Here’s what changed.

More reliable pipeline visibility
Because key fields were standardized and maintained, reporting became more consistent.

• Status and probability logic was defined and applied consistently
• Fewer reporting discrepancies after formula and rollup cleanup

Less back-and-forth to confirm what’s happening
Updates were available where people worked, so fewer “where are we at” messages were needed.

• Opportunity status could be viewed in role-based interfaces without digging through sheets
• Clearer initiative and donor context reduced interpretation gaps

Lower duplicate outreach risk
Ownership and timing signals were visible, which reduces accidental overlap.

• Donor “claiming” created an explicit owner for outreach attempts
• Approach timing was recorded so teams could coordinate asks

Better adoption across teams
As the base and interfaces matured, the system became the operating layer teams relied on.

• Partner-specific views made it easier for external organizations to participate without cross-visibility
• Internal teams used the admin view to coordinate across the portfolio