July is a software product that helps talent agencies manage creators and brand deals. I spent 7 months working with them as a design intern to help bring extra UI and UX polish to their platform. While working there, I designed a growth campaign that booked calls with 2 large enterprise leads (20% increase in revenue), a cross-cutting bulk actions feature, and a few pages of the platform. This case study will dive into bulk actions.

The founder of one of July’s customers reached out and described a unique issue he was facing. His company updated deal invoices bi-monthly, meaning when it was time, he would spend hours selecting deals one by one and updating invoice statuses, amounts, and dates. July’s product is largely a database—any action done in bulk would take painstaking effort by our users, which was more frequent than we initially believed.

To understand the problem, I booked calls with dozens of managers in July’s client base—each of them walked me through their day to day flows while I recorded them. I synthesized commonly used actions in a Figma file across different app surfaces.

I then moved on to create the bulk actions modal. For simplicity, I designed these flows with progressive disclosure—each bulk actions modal showed only content-specific actions, and were only revealed once the user decided complex actions were needed (beyond otherwise accessible actions like delete or archive).

After presenting my work to the team, I identified issues with accessibility, frame structure, and color usage. I then presented my finalized version to the team, and got the go ahead to start building flows.

The solution was built across 7 frequently-occurring actions: Change status, Switch talent, Switch talent (advanced), Unassign from user, Send message to talent, Download deals as CSV, and Edit invoice details.

I presented this work to the lead engineer of the company with fully functional prototypes in Figma.