One request, three tiers of voter. See what it scores plain and weighted.
- Votes, plain
- –
- Votes, weighted
- –
- Share of the weight from paying voters
- Demand, plain and weighted
- –
- Priority, plain and weighted
- –
What is the formula?
Three lines, read out of our own source rather than described from memory.
A weighted vote is the voter's tier multiplier instead of 1, so a customer on a multiplier of 20 counts as twenty votes and a free account counts as one.
Demand is votes * 3 + comments * 2 + round(views * 0.1), and it runs on the weighted total when the project turns weighting on, on the plain count when it does not. Priority is demand divided by effort, where effort is 1 for a few hours and 5 for a month or more.
That is the whole model. There is no machine learning in it, no hidden term, and nothing that changes behind your back.
How does a vote get connected to a paying customer?
By the plan the voter is on, which has to come from somewhere real.
Stripe and Paddle put it there automatically, a CSV import puts it there in bulk, the API puts it there from your own billing, and a person can set it by hand. A voter with no tier stays at weight 1, so an anonymous board behaves exactly like an unweighted one.
Should the weighted number replace the plain one?
No, and that is why both are on the board.
The plain count is how many people want it. The weighted count is how much of your revenue wants it. A request with forty free votes and no paying customers is still telling you something, usually about who you are attracting rather than what you should build next.
Seven of the twenty one tools we priced weight votes this way, so it is not rare. What none of them publishes is the arithmetic, which is the reason this page exists.