A BETTER WAY TO SHARE THE WORK
Create a sales pipeline review around the deals that need attention
Don't just show the pipeline total. Show what moved, why it matters, and which next step needs confirming.
New to creating with an agent? The request will guide it through the task. Bring your notes; you don’t need to write HTML.
How can my agent make a useful sales pipeline review?
Supply a dated CRM snapshot, stage definitions, comparable prior data, and approved deal notes. Ask your agent to separate period movement from closed business, highlight missing next steps, and connect each issue to a confirmed action or ownership question. Verify the figures and keep sensitive customer details within the approved audience before sharing.
01 / SEE THE DIFFERENCE
A smaller quarterly pipeline is not all lost business
Three fictional opportunities illustrate why movement categories and next-step evidence matter.
September 7 snapshot, USD, current-quarter filter. Oak $20,000 moved from September 25 to October 15 and remains open; the buyer has not confirmed the new date. Reed $12,000 remains in the quarter at proposal stage; no next meeting is confirmed. Ash $8,000 is closed won in the CRM; recognized revenue is not supplied. Previous in-quarter open pipeline for these three deals was $40,000; current open pipeline is $12,000. Jo owns checking Oak's timing; Sam owns confirming Reed's next step. No probabilities or forecast recommendation are approved.
- Period movement
- $40,000 previous open pipeline becomes $12,000: Oak's $20,000 moved out of the quarter and Ash's $8,000 became closed won.
- Still open
- Oak remains open; its new October 15 expected date is not buyer-confirmed.
- Needs a next step
- Reed's $12,000 proposal has no confirmed next meeting. Sam owns confirmation.
- Not revenue
- Ash is closed won for $8,000 in the CRM. Recognized revenue is not supplied.
- Owner action
- Jo checks Oak's timing. No close probabilities or forecast recommendation are approved.
Open a complete fictional HTML example, with its source notes →
Create my sales pipeline review02 / MAKE IT YOURSELF
Start with the evidence. Shape the page around the reader.
Fix the scope before adding totals
State which period, currency, team, and opportunities are included. Keep removed, newly created, won, lost, and moved-out opportunities distinct. A deal leaving this quarter's forecast may still exist; it is not necessarily lost business.
Separate pipeline from revenue
Preserve your CRM's stage and forecast definitions. Opportunity value, forecast categories, bookings, and recognized revenue are not interchangeable. Do not invent close probabilities or multiply by guessed weights to create a confident forecast.
Find the next evidence gap
For the material deals, name the confirmed next action and what is missing. Distinguish a seller's plan from a buyer-agreed meeting or commitment. Use the review to focus coaching and verification, not to turn private comments into customer-facing claims.
Make the readout actionable without replacing the CRM
Ask for a short HTML brief with period movement first, then deal-specific evidence and next steps. Verify every amount and status against the dated source. Record new assignments and forecast changes in the CRM; the reading page does not write them back.
03 / TRY THIS PROMPT
Copy this into your agent. Add your source material.
Use the conversation where you already did the work, or start one with your notes. Replace the placeholders and supply any missing context; only attach information you are allowed to share with your agent.
Get the ready-to-copy creation request for guided questions, this task, and a draft review before anything is published.
Create a sales pipeline review from only the authorized dated CRM snapshots, definitions, and deal notes I provide. Ask for missing period filters, currency, stage definitions, comparison snapshot, owners, and next-step evidence. Reconcile period movement without treating moved-out deals as lost. Separate opportunity value, forecast categories, closed-won status, and recognized revenue. Do not invent probabilities, weighted forecasts, buyer commitments, reasons for movement, or dates. Distinguish seller-proposed next steps from buyer-confirmed ones. Keep sensitive customer details and private speculation out of the shared draft. Create static HTML with no scripts, forms, live CRM claims, or writeback. Use my saved artifact style if available. Show the draft and figures to verify. Do not publish or change access without separate explicit approval. Do not change opportunities, assignments, or forecast records.
04 / BEFORE YOU SEND
A polished page still needs your judgment.
- Are period filters, currencies, and comparison snapshots consistent?
- Does movement reconcile without counting moved-out deals as lost or double-counting won value?
- Are pipeline, forecasts, bookings, and revenue clearly distinguished?
- Are next actions and buyer commitments supported rather than inferred?
- Are commercial details appropriate for the approved audience?
When HTML fits
A focused manager readout connecting pipeline movement to deal evidence and coaching actions from the CRM context your agent is authorized to use.
When another format fits better
Keep the CRM as the operational source for deal state, forecasts, assignments, and activity. Use its native view when it already answers the question. This is a dated communication brief, not a forecasting model or revenue-recognition tool.
FROM DRAFT TO A LINK
Make it clear. Make it yours. Then share it.
Keep creating and revising in the agent you already use. With a compatible connection, share/artifacts publishes the reviewed HTML so you do not have to rebuild it in another editor. Ask your agent to use your saved artifact style for headings, color, and tone; review the result before sending it.
Choose who should be able to open the page and verify the returned link. For corrections to the same deliverable, update the existing artifact without changing its link. Publish a separate artifact when the old edition needs to remain available.
These are static pages, not live apps: no scripts, forms, or automatic data refresh. Source collection and scheduling depend on your agent and its available tools, not on share/artifacts.
Make this with my agentQuestions before you start
Should I include every deal?
Include the scope needed to reconcile the totals, then give more space to the deals requiring a decision or action. Keep a larger approved detail view in the CRM rather than hiding the key issues in a huge table.
Can my agent estimate the chance a deal closes?
Do not invent a probability from a stage name or positive comment. Use only an approved model and reviewed inputs if the organization has them; otherwise present the evidence and uncertainty without a made-up score.
Does a closed-won opportunity establish revenue?
Not by itself. Preserve the source's term and use the approved financial record for recognized revenue. The brief should not infer accounting treatment from a sales status.