About UGC Pulse

We were solving our own problem

We were engineers trying to solve Audionotes' UGC problem from first principles. We wanted to understand what earned attention, what patterns repeated, and what we should make next.

For about six months, we built an internal tool to track which public videos were breaking out and help us understand why they worked.

We were not the only ones

The more founders we spoke with, the clearer the pattern became. Too many teams were investing in content with little evidence, posting and praying for a hit.

They could see the occasional breakout video, but not the wider picture: which accounts were accelerating, which hooks kept working, and which ideas were worth adapting for their own app.

So we opened up the tool

We turned that internal system into UGC Pulse so other app teams could use public performance signals to make smarter creative bets and improve their odds of earning attention.

The goal is simple: help teams move from scattered examples and gut feel to a clearer view of what is working, why it may be working, and what they can thoughtfully try next. No data can promise virality.

Come say hello

Have a question, an idea, or a UGC problem you are trying to crack? We would like to hear from you at hello@ugcpulse.app.