Skip to content
← All services

04 / Service

Company brain

An organisational redesign rather than a search box. We turn the knowledge trapped in inboxes, drives and people's heads into a system the whole business can query, act on and trust.

Format
Staged program
Duration
3 - 6 months
Best for
Companies where the answer exists but nobody can find it in time

You leave with

  • One place the business asks first
  • Answers that cite their source
  • Knowledge that outlives the people who hold it

The problem is not storage

Your company already knows the answer. Someone answered this exact question in a thread eighteen months ago. The scope note, the pricing precedent and the reason you walked away from that client in 2023 all exist.

None of it is findable at the moment somebody needs it. So the work gets redone, or worse, decided fresh with less information than the company already has.

That is a structural problem rather than a document management problem, and it gets worse as you grow.

What we build

A retrieval layer over the systems you already run, so that a question asked in plain language returns an answer with citations you can click through to the original.

Then, selectively, agents on top: a small number of tasks where the brain acts rather than only answers. Drafting the scope from three precedents. Flagging the contract clause that differs from your standard. Assembling the tender response skeleton from the last four you won.

We are deliberately conservative about which tasks get an agent. Most of the value is in retrieval, and most of the risk is in action.

The organisational half

This is the part that gets skipped and it is the part that decides whether the thing is still in use next year.

Ownership. Every knowledge domain gets one named human rather than a committee.

Curation. Someone decides what is canonical and what is a draft. Without that distinction the brain confidently returns superseded pricing.

Review. Monthly, someone reads the questions that got bad answers. That list is the highest value document in the program and almost nobody reads it.

Habit. People have to be shown that asking the brain first is faster than asking a colleague. That is a change management problem, and we treat it as one.

Why we call it a redesign

Because when a company can reliably ask itself what it knows, other things change. Onboarding shortens. Decisions get made lower in the org chart because the context is available lower in the org chart. The dependency on a handful of long tenured people softens.

Those second order effects are the actual return.

Questions

Is this a chatbot?

A chat interface is usually part of it, and it is the least interesting part. The work is in retrieval quality, permissions, freshness and the operating model that stops it rotting six months in.

Do we have to move our data somewhere new?

No. We index in place against the systems you already run. Migrations are their own project and bundling one into this is how these programs die.

How do you handle confidential material?

The permission model mirrors your existing access controls. A person sees through the brain exactly what they could see directly. Sensitive classes can be excluded outright.

What stops it going stale?

A named owner per knowledge domain, a freshness signal on every source, and a monthly review of the questions that got poor answers. Without that operating layer it decays, which is the most common failure mode we are called in to fix.

Next step

We map where your hours go and price the work that is worth automating.