Review of ketteQ, Adaptive Supply Chain Planning Vendor

Last updated: April, 2026

Go back to Market Research

ketteQ (supply chain score 4.0/10) is a real supply chain planning vendor with a coherent cloud product, real customer references, and a distinctive Salesforce-centered architecture. Public evidence supports meaningful product scope across demand, inventory, supply, service parts, and execution-adjacent planning, plus a genuine effort to modernize old APS workflows through a shared PolymatiQ engine. Public evidence does not support the stronger reading implied by phrases such as world’s most adaptive, agentic AI engine, or continuously learning decisions at scale. The product looks materially more serious than superficial AI theater, but the public record remains too opaque on solver internals, probabilistic semantics, and operational failure modes to justify stronger technical confidence.

ketteQ overview

Supply chain score

• Supply chain depth: 4.2/10
• Decision and optimization substance: 4.2/10
• Product and architecture integrity: 4.2/10
• Technical transparency: 3.2/10
• Vendor seriousness: 4.0/10
• Overall score: 4.0/10 (provisional, simple average)

ketteQ is best understood as a modern packaged planning suite with a strong Salesforce affinity, not as a transparently documented quantitative decision engine. Its public strengths are architectural coherence, credible planning scope, and a practical commercial story for firms already invested in Salesforce. Its public weakness is that the technical heart of the product, PolymatiQ, is still presented mostly through slogans about multi-pass experiments, adaptability, and agentic AI rather than through inspectable mathematical or engineering detail.

ketteQ vs Lokad

ketteQ and Lokad overlap on demand, inventory, and supply planning, but they approach the problem from almost opposite software philosophies.

ketteQ sells a packaged application suite with prebuilt modules, Salesforce-centric workflows, and a shared solver story meant to sit on top of existing planning landscapes or replace them incrementally. The visible value proposition is faster deployment, familiar enterprise UX, CRM-adjacent collaboration, and a practical bridge between planning and commercial operations. That is a serious proposition, but it remains application-first and vendor-mediated.

Lokad is much narrower in perimeter and much sharper in technical posture. It exposes a programmable environment where forecasting and decision logic are meant to be expressed explicitly rather than hidden inside a proprietary solver brand. The practical tradeoff is clear: ketteQ promises a more packaged operating model, while Lokad demands more modeling work but offers much stronger transparency into the underlying decision logic.

On uncertainty and optimization, the contrast is similarly sharp. ketteQ repeatedly claims probabilistic, adaptive, and multi-pass planning, yet its public material does not disclose how uncertainty is represented, how trade-offs are encoded, or how the solver chooses between competing decisions. Lokad, by contrast, is much more explicit in public about its probabilistic and programmatic posture. That does not prove ketteQ is weak; it does mean that, from public evidence alone, ketteQ looks more like a modern APS suite with a black-box solver than like a transparent system of intelligence.

Corporate history, ownership, funding, and M&A trail

ketteQ is not an incumbent and should be read as a scale-up. Public corporate and funding records point to a company founded in 2018, led today by Mike Landry, with a product family built around Salesforce-native UX and AWS-hosted computational services. The company presents itself as the result of lessons learned from many prior planning implementations and from an experienced founding and leadership team rather than as a research spinout or a solver-first laboratory. (4, 18, 21, 26, 27)

The funding story is straightforward. Public venture databases and the company’s own 2025 announcement indicate roughly $30.9M in disclosed funding across early rounds, culminating in a $20M Series B led by Vocap Partners in August 2025 with existing investor Circadian Ventures participating. That places ketteQ beyond the fragile seed stage, but still far from the capital depth or installed-base inertia of the larger APS incumbents. (19, 22, 23, 24, 27, 28)

No significant acquisition trail was found. That matters positively for product coherence: the current platform appears to have grown as one product family rather than as a collage of purchased modules. The same fact also limits how much proven depth can be inferred from breadth claims, because each adjacent module still depends on the credibility of one relatively young product organization.

Product perimeter: what the vendor actually sells

