What is a CRE deal pipeline?

The anatomy of a CRE deal pipeline

Every functioning pipeline has the same skeleton: a fixed set of stages, a rule that each deal sits in exactly one stage, and a defined trigger that moves a deal forward. The stage names vary from shop to shop. The structure barely does.

Two structural notes. Financing is a column on the board at some shops and a parallel track at others, because lender outreach starts during due diligence rather than after it. And most teams add a Dead or Passed stage so declined deals keep their history, which is what makes a post-mortem on lost deals possible later.

The rule that holds the whole thing together is single-stage membership. The moment a deal can plausibly be described as "sort of in underwriting, sort of at LOI," the pipeline has stopped being a source of truth and gone back to being a decoration.

Pipeline vs deal flow

The two terms get used interchangeably, and they describe different things. Deal flow is the incoming stream of opportunities, measured in volume and quality: how many deals the team sees each month and how many fit its criteria. The pipeline is the stage structure those deals enter once the team engages. Deal flow management covers sourcing, screening, and tracking as one process; the pipeline is the backbone of the tracking part.

The distinction matters because the failure modes are different. A team with strong deal flow and a weak pipeline sees plenty of opportunities and still misses deadlines, because nobody can say what stage a given deal is in without checking three places. A team with a tight pipeline and weak deal flow runs a clean process on too few deals. Diagnose them separately, because the fixes have nothing in common.

Kanban board or list: how pipelines are structured

Teams structure the same pipeline data two ways. A kanban board renders stages as columns and deals as cards, so stage distribution is visible at a glance: six cards stacked in underwriting and one lonely card in closing tells you something before you read a single number. Boards are the default view for the Monday pipeline meeting because dragging a card to the next column is a public, unambiguous act.

A list or table view renders the same deals as rows, which wins when you need to sort and filter: every deal over $20M, every deal assigned to one analyst, every deal with a key date inside 30 days. Purpose-built pipeline management tools give you both views over one dataset, typically with filters for asset class, deal size, and assignee, so the board and the report never disagree.

The structure that fails is the one where the board and the tracker are separate artifacts. A whiteboard plus a spreadsheet is two pipelines, and two pipelines means a reconciliation job that someone quietly stops doing by week six.

The metrics a pipeline produces

Once every deal has a stage and a timestamp, the pipeline starts generating management data. Three metrics do most of the work: days in stage (how long each deal has sat where it sits), stage conversion (what fraction of deals advance from each stage to the next), and pipeline value by stage (what is actually at stake in each column).

Stage conversion is the one most teams never compute, so here is a worked example. Take a mid-size acquisitions team's trailing twelve months:

Overall screen-to-close is 2.2 percent, which is normal. The diagnostic value is in the middle rows. A 42 percent LOI-to-contract rate is healthy; if it were 15 percent, the team is bidding on the wrong deals or bidding late. Now compare a second team that also closed 4 deals but underwrote 60 to get there: its 33 percent screen-to-underwrite ratio means roughly 24 extra full underwrites a year, and at 20 hours each that is about 480 analyst hours spent on deals a tighter screen would have killed on day one.

The market backdrop makes this arithmetic less academic. U.S. CRE investment volume reached $117 billion in Q1 2026, up 19 percent year over year, per CBRE, and full-year 2025 volume hit $560.2 billion across 176,445 properties, up 14.4 percent, per Altus Group. More transactions means more deals entering pipelines with the same headcount, and conversion math is how you find out whether the extra load is being screened or just absorbed.

Acquisitions pipelines vs development pipelines

An acquisitions pipeline measures its stages in weeks: a screening decision in days, underwriting in one to three weeks, due diligence in 30 to 60 days. A development pipeline measures its stages in quarters and years. Ground-up deals pass through site control, entitlement, design and pre-construction, financing, vertical construction, and lease-up or disposition, and a single entitlement stage in a difficult jurisdiction can outlast three full acquisitions cycles.

That changes what the pipeline is for. Development pipelines lean on milestone dates more than stage conversion, because the question is rarely "will this deal advance" and usually "is this project on schedule," and a slipped permit date cascades into every date behind it. Many developers run both: an acquisitions-style pipeline for pursuits and a development pipeline for projects that have closed on land. The mistake is forcing both into one set of stages, which leaves half the columns meaningless for half the deals.

How teams keep a pipeline of record

The pipeline is a discipline before it is a tool, but the tool decides whether the discipline survives. Spreadsheets hold up to roughly 10 active deals, after which stale rows and version drift hand the real pipeline back to whoever has the most context in their head. At the institutional end, platforms like Dealpath, which reports more than 300 firms and over $10 trillion in transactions on its platform, made the pipeline-of-record model standard for large investment managers.

Small and mid-size teams get the same structure from purpose-built deal management software. In MotionCRE, the pipeline is a kanban board with custom stages per pipeline, days-in-stage visible on every card, and filters by asset class, deal size, and assignee, and each card opens into a deal workspace holding that deal's files, tasks, contacts, and key dates. The point of the category is that moving a card and updating the record are the same action, so the board stays true without anyone maintaining it.

Whatever the tool, the test of a real pipeline is the same: can anyone on the team answer "what stage is this deal in, who owns the next step, and how long has it been there" in under ten seconds, without asking a person. If yes, you have a pipeline. If no, you have a list of deals.