Skip to content
Properties and stack
client
ConnectMusic (via MasterBorn)
year
2026
role
Design + prototype
team
Only designer, with a PO, a front-end dev and a back-end dev

Stack

design
  • Figma
  • Claude Design
frontend
  • Next.js
  • React
  • shadcn/ui
  • Tailwind CSS
tools
  • Claude Code

Deal Management System all-in-one

Overview

ConnectMusic is a music publisher. Deal360, its internal app, values song catalogs and runs publishing deals from first contact to underwriting sign-off, across three roles, including sales and the underwriter.

It’s an internal tool, so there’s no public link. The data in every shot is made up.

Biggest challenge

Tight timeline, small team and three roles to cover, each with different needs. On top of that, the app had to replace a lot of third-party tools in one solution, to take away the friction of switching context between YouTube Studio, Luminate (goated tool to review music data in-depth) and the others.

How I’ve used AI here

We started with a pretty basic process in Figma to set the direction and the high-level UX patterns, plus a few (many :P) workshops to map the needs of each role.

Once the project had a proper set-up in the codebase, I dropped Figma completely. I prepared screens in Claude Design and later in Claude Code, and delivered almost ready-to-merge code for each feature. Our front-end developer reviewed it and checked it against the API contracts, so we could connect it to the backend.

It was also the first project where I worked this closely with a back-end developer. I had to understand the limitations and the way they work to design things that were doable. I ran a Docker image of the backend on a seeded database for the first time, too.

AI wrote the prototype code. The layout, the interactions, the copy and which states exist were my calls. The longer story is on How I work, and still no AI slop, I promise.