How to Customize Lio's Sales Pipeline Templates for Your Sales Team

TL;DR: Most pipeline template guides stop at renaming stages. This one walks IT company owners through Lio's default templates, what you can and cannot change, and a decision matrix for knowing when to customize versus adopt as-is — without breaking the lead capture and assignment engine that keeps your response times fast.

What Lio's default pipeline templates include

Lio's default pipeline templates ship with seven stages out of the box: New Lead, Contacted, Qualified, Proposal Sent, Negotiation, Closed Won, and Closed Lost. That covers the standard B2B sales motion well enough for most IT service teams to run a real pipeline from day one without touching a single setting.

Each stage comes pre-loaded with a core field set: contact name, company, email, phone, deal value, expected close date, and lead source. These defaults handle roughly 80% of what a typical IT sales rep needs to log during a deal cycle. The custom field sets across leads, companies, contacts, deals, and pipelines become relevant once your team's qualification criteria or deal data don't map cleanly onto those defaults.

What you get before any Lio sales pipeline templates customization is a functional lead qualification workflow, basic deal tracking, and stage-level visibility across your team. That's a usable starting point, not a finished system.

The gaps show up quickly in practice. A managed services provider selling multi-year contracts needs different stage exit criteria than a VAR closing transactional hardware deals. Understanding what the template includes by default is the first step toward building a pipeline that reflects your actual deal cycle rather than a generic one. The next section gives you a decision matrix to determine exactly where to customize and where to leave the defaults alone.

The Modify vs. Adopt Decision Matrix

Use this matrix before touching a single stage in Lio's custom sales pipeline builder. The decision isn't "do I want to customize?" — it's "does the default template already match how my team actually sells?"

Adopt the template as-is when:

• Your average deal cycle is under 30 days

• Your team has fewer than five reps and one product line

• You're in a horizontal vertical (general IT services, managed support) where no stage is industry-specific

• You're setting up a net-new pipeline and want a working baseline before you have real data

Modify the template when any of these are true:

• Your deal cycle runs 60-plus days and involves procurement, legal, or a security review stage that the default doesn't include

• You sell into a specific vertical (healthcare IT, fintech, government) where stage names and qualification criteria differ from generic SaaS defaults

• Your team uses a defined methodology (MEDDIC, BANT) and needs custom fields to enforce it at each stage

• You need pipeline automation rules to fire on stage transitions — lead assignment, follow-up tasks, notifications — and the default stage sequence doesn't match your triggers

One practical signal: if your reps regularly skip a default stage or manually move deals backward to compensate for a missing step, the template isn't matching your selling motion. That's the clearest sign to customize rather than adapt behavior around a broken structure.

Team size matters less than deal complexity. A three-person team selling six-figure infrastructure contracts needs more customization than a fifteen-person team closing transactional renewals. Match the pipeline to the deal, not the headcount.

Once you've made the call, mapping your selling motion to specific pipeline stages before you configure anything saves significant rework later.

How to customize stages, fields, and automation rules in Lio

Open Lio in a second tab while you read this. The configuration steps below follow the product's actual UI flow, so you can make each change as you go.

Customizing stages is the first move. In your pipeline settings, you'll see Lio's default stages: New Lead, Contacted, Qualified, Proposal Sent, Negotiation, and Closed Won / Closed Lost. To rename a stage, click the stage name inline and type. To reorder, drag the stage card left or right. To add a stage, hit the "+" at either end of the pipeline or between any two existing stages. Removing a stage requires you to reassign any deals sitting in it first — Lio will prompt you before it lets you delete.

Custom fields come next. Navigate to Settings > Field Sets, then pick the object you want to extend: Leads, Deals, Companies, Contacts, or Pipelines. Lio supports text, email, phone, date, select (single and multi), and checkbox field types. A practical example: an IT reseller adding a "License Renewal Date" date field on Deals, then surfacing it in the pipeline card view so reps see renewal windows without opening each record. If you want a consistent intake form, customize sales pipeline stages alongside your field set so the fields you collect at entry match the stage they belong to.

Automation rules are configured under Settings > Automations. The basic structure is trigger → condition → action. A useful starting rule for most IT sales teams:

1. Trigger: Lead moves to "Proposal Sent"

2. Condition: Deal value is above your threshold (e.g., $10,000)

3. Action: Assign to senior rep + send internal Slack notification

You can stack multiple actions on a single trigger. Keep each rule to one clear outcome. Teams that pile three or four actions onto one trigger tend to create conflicts that are hard to debug later.

