What is a pipeline generation meeting?
It is a weekly meeting about pipeline that does not exist yet.Everything in a pipeline review is already in the CRM. A pipeline generation meeting deals with the opposite problem: the opportunities that must be created, qualified, and worked in the coming weeks in order for a future quarter to be reachable. The subject is production capacity, not deal strategy.
The distinction matters because most revenue teams are far better at inspecting existing deals than at forecasting the ones that have not been built. That imbalance shows up at the end of a quarter as a coverage number that looked acceptable attached to a revenue number that was not.
Why does creation need its own meeting?
Because existing deals always take the hour.Put both topics on one agenda and the outcome is predictable. Live deals are urgent, they have names, and someone in the room has a commission attached to them. Creation is next quarter's problem right up until it becomes this quarter's shortfall.
| Dimension | Pipeline review | Pipeline generation meeting |
|---|---|---|
| Subject | Opportunities in the CRM today | Opportunities that must be created |
| Core question | How do we advance this deal | Where does the next $X of pipeline come from |
| Time horizon | This quarter | Next 30 to 90 days |
| Owner | Frontline sales manager | Demand generation lead with sales managers |
| Output | Next steps on named deals | Adjusted targets, reallocated effort, campaign decisions |
What number should open the meeting?
Open with the creation target and the gap against it, not with coverage.Coverage describes what already exists. It is a useful input and a poor conclusion. A team can hold 4x coverage and miss badly when the pipeline is concentrated in the wrong segment, owned by the wrong reps, aged, or built on close dates that keep moving. Across ORM's customers, coverage runs from 1.4x to 5x with most companies near 3.5x, and the number by itself does not separate the teams that hit from the teams that do not. That is the practical case for why the 3x pipeline coverage rule fails as a health check.
The number that belongs at the top of this meeting comes from decomposing where revenue actually originates:
- Carry-over deals already in pipeline on day one that are expected to close this quarter. - In-quarter deals that do not exist yet, but will be created, qualified, and closed inside the quarter. - Pull-forward deals from future periods that close early, usually with a discount or a hole in the next quarter.
The middle category is the one this meeting owns, and it is the one almost nobody models. It is also larger than most teams assume. Across ORM's customers, roughly 20 percent of the pipeline carrying in-quarter close dates on the first day of a quarter closes inside that quarter. The other 80 percent of that value is not realized in the period, which means a meaningful share of what you close was created after the quarter started.
What is on the agenda?
Five blocks, 45 minutes, same order every week.- Gap to the creation target for the period, in dollars and in opportunity count. - New pipeline created last week, split by source and segment. - Conversion from meetings held to qualified opportunities, by team. - Where the next 30 days of creation comes from, named by campaign, territory, or account list. - Blockers that need a decision in the room.
The fourth block is the only one that changes outcomes. Reporting last week's creation is bookkeeping. Committing to where the next 30 days comes from is a plan someone can be held to.
What does the scoreboard look like?
One table, published before the meeting, owned by RevOps.| Metric | Definition | Owner |
|---|---|---|
| New opportunities created | Count and value of opportunities created in the period | Demand generation |
| Creation against target | Actual versus planned creation, period to date | RevOps |
| Source mix | Share of created pipeline by channel and by segment | Demand generation |
| Meeting to opportunity rate | Qualified opportunities divided by meetings held | SDR manager |
| Time from creation to first stage change | Days between creation and the first real movement | Sales manager |
| Segment coverage | Coverage by segment rather than in aggregate | RevOps |
Who should be in the room?
People who own a creation number, and nobody else.The core group is the demand generation lead, the SDR manager, the sales managers carrying creation targets, and RevOps to run the data. Individual account executives do not belong in a standing pipeline generation meeting unless they own a self-sourcing target, in which case they attend for the block that covers it.
Keep the group small enough that the meeting can make a decision. Reallocating spend, changing a target account list, or moving SDR capacity between segments are decisions with owners, and a room of 15 people will not make them.
How do you know the meeting is working?
Creation becomes predictable, and the variance between planned and actual creation narrows.Track that variance week over week and by source. A team that consistently plans 100 and produces 60 has a capacity problem worth naming. A team that produces 100 from wildly different sources every week has a repeatability problem, which is harder to see and just as damaging to the forecast.
The second test is downstream. Newly created pipeline should convert at rates comparable with your historical baseline. When creation volume rises while sales velocity falls, the meeting has started manufacturing opportunities rather than finding demand, and the pipeline number is buying you nothing.
Frequently Asked Questions
What is a pipeline generation meeting?
A recurring meeting about pipeline that has not been created yet. It reviews progress against a creation target by source and segment, and decides where the next 30 to 60 days of new opportunities will come from.
Why can't pipeline generation be covered in the pipeline review?
Because deals that already exist always win the hour. A manager with 45 minutes and a quarter to close will spend all of it on deals in play, so creation gets three minutes at the end and no decisions.
Who should attend a pipeline generation meeting?
The demand generation lead, the SDR manager, sales managers who own creation targets, and RevOps. Keep it to people who own a creation number so the meeting stays decision oriented.
What is the right creation target?
Work backward from the revenue you need in future periods rather than from a coverage multiple. Coverage tells you what exists today, while a creation target tells you what has to be built and by when.
How often should a pipeline generation meeting run?
Weekly for teams with sales cycles under six months, biweekly for longer cycles. Creation shortfalls compound quietly, and a monthly cadence finds them a month after they could have been corrected.
See how ORM turns these insights into action
ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.
Schedule a Demo