A few days ago, a16z and Deel put out one of their joint newsletter chart drops, and the numbers were blunt: by mid-August, roughly a third of employees in Italy and France show up as on vacation, while the US line on the same chart barely moves. My favorite line from the piece: “summer break is still getting mogged by Christmas break,” once you look at the whole year and not just August.

None of this is news to anyone who has actually sold into this market. But it explains something I see constantly: companies expanding into Europe from the US, India, or Asia keep planning their regional bookings target as if every quarter behaves the same everywhere.

The typical ramp looks something like this: Q1: 15%, Q2: 25%, Q3: 20%, Q4: 40% of the annual number. Sensible enough, if you’ve never sold a euro in Europe. If you have, you already know it’s going to be wrong, and not by a little.

A different way to weight the year

What I usually run with instead: Q1: 10%, Q2: 30%, Q3: 15%, Q4: 45%. It looks aggressive on a slide, nearly half the year loaded into the last quarter. In practice, it’s just honest about where the selling days actually are.

This is not a cosmetic exercise. Get the weighting wrong and your cash flow conversation with the CFO goes wrong right along with it. And if you’re the regional team rather than the HQ, this number has to reconcile with whatever cadence is being planned in the US or India, where vacation tends to get booked late and taken in short bursts, which makes a five or six week German or Swedish disappearance even harder to plan around from the other side. Show up with a Q3 at 15% when the global model assumes 25%, and you’d better have the calendar ready, or it just reads as an excuse.

The calendar behind the numbers

None of this is guesswork, since the European calendar barely shifts from one year to the next. Tally up a full year and Germany actually wins the OOO crown outright, which works out well, since it’s also the market I know best:

• Winter break ends around the second week of January (people are skiing, not buying)
• Easter break runs two to three weeks, late March into early April
• Bridge days cluster end of May, early June: a holiday lands on a Thursday, and Friday quietly becomes a day off too
• Summer break runs late June through August, staggered by state
• Fall break sits in October, roughly two weeks
• The last working days of the year end the week before Christmas, and nobody is really back until after New Year’s

Now translate that into deal terms.

Germany effectively shuts down for the Christmas break, and that Christmas-beats-summer line from the top is not just trivia, it’s the reason the December deadline matters most of all. The classic instinct to chase a signature all the way to December 31st is, in most of Europe, a waste of everyone’s time. A decision gets made by the 23rd, or it slides into next year. I’ve written about this before (“Get your P done before year end!”), and the same logic that applies to paperwork in December applies to the whole calendar: if the P in MEDDPICC, the Paper Process, isn’t essentially done before people leave, it isn’t getting done.

May and June create a quieter version of the same problem. Your procurement contact is out the first half, your decision maker is out the second half, and the two windows never overlap long enough to actually finish anything. Summer repeats the trick at scale, especially once decision makers sit across several German states with staggered school holidays.

And Germany is the easy case. The same newsletter shows Sweden and Italy essentially trading the OOO crown across July and August: Sweden checks out hardest in July (Stockholm in July has real zombie-apocalypse energy, minus the zombies), then Italy, with France close behind, takes over in August, which is where that “roughly a third” figure from the opening comes from. The Netherlands and Spain sit somewhere in between. The UK, oddly, stays relatively at its desk through peak summer, so don’t assume “Europe” behaves like one country, even inside Europe itself.

What this means for your forecast, and your sellers

Adjusting the quarterly weighting protects two things at once: your cash flow planning, and your sales team. If a rep can’t get a response in the first three weeks of August, don’t blame the pipeline, and don’t blame the rep. The buyer is simply not at their desk. Holding someone accountable for a close date that was never realistic is a fast way to burn out good sellers over something they never controlled.

This also belongs inside MEDDPICC, specifically in how you map the Decision Process (more on that in “The roadmap of a deal – Decision Process”), and it’s worth pulling out on purpose during pipeline inspection. If the order form isn’t in by November, or the legal agreement isn’t signed, the odds that anything requiring real work moves in December drop close to zero. That’s not a random push-out, it’s a predictable one, and it belongs on the list I laid out in “Pushing deals to next quarter.”

Pro tip: build a simple regional holiday calendar directly into your CRM or your pipeline review deck. One column, showing which weeks a given market is realistically reachable, is enough. It takes an hour to set up and saves a full quarter’s worth of forecasting arguments.

How are you weighting your European quarters this year, or are you still fighting the calendar every August?

Quick facts

