Library·SOP·Operations
Define, order and maintain the stages used by your sales team, preserving linked opportunities and form configurations.
Last reviewed: · Editorial review
Clarity, structure and references reviewed in this version. This is not a test in a live account.
Build the sales process that opportunities will follow in 6am.
Write down the observable condition for entering each stage. For example: New request → First contact → Proposal sent → Negotiation. Keep the initial stage suitable for unreviewed form submissions. Won and Lost are opportunity statuses; they do not need to be duplicated as stages.
Choose a descriptive pipeline name. Search Sales pipelines before creating another process with the same purpose.
Create one controlled opportunity using SOP 103. Select this pipeline and its first stage. Confirm that the opportunity appears under the pipeline filter and can move to the next stage.
To receive opportunities from a form, follow SOP 075. Configure that form explicitly; creating a pipeline does not activate automation.
Rename or reorder existing stage rows through Edit. This keeps their identities and existing opportunity links. Do not remove and recreate a stage merely to rename it.
A stage referenced by any opportunity or an unarchived configured form cannot be removed. Move the affected opportunities and update the form configuration first. Historical won/lost opportunities count as references. Editing a form saves it as a draft; publish again only after checking its destination.
To archive a pipeline, resolve its open opportunities and remove it from unarchived form configurations. Archive preserves the pipeline, stages and history. Reactivate makes it available again; it does not publish forms or reopen deals. Archived pipelines must be reactivated before editing them.
Record the company, pipeline name, ordered stages, date and the controlled opportunity used to verify it. If a stale-record warning appears, reload and review the newer version before saving. This procedure does not configure revenue reporting, custom fields or automatic messaging.