The Company Brain Readiness Score from Paloren rates how ready your business is for a connected company brain across five inputs: sources, ownership, permissions, documentation and workflow clarity. Enter your own figures below to get a 0 to 100 score, a readiness band, and the named next step for that band.
Enter your own figures below. The results table and chart update as you type. The default scenario is pre-loaded so you can see the method before you change anything.
How ready is your knowledge?
| Result | Value |
|---|
Every output comes from the formulas below. Nothing is drawn from a survey, a client result or a third-party benchmark. The figures are model estimates based on the inputs you supply.
| Output | Formula | What it means |
|---|---|---|
| Weighted score | sources x 0.25 + ownership x 0.2 + permissions x 0.2 + docs x 0.2 + workflows x 0.15 | Each input is scored 0 to 10, then weighted to a 0 to 10 total. |
| Readiness band | score below 4 low, 4 to 6.5 medium, above 6.5 high | Band used for planning, not a certification. |
| Blocking gap | minimum of the five input scores | The single biggest constraint, expressed as the input score holding the total back. |
A professional services firm scores 6 on sources, 5 on ownership, 4 on permissions, 4 on documentation and 6 on workflows. The weighted total is 5.0, a medium band. The blocking gap is 4.0, shared by permissions and documentation.
| Input | Value |
|---|---|
| sources | 6 |
| ownership | 5 |
| permissions | 4 |
| docs | 4 |
| workflows | 6 |
This model is deliberately narrow. It values time and direct cost only. It does not price quality improvement, customer satisfaction, risk reduction or revenue lift, because those need evidence from your own operation.
Adoption is the most common source of error. A system that works in a pilot rarely hits its full share on day one. For planning, assume a ramp and test the conservative case.
The model also ignores integration difficulty. Two systems with the same name can differ enormously in effort. List each integration and its owner before you commit budget.
Finally, the figures are not a quote. They are a planning tool. Use them to frame a conversation, then get a scoped proposal based on your actual systems and workflows.
A company brain is a connected knowledge layer that gives AI approved sources, permissions and context for a specific business.
It is not a search engine. It decides which document governs which task, and it applies the same rules to every query, which is what makes AI answers usable inside a business.
Without approved sources, no knowledge system can produce reliable answers.
Sources are the raw material. If records are scattered, duplicated or contradictory, the system will reflect that mess, no matter how good the model is.
A medium band means the foundation exists but one or two constraints will limit the first deployment.
Do not treat it as a failure. Identify the blocking gap, fix that one area, then rerun the score. Most businesses can move a band with focused work on a single input.
Yes. Readiness is necessary but not enough. Adoption, ownership and maintenance still decide success.
A high score means the conditions are right. It does not mean the project will run itself. Name an owner and an acceptance test before you build.
Rescore when you change systems, add a major source type or prepare a new AI use case.
A quarterly cadence is sensible for a business actively deploying AI. For a first project, score once at the start and again after the source and permission work is done.
Paloren provides AI implementation and training. This calculator uses illustrative inputs and the formulas shown here, not client results or a service quotation. Explore Paloren services.
A company brain is one searchable place for your documents, decisions and answers, with sources and access rules kept. Paloren builds these inside the systems you already run, priced from $60k over 8 to 12 weeks.
Sources carry the highest weight because a company brain is only as good as what it can reach. If the brain cannot get to the documents and systems your team actually uses, nothing else in the score matters. Source coverage is where readiness starts.
A medium band, 40 to 69, means the plumbing is partly there but at least one input is blocking. The usual next step is a readiness assessment, from $8k over 2 to 3 weeks, to find the blocking gap before any build.
Yes. The score measures readiness inputs, not ownership. A high score with no named owner for the system on Monday is how projects get abandoned.
Rescore after any change to your systems, permissions or team structure, and at least every six months. The score is an estimate from your own figures, so treat it as a snapshot of today, not a formal evaluation of your business.
Talk through the result with Paloren. Bring the workflow, the assumptions and the questions this opened up.
Talk to Paloren
A number is a starting position. The next step is a decision you can defend.
Talk to Paloren