Icarus GrowthFoundational Implementations

AI / 01 of 08

Second Brain Systems

Turn your intellectual property, notes, online content, branding, and all written business assets into an easy referencing system for your AI agents.

How it runs

New decisions written back · a loop, not a migration

Sources

Docs, Slack, calls, site, brand

Ingest

Triage on keep-bar, drop dupes

Atomise

One idea per note, slug + tags

Link

Wiki-links into topical maps

continues

Agent reads

Any prompt, grounded answer

What it is

A second brain is one linked vault of what your business already decided (offers, pricing, positioning, SOPs, client history, brand rules), sitting somewhere an agent can read before it answers.

You need this if every prompt starts with ten minutes of re-explaining the business and the output still comes back generic: that's a retrieval problem, not a model problem.

You pay that tax on every task, by every person, forever.

If AI already does real work for you, the same prompt now returns your pricing logic and client history unprompted.

The actual build

Second Brain Systems — the as-built system.

What it does for you

01

Every agent, prompt and team member answers from the same source

so nobody re-derives a decision the business already made.

02

The re-briefing tax disappears and output goes from generic to on-brand with no extra instruction

03

Knowledge that lived in two people's heads becomes an asset that survives them leaving

Built and running

Built internally for the business. The vault runs to 877 linked notes, and no content, sales or build work starts without it being read first.

How to build it

  1. Start with a folder of markdown files rather than a tool, one idea per file
  2. Title each file as a claim rather than a topic ("Price the delta, not the deliverable") with a few sentences of prose underneath
  3. Link every note to two or three neighbours so the vault becomes a graph rather than a pile
  4. Build a map-of-content file per topic listing its notes, and an index listing the maps
  5. Point your agent at the folder and make the first instruction of every prompt: read the index, then the relevant map, then answer
  6. Write back to it after every decision, because the vault only earns its keep once that's a habit rather than a project

Want this one built into your business?

Thirty minutes, no deck. We map what you run today and tell you what it would take.

Book a call →