Filippo Baratini

We're always experimenting.

Yeah, exactly.

We wanted to know why people were leaving, and instead of manual outreach, sending the email which no one responds, and stuff like that, we said, we have an engineering team in-house, let's just build a quick survey.

And yeah, that worked pretty well.

Oh, okay.

So building for us was a week, like one week, maybe.

Yeah, we have a good engineering team.

But then packaging it and transforming it into a solution that can work for others, it took a bit more, like a couple of months, maybe.

Oh, say like 20, maybe.

Okay.

Yeah, absolutely.

You try to give them multiple choice answers and the options that you provide them are usually things that you want to, like that you have a sense that might be an issue.

That's also what we recommend to our users.

If you know that you might have an issue with customer support, let's say your documentation, you try to give those options to the user.

And you also, of course, leave the option to have an open answer, but then it's harder to extract the data out of an open answer.

Yeah.

So main one for us, which is very specific to our case, is we no longer need it.

Because imagine a financial model, you do it once, maybe you check it every couple of months, but it's not something that you spend a lot of time on.

Uh, I'm talking about Sturpee.

Got it.