Scouts
How can a scout turn feedback on a pre-revenue B2B SaaS startup into a better next introduction?
a pre-revenue B2B SaaS startup: Use feedback to improve relevance and evidence, not merely to chase a different pitch.
Use feedback to improve relevance and evidence, not merely to chase a different pitch. A pass can reflect mandate, timing, missing information, or investment judgment. Ask which of those applies and avoid presenting one fund's view as a universal verdict on the company.
Start with the decision
Record the stated reason and the question it raises for the next introduction. Share feedback with the founder only as permitted. Distinguish a misunderstood explanation from an actual evidence gap or a fund-specific preference.
The illustrative scenario
This is an educational workbook. The company or fund and all numerical inputs below are fictional. They are not ADIN results, customer claims, market benchmarks, or a forecast.
The fictional company is testing a reporting tool with three operations teams. Users attend demos, but no recurring contract is signed. The founder wants financing to complete integrations and test a repeatable sale.
A pilot conversation, active usage, an invoice, and a recurring commitment describe different evidence. Treat projected sales as assumptions and ask which milestone financing can realistically support.
Turn the scenario into an evidence decision
Consider a review of a pre-revenue B2B SaaS startup in which a confident explanation arrives before the supporting records. Start with the first question in the table. Write down what an answer would change: the next interview, the experiment's scope, a request for specialist review, or a decision to wait. A question without a consequence can produce a longer document while adding little understanding.
Next, inspect the record named in the table and record its date, owner, permission boundary, and limitations. Review permissioned pilot notes, usage records, customer references, and a dated cash forecast. Clarify what is confirmed by the customer rather than inferred by the founder. If the record contradicts the explanation, preserve both accounts and ask which definition, period, or workflow differs. Do not silently select the version that makes the opportunity look strongest.
Finish with a conditional statement: if the specified evidence supports the claim under these conditions, take the named next step; otherwise investigate the unresolved question. A feedback log is useful when it changes the next screen or question. It should not become a collection of unsupported labels about founders or a promise that revising a deck will secure funding. This worked exercise is about the decision process. It does not assert that a fictional company has met a real diligence standard or that a template can authorize an investment.
| Item | Illustration |
|---|---|
| Decision question | Why did the fund pass? |
| Case-specific constraint | A pilot conversation, active usage, an invoice, and a recurring commitment describe different evidence. Treat projected sales as assumptions and ask which milestone financing can realistically support. |
| Record to inspect | Review permissioned pilot notes, usage records, customer references, and a dated cash forecast. Clarify what is confirmed by the customer rather than inferred by the founder. |
| Comparison to preserve | Compare the current evidence with the specific next milestone. An attractive market story does not establish that this team can reach its buyer. |
| Unresolved case question | Who owns the customer's budget? |
Use this worksheet
Answer the questions with a source, date, owner, and next action. Mark an unknown as unknown. Use public or permissioned information and involve a qualified specialist when a question requires expertise beyond the team’s competence.
- Why did the fund pass?
- Was the company understood?
- What evidence was missing?
- What is fund-specific?
- What may be shared with the founder?
Questions specific to this scenario
- Who owns the customer's budget?
- What milestone comes before the next raise?
- Which projection has independent support?
Review permissioned pilot notes, usage records, customer references, and a dated cash forecast. Clarify what is confirmed by the customer rather than inferred by the founder.
A concrete next test
Ask a pilot participant to describe the last time the reporting problem occurred and the next approval needed for a purchase. Compare that account with the founder's pipeline stage. Record an explicit unresolved step rather than interpreting meeting attendance as contract intent.
Interpret the result
A feedback log is useful when it changes the next screen or question. It should not become a collection of unsupported labels about founders or a promise that revising a deck will secure funding.
Compare the current evidence with the specific next milestone. An attractive market story does not establish that this team can reach its buyer.
Sources and method
These primary resources provide background for the concepts. The fictional scenario, calculations, and worksheet are ADIN educational examples; the sources do not report or validate those invented results. Reviewed October 11, 2026.