| name | bd-pipeline-review |
| description | Run the weekly marketing/BD review that turns activity into tracked, advancing opportunities. Pull a funnel snapshot against the KPI spine, enforce pipeline hygiene, focus on priority + at-risk deals, and end with written, owned action items. Guards against vanity metrics and leads falling through the cracks. |
| version | 1.0.0 |
| category | marketing |
| applies-to | ["hermes","claude","codex","gemini"] |
| trigger | weekly |
| auto_execute | false |
| tags | ["marketing","pipeline","review","kpi","metrics","bd","cadence"] |
BD Pipeline Review
The REVIEW stage of the marketing operating system (see ../INDEX.md).
The weekly loop that keeps the whole engine honest and advancing.
Use when
It's the weekly review, or the user asks to "review the pipeline", "check marketing/BD
metrics", "update the dashboard", or "see what's moving / stalled".
Goal
A short, fixed-cadence review that converts activity into advancing opportunities — every
open item has an owner and a next step, and reporting is tied to pipeline outcomes, not likes.
Inputs to gather
- The funnel snapshot for the period (from
linkedin-funnel-ops +
targeted-outreach-sequence).
- The KPI targets from
marketing-campaign-plan and
the shared KPI spine.
- The open-opportunity list with stage + last activity + next step.
Method
- Snapshot the funnel against the KPI spine: awareness → engagement → followers →
conversations → qualified → registrations/RFQs → won. One primary metric per stage.
- Hygiene gate first: flag empty fields, stale stages, and any open item with no next
step or a vague one. Clean before you analyze — a review off dirty data is theatre.
- Focus on the few: the 3–5 priority deals + everything at-risk/stalled, not the whole
list.
- Decide + assign: for each, the next action, owner, and date — written down.
- Report outcomes, not vanity: lead with conversations, qualified leads, registrations,
RFQs, won work; show follower/impression trends only as leading indicators.
- Close the loop: confirm last week's action items were done; carry forward what wasn't.
- Keep it ≤30 minutes on a fixed day.
Output
An updated dashboard/metrics table (emails · replies · followers · conversations ·
registrations · RFQs · won) + a written action list (item · owner · date). Store in the
engagement's BD folder; surface a one-screen momentum view for management.
Definition of done
