What comes back
Not a summary. Not a sentiment score. A decision, with the reasoning attached.
It says what the person wants, and whether they are serious, because people joke, test and vent. It says why they want it, if they said. It judges whether your product actually needs it, measured against your own description of what your product is for rather than against how loudly they asked. And it judges whether the person asking is the customer you are building for, because sometimes they are not, and building for the wrong person is worse than building nothing at all.
Then it says what it would change, and roughly where.
You read three numbers and a paragraph. You say yes or no. That is the entire review.
Two gates, both yours
The first gate is the decision. Nothing is touched until you accept it. Reject it and it is gone.
The second gate is the change itself. Onsay reads everything people said together, finds the gap underneath, and proposes a change that closes it, often one idea that answers several requests at once rather than five disconnected fixes. Approve it and it is built on your schedule. Weekly by default. Or immediately, or monthly, whichever suits how you ship.
Nothing ever goes live on its own. The work arrives finished and waits for you.
Why the judgement matters more than the code
Every tool that writes code from a description has the same problem. The description is the hard part. Somebody still has to decide what is worth doing.
That decision is the thing Onsay is actually for. When four people ask for the same thing in four different ways, that is one piece of work and not four items on a list. When somebody asks for an enterprise integration and you sell to freelancers, the useful answer is no, with the reasoning written down so you can spot it if it keeps happening.
You see the reasoning before a line is written. That is the whole reason it exists in that order.
Getting what people say into it
- A small box on your site. One line to add it, and it cannot collide with your styling.
- Paste it in yourself. Something from a call, an email, a message someone sent you at eleven at night.
- Send it from anything that can make an HTTP request. Point your support inbox at it.
You do not need the box to start. Paste in the three oldest things anyone has told you and see what comes back.
What we keep
What we need to make the decision and do the work. We do not keep a copy of your source. The box takes an email address only if the person types one, and only so you can reply to them.