Second Brain for Founders: Run Your Company From Notes AI Reads
A second brain for founders holds what only the founder knows: why decisions were made, what customers actually said, and how the offer has changed. Kept as plain files, it lets AI draft updates, briefs and hiring docs from your own record instead of from guesses.
Founder of The Viable Edge, with 20+ years of experience helping businesses build competitive advantage through strategic transformation. Expert in AI-era business strategy and systematic implementation.
Published · Updated
A second brain for founders is one note system for the things only you know: decisions and why you made them, what customers said in their own words, your offer and positioning, and the lessons from each week. Kept as plain files an AI tool can read, it lets AI draft investor updates, briefs and hiring docs from your record.
Free: the Second Brain Starter Kit
Seven plain markdown files to set one up this week, in Obsidian or any editor, with Claude or any AI.
No spam, ever
Unsubscribe anytime
What is a second brain for founders?
It is one place for the knowledge that lives only in your head: why you priced the offer the way you did, what the last ten customers said, which channel you dropped, and what you decided on Monday. Written down in plain files, that knowledge stops depending on your memory and becomes something AI and your team can use.
The idea comes from Tiago Forte's second brain method, built for knowledge workers managing their own notes. A founder has the same problem with higher stakes. You are the company's memory. Every question about pricing, positioning or a past customer routes through you, and the answers are scattered across email, call recordings, Slack and your head.
A founder's second brain is narrower than a full personal knowledge system. It does not need your reading notes or recipes. It needs the operating record of the business: decisions, customers, the offer, and what you learned this week.
What should a founder put in a second brain first?
Start with four files or folders: a decision log, customer conversation notes, a one-page description of your offer and who it is for, and a weekly review. Those four answer most of the questions people ask you, and most of what AI needs to write in your voice. Add anything else only after these hold for a month.
What to capture
Why it matters
Example entry
Decision log
The reason is what you forget first
"Nov 3: dropped the monthly plan. Churn at month two was 40%; annual buyers stayed."
Customer notes
Their words become your copy and your roadmap
"Call with a clinic owner: 'I don't need more leads, I need the ones I have to show up.'"
Offer and positioning
One source for every page, pitch and brief
Who it is for, the problem, the promise, the price, what it is not
Weekly review
Turns a busy week into a lesson you keep
What moved, what stalled, one thing to change next week
If you already run projects in folders, these slot into the PARA method: the offer and customers are Areas, launches and hires are Projects, and last year's experiments go to Archive.
How do you keep a decision log as a founder?
Write one short entry per decision: the date, what you decided, the reason, what you expected to happen, and when you will check. Three to five lines is enough. Add the result when the check date arrives. After a few months the log shows which calls held up, and AI can answer "why did we do that?" for you.
A template that takes under two minutes to fill:
Date and decision: "2026-11-03: move onboarding from calls to a recorded walkthrough."
Why: the evidence you had, in one or two sentences.
Expected result: what you think will change, with a number if you have one.
Check on: a date. When it arrives, add what happened.
The check date is the part most founders skip, and it is the part that makes the log useful. Without it you keep a diary. With it you have a record of which instincts to trust.
Free download
Start with the Second Brain Starter Kit
The capture inbox, note template, source log, weekly checklist, connect-your-AI guide and retrieval self-test, as plain markdown files that work in Obsidian or any editor, with Claude or any AI. Enter your email and the download starts.
No spam, ever
Unsubscribe anytime
How do founders use AI with a second brain?
Point an AI tool at the folder and ask it to draft from your record: the monthly investor update from the decision log and weekly reviews, a sales brief from customer notes, a job description from the offer page and role notes. The AI writes from what you know, so you edit a draft instead of explaining the company again.
Prompts that work with a founder's folder:
"Draft this month's update from the decision log and the last four weekly reviews. Name the note behind each claim."
"From the customer notes, list the five phrases customers use for the problem, with how many calls each came from."
"Which decisions in the log have a check date that has passed with no result recorded?"
Ask for the source note every time. It is how you catch an answer the AI filled in from general knowledge instead of your files, and our retrieval test shows a fast way to check. The setup we use, with Claude Code reading an Obsidian folder, is in our Claude Code and Obsidian second brain guide.
What is the best second brain app for founders?
A folder of plain markdown files, opened in Obsidian or any editor, is the best fit for most founders. The files belong to you, not a vendor, every AI tool can read them, and they move into a shared company knowledge base as is. Notion works if your team already lives there, but check what its AI can actually read.
The deciding question for a founder is what happens when you hire. Notes in plain files can be copied into a shared repository on day one. Notes locked in one app depend on that app's sharing model and its AI. We compare the main options on that question in the best second brain apps, and the trade-offs of the most common team tool in how to build a Notion second brain.
For a ready setup, the free Obsidian second brain template gives you the folders, a note template and a CLAUDE.md file in one download.
How much time does a founder second brain take to keep up?
About fifteen minutes a day and thirty minutes on Friday. Log decisions as you make them, paste customer quotes right after calls, and do the weekly review at the end of the week. AI can file the inbox and draft the review from the week's notes, so your time goes to judgment, not sorting.
The habit fails when capture is slow. Keep one inbox note open all day and drop everything into it: a quote, a decision, a number. Once a day, ask AI to sort the inbox into the right files and flag anything that looks like a decision without a reason. If filing is the step that keeps slipping, the low-maintenance setup in our second brain for ADHD guide works for busy founders too.
What decays is the offer page and old customer notes. Our guide to keeping a knowledge base up to date covers the review cadence that stops stale facts from leaking into AI drafts.
How is a founder second brain different from a company knowledge base?
A founder second brain is personal and starts on day one: your decisions, your customer calls, your thinking. A company knowledge base is shared and starts when other people need answers without asking you. Build the first well and it becomes the second. Your offer page, customer notes and decision log are the first files a new hire reads.
When the company grows past you, the shared layer has different needs: owners for each page, a review schedule, and access for agents that do real work. That is the subject of the AI second brain for business and our guide to a company knowledge base. For the full build, from the first folder to connecting an AI tool, follow our guide to building an AI second brain.
For consultants and service providers
Build second brains for clients
Build and Deliver Professional Second Brains is a self-paced course on doing this for other people: scoping the engagement, building a knowledge base from a client's real material, testing retrieval, and handing it over, with a working knowledge base kit to build with. Plain files, no coding, no vector database.
