Marcus gets an email asking if he'll test a new productivity app. He's busy, but the founder seems genuine, so he agrees. Why not?

First day: Marcus mentions he's confused about one feature. Within an hour, there's a thoughtful response with a screen recording showing exactly how to use it. Useful.

Second day: Marcus mentions something isn’t quite working as it probably should. The founders thanks him. Then an hour later, unexpectedly the founder sends a message saying “cool that’s fixed! Thanks for flagging it”. Huh…impressive.

Third day: out of the blue the founder follows up with "Oh, you could also use it for tracking your client invoices - might save you time there too." An additional use Marcus hadn’t really thought about but would absolutely help the business.

By week's end, Marcus isn't just testing the app - he's actively rooting for its success. He starts mentioning it to colleagues. Shares it in his company Slack. When the founder launches properly, Marcus becomes the first customer and biggest advocate.

All because someone made him feel genuinely valued during beta testing. The founder didn’t just listen but also acted based on what Marcus said. Powerful stuff.

Let’s get started:

Why Champions Matter More Than Feedback

OK I have a confession to make. I framed this week as being all about getting feedback to improve our product.

That’s true…but we’re also doing something else smart at the same time. You know me - I like efficiency!

Most founders think beta testing is about collecting data. "What do you think of this feature?" "Rate this experience." "Fill out this survey."

They're missing the bigger opportunity here.

Beta testing is also about relationship building. Every person who tests your product is a potential champion who could refer dozens of future customers. But only if you make them feel valued in the process.

That’s a big proviso! So much so that we’re spending today working on exactly how convert our testers into advocates.

The difference between a one-time tester and a lifelong advocate often comes down to how supported they felt during those early interactions. Marcus from above didn't become a champion because the product was perfect. Not at all. He became a champion because the founder made him feel heard, helped, and important.

In a way the product being bad (and Marcus’ feedback being used to improve it!) is what makes the connection stronger. Marcus is now a co-creator.

We’re going to do this in three ways specifically:

• respond quickly and efficiently

• apply their fixes (when relevant)

• go out of our way to help them more

Responsive Support That Creates Advocates

First up we need to respect their time and effort. When they give us feedback we respond immediately and enthusiastically. This is the very least we can do!

Whatever collection method you chose yesterday, the key is being thoughtfully responsive in ways that help testers succeed. When someone mentions confusion, respond with specific help. When they share how they're using it, suggest additional applications. When they encounter problems, solve them quickly.

To help with this speed let’s use a prompt:

I received this specific feedback/question/response from a beta tester: [PASTE THEIR EXACT MESSAGE]

My product is: [DESCRIBE YOUR PRODUCT]
Context about this tester: [WHAT YOU KNOW ABOUT THEM/HOW THEY'RE USING IT]

Help me craft an immediate, enthusiastic response that:
1. Acknowledges their specific feedback with genuine appreciation
2. Shows I understand what they're telling me
3. Demonstrates that I value their time and input
4. Responds to any questions they asked
5. Makes them feel heard and valued

Make the response conversational and genuinely helpful, not corporate or sales-focused. I want them to feel like I'm personally invested in their success with the product.

Obviously adapt to your own tone of voice. This is primarily for speed.

Quick Fixes That Build Relationships

Next up - fixes.

Do we fix everything they point out as a problem? Absolutely not. Tomorrow we talk about which problems we fix and which we do not - I’ll give you a framework to prioritise.

What we’re fixing immediately are the problems so glaringly obvious that we feel like complete idiots when we’re told about them.

I’m talking about the “I press the submit button and the screen just goes blank” sort of problems. Not the “I think the header text could be larger” type of issue.

Quick fixes serve two purposes: they improve your product (yay) AND they demonstrate to testers that their input matters. When someone mentions a confusing button and you fix it the same day, they feel heard in a way that builds genuine loyalty.

Use AI to help turn feedback into immediate improvements:

I received this feedback from a beta tester: [PASTE FEEDBACK]

Help me determine:
1. Is this an obvious usability fix that should be addressed immediately?
2. What's the simplest way to address this specific issue?
3. How can I turn this into clear development instructions?

My product was built with: [LOVABLE/CURSOR/OTHER]
The issue seems to be: [DESCRIBE THE PROBLEM AREA]

Give me the fix instructions AND a "I've fixed it message" I can send back to the tester that shows that their feedback matters.

Use this below your previous work (especially the product spec work we did earlier this week) so that ChatGPT or Claude will be able to generate helpful possible fixes.

When you do make a quick fix based on someone's feedback, let them know! So many builders miss this simple task. Stupid. It’s easy goodwill that could be acquired with a simple "Thanks for mentioning that button issue - just fixed it!". Immediately they’ll feel heard and valued.

Additional Ways They Could Use It

Let’s go above and beyond. We’re going to overdeliver. Your testers are using your product for one specific purpose (probably the one you first contacted them about), but there might be other ways it could help them that they haven't considered.

After someone's used your product for a few days, follow up with additional use cases they might find valuable. This shows you're thinking about them and their needs, not just your product validation. It’s a pure value add.

I have a beta tester who's been using my product for [DESCRIBE HOW THEY'RE USING IT].

My product is: [DESCRIBE YOUR PRODUCT AND FEATURES]
What I know about their work/situation: [SHARE WHAT YOU'VE LEARNED]

Help me identify 2-3 additional ways they could use my product that might be valuable for their specific situation. Focus on practical applications they might not have considered.

Create a friendly follow-up message suggesting these additional uses without being pushy. Frame it as "you might also find this helpful" rather than trying to convince them.

Drop in feedback they’ve given you and any notes about what they’ve been using it for. And use this to extrapolate out (with the help of AI).

This could be things that they can already do with your product. And you are just mentioning the additional use cases.

OR (and this is more advanced) it could be uses that aren’t yet supported but you could build in. We’ll talk more on this tomorrow.

This approach transforms you from someone asking for favours into someone genuinely trying to help them succeed. You’re basically giving them white-glove concierge service. And one that importantly they were not expecting. That’s the key! Above and beyond.

Your Deliverable Today

Focus on building relationships, not just gathering data:

1. Reach out to every beta tester with genuine interest in their experience

2. Use the AI prompts above to create helpful, relationship-focused support approaches

3. Identify and quickly fix any obvious usability issues that come up

4. Document not just what feedback you received, but how each person responded to your support

Remember, you're building relationships with people who could become your biggest supporters. And first customers. More on that soon!

Build in Public Content

Share the relationship-building approach:

"Day 24 of AI Summer Camp: Turning beta testers into champions.

Doing something different today. Most founders treat beta testing like data collection. I'm treating it like relationship building. Big shift.

I’ve realised every person testing my product is a potential advocate who could refer future customers. But only if I make them feel genuinely valued in the process. So…I’m working on that today. “

What's Next?

Tomorrow we tackle which feedback to act on and which to ignore. Not every suggestion should be implemented, even from people you've built great relationships with. We'll learn about Stephen King's rule for feedback and create a systematic approach to deciding what changes actually improve your product versus what just makes individual users happy.