Pipeline
Pipelines with stages, win percentages and stuck-deal days; a board with a card menu, and a list with filters, saved views, bulk edit and CSV.
Your sales pipeline, one board
Track every sale from first contact to won or lost on a pipeline board, with next steps, reminders and a forecast.
Pipelines with stages, win percentages and days before a deal counts as stuck. A board with drag and drop and a menu on every card, and a list with filters, saved views, bulk edit and CSV. A deal page has details, products, activities, sharing, history and won, lost or reopen; a deal without a next step is flagged. My day shows what to do today; reminders run every 15 minutes, each sent once. The forecast and reports work by month, owner and financial year, with time in stage and lost reasons. The leads inbox takes enquiries, once each, through the API. Contacts can supply the person and Quotations can start a draft quote and show its state, both through service bindings and keys pasted per domain; nothing is sent. API /api/v1/deals, pipelines and a change feed with an API key or the workspace key; webhooks deal.created, deal.stage_changed, deal.won and deal.lost. Optional Claude features summarise a deal and suggest a next step or follow-up text, which is only drafted. Not built: connections to Customers and Enquiries, sending of follow-ups, drag and drop with a finger on the board (the card menu works).
What Deals does for you.
Pipelines with stages, win percentages and stuck-deal days; a board with a card menu, and a list with filters, saved views, bulk edit and CSV.
Details, products, activities, sharing, history and won, lost or reopen; a flag for deals without a next step; a My day page and reminders.
Forecast and reports by month, owner and financial year, time in stage and lost reasons; a leads inbox filled through the API.
A suggested path for Deals. What you can do depends on your access in the app.
Create a pipeline and its stages.
Add them by hand or through the leads inbox.
Follow next steps to won or lost.
Live host, inventory, governance, health checks, verification, dependencies and history.
Pipelines with stages, win percentages and days before a deal counts as stuck. A board with drag and drop and a menu on every card, and a list with filters, saved views, bulk edit and CSV. A deal page has details, products, activities, sharing, history and won, lost or reopen; a deal without a next step is flagged. My day shows what to do today; reminders run every 15 minutes, each sent once. The forecast and reports work by month, owner and financial year, with time in stage and lost reasons. The leads inbox takes enquiries, once each, through the API. Contacts can supply the person and Quotations can start a draft quote and show its state, both through service bindings and keys pasted per domain; nothing is sent. API /api/v1/deals, pipelines and a change feed with an API key or the workspace key; webhooks deal.created, deal.stage_changed, deal.won and deal.lost. Optional Claude features summarise a deal and suggest a next step or follow-up text, which is only drafted. Not built: connections to Customers and Enquiries, sending of follow-ups, drag and drop with a finger on the board (the card menu works).
People and companies belong to Contacts; quotes to Quotations; paid orders to Payments and Store; website enquiries to Enquiries.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
deals.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.