Requesting a feature

Send feature requests through either route in How to get help. There is no separate portal to sign up for.

Describe the problem, not the feature#

The most useful requests describe the situation you are stuck in and leave the solution open.

A request for a specific screen or button tells us what you think the answer is. A description of the problem tells us what the answer needs to do, and fairly often there is a better one, or one that already exists somewhere you did not think to look.

Worth including:

• What you are trying to accomplish, in business terms
• What you do today instead, including the spreadsheet or the workaround
• How often it comes up, and how long it costs you each time
• What it costs you when it goes wrong

That last one carries real weight. “This would be nice” and “we lost recoverable commission last quarter because of this” are both honest answers, and they get read very differently.

What helps your case#

Say whether it affects your clients or just your team. Something that blocks a client organization from doing its own work is a different category from an inconvenience in your back office.

Say how many of your clients hit it. A pattern across your roster is stronger evidence than a single account, and much stronger than a hypothetical.

Say if there is a deadline. A contractual commitment or a migration date changes how a request gets scheduled. One nobody knows about cannot be planned around.

What you will hear back#

Modero is built by a small team, which means saying no to good ideas that belong in a different product. Expect one of three answers, and we would rather be blunt than vague:

• We are building it. Usually with a rough sense of when, not a date.
• Not now. A fair request that is not close to the top of the list. If we say this, it is genuinely recorded, not filed away politely.
• Not this. Outside what Modero is for. You will get a reason, and a suggestion of something that does do it where we know of one.

We will not tell you something is coming when it is not. A roadmap you cannot plan against is worse than a clear no.