What did we sell?
The agreement records S$12,000 of contracted work. It does not prove all work has been delivered.
At a glanceA Brand Brain is an organised source of approved company facts, brand voice, examples and working rules for people and AI tools. It connects the meaning behind your records: what counts as a qualified lead, which offer is current and who can approve a decision. Your team owns and maintains that foundation.
| Layer | What belongs here | Who checks it |
|---|---|---|
| Business facts | Approved offers, customer fit, definitions and evidence | The person accountable for the business fact |
| Brand judgment | Annotated work, tone, claims and boundaries | Your brand or communications owner |
| Working rules | Decision criteria, exceptions and handovers | The department that operates the process |
Keep the underlying records in the appropriate systems. Your foundation explains what they mean and which source is authoritative. A payment entry belongs with accounts; the definition of an overdue invoice belongs in the rules that interpret it.
Illustrative teaching scenario, not a client result. A signed agreement is S$12,000, an issued invoice is S$6,000 and a bank receipt is S$3,000. Asking “what is our revenue?” without definitions invites a misleading single answer.
The agreement records S$12,000 of contracted work. It does not prove all work has been delivered.
The S$6,000 invoice records an amount billed. Terms and due dates determine what action is appropriate.
The S$3,000 receipt shows cash received. Matching its reference confirms which invoice it settles.
A useful answer names the measure, period and source. Revenue recognition follows the company’s accounting policy and qualified review; a language model should not decide it from these three numbers alone. See how the revenue training module and accounts workflow teach those checks.
Yes, reusable facts and instructions can support different approved AI workspaces. The setup still depends on each tool’s access controls, context limits and supported connections. A copied knowledge pack is a snapshot; a connected retrieval workflow needs its own configuration and testing.
Separate shared brand guidance from restricted customer, employee and financial records. Give a workflow only the information required for its job. Changing the model should trigger a repeat of the same example checks, rather than an assumption that its answers will match.
Learn the preparation steps in our knowledge-base guide, then compare starter workshop practice with a guided workflow build.
No. It is our name for the company knowledge and working rules used to guide approved AI tools. The selected tool supplies the model; your business supplies the approved context.
No. Begin with the sources needed for one selected workflow. Keep private records in appropriately restricted systems and share only the information that workflow needs.
Your company retains its information. Assign a business owner to each important source and a workflow owner to check whether answers and handovers still work.
Not automatically. Copies need refreshing; connected tools need tested retrieval and access rules. The build should document how updates reach each workflow.
A folder stores material. A useful foundation also records which facts are authoritative, what terms mean, which examples to follow and when an answer needs human review.
Choose the department problem first. The corporate training overview explains the nine modules and the preparation needed for a workshop or guided build.
Start with one question that currently requires a search across teams. We’ll help identify its authoritative sources and the module to build around it.