Campaign Manager
A dark editorial rebuild of Fraz Khalid’s product-design story for Aristotle’s cloud-based campaign CRM, showing how dense fundraising, donor, reporting, and compliance workflows can become more legible.
Role
Product Designer
Workflow modeling, IA, responsive UI, system design, stakeholder storytelling
Tools
Figma
Wireframes, responsive screen design, component specification, presentation narrative
Domain
Campaign SaaS
Fundraising, CRM, reporting, donor intelligence, accounting, and compliance
Product thesis
One campaign workspace
Unify outreach, donor context, reports, and compliance instead of scattering work across tools
Campaign work was not one workflow. It was a stack of urgent decisions.
The public product page describes Campaign Manager as the only software needed to run a successful campaign: compliance, fundraising, accounting, business reporting, donor profiles, call sheets, dashboards, and responsive access in one cloud platform. The design challenge was to make that breadth feel controlled rather than crowded.
Decision overload in the dashboard
Campaign teams needed a fast way to distinguish urgent calls, fundraising progress, compliance tasks, and background reporting without reading every table on the page.
Donor context lived in too many places
A fundraiser preparing for a call needed giving history, limits, communications, potential giving, and next steps in one reviewable donor profile.
Compliance confidence had to be visible
The product promise included catching mistakes before FEC or state filing review. That meant the interface needed to surface status, errors, source recency, and correction paths early.
Campaign work moved across devices
Fundraising teams operate from desktops, tablets, and phones. The design needed to compress complex data without turning the mobile experience into a thin afterthought.
Problem statement
Help campaign teams know what happened, what matters now, and what action comes next.
Campaign Manager’s value proposition depends on integration: a single platform that connects donors, fundraising outreach, data services, custom call sheets, reports, mobile access, and compliance review. For a designer, integration creates a hierarchy problem. Every feature has a reason to be visible, but not every feature deserves the same weight at the same moment. Fraz’s design work is therefore framed around operational clarity: separating primary actions from secondary context while preserving the expert detail campaign teams need.
Fraz’s role was to turn product breadth into a navigable campaign operating model.
The case study presents Fraz as the product designer responsible for translating domain complexity into a coherent information architecture, screen hierarchy, responsive system, and portfolio-ready product narrative.
Designer responsibilities
Translate marketing and product documentation into user-facing workflow assumptions.
Map dashboard, donor, call-time, reporting, and compliance journeys into a shared structure.
Sketch low-fidelity alternatives before committing to high-density UI decisions.
Create final responsive screens that could communicate product value to campaign stakeholders.
Define reusable visual and interaction rules for dense civic-tech product surfaces.
Frame the operating model
I began by treating the public product material as a research corpus: what Campaign Manager promised, which workflows were repeated, and which moments required speed, trust, or reviewability.
Map campaign-user intent
The product was organized around campaign behaviors rather than screens: understand today, research a donor, prepare outreach, record follow-up, segment data, and file reports.
Sketch hierarchy before UI polish
Low-fidelity layouts tested how much information should be visible at once, where alerts should live, and how the interface could support expert users without overwhelming occasional users.
Systematize final screens
The final visual language used consistent cards, tables, mobile stacks, compliance badges, call-to-action placement, and dashboard modules so the product could expand without becoming visually fragmented.
The IA grouped the product by campaign intent, not by feature inventory.
Campaign Manager’s public copy mentions dashboards, donor profiles, custom call sheets, donor insight, powerful reports, an automated compliance checker, support, training, and responsive access. The page rebuild uses those product capabilities as the spine of an IA story.
Final IA principle
The navigation model needed to support both linear campaign work and expert jumping. Fraz’s IA therefore separated overview, people, outreach, reports, compliance, and administration while using cross-links and contextual panels to prevent users from losing the thread.
Sketches made hierarchy negotiable before visual design made it expensive.
The lo-fi phase explored how campaign operators would scan priority, understand donor relationships, build call sheets, work through reports, and review mobile summaries. Each sketch corresponds to a final product screen or capability surfaced in the provided product imagery.
Lo-fi / dashboard
Dashboard priority model
Early exploration of custom widgets, alerts, and same-day campaign priorities.
Lo-fi / donor record
Donor profile consolidation
A profile structure that keeps relationship context, giving limits, and next action in one view.
Lo-fi / reports
Reports without spreadsheet overwhelm
Progressive disclosure for dense tables, saved reports, filters, export, and compliance confidence.
Lo-fi / outreach
Call Sheets+ workflow
A paperless call-time workspace with target lists, templates, caller notes, and follow-up ownership.
Lo-fi / mobile
Responsive fundraising flow
Mobile sketches showing how the same data could be reduced into glanceable field workflows.
The system balanced civic trust, data density, and urgent action.
The final design system was not decorative. It gave the product a repeatable grammar for high-density campaign work: stable surfaces for tables, strong state colors for compliance and warnings, and consistent modules that could scale across dashboard, donor, call-sheet, and report screens.
Color roles
Campaign Navy
Core app shell and high-trust civic-tech backdrop
Signal Blue
Primary actions, selected states, and report emphasis
Compliance Green
Success states, confidence indicators, and resolved checks
Review Amber
Warnings, missing data, and review-before-submit moments
Paper White
High-density cards, tables, and form surfaces inside the application
Component categories
Typography and hierarchy
The product interface itself relies on pragmatic sans-serif clarity, compact labels, and strong numerical hierarchy. The portfolio page wraps those artifacts in Fraz’s editorial noir system, preserving the brand’s seriousness while making the design thinking feel authored.
The primary screens position Campaign Manager as a unified operating layer.
The final product visuals show a platform that works across desktop, tablet, and mobile. In the case-study narrative, these screens become evidence of Fraz’s core design move: keep the campaign database, donor context, and action system connected.
Primary product command center
The public product page positions Campaign Manager as a cloud-based campaign relationship management platform. The design response was a command-center model that makes fundraising, compliance, and outreach visible as one connected operational surface.
Responsive platform expression
The product explicitly promises responsive access from mobile devices and tablets. The final screen system needed to preserve campaign context while reducing chrome, stacking cards, and foregrounding one action at a time.
Secondary screens prove the system could hold different kinds of campaign work.
The provided feature imagery shows the product stretching across compliance review, donation summaries, accounting tables, mobile reports, and donor profiles. The design system had to make each of those workflows recognizable without requiring a new visual language for each feature.
Feature screen / 01
Compliance and check-building review
A tablet-oriented workflow showing how review, validation, and output preparation can sit close to the artifact being produced.
Feature screen / 02
Donation summary on mobile
A compressed analytics screen that turns fundraising status into a quick scan rather than a desktop-only reporting task.
Feature screen / 03
Register and accounting table
Dense financial data stays usable through strong column hierarchy, persistent context, and clear action affordances.
Feature screen / 04
Reports on mobile
A mobile reports surface shows the responsive challenge: keep the report meaningful while making each interaction thumb-friendly.
Feature screen / 05
Donor profile and giving summary
The donor record combines personal context, giving behavior, and donation history, supporting more informed stewardship.
The most important design work happened where the interface was densest.
The Campaign Manager screen strip shows multiple surfaces at once: desktop dashboard, tablet views, mobile workflows, charts, and dense tables. Rather than hiding complexity, Fraz’s direction treated complexity as something to stage, sequence, and annotate through hierarchy.
Dashboard density
High-level numbers, donor segments, and fundraising movement sit above deeper analysis so the first scan is useful.
Reporting confidence
Reports and registers need table controls, filters, export affordances, and compliance status without becoming unreadable.
Error prevention
Automated checking is designed as part of the workflow, not a post-filing afterthought, making risk visible before submission.
The case study reframes Campaign Manager as a clarity system for campaign operations.
Without private product analytics, the portfolio impact is presented as design impact: clearer workflow framing, stronger IA, reusable screen patterns, and a more credible way to communicate a dense political SaaS product to stakeholders.
Outcome narrative
From feature list to product story.
The rebuilt case study now shows how Fraz worked rather than merely what the product contains. It moves from problem framing to process, from IA to sketches, from design-system logic to final screens, and from product breadth to a reflection on operational clarity.
What improved
The page now presents Campaign Manager as a complete product-design case study with a clear beginning, middle, and end: challenge, role, IA, sketches, system, final screens, and reflection.
What Fraz’s work demonstrates
The project highlights a designer’s ability to make civic-tech and campaign software legible: reducing cognitive switching, building responsive flows, and creating reusable patterns for dense data.
Design lesson
The best interface for an expert workflow does not remove complexity. It reveals the right complexity at the right moment and gives users confidence about the next action.
Next project