Skip to main content
Leadership

Building a Salesforce Center of Excellence on a Nonprofit Budget

When I joined Boys Hope Girls Hope as Director of Technology Services, we had Salesforce deployed across the US and Latin America — but governance was inconsistent, technical debt was accumulating, and end users in different regions were doing things very differently.

The answer was establishing a Center of Excellence (COE). But unlike a Fortune 500 with a team of architects, we had to build ours lean.

What Is a Center of Excellence?

A Salesforce COE is a team, structure, and set of practices designed to:

  • Define standards for how Salesforce is used, developed, and maintained
  • Provide training and support to users
  • Review and approve platform changes before they go live
  • Maintain documentation and architectural decisions

In a large company, this might be a team of 10+ people. At a nonprofit, it might just be you.

The Minimum Viable COE

Here’s what I built in year one with limited resources:

1. A Change Advisory Process

Before any new Flow, report, or custom object goes into production, it has to go through a simple review. We use a Salesforce Case with a custom record type: “Change Request.” The review questions are simple:

  • Does this align with our data model?
  • Does this duplicate something that already exists?
  • Who will maintain this after it’s built?

This simple gate stopped a lot of technical debt before it started.

2. Naming Conventions

The most boring thing I implemented was also one of the most valuable. We established naming conventions for:

  • Custom fields: Object_DescriptiveName__c (e.g., Contact_VolunteerStatus__c)
  • Flows: [Object] - [Trigger Type] - [Action] (e.g., Opportunity - After Update - Send Thank You Email)
  • Reports and Dashboards: [Team] | [Report Name] (e.g., Development | Annual Giving by Month)

3. Documentation First

Every Flow, custom object, and integration has a corresponding Confluence page (we use the free tier). At minimum, the page captures:

  • Why it was built
  • Who owns it
  • How to test it
  • Known limitations

When staff turns over (and in nonprofits, it does), this institutional knowledge doesn’t walk out the door.

4. Release Notes

We send a brief email to all Salesforce users after every deployment. Two or three bullet points. What changed, and why. Users feel informed, trust improves, and adoption goes up.

Working With Salesforce.org

Don’t overlook the resources available through Salesforce.org:

  • Power of Us Hub — Community support from other nonprofit Salesforce users
  • In-kind grants — If you’re not already on the nonprofit pricing, apply for the 10 free licenses
  • Accelerator programs — Occasionally available for eligible nonprofits

The Biggest Lesson

Start with documentation and governance before you start building. Every complex flow you build without a review process creates future work for your future self. The COE isn’t bureaucracy — it’s self-care for your org.

Questions about building your COE? Let’s talk.

← Back to Blog