The report nobody asked for (until they did)

The moment we realised we'd built half a product

When you're hosting a live event with Feedr, the comments come in fast. Really fast. A lecturer running a 45-minute class with 80 students, or a conference speaker taking Q&A from a room of 200 people, they're focused on the stage, not their phone screen. They're watching the crowd, answering questions, moving through slides. The live comment stream is there, sure, but it's almost background noise.

What stuck with us was the follow-up question every host asked within 24 hours: what did people actually say? Not 'show me the comments as they happened,' but 'give me a summary, a record, something I can review later.'

That pastor wasn't alone. A podcast host wanted to see which questions got the most upvotes so she could address them in a follow-up episode. A university lecturer needed proof that students had engaged, not just shown up. A speaker at a tech conference wanted to know if the live Q&A had revealed gaps in his talk he could fix next time.

We realised we'd built Feedr to solve the live moment, but we'd left people hanging when that moment ended. The comments evaporated. There was no trace.

Why we didn't charge for it

There's a logic to paywalling analytics. Paid users get the dashboard, the metrics, the deeper insights. The report would have been an easy upsell, a natural feature gate for our Creator tier.

But the more we talked to free users, the more that felt backwards. The basic session report isn't a luxury feature. It's table stakes for anyone who's serious about hosting, even once a month. A speaker or lecturer or preacher doesn't need a fancy dashboard to know whether their audience engaged. They need to be able to say, 'I ran a session, and here's what happened.' Full stop.

The basic report is simple by design. It shows you the comment stream in order, the upvote count on each message, and the audience size. No filtering, no sentiment analysis, no attempt to be clever. Just the raw shape of the conversation. Anyone on the free tier gets it, whether they're running their third session or their thirtieth.

We kept it lean because we wanted it to be useful to someone running a single event, not a conference organiser running twenty. The people who need deeper analytics, the ones managing multiple events or tracking engagement trends across months, that's where the Pro tier comes in with the full analytics dashboard. But a basic record of what was said? That's non-negotiable.

What the report actually taught us

Once we'd shipped the basic session report, something unexpected happened. We started getting screenshots. Hosts would email in images of their session reports, usually with a note like 'Thought you'd like to see this' or 'Can you believe the engagement?' It was never about bragging. It was always about surprise.

They were surprised at what people had asked. Surprised at which comments got upvoted to the top. Surprised that their audience had engaged at all, given how passive they'd seemed during the live event.

One user, a lecturer, told us the report changed how she structured her next class. She'd assumed the live Q&A comments were scattered and shallow. When she actually read through the report, she saw a thread of genuine confusion about a concept she'd rushed through. The comments told a story she'd missed while she was presenting. Her next lecture, she slowed down on that section and opened with a direct question about it. Engagement doubled.

That's when we understood what the basic session report was really for. It wasn't analytics. It was reflection. It was a way for hosts to think about what just happened, away from the stage, with time to breathe and actually read what people had said.

The constraints that made it work

We've learned that constraints are useful. The basic report doesn't let you filter by user or sentiment or keyword. It doesn't rank comments by virality or time-of-day. It just gives you the ordered list: what was said, in sequence, with upvotes visible.

That simplicity is intentional. We wanted hosts to see their session the way it unfolded, not the way a dashboard algorithm would curate it. The comment with three upvotes sits next to the one with zero. The question that seemed minor at the time gets read in context, alongside the conversation that surrounded it.

It also meant we could ship it fast and keep it reliable. No complex queries, no aggregation logic, no edge cases where the data shape breaks the report. It's a straightforward download or view: here's your session, sorted by timestamp, with counts. Done.

For our Creator and Pro users, we knew there'd be room to go deeper later. The paid tiers have the moderation queue, emoji reactions, guest moderators, and for Pro the full analytics dashboard. Those features reward hosts who run Feedr regularly and want more control. But the free tier needed something that was complete on its own, even if it was basic. The session report does that.

What free users actually do with it

We don't have perfect data on how often the basic report gets downloaded (that's part of why the analytics dashboard is a Pro feature), but from the conversations we have, patterns emerge. Some hosts screenshot it and drop it in a follow-up email to attendees. Some paste it into a shared document for their team. A few have told us they read it aloud to a small group afterward, turning the live event into a async conversation.

The most interesting use case came from a podcaster who exports the report and uses it as outline notes for her follow-up show. The live session becomes raw material for content creation. She's not paying for analytics, but she's getting real value from knowing what her audience cared enough to type and upvote.

None of that required us to charge. None of it needed a paywall or a premium tier. They just needed access to what happened, presented plainly, so they could decide what to do with it.