LiveGig
Serious Request Management for Serious Musicians
-
3
The print friendly queue coming from watching a customer use it for karaoke instead of live sets was my favorite part. Those unexpected use cases are usually the interesting ones.
I can imagine someone asking ChatGPT for a better way to handle song requests at a bar night and finding LiveGig without even knowing it exists. At that point they're really looking for signs that people actually use it in messy real venues and not just in demos.
I'm curious if you've started noticing people describe LiveGig differently than you originally imagined after those first customers got their hands on it.
-
1
Yeah, the karaoke use case totally surprised me! I'll certainly be keeping an eye on that to see if there are more needs to meet for that crowd. (The fact that they found LiveGig, which is not designed with that in mind, says there's a need there.)
To answer your question, doing testimonials has been really interesting. I've had a tough time getting any feedback whatsoever from the organic Google signup, but the people I know personally who are using it emphasize different benefits than the ones that occurred to me originally. I'm thinking "order", they're thinking "connection" and "energy" -- great learning experiences.
-
1
That's a fascinating shift because "order" describes what the software does, while "connection" and "energy" describe why people remember using it. Those are the kinds of words that tend to stick.
It also makes me wonder whether those customer stories could become part of your discoverability strategy. When someone asks ChatGPT for a tool to run karaoke nights or manage live song requests, it's not just features that make a product stand out—it's the real-world language and experiences people consistently associate with it.
Have you thought about collecting more of those stories intentionally? It feels like they could end up being just as valuable for how people discover LiveGig as they are for improving the product.
-
1
For sure. I've got a couple of user case studies linked from the home page emphasizing those angles they valued that surprised me, but am eager to gather more. I'll likely send out some "Can I do a case study on how you're using the service in exchange for 6 months free?" emails, or just talk with people in person if more local bands pick it up.
-
1
Sean, if you’re looking to grow your organic traffic in a way that feels completely natural to your brand's journey, I’d love to help you with some outreach strategies. I prefer keeping things authentic rather than forced. If you're open to chatting about it, feel free to reach out to me at mumar @ growwithmumar. online
-
-
-
-
-
2
The karaoke example is interesting because it wasn't really feature feedback—it was someone showing you what they were trying to accomplish.
Those moments are usually more valuable than feature requests. They reveal where the product naturally wants to expand, instead of where users think it should.
-
1
The print-friendly queue turning into a karaoke sign-up sheet is such a good example of a feature getting used in a way you never planned for.
Building for that unexpected use case instead of dismissing it as an edge case is probably what makes customers stick around.
-
1
I really like this. It also feels like it has legs beyond just song requests. Once people are already conditioned to scan a code at their table or by the stage, you could use that same touchpoint for kudos/applause, tips to the band, or linking out to socials and merch. Feels like the QR code becomes a general direct line to the artist, not just a request box.
-
1
Love the transparency with the CSV export—giving users total control over their data always builds massive trust. The karaoke queue idea is brilliant, too. Have you thought about officially marketing to karaoke hosts now, or are you sticking strictly to live bands?
-
1
Sticking to live bands for now -- it's what I know best. It raises an interesting question, though; when the market signals demand, does one expand the existing product to fill that need, or keep it focused and start a different product with its own focused branding?
-
-
1
The karaoke customer might be showing you a bigger market than the one you built for. KJs run the same venue every week, which means recurring revenue and word of mouth between hosts, while gigging musicians buy sporadically and churn with their calendars. Before building more musician features, I'd interview that one customer and spec a karaoke-night mode; the niche that finds you by accident is often the one that pays.
-
1
It's a great point. Right now, I'm fortunate that my day job (which I quite like) keeps the bills paid, so I can stick with the live band focus, which is what I know and am enthusiastic about, but address other needs as they align nicely. (In this case, printing the request list can be helpful even for the sound booth or MC, even if it is still a live band playing.)
-
-
1
The CSV export decision is underrated. Most founders add lock-in features to keep users from leaving. Doing the opposite actually builds more trust, people stay because they want to not because they're trapped. The print-friendly queue is a good example of watching what people actually do with your product rather than what you built it for. The karaoke use case probably never came up in any planning session but someone just started using it that way and you noticed. That kind of observation is worth more than a dozen user interviews.
Comment