Skip to content
Toolspike

Request a tool

Tell us what is missing

The most useful requests describe a problem rather than a feature. What are you trying to do, what do you do instead at the moment, and how often does it come up? A tool that can run entirely in the browser is far more likely to be built.

Request details

What you would call it, for example “Rotate PDF” or “YAML to JSON”.

What you are trying to do, what you do instead today, and how often it comes up.

Only if you would like a reply. Leave it empty otherwise.

What gets a tool built

The requests that turn into tools describe a job rather than a feature. “I get a weekly export where the dates are in the wrong format and I fix them by hand” says far more than “add a date converter”, because it carries the input, the output and the reason the existing tools do not cover it.

Say what you do at the moment. If the answer is a spreadsheet formula, a desktop program or a site you would rather not upload to, that tells us what the tool has to beat. Say roughly how often you need it, too — something faced weekly is worth more than something faced once.

One thing worth knowing: most tools here run entirely in your browser, which rules some things out. Anything needing a licensed engine, a paid data source or a server that holds your files for a while is a poor fit, and saying so up front is more useful than a request that quietly cannot be built.