Back

SaaS

gigmelon

gigmelon

Book gigs and find talent. Performers and venues connect directly, and you only pay when you book.

Role

Designer and developer

Duration

Feb 2026 to present

Services

Product design, Web development

Status

Final stages

gigmelon dashboard where venues and performers book a gig.
gigmelon dashboard where venues and performers book a gig.
View live

Overview

Book the gig, then pay

Performers and venues find each other directly. Posting a gig is free, there is no subscription, and you pay when the booking is made. Venues, private events, and performers each move through the same path: profile, discover, book, then play.

gigmelon booking overview for venues and performers.

Problem

Gigs still get booked in a group chat

Venues chase last-minute cancellations through Facebook messages. Performers chase the next room the same way. Someone in the middle takes a cut for an introduction. gigmelon is a marketplace where a bar, a private event, and a performer can find each other directly. Posting is free, there is no subscription, and you pay when a gig is booked.

Research

Three people, one booking

The same product has to make sense to a bar booking Friday music, someone planning a wedding, and a trio looking for the next room. Those became three doors into one path: a profile, a way to discover, a booking with a conversation attached, then the show. Venues want reliable talent and a price they can see. Performers want to set their own rate and get paid when the gig happens. Private events want to compare acts without a dozen email threads.

gigmelon research on how gigs get booked.

Ideation

The booking is the product

A feed of talent looks busy and does not book a Friday. The versions that mattered were the plain ones: a profile with a rate and a city, a request, a message thread, and a status that says pending or confirmed. A suggestion can point a jazz trio at a room, but a person still sends the request. The conversation, the date, and the payment stay in one place so the booking does not fall back into a chat app.

Designs

A dashboard for both sides of the gig

The site walks both sides through the same four steps: profile, discover, book, then play. The product itself is a profile with availability and a fee, a search with a city and a budget, and a message list where a request becomes a confirmed date. The interface is dark navy with a purple accent, closer to a room at night than to a generic dashboard. It is in the final stages, so the work is that loop, not a pile of customers.

gigmelon dashboard designs for both sides of a booking.

Lessons

Free to post, paid when it happens

A subscription would ask venues and performers to pay before they trust the booking. Taking the fee when a gig is booked matches how the work already gets paid. The other lesson was to keep both sides in one product. A performer tool and a venue tool that drift apart is how a marketplace dies. Profile, request, message, confirm. If that loop is obvious, the rest can wait.

More apps I've created

All work

Callum O'Connor

I'm a product designer who makes complex experiences feel simple.

© 2026 Callum O'Connor

Callum O'Connor

I'm a product designer who makes complex experiences feel simple.

© 2026 Callum O'Connor

Callum O'Connor

I'm a product designer who makes complex experiences feel simple.

© 2026 Callum O'Connor