Campaigns, movements & advocacy
A print-to-web recruitment funnel that turns cards into supporters.
A designed direct-mail conversion system: emotion-front/agency-back cards driving a QR doorway into a multi-tenant landing engine wired to the supporter platform.
A statewide membership organization was recruiting with a decade-old set of outreach cards that explained a case rather than converting anyone. Education, not action. It needed to turn a static print channel into a measurable digital funnel that fed its supporter platform, without reprinting every time the message changed.
We designed the conversion system end to end and built the engine to run it. The strategy: one card, one ask; emotion on the front, agency on the back; psychological triggers instead of statistics; and a “static card, dynamic doorway” model: the printed card is permanent, but every living detail sits behind a QR code on a page we can update any day. A single through-line action carries from card to landing; the cold ask is web-and-email-first, with SMS demoted to an explicit opt-in; and the promise not to flood people’s phones is turned into a stated trust signal. Then we built the landing engine: a lightweight, multi-tenant-by-domain Next.js app with the first card’s landing and capture form built (first name, email with client-side typo suggestion, optional ZIP), architected to resolve ZIP to locality, send a welcome email, and feed the organization’s supporter-capture platform with source attribution, behind a spam challenge and rate limiting.
- Turns a static, unmeasurable print channel into a measurable digital funnel. Every card scan is built to become an attributed supporter record in the platform.
- The “static card, dynamic doorway” design means the organization prints once but can update the message behind the QR any day, no reprint to stay current.
- The strategy shifts the cards from education to conversion: one ask, built on the triggers that actually move people, each closing on agency.
- The engine is multi-tenant by domain and reusable across the whole card series: one system, many campaigns, all feeding one supporter platform.
print once, update the doorway anytime
multi-tenant landing engine
name · email · optional ZIP capture
attributed to the supporter system
Client name and identifying details withheld by design. Every figure here is drawn from the system we actually delivered.
More case studies
All workMembership & advocacy · Organization-wide platform
One operating platform for a 600,000-supporter organization.
ReadData architecture · Coordinated back-office systems
Four department systems that finally agree on who someone is.
ReadCommunications · Deliverability engineering
A self-hosted email operating system, built to survive Gmail.
ReadYour work would get the same discretion.
Tell us what's breaking. We'll tell you whether we've solved something like it. And if we take it on, your name stays yours.
Start with a diagnostic