• a16z’s analysis of Deel platform data (published in a16z and Deel’s newsletter, summer 2026) found that by mid-August, roughly a third of employees in Italy and France were on vacation, while the equivalent figure for the US barely moved over the same period.
• The same data shows a sequence rather than a single “Europe is out” moment: Sweden’s out-of-office rate peaks in July, then Italy and France take over in August.
• Germany’s summer school holidays are staggered by state (Bundesland), spreading the country’s out-of-office period across roughly late June through August instead of concentrating it in one peak.
• Germany’s working year effectively ends the week before Christmas and does not resume until after New Year’s, a bigger single drop in decision-maker availability than any point in summer.
• A common default quarterly bookings ramp used by companies expanding into Europe from the US, India, or Asia (roughly 15% / 25% / 20% / 40% by quarter) overweights Q3 and underweights Q4 relative to actual European selling capacity.
• A better-fitting weighting for European bookings targets is roughly Q1 10%, Q2 30%, Q3 15%, Q4 45%.
• In the MEDDPICC sales framework, the Decision Process and Paper Process elements are the most exposed to this seasonality: deals without signed paperwork heading into a regional holiday window, especially the pre-Christmas shutdown in Germany, are statistically more likely to slip into the following quarter.

Frequently asked questions

• Why don’t European sales quarters follow the same pattern as the US or India? Decision-makers are unavailable for concentrated, predictable windows: Sweden largely checks out in July, Italy and France in August, and Germany’s states stagger their summer breaks from late June through August. December adds a separate, often larger, drop around the Christmas shutdown.
• What quarterly bookings weighting works better for Europe? Roughly Q1 10%, Q2 30%, Q3 15%, Q4 45% of the annual target, instead of a flatter model that assumes every quarter behaves the same.
• How does European seasonality affect the MEDDPICC framework? Mainly through the Decision Process and Paper Process elements. Deals without signed paperwork in place before a regional holiday window, especially the run-up to the German Christmas shutdown around December 23, are statistically more likely to slip to the next quarter.

Every pipeline review I have ever sat through starts the same way: coverage ratio, deals by stage, total weighted value. These numbers are comfortable because they are easy to calculate. They are also nearly useless as leading indicators.

Multi-threading. If your deal has one contact at the buyer, it is not a deal — it is a conversation.

Decision-timeline specificity. “Q3” is not a timeline. “Before our ERP go-live in September” is a timeline.

Champion credibility. Does this person have a track record of getting budget approved?

The moment you walk through the door as an interim, everyone wants to know what you are going to change. Resist the urge.

The most expensive mistake an interim leader makes is moving too fast. You do not yet know which problems are structural and which are symptoms.

Days 1–30: Diagnose. Your job in the first month is to ask questions and take notes. Talk to every direct report. Sit in on pipeline reviews without running them.

Days 31–60: Stabilize. Pick the two or three things that are actively bleeding and stop the bleeding. Do not reorganize. Stabilize first.

Days 61–90: Transfer. Everything you build from day 30 onwards should be designed to run without you. The handover is not the end of the engagement — it is the point of it.

Welcome to WordPress. This is your first post. Edit or delete it, then start writing!

Key takeaways

• Product type in CRM is a high-level category field on the opportunity record. It works alongside CPQ tools, not instead of them.
• CPQ data is too granular for pipeline reporting. As a result, most teams end up grouping it manually in spreadsheets, which is slow and error-prone.
• Early-stage deals rarely have a quote attached. Without a product type field, those opportunities are invisible to product-level reports.
• Product portfolios change through renames, merges, and discontinuations. Because quoting tools are often controlled outside sales operations, those changes can silently break reports built on CPQ data.
• This is Part 2 of the Magical Fields series. Part 1 covers Opportunity Type, and Part 3 covers Sales Motion.

What product type in CRM actually means

Product type in CRM is a simple dropdown field on the opportunity record. It classifies each deal by its high-level product category. Specifically, it is not a quoting field. Instead, it sits one level above the CPQ layer and answers a different question: what area of the portfolio does this deal belong to?

For example, a software company might use categories like Productivity, Infrastructure, and Security, rather than listing individual products. The field is quick to fill in and requires no quoting step. Consequently, it covers every opportunity from the moment the rep creates it.

The problem with relying on CPQ data for product reporting

CPQ tools do one thing well: they capture exactly what a customer will buy at the line-item level. That detail is essential for pricing and invoicing. However, it creates a pipeline reporting problem.

