Skip to content
← All articles

Scouts

How should a scout identify conflicts when sharing an early marketplace startup?

an early marketplace startup: Identify conflicts when a scout works with several funds, invests personally, advises the company, or receives another form of compensation.

Identify conflicts when a scout works with several funds, invests personally, advises the company, or receives another form of compensation. The practical issue is how incentives and information affect the introduction. Disclosure and handling depend on the specific relationships and agreements.

Start with the decision

Map the roles before sharing the opportunity. Ask each relevant party what may be shared and what process applies. Use qualified advice for contractual or securities-law questions, especially where compensation and solicitation are involved.

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 connects independent repair businesses with commercial property managers. Initial transactions happen in one city. The founder reports total booking value, but revenue depends on completed jobs and the platform's actual take.

Supply listings are not the same as available, reliable capacity. Booking value, collected revenue, cancellations, and repeat demand must be separated.

Turn the scenario into an evidence decision

Consider a review of an early marketplace 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. Inspect completed transaction cohorts, cancellation reasons, provider retention, and contribution costs by market. Obtain permission before contacting participants or sharing their transaction details. 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 scout should not assume that a friendly introduction removes every legal or contractual question. Keep the operating process narrow, permissioned, and consistent with the actual program's responsibilities. 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: an early marketplace startup
ItemIllustration
Decision questionWhich roles overlap?
Case-specific constraintSupply listings are not the same as available, reliable capacity. Booking value, collected revenue, cancellations, and repeat demand must be separated.
Record to inspectInspect completed transaction cohorts, cancellation reasons, provider retention, and contribution costs by market. Obtain permission before contacting participants or sharing their transaction details.
Comparison to preserveCompare a completed, repeatable match with the current alternative. Separate demand acquisition from the work needed to fulfill and support each transaction.
Unresolved case questionWhich bookings completed?

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. Which roles overlap?
  2. Who may receive the information?
  3. What compensation exists?
  4. What agreements apply?
  5. Who resolves competing expectations?

Questions specific to this scenario

  • Which bookings completed?
  • What brings a buyer back?
  • How much local support does each market need?

Inspect completed transaction cohorts, cancellation reasons, provider retention, and contribution costs by market. Obtain permission before contacting participants or sharing their transaction details.

A concrete next test

Choose one completed match and one cancelled booking. Trace acquisition, fulfillment, payment, and support costs for each. Ask what would bring both sides back without an incentive so the inquiry separates transaction volume from a repeatable local marketplace.

Interpret the result

A scout should not assume that a friendly introduction removes every legal or contractual question. Keep the operating process narrow, permissioned, and consistent with the actual program's responsibilities.

Compare a completed, repeatable match with the current alternative. Separate demand acquisition from the work needed to fulfill and support each transaction.

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.