The visible perimeter is broad enough to classify ketteQ as a real planning-suite vendor rather than a narrow forecasting tool. The current product surface spans demand planning, inventory planning, supply planning, integrated business planning, service parts planning, control tower, fulfillment and allocation planning, and Salesforce-linked CRM or Manufacturing Cloud overlays. The product narrative is therefore about a multi-module planning and execution layer, not just about one statistical forecasting widget. (1, 2, 6, 7, 8, 9, 10, 11, 12, 13, 14)

The strongest evidence sits in the planning core. Inventory, service parts, and supply planning pages expose actual concepts such as MEIO, ASL generation, order-policy tuning, BOM-aware supply planning, install-base forecasting, rotable pools, trigger-point ordering, and capacity-aware supply planning. That is materially better than generic marketing language and strongly suggests a product dealing with genuine supply-chain objects. (7, 8, 9)

The weaker evidence sits in the more expansive AI-and-agent framing. The homepage and platform pages now present ketteQ as intelligent planning and CRM agents powered by PolymatiQ, able to augment existing environments or replace them. That may be directionally true as a commercial packaging strategy, but the public record does not yet show that every advertised module rests on equally deep, distinctive computational substance. (1, 2, 3, 20)

Technical transparency

Technical transparency is ketteQ’s weakest area. The company publishes enough material to understand the product family, the cloud positioning, and the Salesforce-plus-AWS architecture. A technical buyer can infer that Salesforce carries much of the workflow, data-sharing, security, and user-experience burden, while AWS hosts heavier analytical and solver workloads. That is useful and better than pure brochureware. (2, 4, 13, 15, 16)

The problem starts where the strongest claims begin. Public pages repeatedly mention multi-pass experiments, probabilistic planning, adaptive tuning, and agentic AI, but do not explain objective functions, optimization methods, distribution semantics, model classes, or the operational limits of the solver. No public API reference, SDK documentation, engineering handbook, or developer-grade technical manual was found during this refresh. (1, 3, 6, 15, 17, 21)

This opacity matters because ketteQ’s differentiation story is itself technical. A conventional planning vendor can perhaps get away with generic language around collaboration and visibility. A vendor selling a patent-pending adaptive solver and agentic planning engine invites a higher evidentiary bar, and the public material does not yet meet it.

Product and architecture integrity

Architecturally, ketteQ looks more coherent than many peers. The public record consistently points to one product family built around Salesforce-native UX, workflow, and data-sharing on one side, with AWS-hosted analytics and solver services on the other. The same PolymatiQ brand appears across planning and execution pages, and the company repeatedly frames deployment as either augmenting incumbent suites or serving as the end-to-end planning stack. That is a cleaner product story than a suite assembled from many acquisitions. (1, 2, 4, 13, 14, 15)

The main architectural risk is hidden complexity rather than obvious fragmentation. ketteQ now claims to bridge planning and CRM, to embed agents into Salesforce, and to deliver planning augmentation on top of SAP, Oracle, Kinaxis, Blue Yonder, o9, Anaplan, Logility, or homegrown systems. That is commercially attractive, but it also suggests a fairly demanding integration and orchestration problem that the public material describes only at a high level. (1, 2, 13, 16)

Security evidence is mixed but not empty. ketteQ strongly foregrounds Salesforce and AWS as the foundations for scale and security, and its FAQ and Salesforce pages clearly lean on inherited enterprise-platform trust. That is still partly box-ticking rhetoric, yet it is attached to real underlying platforms rather than to purely abstract assurances. (13, 14, 15)

Supply chain depth

ketteQ is materially inside the supply-chain-planning category. The product addresses demand forecasting, replenishment, capacity and supply balancing, service parts, field stock, BOM-aware planning, allocation, and control-tower monitoring. It is clearly not just BI software wearing supply-chain branding. (6, 7, 8, 9, 10, 11, 12)

The doctrinal depth is uneven, however. On the positive side, ketteQ openly talks about volatility, supplier constraints, lead times, rotable pools, field locations, multi-echelon inventory, and scenario analysis. On the negative side, the visible framing still leans heavily on service levels, forecast accuracy, adaptability, and responsiveness rather than on a sharply economic theory of decision quality. (6, 7, 8, 9)

