Require a piece count
Make it a requirement when post new projects that an approximate piece count be added to the listing so when someone supports the project and is asked to say how much they would pay, we have a better idea of what the cost of a set would be based on the number of pieces
Mark Bellis commented
A requirement only for projects reaching 10000 votes. When building a real model, I don't count the pieces in and out; there is so much trial and error that I would lose count.
The rules say a model cannot have more than 3000 pieces so the nearest 500 should do for large models. An idea of price is no more accurate than that anyway; the professionals have to work to price points for the final set but there might be changes from the fan model. Experienced builders can look at a model and guess!
RuBrick's Cube commented
When entering a project, it would be required to enter an estimated brick count. The moderators could decide if the count is accurate or not.
I believe a piece count should be optional. Just in case users couldn’t keep track of how many pieces their product ideas have, they could just leave that field blank.
I agree with Carter Johnson on this. Plus we don't have to take the serve anymore.
I completely agree with Carter Johnson. Lego often drastically redesigns sets (like ship in a bottle) changing the piece count anyway. As long as the model's not too big, it shouldn't be an issue. We no longer have to guess price in the fan survey now anyway.
Carter Johnson commented
This is a good idea, but also a bad idea. For people who use software like LDcad and LDD it is very easy to acquire a count, but people who have built amazing things in real life would have to tediously disassemble their builds and then count every piece one by one to get an accurate measure. The only two benefits I can see to this would be the ability to judge price, but it isn't very difficult as-is, and the ability to estimate how long it would take to build the kit. which is also not that much of a problem.