When you build a product view from quoting data, you work with dozens or hundreds of individual SKUs. Grouping them into something meaningful requires custom joins or higher-tier CRM licenses that unlock cross-object reporting. Many CRM platforms restrict that capability to their most expensive tiers. As a result, smaller teams export data to Excel and group it manually, which is slow, error-prone, and hard to automate.

There is also a second problem that quoting data cannot solve at all: early-stage opportunities. At the top of the funnel, most deals do not yet have a quote attached. The sales rep knows roughly what product area the customer is interested in, but formal quoting has not started yet. Without a product type field, those opportunities simply drop out of product-level reporting entirely.

How a product type field in CRM solves both problems

A product type dropdown on the opportunity record solves both issues at once. Reps select the category when they create the opportunity. Because the field lives on the opportunity record itself, every deal appears in product reports from day one, whether or not a quote exists.

Reporting then becomes a query on a single field rather than a join across multiple tables. For example, if you want to know how many open deals sit in the Infrastructure category this quarter, you filter by one field and you are done. You do not need cross-object reporting licenses or manual exports.

A practical example

Consider a company with eight products across three categories: Productivity (four tools), Server Products (two platforms), and Operating System (two editions). Each category has its own go-to-market motion, its own sales cycle length, and its own targets. Without a product type field, a pipeline report by category requires querying the quoting tool and grouping by product name. With the field, one filter does the work.

Each of those three categories also behaves differently in the pipeline. Productivity deals may close faster because buyers know the products well. Server Products often involve longer technical validation. Consequently, grouping them together in reporting produces averages that describe none of them accurately.

What this means for reporting consistency over time

Product portfolios change. Companies rename, merge, discontinue, or split products into new SKUs. In most companies, the quoting tool is under the control of finance, product management, or marketing. When those teams make changes, the product names in the quoting data shift. Reports built on CPQ line items then break silently, or start grouping deals differently without anyone noticing.

Product type on the opportunity record stays stable because sales operations controls it. When the portfolio changes, the team updates the field’s allowed values. Historical data remains intact, because the category on each old opportunity reflects what that deal was about at the time. Therefore, multi-year trend reports stay accurate even through significant portfolio changes.

Pro tip: Keep the product type list short. Four to six categories is usually enough. The more granular the list, the more it starts duplicating what the quoting tool already does. The goal is a high-level view that reporting can use quickly, not a second SKU catalog.

Two scenarios where product type in CRM earns its keep

Scenario 1: The early-stage pipeline

A rep creates ten new opportunities in January. None of them have a quote yet. In the CPQ tool, all ten are blank. However, the rep knows that six are Productivity deals and four are Infrastructure deals. With a product type field, those ten opportunities appear correctly in the January pipeline report by category. Without it, those deals stay invisible to product reporting until the rep adds a quote, which may take weeks.

Scenario 2: The product portfolio change

The product team renames a key platform from “Enterprise Suite” to “Business Suite” in the quoting tool. All new quotes use the new name. Historical quotes still show the old name. As a result, any report grouping by product name now splits what was one product into two entries. Because sales ops controls the product type field’s categories, a product name change in the quoting tool does not touch it. Reporting continues without interruption.

Quick facts

• Product type in CRM is a category-level field on the opportunity record. It sits above the CPQ layer and covers every deal, even those where the rep has not yet attached a quote.
• CPQ tools track individual SKUs and line items. Because pipeline reporting typically needs category-level data, CPQ alone requires additional grouping steps and often higher CRM license tiers to support cross-object queries.
• Many CRM platforms restrict cross-object reporting to higher license tiers. A product type field on the opportunity record eliminates this dependency by placing the data where it is easiest to query.
• Early-stage opportunities frequently have no products in the quoting tool. A product type field ensures these deals appear correctly in product-level reports from the moment a rep creates the opportunity.
• Quoting tools are commonly controlled by finance, product, or marketing teams. When those teams rename or restructure products, reports built on CPQ line items break. A product type field managed by sales operations stays consistent through portfolio changes.
• This is Part 2 of the Magical Fields series. Part 1 covers Opportunity Type, and Part 3 covers Sales Motion.

Frequently asked questions

• What is a product type field in CRM and how does it differ from CPQ?
  Product type in CRM is a high-level category dropdown on the opportunity record. CPQ tools track individual products and pricing at the line-item level. The two serve different purposes: CPQ handles what a customer will buy and at what price, while product type tells the pipeline which area of the portfolio a deal belongs to.
