Over the past several weeks, I’ve had many conversations about “second brains.” Some people are building sophisticated systems. Some are tinkering with a few tools. Others have just heard the term and are trying to understand what it means.
The term makes it sound like the first brain could use a little backup. Fair enough. It can remember every word of a song you haven’t heard in 20 years, while the details of yesterday’s customer conversation are already getting fuzzy. Giving those useful details somewhere else to live starts to sound reasonable.
For a small business owner, though, a new system can sound suspiciously like hiring someone who creates more work. But getting started can be much simpler. You may already have much of the information you need.
AI can help put that knowledge to work. With access to your business information, an assistant can help answer recurring questions, prepare for customer conversations, and find connections across what you’ve already learned. With the right setup, it can also carry out tasks and help keep that knowledge current as your business changes.
I thought it would be helpful to share my perspective without turning one newsletter into a small textbook. So we’ll take it in three parts:
- Getting started—our focus here: What a second brain means, why it matters when using AI, and how to begin with information you already have.
- Adding AI: Practical examples of using business knowledge to prepare for client conversations, answer recurring questions, and carry out tasks, with the right checks.
- Keeping it useful: Choosing tools, maintaining the information, and introducing automation without creating another job.
What a second brain actually is
“Second brain” is a fancy way of saying you keep useful information somewhere you can find it, connect it to other ideas, and use it again, without having to remember everything yourself.
That might include proposals, customer conversations, the reasoning behind decisions, lessons from completed projects, or research and ideas you’re still working through.
The underlying practice has a long history in notebooks, files, and reference collections. Author Tiago Forte helped popularize the modern approach through Building a Second Brain. His introductory guide describes capturing useful information, organizing it around your work, distilling what matters, and putting it to use.
You can begin with a folder, a notes app, or a shared workspace. The important part is being able to use the information you’ve kept.
AI doesn’t automatically know what your business offers, how you handle a particular situation, or why you made a decision. That information has to come from somewhere. Giving an assistant access to the records in your second brain provides those details, so it can draw on what your business already knows when helping with the next question or task.
You spend less time supplying the background from scratch, and the answers can reflect how your business actually works.
When the answer keeps coming back to you
Consider a few familiar questions:
- What did we include in the last proposal for this kind of work?
- Why did we change that process?
- What did we agree to do after the last customer meeting?
This happens in organizations of every size. Often, one person remembers why an exception was made, what a customer needed, or what went wrong last time. Finding the document gets you part of the way there. Understanding the circumstances may still require finding that person and “picking their brain.”
In a small business, the owner is often plugged into almost everything. You hold a lot of the context because you’ve had a hand in so many decisions. Questions come at you from across the business, each requiring you to switch hats, explain the background, and then remember what you were doing before the interruption.
For a solo professional, you play both roles: the person looking for the answer and the person who was supposed to remember it. You return to a project after a few weeks and have to reconstruct what you decided and where you left off.
Recording that context makes it available to colleagues and assistants helping with the work.
What my experiments taught me
I’ve experimented with several ways of building my own second brain. Some failed miserably. A few were particularly good at giving my first brain more things to manage.
Over time, I’ve learned that simple works best for me. I want to find and connect useful information. If I’m spending more time looking after the system than using it, I’ve probably gotten carried away.
I landed on Obsidian, a note-taking app that lets me link notes and see their connections as a visual map. As a visual thinker, that helps me explore how different AI use cases relate or how ideas might come together for an article. We’ll look at specific tools and how to choose what fits your work in the third article.
One mistake I made was keeping the same information in more than one place. Update one copy and overlook another, and suddenly the answer depends on which version you open. You end up checking dates and comparing details. On a team, people may quote different prices or follow different instructions. Working alone, you get to argue with an earlier version of yourself.
The lesson was straightforward: be clear about where information belongs. If information already has a useful home, I can link to it and add whatever context helps. I don’t need another copy to look after. I have enough things that require supervision.
Getting ready for AI starts with the information
Those conflicting versions become a problem for an AI assistant, too. If it can access two service descriptions and neither is identified as current, it may produce a beautifully written answer based on the wrong one. Now you have the same confusion, with better punctuation.
Getting value from AI takes some preparation. In a 2026 PwC survey, 56% of CEOs reported they hadn’t yet seen significant financial benefits from AI. Many factors can make an investment disappointing, but the information an assistant has to work with deserves attention.
Even businesses with substantial resources struggle here. A 2025 survey commissioned by data-software company Qlik found that 81% of 500 data and analytics professionals at large U.S. companies reported significant data-quality issues. Apparently, a bigger budget doesn’t automatically settle which version of the document is correct.
This is where building a second brain becomes part of getting ready for AI. You identify the knowledge you repeatedly need, establish where the current information belongs, and keep the important context alongside it.
You don’t need to organize every forgotten folder in the business before putting this to use. Build your second brain around one recurring piece of work, with information you and an AI assistant can draw on. A good starting point is something you’d be delighted to stop explaining quite so often.
Start with a question you’re tired of answering
Perhaps people keep asking what a particular service includes or how it works. You’ve explained it in emails, discussed it with your team, and answered it on calls. At this point, you’re considering recording yourself.
Those explanations are useful knowledge you already have. Bringing the clearest, current answers together gives you something to reuse—and gives an AI assistant the background it needs to help with the next question.
Here’s a manageable way to get started.
1. Pick one recurring issue
For this example: “What does our standard service include, and how do we explain it?”
Choose something that comes up often enough to be worth addressing. The aim is to help someone answer consistently without repeatedly checking with you or, if you work alone, hunting through old emails.
2. Find the good answers you already have
Look for your current service description, an existing FAQ, and previous explanations that were particularly clear. Include useful reasoning, such as why a boundary exists or why a past exception shouldn’t be treated as standard practice.
Choose material that reflects how the service works today.
3. Give the information a dependable home
Use an existing page, document, or note as the starting point. Link to the current details where they already live, and add explanations where something is missing.
“Service name — common questions” is a perfectly respectable title. This part doesn’t need a branding exercise.
4. Add what someone would still need to ask you
Explain common misunderstandings, the usual response, and when someone needs to check before making a commitment. Keep unresolved questions visible.
A few clear answers and examples can help both a person and an AI assistant interpret the information correctly.
5. Reuse it and improve the shared answer
Use the reference during a call, when preparing a customer reply, or when helping a colleague. If something is unclear, improve that same reference. When the service changes, update the information where it belongs.
The same knowledge can support many conversations. Each new customer doesn’t require another document.
Where AI can take it
A second brain becomes much more powerful when an AI assistant can use that knowledge to take action.
The knowledge gives it context: what your business offers, how you handle common situations, what’s been agreed, and which decisions need your involvement. Connections to tools—such as email, your calendar, or your customer management system—give the assistant ways to do something with that context.
Take our service example a step further. With those connections in place, an assistant could read an incoming inquiry, check your current service information, respond within rules you’ve established, and record the interaction in your customer system. If the request falls outside those rules, it brings the question to you with the relevant background.
That’s recurring work getting done while you attend to the other seven jobs that apparently came with owning the business.
As the assistant completes tasks, it can also record what happened, carry forward useful context, and help maintain the knowledge it relies on. A clarification you provide can become guidance for similar situations. Connected workflows can turn that guidance into action across several tools.
With dependable information and demonstrated results, you can give the assistant more responsibility. You decide what it can do independently, what needs approval, and how you check its work.
That small service reference can become part of a system that handles meaningful work for you.
You don’t need to build all of that on day one. But it helps to understand what you’re building toward. In article two, we’ll explore what increasingly capable assistance can look like in practice. In article three, we’ll cover the tools, maintenance, and controls that help it work reliably.
Let’s get some recurring work off your plate.
If you can see the potential here but could use help making it work in your business, I can help.
At Tether, we help owner-led businesses and solo professionals identify useful ways to apply AI and put them into practice. We can start with an AI Quick Wins Assessment to identify real opportunities.
You don’t need to arrive with a plan or a preferred tool. Bring one task you keep repeating or one issue that keeps coming back to you. We’ll talk through what could be handed over, what needs your judgment, and how I can help you get there.
Book a conversation

