When basic session report matters

The moment you realise engagement is not enough

Feedr started with a simple promise: get your audience to comment and upvote in real time, no app downloads, no accounts. Just scan a QR code and start talking. But real-time is only half the story.

When you're running a session, you're in the moment. You see comments flood in. You see people upvoting a question to the top. You watch the energy shift. But the instant the session ends, all of that vanishes. The host closes their phone. The audience leaves. And you're left with nothing but a memory of what felt important.

That Bristol pastor's message stuck with me because it exposed something we hadn't properly addressed: creators need to know what their audience actually said. Not for vanity. For preparation, for follow-up, for understanding what landed and what didn't.

Why a report matters even when it's free

The free tier of Feedr is deliberately generous on some things. Three sessions a month, up to 100 audience members, full access to comments, upvotes, reactions, pinning. We wanted creators to try it properly, not feel throttled by artificial limits.

But what we almost missed was that a free user has no way to prove the session even happened. No record. No proof of engagement. A school teacher using Feedr with her class of 45 kids would run the session, see brilliant questions come through, moderate them live, and then have nothing to show a colleague or a parent about what actually occurred.

A basic session report solves that problem. Not a fancy analytics dashboard with graphs and sentiment analysis. Just the facts: how many people joined, which comments got upvoted the most, what actually mattered to your audience. A PDF you can download and keep.

It's the difference between 'I ran a session' and 'here's what my audience said during the session.' One is a thing that happened. The other is data you can act on.

The report exists because someone asked for it

We didn't dream up basic session reports in a strategy meeting. A lecturer at Oxford used Feedr with 60 students and asked if she could get a list of the top questions at the end. A podcast host with 12 listeners wanted to know if the live comment feature was actually driving engagement or if people were just lurking. A conference speaker wanted to follow up on the most popular topic with a blog post.

Each of them had the same underlying need: proof. Evidence. A record they could refer back to, share with a team, or use to improve next time.

So we built it into the free tier. When your session ends, you get a report. Not instantly (we batch them), but within a few hours. It shows you the total attendees, the comment count, the upvoted questions ranked highest first, and the overall engagement pattern across the session. It's basic. It's not a heatmap or a sentiment breakdown. But it's real, and it's yours to keep.

What happens when creators can actually see

The shift in how people use Feedr changed when the report went live. We started seeing free-tier users run multiple sessions instead of abandoning after the first. They'd check the report, see which questions the audience cared most about, and run another session to dig deeper into those topics.

A church preacher in Manchester ran a session, saw that the audience upvoted a particular theological question above everything else, and built his next sermon around that feedback. He couldn't have done that without the report. He would've had nothing but his own intuition.

One podcaster told us the report showed him that 68% of his audience's comments were questions rather than statements. He hadn't noticed during the live session because he was focused on keeping the momentum. But the report made it obvious. So he restructured how he runs episodes, dedicating the second half to audience questions instead of the first few minutes. Engagement went up. He upgraded to Creator tier to get moderation tools because the volume of good questions increased.

That's the real value. Not the report itself. The fact that creators can see what happened, adjust, and try again. It closes the loop between speaker and listener.

Why we didn't hide it behind a paywall

We could've made the basic session report a Creator tier feature. Technically, it's simple to do. It would've been easier to explain the upgrade path. Every other app does this, so why didn't we?

Because the moment we made reports paid-only, we'd have made engagement invisible for free users. And if engagement is invisible, why would anyone bother building it into their workflow? They'd try Feedr once, see a live comment stream for an hour, then forget about it because there's no hook pulling them back.

Free users who see their own data tend to become paid users. Not because they feel manipulated into upgrading, but because they suddenly understand the value. They see 15 people showed up and asked genuine questions. They see 80% of those questions went above a certain upvote threshold. They think, 'Maybe I should run this again, and next time I'll moderate those comments properly.' That's when they look at Creator tier and its moderation queue and comment filtering tools.

But that journey only starts if they can see the report first. If we'd hidden it, they'd never get there.

The report as evidence

Here's the thing I've learned about creators: they need to prove value upward. A teacher needs to show a head of department that live comments improved student engagement. A conference organiser needs to show a sponsor that attendees were genuinely participating. A podcaster needs to show a producer that the audience cares enough to ask questions live.

A basic session report is evidence. It's not the full story, but it's real. It's a number. It's a list. It's something you can share in Slack, in an email, in a meeting, and say: 'This is what happened in the room.'

The pastor from Bristol downloaded his report, saw the top 10 upvoted questions, printed it out, and used it to plan his next three sermons. He didn't upgrade. He didn't need to. He just needed to know that people cared about certain topics and that they'd shown that care in real time.

That's the bar for a free feature: it needs to solve a real problem, even if it's not the fanciest problem. A basic session report does exactly that.