Building a Sales Process One Deal Type at a Time

Most sales teams run one pipeline for all deals. New logo prospects, expansion conversations with existing customers, and renewals all move through the same stages with the same exit criteria and the same expected close timelines. It's the default because it's simple to set up.

But it produces a pipeline that predicts nothing and coaches nothing. The solution starts with designing pipeline stages that actually match how customers buy, then layering deal-type segmentation on top.

A renewal at Stage 3 is not the same as a new logo at Stage 3. A new logo requires the buyer to make an entirely new commitment; a renewal requires them to re-justify an existing one. The risks are different, the objections are different, the stakeholders involved are different, and the average time to close is different. Running them through the same process means your stage definitions fit neither well.

The goal here isn't to create a dozen pipeline variants that make your CRM unmanageable. It's to design three distinct process tracks, one for each core deal type, that improve forecast accuracy and give managers something specific to coach against.

---

Why One-Size-Fits-All Pipelines Mislead Managers

When you blend deal types in a single pipeline, two things go wrong.

Gartner research on sales pipeline management found that organizations with deal-type segmentation in their CRM achieve 28% higher forecast accuracy and significantly better coaching specificity compared to those running a single blended pipeline.

First, your metrics become uninterpretable. Your win rate is probably somewhere between 20-50%, but that average hides the fact that renewals close at 80%, expansions at 55%, and new logos at 25%. Those are three different business realities. A "blended 40% win rate" produces neither insight nor useful goals.

Second, your stage definitions stop reflecting real buying behavior. Stage 3 means "proposal delivered" for a new logo (where the buyer is still learning) and something very different for a renewal (where the buyer already knows the product and is evaluating switching costs). A manager looking at "10 deals at Stage 3" sees a number, not a business.

The fix isn't more complexity. It's appropriate segmentation: separate processes for deals that are genuinely different, unified infrastructure so you don't manage three completely separate CRM systems.

---

Step 1: Identify Your Core Deal Types

Most B2B sales teams can cover 90% of their revenue with three deal types:

New Logo: Net-new customer acquisition. The buyer has no existing relationship with your company and is making a new purchasing decision.

Expansion: Selling additional products, seats, or scope to an existing customer. The relationship exists; the question is whether to grow it.

Renewal: Re-committing an existing customer to continued service before a contract expires. The default is continuation; the risk is churn.

Before you build distinct processes, count your deals by type for last year. If 90% of your revenue comes from new logos with only occasional expansions and renewals, designing full processes for all three might be premature. Focus on new logos first and add the others when volume justifies it.

If you have a mix, segment now. And resist the temptation to add a fourth type immediately. More than three deal types in the first iteration creates more problems than it solves.

---

Step 2: New Logo Process Design

New logo deals are the hardest to close and the longest to manage. Every stage exit criteria should reflect a genuine shift in buyer commitment.

Recommended stages:

Key characteristics of new logo process:

• Longest average cycle length (typically 2-4x longer than expansion)
• Highest risk of multi-stakeholder complexity
• Requires explicit discovery of problem, budget, and buying process
• Champion identification is a stage requirement, not an optional activity
• Competition is most active here

Qualification questions unique to net-new:

• Why are they looking now? (trigger event)
• Who else is evaluating, internally and externally?
• How have they bought software like this before?
• What would make them stay with the status quo?

Each of these maps to a specific criterion in your qualification framework. If you're using MEDDIC, for instance, the trigger event maps to "implicate the pain" and the stakeholder question maps to economic buyer identification.

---

Step 3: Expansion Process Design

Expansion deals are faster to close and require less discovery since the buyer already knows you. But they have a different set of risks.

Recommended stages:

What's different from new logo:

The customer success team often surfaces the expansion opportunity before sales is involved. That handoff from CS to sales needs to be as defined as your SDR-to-AE handoff for new logos. Who triggers it? What information transfers? What's the CS team's role during the expansion sales process?

Expansion deals fail most often for two reasons: the new buyer (say, a different department) doesn't trust the existing relationship, or the existing champion doesn't have authority over the new scope. Both are solvable with early stakeholder mapping.

Stakeholders to identify in expansion:

• The economic buyer for the new scope (may be different from the original buyer)
• The implementation owner (new users often means new IT involvement)
• The internal champion who's advocating for the expansion

---

Step 4: Renewal Process Design

Renewals are the most neglected of the three deal types, often treated as administrative tasks rather than sales processes. That's a mistake. Churn happens most often when renewal is treated as inevitable right up until it isn't.

Recommended stages:

