> ## Documentation Index
> Fetch the complete documentation index at: https://developers.within.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Build the Company Brain

> Turn on Companion to capture how work actually happens, then spend time in what it captures before building anything.

The Company Brain provides the process context used throughout the transformation workflow. This page covers the first two phases: capturing how work happens and reviewing what was captured.

## Discover

[Companion](/concepts/discover-structure-improve) captures work as participating team members perform it. It processes the captured activity to remove detected PII and user attribution, then organizes the result into a queryable map of processes and value streams.

Capture can run across several people at once, which helps reveal process variation that interviews and written procedures may miss. The Interviewer can add context for work Companion cannot observe.

Discover still needs a defined scope, clear communication, and enough coverage to support the decisions you plan to make.

**1. Enable Companion for the team**

Follow the deployment guidance for your environment, then have participating team members use it while they perform the work in scope.

**2. Select the right scope of users**

Choose the people who actually perform the work in the processes you care about. They are who you learn from.

**3. Make sure that scope is sufficient**

Include enough people and natural variation to support the intended analysis. A single person's sessions may not represent the process across roles, regions, or exception types.

**4. Run a kickoff**

Explain the scope, collection period, support path, and expected participation before capture begins.

**5. Explain the value to users**

Be transparent about what Companion captures, how the data is processed, who can access the result, and how the analysis will be used. Address questions about privacy and role impact directly rather than leaving participants to infer the answers.

**6. Help them feel part of it**

Give the people doing the work a way to correct missing context and review conclusions that affect their process.

**7. Encourage Signals**

Ask people to contribute Signals during sessions, including effective practices and recurring friction that may not be clear from the activity sequence alone.

**8. Keep it on, and make it recurring**

Run Companion for at least two weeks per cycle, and repeat at least four times a year. Work changes, and a recurring cadence keeps the Company Brain a live picture rather than a one-time snapshot.

## Structure

Once Companion has run, review the resulting Company Brain before selecting a build. This is where you check whether the available evidence supports the scope and assumptions behind the objective.

### Explore the visualizations

Start at the value-stream level and drill down to the processes relevant to the objective.

### Review the process steps

Inspect the captured activities to see where time goes, handoffs fail, or people move repeatedly between tools.

### Ask Advisor

When a pattern needs explanation, ask Advisor to analyze it, generate a visualization, or prepare a time-and-motion view.

```text theme={null}
How does our vendor-onboarding process actually work today, and where do we
lose the most time?
```

The point of Structure is to build intuition for your own operation before you build anything on top of it.

> [!NOTE]
>
> You can ask the same questions from any MCP client. [Help a process performer](/guides/process-performer) and [State-of-the-team report](/guides/state-of-team) show the tool chains behind this kind of exploration.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.