Your input drives the backlog
Software for artists is usually a thing that happens to you. This is the part where it is a thing you have a hand in — and the specifics of how, so you can hold us to it.
Most product feedback forms are a politeness. The message goes to an address nobody reads, and the roadmap was decided in a meeting you were not in. We would rather tell you precisely where a report goes, so that "your input drives the backlog" is a claim you can check instead of a slogan you have to take on faith.
There is a report control at the bottom of every tool page — including the free calculators that need no account, and including this one. It takes three kinds of report.
Three kinds, and the third one matters most
Something is broken
A number is wrong, a button does nothing, a page will not load. These jump the queue — a tool that lies to you about money is worse than no tool.
Something is missing
A field you need, a tool that should exist, an export that should include one more column. Most of the backlog starts life here.
Something made no sense
Not a bug — you could not work out what the page wanted. We treat this as a defect in the software, not in the reader. It is the report type most products never ask for.
What happens after you press send
- 1
You send it from the page it happened on
The report carries the exact path and which tool you were in, so nobody has to reconstruct where you were. You do not need an account, and you do not have to leave what you were doing.
- 2
It lands in the queue as new
Not an inbox that fills up and gets declared bankrupt. A queue that can be filtered by kind and by tool, so ten reports about the same confusing screen read as one loud signal rather than ten separate annoyances.
- 3
It gets triaged, and the tool it names gets the weight
Reports cluster. When they cluster on one tool, that tool goes to the top of the list — which is the entire mechanism by which what you use most becomes what gets worked on most.
- 4
It ends as fixed, or it ends as declined
Both are real endings. Declined means we decided against it, and it stops being a thing you are waiting on. Nothing is left sitting in the queue forever to avoid saying no.
What we are not promising
A page like this is easy to overwrite. So, plainly:
- We do not promise to reply to each report. Reports are read, but there is no individual response — if you want an answer, contact us instead and say so.
- We do not promise a date. A one-line fix can ship the same week; a new tool takes as long as it takes. No ticket numbers, no fake ETAs.
- We do not promise to build every idea. Some conflict with each other, some conflict with the rules we build by. Those get declined rather than quietly ignored.
- Paying does not buy queue position. A bug reported by somebody on the free tier is the same bug.
Where else your input goes
The report control is the fast path. Two others exist and do different jobs: contact for anything that needs a conversation, and connect when what you actually need is a person — a publishing admin, a mixer, someone to pitch playlists — rather than a feature.
If you have not started yet, the shortest way to have an opinion worth sending is to use a calculator or open a free account and find the first thing that annoys you. That is a genuinely useful contribution, and it takes a minute.
Every tool page has a report control. Use it — that is the backlog.
Create your free accountEverything free (within limits) · premium for advanced access · no credit card