# Make intelligence part of the work

> Connected workflows, operational systems, document processing and the economics of automation.

Canonical URL: https://marmation.com/review/operations/

The business does not care how many tokens or documents a system processes. It cares whether customers receive the right answer, teams complete correct transactions, exceptions become manageable and a process stops relying on invisible manual labor.

## How to use this collection

Our Operations essays look at the work around the model: people, approvals, source data, integration, cost, queue design and error recovery. This is where an AI system becomes an operational asset instead of another disconnected application.

Use the articles as thinking tools, not as product advertisements. Start with the question nearest your current decision, follow the cited sources and inspect the limitations. Each article should tell you what to do differently, when the recommendation changes, and which risks cannot be resolved by reading alone.

## Talk to an engineer, not a form letter

If the decision leads to a real engineering assignment, share the relevant requirements and constraints. Marmation can help determine whether a focused engagement is appropriate. [Discuss a project](<https://marmation.com/contact/>).

## Related reading

- [Document extraction is not document automation.](https://marmation.com/review/document-extraction-is-not-automation/)
- [Your ERP is a system of record. It is not the entire workflow.](https://marmation.com/review/erp-is-not-the-entire-workflow/)
- [Your knowledge assistant cannot repair an ungoverned knowledge base.](https://marmation.com/review/knowledge-quality-is-ai-quality/)