A foundation's intake and partnerships system

A foundation's intake and partnerships system

The Eddie Betts Foundation ran youth applications and partnership deals across duplicate databases and a WordPress-to-Monday pipeline. I merged everything into one clean Notion system with the right privacy for every role.

Eddie Betts Foundation

·

Nonprofit & Foundations

·

Workspace Audit & Rebuild

·

4 to 12 weeks

Published

·

Last updated

By

Imene Mellal

A foundation's intake and partnerships, systemized

THE PROBLEM

The Eddie Betts Foundation's youth program applications lived in two overlapping databases, website inquiries traveled from WordPress into Monday, and partnership deals had no clear home. The result: duplicates, privacy risks around sensitive data, and no single view of the foundation's work.

THE SOLUTION

One Notion workspace: a merged applications database with a clean intake form and approval checklist, an inquiries database that captures website submissions straight into Notion and spawns follow-up tasks, and a partnerships dashboard where deals stay exec-only while operational tasks are visible to staff.

THE PROCESS

A scoping call to map how deals become programs, a visual process map agreed before any build, then staged changes to the live workspace with team feedback each round, so nobody lost their bearings mid-migration.

THE RESULT

Two systems merged into one intake pipeline, an external tool retired in favor of native Notion forms, and a partnerships pipeline with the right level of privacy for every role: one trustworthy workspace for the whole foundation.