Give Feedback Founders Can Use

For Mentors

Use the package to see where the founder is now.

Good mentor feedback names:

• the clearest part of the idea;
• the claim that needs proof;
• the next customer or buyer question;
• the risk to test next;
• the choice to make after the test.

The goal is progress between meetings, not a long lecture.

For Judges

Judges need a steady view of each entry.

A good package shows the problem, customer, model, proof, and missing parts. Judges still use the program score sheet and their own judgment.

Do not treat AI summaries, scores, or ready signals as final calls.

Safe Feedback Bounds

Keep feedback specific and bounded.

Use phrases like:

• "The proof I would look for next is..."
• "A judge may ask..."
• "This guess looks risky because..."
• "Try testing..."

Avoid promises about funding, awards, legal safety, market success, or investment readiness.

Secure Review Links

A founder may share a package through a secure review link. Review only what was shared. Do not ask for private workspace content unless the founder chooses to share it.

The review page should explain the package without showing raw link details.

Next Step

Read the feedback guide. Use focused packages, proof, and gaps as the center of mentor or judge feedback.