Starting 90 days before renewal is not aggressive. It's the minimum.

Forrester's research on customer retention shows that proactive renewal engagement starting 90+ days before contract expiration correlates strongly with higher renewal rates and lower churn, compared to reactive renewal processes initiated within 30 days.

Teams that start renewal conversations 30 days out are already negotiating from a weak position. The buyer who's been thinking about alternatives for two months will evaluate your renewal proposal differently than one who's been kept engaged and reminded of value throughout the relationship.

What "at risk" looks like 90 days out:

• Usage below expected thresholds
• Unresolved support tickets or product complaints
• Key internal champion has left the account
• Merger, acquisition, or budget restructure at the customer
• No executive sponsor contact in 60+ days

Own any at-risk account before the renewal process formally starts. CS and sales need to agree on what "at risk" means and who is responsible for the recovery plan.

---

Step 5: CRM Implementation

You don't need a completely separate CRM pipeline for each deal type. But you do need deal-type segmentation built into your existing setup.

What to configure:

Deal type field: A required field on every opportunity (New Logo, Expansion, Renewal). This single field is what makes segmented reporting possible. Your CRM data model design should account for this field from the start, not as an afterthought.

Pipeline stages: If your CRM supports multiple pipeline views, create one per deal type. If not, use a single pipeline with stage names that are generic enough to apply to all three (Discovery, Evaluation, Proposal, Negotiation, Closed) but supplement with deal-type-specific requirements tracked in the deal record.

Shared fields (apply to all deal types):

• Deal owner
• Close date
• ARR/TCV
• Forecast category
• Last activity date

Deal-type-specific fields:

• New Logo: Competitor, trigger event, # of stakeholders mapped
• Expansion: Expansion trigger, existing contract end date, CS handoff date
• Renewal: Contract end date, health score, at-risk flag, days since last exec contact

What to avoid: Don't create six stages for new logos and six different stages for renewals if you only have one pipeline view. Your reps will use whatever's simplest. Complexity that isn't used is worse than no complexity.

---

Step 6: Reporting by Deal Type

Once you have deal type tagged on every opportunity, your reporting becomes dramatically more useful.

Metrics that should be reported separately by deal type:

What to look for once you have the data:

If your expansion win rate is 60% and your new logo win rate is 20%, those two parts of your business need completely different coaching priorities. If your renewal cycle is averaging 75 days, you should be starting renewal conversations earlier, not running a faster process.

The blended number doesn't tell you any of this.

---

Common Pitfalls

According to a McKinsey analysis of B2B revenue operations, companies that segment their sales process by deal type report 15–20% improvements in average deal velocity, primarily because stage exit criteria become more precise and coaching conversations become more focused.

Too many deal types. If you design separate processes for enterprise new logos, mid-market new logos, SMB new logos, enterprise renewals, and mid-market renewals, plus expansions, you've created a system that your ops team can't maintain and your reps won't follow. Start with three. Add a fourth type only after the three are running cleanly.

Expansion treated as a surprise. The most common expansion failure is that nobody was watching for the signal. A customer who's grown from 20 seats to 60 seats should have triggered an expansion conversation months ago. Define the usage or trigger thresholds that create an expansion opportunity, and automate the alert if you can.

Renewal as an admin task. "Renewal" shouldn't mean "send them the contract and hope they sign." A renewal without a business review, ROI documentation, and executive contact is an at-risk renewal that just hasn't shown its hand yet.

---

Stage Exit Criteria by Deal Type (Reference Tables)

New Logo: Stage Exit Criteria

Expansion: Stage Exit Criteria

Renewal: Stage Exit Criteria

---

What to Do Next

Don't start by redesigning your CRM. Start by tagging last quarter's deals. The Harvard Business Review's research on sales analytics consistently shows that incremental data improvements produce faster behavioral change than full-system redesigns.

Pull every closed deal from last quarter and manually tag each one: New Logo, Expansion, or Renewal. Then calculate, for each type: win rate, average deal size, and average days to close.

If those numbers are meaningfully different across deal types (which they almost certainly will be), you've made the case for segmented processes. And you now have a baseline to measure against once you've built them.

Start with the deal type where you have the most volume and the most variance in outcomes. That's where a clearer process will have the fastest impact. And once you have the data segmented, run a win/loss analysis per deal type rather than across the blended pipeline. The insights will be meaningfully sharper.

---

Learn More

• Designing pipeline stages that match how customers actually buy
• Qualification frameworks: BANT, MEDDIC, GPCT
• Running a weekly pipeline review that doesn't waste an hour
• Forecasting discipline for CROs