A Workblock is the unit of execution. It takes inputs, applies business logic and AI where useful, brings in people where judgment matters, acts across systems, records evidence, and produces an outcome. Workblocks are governed, reusable, and improve with use.
Platform · Workblocks
The unit of intelligence in the enterprise.
A Workblock is a typed, versioned, schema-bound piece of work that takes inputs, runs intelligence over them, and produces outputs other systems can use.
01Anatomy
INPUTS
Typed parameters. A vendor record. A contract PDF. A free-text email with attachments. Whatever the work needs.
LOGIC
A sequence of steps. Each step may invoke a model call, a system call, a human approval, or a deterministic operation. Steps compose; steps fail cleanly.
SCHEMA
The typed shape of the output. The downstream system reads this. Conformance is enforced at the Flow runtime, not at integration time.
VERSIONS
Semantic. v1, v1.1, v2. Each version is a distinct artefact. Reverting is a runtime decision.
CHANNELS
Draft, staging, production. Each channel can pin a different version. Promoting v1.2 from staging to production is one approval.
02In the world
A supplier-onboarding Workblock at a global industrials company runs 14,000 times per month. Three versions live in production, pinned per geography.
A contract-review Workblock authored by a consultant at Bekaert is now in production at four other Bekaert clients. The author is credited on every run.
A sustainability extraction Workblock authored with Accenture runs against a 100-attribute schema across two languages. 95% schema conformance on the first version.
The number is not the point. What runs at scale, repeatably and under audit, is.
Once you start, you're ahead.
In the enterprise, real execution matters. That's where we lead.