From sale to project: one deal's next step
The deal page shows where a customer stands across the quote, documents, payment, service, tasks and project, what happens next and who does it.
Steps
- Open a deal. Beside its history, "From sale to project" lists seven steps: sale, quote, documents, payment, service, tasks and project. Each one says done, in progress, waiting, needs attention, not started, not needed or not available, and who owns it.
- "Next action" names one step and its owner. Late tasks and urgent tickets come first; then whatever blocks the deal, such as a draft quote to send, an expired quote or an accepted quote on a deal that is still open; then the next task your team planned.
- When the deal is won, it points to what is still missing: issuing the accounting document again if it failed, a payment link for an accepted quote with no payment yet, and the project that takes over the work.
- It only suggests. Every step is done where it already lives: the quote on the deal, the payment link in Money, the project in Projects. Each of those makes its record once, so a second click does not create a second quote document, charge or project.
- "Already exists" lists what it held back and why, for example a payment that is already recorded or a project already opened from this deal.
Questions
- Does it show internal notes or ticket messages?
- No. It reads statuses, dates, numbers and owners only. Notes, quote notes, decline reasons, ticket messages and payment amounts are not part of it, and it is visible only to people who can open the deal.
- Can an AI assistant act on it?
- Through MCP an assistant can read the same answer (crm_deal_continuity). It is read only: creating a quote, a payment link or a project stays a separate step that a person approves.
- What if a project exists that I cannot see?
- The step says a project exists and that you do not have access, and it does not suggest opening another one.
Updated 2026-10-25 · llms-full.txt