Case study
What would the President want to see?
A live leadership board for PROPEL Center, built on the tools the team already used.
The situation
PROPEL Center is a national education nonprofit that runs skills challenges for HBCU students.
In team meetings, its President kept asking the same kind of question: can I see that? The answers existed. They sat in project boards and inside the CRM, and getting one meant someone had to go dig. Attendance for one event series depended on someone importing a spreadsheet by hand.
Her ask to the team was to be better: reach the goals and improve how the work gets done. We took that as a design question. In her seat, what would we want to see?
What was built
- One private board, behind a login, used by more than five people on the team.
- Live data pulled from the CRM and from PROPEL U, the course platform, refreshed on a schedule about every 15 minutes.
- Students and email performance broken out by challenge, with a filter that follows you from tab to tab.
- A list of students who need a nudge, so outreach goes to the right people.
- Outreach to schools kept in its own section, so it does not skew the student numbers.
- A private fundraising view with an overview, a pipeline, deals, and a needs-attention list. It reads CRM deals and writes nothing back. Only the logins that should see it can.
Where every student is right now
From the first click on Apply to a submitted project. Red tags show how many students stopped at each stage.
Needs a nudge
Students who need a personal touch. Hottest first, since they are the easiest to win back.
Engagement
Who is with us right now. Points come from real actions. Email opens are never counted.
How it was built
We designed the views first, then directed AI to build them as custom code on top of tools PROPEL already paid for.
It started as a preview on sample data. Live data was connected only after the preview was approved. It went through at least nine versions, each one shaped by what leadership asked to see next.
The fundraising view is read-only by design. Access keys live in the host's settings, not in the page, and everything sits behind a login.
Tools: their CRM and email platform, PROPEL U, Netlify, GitHub, and Claude with its connectors (MCP).
What came next
On the call where the board was reviewed, the conversation turned to PROPEL U and the student experience. That became the student platform.
Next on the board itself: trends over time, goals, and a weekly summary for leadership.
Same client. See the other builds.
Finish this sentence.
It is the only brief we need to tell you how we would build it.