AI sounds like everybody else because it knows your industry but it hasn't lived your life. It can be accurate, clean, and on topic and still leave you feeling nothing, because it's missing the one ingredient nobody can copy: your stories. A story bank fixes that. It's six categories of stories (Origin, Client Wins, Lessons Learned, Behind The Scenes, Values In Action, and Industry Perspectives), each captured as a five-line card (Title, Summary, Lesson, Emotion, Best Content Types) that AI can actually retrieve and use. Build it once with a 30-day team sprint, point your AI at it on purpose, and your content stops sounding like the assembly line and starts sounding like your team. That's the unfair advantage, because AI can write about concepts, but it can't write about what your humans have lived.
That's the build we walked through in Session 5 of our free 8-part series, Building Your AI Content System. The full 42-minute replay is up top. Hit play, or keep reading for the recap.
Why Does AI Content Sound Like Everybody Else's?
AI content sounds generic because AI knows a lot about your industry and your audience, but it has never lived your life, your business life, or your team's life.
Think about something your team made with AI in the last year or two. It was accurate. It might even have been clean. It was definitely on topic. And it still felt like nobody actually wrote it. No soul. No connection to a human. That's what people mean when they complain about AI slop, and it isn't really a tool problem.
It can be accurate. It can be on topic. It can feel clean, but it doesn't make you feel anything.
The gap is everything your team has lived that the model has never seen. When a project blew up. When you had a big win. When you went through a mindset shift, or rewrote your mission and vision and the new version actually meant something. AI hasn't lived any of that, so it can't write from it. Close that gap and the same model that was writing cardboard starts writing like you.
Every piece of content that earns trust does it with three ingredients, and the Greeks named them a couple thousand years ago. Logos is the logic: the data, the facts, the stats, the part that makes sense. Ethos is credibility: authority and experience, the part that says this team clearly knows their stuff. Pathos is emotion: story and connection, the part that says this team actually gets me. And here's what most teams miss.
It'll give you facts all day, but it can't give you feeling.
Most AI output is heavy on logos, a little ethos, and almost completely missing the third ingredient. Feelings come from human moments, and AI doesn't have yours yet. Blend all three and your content earns trust before the transaction instead of reading like a transaction. At Sidekick Strategies we spent years making HubSpot work for humans. This is the same instinct pointed at a new target: making your content sound human even when AI helped write it.
What Are The Six Story Categories Every Business Needs?
The six story categories are Origin, Client Wins, Lessons Learned, Behind The Scenes, Values In Action, and Industry Perspectives. Those are the six buckets your whole team can start filling, whether you're a solo operator or a group of six.
Walk each one with George's framing.
Origin: Why You Started
This is how your company started and why you do what you do, and it goes deeper than your About page, because most About pages just aren't rich enough for this. The moment, the spark, the problem somebody got so fed up with that they decided to build a fix. Origin stories answer the question every prospect is silently asking: why should I trust this team over the other five, seven, or ten options in my feed? Don't write the press-release version. Write the it-was-late-night-and-I-was-seven-hours-deep-and-frustrated version. There might be several origin stories from several people at different angles. Capture them all.
Client Wins: Proof, Not Bragging
These are the results your team helped real humans achieve, which is to say case studies, with one important fix on the framing. The wrong frame is "look how amazing we are." The right frame is "here's what's possible for someone like you." When you tell the story of a specific human who was stuck and what changed for them after working with your team, that's not a brag, that's proof, and proof is pure ethos. Case studies used to take months. With AI in the loop and your wins in the bank, they get easier to produce over time. Keep them two places at once: inside your story bank, and in an accessible case-study library your AI can reach when you say "go look at the case study where we helped these humans do this thing."
Lessons Learned: What Life Has Taught You
George's favorite category, and it's your failures, except he doesn't call them failures. He calls them what life has taught me. The project that went sideways. The strategy you were sure about that flopped. Most teams hide these. That's backwards. Admit the stumble, then teach the lesson that came out of it, and your audience thinks: these are honest humans, and I like working with honest humans. You're not pretending you had it all figured out. You're showing the messy middle, except you're 17 levels further down the road than the human reading it.
Behind The Scenes: How You Work When Nobody's Watching
This is how your team actually operates when nobody's looking: the good stuff, the fun stuff, the messy middle. The epiphany stuck in a Slack thread. The whiteboard session you rewrote four times. The little rituals that make your team your team. George once told a webinar audience he doesn't do hot takes because nobody cares what he thinks, only what he knows, and the chat lit up to say they wanted to hear what he thinks. There are humans behind the logo. Behind-the-scenes stories are the oxygen audiences aren't getting anywhere else, and they turn a faceless brand into humans who care.
Values In Action: Beliefs That Cost You Something
Every company has a values page, and most readers don't believe a word of it, because anybody can type "integrity" onto a page. What people believe is values lived out in a specific moment when it cost you something. The time you refunded a client you didn't have to. The time you told a prospect honestly, "we're not a good fit for you, and you're not a good fit for us." Those moments show what you actually believe louder than any values page ever could. Don't tell. Show.
Industry Perspectives: Your Contrarian Take
This is your team's point of view on your industry, especially where you disagree with the crowd. Not disagreement for its own sake, but the contrarian take your values actually plant you on and you'll defend. The thing everyone in your space does that you think is dead wrong. The trend everyone's hyping that you're quietly skeptical about. Unless your real opinion is in the bank, AI writes the neutral, encyclopedia version that sounds like everyone else. Put your point of view in, and it starts sounding like a company that stands for something, which builds the right audience, the one ready to go on the journey with you.
How Do You Structure A Story So AI Can Actually Use It?
You capture each story as a five-element card, and the whole thing fits in about five lines, not five pages.
Five lines, not five pages.
Notice how short George's own stories were when he told them. That's the target. Here are the five elements:
- Title. Make it memorable. Not "Story One." Call it "The Blue Windbreaker" or "The 2 a.m. Almost-Quit," something anyone on your team recognizes instantly.
- Summary. Two or three sentences: the setup, the moment, the outcome.
- Lesson. What does this story teach, in one sentence?
- Emotion. What should the reader feel: inspired, relieved, challenged? Knowing the emotional target helps AI place the story in the right spot. Worth capturing both sides: how the reader should feel, and how you or your founder actually felt in the moment.
- Best Content Types. Where does this belong? Blog intro, LinkedIn post, email, sales call, all of the above?
Here's one of George's own as a finished entry, so you can see it click together. Title: The Blue Windbreaker. Summary: Showed up to an interview with no portfolio, promised I'd learn InDesign over the weekend, and did exactly that. Lesson: Consistency beats raw talent every time. Emotion: "If he could learn it, I can learn anything too." Best Content Types: origin-story post, anything about hiring or human potential, the opening of a keynote.
That's it. Ninety seconds, maybe two minutes per card. Now multiply that across your team over a few weeks. Pull from interviews, submitted forms, or transcripts of historical meetings you already have sitting around. The cards won't be polished, and they won't win awards. They don't need to. They give AI the nuance, and AI takes the story from there. If you want the AI to tell a story more precisely later, a card can link out to the rich, raw, full version too.
The Live Demo: Inside George's Story Bank
To make it real, George opened his actual system live: the main brain, a second brain he uses to create content.
Inside it, the stories live in a light database with tags for themes and tags for "best for." One card reads "13 Hours From Death On The USS Cunningham," a real story with a short version and a robust version attached, so when George tells the AI to use that story, it knows more about how to tell it. The card is also linked to the podcast transcripts where George originally told it, because the team pulled all 59 episodes of his Beyond Your Default podcast and extracted his personal stories and lessons into cards. Another reads "30 Summers Left," the one where he talks about legacy and why he thinks the way he does. These are just .md files in a system the AI can reach into and grab.
The point isn't the specific tool. The point is that a real, lived, tagged, linked story is sitting somewhere the AI can find it, attached to the identity it belongs to. That's what makes it irreplaceable. Those stories haven't been indexed into the AI yet, because they're yours.
Where Should Your Story Bank Live?
A story bank can live in two main places, and the second is where the magic happens.
The first is a single shared document for the whole team, one source of truth instead of stories scattered across a dozen apps. A lot of humans work inside ChatGPT projects or Claude projects, so an individual document people can drop into a project or a conversation gives everyone instant access to the same stories.
The second is loaded into a system, a workspace where you've built both the brain and the hands for it. The hands are the connectors: the APIs, the MCPs, the CLIs, the words that used to sound nerdy and are now just conversations happening in different places. In that setup the story bank grows on its own. George gets off a call and the system asks: did he tell any stories we don't already have? It finds two, extracts them, and adds them to the bank. The bank compounds because it's part of a content system, not a static file.
Why Won't AI Use Your Stories On Its Own?
AI won't use your stories on its own because having a document available is not the same thing as telling the AI to use it.
This is the historical trap. You upload a beautiful story bank, you feel great, you ask for a blog post, and the AI ignores the whole thing. Why did I give you that context?
Having the document available is not the same thing as telling AI to use it.
The fix is to lead it on purpose. George's rule:
I love serendipity in life, but I do not lean on serendipity in the AI chat.
So he says it out loud: "I've uploaded this document of stories. Pick the most relevant one for what we're about to write." If he already knows the story he wants, he names it. If he doesn't, he hands it the set and lets it choose, which gets more useful when the bank holds 200 or 300 stories instead of 12. That one sentence in your prompt is the difference between content that reads like a robot and content that reads like you. It's the same prompt discipline we covered in Session 4 on the prompt framework: you have to point the AI where you want it to go.
When the system has absorbed enough of your source material, it starts surfacing your own language back to you. George watched his AI use the word "automagical," a word he made up around 2014, without being told to. He's watched it reach for a Salesforce-versus-HubSpot-versus-Zoho take he'd forgotten he wrote two years earlier. His brain forgets. The system's brain has everything. That's when you know it's working: you read the output and think, that's our founder, or, that's me.
AI-Generated Vs AI-Assisted: What's The Difference?
AI-generated content is what you get when you type a line or two into a chatbot and spit out whatever drops. AI-assisted content has a human in the loop from start to finish.
AI-assisted means you bring the idea or the strategy at the beginning, you finesse and feed it the right stories in the middle, and you're constantly fighting the generic, the forgettable, the average. Your stories are in there. Your mindsets, your beliefs, your experiences, your point of view, all in there. Same tool, same model, completely different results.
So when somebody says "AI just isn't that great," the honest read is usually that they haven't taken the time to build the system or make it theirs. That's the entire difference. Together with the identity work from earlier in this series, the story bank is one of the two heaviest levers you have. Identity tells the AI who you are. Stories give it what you've lived.
Your 30-Day Story Bank Sprint
Here's how to build the bank without it turning into a someday list. Run a 30-day sprint, solo or with your team, in four moves.
- Divide and conquer. Assign the six categories across your team. Founder takes Origin and Values In Action. Account folks take Client Wins. Project leads take Behind The Scenes. Strategists take Industry Perspectives. Solo? You're all six roles, and that's fine.
- Make it a 15-minute weekly ritual. Once a week, everyone adds one or two stories to the shared doc using the five-element template. Fifteen minutes, and make it mandatory.
- Hit a starter target of 10 to 12 stories. Roughly two per category. Then declare the bank open and start using it.
- Keep it living. After the starter set, every meeting, every new hire, every internal get-together is a place to mine for the next story. The bank should never stop growing.
Why This Stacks With Everything Else
Here's why all of this matters: it stacks. Across this series you've been building layers, and the story bank is the one that makes the others come alive.
Layer one is identity. Who are you, how do you tick: mindsets, beliefs, and core values on the personal side; mission, vision, voice, and tone on the business side. We built that in Session 2 on your digital identity. Layer two is structure: the system you work inside, whether that's ChatGPT projects, a prompt library, or a full build. Layer three is stories, stacked on top.
Three takeaways to walk away with. First, your stories are your unfair advantage:
AI can write about concepts. It cannot write about what your team has lived. That's the one thing nobody can copy.
Second, logos plus ethos plus pathos equals trust before the transaction.
You've got to get in their head and their heart before you try to get into their wallet.
Most AI output is missing the pathos, and your story bank is what fixes it. Third, AI won't use your stories unless you point it to them. Stack identity, structure, and stories, and it's a genuine game changer. Inspiration without application is just noise. This session was built to get you to move.
Frequently Asked Questions
What Are The Six Story Categories In A Story Bank?
Origin (how and why your company started), Client Wins (specific results for real humans, framed as proof not bragging), Lessons Learned (the projects that flopped and what they taught you), Behind The Scenes (how your team works when nobody's watching), Values In Action (beliefs lived out in a moment that cost you something), and Industry Perspectives (your contrarian take on your space). Aim for two stories per category to start.
How Long Should Each Story Be?
Five lines, not five pages. Each story is a card with five elements: a memorable Title, a two-to-three-sentence Summary (setup, moment, outcome), the one-sentence Lesson, the Emotion you want the reader to feel, and the Best Content Types it fits. Ninety seconds to two minutes per card. It can link out to a longer raw version if you want the AI to tell it more precisely later.
Why Does AI Ignore My Story Bank Even After I Upload It?
Because having the document available isn't the same as telling the AI to use it. You have to lead it on purpose: "pull the most relevant story from this bank for what we're writing," or name the specific story you want. Don't lean on serendipity in the chat. That one sentence in your prompt is the difference between robotic output and content that sounds like you.
What's The Difference Between AI-Generated And AI-Assisted Content?
AI-generated is typing a line into a chatbot and publishing whatever comes out. AI-assisted keeps a human in the loop from start to finish: you bring the strategy, feed it your stories and point of view, and fight the generic at every step. Same model, completely different results. The story bank is what makes content AI-assisted instead of AI-generated.
Do I Need A Fancy System To Have A Story Bank?
No. The simplest version is a single shared document your whole team adds to, which anyone can drop into a ChatGPT or Claude project. The advanced version loads the bank into a system with connectors so it can grow on its own. Start with the shared doc and 10 to 12 stories. You can build the bigger system later.
How Do I Get My Whole Team To Actually Contribute?
Run a 30-day sprint. Assign the six categories across the team, make a mandatory 15-minute weekly ritual where everyone adds one or two stories, hit a starter target of 10 to 12, then keep it living by mining every meeting and new hire for the next story.
Your Next Move
Keep going with the free series. Session 5 added the story bank on top of the identity and prompt work that came before it. The free 8-part Building Your AI Content System series keeps building from here, session by session. Explore the full series and grab the next live session.
Catch up on the prior sessions. The story bank stacks on the layers underneath it. Session 1 made the case for why systems beat tools, Session 2 walked through building your digital identity, Session 3 covered setting up your AI partner the right way, and Session 4 broke down the prompt framework that actually works. Watch those and this one clicks even harder.
Go build the real thing. Ready to stop watching and start building? The paid AI Content System training walks you through the whole pipeline, from identity to story bank to publish, with the second-brain layer George demoed live. Want the deeper build behind that layer first? Read Second Brain Mastery: How To Build An Obsidian AI System That Actually Remembers You, then see the paid training.
References: The logos, ethos, and pathos framing comes from Aristotle's three modes of persuasion, the classical foundation behind why content that blends logic, credibility, and emotion earns more trust than content built on facts alone.
