Custom pipelines in TatvaCRM
How to create and manage multiple custom pipelines in TatvaCRM. When to add a second pipeline, how to route deals to the right one, and how to view per-pipeline forecasts.
Most businesses start with one pipeline and add more as their sales motions diverge. This page covers when to add a second (or third) pipeline, how to create it, and how to keep deals from leaking between them.
Common pipeline splits
| Split | Why |
|---|---|
| New Business vs Expansion | Acquisition cycles look very different from upsells to existing customers |
| SMB vs Enterprise | Sub-₹2L deals vs ₹20L+ deals have very different stage durations |
| Inbound vs Outbound | Inbound leads pass discovery faster; outbound leads need pre-qualification |
| Product A vs Product B | If your two products sell to different buyers entirely |
| Sales vs Renewals | Renewal cycles are calendar-driven, sales cycles are demand-driven |
Creating a new pipeline
- Go to Settings → Pipelines → New pipeline
- Name it descriptively (“New Business — B2B SaaS”, “Expansion — Existing Customers”)
- Add stages with names and default probabilities
- Pick a default pipeline (the one that appears when a user creates a new deal)
- Save
You can clone an existing pipeline if your new one shares most stages — useful for variations of the same process.
Routing deals to the right pipeline
Three approaches:
Manual selection
When creating a Deal, the user picks the pipeline from a dropdown. Works well for small teams where everyone knows which pipeline goes with which deal.
Routing rules (Pro+)
Auto-route based on conditions: “If deal value > ₹10L, use Enterprise pipeline.” Configure under Settings → Pipelines → Routing rules.
Per-team default
Assign a default pipeline per team — the SDR team’s default pipeline is New Business, the CS team’s default is Expansion.
Viewing multiple pipelines
The Pipeline page has a pipeline switcher at the top. Switch between pipelines to see each one’s Kanban view. The Forecast view aggregates across all pipelines by default — filter to one pipeline if you want a focused number.
Pipeline visibility per role
You can restrict pipelines per role. The Expansion pipeline might be visible only to your Customer Success team; the New Business pipeline visible to everyone. Configure under Settings → Pipelines → [Pipeline] → Access control.
Moving a deal between pipelines
Open the deal, click More → Move to another pipeline, pick the new pipeline and stage. Stage mapping is manual — you choose where in the new pipeline this deal sits. History stays intact, including the time the deal spent in the original pipeline.
Common questions
“Can I archive an old pipeline without deleting it?”
Yes. Set the pipeline to “Archived” — it stops appearing in new-deal dropdowns but historical deals stay attached. Useful when you’ve evolved your sales process and don’t want to lose old reports.
“I created the wrong pipeline. Can I delete it?”
Yes, if no deals are attached to it. If deals exist, you’ll need to either delete those deals first or move them to another pipeline.
“How many pipelines is too many?”
Three is usually enough. Five is a lot. Above five, your team will pick the wrong pipeline routinely. If you find yourself needing many pipelines, consider whether some of them should actually be a single pipeline with different starting stages.