Most CRMs give you one pipeline. You get your stages -- Lead, Qualified, Proposal, Negotiation, Closed -- and you are supposed to shove every deal through the same funnel. It works fine when you sell one product to one type of buyer. It falls apart the moment your business gets even slightly more complex.
We built SalesSheet for founders and small teams who are actually selling, and the reality is that most of them sell more than one thing. Maybe you have a SaaS product and a consulting service. Maybe you sell to SMBs with a 2-week cycle and enterprises with a 6-month cycle. Maybe you have a US team and a LATAM team with completely different sales motions. Cramming all of that into one pipeline is like using a single to-do list for your work, your groceries, and your home renovation. Technically possible. Practically useless.
If your pipeline stages do not match how a deal actually moves through your process, you are just moving cards around a board. You are not managing anything.
In SalesSheet, you can create as many pipelines as you need. Each pipeline has its own stages, its own deals, and its own metrics. You switch between them with a single click in the pipeline selector at the top of the pipeline view. There is no limit on the number of pipelines you can create, even on the free plan.
Creating a new pipeline takes about 30 seconds. Click "New Pipeline," give it a name, and define your stages. You can start from scratch or duplicate an existing pipeline and modify it. Each stage gets a name, and you can reorder them by dragging. That is the entire setup process.
This is the most common reason teams create multiple pipelines. A company sells both a self-serve product and a managed service. The self-serve pipeline might have three stages: Trial, Activated, Converted. The managed service pipeline might have seven stages: Discovery, Needs Assessment, Proposal, Legal Review, Pilot, Negotiation, Signed. Completely different processes. Completely different timelines. They need to live in separate pipelines because the stages, win criteria, and velocity metrics are all different.
One of our early users runs a marketing agency that also sells a SaaS analytics tool. Before SalesSheet, they used one pipeline and tagged deals as "Agency" or "SaaS." It technically worked, but the pipeline view was chaos. Agency deals sat in "Proposal Sent" for 2 days while SaaS deals sat there for 2 weeks. The averages were meaningless. The forecasts were wrong. Two pipelines solved all of it overnight.
Sales processes vary by geography more than most people expect. A US deal might go from Demo to Proposal to Close. A deal in Germany might require an extra Legal Review stage because of procurement rules. A deal in Japan might need a Relationship Building stage before any formal proposal is even discussed. Multiple pipelines let you model each region's actual process instead of forcing a generic one on everyone.
Inbound and outbound sales are fundamentally different processes. Your inbound pipeline might start with "Website Lead" and move to "Demo Scheduled." Your outbound pipeline starts with "Cold Outreach" and moves to "Reply Received." The stages are different because the motions are different. Running them in one pipeline obscures your conversion data because you are mixing two completely different funnels.
Each pipeline supports saved views. A saved view is a combination of filters, sort order, and visible columns that you can name and switch to instantly. For example, in your Enterprise pipeline you might have saved views for "Deals closing this month," "Deals over $50K," and "Stalled deals (no activity 14+ days)." In your SMB pipeline, you might have "This week's demos" and "Trials expiring soon."
Saved views are personal by default but can be shared with your team. When a manager creates a "Forecast Review" view that filters to deals in Negotiation stage with expected close dates in the current quarter, every rep on the team can access it. This eliminates the weekly scramble of "can you filter the pipeline and screen-share it" during forecast calls.
Every pipeline stage in SalesSheet can be customized with a few key properties. Stage name is obvious. But you can also set a default probability percentage for each stage (used in weighted pipeline forecasting), a target time-in-stage (so you get alerts when deals stall), and required fields (so reps cannot move a deal to Proposal without filling in the deal value).
Required fields per stage is one of those features that sounds minor but transforms data quality. Before required fields, we found that 40% of deals in our users' pipelines had no dollar value attached. After enabling required fields on the Proposal stage, that dropped to under 5%. Good data in, good forecasts out.
Processes evolve. Maybe you realize you need a "Security Review" stage between Proposal and Legal. In SalesSheet, you just drag the new stage into position. Existing deals stay in their current stages. Nothing breaks. Compare this to CRMs where changing pipeline structure requires an admin to submit a support ticket and wait 48 hours. We believe the people using the tool should be able to modify it without gatekeepers.
Sometimes a deal starts in one pipeline and needs to move to another. A self-serve trial converts into an enterprise conversation. A US deal gets handed to the LATAM team. SalesSheet lets you move deals between pipelines with a right-click menu. The deal keeps its full history -- notes, emails, calls, attachments -- and lands in whatever stage you specify in the destination pipeline.
This sounds simple, but try doing it in most CRMs. You usually have to close the deal in one pipeline and re-create it in another, losing all the context. Or you export and re-import. Or you just leave it in the wrong pipeline and tag it with a note. None of those are real solutions. Moving a deal between pipelines should be as easy as moving a file between folders, and in SalesSheet, it is.
Each pipeline generates its own analytics: conversion rates between stages, average time in stage, pipeline velocity, and win/loss ratios. This means you can compare the health of your SMB pipeline versus your Enterprise pipeline without one contaminating the other's metrics. Your SMB pipeline might have a 30% win rate with a 14-day average cycle. Your Enterprise pipeline might have a 15% win rate with a 90-day cycle. Both are healthy -- but you would never know that if you averaged them together in a single pipeline.
You can also view a combined dashboard that aggregates all pipelines for a total revenue forecast. The key is that you have both views: separated for analysis, combined for forecasting.
Not every team needs this feature. If you sell one product to one type of buyer through one process, a single pipeline is cleaner and simpler. Do not create multiple pipelines just because you can. Create them when your existing single pipeline is hiding information from you -- when the averages do not make sense, when deals get stuck at stages that do not apply to them, when your team cannot find their deals in the noise. That is when you know it is time to split.
Multiple pipelines are not about complexity. They are about clarity. Each pipeline should model exactly how a specific type of deal actually moves through your business.
If you are running more than one sales motion through a single pipeline right now, try splitting them in SalesSheet. Create your first pipeline in the pipeline management view, define your stages, and move your deals over. Most teams set this up in under 10 minutes and immediately see clearer data. No migration required -- just create a new pipeline alongside your existing one and start routing new deals into the right place.