Vyom builds a single living causal model of how one specific company actually works, then runs a workforce of agents from it. The same engine covers construction, manufacturing, SaaS, logistics, healthcare and more. What changes per industry is configuration, never code. Everything here is built and verified on reality-grade synthetic companies with known ground truth. We are pre-seed, with zero live deployments, and we say that plainly, because known ground truth is exactly what makes these worked examples checkable.
There is one engine. It ingests events, builds a graph of variables and the weighted causal edges between them, propagates the effect of a change through that graph, simulates an intervention before anyone commits to it, and runs agents that watch, reason and act. That engine does not know or care what industry it is looking at.
What a specific company brings is configuration, not new software: the variables that describe its business, the connectors into its systems, the external signals that move it, and the metrics each role watches. A construction GC and a SaaS company load different configuration and get the same reasoning. If a line of runtime code ever read if industry == “construction”, that would be a bug we would remove, not a plan we would ship. The vocabulary is per company. The math is shared.
The proof that this is one environment and not a set of vertical products is what happens when a company that fits no template shows up. You describe the business in plain English. Vyom builds its model on the spot: the variables that matter, the weighted causal edges between them, the levers someone can actually pull, the roles who own each metric, 10 to 16 entity types, and about 1,500 synthetic records to give it a running start. No template. No industry-specific code.
From that moment the same six modes run on it exactly as they run on Meridian Construction. There is no separate build step for a new industry, because there is no new industry code to write.
Everything below is an instance of the same six modes running on a different company. They do not change by industry. Meridian Construction’s rain-to-cash chain and a hospital’s no-show-to-revenue chain are the same six modes pointed at different variables.
Eight industries are built as templates you can load now, each configuration for the same engine. Beyond the eight, any company can be onboarded from a plain-English description. On connectors, the honest status: construction and SaaS are wired (integrations built for read and, where it makes sense, write); the other six are modeled (the connector surface specified and reasoned over, with the live external hookup as the remaining step). The reasoning runs identically across all of them.
Four worked examples on named synthetic companies, wired-first. Open each for the full how, why and what. Because the true structure was authored, every claim is checkable against known ground truth.
Everything above is built and verified against reality-grade synthetic companies whose true cause-and-effect structure we authored, so every claim traces back to a number we can check. Vyom is pre-seed and pre-revenue, with zero live customer deployments.
Two genuine outstanding items, everywhere: large-GPU pretraining, and live external hookups to real partners’ systems. Connector packs: construction and SaaS wired; the other six modeled. Full status →
The interactive Explore page is the hands-on version: switch companies and fire a signal through the model yourself. Or start the conversation.
Request access