01
Deals, stages and ownership on one board
See open commercial work by stage, move a deal as the decision changes and keep the client, value, close timing and owner attached to the same record.
- What is implemented
- The application ships a pipeline board and deal detail routes backed by the sales-pipeline schema and API module.
- Availability boundary
- The sales_pipeline capability must be enabled; the live plan may limit active pipelines and open opportunities, not closed history.
02
Next actions that prevent silent deals
Keep the upcoming action and its due context visible on the deal, and create a follow-up task when the person has permission to turn intent into assigned work.
- What is implemented
- The pipeline surface implements next-action prompts, overdue signals and task creation tied to commercial records.
- Availability boundary
- Deal and task actions remain permission-gated; viewing the pipeline does not grant the right to create work for others.
03
An optional forecast built on live deals
Review open, weighted and won views by month, owner and pipeline when management needs a directional reading of the commercial record.
- What is implemented
- A dedicated forecast route reads pipeline data and exposes the implemented open, weighted and won views.
- Availability boundary
- sales_forecast is a separate capability and depends on sales_pipeline; a plan cannot enable the forecast without its underlying funnel.
04
Reusable services and prices for consistent scoping
Keep repeatable offerings in a service catalog so the person building a proposal can start from maintained commercial material instead of recreating every line.
- What is implemented
- Service list and detail routes support maintained service records and feed proposal composition.
- Availability boundary
- Services are plan-gated and the plan may limit catalog entries; creation and editing also require service permissions.
05
Rich proposals with a client decision
Compose scope and line items, preserve the client and commercial context, and give the client a focused surface for reviewing and accepting the proposal.
- What is implemented
- Proposal creation, detail and client-portal proposal routes are implemented, including the client acceptance workflow.
- Availability boundary
- Proposal management requires the proposals capability and record permissions; portal access is separately governed for client users.