Onsay Start free

Beta Free to start, no card

Software that fixes itself.

Your users say what is wrong. The software changes. You approve it, or you tell it to stop asking.

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

“every time i log in on my phone it signs me straight back out. happens constantly, i have basically stopped using it on mobile”

Onsay decided

People are being signed out on mobile

Worth doing 95% Your customer 85% A real request 95%

Onsay wrote this

- maxAge: THIRTY_DAYS,
+ sameSite: 'lax',
+ secure: true,

You approve it before any of it ships

How it works

Four steps, and you are only in one of them

  1. 01

    They say something

    From a box on your site, your inbox, or pasted in by you. However it already reaches you.

  2. 02

    It comes back decided

    What they want, why it matters to them, whether it is worth doing, and whether they are even your customer.

  3. 03

    You approve or you do not

    Ten seconds a piece. Reject it and it is gone. Nothing has been touched yet.

  4. 04

    The software changes

    The work is done and waiting for you. Nothing ships until you say so.

Start to finish

One person said one thing

They said

“every time i log in on my phone it signs me straight back out. happens constantly, i have basically stopped using it on mobile”

It came back decided

People are being signed out on mobile

Worth doing 95%

A signed in person being signed out is a broken core path. Nothing else on the list matters while this is live.

Your customer 85%

An existing paying customer, on the platform most of them use.

It shipped

Keep the session across the sign in redirect on mobile Safari

Three people described the same thing in different words, so it became one change. Sets the session cookie flags correctly and adds a test that fails if this breaks again.

Approved on a Tuesday. Live the same afternoon.

And this is what landed in the code

server/lib/session.js onsay/auth-mobile-session
1 . export const startSession = (res, token) => {
2 . res.cookie(SESSION, token, {
3 . httpOnly: true,
- maxAge: THIRTY_DAYS,
4 + maxAge: THIRTY_DAYS,
5 + // Safari drops the cookie on the redirect back from sign in
6 + sameSite: 'lax',
7 + secure: true,
8 . })
9 . }
Pull request opened #215 3 files changed Not merged. That part is yours.

What comes back

Three people. Three very different answers.

Every one of these is real, and so is the answer it got. The third one is the one that saves you a month.

A user said

“every time i log in on my phone it signs me straight back out. happens constantly, i have basically stopped using it on mobile”

Onsay decided

People are being signed out on mobile

Worth doing 95% Your customer 85% A real request 95%

Onsay wrote this

- maxAge: THIRTY_DAYS,
+ sameSite: 'lax',
+ secure: true,

You approve it before any of it ships

Two gates

Nothing gets past you by accident

The first gate is the decision. Nothing is touched until you accept it. The second is the change itself, which arrives finished and waits. Neither one can be turned off, because the gates are the product and not a setting.

How it works

Waiting on you 1 of 3

Export is hidden in the wrong place

Move Export next to the data it exports. Leave something behind in Settings for anyone who learned the old place.

Approve Reject

Nothing has been touched yet

Three doors

However it already reaches you

  • A box on your site

    One line to add it. It cannot collide with your styling because it renders in its own root.

  • Paste it in yourself

    Something from a call, an email, a message somebody sent you at eleven at night.

  • Send it from anything

    Point your support inbox at it. Anything that can make an HTTP request can add to the pile.

Try it on something a user told you

Anything real. Nothing is saved.

Where it hurts

Pick the one that is you

It says no, too

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.

Live numbers

Small, and true

Read straight from the product. They are small because we are new, and we would rather show you a small true number than a large invented one.

pieces of feedback read
changes made
products connected

Your users already know what is broken

Paste in the three oldest things anyone has told you and see what comes back.

Free to start. No card.

Start free