The question that got 800 upvotes
It was a Sunday morning in March when I got the message. A pastor using Feedr during his church conference had just sent through a screenshot. A single question from the audience had accumulated 800 upvotes in under five minutes. I stared at that number for a while, trying to understand what had actually happened.
Context: 1,200 people in a room, one QR code
The conference was being held in a fairly large venue. We're talking around 1,200 attendees. The pastor had set up Feedr on his phone before taking the stage. During his message, he'd asked people to use their phones to send in questions and reactions. No downloads. No account creation. Just a QR code displayed on the big screen, and within seconds, people started joining the session through their mobile browsers.
For the first fifteen minutes, the engagement was steady but typical. A comment here, a question there. Standard conference activity. Then someone in the audience posted a question about something the pastor had mentioned in passing. It wasn't a particularly complex question. But it clearly resonated.
People started upvoting it. Five upvotes. Fifty. By the time the pastor saw it on his phone and pinned it to the top of the comment stream, it had already crossed 300. The upvoting kept going. 500. 700. Then 800.
Why that question mattered more than the answer
I spent time thinking about what that moment actually meant. It wasn't a technical achievement on our end. The infrastructure was simply doing what it's supposed to do: letting an audience signal agreement in real time. But what struck me was that the pastor had created a space where people felt safe to both ask and vote on what mattered to them.
The upvoting feature exists on the free tier of Feedr, by the way. We didn't restrict this to paid users. And that's intentional. Upvoting is how you let 1,200 people have one conversation instead of 1,200 separate monologues. A live comment stream without voting is just noise. With voting, it's a collective voice.
What made this particular moment stand out to me was the speed and unanimity of it. 800 people didn't disagree on whether that question mattered. The pastor hadn't planted the question. No one was gaming the system. It was just an audience signalling what they actually wanted to hear about. That's what engagement should feel like.
The friction that almost never happened
Here's what could have gone wrong. If Feedr required attendees to download an app, create accounts, or verify emails, most of those 1,200 people wouldn't have engaged at all. We'd have had maybe a hundred questions and comments, mostly from people patient enough to deal with friction.
Instead, scanning a QR code takes about four seconds. By the time the pastor had finished his opening remarks, the session was already active and growing. That matters more than it might sound.
I mention this because we made this choice deliberately. We're not a webinar platform. We're not trying to be Zoom with engagement bolted on. We're trying to be the simplest possible layer between a speaker and their audience's real thoughts. The session report we generate afterward shows the pastor what people actually cared about. The comment moderation tools on the Creator tier (and above) mean he could have deleted spam if it had appeared. But that's optional, and most of it never comes.
What happens with 800 upvotes on your phone
The pastor told us later that seeing that number climb was one of the most energising moments of his service in months. Not because it was flattering. But because it was instant, visible proof that his congregation was listening and thinking and engaged. He answered the question differently than he might have otherwise. He spent more time on it. The rest of his message shifted slightly based on that feedback.
That's the thing about real-time engagement that doesn't quite come through in a blog post. It changes the conversation. The speaker sees what the audience is actually thinking and responds to it. They're not guessing. They're not relying on feedback forms filled out three weeks later. They're watching people vote in the moment.
One moderator from the conference reached out afterward to ask if we could scale this further. They're planning an event with 3,000 people next year and wanted to know if Feedr could handle it. The Pro tier supports unlimited audience size, and we've run sessions with much larger numbers without issue. But more importantly, they'd seen what this looked like at scale and wanted more of it.
The single question that said everything
I keep thinking about that particular question, by the way. We never found out what it was. The pastor was kind enough to tell us the story, but he didn't quote it back. He didn't need to. The 800 upvotes were the entire story.
When you're running a conference or a church service or any kind of live event where you want to know what your audience is actually thinking, upvoting is one of the most honest feedback mechanisms that exists. It's not perfect. It's not comprehensive. But it's real. Eight hundred people couldn't all have been wrong about whether that question mattered.
What has me thinking, more than anything, is how little friction it took to create that moment. A QR code. A mobile browser. An upvote button. No accounts, no apps, no passwords. Just the ability for people to instantly, publicly align on what they cared about.
How often do you actually know what your audience is thinking while you're in front of them? Not afterward. Not based on surveys. But live, in the moment, while you can still do something about it.
Ready to try Feedr by MRVL?
One tap to download. No sign-up wall.