Onsay Start free

You are support, product and engineering. All of you is behind.

The bottleneck is not how fast you type. It is deciding.

Onsay reads what your users tell you, works out which of it is worth doing, and writes the change.

Free to start. No card.

A user said

“the export button is hard to find, i looked for five minutes and it was under settings which is not where i expected it”

Onsay decided

Export is hidden in the wrong place

Worth doing 80% Your customer 90% A real request 95%

Onsay wrote this

- <SettingsPanel item="export" />
+ <ReportsToolbar>
+ <ExportButton format="csv" />

You approve it before any of it ships

When you are one person, what users tell you is not a resource. It is an interruption with guilt attached.

You read it because you should. You cannot act on most of it. The part that would actually help, working out which three of the forty things matter, takes the most attention and you have the least of it.

So you build whatever was mentioned most recently or most loudly, which is not the same as what matters.

Start to finish

One person said one thing

They said

“i wish this integrated with salesforce, we are a 400 person sales org and that is the only way we could adopt it”

It came back decided

Salesforce, asked for by a 400 person sales team

Worth doing 15%

It serves nobody currently using this, and it is months of work that then has to be maintained forever.

Your customer 10%

This is bookkeeping for solo freelancers. A 400 person sales team is not the customer, and building for them moves the product away from the people already paying.

It was rejected

Nothing was built

They are not the customer this product is for. That is a month you did not spend on the wrong thing.

The expensive part is deciding

Building a small fix is an hour. Working out which small fix, out of forty, is worth that hour is the thing that quietly costs you a week.

Onsay does the sorting and leaves you the decision. Everything comes back with three judgements: does your product need this, is this person your customer, are they serious. You read those and you say yes or no.

The judgement that saves the most time

Not the bug reports. The people you are not for.

When you are small, a large prospect asking for a large feature is the most dangerous thing that can land in your inbox. It sounds like growth. It is usually months of work that moves your product away from the people already paying you.

Onsay scores that against your own description of who you serve, and says plainly when somebody is not that person. It does not decide for you. It makes the trade visible before you have spent the month.

Under three minutes to your first one

Sign up, describe your product in two sentences, paste in one thing somebody told you. You get something back. Nothing to connect for that part.

Connect your code when you want the work done. Not before.

It is not another thing to check

The only things waiting for you are the ones that need a decision. Yes, no, done. What you approve gets built on the schedule you set, weekly by default, and it arrives where you already work.

There is no board to maintain, no statuses to drag things between, no second inbox.

One that already happened

Something a person actually said, and what it turned into.

i wish this integrated with salesforce, we are a 400 person sales org and that is the only way we could adopt it
what came back integrations months

Salesforce, asked for by a 400 person sales team

Worth doing 15%

It serves nobody currently using this, and it is months of work that then has to be maintained forever.

Your customer 10%

This is bookkeeping for solo freelancers. A 400 person sales team is not the customer, and building for them moves the product away from the people already paying.

A real request 90%

A completely genuine request. Genuinely not for us.

What they want
A Salesforce integration, as a condition of adopting.
Why it matters to them
They are evaluating for a large sales team and this is their blocker.

What would change

Say no, and say why. Worth watching: three of these in a month is a signal about who is finding you, not about Salesforce.

nothing shipped

Rejected, and that is the useful answer

It said this person is not the customer this product is for. Nothing was built. That is a month you did not spend on the wrong thing.

Questions

I do not have enough feedback for this yet.
Then you have the easy version of the problem. Paste in what you have, including the old things. Most people find their pile is smaller and far more repetitive than they thought.
How long does reviewing actually take?
It is built to be a ten second decision. The three judgements are right there, you do not have to open anything.
Can I change what it wrote?
Yes, and your edits are kept next to the original. The record shows what you corrected.

The bottleneck is not how fast you type. It is deciding.

Free to start. No card.

Try it on something a user told you

Anything real. Nothing is saved.

Start free