Pipeline hygiene report
Stage-aging, missing next steps, stale close dates – flagged with the deal context, not as a blind warning list.
By team · Sales
Pipeline hygiene and follow-ups, under approval.
A co-worker for the work that keeps the pipeline clean and the customers warm.
§01 · Weekly work
The recurring work between the real selling.
The pipeline maintenance and customer touches that AEs already do – drafted by a co-worker, sent only after the AE approves.
Customer follow-up drafts
Personalised next-touch drafts informed by the last call, the last email, and the deal's current state – queued for AE approval.
Deal review prep
The 1:1 prep doc your manager already asks for – risk, ICP fit, next step, what would unblock – drafted before the meeting.
Forecast call prep
Weighted view, commit confidence, slip risk, and the one-line "why" on each deal – pulled from CRM plus call notes.
§02 · Co-worker
A co-worker that reads CRM, calls, and email – drafts, waits for approval.
Connects to the sales stack you already use. Drafts. Asks. Nothing goes to a customer until the AE says yes.
RIY-SLS-01
Connected
Salesforce / HubSpot
Gong / Chorus
Email
Slack
Sales co-worker
read·draft·approve
Follow-up drafts queued
Risk-flagged deal list
Forecast packet
§03 · Engines
The agent engines doing the work.
For sales: the analytical engine for context, the watchful engine to flag slipping deals, and the goal-based engine to carry a follow-up through to approval.
Data Analysis Agent
Reads CRM, call summaries, and email history. Synthesises the "where is this deal really" view – with citations.
Analytical · Cited
Anomaly Detection Agent
Watches for slipping deals, sentiment shifts on calls, and stage-aging outliers. Flags the deal before it goes cold.
Watchful · Proactive
Goal-Based Agent
Carries a follow-up goal across steps – drafts, queues for approval, logs the send, updates the CRM stage.
Persistent · Step-aware
§04 · Sample workflow
5 idle deals, warmed the same morning.
A real engagement pattern – what the team asked for, what the co-worker did, what got approved, and what saved the AE 6.5 hours that week.
What was asked
"Help me warm the deals that are slipping – without sending generic email."
An AE running 38 deals knew which 5 had gone idle but couldn't get to a personalised re-engage each week. Generic sequences felt off-brand; writing each from scratch ate Friday afternoon.
What the co-worker did
Read the 5 idle deals. Drafted 5 follow-ups, each tied to the last real touch.
The co-worker pulled the deal record, the last Gong call summary, the last email thread, and the latest product or pricing update the customer might care about. It drafted five personalised follow-ups – each tied to a specific thread or moment.
What got approved
The AE reviewed all five, edited two, hit approve.
The AE opened the queue at 9am, tightened the tone on two, removed one reference the co-worker had over-read, approved all five. Nothing left the approval gate until the AE said yes.
What shipped
All five went out same morning. 6.5h saved that week.
An implementation-led engagement that took four weeks to map and ship – including the CRM permission scope review. The AE got Friday back. Two of the five deals re-engaged within a week.
§05 · Get started
Bring the one weekly thing your sales team repeats.
We'll map it with you, identify the minimum context, and ship a working version in 2—4 weeks – your CRM, your tools, AE approval before anything reaches a customer.