MalleableMalleable

How Malleable works

Most software is rigid: written once, deployed to everyone, designed for someone else's process, not yours. Every team's way of working is a little bit bespoke, and changing operationalized workflows is usually so costly that organizations mostly don't.

Malleable inverts that. Instead of adapting your process to the software, the software adapts to your process. You focus on the outcome; Malleable builds and rebuilds the implementation around it.

Three layers

Setup. You describe your use case in plain English: what it should accomplish, what success looks like, and what real-world side effects it has (approvals, orders, notifications). An agent called the architect turns that into a structured workflow: stages, components, integrations, and data. The plain-language intent stays attached to the workflow rather than being lost in translation to code.

Execution. End users run the workflow through an adaptive interface (a web form, Slack, email, or an API), and an agent called the runner works through the stages. To the person running it, it can look and feel like ordinary software, just shaped to your process.

Improvement. Because the workflow's source of truth is your intent, not a hard-coded implementation, changing it is a conversation with the architect rather than a rebuild. The system also proposes changes itself via suggestions.

The workflow is a plan, not a script

This is the key difference from traditional automation tools. The structured workflow gives the runner agent a plan to follow, but during a run, the agent can exercise judgment: handle an edge case the plan didn't anticipate, ask the user a clarifying question, or flag a problem instead of failing silently. Rigid automations break on unexpected input; an agent following a plan can adapt while staying inside the guardrails the workflow defines.

The division of authority is deliberate: only the architect can add integrations, emails, and components, and the runner can only use what was configured at setup. You get flexibility during runs without a run ever inventing new capabilities nobody approved.

Where to go deeper