In this guide
Define the stages plainlyKeep quantity estimates conditionalUse the pipeline for a reviewAvoid customer-facing overclaimsAn enquiry is not the same as an approved order, and an approved order is not the same as a completed provider action. Keep these states separate when reviewing workload or a credit reorder. A pipeline is an internal view of uncertainty, not a guarantee of future sales.
Define the stages plainly
Use stages that match the actual process: enquiry, scoped quote, customer instruction received, provider action pending and confirmed result. Record the relevant evidence for each transition. Do not label a casual question as a purchase merely because a customer asked about a price.
Keep quantity estimates conditional
If planned actions require credits, use only provider-confirmed consumption for those exact actions. Do not multiply every enquiry by an invented conversion. Separate confirmed commitments from possible future work so a reorder review can see the uncertainty.
| Stage | What it establishes |
|---|---|
| Enquiry | A question was asked |
| Scoped quote | A defined offer was supplied |
| Customer instruction | A specific action was requested |
| Provider pending | Result not yet confirmed |
| Confirmed result | Actual completed outcome recorded |
Use the pipeline for a review
A team can compare confirmed available credits, confirmed upcoming actions and unresolved conditions. Dream’s published package totals provide purchase arithmetic, but not a demand forecast, expiry rule or permitted-use answer. Keep those inputs separately sourced.
Avoid customer-facing overclaims
Do not publish an internal pipeline count as a customer total, growth statistic or guaranteed capacity. If an illustrative example is used, label it hypothetical. Review old entries and close or update them when the actual customer instruction changes so the working view remains meaningful.
Questions about this guide
Can an enquiry reserve credits automatically?
No such rule is established here. Any reservation process must come from the actual system and the team’s authorised workflow. Do not infer a provider feature or account deduction from an internal pipeline label.