CLIENT CASE STUDY / A GLOBAL NONPROFIT
This global nonprofit runs development programs alongside corporate and government partners around the world. Its institutional knowledge lived in a handful of people’s heads. In 90 days, we helped turn that knowledge into a shared company operating system built for the next chapter.
A GLOBAL MISSION, BUILT FOR WHAT’S NEXT
~60 million
People reached today
100 million
The goal for 2030
Clean water. Public health. Circularity. Nearly 80 countries.
~700 hrs
Modeled annual time reclaimed at conservative adoption
~$50K
Annual value of that time at conservative loaded rates
$120K+
Potential annual time value at full adoption
36 days
A year one program lead spent reconciling consultants
THE CONTEXT
For decades, this global nonprofit has run development programs alongside corporate and government partners around the world. Its work reaches millions of people, and the mission keeps growing. A distributed team of about 40 people across several continents had no shared place to find the institutional knowledge behind decades of programs.
Of relationships, programs, and institutional knowledge
Development programs around the world
Core staff and consultants across several continents
THE CHALLENGE
Program updates lived in manually maintained Excel files. Proposals disappeared into a 40,000-email inbox. Documents were split between SharePoint and an aging legacy server. When someone needed an answer, the path often led back to the CEO or COO.
“In my head, it lives in some of my other team’s heads.”
NONPROFIT LEADERSHIP / WHERE THE KNOWLEDGE LIVED
BEFORE / KNOWLEDGE BOTTLENECKS
Every answer leads back to leadership.
Several continents
A distributed team of about 40 people with no shared home for institutional knowledge
CEO + COO
The human search engines for program knowledge
Scattered information
Email inboxes, Excel, SharePoint, and a legacy server
90 DAYS
AFTER / A SHARED ORGANIZATIONAL BRAIN
The knowledge works for the whole team.
CompanyOS
Six connected databases with relevant team views
Answers in context
Program status, proposal history, and consultant agreements
Knowledge that grows
Meeting transcripts and reusable templates, with controlled access
THE DECISION
The nonprofit came looking for a fractional COO. The real need was a shared organizational brain. The team was already open to AI, but scattered experiments would not solve fragmented information. First, the knowledge had to be curated, connected, and accessible.
Nearly all of the nonprofit’s work comes through referrals, with long-standing corporate partners. Making past programs searchable helps the team reuse proven language and qualifications when the next donor opportunity arrives.
THE BUILD
We began with two weeks of structured interviews across leadership and regional program teams. Then we translated the assessment into CompanyOS: six linked databases, clear access permissions, and a practical way to keep knowledge growing.
01 / PROGRAM VISIBILITY
One place to see the work
Programs, projects, funders, and implementing partners are connected, so status no longer depends on chasing someone for an update.
02 / PROPOSAL KNOWLEDGE
Build on what already worked
Proposals have a real home. Reusable templates are taking shape from historical program language and qualifications.
03 / CONSULTANT AGREEMENTS
Keep critical dates in view
Agreements are moving into a structure built to flag expirations, rather than letting them lapse unnoticed mid-engagement.
04 / INSTITUTIONAL MEMORY
Make knowledge compound
Meeting transcripts become part of the system, while group permissions keep sensitive agreement information restricted.
SIX DATABASES. ONE CONNECTED OPERATING SYSTEM.
CompanyOS
A shared home for the nonprofit’s institutional knowledge
Programs
The big picture
Projects
The work in motion
Funders
The relationships behind it
Implementing Partners
The partners delivering it
Staff & Consultants
The people doing it
Proposals
The knowledge to build on
Linked records connect the work. Group permissions control access. Meeting transcripts keep the knowledge growing.
DISCOVER
Listen first
Two weeks of interviews with the CEO, COO, and regional program leads.
MAP
Find the friction
Surface fragmented visibility, manual agreements, and knowledge bottlenecks.
BUILD
Connect the knowledge
Link six databases and configure relevant views and access permissions.
ENABLE
Train the team
Live training with approximately eight staff on linked records, filters, and groups.
THE OPPORTUNITY
The time model covers leadership requests, consultant reconciliation, proposal production, board preparation, and everyday staff self-service. At conservative adoption, the nonprofit is on track to reclaim approximately 700 hours a year. Full adoption creates a larger opportunity.
Annual time that could be reclaimed
Conservative adoption: ~700 hours / ~$50K
Full adoption potential: 1,700+ hours / $120K+
Modeled annual estimates using loaded time costs, not audited cash savings. Actual results depend on adoption.
Per month spent on manual consultant reconciliation
Of repeating the same administrative work
A year consumed for one program lead
Budgets involved in the reconciliation process
That 36-day baseline shows how quickly small, recurring tasks consume meaningful capacity. The opportunity is not just administrative efficiency. More time for proposals and donor relationships could help the team pursue additional funded programs.
Three days a month adds up.
Before CompanyOS, one program lead spent 36 days a year manually reconciling consultant time and payments.
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
NOV
DEC
Baseline workload, not a claim that all 36 days have already been eliminated.
THE NEXT CHAPTER
Leadership wants the organization ready for an eventual leadership transition. An organization that runs on two people’s memory is not one you can hand off cleanly. CompanyOS gives decades of hard-won knowledge a shared home, so the next chapter does not depend on one person remembering where everything lives.
THE NONPROFIT’S VISION FOR THE ORGANIZATION
If your business still runs on a few people’s memory and a fragile spreadsheet, that is the problem we install CompanyOS to fix, in 90 days.

