The ADIN blog
Practical guides and worked examples for founders, angel investors, scouts, limited partners, and fund managers.
1,000 articles published · Page 12 of 42
265 / Angel investors
a developer infrastructure startup: Assess overlap by the underlying exposures and dependencies of the portfolio, not only company labels.
Read the guide →266 / Limited partners
a pre-seed venture fund: Test whether fund size, initial checks, reserves, costs, and company count fit together.
Read the guide →267 / Scouts
a developer infrastructure startup: Use feedback to improve relevance and evidence, not merely to chase a different pitch.
Read the guide →268 / Fund managers
a pre-seed venture fund: Prepare references who can speak to specific relevant work, with their permission and without scripting an endorsement.
Read the guide →269 / Founders
AI workflow automation: Organize an early data room around the claims a reviewer needs to test.
Read the guide →270 / Angel investors
a climate software startup: Reassess a follow-on using the evidence and terms available now.
Read the guide →271 / Limited partners
a seed venture fund: Investigate unrealized values through the policy, valuation date, evidence, and review process.
Read the guide →272 / Scouts
a climate software startup: Maintain an evidence trail that records relationship context, consent, source dates, introductions, and milestone changes.
Read the guide →273 / Fund managers
a seed venture fund: Explain operating responsibilities through actual work and authority.
Read the guide →274 / Founders
AI analytics copilots: Find a budget owner by tracing how a comparable purchase is proposed, approved, and renewed.
Read the guide →275 / Angel investors
a deep tech startup: An SPV adds a vehicle and operating arrangement that deserve separate attention from the underlying company.
Read the guide →276 / Limited partners
an AI specialist venture fund: Operational diligence asks who performs the work, what controls exist, and what evidence supports them.
Read the guide →277 / Scouts
a deep tech startup: Demonstrate domain knowledge through better questions, relevant evidence, and a clear account of uncertainty.
Read the guide →278 / Fund managers
an AI specialist venture fund: Track unresolved LP questions as an evidence workflow rather than a sales-pressure queue.
Read the guide →279 / Founders
AI document processing: Recruit design partners for learning access and relevant use, with explicit expectations about time and scope.
Read the guide →280 / Angel investors
a healthcare software startup: Distinguish a source's direct observation from their opinion, inference, or relationship with the company.
Read the guide →281 / Limited partners
a sector specialist venture fund: Examine alignment through the actual economics, decision responsibilities, constraints, and conflicts.
Read the guide →282 / Scouts
a healthcare software startup: A sourcing thesis explains which founders and problems a scout can encounter and understand through a real network.
Read the guide →283 / Fund managers
a sector specialist venture fund: Prepare evidence that lets an LP examine the fund's strategy, relevant experience, portfolio model, economics, and operating readiness.
Read the guide →284 / Founders
AI customer support agents: Scope a first pilot around one workflow and an agreed decision.
Read the guide →285 / Angel investors
an early marketplace startup: Investigate downside through concrete failure paths and dependencies rather than a generic risk list.
Read the guide →286 / Limited partners
a generalist venture fund: Ask how the manager allocates opportunities, expenses, and attention among funds, SPVs, personal holdings, and related relationships.
Read the guide →287 / Scouts
an early marketplace startup: Verify fit and basic facts before introducing a company, while remaining clear about what has not been investigated.
Read the guide →288 / Fund managers
a generalist venture fund: Explain attribution investment by investment.
Read the guide →