That leaves ketteQ in a respectable middle position. It is clearly solving real planning problems, and more substantive than broad CRM vendors that only dabble in supply chain. It is not yet publicly evidenced as a vendor with a particularly sharp, opinionated doctrine about supply chain as applied economics.

Decision and optimization substance

This is the strongest positive dimension of the review, but also the one where public opacity matters most. ketteQ clearly aims to do more than reporting and workflow. The product pages repeatedly describe scenario generation, inventory-policy tuning, multi-item and multi-echelon optimization, available-to-promise logic, supply-capacity balancing, and service-parts decision support. That is enough to conclude that a genuine planning engine exists behind the UI. (3, 6, 7, 8, 9, 12)

The missing piece is methodological disclosure. Public evidence does not reveal whether PolymatiQ is built around mathematical programming, simulation optimization, heuristics, reinforcement learning, or some hybrid. The demand-planning page references a plug-in best-fit forecasting API and mentions Python, Meta, and AWS, which suggests extensibility and real engineering, but not enough to establish distinctive scientific depth. (6, 21)

So the judgment has to stay balanced. ketteQ looks more serious than a fake AI layer pasted onto MRP screens. It does not look transparent enough to earn high confidence in the distinctiveness of its optimization and probabilistic claims.

Vendor seriousness

ketteQ looks like a serious commercial software company, but one whose public language increasingly outruns its public evidence. The positive case is real: there is a coherent product, real customer references, a believable venture trajectory, and a thoughtful positioning around Salesforce-native deployment rather than a generic all-things-to-all-buyers story. (4, 5, 18, 19, 20, 22, 25)

The negative case is the current messaging stack. The phrases world’s most adaptive, agentic AI engine, AI that acts, intelligent planning agents, and continuously improves decisions are all very strong claims. They are not absurd claims, but the public record does not back them with an equally strong level of technical precision, explicit trade-offs, or discussion of failure modes. (1, 3, 17, 20)

This produces a middling seriousness score rather than a low one. ketteQ is not empty hype, but its public communication is still more commercially inflated than technically disciplined.

Supply chain score

The score below is provisional and uses a simple average across the five dimensions.

Supply chain depth: 4.2/10

Sub-scores:

• Economic framing: ketteQ does discuss working capital, service trade-offs, budget alignment, and inventory risk across its planning pages. That is better than pure KPI theater. The visible doctrine still leans much more on service levels, adaptability, and responsiveness than on a sharp economics-first theory of decisions, which keeps the score in the middle. 4/10
• Decision end-state: The product is clearly intended to recommend and in some cases automate supply decisions rather than merely produce dashboards. That deserves real credit. The public posture still centers on planners, scenario management, and collaborative review rather than unattended decisions as the normal state, so the score cannot go much higher. 5/10
• Conceptual sharpness on supply chain: ketteQ has a coherent thesis around adaptive planning in volatile conditions and around bridging planning with CRM and Salesforce workflows. That is more distinctive than generic APS language. The thesis remains commercially broad rather than technically sharp, so it lands as a moderate strength rather than a high-conviction doctrine. 5/10
• Freedom from obsolete doctrinal centerpieces: The product clearly goes beyond static MRP and static safety-stock administration, especially in service parts and scenario planning. That is a genuine positive. Still, service levels, forecast accuracy, and conventional planning constructs remain highly visible in the public pages, which limits the score. 3/10
• Robustness against KPI theater: Public messaging is not dominated by vanity analyst badges or pure transformation clichés, and some real operational objects are visible. Even so, the product story still relies heavily on outcome claims that are not deeply evidenced publicly, and the public doctrine does not show strong skepticism toward metric gaming. That supports a moderate score rather than a high one. 4/10

Dimension score: Arithmetic average of the five sub-scores above = 4.2/10.

ketteQ is plainly engaged with real supply-chain problems. The cap comes from a doctrine that is operationally serious but still conceptually mainstream. (6, 7, 8, 9, 10)

