The reason I agreed about the new production cues is because they can be had anywhere...including the AZB Marketplace. The only potential benefit to AZB members is perhaps a lower price than is already out there, but honestly, they can only go so low before violating their agreement with whichever company they are offering....so there is no real advantage to keeping them....there are plenty of places to buy a new production cue. I am not targeting all production cues...just the new ones. Many of the older models have actually gained in value over the years, and there are faithful collectors to many brands.
Customs are not as readily available, can be almost impossible to get from certain makers, and the places they can be found are much, much more limited. Example: Brent most often posts up in the Cue Gallery cues he has completed for a customer. It can take a while to get a cue from him. The last cue he posted an actual FS ad for, was one leftover from the most recent cue show. Brent does not typically have available cues for sale, because he has developed a following. This was an opportunity for someone who may have wanted one of his cues, but maybe didn't want to wait, or it had the exact woods in it that they liked...to purchase one. It rarely happens, was really no big deal, and he contributes to AZB frequently. He's not abusing the system. There are others who do...some posting a half dozen or more cues a month. They are relying on the AZB W/FS as part of their business plan...which, IMHO, is a huge mistake.
Look, the solution is pretty simple actually. I can think of a few cue and case makers who have not relied on the W/FS to drive their sales. Instead, they post up photos of a cue or case they have just completed, often for a customer....in the Cue Gallery. A picture is worth a thousand words. Throw in a few testimonials....and sales are generated.
BTW...I believe you posted earlier in this or another thread about derogatory/negative comments being made concerning pricing/condition of an item for sale. It is already a rule that this type of behavior is not condoned in an active W/FS thread. If you see it happening, you need to report it.
Lisa