Skip to content

How feature requests work here

Started by MarketPadHQ Team0 replieslast activity 1 week ago Pinned Closed

MarketPadHQ Team

This room is not a suggestion box that nobody reads. Here is what actually happens to a request. Post one idea per thread, with a title that describes the outcome rather than the mechanism. "Let me see which campaign a contact came from" is a better title than "add a field to the contact table" — the second one has already picked the solution, and it might not be the right one. The most useful thing you can include is the problem behind the request: what you are doing today instead, how long it takes, and what it costs you when it goes wrong. That is what lets us tell two requests apart when they sound similar but are not. If a thread already exists for your idea, reply to it rather than starting a second one. A thread with fifteen replies explaining fifteen different situations is far more persuasive than fifteen separate threads. What we do with them: we read every one. Some get built. Some get built differently from how they were asked for, because the underlying problem turned out to have a better answer. Some do not get built, and when that is the decision we would rather come back and say so in the thread than let it sit there unanswered for a year. Announcements is where shipped work gets written up, and where we link back to the request thread it came from. Locked because it is a reference. Post your request as a new thread.

This topic is closed for replies.