Skip to content
← All articles

Scouts

What should a scout clarify about attribution for a pre-revenue B2B SaaS startup?

a pre-revenue B2B SaaS startup: Clarify attribution before assuming an introduction creates compensation rights.

Clarify attribution before assuming an introduction creates compensation rights. Programs may distinguish prior contact, first submission, a warm introduction, substantive assistance, and a completed investment. The applicable agreement determines the actual arrangement.

Start with the decision

Ask how the program records a referral and handles duplicates or stale opportunities. Maintain a consent-aware timeline with the information the program actually requires. Obtain qualified legal advice for rights or disputes rather than inferring terms from marketing copy.

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 timestamp can support a factual timeline while remaining insufficient to establish eligibility. Keep the program's acknowledgment and the governing terms distinct from the scout's own expectation of credit. 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.

Worked example: a pre-revenue B2B SaaS startup
ItemIllustration
Decision questionWhat event creates credit?
Case-specific constraintA 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 inspectReview 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 preserveCompare the current evidence with the specific next milestone. An attractive market story does not establish that this team can reach its buyer.
Unresolved case questionWho 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.

  1. What event creates credit?
  2. Was there prior fund contact?
  3. How are duplicates handled?
  4. What record is required?
  5. Who confirms the attribution?

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 timestamp can support a factual timeline while remaining insufficient to establish eligibility. Keep the program's acknowledgment and the governing terms distinct from the scout's own expectation of credit.

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.