“Start the bridge more quietly” is a useful rehearsal note until it disappears into a group chat between a venue address and a photograph of somebody’s dinner.
A focused rehearsal tool could connect notes, recordings and the next session. Treat that as a hypothesis about coordination, not a proven market gap.
Follow one note through time
Ask a small group how feedback is captured, shared and used at the following rehearsal. Does the problem concern finding the note, agreeing on the change or practising it individually? Those lead to different products.
A generic document may already be sufficient. The opportunity needs a repeated failure with a consequence the group cares about.
Keep the first prototype narrow
Try a set list with time-stamped notes and links to recordings the group owns or has permission to use. Avoid building a music catalogue or distributing copyrighted material as a shortcut to content.
Test how a member who missed rehearsal catches up. The workflow should not require everyone to adopt a complicated new system before any value appears.
Budget for the actual medium
Audio storage, upload reliability and sharing permissions can create more operating work than a text-only prototype suggests. Start with bounded file sizes or external links where appropriate, then measure actual needs before promising unlimited media.
The return event is the next rehearsal. Inspect whether notes are found and acted on there, rather than celebrating daily app opens between sessions.
For distribution, a useful demonstration tailored to one kind of group may be more informative than broad “collaboration app” positioning. Seek feedback with permission and respect the group’s time.
Reject the idea if the real problem is interpersonal agreement rather than lost information. Software can preserve the note. It cannot make the drummer agree with it.