If you are starting from the Phage Project Success Hub, this guide is designed to help you translate a scientific objective into a right-sized, decision-ready service package from Creative Biolabs, with clear deliverables you can use to move to the next phase. All services and outputs described on this page are for research use only and are not intended for clinical diagnosis or therapeutic applications.
A recurring problem in phage projects is not the lack of assays, but the lack of a minimal, coherent dataset that supports a go/no-go decision. Teams either over-purchase early (collecting data they cannot interpret yet) or under-purchase (missing one critical confirmation that later forces a restart). The goal of this page is to prevent both outcomes by mapping common end goals to a goal-driven decision tree, defining minimal viable data packages, and calling out the most frequent “looks fine on paper” pitfalls.
Before you select any package, write down the single primary output you need at the end of the current stage. In most phage workflows, your end goal is one of the following:
If you are not sure which category you are in, use this rule: your “final output” is the artifact that lets you confidently decide what to do next without repeating upstream work.
This Phage Service Selection Guide is organized as a goal-driven decision tree. Read the “If your goal is…” statement, then follow the recommended path to a minimal package that is sufficient to proceed.
Choose an isolation-first path when you need new phage candidates from environmental or custom samples and do not yet have a confirmed lytic phage in hand.
Choose a host-range-first path when you already have a phage and the next decision depends on which hosts are permissive and how strongly.
Choose a sequencing-first path when you need to de-risk candidates before investing in scaling, purification, or engineering.
Choose a purification-first path when material quality, buffer exchange, or contaminant removal is the bottleneck for downstream research.
Choose a display-first path when objective is selection/enrichment of binders and next step depends on validated hits.
Choose an engineering-first path when the needed modification is understood and build feasibility is the main risk.
A minimal viable data package is the smallest set of deliverables that allows you to proceed without redoing upstream work. Below are pragmatic “must-have” packages aligned to common goals in this Phage Service Selection Guide.
You should require: a record of sample origin and handling; host strain identity and culture conditions; plaque purification history (with passage count); a baseline titer range with the method used; and an archive plan (storage condition, labeling, and traceability).
If any one of these is missing, teams often discover later that their “best candidate” cannot be reproduced outside the original setup.
Suggested add-on when scaling decisions are near: Genome sequencing and annotation to support early risk screening via Phage Genome Sequencing and Phage DNA Analysis.
You should require: the complete host panel list with strain identifiers; assay definition (spot test vs plaque assay logic); replicate policy; a rule for calling positives; and a quantitative confirmation step for any “important positive” before you commit to the next stage.
In practice, many projects fail here because they only capture “lysis yes/no” and cannot distinguish productive infection from ambiguous clearing. If your downstream plan depends on true propagation in the host, your dataset must reflect that.
You should require: assembly summary metrics (coverage, contig structure, completeness indicators); an annotation file; a screened feature list that flags elements you consider incompatible with your research plan; and a recommended experimental action list (keep, drop, re-isolate, re-sequence).
Pairing Phage Genome Sequencing with Phage DNA Analysis is often the fastest route to a decision-ready package rather than a raw sequence you must interpret internally.
You should require: starting lysate provenance; purification workflow summary; titer before and after; buffer composition; storage condition; and QC notes relevant to your downstream assay.
If your assay is sensitive to residual host material, do not accept a package that reports only PFU/mL. High titer does not automatically mean high suitability.
This section exists because most delays are avoidable and tend to repeat across teams.
If you advance a mixed population, you may later discover the phenotype you cared about belongs to a minority phage. "Time saved" becomes time lost if you must re-isolate. Plaque purification history belongs in your minimal package.
A high titer can coexist with poor target host performance, inconsistent morphology, or instability across passage. Do not treat PFU/mL as a proxy for functional suitability.
Spot tests are useful screens but can overcall positives due to non-productive effects. Build quantitative confirmation rules via Phage Test and Phage Analytics.
Sequencing is a decision tool. If you do not define stop or redesign triggers, you end up with a nice assembly and no action. Pair Phage Genome Sequencing with Phage DNA Analysis to produce a screening-informed recommendation.
If you cannot state the next go/no-go decision, you cannot define the right deliverables. Start with the decision gate, then select the minimal viable package that supports it.
You can reduce project turnaround variability by providing a complete input set up front. Use the checklist below as a practical intake guide.
Provide sample type and origin (environmental, industrial, lab stock), collection date, storage condition, any filtration steps already performed, and any safety or handling constraints. If multiple samples exist, prioritize those most likely to contain your target host.
Provide host strain identifiers, growth medium and temperature, antibiotic markers if relevant, and any known restriction-modification systems or resistance traits if you track them. If you need a host panel for host range, specify the full list and what “positive” means for your application.
Provide your ideal decision deadline, acceptable iteration count, and constraints such as “must use this host,” “must avoid this buffer,” or “must deliver sequence before purification.”
Provide a pass/fail statement in plain language, such as: “Select 1–3 candidates that propagate on Host A and at least 30% of the panel,” or “Deliver a genome and annotation suitable for comparative analysis and engineering design.”
Host range is not just a label; it is a structured interaction dataset that can be represented as a network or matrix and used to guide selection strategy. An open-access example illustrates how phage–host interactions can be visualized to make decisions transparent and reproducible.
Fig.1 Phage–host interaction network for host range interpretation¹
This type of visualization is useful in service planning because it forces clarity: which hosts were tested, what counts as a positive interaction, and how candidate phages differ in breadth and specificity. It also makes it easier to define your “next stage” rules, such as selecting candidates that cover a defined subset of hosts, or prioritizing candidates for sequencing and downstream development.
Q: What is the fastest way to choose a phage service package if I am starting from scratch?
Q: Why do you emphasize minimal viable data packages instead of “as much data as possible”?
A: Because phage workflows are iterative, and the most expensive delays come from missing one critical confirmation that forces you to repeat upstream steps. A minimal viable package is designed to be sufficient for the next decision, so you can move forward without rework.
Q: Do I always need genome sequencing before purification or testing?
A: Not always. If your immediate goal is a host range decision on a small panel, Phage Test and Phage Analytics may come first. Sequencing becomes high value when you need de-risking, triage across multiple candidates, or a foundation for engineering and comparative analysis via Phage Genome Sequencing and Phage DNA Analysis.
Q: What should I provide so you can quote accurately without multiple back-and-forth emails?
A: Provide your target host strain identifiers, sample type and handling history, the output you need at the end of this stage, your timeline, and any constraints (buffers, hosts, assay requirements). A clear success criterion dramatically improves package selection and reduces iteration.
Q: Can you support display workflows or engineered phage research workflows within the same project plan?
A: Yes. If your goal is display hit discovery and enrichment, use the Phage Display Platform. If your goal is engineered builds for research testing, use the Engineered Phage Platform. In both cases, define the acceptance criteria up front so the package can be aligned to measurable outcomes.
Q: Are these services intended for clinical applications?
A: No. All services and deliverables referenced in this Phage Service Selection Guide are for research use only and are not intended for clinical diagnosis or therapeutic use.
Reference:
Please kindly note that our services can only be used to support research purposes (Not for clinical use).
Creative Biolabs is a globally recognized phage company. Creative Biolabs is committed to providing researchers with the most reliable service and the most competitive price.
