Skip to content
← All articles

Scouts

How can a scout develop a sourcing thesis around a developer infrastructure startup?

a developer infrastructure startup: A sourcing thesis explains which founders and problems a scout can encounter and understand through a real network.

A sourcing thesis explains which founders and problems a scout can encounter and understand through a real network. It should include exclusions, stage, and the fund's mandate. A broad interest in technology is not the same as a repeatable way to find relevant companies.

Start with the decision

Map the communities and work where the scout has trusted access. Compare that access with the fund's actual criteria. Ask what evidence the scout can contribute beyond a publicly available company description.

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 maintains an open-source integration library and offers a hosted service. Downloads are growing, but paying teams are few. A small group of maintainers handles support, releases, and infrastructure incidents.

Community activity and commercial demand overlap imperfectly. Count organizations and actual production use separately from package downloads, forks, and repeat installs.

Turn the scenario into an evidence decision

Consider a review of a developer infrastructure 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 production references, hosted conversion cohorts, support workload, repository ownership, and release history. Check the permission to reuse code and data rather than assuming public availability grants every right. 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 thesis is useful when it helps the scout choose where to spend time and what to pass on. Revisit it when the fund's mandate or the scout's actual access changes. 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 developer infrastructure startup
ItemIllustration
Decision questionWhich community provides access?
Case-specific constraintCommunity activity and commercial demand overlap imperfectly. Count organizations and actual production use separately from package downloads, forks, and repeat installs.
Record to inspectReview production references, hosted conversion cohorts, support workload, repository ownership, and release history. Check the permission to reuse code and data rather than assuming public availability grants every right.
Comparison to preserveCompare the commercial workflow with the free alternative. Identify who has budget for reliability, support, or managed operations.
Unresolved case questionWhich users have buying authority?

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 community provides access?
  2. What problem is understood?
  3. What does the fund exclude?
  4. What evidence can the scout add?
  5. What relationship needs permission?

Questions specific to this scenario

  • Which users have buying authority?
  • What makes a hosted account renew?
  • Who can maintain the critical dependencies?

Review production references, hosted conversion cohorts, support workload, repository ownership, and release history. Check the permission to reuse code and data rather than assuming public availability grants every right.

A concrete next test

Ask one production user of the free library and one hosted customer what would make them switch or stop paying. Keep their roles and deployment needs separate. Compare their answers with the proposed commercial conversion path and actual support workload.

Interpret the result

A thesis is useful when it helps the scout choose where to spend time and what to pass on. Revisit it when the fund's mandate or the scout's actual access changes.

Compare the commercial workflow with the free alternative. Identify who has budget for reliability, support, or managed operations.

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.