Internal · Admin
One customer. Three teams. Shared data.
The admin panel is an internal tool for Finance, Customer Success, and Deliverability. Daily work crossed teams. The data did not. I designed the surface they could share – not a restyle of a private list.
Silos were the product bug
Customer Success held account settings and overages. Deliverability held ecosystem health, ISP reports, and delivery reports. Finance held NetSuite invoices and consolidated cluster data. Soft bounce, complaint rate, and blocks sat between CS and Deliverability. Renewals, contract changes, and trailing overages sat between CS and Finance. Deliverability and Finance had no overlap. No shared workspace connected all three teams.
I was the UX designer: interviews with those internal teams, user flows, wireframes, and hi-fi. The brief was to understand the frustration, then design a surface they could share. The outcomes reported here are specific to the admin-panel work.
Constraint
Feasible for engineering. Viable for the business. Usable for Maropost employees.
Any data visualisation had to be technically feasible—either built in-house or supported by a viable third-party tool. Ease of use for internal teams was non-negotiable. The viable solution had to balance technical feasibility, business value, and usability—not simply produce a prettier table.
The workspace is customers, not campaigns
The first iteration introduced a customer table (ID, business name, email, created date, and actions) and an Add Customer action. The form asks for business name, account number, success manager, deliverability manager, package plan, subscription dates, licence hours, CRM, and a Stripe URL – because those teams already needed those fields in one place.
The Edit Customer view is organised into Profile, Address, and Subscription. Subscription shows plan, billing frequency, renewal, and monthly usage with export. Haymarket Media is the working example in the file.
