I built a tiny birthday tool and learned that small products need stricter boundaries

I’ve been working on a very small web tool: a page where someone can create a birthday song with a name and share it quickly.

The product itself is simple, but the interesting part has been deciding what not to add.

For this kind of tool, the user is probably not looking for a full music editor, a dashboard, or an account. They may be on a phone, trying to send something personal to a family member, classmate, coworker, long-distance friend, or someone in a group chat.

So I kept the flow narrow:

1. enter a name

2. create the result

3. share it

The hard part is resisting all the obvious “maybe later” features: templates, public galleries, reminders, profiles, editing tools, saved projects, and social sharing pages. Some of those may make sense eventually, but they also make the first version heavier.

Here is the project: ai birthday song with name

My current rule is: if a feature does not help the user finish the birthday greeting faster, it should probably wait.

Curious how other indie hackers decide when a small tool should stay small, and when it is worth turning it into a bigger product.