Michael ZhaoAPAC / WEB3 / EARLY STAGE
FIELD NOTE / 06 / Post-investment research

Diligence Questions Change after Launch

A live product turns architecture claims into operating evidence. The work shifts toward recurring use, incident response, support load, and the assumptions that no longer fit.

Convert pre-launch claims into observations

Roadmaps, tests, and management explanations carry much of the pre-launch case. Once the product is live, restate those claims as records that can be checked: repeated workflows, maintained integrations, incident ownership, and the location of operating cost.

I revisit the original diligence conclusions and tag what is now supported, what remains open, and what has expired. Adding a metrics appendix is insufficient if the old assumptions remain untouched.

CHECKPOINTS+Workflows that recur without prompting+Ownership of deployment and upgrades+Traceable incident records+Costs that rise first with usage

Track progression, not the launch audience

Campaigns and announcements can fill the top of a funnel. The stronger signal is progression: a second deployment, an integration that survives an upgrade, or an institutional trial that enters another internal review.

Those participants follow different paths. One retention curve can mistake a completed experiment for abandonment and a stalled evaluation for continued adoption.

An incident log can be more useful than a smooth update

Faults are expected in young products. The evidence lies in detection, communication, recovery, and whether the same failure returns. A blank incident history can indicate stability or weak observation.

Resolved is too broad a status. Separate impact, containment, root-cause progress, and the verification that closes the record.

Keep support load on its own line

Greater usage can increase infrastructure cost, manual support, and requests for bespoke work at the same time. Activity alone does not show which burden is rising or who absorbs it.

I separate standard support that can be automated, exceptions that require engineering, and custom work for one participant. The mix shows whether the product is becoming easier to deliver.

Tie support back to the thesis

Market entry, hiring, fundraising, and product changes may all be sensible. Each should still connect to a constraint identified in the investment work.

The updated note should name the evidence that strengthened, the premise that weakened, and the next unresolved question with the greatest bearing on the case.