Nightingale: audience and demand research

Use the launched product as it is and invite a few interested people who keep their own music library to try it with songs they choose. Observe setup through an actual sing-through, then whether they voluntarily try another song or return; note where they need help or corrections. Keep recruitment narrow because the founder's actual available time and recruiting capacity are unknown.

Why this test: This observes meaningful use of the core job, rather than relying on stated interest. It can also reveal setup and song-quality friction without requiring a new build or assuming that a landing page, interview, or deposit is necessary.

Success signal: Participants reach a real sing-through using their own tracks, and their actions show whether they choose to continue or return; record setup failures, correction effort, and reasons for choosing this over a workaround. This is a learning signal, not a pass threshold.

Counter-signal: The early signal sits alongside alternatives for catalog karaoke, user-created song libraries and editors, and tools for turning supplied tracks into karaoke media. The scan does not establish which option people prefer; the reported lyric drift also makes output quality a relevant early uncertainty.

Candidate segment to examine: Karaoke hobbyists who maintain a personal digital music library, possibly through a home media server, and want to sing songs they cannot readily find in standard karaoke catalogs.

Why examine it: This is a direction to examine, not a selected niche: it fits the described library-based workflow, and early anecdotes mention limited song coverage and using video sites as a workaround. Whether that frustration leads people to install and use a local app remains unproven.

Key assumption: People with their own music have a strong enough karaoke coverage or use-case problem to set up local software and tolerate song-by-song processing, rather than relying on catalog services, video sites, or custom-song workflows.

Why it matters: This assumption links the product's distinctive owned-library workflow to actual setup and use. Interest in the concept, or the founder's stated product capabilities, does not establish that behavior.

Local, per-song processing and track-dependent lyric alignment may make first use uneven. One firsthand tester reported lyrics drifting during playback, and the developer acknowledged that alignment and transcription can vary by song.

Consequence: If setup or song output disappoints on a user's first chosen track, people may stop before a satisfying session or choose an existing alternative; feature breadth alone would not establish adoption or repeat use.

Early check: During first-use observation, note whether people complete setup and a sing-through with their own varied tracks, how often they need to fix lyrics or timing, and whether they choose to continue or return.