How to summarize a selected sales pipeline view
A pipeline summary explains the opportunities visible in a chosen view and the questions they raise. It helps prepare a review when people need more context than a list of deal names.
Start with the right material.
- What you provide
- a loaded CRM pipeline table with visible totals or rows.
- The intended result
- Summarize only displayed deals by stage and flag incomplete coverage.
How the workflow works.
Organize the selected deals by the supplied stage definitions and keep value, currency and expected dates explicit. Highlight missing next steps or stated blockers without inventing a probability of closing.
What to check in the result.
Reconcile counts and totals with the selected view. A pipeline value is not booked revenue, and a partial view should not be described as the company's entire forecast.
Preview the Markdown to check headings, lists and links as well as the words. Keep source references with the document so a reviewer can trace important statements back to the material you supplied.
Learn from the worked example.
The downloadable Markdown example shows one possible organization of the result. Read it alongside the source example and notice which statements are recorded facts, proposed wording or questions still needing an answer.
The supplied example is illustrative. It is not a recorded run on your data.
Download the example ↓Use it with your own material.
- Open the source you want to work with and activate WebAct on that tab.
- Copy the task from the hero, add any required fields or preferences, and review the proposed actions.
- Compare the first result with your source. Ask for a specific correction or refinement where needed.