Why I built hoot?

Hoot wasn't born from market research.

It wasn't born from a startup idea list either.

It started with a problem I kept running into while building my own apps.

One of them is Elenya, an appointment scheduling platform built for the Brazilian market. As the product grew, users started sending feature requests, bug reports, and feedback through different channels.

Some came through email.

Some through WhatsApp.

Some through social media.

Some through direct messages.

Keeping track of everything became harder than building the features themselves.

My first thought was simple:

I'll just build a feedback feature inside the app.

But then another project came along.

And another one.

Soon I realized I'd either have to rebuild the same feature over and over again or maintain some internal package that wasn't really a product.

Neither option felt right.

What I actually wanted was a single place where all feedback could live.

A place to collect ideas, understand what users wanted, prioritize requests, and communicate progress.

So I built Hoot.

At first, it was purely for myself.

A tool to manage feedback across all my products.

But there was one requirement from day one:

It had to be incredibly easy to add to new projects.

I didn't want to spend hours configuring integrations, setting up databases, or rebuilding the same workflow every time I launched something new.

I wanted a single place for feedback, with a setup simple enough that I could add it to any project in minutes.

Because if adding feedback collection becomes a project on its own, most founders simply won't do it.

That principle still guides Hoot today: simple, fast, and easy to plug into any product.

After using it for a while, I started wondering:

If I have this problem, how many other founders have it too?

That's when Hoot stopped being an internal tool and started becoming a SaaS.

Today, every feature request, bug report, and piece of user feedback from my products flows through Hoot.

Everything is centralized.

No more searching through emails.

No more forgotten conversations.

No more wondering if a request came from a customer, a DM, or a support ticket.

Just one place to understand what users want and decide what to build next.

Most products start with an idea.

Hoot started with a problem I already had.

And honestly, those are usually the best products to build.