← Case studies
Case study · Design systems

A design system a two-person team could actually run.

A growing ministry was launching six campaigns a year with no in-house designer. Each one started from scratch, ran late, and looked like it belonged to a different organization. We built the system that changed that.

Faith-based nonprofit · 24 staff · 6 major campaigns per year

9 days
New campaign turnaround, down from 6 weeks
1
Person needed to ship a full campaign kit
0
Freelance-designer rush fees in the first year
The challenge

Every campaign — Easter, back-to-school, giving Tuesday, year-end — started with the same conversation: what colors are we using, where are last year's files, and who can design the social graphics by Friday? The team was spending more time recreating than creating.

The communications lead had built a Canva folder that mostly worked. It just wasn't a system — nothing carried across web, print, and email, and no one knew which version was current.

The approach
01

Audit what the team was already reaching for

We inventoried every campaign asset shipped in the last 18 months, sorted them by what actually got used, and threw out everything that didn't. What remained told us the real system — the one the team had been building without naming it.

02

A small kit, not a big library

Two type styles. Three colors. Six page layouts. Four social templates. One email template. Rules for photography. That's the whole system.

A tight kit is one a two-person team can hold in their head. A big one becomes a museum no one visits.

03

Templates in the tools the team already uses

Web templates in their CMS. Social templates in Canva. Email templates in their ESP. Print templates in Google Docs and Canva Print. Nothing that required learning new software. Nothing that broke when a staff member left.

04

A one-page guide instead of a 40-page brand manual

A single page — a laminated copy sits by every workstation — covers colors, type, spacing rules, and the three things to never do. New hires can absorb it in five minutes. Board volunteers can follow it well enough to ship.

The outcome

The first campaign after rollout shipped in nine days end-to-end. The next five shipped without a single freelance design invoice — the first year the org didn't need one. Campaign-to-campaign visual consistency, measured by an outside consultant, jumped from "fragmented" to "clearly one organization."

The team stopped dreading campaign kickoffs. That was the outcome we cared about most.

For the first time, launching a campaign feels like assembling something — not inventing it.

Communications Lead, client organization
Common questions

What teams ask before starting one of these.

What is a nonprofit design system, exactly?
It's a small, opinionated kit of reusable pieces — colors, type, buttons, page templates, social layouts, email components — plus the rules for using them. For a nonprofit, the point is that a two-person team can ship a new campaign without hiring a designer for each one.
Isn't a design system overkill for a small team?
The opposite. A big team can absorb inconsistency with headcount. A small team can't. A design system is how a small team ships work that looks like it came from a much bigger one — and how they avoid rebuilding the same landing page from scratch every fall campaign.
Do we need custom code to have a design system?
No. Most nonprofit design systems we build live in whatever platform the team already uses — Canva, Figma, Webflow, Framer, Google Docs. The value is in the constraints and templates, not in fancy tooling.
How do we keep a design system from going stale?
A short quarterly review — 60 minutes with whoever's using the system — is usually enough. Add what's working, retire what isn't. Systems that never change stop being used; systems that change every week become chaos again.

Small team, big campaign year? A design system is how you survive it.