Skip to main content

How to Build a Pipeline Your Whole Team Can Use

How to structure your LRM pipeline with stages, tags, and color-coding so your team — and leadership — always knows where every deal stands.

Written by Mikaila McLane

Pipeline stages — your deal funnel

Stages are the backbone of your pipeline. Every project lives in exactly one stage at a time, and moving a project through stages tells the story of a deal's progression. Prophetic comes with a set of default stages you can load as a starting point, and org admins can add, rename, reorder, or remove stages to match your division's actual workflow.

A typical residential land acquisition pipeline might look like:

  • New — just identified, no underwriting done yet

  • Research — ZoneAI, SiteAI, and Full Analysis complete

  • Pursue — decision made to move forward, outreach initiated

  • Under Contract — LOI or PSA executed

  • Due Diligence — formal diligence period active

  • Closed — site acquired

  • Dead — disqualified or lost

The exact stages don't matter as much as consistency. When everyone on the team uses the same stage definitions, leadership can look at the pipeline and immediately understand where every deal stands without asking anyone.

Tags — the cross-cutting layer

Tags let you label projects with attributes that cut across stages. Where stages answer "where is this deal in the funnel?", tags answer "what kind of deal is this?" Useful tag examples:

  • Market name or submarket (Austin North, DFW Suburban, Tampa East)

  • Product type (SFD, Townhome, MF, Commercial)

  • Deal size (Small, Mid, Large)

  • Priority flag (Hot, Watch, Low)

  • Owner status (Contacted, Responded, Not Yet Reached)

You can filter your pipeline by tag at any time — useful for pulling up everything in a specific market, or everything flagged as hot, or everything where the owner hasn't been contacted yet.

Color-coding parcels

There are two ways color works on the map in Prophetic:

Stage color dots (automatic): When the Projects layer is enabled on the map and dots are selected under Annotations, each project appears as a dot color-coded by its current pipeline stage. As you move a project from one stage to the next, the dot color updates automatically. This gives anyone looking at the map an instant visual picture of where every deal stands — no clicking required.

Annotation colors (manual): Within a project, you can also manually assign annotation colors to individual parcels. Use this to visually distinguish parcels within an assemblage, separate active from disqualified sites, or apply custom color-coding beyond what the stage colors provide. The Copy Annotation Style feature lets you apply one parcel's color and style to multiple others at once — useful when you're color-coding a large batch of results from a SearchAI run.

Task automation — your pipeline on autopilot

Org admins can configure task templates for each pipeline stage. When a project moves into a stage that has templates assigned, Prophetic automatically generates the task checklist for that stage — assignee, due date, requirement level, and all. Blocking tasks prevent the project from advancing until they're checked off.

This means your team doesn't have to remember what needs to happen at each stage — the pipeline tells them. And leadership can see task completion status across all active deals without having to ask.

Visibility triggers

Projects can be set to become visible to the broader team when they reach a certain stage. This lets individual users work early-stage leads privately until they're ready to share, while ensuring that anything moving into active pursuit is visible to the full division.

The result

A well-structured pipeline is a live picture of your division's land acquisition activity. Every deal in the right stage, tagged correctly, with tasks assigned and completion tracked. Leadership opens the pipeline and sees what's being worked, what's moving, and what's stalled — without a single status meeting.

Did this answer your question?