Sales & pipeline

Keep your pipeline up to date

Review the evidence behind each opportunity and decide which record changes are justified.

Copies a prompt for your AI assistant

View prompt

Start wherever you are

Bring an opportunity, recent activity, or a review process. Your agent helps you choose what should actually change.

Start with your AI assistant. Connect tools when needed.

Fictional example

You

Maya replied positively after discovery. Should I move Northline to Proposal?

Agent

What does your team require before an opportunity enters Proposal?

You

An agreed scope and a request for a proposal. Neither is agreed yet.

One possible change review after checking the fictional record fields, activity, and stage criteria together

Proposed update · stage stays Discovery

Record progress without overstating it.

The reply is useful context. It does not yet meet this team’s criteria for moving Northline into Proposal.

Stage: Keep Discovery. An agreed scope and a proposal request are both still missing.
Proposed Next step value: Clarify the scope with Maya and ask whether a proposal would be useful.
Review note: Positive reply after discovery; scope and proposal request remain unconfirmed. This note is drafted for review, not recorded activity.

Checked in this fictional example

The example record is at Discovery and has a free-text Next step field. The team requires agreed scope and a proposal request before Proposal.

What the reply does not prove

A positive response does not establish the missing criteria, a purchase commitment, or a changed close date.

A next step to review

Review the proposed Next step text against the source. Apply only the selected change if the actual workspace supports it and you authorize it.

Context & open questions

Example allowed stage values: New, Discovery, Proposal, Won, Lost. A real review uses the actual workspace schema and allowed values.
Keep other fields unchanged: No evidence supports changing value, close date, probability, or ownership in this example.
Status: Review prepared. No CRM field, activity, stage, or task has been changed.

Your result will reflect your conversation. Keep it in your assistant or a document you choose.

How the tools fit together

01
Selected opportunities
A defined review scope in the chosen workspace.
02
Schema & evidence
Actual fields, allowed values, and authorized sources.
03
Proposed changes
Current value, new value, and reason for each.
04
Verified updates · if authorized
Write selected changes and report their individual results.

Choose tools together. Execution depends on the connections and actions available in your assistant.

Read the full guide

Start wherever you are

Start with one opportunity or a defined review scope. Bring your team’s stage criteria if available.

Figure it out together

Choose what to review
Agree the opportunities, evidence sources, and decision you want to make.
Check fields and evidence
Inspect the actual workspace schema and compare recent information with the team’s criteria.
Review selected changes
Show the current and proposed values with reasons, then carry out only authorized supported updates.
Verify the result
Report which changes succeeded, failed, or remain proposals.

Tools and connections

Your AI assistant: Coach the review and explain the evidence for each proposed change.
Capable · optional: Inspect available opportunity fields, allowed values, and records; update only through supported operations.
Activity source · optional: Review specific notes, messages, or other evidence you choose.

What you’ll keep

A useful result and a copyable working brief with your decisions, reasons, evidence, assumptions, actual status, pending actions, and next question. Bring it back when you’re ready to continue.

A useful first outcome

You have a clear change list grounded in evidence, with actual update status and unresolved gaps.

When to revisit it

When new evidence meets stage criteria, planned actions change, or a scheduled review is agreed.

View the setup prompt

Copy into your AI assistant to begin

Help me keep my sales pipeline accurate through a guided review. Help me decide which opportunity updates are justified by evidence, using the actual workspace fields and our team's definitions rather than assuming activity means progress.

Check the context I have supplied first. If I have not described a scope or concern, ask: "Which opportunity or part of the pipeline feels out of date?" If that is already clear, acknowledge it and ask the next useful unanswered question. Reuse an existing review process or working brief, check relevant changes, and begin with the issue I named. We can discuss a record or plan without connecting tools first.

Ask one useful question at a time. Agree the opportunities and evidence sources in scope. Before a connected review, inspect the actual supported records, field types, required fields, and allowed values. Do not invent stage names, probabilities, health scores, ownership fields, activity types, or storage locations. Ask for the team's stage criteria where they matter; if there are none, help draft provisional definitions without applying them as established policy.

Compare current record values with the evidence I supply or authorize you to read. Keep source references and distinguish verified facts, interpretations, stale information, missing information, and conflicting evidence. A reply, meeting, sent proposal, or other activity does not by itself justify advancing a stage. Check whether the agreed exit and entry criteria are met. Do not infer a close date, value, buying intent, loss reason, or probability from weak signals or silence.

Give me a useful review early: what appears accurate, what may need changing, and what needs a question rather than a write. For each proposed update, show the exact record and field, current value when available, proposed value using the supported format, evidence, and reason. Keep unchanged fields out of the write set. If there is a conflict or a newer value, pause that change and resolve it instead of overwriting it silently.

Help me choose the smallest meaningful set of updates. An opportunity can stay in the same stage while its next step changes. Keep draft review notes distinct from recorded activity and completed work. Do not create tasks, alter owners, mark opportunities won or lost, delete records, or update the whole pipeline merely because we are reviewing it. Apply only the specific supported changes within the scope I authorized, after resolving consequential choices or missing authorization. Do not require repeated approval for the same exact action already authorized.

Verify each attempted update from the available tool result and, where appropriate, the resulting record. Report successful writes, failures, conflicts, and remaining proposals separately. Do not claim the pipeline is up to date if only some records were reviewed or writes failed. Keep a record of the evidence and the remaining questions so the next review can build on this one.

Keep a reusable working brief as we decide things. Include our goal and scope; the decisions and why we made them; the exact current output; sources and evidence; assumptions and open questions; the actual status of any actions; pending work; and the next useful coaching question. Add owners, dates, and a review point only where we agreed them. Distinguish a proposed action from an authorized action, an attempted action, and a verified result. Give me an early provisional result when the context supports it, then improve it with my feedback rather than waiting for every detail.

Before using connected tools, ask which sources I want to use unless I have already specified them. Work only within that scope. Use Capable for available context and supported records or operations; check the actual tools, fields, permissions, and capabilities instead of assuming an integration can read, write, send, schedule, or store anything. Use existing authorization for the exact action it covers. Resolve missing authorization or consequential choices before acting, without making me repeat settled decisions. Report what actually happened and any partial failures; do not imply that a draft, copied prompt, or configured rule ran successfully.

Keep the brief in this conversation unless I choose another place. Save it only if I ask and an appropriate operation is available. Do not imply that Capable or a new chat will automatically remember it. Include this continuation instruction with the brief: check what has changed, reuse the decisions that still apply, and ask the next useful question. The brief supplies context, not permission to contact people or change records. Before we pause, give me a clean, copyable version so I can continue in my chosen assistant or document.

How did it go? Optional feedback

Keep your pipeline up to date

Start wherever you are

Record progress without overstating it.

Checked in this fictional example

What the reply does not prove

A next step to review

Example working brief

Selected opportunities

Schema & evidence

Proposed changes

Verified updates · if authorized

Start wherever you are

Figure it out together

Tools and connections

What you’ll keep

A useful first outcome

When to revisit it