Ask for honest feedback (post-launch)
Email to engaged users asking for direct critique after launching a feature.
Hi {{firstName}},
We shipped {{newFeature}} on {{date}}. You've used it {{usageCount}} times since.
I'm asking for brutal feedback — what's broken, what's confusing, what's flat-out wrong. Compliments are nice; we don't need them. Specifics are what we need.
Reply with whatever you've got. Bullets are fine. Voice memos are fine. Anything that catches something I should fix.
— {{founderName}}Why this works
Asking for brutal feedback after a launch generates substantially better signal than generic 'thoughts?' asks.
**Subject is direct.** 'Brutal feedback wanted on {{newFeature}}' tells the recipient what's expected. Specific framing pre-commits the responder to specific feedback rather than polite vagueness.
**Specific user data in the opener.** '{{usageCount}} times since' signals you're talking to actual users, not blasting a list.
**'Compliments are nice; we don't need them' line.** This is the move that earns honest replies. Most feedback requests get compliments by default because recipients want to be polite. Explicitly declining compliments shifts the response distribution toward critique.
**Format options.** 'Bullets are fine. Voice memos are fine.' lowers friction by accepting whatever format the responder prefers. Some power users prefer voice memos because typing structured feedback feels heavy.
**Founder signature.** Brutal-feedback asks should always be founder-signed. The implicit message: the person reading this can actually act on the feedback.
Useful-feedback rate from engaged power users on this pattern: 20–35%. Most of the responses become product roadmap data.