> ## Documentation Index
> Fetch the complete documentation index at: https://klarityai-add-transformation-playbook.mintlify.site/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 is what everything else is built on. This page covers the first two phases of the motion: capturing how work happens, and making sense of it.

## Discover

[Companion](/concepts/discover-structure-improve) is how you build the Company Brain. Your team turns it on and works normally. There is nothing to learn and no documentation to write. As they work, Companion observes how the work actually gets done, scrubs PII and user attribution, and assembles a living, queryable map of how the organization really operates, down to the button-click level and packaged into value streams.

Because capture runs in parallel across everyone in scope, you cover a whole function in days. That is a picture months of one-on-one interviews could never produce. The Interviewer fills the gaps Companion can't observe.

Running Discover well is a real motion, not a switch you flip.

<Steps>
  <Step title="Enable Companion for the team">
    People run it in the background of their normal work. There is nothing new to learn.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Make sure that scope is sufficient">
    Include enough people, and enough of the natural variation, that the Company Brain comes out rich rather than thin. One user gives a sliver. A representative cross-section gives the real picture.
  </Step>

  <Step title="Run a kickoff">
    Bring everyone together on a call, ideally in person, and start as a group. A shared start drives shared momentum.
  </Step>

  <Step title="Explain the value to users">
    Be transparent about how it works and what's in it for them: no SOPs to write, no interviews to sit, PII scrubbed and nothing attributed to them, and making their work visible is what lets AI take the grunt work off their plate.

    Naming the fear directly, that this is not about automating people out of a job but about taking the drudgery off their plate, is what turns skeptics into participants.
  </Step>

  <Step title="Help them feel part of it">
    Frame this as something they are shaping, not something done to them. The people doing the work are the experts, and their input directly shapes what gets built.
  </Step>

  <Step title="Encourage Signals">
    Ask people to contribute Signals during sessions, flagging what they already do well. Signals surface the bright spots and repeated practices that make the best skills.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## Structure

Once Companion has run, the platform turns the captured activity into your Company Brain. Before building anything, spend time in it. The teams that explore first make far better build choices later.

**Explore the visualizations.** Klarity packages thousands of process nodes into value streams and maps you can navigate. Start at the value-stream level and drill down.

**Review the process steps.** Go to the button-click level to see how work actually happens: where time goes, where handoffs drop, where tools multiply.

**Ask Advisor.** When something looks off or interesting, ask. Advisor can drive process-excellence analysis, surface cost optimizations, generate visualizations, and run time-and-motion views.

```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.
</Note>