Guides
A guide to giving feedback founders can act on
Tyler Hutto, Founder · October 8, 2026 · 4 min read

Founders read a lot of feedback. The notes that change their roadmap all sound the same: they describe one moment, one expectation, and one gap. Everything else is noise.
Below is the shape to use, the same experience rewritten twice so you can see the difference, and the edge cases that trip people up.
What makes a note reproducible?
A note a founder can act on describes something that happened, not an impression of the whole product.
Say where you were and what you were trying to do. Not "the onboarding is confusing", but "I signed up on my phone and could not tell whether the second screen had saved." A moment can be reproduced. A mood cannot.
Say what you expected
Expectations are the invisible half of every complaint. If you thought the button would email you a link, say so. Founders can only design against an expectation they know about.
Describe the gap in one sentence
What happened instead? Keep it to a single line. If you need three paragraphs, pick the smallest true version.
One clear moment beats a page of impressions, every time.
How long should a note be?
Four to six sentences. Long enough to carry the moment, short enough to be read on a phone.
Founders triage. A note that opens with a conclusion, "I would not have found the export button", gets read to the end. A note that opens with a paragraph of background gets skimmed. If your verdict is the most useful thing you have, move it to the top.
Then add the idea, labelled as an idea
Suggestions are welcome and should be marked as such. "What I would try" is a different sentence from "this is broken", and mixing the two is how good feedback gets discounted.
- The moment
- What you expected
- What happened
- What you would try, if anything
What does a good note look like end to end?
Here is the same twenty minutes written two ways. First, the vague version:
The app feels cluttered and the flow is confusing. Also the colours are a bit much.
Now the same experience, in the shape above:
I opened the app on my phone to log a plant I bought yesterday. I expected the add button on the first screen, because adding a plant was the only thing I came to do. Instead it was two taps deep behind the profile tab, and I gave up the first time. What I would try: one add button at the bottom of the home screen, even if it duplicates the one in the profile menu.
Verdict: I would use this weekly and pay around $3 a month, not more, because I already have a notes app that half does it.
The first note hands the founder a mood. The second hands them a screen, an expectation, a two-tap cost and a price ceiling. One of those can be fixed tomorrow.
What if you have nothing nice to say?
Say the true thing, once, without the cushion. "I stopped at the third screen because I did not understand why it wanted my location" is not rude, it is a fact with a number in it.
What founders cannot use is a softened version that hides the reason. If the product is not for you, say that and say why: a clear no saves them a month of chasing a market that is not there.
Close with the verdict
Would you use this? Would you pay for it, and roughly how much? That answer is often the single most valuable line in the whole note, because it turns an opinion into a signal.
Ranges are fine. "$5 to $10 a month, not $20" is more useful than "$10", because it shows where the ceiling is. If the answer is never, say what would have to be true for that to change: that is a roadmap note wearing a no.
How many notes should you send?
One per test, plus a short second note if you kept using the product afterwards.
The follow-up is undervalued. "I used it again this week and the thing I struggled with was X, not Y" tells a founder which problem actually repeats. Most testers go quiet after the first note, which is why the ones who come back get remembered.
What about screenshots and recordings?
Attach one if it shows the moment, and skip it if it only shows what you already described. A screenshot of the button you could not find is worth a paragraph; five screenshots of the home screen are worth none.
Use the same shape every time and your feedback becomes something a founder can compare across a hundred testers.
Find your first fans on Earlynest
Join the communities where the people who need what you are building already gather.
Keep reading
For startups · October 24, 2026
Your first 50 users are in a community, not a funnel
Paid ads buy attention you have to keep paying for. A community you show up in compounds. Here is how we found our first testers by being useful in one place.
For early adopters · October 16, 2026
What early adopters actually get out of testing
Giving feedback is not free labour. It is how the products you use every day get built around you, and it comes with perks, reputation and a seat at the table.