Decision and optimization substance: 4.2/10

Sub-scores:

• Probabilistic modeling depth: ketteQ repeatedly uses probabilistic language and ties it to multi-pass scenario analysis, adaptive tuning, and demand planning. That suggests more than cosmetic Monte Carlo rhetoric. The public record still does not explain the actual probabilistic semantics or how uncertainty is propagated through decisions, so the score remains moderate. 4/10
• Distinctive optimization or ML substance: PolymatiQ appears to be a real solver layer rather than a purely decorative AI label, and the product pages expose enough constrained-planning objects to support that reading. The missing public methodology, benchmarks, and model detail prevent a higher score. 4/10
• Real-world constraint handling: The service-parts and supply-planning pages mention BOMs, rotable pools, ASLs, supplier price breaks, lead times, repairs, returns, capacity constraints, and different stocking locations. That is a strong sign of real-world planning scope. The score is still capped because public evidence does not show the exact optimization formulation or how those constraints interact computationally. 5/10
• Decision production versus decision support: ketteQ clearly aims to produce orders, allocations, and planning outputs rather than only charts and alerts. That is a real positive. The product still looks primarily like an advanced decision-support suite with automation features rather than a system that publicly proves unattended decision production at scale. 4/10
• Resilience under real operational complexity: Public pages show awareness of complexity such as field stock, service parts, vendor constraints, and changing supply conditions. That is better than toy optimization language. The company still does not discuss failure modes, degradation, or limits with enough specificity to justify a higher score. 4/10

Dimension score: Arithmetic average of the five sub-scores above = 4.2/10.

ketteQ likely has real optimizer substance. The review cannot score it higher because the public record leaves too much of that substance hidden behind one solver brand. (3, 6, 7, 8, 9, 21)

Product and architecture integrity: 4.2/10

Sub-scores:

• Architectural coherence: The public story is unusually consistent about one Salesforce-plus-AWS architecture and one shared PolymatiQ planning engine. That gives the product a coherent center of gravity. The score stops short of high because the actual internal boundaries and orchestration patterns are not publicly described in enough detail. 5/10
• System-boundary clarity: ketteQ does a reasonably good job of presenting itself as a planning and decision layer rather than as the system of record. Its positioning on top of ERP and inside Salesforce makes that visible. The score remains moderate because the boundary between CRM workflows, planning logic, and execution logic is still more marketed than technically specified. 4/10
• Security seriousness: The security story leans heavily on inherited trust from Salesforce and AWS, which is better than pure abstract assurances. That remains partly platform-badge signaling rather than a deep public articulation of secure-by-default design choices, so the score stays moderate. 4/10
• Software parsimony versus workflow sludge: ketteQ appears more focused than the broader legacy suites and is clearly not just endless CRUD wrapped in AI language. At the same time, the growing mix of planning modules, CRM agents, control towers, and collaborative layers creates a real risk of workflow accretion around the core engine. That balance supports a middle score. 4/10
• Compatibility with programmatic and agent-assisted operations: The public material references Python, SQL, JSON, APIs, and plug-in forecasting methods, which suggests a degree of openness beyond pure UI configuration. Yet the product is still fundamentally presented as a packaged suite rather than as a naturally text-first or versioned operating environment. That keeps the score moderate. 4/10

Dimension score: Arithmetic average of the five sub-scores above = 4.2/10.

ketteQ’s architecture looks cleaner than many older APS vendors. The constraint is not obvious incoherence, but limited inspectability of the boundaries and operating mechanics. (2, 4, 13, 15, 16, 21)

Technical transparency: 3.2/10

Sub-scores:

