What to Send a Synthesis Partner to Get a Fast, Accurate Quote (and Avoid Scope Drift)
One of the fastest ways to lose time in a chemistry program is an avoidable loop of clarification emails:
- “What purity do you need?”
- “Do you have a preferred salt form?”
- “Is this for discovery or cGMP?”
- “Do you need plate formatting?”
- “Do you require method development or just release testing?”
You can compress that cycle dramatically by sending a complete, sponsor-friendly request package upfront. Here’s a practical checklist that works across research compounds, APIs, and CDMO engagements.
1) Compound identity and structure package
Include:
- structure file (SMILES/MOL/SDF preferred)
- CAS (if available)
- internal compound ID(s)
- stereochemistry notes (if relevant)
- known stability concerns (light, moisture, oxidation)
Why it matters: feasibility, route choice, analytical approach, and risk profile all start here.
2) Quantity and delivery format
Include:
- target quantity (and whether it’s a one-time need or recurring)
- preferred delivery format:
- single vial vs multi-vial set
- plate-ready format for libraries
- free base vs salt
- concentration or solvent requirements (if applicable)
Why it matters: packaging, QC sampling, and production planning change based on format.
3) Specifications and acceptance criteria
Include:
- purity target (and method preference if you have one)
- assay target and tolerances
- critical impurity constraints (if known)
- residual solvent limits (if you have a standard)
- any elemental impurity constraints (stage-dependent)
Why it matters: “high purity” is not a single standard. Target criteria drive route and purification decisions.
4) Program stage and required grade
Include:
- discovery / screening
- lead optimization
- preclinical / tox
- clinical (non-GMP vs cGMP)
- commercial readiness considerations (if relevant)
Why it matters: documentation, QA oversight, testing expectations, and release processes vary by stage.
5) Analytical expectations and documentation
Include what you expect to receive:
- CoA detail level
- identity confirmation expectations
- raw data needs (if any)
- method development/optimization needs
- stability planning/studies (if in scope)
- CMC/regulatory support needs (if applicable)
Why it matters: misalignment here causes the most common scope changes.
6) Timeline, shipping, and handling constraints
Include:
- required delivery date (and whether timing is “hard” or “preferred”)
- destination country
- cold-chain needs (if any)
- storage requirements
- hazardous/potency handling notes (if relevant)
Why it matters: logistics can be as schedule-critical as synthesis.
7) For analogue series and libraries: add a mapping table
If you need multiple compounds:
- list each target with structure/ID
- specify common core + variable positions
- note desired plate map or vial labeling scheme
- define “must-have” vs “nice-to-have” compounds if time is tight
Why it matters: avoids confusion, accelerates execution, and prevents labeling errors.