# Pipeline customization Pipelines in Fluid are flexible by design. They adapt to how you actually sell, not the other way around. *** ### What pipelines are in Fluid A pipeline represents a sales or task motion. You can use pipelines to: * Separate different businesses * Separate different services or offers * Separate inbound and outbound sales * Separate sales from onboarding, partnerships or client delivery * Separate personal and team workflows Fluid does not limit how many pipelines you can create. There are: * No upgrade requirements * No artificial restrictions * No feature gating * No "pro plan" to unlock more pipelines You can create as many pipelines as you need on every plan. ### Create and manage multiple pipelines You can create pipelines directly from the Deals view. From there, you can: * Create a new pipeline * Switch between pipelines from the dropdown at the top * Edit an existing pipeline * Duplicate a pipeline to use as a template * Delete pipelines when they are no longer needed This allows you to run multiple businesses or sales motions inside one workspace without mixing contexts. ### Control pipeline visibility for teammates Pipelines can be scoped to specific users. For each pipeline, you can define: * Which team members can see it * Whether a user is an owner or a member of that pipeline This allows setups like: * One assistant seeing only one pipeline * Partners accessing only their relevant deals * Separate teams working in separate pipelines * Client-facing pipelines hidden from internal teams Because of this, Fluid can be used across multiple businesses and teams inside the same workspace without confusion. ### Customize pipeline stages Each pipeline consists of stages that represent how deals progress. You can fully customize stages by: * Renaming stages * Adding new stages * Removing stages * Reordering stages by drag and drop * Adjusting stages at any time There is no "correct" pipeline structure. The goal is alignment with how your real sales conversations move forward. Common pipeline structures by use case: * **Outbound sales:** Positive Reply → Sales Call → Proposal → Negotiation → Won * **Inbound demos:** Demo Booked → Demo Done → Trial → Proposal → Won * **Agency client work:** Discovery → Scope → Contract → Kickoff → Active * **Coaching:** Application → Discovery Call → Offer → Onboarded → Active You can start with one of these and adjust as your process evolves. ### Set deal probability per stage Each stage can have a deal probability. Deal probability is used for forecasting and dashboard calculations. How it works: * Each deal has a value * Each stage has a probability percentage * The weighted value is calculated automatically Example: * Deal value: €5,000 * Stage probability: 10% * Weighted value shown: €500 This allows you to: * See realistic pipeline value * Understand expected revenue by stage * Get meaningful data in the Dashboard and Forecast views * Make better hiring, spending and planning decisions Probabilities do not affect daily execution. They exist to improve visibility and decision-making. Default probabilities you can start with: * Early stages (Positive Reply, Demo Booked): 10 to 20% * Mid stages (Sales Call, Proposal): 30 to 50% * Late stages (Negotiation, Contract): 60 to 80% * Closed Won: 100% Adjust based on your actual close rates over time. ### Edit pipelines without breaking your workflow You can safely edit pipelines at any time. When you: * Rename stages * Reorder stages * Adjust probabilities * Add new stages Existing deals adapt automatically. This means you can evolve your pipeline as your sales process improves, without losing data or momentum. ### Delete a pipeline safely Pipelines can be deleted when they are no longer needed. To prevent accidents, Fluid requires confirmation: * You must explicitly confirm the deletion * A warning shows you how many deals will be affected After deletion: * Pipeline settings can be restored for 30 days * Restoration is available from Settings, then Data, then Restore pipeline This safety mechanism exists to protect historical data and prevent irreversible mistakes. ### Why pipeline customization matters Pipelines in Fluid are not about reporting for managers. They are about: * Reducing mental load * Separating contexts cleanly * Supporting accurate forecasting * Letting you focus on execution instead of structure Pipelines organize work. Reminders drive action. ### What to read next * Field customization, how to customize deal fields per pipeline * Deals, how deals move through pipelines * Forecast, how pipeline data drives revenue visibility * Automations, how to automate stage actions and notifications --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://fluid-crm.gitbook.io/fluid-crm-docs/getting-started/pipeline-customization.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.