Payback
Payback
Product Designer
2025-2026
About Project
Payback runs on partnerships and every partnership runs on briefings. What started as a way to organize a single process grew, briefing by briefing, into the operating system for how Payback and its partners work together. Sales ops, partner managers, admins: different roles, different needs, one shared source of truth.
The platform wasn't designed to impose structure from above it was designed to reflect how collaboration already happened, and simply make it visible, fast, and accountable.
- Enterprise platform design
- Workflow & role-based UX
- Systems integration design
One briefing,
four responsibilities.
A briefing moves through the same five stages for everyone, but each role only sees the part it owns. The audit log runs underneath the whole thing, so no step is ever anonymous.
Roles, and what
each one can touch.
Permissions were drawn before screens were. Sales ops carry the widest day-to-day access, partners reach only their own records, and admins hold the platform-level actions — integrations, roles, escalations — that nobody else can bypass.
Designed for trust in every action,
turning collaboration between partners into something
clear and accountable.
01. Framing the Challenge
Research began inside the chaos of manual coupon creation; thousands of coupons a month, shared spreadsheets, no real audit trail to identify where a structured system could remove friction without removing flexibility.02. Designing the Product
Interfaces were shaped around roles, not features giving admins, sales ops, partners and partner managers each a workflow suited to their responsibilities, while keeping every action traceable through a shared audit log.03. Scaling the Solution
The platform launched as a focused tool and expanded in phases, growing new integrations and briefing types as adoption spread from internal teams to daily use by external partners.
