The system does the checking an estimator does on a good day, every day: purchased-item usage risk is flagged automatically when the quoted MOQ sits below a purchased-item quantity break, and the correct quantity break is selected automatically from the quoted volume.
Alerts fire automatically on approaching deadlines, delays, and incomplete tasks.
Open an item. Its Command Center answers the questions that otherwise take a week of archaeology:
From the same screen: update pricing and generate a customer-facing quote in seconds. Run a what-if in seconds — what if material cost increases, what if cycle time improves 20% — and compare the scenario to current state with one click.
A purchasing manager updates a material cost in master data.
Automatically, for every item consuming that material.
Against each item's governed price.
Any item crossing its allowable gross-margin drift threshold alerts the people who own the decision — in real time.
No email. No meeting. No “remembering to update team”.
Pricing Lab runs two kinds of session. Both follow the same process at any scale — thousands of items, hundreds of customers, minutes.
Reactive — a cost has already moved. Standard rates increased, a purchased-item price changed, underperforming items need a general update. A BPU session reprices the affected book and commits: every item activates through the same governed pipeline as an individual re-price, with its own revision, reason code, and quote line.
Forecast — model a change that hasn't happened. Rumor of a major purchased-item increase? Set the hypothetical new values across every impacted item, analyze the margin impact, adjust, and generate budgetary quotes — before the letter from the supplier arrives. A BWI session commits nothing and touches no governed record.
Open a session. Scope the items: the whole book, by customer, by purchased item, by machine, or by tool.
The affected items resolve automatically; review and confirm the set.
Apply a pricing methodology across the entire selection at once — maintain GM%, hold a GM% band, uniform price increase, or cost pass-through.
Impact across the lot, or per customer, before anything is decided.
Locked pricing is engine-priced, item by item. If costs move again between lock and activation, the item holds for review instead of activating on stale numbers.
Customer-facing quote documents generate automatically, grouped by customer — prices and terms only.
A bulk session is not a different kind of pricing. It is the individual re-price, industrialized: every item in a committed session carries a complete governed record of its own — indistinguishable from one updated by hand.
Every completed action in an item's Command Center or a Pricing Lab session writes to the Quote Log on its own. Create a draft: a line opens, In Process. Activate the pricing: the same line closes, Completed. Issue a budgetary quote from a what-if: logged, marked as forecast. Revise, supersede, cancel — every status is the direct consequence of a governed action.
No status is ever set by hand. Nobody maintains a quote tracker, nobody updates a spreadsheet after the fact, and nobody wonders whether the log is current — it cannot be anything else.
Lighthouse combines multiple forecasting models over historical and active item data, using a proprietary methodology. Nobody builds the forecast; the record does.
Revenue and margin, twelve months forward, grounded in governed pricing.
Machine loading from the same items and cycle data production runs on.
Material and component demand, by item, ahead of the buy.
Each month, the forecast regenerates on its own: prior-month actuals roll in, and every change to an active item — a price activation, a volume update, a cost movement — carries forward automatically. The forecast is never a project. It is never stale. It maintains itself.
Every report follows the same three steps — and every report reads the same governed record, so the numbers agree with each other, and with the quotes, the forecast, and the customer-facing documents.
One record underneath means one set of numbers. The margin report, the quote log, the forecast, and the customer quote can never disagree — they are all reading the same truth. Command CGP™ also connects to the AI platforms your team already uses, for analysis on top of governed data.
Every cost in Command CGP™ is built from master data. Which means every master record is a margin input — and each one is governed like it.
Presses and work centers — tonnage, type, environment, and the machine-class rates every cycle second is costed against.
Tools and their architecture — type, cavitation, melt delivery — the physical truth behind every quoted cycle.
Resins, additives, colorants, components, packaging — with quantity breaks, so the price the cost engine uses is the price you actually pay at volume.
Fixed overhead, variable overhead, direct labor, skilled labor — the rate structure beneath every item in the book.
Every record carries where-used links. Open a purchased item and see every item that consumes it; open a machine and see everything that runs on it. Finding information stops being a task.
Change a value here and Chapter 4 takes over: live costs recalculate, drift recalculates, and anything crossing its threshold raises an alert. Master data is where governance starts — the record ends where margin is defended.
Command CGP™ is the single source of truth for the commercial activity and decisions that directly impact bottom-line margin.
Start a Conversation