Workblocks · Platform
The execution layer for enterprise work.
Beyond Work is where intelligence meets the systems that run the enterprise. Workblocks are the unit. Studio is where they're authored. Flow is where they run. Library is where they are visible.
Field record · 04 · leaf veins
The five surfaces, and the framework
Workblocks
The unit of execution. A typed, versioned, schema-bound artefact that takes inputs, runs intelligence over them, and produces outputs downstream systems can use.
Studio
The author's surface. Where the person closest to the problem builds the Workblock: with real data, against a real schema, in-room with the client.
Flow
The runtime. Where Workblocks execute in production, with human-in-the-loop as a native state and full audit captured by default.
Library
The accumulation. Workblocks authored at one client become reusable across the network. The Library is where the compounding happens.
Workable
The framework. Source-to-pay built on the platform and delivered with a partner: five stages, nine domain Workblocks and one canonical record model across every spend type.
Composer & Conductor
Two specific surfaces inside the platform sit alongside Studio:
Composer
The document surface: where contracts, memos, legal positions, and structured documents are authored against typed schemas. It is to Word what Studio is to bespoke engineering: a way for the person doing the work to capture it in a form the system understands.
Conductor
The spreadsheet surface: where models, analyses, and structured calculations live with the same schema rigour. Composer and Conductor will be externally announceable at v1.5. A short note for the curious, not the headline of this page.
Properties
Fully model-agnostic. Workblocks are bound to schemas, not to models. Commercial providers and open-weight models are interchangeable at the Flow layer, and a Workblock can run one model for reasoning and a cheaper one for extraction in the same job. Deploy on AWS, Azure, or the customer's own enterprise licenses: the model choice and the data both stay theirs.
Single-tenant by default. Customer data does not leave the customer's environment. The platform deploys into the customer's cloud, not ours.
Human-in-the-loop as a native runtime state. Not a fallback. Not an exception. A first-class state that Workblocks declare and Flow enforces.
Versioning and channels. Workblocks have semantic versions. Channels (draft, staging, production) gate which version runs where. Reverting is a query.
Audit by default. Every input, every output, every model call, every human approval, recorded as an event-sourced timeline. The audit is the runtime, not a sidecar.
Principles
How we think.
The platform is shaped by how we believe enterprise work has to run. Five principles, written down.
How we operate.
We sell into industries that got there by being careful. We carry the same posture. Single tenant, governed and auditable, with ISO 27001 and HDS audits underway and EU AI Act registration in place.
How it fits.
One layer above the tools you already run. Beyond Work does not replace your landscape: it is the orchestration, document intelligence and workflow layer that connects it.