Pipeline automation rules tied directly to stage transitions are what separate a configured pipeline from a working one. Get the stages right first, then layer fields, then automate — in that order.

Constraints and best practices when modifying Lio templates

Some parts of Lio's pipeline structure are fixed by design, and editing around them without understanding why they exist will cost you.

Lead assignment speed depends on stage order: Lio's automation rules fire sequentially based on stage position. If you reorder stages after setting up assignment rules, those rules can misfire or skip triggers entirely. Always audit your automation rules after any stage reorder, not before.

The default entry stage also anchors your lead qualification workflow. Renaming it is fine. Removing it or replacing it with a custom stage that lacks the same trigger conditions will break incoming lead routing. If you're unsure, duplicate the stage first and test with a sample lead.

A few constraints worth knowing before you customize sales pipeline stages:

• Automation rules tied to a deleted stage are not automatically reassigned. They go inactive silently.

• Custom field sets on deals are pipeline-specific. Changing a field type after data exists in that field will corrupt historical records.

• Stage-level probability weights feed your forecast. Adjust them deliberately, not as a side effect of renaming.

For sales pipeline visibility to stay accurate, keep stage names and probability weights in sync whenever you restructure. Lio's custom sales pipeline builder shows exactly where those weights live in the UI.

If you want the deeper rationale, building a pipeline that reflects your actual deal cycle covers why stage design and forecast integrity are inseparable.

How to run multiple pipelines for different teams or verticals

Each pipeline in Lio is fully independent. Stage names, stage count, and the custom fields attached to each deal record can all differ between pipelines without affecting each other. That means your enterprise software team can run a six-stage pipeline with fields for contract value, compliance requirements, and procurement contact, while your SMB team runs a three-stage pipeline with nothing but a budget qualifier and a close date.

To set this up, open Lio's custom sales pipeline builder and create a new pipeline for each team or product line. Assign a distinct field set to each one. Custom fields for leads and deals — text, select, date, phone, and others — are configured at the pipeline level, so changes in one pipeline never bleed into another.

A few practical rules for multi-pipeline sales teams:

• Name pipelines after the team or vertical, not the stage logic. "Enterprise APAC" is easier to navigate than "Pipeline 3."

• Keep stage count under eight per pipeline. More than that and forecast accuracy drops.

• Before you finalize stage logic, read how to map your selling motion to specific pipeline stages — stage order directly affects how fast leads get assigned.

How pipeline customization connects to lead capture and assignment

The order of your pipeline stages isn't just an organizational choice — it's the trigger logic that determines how fast a lead gets assigned to a rep.

Lio's Smart Lead Distribution reads your stage configuration to decide when and how to route an incoming lead. If your first stage is "New Inquiry" with a qualification field attached, Lio can score and assign that lead the moment it enters, before a rep ever opens their inbox. Move that qualification step to stage three, and assignment waits. The stage order you set during pipeline setup directly controls your response window.

Custom fields sharpen this further. Attaching a "Lead Source" or "Budget Range" field to an early stage gives the distribution engine the data it needs to route by territory, deal size, or product line — which is where pipeline automation rules and sales pipeline visibility start working together rather than separately.

For IT companies managing multiple service lines, this means your lead qualification workflow can differ per pipeline while the same Smart Lead Distribution logic runs underneath each one.

Lio customizable pipelines vs. static templates in other tools

Most tools give you a template and call it done. You can rename a stage, maybe reorder it, and that's the extent of "customization." When your deal cycle changes, you rebuild from scratch.

Lio's custom sales pipeline builder works differently. Stages aren't just labels — they carry trigger logic. Move a lead to "Proposal Sent" and an automation rule fires: follow-up task created, owner notified, timer started. That connection between stage position and action is what drives pipeline automation rules that actually reduce response lag.

For teams mapping their selling motion to specific pipeline stages, that rebuild cost difference compounds fast. One process change in a static tool means hours of reconfiguration. In Lio, it's a stage edit.

Closing

The real power of Lio's templates isn't in the defaults — it's in knowing which ones to keep and which ones to reshape around your actual deal cycle. Use the Modify vs. Adopt Decision Matrix to make that call before you touch a single stage. Then layer in custom fields and automation rules in that exact order, and audit your rules after any structural change. Start with the default template, visit Lio's custom sales pipeline builder feature page to see the drag-and-drop stage editor in action, and use the matrix to decide what to change first. Your pipeline should reflect how you sell, not force your team to sell around a template.

FAQ