• Why cannot I just use CPQ quoting data for product reporting?
  CPQ data works at the SKU level, which is too granular for pipeline reporting. Grouping it into categories requires custom joins or higher-tier CRM licenses. It also misses early-stage deals where no quote exists yet. A product type field avoids both problems because it sits on the opportunity record itself.
• How many categories should a product type field contain?
  Four to six is usually sufficient. The goal is a high-level view for fast reporting, not a replica of the product catalog. If you need more than six, the categories are probably too granular and start duplicating what CPQ already tracks.
• What happens to product type data when the portfolio changes?
  Because sales operations controls the product type field, they manage any updates to the category list. Historical opportunities keep their original category, so trend reports remain accurate. In contrast, reports built on CPQ product names break whenever the quoting tool changes a product name or structure.
• Does product type in CRM matter if we only sell one product?
  Not yet. However, most companies that start with one product eventually expand. Adding the field early costs almost nothing. Retrofitting it across hundreds of historical opportunities costs significantly more time and produces less accurate data.

The case for adding product type in CRM from day one

Product type in CRM is not a complex field. It is a short dropdown with four to six values. However, it delivers something quoting tools cannot: stable, consistent, category-level reporting from the first day of a deal’s life to the last.

Set it up before you create the first opportunity. Keep the category list short and stable. Ensure sales operations owns it, not the product or finance team. Do those three things, and this field will serve your reporting needs reliably for years, through product renames, portfolio changes, and CRM license upgrades.

Part 3 of this series covers Sales Motion, the third field that rounds out this reporting foundation. If you want help structuring the field setup for your specific CRM, get in touch.

Key takeaways

• Opportunity type in CRM classifies every deal as New, Upsell, Renewal, or Services. Together, these four categories cover the vast majority of B2B revenue.
• Most early-stage CRM setups skip it because the pipeline is small enough to manage without it. That decision creates a costly data problem later.
• Mixing renewals with new business inflates apparent sales cycles. As a result, it becomes impossible to measure how quickly the team generates net new revenue.
• In fundraising and PE due diligence, investors ask for ARR split by type. Without this field, you have to rebuild that analysis from billing records.
• Make it mandatory from the first opportunity record. Retroactively adding it is never as accurate as setting it correctly at the time.

What opportunity type in CRM actually means

Opportunity type in CRM is a classification field that defines what kind of revenue a deal represents. Specifically, it answers one question that deal stage and close date cannot: what type of revenue does this deal represent? In fact, each category carries a different sales cycle, a different resource need, and a different meaning for your growth story.

Without this distinction, a pipeline report is a count of deals, not an analysis of the business.

The four opportunity types that cover most B2B pipelines

The categories below apply to almost every B2B software or services business. The labels can vary, but the logic should not.

New

New covers any product sold to an account for the first time: a first subscription, a software module, a service contract. This is the category most sales teams track instinctively, and often the only one they track.

Upsell

Upsell covers any expansion of an existing relationship: adding users, upgrading a license tier, introducing a second product. Upsells typically close faster than new business because the trust and legal groundwork already exist. However, they require a different sales motion: more internal than external.

Renewal

Renewal applies when an existing customer renews a subscription for another term. Teams create renewals in the CRM at the time of the original sale, setting the contract end date as the expected close. As a result, renewals can sit in the pipeline for 12 months or longer. That timeframe is long enough to distort every cycle metric in the system if you leave them unseparated.

Services

Services covers consulting, implementation, training, or any service engagement. Services deals often run in parallel with product deals. Consequently, conflating them with software revenue makes both harder to analyze.

Why teams skip this CRM field, and why that logic breaks down

Early in a company’s life, the pipeline is almost entirely new customers. There are no renewals yet and upsells are rare. Total volume is low enough that a spreadsheet handles segmentation just fine. So the field waits.

The problem is timing: good data becomes critical at precisely the moment when fixing bad data is hardest. A fundraise, a PE review, or a new sales leader understanding ramp times: all require clean, segmented pipeline history. If the team never set opportunity type, that history does not exist. Instead, the team faces a reclassification project: going through every record manually, inferring type from deal name, company, and notes.

That project takes days. It is also rarely accurate. Moreover, it is entirely avoidable.

What this means for sales analysis and forecasting

Once opportunity type in CRM is consistently populated, the analytical questions you can answer change significantly. Sales cycle by deal type becomes a real metric. For example, you can measure how long it takes to close a new logo versus an upsell or a renewal. That distinction matters for quota design, territory planning, and headcount decisions. For instance, a rep focused on renewals operates on a fundamentally different timeline than one building a greenfield territory. Holding both to the same activity metrics produces poor decisions for both.

