HubSpot (CRM)
Open deals, deal line items and quantities, stage, probability, and expected close date.
Operations
Your planning system forecasts from history. Your sales team is sitting on a pipeline that says next quarter will not look like last quarter. Those two facts never meet, so you buy too much of what sold before and run out of what is about to sell. Coheed feeds weighted pipeline demand into the planning picture and shows the gap while there is still lead time to close it.
Teams bring us this use case when one or more of these is true.
Coheed runs this every six hours, so the projection keeps pace with the pipeline.
Open deals are broken down to product level and weighted by stage and probability, so a pipeline in euros becomes a demand signal in articles and quantities.
Current stock, open purchase orders, planned receipts, and lead times per article give the supply side of the equation.
Weighted demand is set against planned supply over the coming months, producing a projected shortage or surplus per article together with the lead time available to act on it.
Gaps that fall inside the lead-time window and exceed your threshold are raised, so planning acts on the handful of articles where the decision is still open.
Only the fields this use case needs are read. Nothing is copied that the insight does not use.
Open deals, deal line items and quantities, stage, probability, and expected close date.
Stock positions, planned receipts, lead times, and supplier data per article.
Historical order patterns, open purchase and sales orders, article master data.
What a team notices once this runs. No invented percentages: the effect depends on your data and your process.
From insight to action
Available as an agent
Promoted from this insight, the agent prepares the purchase proposal: which articles fall short, in which week, at what quantity, and against which supplier lead time. Purchase orders are proposed for approval, never placed automatically.
Mode: Human-in-the-loop
Every insight can stay read-only, run with human approval, or run autonomously. You decide per action type, and you can change it later.
FAQ
On its own, no. Weighted by stage and probability and calibrated against your historical conversion, it is a useful early signal, and it complements your planning baseline rather than replacing it.
No. If you run a dedicated demand planning tool such as Slim4, Coheed supplies the pipeline-derived demand signal it cannot see, and the plan stays in your planning system.
Three months by default, and the horizon is configurable. What matters is that it covers your longest supplier lead time, because that is the window in which a decision still exists.
Then the signal is coarser, at product-group level. Getting line items onto deals is usually part of the first configuration, and the lead-to-quote use case puts them there as a side effect.
Predictive Customer Lifetime Value
Score churn risk and future value per account by combining CRM engagement decline with ERP order frequency and value trends.
Lead-to-Quote Readiness
Surface correct ERP pricing, live stock, discounts, and customer agreements on every new CRM lead so sales can quote immediately.
Order Exception Monitoring
Catch stock gaps, unrealistic delivery dates, pricing errors, and missed agreements after the order, before the customer notices.
Tell us your ERP, CRM, and SCM stack and we will show what this use case looks like on your systems.