3 builders who never spoke to each other

Put a named feedback prompt in every send

A button at the foot of each issue with a name that fits your subject collects far more than a generic request for feedback, and polling the list on what to build next gives you demand proved before the work starts. Rewriting confirmation emails to invite a reply turns transactional mail into the same channel.

The method

1. 01

   Put a feedback button at the foot of every send pointing at a short form, and give it a name that fits your subject instead of asking for feedback in the generic way.

2. 02

   Poll the list on what you should build next and then actually build the winner, which gives you a second format with demand already proven.

3. 03

   Rewrite your purchase confirmation emails to actively ask for feedback, which gets customers talking back to you.

4. 04

   Ask the subscribers you already have which paid version they would want, then build that one instead of guessing between the options yourself.

What it returned

• 5

  Mike Benitez calls his the 5-second Debrief, which suits an audience of military aviators and collects weekly responses through a Google Form.

• Mike Benitez asked readers what The Merge should do next, the answer was overwhelmingly a podcast, and he launched one as a further touchpoint to monetise.

• Zue redid all of his product confirmation emails to solicit dialogue and reported it working well straight away

• The candidates he was choosing between were locking the full database and newest trends behind a pro tier, gating exact stats inside the free tools, deep dive reports, and reports made to order.

Sources

• ⭐️ You need a game plan – Jakob GreenfeldJakob Greenfeld · jakobgreenfeld.com · ⭐️ You need a game plan · 2022-03-08
• Friday Feature: The MergeMike Benitez · sparkloop.app · 🙋 How The Merge does it · undated
• Week 27 RetrospectiveCory Zue · coryzue.com · Comments · 2017-09-25