What should we build next?

Everything here starts as somebody describing a job they were sick of doing. Send one in, and if it gets built you get the tool, the prompts and the repo, the same as everybody else.

Route one · Becomes a build

A job you are sick of doing

Describe the task, not the tool you think you want. What happens now, how long it takes, how often. The best requests are the boring jobs that eat a Tuesday, and the ones that get built ship as a free repo with the prompts attached.

The task, in your words What happens now, and how long it takes

Times a month

Your function

Email, so you hear when it is built Where did you hear about us? Join our newsletter (you can opt out at any time)

Route two · Becomes an answer

A question, rather than a job

Is this worth automating at all. Am I allowed to put that data in it. Where does somebody who has never done this start. The questions that come up most often turn into published answers, so asking once helps everybody who never got round to it.

Keep it general

Ask about the problem, not the people in it. No company names, no employee names, nothing about a live grievance or investigation. That work belongs with your HR advisers and your lawyers, and a tool built from one case would be no use to anybody else anyway.

Use the form above

Answers are published anonymised where more than one person would find them useful, and never with anything that identifies you or your employer. Nothing here is legal advice, and where a question needs a lawyer the answer will say so.

What happens to what you send

Every one gets read

One person, no team, no ticketing system. That is the limit on how fast this can move, and it is also why the answers are worth having.

Nothing is published without a yes

If what you sent would make a good build, you get asked first. Silence is a no. Anonymous is always an option and it costs you nothing.

Nothing is sold to anyone

Not to vendors, not as a list, not as research a sponsor paid for. Sponsorship goes through partners@ and never touches this.

Asked for, then built

The queue is public even when the questions are not

Every build names the problem it came from, so nobody has to take anyone's word for it that requests turn into things.

Nothing has been built from a request yet, because nothing has been published yet. This list fills from the first issue onwards, and it starts empty rather than starting with something invented.