Real Salesforce Transformations for Nonprofits

The Challenge

Every publication goes through fact-checking. Every assignment matters. Before every single assignment, the editor had to pause and think: Who reviewed it most recently? Who has carried more load? Who declined last week? Is there any conflict? Am I being fair?

• Fairness lived entirely in one person's head
• Cognitive bandwidth problem, not a reviewer problem
• High-stakes environment requiring defensible decisions

Solutions

• Designed a fairness model with two rules: eligibility (recency) + priority (workload)
• Dynamic median logic recalculates eligibility daily (not fixed "30 days")
• Automatic conflict filtering (authors, collaborators, project managers)
• Cooldown logic for recent declines and protected windows

The Challenge

When I joined this organization, they had Applications and Reviews. Applicant information lived as fields directly on the Application record. There were no Application Contacts. No relational structure. No clean way to track people across cycles. And intake ran through a large FormAssembly integration. It worked. But it was fragile and hard to evolve.

• No relational structure for applicants, co-PIs, and collaborators
• Complex FormAssembly integration that was hard to maintain
• Program and finance disconnected — spreadsheet handoffs

Solutions

• Phase 1: Introduced Application Contact junction object — multiple applications per person, accurate institutional tracking, clean reporting across cycles
• Phase 2: Built four-path processing architecture with duplicate prevention, file classification, and downstream automation
• Phase 3: Designed finance layer (Expense Request, Budget Line, Budget Change, Expense Payment) with Bill.com integration
• Phase 4: Integrated with Submittable for portal experience while maintaining Salesforce as the system of record

The Challenge

At the time, Salesforce didn't have built-in impact tracking. Nonprofit Cloud didn't exist in its current form. And yet, our think tank needed to answer a deceptively simple question: How do we know we're actually making change in the world?

• No system to track outputs, outcomes, and impact
• Scrambling for anecdotes when funders asked for evidence
• Disconnected program data from fundraising reporting

Solutions

• Phase 1: Cross-department requirements gathering — interviewed Communications, Editorial, Policy Relations, Academic Relations, and Fundraising
• Phase 2: Designed custom Impact (Success Indicator) object with four record types and structured taxonomy for outputs, outcomes, and impact
• Phase 3: Built junction object connecting Impact records to Contacts — enabling queryable cross-functional influence patterns
• Phase 4: Aligned system with fundraising reporting — outputs, outcomes, and impact now queryable for funder reports

The Risk

Grants were being recommended and disbursed. But financial controls relied heavily on vigilance:

• Was a W-9 on file?
• Had this payee crossed the IRS reporting threshold?
• Was the amount high enough to require executive approval?
• Had a budget change been formally approved before overspending?

Each of those checks required attention. Attention fails under pressure.

Solutions

• Threshold Enforcement: System tracks year-to-date payable totals by Account — blocks disbursement if IRS reporting thresholds approached and documentation missing
• Multi-Level Approval Routing: Amounts automatically route based on thresholds — standard approvals to VP/CEO for high amounts
• Budget Governance: Payments exceeding approved budget lines require Budget Change records with their own approval chain
• Payment Infrastructure & Sync: Once approved, payments sync automatically to Bill.com with inherited parent data