Pipeline Hygiene.

A side-panel in the CRM with the rep's real Friday list.

Pipeline Hygiene is an Embed co-worker that runs every Monday at 06:00 and refreshes mid-week as data changes. It lives as a side panel in the CRM (Salesforce in most installs — HubSpot supported via the same connector model). Reps see, for their own pipeline: the opps that have skipped a stage gate, the ones where the forecast confidence doesn't match recent activity, the missing-but-required fields, and the silent ones (no logged activity in 14+ days).

Managers see the same data, aggregated, with patterns: which stage gates are getting skipped, which fields are perpetually empty, which reps have the most stale opps. One panel per role, same underlying analysis.

What connects.

Targeted write (one exception to the read-only default)

The co-worker can update CRM fields via a rep-driven "apply" button. Example: it suggests setting "Next Step" to "Send pricing" because the most recent activity was a discovery call. Rep clicks Apply → the field updates, audit log captures the rep, the suggestion, and the change. Without the click, nothing writes.

Five lists in the rep's side panel.

1. Stage gate violations. Opps that have skipped a required stage event (e.g., no discovery call logged but stage is Proposal). Reordered by close date.
2. Forecast-activity mismatch. Opps marked "Commit" with no rep activity in 14+ days, OR "Pipeline" with weekly cadence that looks like a Commit. Forecast lies in both directions.
3. Required fields missing. Champion blank on stage-3+ opps. Renewal contact missing on existing-customer expansions. Etc.
4. Silent opps. No logged activity in 14+ days, ranked by $ amount.
5. One-step suggestions. "Set Next Step to 'send pricing'" or "Add note: champion attended demo on 5/14." Single-click Apply.

The hygiene fix loop.

For most items, the rep's job is one of three actions:

• Fix in CRM — the co-worker's panel shows "missing field"; the rep fills it.
• Apply suggestion — one-click write where the co-worker proposes a value. Apply commits, audit logs.
• Dismiss with reason — "champion blank because contract is signed; not relevant here." Logged. The co-worker learns to skip that opp from this check.

Manager view is observational, not interventional, by design. The pattern view tells the manager which sales motions are leaking discipline — not which reps to message. The conversation that follows happens in their existing 1:1, not via an automated DM.

What we measure.

• Forecast accuracy — quarterly variance against final closed-won. Target: tighten by 30% within two quarters.
• Time-to-update — from the moment a stage gate is skipped to the moment the rep fixes it. Baseline 2–3 weeks; target < 2 days.
• Field completeness — % of stage-3+ opps with champion, decision criteria, and economic buyer populated. Target > 85%.
• "Surprise" close-lost rate — opps that closed-lost from Commit. Pre-rollout baseline; target halve it.

The most underrated metric is the last one. Surprise close-losts are usually the result of forecast-activity gaps that no one caught. Pipeline Hygiene is built around catching them on Monday, not in week 13.

Things we considered and cut.

• No auto-DMing reps when their pipeline degrades. We considered it; reps hated the demo within two minutes. The CRM panel is the right surface, not Slack.
• No "predicted close date" overrides. We don't auto-change rep-entered dates. Suggesting yes, overriding no.
• No leaderboards. The aggregation is for patterns, not rankings. We've never seen a hygiene leaderboard improve hygiene over a one-month window; just resentment.
• No outbound autonomous email. The co-worker can suggest "send pricing" but doesn't draft the email. Most reps have a voice they'd rather not have automated.