Insights & Use Cases
Explore our use cases and insights to learn how optimization can transform your business
Sales just landed a huge contract. Big volume, a name everyone knows. Operations isn't celebrating. They've seen this before: the volume is high, but the complexity is higher, and complexity is where the money quietly goes.
In process manufacturing, not all volume is equal. A standard product on a standard run is profitable. But a slightly customized formulation, an odd package size, a tight delivery window, each one triggers tank washouts, line changeovers, and overtime that never make it into the margin math. So the number on the contract looks great, and the plant loses money filling it. That's the profitability illusion: revenue that looks like your best account and costs like your worst.
Most plants calculate margin with standard costing: take total plant overhead, divide by total volume, apply the same rate to everyone. It's simple, and it's exactly what hides the problem. Averaging smears the cost of complexity evenly across every product and customer, so the difficult account that eats changeovers and washouts looks just as profitable as the clean, high-volume run that doesn't.
That average is comforting and wrong. It tells you every customer pulls their weight, because by construction, it can't tell you otherwise. The customers who actually cost you, the ones whose orders force the expensive setups, are subsidized on paper by the ones who don't. You can't see it, because the one number you're looking at was built to average it away.
Standard costing spreads the cost of complexity evenly across everyone, so the accounts that actually cause the cost look exactly as profitable as the ones that don't. The average hides the very thing you need to see.
You can't find the true cost of a complex customer by staring harder at a spreadsheet. The only way to measure what they really cost is to build the plan two ways, once with their orders in it, once without, and compare.
That comparison is what WonForge is built to show you. You start one scenario, make your change, and start the other, and they run concurrently, so you're not waiting for the first to finish before you set up the second. Each solve takes minutes to hours depending on how complex your operation is, which sounds like a lot until you remember the alternative: a team of planners spending days rebuilding a spreadsheet by hand, and landing on a worse plan at the end of it. When both scenarios finish, you compare them side by side across the numbers that matter: total cost, capacity used, changeover hours, margin. The difference between them is the customer's real cost to serve, not an allocated guess, a number you can read straight off the comparison.
And the result is often uncomfortable. You might find that dropping $50k of revenue from a difficult account actually raises total profit, because it clears out the changeovers that account was forcing and frees the line for higher-margin work you were turning away.
Comparing the plan with and without a customer turns their true cost to serve from a guess into a number. Sometimes removing revenue raises profit, and the comparison is the only thing that shows it.
Most planning systems answer one question: do we have the capacity to fill this order? That's a feasibility question, and it's the wrong one to sign a contract on. The question that decides whether the deal is good is different: does filling this order actually raise total profit, once the changeovers, washouts, and displaced production are counted?
Scenario comparison lets you answer that before you sign, not after. Run the plan with the prospective order and without it, and you see the real trade: what it adds in revenue against what it costs in disruption and displaced margin. A line that "has room" can still be the wrong place to put that order. You're no longer asking whether you can make it. You're asking whether you should, which is the only question that protects the margin.
"Can we make it" is a feasibility check; "should we make it" is a profit decision. Scenario comparison lets you answer the second one before the contract is signed, not after the plant is losing money on it.
Finding an unprofitable account doesn't mean firing the customer. It means walking into the next conversation with a number instead of a hunch. When you know that a specific product triggers a cleaning cycle that costs $4,000 every run, you have something concrete to work with: a minimum order quantity that makes the run worthwhile, a small price adjustment on the custom grade, a delivery window that lets you batch the work instead of scrambling.
That's a different negotiation than "we think you're expensive." It's specific, it's defensible, and it usually lands as a fix rather than a fight, the customer keeps the product they need, you stop losing money making it. The unprofitable relationship becomes a workable one, because for once both sides are looking at the same real number.
Scenario analysis turns a vague "this account is painful" into a specific cost you can negotiate around, so the conversation ends in a fix, a minimum order, a price tweak, a better window, instead of a standoff.
Some ERPs report customer profitability, but on allocated, standard costs, overhead spread across customers by a fixed rule. Even a good costing module can't capture what a specific account actually forces on the floor: the changeovers its orders trigger, the washouts, the capacity it displaces from higher-margin work. That's not a cost-allocation number. It's the difference between running the plan with that customer and running it without them. An ERP can tell you a customer's average margin; it can't tell you what removing them would do to your profit. That gap is what scenario comparison fills.
Because a difficult account can consume more in changeovers, washouts, and displaced capacity than it contributes in margin. When you drop its orders in a scenario, those costs disappear and the freed capacity goes to higher-margin work you were turning away. If the sum of that outweighs the lost revenue, total profit goes up. It doesn't always, which is exactly why you run the comparison instead of guessing.
No. The point isn't to fire accounts, it's to see their real cost so you can fix the economics. Once you know a product's true cost to serve, you can set a sensible minimum order, adjust the price on the complex grade, or change the delivery terms so the run is efficient. Most unprofitable accounts become profitable with a small change, once both sides can see the actual number.
Volume is vanity; margin is sanity. If you're planning on averages, you're almost certainly losing money on your most complex accounts and calling them your best ones, because the one number you trust was built to hide the difference. Comparing the plan with and without an order turns cost to serve from a guess into something you can read, decide on, and negotiate around, before you sign, not after the plant is bleeding. If you want to see which of your accounts are quietly costing you, Check Your Fit is a short, no-commitment call to find out.
We'll tell you in 20 minutes whether we can solve it.
Email: contact@wonforge.com
Based in Wilmington, DE, serving businesses across the U.S.