Skip to content
All field notes

Build a company second brain your team can actually use

Turn approved client information into sourced briefs and clearer handoffs—with a small knowledge-base pilot and visible human review.

In this article

Your team should not have to search five conversations to discover what a client approved. An AI-assisted knowledge base can help, provided the sources, decisions and ownership stay clear. Start with one client and one recurring question.

A company second brain in plain language

A second brain is an organized collection of information you can return to. Add an AI assistant and it can help you find, connect and draft from that information. The useful outcome is a better answer to a work question: what did the client approve, why did we choose this message, or what should the next person know?

Karpathy’s LLM Wiki describes an AI-maintained knowledge base with preserved source material, linked pages and rules for maintaining them. That is a useful reference pattern. It does not establish that the separate Obsidian, Opus 5.5 and Jev stack in the viral post is his endorsed setup.

Start with one client question

Choose one recurring question before importing a large archive. For example: “What is approved for this client’s launch?” Gather a permitted brief, the current offer, the brand guide and the decision notes. Date each source and record who approved it.

Keep unrelated clients separate. If a source contains private customer information, use an approved environment and the minimum information needed. A local notes application does not mean every AI integration keeps its processing local.

Use four clear places for the work

For a first pilot, create folders called Sources, Working summaries, Decisions and Drafts. Sources holds the original material. Working summaries holds editable explanations with links back to evidence. Decisions records what was approved and by whom. Drafts holds proposed emails, briefs and other deliverables.

This is our suggested team adaptation. A summary is allowed to change; the original source should remain available. When two notes conflict, record the conflict and ask the owner. Do not let the assistant silently turn the newer-looking sentence into company policy.

Know what each tool would do

Obsidian provides a local Markdown workspace. Claude Opus 5.5 is an available Anthropic model for knowledge and coding work. TypeSafe documents Jev as a model for structured decisions. In a custom knowledge workflow, it could help select or rank material before a writing assistant uses it.

You still need an integration that connects those roles. Installing three products does not create a running workflow. Start with manual selection and one assistant; introduce another component only if your evaluation exposes a specific retrieval problem. We have not benchmarked the viral configuration.

Ask for a brief with evidence attached

A fictional agency example: a client’s older positioning document says “lowest price,” while the current brief says “specialist support.” Ask the assistant to show both sources and flag the unresolved message. The launch owner chooses what the team can claim. A confident blend of the two is not an acceptable substitute.

Using only this client’s approved sources, draft a launch brief. For every decision, include the source filename and date. List conflicting or outdated guidance separately. Mark unanswered questions. Propose knowledge-base changes in a separate list for review. Do not overwrite sources or publish the brief.

Review the knowledge base as well as the output

Test five questions whose answers you know. Include an old decision, a contradiction, a question with no answer and a question that belongs to a different client. Check whether the assistant cites the right passage, acknowledges missing evidence and stays within the permitted material.

Keep a record of proposed edits and a way to restore an earlier version. Assign an owner to retire stale guidance and review updates. If you later schedule the workflow, define when it runs, its spending limit, how failures are reported and which changes need approval.

Measure whether a teammate can prepare a trustworthy brief with less searching and correction. That is a more useful result than the number of notes imported. Bring one knowledge handoff to Waymaker Agency to scope a focused pilot.

Sources and editorial note

Sources checked October 23, 2026. The exercises below are original editorial recommendations, not measured product results.

Want this applied to your business? The Growth Fix is one fixed-price session to find where your customers drop off and fix the part that matters most.

Ashley Kays

Ashley Kays

Founder

Founder of Waymaker. BigCo veteran (NCR, Walt Disney World, Wyndham Worldwide) turned solo operator. Building the operating layer above AI building tools.

More field notes