Deal Pipeline

Keep a simple, living record of Bristol deals and produce clean status updates.

When to use

"Add this to my pipeline," "what's in the pipeline," "update [deal] to underwriting," "give me a pipeline summary for Monday."

Where it lives

A single file: bristol-os/pipeline.md in the workspace. Create it on first use.

Stages (Bristol deal lifecycle)

Sourced → Screening → Underwriting → IC/Approval → Capital Raise → Closing → Development → Lease-up → Stabilized → Disposition/Refi

For each deal track

• Name / location / product & units
• Stage + date entered stage
• Owner (who at Bristol is driving it)
• Next action + due date
• Key open items / blockers
• Link to the deal folder and latest memo

Operations

• Add: append a new deal row/section.
• Update: move stage, log the change with a date, update next action.
• Summary: produce a grouped-by-stage overview, highlight what's stalled (no movement / overdue next action) and what needs a decision.
• Whenever another play produces a deliverable for a deal, note it on that deal's pipeline entry.

Output

• Updated pipeline.md, plus a readable summary when asked (e.g., a Monday update grouped by stage with a "needs your attention" section at top).

Live tracker artifact (build it for them — HARD LAW)

Bristol OS gives each person a live visual deal board they can reopen any time.

1. The first time pipeline is used (and during onboarding), build it for them: read bristol-os/templates/project-tracker.html and create a persistent artifact from it with the create_artifact tool (title it "Bristol Deal Tracker"). Don't tell them how — just make it and open it.
2. Tell them where it is and how to use it in one plain sentence: "I made you a live Deal Tracker — it's pinned in this conversation; click any card to update a deal, and it saves itself on your computer."
3. Keep it in sync: when a deal changes, update both pipeline.md and (when asked for the board) regenerate/refresh the artifact. The board saves deals in the browser, so it persists across sessions.
4. Never make the user build or find it themselves — you create it and point to it.

Guardrails

• Keep it factual — reflect only what the user tells you or what's in the deal folders.
• This is internal tracking; keep it in the workspace, never anywhere public.