Turning a birthday song project into a broader song-gift product

I started with a simple birthday-song product.

At first, I thought people were mainly buying a generated audio file. But after seeing how people used it, the pattern felt a little different: they were trying to turn a personal memory into something more emotional than a card, a playlist, or a generic gift.

That led me to build WrapASong, a product for turning personal stories into custom song gifts: https://wrapasong.com

The idea is simple: someone writes a short personal story, gets custom lyrics, generates two song versions, and then shares the final result as a gift page.

Right now I’m testing a few occasion-based flows:

- birthday songs

- Mother’s Day songs

- anniversary songs

- love songs

- wedding songs

I’m learning that the occasion matters a lot. “Generate a song” is too broad. “Make a song for Mom before Mother’s Day” or “turn your anniversary story into a song” is much easier for people to understand.

The product is still early. I’m currently working on:

- making the creation flow feel less intimidating

- improving the first story prompt

- figuring out which occasion converts best

- making the final gift page feel worth sharing

- learning whether old birthday-song customers are interested in the broader product

The hardest part so far has not been the generation itself. It has been positioning. A custom song can sound like a novelty, but the real value is the emotional context around it: the story, the recipient, the occasion, and the final shareable gift.

I’d love feedback from other indie hackers:

- Would you position this as a gift product, an AI music product, or something else?

- Would you lead with one occasion first, like Mother’s Day, or keep the product broader?

- What would you want to see before trusting a product like this enough to buy?