Skip to content
← All articles

Angel investors

What should an angel ask a syndicate lead about an early marketplace startup?

an early marketplace startup: Ask a syndicate lead who performs each diligence task, what information investors receive, and how the lead is compensated.

Ask a syndicate lead who performs each diligence task, what information investors receive, and how the lead is compensated. A familiar name or shared network does not resolve conflicts or establish that every material question was investigated.

Start with the decision

Map sourcing, analysis, references, document review, ongoing reporting, and investment authority. Ask which tasks are outside the lead's scope. Review compensation and related relationships through the actual disclosures and agreements.

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 syndicate can coordinate work while leaving participants responsible for their own decision. Do not equate membership, a lead's participation, or a deal memo with a guarantee of diligence quality or returns. 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 questionWho owns diligence?
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. Who owns diligence?
  2. What is independently verified?
  3. How is the lead compensated?
  4. Which conflicts are disclosed?
  5. What reporting follows the investment?

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 syndicate can coordinate work while leaving participants responsible for their own decision. Do not equate membership, a lead's participation, or a deal memo with a guarantee of diligence quality or returns.

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.