Example prompt
Copy this into Claude once it is connected to Klipy:What happens
1
Claude resolves your pipeline
Claude calls
list_pipelines to get your pipelines and their stages — the structure a weighted forecast is built on.2
It reads the deals
Claude calls
list_crm_records for the deal type in each pipeline, reading each deal’s value, confidence, stage, and projectedCloseDate, and uses stage to tell open deals from closed ones.3
It builds the projection
Claude weights the deals by stage and confidence and reasons out best, likely, and worst scenarios from the real numbers — then reports them back to you. This is read-only; nothing is written to your CRM.
Good to know
- Forecast quality depends on populated deals.
value,confidence, andprojectedCloseDateare real fields on every deal — but they are optional. If your deals do not carry a value or a confidence, the forecast has less to weight, and the result is only as good as what you have filled in. Keeping those fields current is what makes the projection trustworthy. - Deals are scoped to a pipeline. Listing deals requires a pipeline id, so Claude works pipeline by pipeline. If you run several, ask it to cover all of them or name the one you mean.
- The scenarios are Claude’s reasoning, not a stored model. Klipy exposes the deal data; the best/likely/worst split is Claude weighting it. Two runs can phrase the split differently — treat it as a grounded estimate, not a fixed system number.
Related
Cold deal outreach
Act on the stalled deals the forecast surfaces.
Ask your data
Ask follow-up questions about specific deals in the pipeline.
Tool reference
Every tool Claude can call, grouped by scope.