Time to pipeline: how long each B2B channel takes to create deals
Time to pipeline is the number of days between an account's first tracked touch and the day a sales opportunity is created for it. Measured by channel, it tells you how long to wait before you judge a channel, which channels fill this quarter's pipeline, and which ones are building next quarter's. Without it, slow channels look broken and fast channels get more credit than they earned.
This explainer covers what the metric measures, how to calculate it from data you already have, and how it should change the way you read attribution reports.
What does time to pipeline measure?
It measures lag. Every B2B deal has a gap between the moment a company first meets you and the moment sales opens an opportunity. Time to pipeline puts a number on that gap and lets you compare it across channels.
The start point is the account's first tracked touch: an ad view or click, an organic visit, a webinar registration, an event scan, or a referral. The end point is the opportunity created date in your CRM. Everything in between, such as return visits, content, pricing page views, and a demo request, is the path that attribution explains.
Channels differ because buyers arrive in different states. Someone who searches for your category already has a problem and a budget in mind. Someone who hears you on a podcast may not need you for months. Both can be good channels. They just pay back on different clocks.
Why does it matter for attribution?
Most attribution reports look at a fixed period, like last month or last quarter. That works for channels with a short lag. It misleads you for channels with a long one.
Say you launched a podcast sponsorship in September. In October's report, it shows almost no pipeline, because the accounts it reached have not reached sales yet. Cut it then and you will never see the deals it started. Our guide to podcast attribution for B2B walks through why awareness channels in particular look weak early.
The same lag skews cost metrics. If you divide this month's spend by this month's new pipeline, every long-lag channel looks expensive and every short-lag channel looks cheap. Our explainer on reading CAC by channel when deals take months shows how to match spend to the deals it actually started.
How do you calculate time to pipeline by channel?
You need two dates per account and one rule for which touch counts as first. Most teams can build it from web tracking plus their CRM, such as HubSpot or Salesforce.
- For every account with an opportunity, find the earliest tracked touch from anyone at that company.
- Find the opportunity created date for that account.
- Count the days between the two.
- Group the accounts by the channel of that first touch.
- Report the median days for each channel, along with how many accounts sit behind it.
Use the median, not the average. One account that sat quiet for a year and then came back will drag an average far out, while the median shows what a typical deal looks like. Show the account count next to it, so nobody reads too much into a channel with a handful of deals.
Work at the account level, not the contact level. In B2B the person who first found you is often not the person who books the demo. If you only track contacts, the first touch disappears when a colleague fills out the form, and the lag looks shorter than it really is.
How is it different from sales cycle length?
Sales cycle length starts when an opportunity is created and ends when the deal closes. Time to pipeline covers the stretch before that, which is the part marketing influences most. Put together, they describe the full journey from first touch to revenue.
Pipeline velocity is a third, related number. It combines how many opportunities you have, their average value, and your win rate, divided by sales cycle length, to estimate revenue per day. It is useful for sales forecasting, but it says nothing about how long marketing channels take to create those opportunities in the first place. Time to pipeline fills that gap.
How should it change your reporting?
Once you know the lag by channel, three habits change.
- Judge channels on their own clock. If a channel typically takes a quarter to produce opportunities, do not call it a failure after a month. Read early signals, like target accounts visiting and coming back, until its pipeline is due.
- Set attribution windows to fit. A lookback shorter than a channel's typical lag will drop its touches from the path entirely. Our explainer on attribution windows for long B2B sales cycles covers how to size them.
- Plan budget with the lag in mind. Spend on slow channels this quarter shows up as pipeline next quarter. Leadership should hear that before the numbers dip, not after. Our guide to building next year's budget from attribution data shows how to plan for it.
What skews the number?
Bad first-touch data is the biggest problem. If UTMs are missing or inconsistent, early touches land in Direct and every channel looks faster or slower than it is. A quick pass through common UTM mistakes that break B2B attribution fixes most of this.
CRM habits come next. Opportunities created long after the first sales conversation, or contacts that are not tied to the right account, both distort the end date. Our post on CRM hygiene for B2B attribution lists the fixes that matter most.
Finally, watch for touches you cannot see. A buyer who heard about you from a peer or in an AI answer and then typed your URL will look like they started on Direct. Asking "How did you hear about us?" on the demo form recovers some of that first touch.
How Source helps you read time to pipeline
Source keeps every account's path in one place, from the first visit to the deal in your CRM. It installs with one pixel or Google Tag Manager, with no warehouse to build. Multi-touch, view-through, offline, and LLM attribution from ChatGPT, Claude, Perplexity, and Gemini sit on the same path, so the first touch is not lost when the buyer comes back through another channel.
You can chat with your data to ask how long accounts from a given channel took to reach an opportunity, and see real CAC, goals, and channel quality next to it. AI recommendations and daily Slack reports flag what changed. Source is SOC 2 Type II and ISO 27001 certified, and customer data is not used to train external models.
If you want to see how long your channels really take to create pipeline, start free at dash.source.app/signup.