• Public technical documentation: ketteQ exposes a meaningful amount of product and architecture material, including platform pages, Salesforce integration pages, FAQs, and product sheets. That is enough to classify the offer with confidence. It is still far from developer-grade technical documentation, so the score remains low-moderate. 3/10
• Inspectability without vendor mediation: A technical reader can infer the high-level architecture, deployment posture, and module perimeter without booking a call. That is a genuine positive. The core solver logic remains too opaque to inspect meaningfully from public sources alone, which caps the score. 4/10
• Portability and lock-in visibility: The product openly states that it can augment incumbent planning stacks and that it relies on Salesforce and AWS in structured ways. This makes some operating assumptions legible. However, the public material says little about migration boundaries, data semantics, or the practical difficulty of leaving the platform, so only a moderate score is justified. 4/10
• Implementation-method transparency: ketteQ repeatedly promises rapid deployment and practical augmentation of existing systems, which at least gives the buyer some sense of the intended rollout model. The public record still does not expose implementation playbooks, governance patterns, or detailed delivery mechanics in a way that would support a higher score. 3/10
• Evidence density behind technical claims: This is the weak point. The stronger the claim becomes, especially around agentic AI, adaptive learning, or solver distinctiveness, the thinner the public proof tends to get. That gap forces a clearly low score on this sub-criterion. 2/10

Dimension score: Arithmetic average of the five sub-scores above = 3.2/10.

ketteQ is transparent enough to be taken seriously as a real product. It is not transparent enough to validate its strongest technical claims with confidence. (1, 2, 3, 13, 15, 21)

Vendor seriousness: 4.0/10

Sub-scores:

• Technical seriousness of public communication: ketteQ’s communication is attached to a real product family, real customers, and real deployment claims. That is meaningfully better than empty startup rhetoric. The score remains moderate because the public communication still prefers strong slogans over precise technical exposition whenever the solver is discussed. 4/10
• Resistance to buzzword opportunism: The current public messaging leans hard into agentic AI, intelligent agents, and adaptive planning as catch-all differentiators. Some of that branding may reflect real product work. Even so, the eagerness to adopt current AI vocabulary without equal technical disclosure warrants a below-average score here. 3/10
• Conceptual sharpness: ketteQ does have a visible point of view around Salesforce-centric planning and around augmenting existing landscapes instead of demanding immediate rip-and-replace programs. That is more distinctive than generic suite messaging. The product philosophy is still not especially sharp once it moves from architecture to decision theory, which keeps the score moderate. 4/10
• Incentive and failure-mode awareness: The product pages show awareness of operational volatility, supplier constraints, and execution risk. That is useful. The public record says very little about how ketteQ itself can fail, when its automated recommendations should be distrusted, or what trade-offs it knowingly rejects, so the score remains moderate. 4/10
• Defensibility in an agentic-software world: ketteQ has some genuine defensibility because it sits on real planning logic, real integrations, and a coherent architecture rather than on pure workflow theater alone. A material part of the visible value proposition still depends on packaged enterprise software and AI-facing UX layers that may become cheaper to replicate, so the score is positive but not high. 5/10

Dimension score: Arithmetic average of the five sub-scores above = 4.0/10.

ketteQ looks like a serious scale-up with a real product. The score stays moderate because the company’s public discipline around technical claims still lags behind the ambition of its branding. (1, 4, 18, 19, 22, 25)

Overall score: 4.0/10

Using a simple average across the five dimension scores, ketteQ lands at 4.0/10. This reflects a credible and coherent planning vendor whose public substance is real, but whose strongest technical claims remain under-documented.

Conclusion

ketteQ is not a fake. It has a coherent architecture, real planning scope, named customers, and a product story that is more modern than many legacy APS incumbents. The company also deserves credit for building around a consistent Salesforce-plus-AWS posture instead of pretending to be a universal platform detached from concrete enterprise constraints.

The problem is not that the product looks trivial. The problem is that the public record does not let an external technical reader inspect the solver, the probabilistic layer, or the operational limits of the automation story with enough precision. As a result, the fairest public assessment is that ketteQ is a promising and commercially serious packaged planning suite whose core engine may be meaningful, but is still too opaque to rate as a clearly distinctive system of intelligence.

For buyers already committed to Salesforce and looking for a modern planning layer with a practical deployment story, ketteQ is a credible candidate. For buyers who need high transparency into decision logic, probabilistic semantics, and optimization mechanics, the public evidence still points toward more explicit platforms such as Lokad.