This is the one we are building. You connect nine71 once and
pick a page. A database appears, and every demo that reaches your inbox
becomes a row in it, measured and kept current as we learn more
about the track.
Notion database sync
In build
Your views, filters, boards and assignees keep working, because it is an
ordinary Notion database. These are the columns, and every one of them is
something we measure rather than guess:
| Column | What it is |
| Track, Artist | As the artist submitted them. |
| Fit | How close the audio sits to your catalog, 0–100. Measured on the sound, never on the name. |
| Closest record | Which of your own releases it lands nearest. |
| BPM, Key | Measured from the file. |
| Loudness, True peak | LUFS and dBTP off the master. |
| Released already | Whether the recording is out somewhere. |
| AI markers | What the audio shows, stated as what it is and never as a verdict. |
| Sent before | Whether you have already been sent this record under another name. |
| Sound | A plain sentence about the record, written from the measurements. |
| Open in nine71 | A link straight to the track, to play it and see the full read. |
| Received | When it arrived. |
What we can see is what you pick. Notion asks you which
pages a connection may open, and only shows you pages you have full
access to yourself. We get those and nothing else. Not your other
databases, not your team's documents.
It reads one way. What you type in Notion stays in
Notion. Editing a Fit number changes your dashboard and changes nothing
about how we score anything, for you or for anyone else.
No date on this yet, and we would rather build it with one label than
guess at the shape. If your A&R lives in Notion, say so at
support@nine71.ai
and you are that label.