Next steps
What to do once you've exported results — verify outputs, hand off to external tools, and translate in-silico predictions into wet lab experiments.
Computational results are the start of a decision, not the end of the work. You've folded a structure, docked a ligand, profiled ADMET, or run a multi-step chain — now you have exported files and predictions that need to be verified, moved into your own analysis stack, and turned into experiments. This section covers everything that happens after the export: confirming your outputs are intact, integrating them with external tools, and prioritizing which computational hits are worth wet lab time.
These guides are tool-agnostic. Whether you ran ESMFold, DiffDock, ADMET-AI, or a multi-step chain, the post-export and wet lab transition principles apply equally — so read them once, and reuse them across every campaign.
The through-line is to verify before you act on a prediction. A docking score, an ADMET flag, or a predicted structure is a hypothesis with a confidence attached, not a fact — the playbook shows you how to sanity-check exported outputs before you commit synthesis budget or bench time to them.
What this section covers
Post-export playbook
File-integrity checks, external analysis tools, data archival, and sharing results with collaborators or ELNs like Benchling.
From predictions to the wet lab
Prioritizing hits for synthesis, dose-response screening, lead optimization, CRO engagement, and IND-enabling considerations.
Where to start
Read the two pages in order. The post-export playbook comes first — it verifies the files you just exported are complete and correct, then hands them off cleanly to your own tooling. The wet-lab guide comes second: once you trust the outputs, it helps you decide which candidates justify synthesis and screening, and how to sequence the move from in-silico to the bench.
Read next
Was this page helpful?