The request board is not a feature-voting page bolted onto a finished product. It is where the product comes from. Detector, the PDF editor and signature verification were all requests before they were tools.
The loop
- Someone describes a workflow on the public board — in their own words, not as a spec.
- We estimate it in public. If it is a week, we say a week. If it is not something we should build, we say that instead.
- We build it and ship it to the requester first, behind their account.
- It goes on the platform once it survives contact with real documents.
Nothing is charged until step three has already happened.
Why this order
The usual order is to charge first and build second, and it produces software that is easier to sell than to use. Building first is slower and it is a worse business on paper. What it buys is that every tool has at least one person who needed it badly enough to describe it, and that person used it before anyone else was asked for money.
That constraint has killed more ideas of ours than it has shipped, which is roughly the point.
What to do with it
If there is a document workflow you keep doing by hand, describe it on the board. The worst outcome is a public answer explaining why it is a bad fit — which is still a faster answer than a sales call.