1,500 Donors Tracked Without Sacrificing Privacy

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 Google Sheets.

It worked until multiple teams needed to update the same records at the same time. Ownership became unclear, outreach history was hard to follow, and the data became stale or inconsistent. The #1 reason they moved off Google Sheets was to prevent duplicate funder outreach. 

Issues the team called out:

• Duplicate or conflicting outreach
• Too many people editing and unclear ownership
• Hard to track outreach history (who, when, what happened)
• Data got stale or inconsistent
• Lack of consistency in process

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 captured key context like interests and 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 a clear ownership approach so teams could assign outreach and reduce overlap
• Added a donor “claiming” workflow so staff could mark who is approaching a donor and when
• Improved the ability to log and reference outreach history, so the team isn’t reconstructing context from edits and messages

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 improved.

Scale and adoption

• Active users grew from 3 to 30
• ~1,500 funders tracked

Time and coordination

• 10+ hours/week saved by reducing coordination and manual upkeep
• Less time spent coordinating updates across teams

Fewer errors and clearer ownership

• Fewer communication errors and less confusion
• Clearer outreach history (who/when) and clearer ownership

Privacy and control

• Better privacy, security, and control
• Partner-specific access without cross-visibility

Messy-before, smooth-now

• They can now see when multiple teams are engaging the same major funder, who is involved, what they’re discussing, and coordinate strategy as one team instead of colliding on outreach