Go back to Market Research
Factible Tools is cloud software for supply chain network design and tactical planning. Supply Chain Designer models facilities, sourcing, and product flows; Tactical Planner evaluates production, capacity, inventory, and sourcing across planning periods. Users load business data, establish a baseline, and compare alternative scenarios. The two products share an interface and data model. (1, 2, 3, 14)
Overall supply chain score: 4.0/10.
| Dimension | Score |
|---|---|
| Supply chain depth | 4.0/10 |
| Decision and optimization substance | 3.6/10 |
| Product and architecture integrity | 4.0/10 |
| Technical transparency | 3.8/10 |
| Vendor seriousness | 4.4/10 |
Factible Tools addresses meaningful economic decisions with a deliberately focused application. Its central limitation is the treatment of an uncertain future as a set of separately specified scenarios. Public documentation explains how to change assumptions and obtain an optimized plan; it does not establish a policy that jointly prices demand, supply, and timing uncertainty. A better solution to one assumed future can remain a poor commitment in the real operation. (2, 4, 5)
The self-service workflow has concrete support: planners change models themselves, and a 2026 release exposes specific new constraints. The unanswered questions concern the quality of the economic model, the continuing effort to maintain it, and the difference between modeled improvements and realized returns. (6, 7, 8)
Factible Tools versus Lokad
Factible Tools packages strategic and tactical scenario analysis for planners. Lokad’s supply chain optimization centers on recurring purchasing, production, allocation, and replenishment decisions, with uncertain futures and economic trade-offs represented explicitly. The distinction concerns the work the software performs and the assumptions it carries into a decision.
A network study can identify a cheaper sourcing arrangement for a chosen demand forecast. The operational decision also depends on how that arrangement behaves when demand changes, deliveries arrive late, products substitute for one another, or several constraints bind simultaneously. Lokad’s perspective, presented in Introduction to Supply Chain, makes those interactions part of the economic problem.
Factible’s attraction is a focused interface and a relatively direct path from a spreadsheet to a scenario comparison. Lokad’s programmatic approach makes the decision logic more explicit but requires technical modeling and continuing maintenance. For either approach, the difficult question is whether the model captures the business mechanisms that change the best action. Mathematical optimality within an inadequate representation does not resolve that question; this is the distinction developed in Holimization.
Product scope and delivered constraints
Tactical Planner targets a one-to-eighteen-month horizon and supports monthly or quarterly S&OP work. Its published process loads data through Excel, establishes a baseline, runs alternative plans, and brings comparisons to a meeting. ERP integration is optional rather than a prerequisite. The output is a planning decision for people to evaluate, with no documented continuous production loop issuing operational transactions. (3)
The January 2026 release adds a rule requiring each customer to use a single supplying plant or distribution center, and a minimum total shipment volume for any used plant or center. Both are exposed as scenario parameters. The volume threshold applies to the facility’s total activity. (6)
Those controls can represent genuine business restrictions. They also show why parameter maintenance is substantive work. A single-source rule may simplify operations while preventing a cheaper or more resilient split. A minimum volume can stand in for fixed costs, but the appropriate threshold changes with margins, transport prices, and alternatives. The model should make the economic consequences of such rules visible rather than treating every inherited policy as an unquestionable constraint.
The sourcing page separately lists supplier prices, minimum quantities, capacities, and contractual obligations. The production page includes line capacity, changeovers, forecasts, and inventory policies. These are relevant inputs; the public material does not expose their formulation, interactions, or supported scale. (4, 5)
Scenario optimization and uncertainty
Factible’s production description promises a mathematically optimal plan given supplied forecasts and policies. That qualification defines the practical weakness. Supply chains must commit resources before the future is known, and the cost of an error is rarely symmetric. A plan built around a central forecast can overcommit to a fragile supplier or understate the value of flexible capacity. (4)
Changing an input and rerunning a scenario is useful sensitivity analysis. It does not supply the probabilities, dependencies, and consequences needed to choose one action before uncertainty resolves. Nor does a menu of independently optimal scenarios identify a feasible policy for adapting over time. The public product evidence does not establish that connection.
Demand is only one source of risk. Supplier delays, production yield, breakdowns, and transport variability can change both feasible actions and their costs. A sourcing plan needs a projection of those uncertain quantities and times, including shared failure causes. A supplier with a low quoted cost can be expensive once the resulting shortages, emergency freight, or protective inventory are included.
The underlying optimizer is not publicly identified. That prevents inspection of its formulation and limits, but the central problem is already visible in the workflow: specified inputs produce separate optimized plans. Naming a solver or supplying a faster benchmark would not establish that the chosen representation makes economically sound decisions under uncertainty.
Factible also offers ProdFlow, a FlexSim-based production simulation tool. Its broader FlexSim service explicitly addresses variable processing times, equipment failures, demand peaks, and statistical distribution fitting. Those are separate capabilities in the wider offering. Public documentation does not describe a unified feedback mechanism through which their uncertainty estimates change the network optimizer’s decisions. (18, 19)
Customer results: a model result needs an operating account
The May 2025 Colombian dairy case centers on an expiring milk-supply contract. Factible built a 2024 baseline, relaxed constraints, and compared alternatives. It attributes a 3.75% profit improvement to different raw-milk flows and another 2.43% to adding a distribution center in Valledupar, presenting the combined result as more than 6% higher operating profit. The article supplies no implementation dates, realized accounting period, or reconciliation of projected and actual costs. (7)
The business mechanism is plausible: an expiring contract can make previously unavailable sourcing options feasible. The reported percentage nevertheless needs a denominator, a realized baseline, and the cost of operating the new arrangement. A facility can require little initial capital while still adding rent, labor, handling, inventory, and coordination costs. The case establishes a quantified modeling exercise more clearly than a measured financial outcome.
An April 2025 tariff case is narrower and more concrete. During a proof-of-concept presentation, two customer planners changed the modeled costs of Colombian and Mexican supply into the United States, reran the model, and compared results. It demonstrates responsiveness and user control. It does not measure subsequent savings or establish a strategy robust to further tariff changes. (8)
Factible’s profitability module recognizes production, logistics, inventory carrying, and service costs at product and customer level. That is a better starting point than optimizing a forecast score. The remaining issue is whether those costs capture the consequences of decisions, including nonlinear costs and uncertainty, rather than merely allocating historical expenditure. (22)
Maintenance cost and the productivity test
Factible’s strongest methodological writing concerns maintenance. Its December 2024 implementation guide asks for automated data preparation, integrity checks, scenario management, and flexibility when omitted requirements emerge. It also identifies poor solutions and overly time-consuming systems as causes of failure. These are useful engineering priorities. (9)
The current Excel-first workflow lowers the initial integration barrier. It also creates a choice about recurring work: maintain reliable automated feeds or repeatedly prepare and reconcile spreadsheets. A quick first scenario does not measure the cost of keeping facility capacities, tariffs, product transformations, cost tables, and contractual rules current.
The vendor’s September 2025 essay reports approximately 1,500 database fields and argues against adding detail merely to appear comprehensive. Field count is a weak measure of either analytical depth or simplicity. The material test is how many business concepts customers must maintain, how changes are checked, and which omissions could reverse the preferred decision. (10)
This concern has a long history in the team. Jerry Bendiner’s 2016 account of Chemtrade describes a bespoke Opti-Net application linked to SAP, evolving through new constraints, reporting, and changes to the model, data, interface, and analytics. The durability he describes depended on continuing adaptation. The current product needs an equally clear account of who performs that work when a customer’s needs exceed the configurable model. (17)
In an agentic software environment, productivity includes maintaining and improving the decision system. Faster scenario manipulation helps, but the larger test is whether data checks, model revisions, regression comparisons, and deployment can be performed with less total customer and vendor effort. Factible exposes neither a public programmable model interface nor an independently inspectable release-and-test workflow for customer logic.
Its March 2025 essay on slow planning projects says that failure is often not the tool’s fault. That explanation needs to be tested against the vendor’s own earlier diagnosis: a model that misses a business rule can produce poor recommendations, and the application has to adapt. Customers should be able to distinguish data defects, model omissions, poor software ergonomics, and bad decisions through recorded evidence. Blaming adoption or scope alone would leave the supplier’s contribution unevaluated. (13, 17)
Technology history and AI follow-through
| Period | Evidence | Significance |
|---|---|---|
| 1990s–2016 | Technologix’s custom-modeling history includes the long-lived Chemtrade application described by Bendiner. (16, 17) | This supports modeling experience and maintenance continuity; it is historical bespoke software. |
| 2024 | Published guidance emphasizes model scope, data preparation, and implementation failures. A separate trends article promotes AI, machine learning, digital twins, IoT, and automation broadly. (9, 12) | The implementation guidance is more specific than the technology-trends claims. |
| 2025 | Case articles show dairy-network and tariff scenarios; the product argues for a smaller, accessible modeling surface. (7, 8, 10) | There is a consistent focus on scenario preparation and analyst usability. |
| October 2025 | AI Copilot is introduced for natural-language analysis and recommendations; the article describes next-generation models learning to rerun and refine scenarios. (11) | The future automation claim lacks a published evaluation or technical mechanism. |
| January 2026 | Release 26.1 adds two specific model constraints and updates their configuration and documentation. (6) | Concrete model maintenance is visible, with much narrower claims than the AI roadmap. |
The 2024 trends article discusses digital twins as a way to anticipate outcomes, without specifying how their predictive accuracy would be evaluated. It is general advocacy, not evidence that Factible Tools shipped every technology mentioned. Its weakness is the implication that more simulation and visibility automatically reduce decision risk. A model’s usefulness depends on the accuracy of the consequences it predicts for competing actions.
The AI Copilot announcement similarly emphasizes assistance to judgment. It does not publish the language model, grounding process, data boundaries, or tests connecting recommendations to feasible and profitable plans. The proposed automatic rerunning of scenarios would matter if it reliably discovered economically relevant alternatives and maintained constraints. Generating persuasive commentary on existing results is a much smaller capability. (11)
The present company page explicitly distinguishes team experience across decades from the current cloud platform and identifies modeling, data-integration, and infrastructure roles. Customer names from that history should be read in that scope. They are not a count of current SaaS deployments. (15)
Bill of software materials and security
| Layer | Publicly established evidence | Material limit |
|---|---|---|
| Current application interface | The public Factible Tools login and its delivered JavaScript contain Phoenix LiveView components. (20) | This identifies the web interface technology, not the optimization engine or database. |
| Data interchange | The product uses structured Excel input; automated integration is optional. (3) | Data refresh, validation, and reconciliation still need an operating owner. |
| Optimization engine | The product describes mathematical optimization. | Solver identity, formulation, compute limits, and dependency lifecycle are undisclosed. |
| Companion production simulation | ProdFlow is built on FlexSim. (18) | Its licensing and model maintenance form a separate dependency from the SaaS network application. |
| Historical custom applications | Chemtrade’s older implementation used Opti-Net and SAP integration. (17) | Current SaaS architecture is not specified by that historical implementation. |
The visible materials do not support a detailed hosting-cost estimate. Public employment and product information did not establish the production database, cloud provider, or model-serving stack. The useful disclosure would identify the components actually required to run the service, their maintenance responsibilities, and how customer-specific models survive upgrades.
Security documentation is thinner still. The published privacy policy concerns website visitors, contact forms, support, emails, and cookies. It does not explain protection of uploaded supply chain models, tenant separation, privileged support access, backups, retention, or AI-provider processing. Those models can contain commercially sensitive costs, contracts, and capacity plans. Their custody requires a production security account. (21)
The public login shows an application with authentication; it does not establish the controls governing an authenticated customer’s data. AI-assisted analysis adds another boundary: what model content leaves the application, which provider receives it, and which generated changes require independent validation. The current Copilot description leaves those questions unanswered.
Supply chain score
The overall result is the mean of 25 equally weighted criteria: 3.96/10, displayed as 4.0/10.
Supply chain depth
| Criterion | Score |
|---|---|
| Economic framing | 5/10 |
| Decision end-state | 4/10 |
| Conceptual sharpness on supply chain | 5/10 |
| Freedom from obsolete doctrinal centerpieces | 3/10 |
| Robustness against KPI theater | 3/10 |
Average: 4.0/10.
Economic framing — 5/10. Profit and cost-to-serve are relevant objectives. Their adequacy depends on representing the consequences of decisions rather than simply distributing costs across a fixed forecast. (22)
Decision end-state — 4/10. Plans guide material commitments, but evaluation and execution remain separate human responsibilities. Recurring automated transaction production is not publicly demonstrated. (3)
Conceptual sharpness on supply chain — 5/10. The vendor understands model scope and operating constraints. It is less explicit about the joint uncertainty that determines which commitments are financially sound. (9)
Freedom from obsolete doctrinal centerpieces — 3/10. The tactical product remains organized around planning meetings and scenario comparisons. Better calculations can improve that process without eliminating its recurring manual coordination. (3)
Robustness against KPI theater — 3/10. Financial language is more useful than accuracy slogans, but projected improvements are presented without a sufficient realization account. (7)
Decision and optimization substance
| Criterion | Score |
|---|---|
| Probabilistic modeling depth | 2/10 |
| Distinctive optimization or ML substance | 4/10 |
| Real-world constraint handling | 5/10 |
| Decision automation and labor productivity | 3/10 |
| Resilience under real operational complexity | 4/10 |
Average: 3.6/10.
Probabilistic modeling depth — 2/10. Sensitivity analysis is accessible; a coherent distribution of future demand and supply feeding a common decision policy is not documented. (2, 5)
Distinctive optimization or ML substance — 4/10. Functional modeling is credible, but no public formulation or reproducible comparison establishes unusual computational depth. The AI announcement supplies few mechanisms. (11)
Real-world constraint handling — 5/10. Release notes expose specific business restrictions, supporting a more concrete assessment than generic optimization claims. Their interactions and economic calibration remain hard to inspect. (6)
Decision automation and labor productivity — 3/10. Self-service scenario changes reduce dependence on specialists for routine analysis. The broader preparation, maintenance, approval, and execution workload is not measured. (8)
Resilience under real operational complexity — 4/10. Replanning offers a practical response to changed circumstances. The historical implementation account recognizes that the model itself must change; the current product leaves the cost and testing of such reformulations unclear, particularly when an omitted interaction exceeds its configurable rules. (9, 17)
Product and architecture integrity
| Criterion | Score |
|---|---|
| Architectural coherence | 5/10 |
| System-boundary clarity | 6/10 |
| Security seriousness | 2/10 |
| Software parsimony and ownership cost | 4/10 |
| Compatibility with programmatic and agent-assisted operations | 3/10 |
Average: 4.0/10.
Architectural coherence — 5/10. The shared scenario application is focused. The technical boundary between model execution, data handling, and Copilot remains largely unpublished. (14)
System-boundary clarity — 6/10. Strategic and tactical analysis have identifiable inputs, users, and outputs. That clarity helps distinguish the application from an execution system. (1, 2)
Security seriousness — 2/10. Sensitive operational models require controls beyond a website privacy notice. Public evidence does not establish their tenant, support-access, retention, or AI-processing boundaries. (21)
Software parsimony and ownership cost — 4/10. Deliberate scope control is sensible. Neither database field count nor a small interface measures the cost of keeping business logic and input data reliable. (10)
Compatibility with programmatic and agent-assisted operations — 3/10. Natural-language assistance may ease analysis. A public path for agents to inspect, test, and maintain the decision model is missing. (11)
Technical transparency
| Criterion | Score |
|---|---|
| Public technical documentation | 4/10 |
| Inspectability without vendor mediation | 3/10 |
| Portability and lock-in visibility | 3/10 |
| Implementation-method transparency | 5/10 |
| Evidence density behind technical claims | 4/10 |
Average: 3.8/10.
Public technical documentation — 4/10. Release descriptions and implementation essays explain parts of the product. The solver, schema, evaluation, and production interfaces remain less accessible. (6, 9)
Inspectability without vendor mediation — 3/10. Users can compare inputs and outputs, but that does not make the computational logic inspectable. Public material does not substantiate the claim that the application has no black box. (14)
Portability and lock-in visibility — 3/10. Spreadsheet interchange helps move data. It does not preserve the semantics of a maintained model or establish a portable replacement for its execution. (2)
Implementation-method transparency — 5/10. Baseline validation and requirements work are described in useful terms. The continuing delivery process for customer-specific changes is less visible. (9)
Evidence density behind technical claims — 4/10. Specific cases and a model release support real functionality. Public evidence is thinner for optimality, robustness, and learning-based improvements. (4, 6)
Vendor seriousness
| Criterion | Score |
|---|---|
| Technical seriousness of public communication | 4/10 |
| Technology roadmap integrity | 5/10 |
| Conceptual sharpness | 6/10 |
| Economic accountability | 3/10 |
| Defensibility in an agentic-software world | 4/10 |
Average: 4.4/10.
Technical seriousness of public communication — 4/10. Practical modeling essays coexist with sweeping technology trends and underspecified AI claims. The more ambitious language exceeds the exposed technical evidence. (12)
Technology roadmap integrity — 5/10. Long-lived modeling work and identifiable releases support continuity. The proposed self-improving scenario generation has not received comparable public validation. (16, 11)
Conceptual sharpness — 6/10. The vendor recognizes that usability, model fit, and maintenance determine success. Those principles are stronger than its description of how uncertain futures enter the optimizer. (13, 17)
Economic accountability — 3/10. Claimed profit gains lack the period, cost reconciliation, and counterfactual needed for an outcome assessment. Responsibility for model inadequacy must remain visible alongside customer responsibilities. (7)
Defensibility in an agentic-software world — 4/10. Domain modeling experience is valuable. The durable advantage requires lowering the full cost of producing and maintaining reliable decisions, beyond making scenario conversations easier. (15)
Sources
Sources accessed November 4, 2026. Historical custom applications and companion simulation products are distinguished from the current Factible Tools SaaS application.
Factible Tools homepage. Published undated. Accessed November 4, 2026.
Supply Chain Designer. Published undated. Accessed November 4, 2026.
Tactical Planner. Published undated. Accessed November 4, 2026.
Production Planning. Published undated. Accessed November 4, 2026.
Sourcing Optimization. Published undated. Accessed November 4, 2026.
[6] Factible Tools Update 26.1
Factible Tools Update 26.1. Published 2026-01-15. Accessed November 4, 2026.
[7] Colombian Dairy Company: 6% Profit Boost
Colombian Dairy Company: 6% Profit Boost. Published 2025-05-16. Accessed November 4, 2026.
[8] Tariffs are causing chaos. Modeling them shouldn’t
Tariffs are causing chaos. Modeling them shouldn’t. Published 2025-04-05. Accessed November 4, 2026.
[9] Supply Chain Planning and Optimization: A Roadmap to Success
Supply Chain Planning and Optimization: A Roadmap to Success. Published 2024-12-05. Accessed November 4, 2026.
[10] 4,000 Reasons Supply Chain Design Tools Fall Short
4,000 Reasons Supply Chain Design Tools Fall Short. Published 2025-09-10. Accessed November 4, 2026.
Introducing AI Copilot. Published 2025-10-27. Accessed November 4, 2026.
[12] Trends in Supply Chain Design Optimization
Trends in Supply Chain Design Optimization. Published 2024-11-01. Accessed November 4, 2026.
Too Late for Optimal. Published 2025-03-12. Accessed November 4, 2026.
Why Factible Tools. Published undated. Accessed November 4, 2026.
About Factible Tools. Published undated. Accessed November 4, 2026.
[16] Technologix supply chain intelligence
Technologix supply chain intelligence. Published undated. Accessed November 4, 2026.
[17] 25 years of Chemtrade supply chain optimization
25 years of Chemtrade supply chain optimization. Published 2016-09-12. Accessed November 4, 2026.
[18] ProdFlow production simulation
ProdFlow production simulation. Published undated. Accessed November 4, 2026.
FlexSim at Factible. Published undated. Accessed November 4, 2026.
[20] Factible Tools public login and delivered frontend
Factible Tools public login and delivered frontend. Published observed 2026-11-04. Accessed November 4, 2026.
[21] Factible Tools Privacy Policy
Factible Tools Privacy Policy. Published 2024. Accessed November 4, 2026.
Profitability Analysis. Published undated. Accessed November 4, 2026.