Done-with-you install week

Build the first usable Company Brain with Marc in the room.

A focused 5-day working week for operators who already know the first proof area and want help turning scattered company context into a working brain: structure, source boundaries, starter documents, access plan, and live use cases.

This is more hands-on than the Audit and narrower than the Sprint. We install one proof area with you; we do not diagnose the whole company or build the full rollout.

From £2,500 · 5-day done-with-you install week · Best after the kit or audit when one team is ready.

Use Build Week when the first build is clear, but DIY will stall.

You already understand the Company Brain model and know the first team or operating loop.

You have one operator, AI lead, COO, founder, or team owner ready to work during the week.

You want hands-on installation for one proof area, not a company-wide rollout yet.

You do not need leadership diagnosis; you need the first usable version built with you.

Not for

This is not a cheaper Sprint or a generic workshop.

  • ×A broad AI training session.
  • ×Prompt coaching without changing how company context works.
  • ×A vendor to automate random workflows without fixing the context layer.
  • ×A lower-friction diagnostic — if the first build is politically unclear, start with the Audit.

What gets built

A first brain, one owner, one proof area.

A first Company Brain structure in your own repo or workspace.

The first approved context pack for one team, function, or operating loop.

Source-system boundaries: what goes in the brain, what stays live, and what should never be ingested.

Starter skills and instructions your agents can use.

A tool and access plan for Claude, ChatGPT, Cursor, Copilot, Slack, or your chosen runtime.

Two or three tested use cases that prove whether the brain is useful.

A clear recommendation: keep building internally, move to an Audit, or plan a full Sprint.

How the week runs

Day 1

Map the operating reality

Pick the first team or operating loop, map the context people keep re-explaining, and agree the source boundaries.

Day 2

Build the first brain structure

Create the initial repo or workspace, add the core documents, and assign owners, sources, dates, and review rules.

Day 3

Turn raw knowledge into usable context

Curate the first decisions, workflows, meeting notes, product context, customer rules, or repo knowledge into agent-readable documents.

Day 4

Connect and test

Connect the brain to the tools your team already uses and test it through real prompts or agent workflows.

Day 5

Tighten and hand over

Fix gaps, define write-back rules, and leave with the next 30 days of build priorities.

Want help installing the first version?

If the kit is useful but you know it will not happen without a working session, Build Week is the done-with-you path. We keep the scope tight: one brain, one owner, one first proof area.

Book a 20-minute call →