Give Clear Feedback as a Mentor or Judge

Start With the Stage

Before you comment, ask where the founder is:

• learning about a problem;
• testing demand;
• drafting early work;
• getting ready for a contest;
• sending work for program review;
• preparing for a funding talk.

Stage matters. A founder who is still checking the problem may not need a full money model.

Match feedback to the stage. Early ideas need sharper questions. Packages need to fit the score sheet and show clear proof.

Use the Work in Front of You

Tie comments to the package you see.

Try:

• "The problem is clear, but I do not see proof that the customer feels pain."
• "The talks show a problem, but I do not see who buys."
• "This market claim needs a reason, not just a big number."
• "The shared package has enough context, but the proof needs clearer labels."

This helps the founder know what to fix, test, or explain.

If the package is missing context, ask for the smallest missing piece. Do not ask the founder to rebuild everything.

Keep Safe Bounds

Do not state your view as a sure fact. Do not give legal, tax, finance, or investment advice unless you are hired to do that work outside the app.

Use:

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

Avoid:

• "This will get funded."
• "This cannot work."
• "You should raise now."
• "This is legally safe."

Also avoid private data you were not allowed to see. If you received secure review access, stay within that package.

What to Review

For early work, look at:

• customer clarity;
• problem urgency;
• proof quality;
• value proposition;
• business model assumptions;
• go-to-market logic;
• founder next steps.

For a contest package, also check the score sheet, missing parts, story clarity, and proof.

For official judging, follow the program score sheet and conflict rules. Secure review comments are not the same as official scores.

The Feedback Loop

When founders share clear work, mentors can give better notes. Better notes help founders improve. Stronger packages help judges and programs review faster.

That loop is the point.

Feedback Template

Use this structure:

1. What is clear.
2. What claim needs more proof.
3. What risk matters most now.
4. What next test would help.
5. What the founder should update after the test.

Short, specific feedback is easier to use.

Next Step

Use focused packages and clear feedback to help founders improve the next version of their work.