Request a Tool

What makes a useful tool request

A strong request begins with a real recurring problem. It should describe a task that currently requires repeated manual work, several separate websites, a script, a spreadsheet formula, or a confusing technical process.

The best ideas have a defined input, a predictable transformation, and a clear result. Examples include validating a structured value, generating a secure identifier, converting between formats, comparing two data sets, or formatting content for another platform.

Information to include

To submit a useful request, explain:

• The problem the tool should solve.
• Who would use it and in what workflow.
• The expected input format.
• The expected result or downloadable output.
• Important settings, limits, and validation rules.
• Whether processing must remain local or offline.
• A realistic but non-sensitive example.

How requests are evaluated

Tool ideas are assessed by usefulness, likely demand, implementation difficulty, maintenance cost, privacy and security impact, SEO potential, and whether the feature can reuse an existing Trexmi workspace. Reusable tools with a clear audience are more likely to be prioritised.

A high priority request is not automatically accepted. The team may adjust the scope, combine related ideas, or postpone features that depend on unreliable third-party services.

Requests that may be rejected

Trexmi will not build utilities intended to facilitate abuse, unauthorised access, malware, surveillance, evasion, credential theft, dangerous activity, or infringement. Requests may also be rejected when they require copyrighted content, unstable scraping, restricted APIs, excessive infrastructure, or a full application rather than a focused tool.

How to submit your idea

Email hello@trexmi.com with the subject “Trexmi tool request.” Use the structure above and include one concise example. Do not attach confidential files or production credentials.

Before submitting, browse the current tool catalogue to confirm that a similar utility does not already exist under another category.

What happens after submission

Requests may be added to an internal product backlog, grouped with similar ideas, or used to improve an existing tool. Submission does not guarantee implementation, a specific release date, or an individual reply. Particularly useful requests may be clarified before development begins.