Move a deal through your pipeline

Pipeline is where you track deals from first contact to close. This article shows the three ways to move a deal to the next stage and what to do when a move is blocked.

Before you start

• Your workspace has at least one deal in any stage.
• You have permission to move deals in your workspace. Creating deals requires Admin or Owner permissions, and Members may not always have this permission. If an action below is hidden or disabled, contact an Admin.

The five stages

Every deal sits in one of five stages:

• Qualification: you are figuring out whether the company is a fit.
• Proposal: you have sent a proposal or quote.
• Negotiation: you and the buyer are aligning on price and terms.
• Won: the deal closed. Blake stamps the close date automatically.
• Lost: the deal closed without a sale. Blake asks for a loss reason and stamps the close date automatically.

Move a single deal

1. Open Pipeline from the sidebar. The view opens on the kanban board by default.
2. Grab a deal card and drag it into the next column.
3. Blake asks for any required fields on the target stage. Fill them in and confirm.

If you prefer the keyboard, click a card and use the arrow keys to move it left or right.

Ask Blake to move it

You can also move a deal from Ask Blake:

• Open a deal detail page.
• Open Ask Blake with Cmd + B.
• Ask "Move this deal to Negotiation and update the close date to end of quarter."

Blake proposes the change as an approval card. Click Approve and Blake updates the stage, timestamps the transition, and logs it in the deal activity.

Move deals in bulk

1. Switch to the List view using the toggle in the top right.
2. Select multiple deals with the row checkboxes.
3. Use the bulk-action bar at the bottom to change stage for all selected deals at once.

Mark as Won or Lost

Moving a deal to Won or Lost is a close event.

• Won: Blake stamps the close date and moves the deal into your workspace history. The card leaves the kanban board and lands on the Won section of your Deals list.
• Lost: Blake asks for a loss reason from the eleven standard categories (Price too high, Wrong timing, No decision, Chose competitor, and so on). The reason feeds Overview widgets so you can see loss patterns over time.

Both moves are reversible from the deal detail page if you close by mistake.

If a stage change is blocked

• A required field is missing: Blake shows which field needs a value for the target stage. Fill it in on the card and try the move again.
• You cannot drop the card: your role likely does not have edit rights on the pipeline. Contact an Admin to change your role.
• Drag feels laggy on a large pipeline: switch to List view for bulk moves. Kanban drag is optimised for a few dozen cards, not hundreds.
• The stage move requires a team: some workspaces enforce "Team required on every deal." Fill the Team field before the move.