Start with the work. Define the evidence.

Describe who needs information, what decision they are making and which sources they can use. Agree on what the system may do and where a person must decide. A fluent answer is useful only when it fits that operating context.

Company Brain starts from a practical problem: company understanding is scattered across people and tools. The implementation uses stable records, explicit sources and change history so that context can be inspected and maintained.

That structure is a starting point for evaluating retrieval. It does not prove that an agent has found every relevant fact. Keep the question of missing or outdated context visible.

A demonstration can show that a workflow is possible. A business result needs additional evidence: a baseline, a defined measure, real use and a defensible account of what changed.

Company Brain remains an MVP for that reason. Its internal implementation demonstrates an approach to organizational context; measured revenue impact is a separate question.

Define who reviews the answer, who maintains the sources and who responds when something fails. Give those people enough visibility to challenge the result. Permissions, verification and feedback belong in the workflow from the beginning.

These ideas also appear in my Edmonton Startup Week teaching material: set it up, run it and keep it working.