How can an angel distinguish references from independent evidence for a healthcare software startup?

Distinguish a source's direct observation from their opinion, inference, or relationship with the company. References can be informative and biased at the same time. Important claims deserve a provenance trail and, where feasible, corroboration.

Start with the decision

For each claim, record the source, relationship, date, actual observation, and available supporting record. Seek permission before sharing private statements. Preserve contradictions instead of selecting only the reference that supports the preferred decision.

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 team is piloting an administrative scheduling product with a provider group. Staff use it in a narrow workflow, while procurement and data review determine whether a broader rollout is possible.

A clinic's enthusiasm does not resolve data handling, workflow ownership, or applicable regulatory questions. This example does not assume a particular legal classification or approval.

Turn the scenario into an evidence decision

Consider a review of a healthcare software 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 authorized workflow observations, procurement requirements, permissioned usage evidence, and specialist advice about applicable obligations. Avoid using identifiable patient information in a diligence packet. 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. Source quality depends on relevance and independence as well as reputation. A detailed firsthand account can answer a narrow question while remaining insufficient to support a broader claim about the company. 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.

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 was directly observed?
2. When was it observed?
3. What relationship exists?
4. Can a record corroborate it?
5. Which source disagrees?

Questions specific to this scenario

• Which workflow is actually in scope?
• Who approves data access?
• What specialist review is needed?

Review authorized workflow observations, procurement requirements, permissioned usage evidence, and specialist advice about applicable obligations. Avoid using identifiable patient information in a diligence packet.

A concrete next test

Ask the authorized workflow owner to map a narrow administrative use case without disclosing patient information. Identify the data-access and procurement approvals needed for the next step. Keep operational adoption evidence separate from claims about clinical benefit or regulatory status.

Interpret the result

Source quality depends on relevance and independence as well as reputation. A detailed firsthand account can answer a narrow question while remaining insufficient to support a broader claim about the company.

Compare the administrative workflow and rollout dependencies with the current process. Do not treat an operational pilot as clinical efficacy evidence.

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.

• Angel Capital Association: Knowledge Center
• Investor.gov: Private Equity Funds