Bringing clarity to a complex partner ecosystem.

Designing tools that give partners visibility into what matters and a structure built to grow with the product.

๐Ÿ’ฌ Some details in this case study have been adjusted or generalized for portfolio presentation. Core decisions and design rationale reflect the actual work.

Project

Enterprise tooling, Partner portal

Team

CTO, PM, Engineering

Scope

End to end

Timeline

Q2 2026

01_Context

The vision: answer three questions.

Before building anything, we needed to show the client where this could go. A vision prototype answered three questions about their AI coaching rollout โ€” then V1 tackled the most basic version of the first one.

โœ๏ธ Do they use it?

Adoption ยท activation

โ†’ V1 partially answers this

๐Ÿ˜ Do they like it?

Satisfaction ยท sentiment

Future scope

๐Ÿš€ Is it working?

Outcomes ยท behavior change

Future scope

02_Starting point

Start with the foundation. Ship a full experience.

We don't have enough data and insight yet to deliver the full vision โ€” so V1 starts by providing the most essential information, fully. Not a partial experience, but a complete one scoped to what we know.

Vision

Qualitative coaching insight

Full analytics โ€” outcomes, flags, recommended actions for at-risk companies

โœ… Vision prototype built for client call

V1

Full portal with key features

User Analytics, Ally Demo, Audit logs, Team management, Token management

PM on vacation โ€” worked directly with CTO to define scope

03_User Analytics

Defining what data belongs.

What's included wasn't just a design call โ€” it was a negotiation between what's defined, what the endpoint supports, and what partners actually need to see

โœ… Included in V1

Focused on billing transparency and upcoming client needs.

Total provisioned users

High-water mark

6 month trend

Total messages

Average message/user

Company overview

Users by country

Deferred metrics

Good signal, but needs further definition before we can design around it.

Activation rate

Retention

At risk companies

Session engagement

04_Role and entry points

Designing for roles we haven't built yet

Developer and Partner's Client roles weren't in V1 scope โ€” but both were kept in mind from the beginning. The role tag component accommodates new variants without a redesign, and the page structure already anticipates new entry points.

V1 has four roles. Designed for six.

Superadmin / Viewer

๐ŸŸข Shipped

Partner Admin / Viewer

๐ŸŸข Shipped

Developer

Future

Partner's client

Future

One page. Two different homes.

Superadmin / Partner Admin

Login

User Analytics

Home view

Company Overview

Company Drilldown

Detail view

Partner's client

Login

Company Drilldown

Home view

05_Log page

Built once we understood why.

The Log page was designed to let both AceUp and partner developers audit API events โ€” tracking what happened, when, and why. It seemed straightforward. It wasn't.

๐Ÿšง Challenge

Engineers pushed back โ€” and they weren't wrong. From a technical side, it made sense. But none of us clearly understood why this page needed to exist for partners.

๐Ÿš— Process

Researched partner engineer use cases, identified what they actually need when something breaks, then aligned with the Engineering Manager on scope.

โœ… Aligned

Scope confirmed. The EM meeting was the turning point โ€” it narrowed down what V1 needed to be and gave the team a shared reason to build it.

06_Navigation

Built for what's next.

When V2 made clear more tools were coming, a header wouldn't scale. Switching to a sidebar was a structural call, not a visual one. It also sets up future groupings: a Developer section for Logs and Token Management, and a Settings restructure for Account.

Current

Header navigation

Dashboard

Profile

API Docs

Ally Demo

โ—๏ธ Break with 5+ items

Plan

Sidebar navigation

User Analytics

Ally Demo

DEVELOPER

Logs

Token Mgmt

V2

API Docs

SETTINGS

Team

Billing

V2

Account

07_AI workflow

AI fully integrated into the design process.

All wireframes and iterations done with AI. Every design decision was tested with a working prototype before moving to Figma.

1โ€“2 weeks

3 days

The feedback cycle decreased โ€” details easy to miss in static design were already covered during iteration.

08_Status

V1 in motion.

๐Ÿš€ Ready for shipping

User Analytics

๐ŸŸข Design Complete

Account

๐ŸŸข Design Complete

Logs

๐ŸŸข Design Complete

โณ In progress

Token management

In progress

Ally Demo

Up next

Billing page

Future

AI Insights

Future

Let's Connect.

Interested in product design,

behavior change, AI, and building systems that scale.

studiohaena3@gmail.com

linkedin.com/in/studiohaena

See more works

ยฉ 2026 Haena Lee