For investors and private equity, this field is often the difference between a credible ARR narrative and a vague one. Growth equity and PE buyers routinely ask for ARR broken into new, expansion, and renewal. However, without a properly set opportunity type, the CRM cannot produce that split directly. Rebuilding it from billing records or contract data takes time the selling process rarely allows.

Pro tip: The best time to add opportunity type to your CRM is before you create the first opportunity record. The second best time is now. Make it a required field, not a recommended one. Sales reps skip optional fields under pressure, which is exactly when data quality degrades fastest.

The renewal rule that most teams learn the hard way

Keep renewals completely separate from new business. This is not a preference. It is a data integrity requirement.

Teams create renewals in the CRM at the time of the original sale, setting the contract end date as the expected close. In B2B, contract terms of 12 months or more are standard. A renewal sits in the pipeline for 365 days. New business opportunities average 60 to 90 days. Combining the two pulls the apparent average sales cycle in a direction that reflects neither type accurately.

The effect compounds over time. As the customer base grows, renewal volume grows too. Without segmentation, renewals eventually dominate the pipeline by count, even when new business dominates by strategic importance. By that point, the sales cycle metric is so distorted it cannot inform any meaningful decision.

Separating renewals from new business does not require a complex CRM configuration. It requires setting opportunity type correctly from the start.

Quick facts

• The four opportunity types that cover most B2B revenue are New, Upsell, Renewal, and Services. Most CRM setups that skip this field merge all four into a single undifferentiated pipeline view.
• Teams create renewal opportunities at the time of the original sale, because the expected close date matches the contract end. In B2B, that typically means these deals sit in the pipeline for 12 months or more. Including them in new business pipeline data inflates average sales cycles for the entire team.
• Growth equity investors and PE firms routinely ask for ARR split by new, expansion, and renewal. This is a standard due diligence request. Without a consistent opportunity type field, you have to rebuild that analysis from billing or contract records.
• Making a field mandatory in most CRM systems is a single configuration change. However, skipping it at the start triggers a reclassification project later. That project typically takes days and produces less accurate results than setting opportunity type correctly at deal creation.
• This is Part 1 of the Magical Fields series, which covers three CRM fields that carry disproportionate analytical weight: Opportunity Type, Product Type, and Sales Motion.

Frequently asked questions

• What is opportunity type in CRM and why does it matter?
  Opportunity type in CRM is a field that classifies each deal as New, Upsell, Renewal, or Services. It matters because each type carries a different sales cycle and different resource needs. Without it, pipeline reports measure activity but cannot diagnose performance.
• Why does mixing renewals with new business distort sales cycle data?
  Teams set renewals to close on the contract end date, often 12 months after the original sale. When you count renewals alongside new business deals that average 60 to 90 days, they pull the average sales cycle upward. That average then reflects neither type accurately, so it cannot support quota setting, ramp planning, or headcount decisions.
• When should you add opportunity type to your CRM?
  Before you create the first opportunity record, and make it mandatory, not optional. Sales reps skip optional fields under pressure. Adding it late means a manual reclassification project. That project grows with pipeline volume and rarely produces fully accurate results.
• Does opportunity type matter for early-stage startups with a small pipeline?
  Yes, precisely because the pipeline is small. Adding and enforcing the field takes minutes when there are ten opportunities. It takes days when there are a thousand. The payoff only becomes visible later, at exactly the point when fixing the data is hardest.
• Which CRM fields should you set up alongside opportunity type?
  Product Type and Sales Motion. Together, these three fields give you the analytical foundation to understand how each part of the business performs. They cover different customer segments, products, and selling approaches. Part 2 and Part 3 of this series cover each in turn.

The case for setting up opportunity type in CRM from the start

Opportunity type in CRM is not a complex field to implement. The configuration takes minutes. The discipline is making it mandatory and enforcing it from the first opportunity record.

The payoff is a CRM that answers the questions that matter. How long does it take to close a new customer? How quickly does the first upsell follow? Is the renewal base growing or eroding? These are the questions that drive planning decisions and satisfy investor scrutiny.

The alternative is a system that counts deals but cannot explain them. Consequently, the reclassification project ends up in the backlog indefinitely.

Setting up or auditing a CRM and want a second opinion on the field structure? Get in touch. Part 2 of this series covers Product Type. That field becomes critical the moment your product portfolio grows beyond a single offering.