Sales template

Pipeline Risk Monday

Files an at-risk-deals brief every Monday from your pipeline export.

A self-running pipeline doctor that shows up every Monday morning before the forecast call. Feed it the week's open-opportunity export (deal, stage, amount, close date, days-in-stage, last activity) and it returns the deals most likely to slip, why each is at risk, and the one move that saves it. A weekly forecast review that runs itself. Example input: "Deals: 1) Acme $90k, Negotiation, closes 7/15, 28 days in stage, last activity 11 days ago. 2) Globex $40k, Proposal, closes 7/30, 4 days in stage, last activity 2 days ago." Example output: "At risk: Acme $90k, 28 days stuck in Negotiation and 11 days dark; classic stall. Move: rep requests a redline call by Wed or the deal slips to next quarter. Healthy: Globex (fresh, active). Forecast note: $90k of committed pipeline is soft this week."

The flow this template ships
ScheduleLLM (Claude)Output
Coreruns weekly on Mon at 08:00 UTC$0.12 / call3 steps wiredSales

Who pays: Sales managers and RevOps: a pre-forecast-call brief flagging slipping deals every Monday.

How it runs
Runs weekly on Mon at 08:00 UTC

A schedule step drives this agent on its own cron, so it runs weekly on Mon at 08:00 UTC without anyone pressing a button. When preview is available, those runs are free and have no side effects.

$0.12 per brief, suggested

The template opens with this intended price loaded. Launch publishes the service and its current call state. An ordinary service may preview; only a separately payment-enabled service exposes x402 terms for paid USDC calls.

Built on core nodes

The wired flow uses built-in nodes only. Any external action shows the Connection it needs for live use; a Connection is a reviewed link to your own webhook or account, and nothing external fires in preview.

Related templates
Start building

Open Pipeline Risk Monday in the studio

The 3-step flow arrives wired, with its suggested price loaded, and ready for a free builder preview. Make it yours, then launch with its public call state reported.

Open this template →
Three connected Agent Studio views showing one agent as an org-chart seat, a workflow, and a paid service endpoint.
Seat, flow, serviceThe same agent as a seat, a flow, and a service.