Writing a detailed review

A detailed review earns 3 credits because it's supposed to take 45–60 minutes. If you're rushing through it in 10, you're getting the basic credit but delivering detailed-grade expectation — the recipient will flag it.

Structure

The form has 6 sections. Each takes ~8 minutes.

1. First impression (5 min)

Visit their app as a first-time user. Write what you notice in the first 30 seconds — visual hierarchy, value prop clarity, trust signals. Don't over-think; capture genuine reactions.

2. Positioning (8 min)

Read the homepage hero and any sub-sections. Is the target audience clear? Is the unique angle obvious? Does the app pass the "one-line answer to what does this do" test? What's missing?

3. Distribution channels (10 min)

Look at their app onboarding data (the summary is visible to reviewers). Are the channels they're focused on right for their audience? What would you change? This is where distro-specific expertise pays off.

4. Content audit (10 min)

Open their public profile, check their last 5 shipped posts. What's working? What's generic SaaS speak? Any consistent hooks that aren't landing? Specific examples > vague feedback.

5. One strategic recommendation (8 min)

The single most important thing you'd change. Not a laundry list — one thing, argued specifically. "I'd kill the email capture and move to a gated case study" is a recommendation. "Improve conversion" is not.

6. One warning (5 min)

The thing they're about to do that you'd tell them not to. Optional but valued — most founders get too much validation and not enough honest "don't."

Rating

Recipients rate reviews on a 5-point scale: 1 (useless) to 5 (changed my thinking). Average review quality feeds into your reputation score. Long-but-generic reviews score worse than short-and- specific. Be specific.