Boring Magic

Company Wiki

A wiki your AI writes, keeps current, and builds from.

Most AI setups re-read your raw documents every time you ask, and start from nothing every time. We build the opposite: a company wiki your AI compiles once — every client, product, price and decision — and keeps current as the business moves.

Your team and your automations read from it, so they finally know your business. And your design skills build from it, so a deck or a campaign arrives with the right context and your brand already in.

The idea

Compiled once and kept current, not worked out again on every question.

The pattern comes from Andrej Karpathy’s LLM Wiki. Instead of searching raw documents each time someone asks, the AI builds and maintains a wiki that sits between your team and your sources. In his words, “the wiki is a persistent, compounding artifact.”

People abandon wikis because of the upkeep. As Karpathy puts it, “the tedious part of maintaining a knowledge base is not the reading or the thinking — it’s the bookkeeping.” Bookkeeping is exactly what the AI is good at. Your team decides what matters and asks good questions. The AI does the rest.

How it is built

Three layers, each with one job.

01

Sources

Calls, CRM notes, docs, briefs and results, read from the tools they already live in. Never edited, so every claim can be traced back.

02

The wiki

Pages the AI writes and owns: one per client, product and competitor, plus your pricing, your decisions and each rep’s voice. Cross-linked, with the source attached.

03

The rules

One file that sets what goes on each page, which source wins when two disagree, and how your team words things. Your team owns it; the AI follows it.

How it stays current

Three routines, run by the AI.

IngestQueryLint

  1. 01

    Ingest

    A call ends or a deal moves, and the AI reads it, updates that client’s page and every page it touches, and logs what changed.

  2. 02

    Query

    Your team, your AI and your automations ask the wiki, not the raw files. Answers come back with the source attached, and good answers are filed back as new pages.

  3. 03

    Lint

    A regular health check for contradictions, outdated claims, pages nothing links to and gaps worth filling, so the wiki does not rot the way a shared drive does.

What it builds

Your wiki plus your brand builds the assets.

This is where the wiki pays for itself. Your design skills read the wiki for what to say and your brand system for how it should look, so every deck, campaign and page starts from what the business actually knows.

Request

Renewal deck for Northwind, 6 slides. Lead with what changed since they signed.

Skill · Pitch deck v3

  • Read Northwind’s wiki page and last three calls
  • Applied the master template and slide layouts
  • Checked type, colour and tone against the brand
  • Cited every figure to its source in the wiki

Output · 6 slides

On brand
01

Northwind, a year in

02

What changed since you signed

03

Hours back per week

04

Where it is used most

05

What we would do next

06

Renewal terms

A sales deck, from one line of request

The skill reads the client’s wiki page and last three calls, lays it into your template, and cites every figure to its source before anyone sees it.

Campaign kit · one brief

3 sizes

Stop answering the same question twice.

See how

1:1

Stop answering the same question twice.

See how

4:5

Stop answering the same question twice.

See how

1.91:1

A campaign, every placement

The message comes from the wiki’s product and customer pages; the kit renders it at each size a channel needs.

Tone check

  • Unlock the power of AI-driven insights.

    Answers from your own wiki, with the source attached.

  • Trusted by leading companies worldwide.

    Northwind cut onboarding questions by two thirds.

ToneFigures sourced1 claim needs a source

In your voice, not the model’s

Copy is checked against the house tone kept in the wiki. Anything it cannot source is flagged rather than invented.

Design skills

The wiki is what makes the design skills good.

A design skill without the wiki produces your layout with placeholder copy. With it, a sales deck, a one-pager, a campaign kit or a landing page arrives already carrying the right client, product and numbers.

“New hires stopped asking where things live. They just ask.”

Head of Operations · B2B SaaS

The distinction

Why this is not another wiki.

  • A normal wiki depends on someone updating it.

    This one is written and maintained by the AI from your sources, so it stays current without anyone remembering to.

  • Searching raw files starts from zero every time.

    The wiki is compiled once and kept current, so an answer builds on everything already worked out instead of re-deriving it.

  • A search box returns a reading task.

    An answer comes back with the source attached, so you can check it in one click instead of opening six tabs.

What we deliver

Built inside your accounts, owned by you.

  • A company wiki compiled from what you already have: a page for every client, product and decision
  • The rules file that sets its structure, written with your team
  • Ingest from the tools your knowledge lives in, plus a regular lint pass, so it stays current on its own
  • Permissions inherited from your existing rules — people see what they were already allowed to see
  • Your design skills wired to it, so assets build from the wiki from day one

It is plain Markdown in your own accounts. Nothing gets copied somewhere you cannot revoke, and nothing locks you in.

Questions

The questions buyers actually ask.

Direct answers for teams deciding whether a company wiki belongs on the shortlist.

Is this Karpathy’s LLM Wiki?

It is built on that pattern — sources, a wiki the AI maintains, and a rules file — applied to a business rather than a personal research project. We add the connections to your tools, permissions, and the design skills that build from it.

Do we have to move everything into a new tool?

No. Your sources stay where they are. The AI reads from them and writes the wiki alongside, so there is no migration to finish.

How does it stay current?

Ingest runs when something changes at the source — a call, a deal, a doc — and a regular lint pass catches contradictions and outdated claims. Nobody has to maintain a second copy.

What stops it being wrong?

Every page cites its sources, and sources are never edited, so a claim is checkable in one click. Where two sources disagree, the rules file decides which one wins.

How does it help with design?

Your design skills read the wiki for what to say and your brand system for how it looks. That is why a deck arrives with the client’s real history in it rather than placeholder copy.

Does our data stay ours?

Yes. The wiki is plain Markdown inside your accounts and your permissions. Nothing gets copied somewhere you cannot revoke.

Where do we start?

With the audit. We map where your knowledge lives, what people keep asking for, and which assets you would build from it first, then hand you a sequenced 30-day plan.

How it starts

Make the call. Watch the magic happen.

No packages before we understand the problem. Three steps from the first call to work in market.

  1. 01

    Book a strategy call

    Tell us where growth is stuck. We look at your site, your search presence and your stack before we speak, so the call starts somewhere useful.

  2. 02

    Get your 30-day plan

    What to fix first across your website, marketing and AI, and what to leave alone. The plan is yours whether or not we build it.

  3. 03

    We get to work

    Site, campaigns and automations built and run inside your accounts, with reporting on what moved and what we will do next.

Book a strategy call

One reply within a business day, from a person.