# Grain for OPERATIONS: Build tools that fit the way work happens.

> Turn spreadsheets, documents, processes, and repeated requests into inspectable tools and routines without separating builders from operators.

- Canonical page: [/solutions/operations](https://grain.sh/solutions/operations)
- Agent-readable page: [/agents/solutions--operations.md](https://grain.sh/agents/solutions--operations.md)
- Section: Solutions

## What this page covers

- Output: Internal tool
- Output: Operating table
- Output: Process document
- Output: Weekly automation
- Use your real source files: Start with CSV, XLSX, documents, screenshots, or repository context instead of rebuilding the inputs.
- Return an editable system: Open the result in Grain Sheets, Docs, Tables, or an app surface and keep refining it in chat.
- Keep a human checkpoint: Make approvals, exceptions, and owner decisions explicit in the operating flow.
- Start with the outcome: Describe what should be true when the work is done. Grain turns that outcome into a visible Mission.
- Bring the right engine: Use hosted Grain Models or route execution to supported models and CLIs on your connected machines.
- Inspect, edit, and ship: Review the result in Grain, ask for changes, and keep a person in control of the final action.

## Why it matters

Operational software should match the business, not force the business to match a generic template. Grain starts with your files, rules, and outcomes.

## About Grain

Grain is a multi-agent work platform. A person describes an outcome as a Mission, Grain coordinates the models, tools, files, repositories, and connected computers needed to do the work, and the result returns for review.

Start with [the complete agent-readable index](https://grain.sh/agents/index.md) or read [the full site corpus](https://grain.sh/llms-full.txt).