While building my fractional company and this newsletter, I’ve been clear with my audience: I LOVE AI. I feel fortunate that it’s at my fingertips while I launched this portfolio career of mine. Truly couldn’t have seen the success I’ve seen in the last year without the help of these tools.

Last week I sat down drafted, edited, and posted my newsletter. Breathed a sigh of relief. Then went to my Substack notes feed and immediately saw a post from saying Substack rolled out AI detection.

WTF??? My heart dropped. Panic ensued. I hadn’t received any heads-up this was happening. What does this mean? Where does that show up? Who sees that? Can I turn it off? Will I be punished for how I just used AI?

I felt like I was about to be outed as a fraud to my audience. My first thought was far from “Oh wow this is an interesting and helpful feature!” It was “What if my readers assume everything I do is GPT with my name at the top?” That is incredibly uncomfortable when you’ve spent countless hours of energy and heart working to build trust. This complete flip of a belief that you’re not valuable if you use AI was foreign and felt like an attack.

As the dialogue progressed and my nervous system chilled out, I realized I would love to be super open about how I use AI in my work. So I want to take this opportunity to offer a deeper peek behind the curtain into how I use the tools. If you’ve been here a while, you know my brand is transparency and human-first. Even in my LinkedIn banner, I make it clear that I am about human-first, AI-powered systems. I consider this to be a huge benefit to my clients and readers. AI is NOT going anywhere. I strongly believe if you don’t adapt and use it in your practices, you will be left behind. I still believe this after feeling like I was stripped down naked and the Substack lords yelled “Shame” upon me. (God, does being a Game of Thrones fan just age me now?)

Subscribe now

Anyway, I am going to share my process for using AI in my content here. The process is a lot like working with another human in the room, but as a solo, I don’t have that luxury. When I sit down to write my newsletter for the week, there are a couple of ways it goes.

Sometimes I have the fully fleshed-out idea for an article.

Sometimes I have a vague idea of where I want to go with an article

Sometimes I sit down with severe writer’s block and stare at the screen for a hot minute.

Whatever the case, I usually will still have my GPT or Claude (depending on who is on my good side that day) interview me. Ask me about what I am seeing with clients, what’s being talked about in my world, and what I am feeling lately. For this piece of the process, I like using Wispr to speak it out. It feels more natural.

Once I get that out, I outline, draft, rewrite, edit. Then I hand it back to my robot buddy for feedback.

The journalism kid in me despises being called out for grammar issues, so I make sure that it’s checking me on my grammar. (I’m not perfect but damn my brain sure thinks I should be.) If there’s research that I need to do for the piece, I work back and forth with Claude to help me surface that. I still go through and click on the sources and articles that Claude’s giving me to verify because it’s not always accurate. It’s like your well-meaning and hard-working, but still rather young, intern.

Then, at the end of all this, I’ll put it on Substack and do one last pass on it myself. Okay, let’s be real: 10 passes because aren’t we all afraid to commit to clicking the send button only to send something horrifically wrong? (Anyone else previewing all 3 formats a stupid amount of times before send? Anyone??) Eventually, I finally fire away.

The stories, frameworks, and witty quips 😬 start in my brain first. But, YES, the AI does help me clean this up and give the final product you’re reading. I don’t know what grade I’m going to get from that detector, but it’s fair to say it’s not 100% human these days. It’s also not close to 100% AI.

Which is why I am still not sure what the detector is measuring. I’ve read thoughtful arguments from both the supporters and the haters. Maybe this removes some of the low-effort “AI slop” out there. And I am all for that! I don’t think there is a single person out there asking for more generic content. But I keep finding myself coming back to the negatives. False negatives. False positives. Then something I didn’t even think about before: there is a whole set of people out there who speak English as a second language, and they’ve suddenly been able to access a whole new market. This feels like a punishment to them. My friend, speaks about this extensively in his publication, Slow AI.

I'm just not convinced we've figured out how to measure "human" in a way that's actually fair.

Other AI tools I am using to streamline my business because it doesn’t stop here:

Claude

ChatGPT

Whispr

Granola

Grammarly

Gamma

Lovable

Probably five more next month because I have absolutely no self-control when a new AI tool drops.

If AI really isn’t your thing?

That’s cool. You can still hang with me.

By the end of this you’ll have:

✅ The operating rhythm I use as a starting point with most growing SaaS companies

✅ The purpose of every recurring meeting

✅ Rules for when meetings should (and absolutely shouldn’t) exist

✅ A downloadable worksheet to audit your own company’s rhythm

Before we get into the template...

The first thing I look at when I join a company isn’t Notion.

It isn’t Jira.

It isn’t Slack.

It IS the calendar.

Because the calendar tells me how work actually moves through a company.

I don’t care how many AI tools you’re using.

If every answer still ends with someone tagging the founder...

If Engineering has no idea what Sales promised...

If Customer Success finds out about product changes from customers...

...your problem isn’t communication.

Your company doesn’t have an operating rhythm.

Most startups think they need fewer meetings.

Most actually need meetings that know what job they’re supposed to do.

Read more

Not the highlight reel.

The actual, messy, three-Slack-threads-deep reality of it. I am incredibly grateful that there are over 4,800 of you here sitting in the mess.

Over time, I realized there are two groups in that 4,800.

The founders living through the chaos.

And the operators helping them clean it up.

Where that’s already showing up

I didn’t plan for both of you to be here, but looking back, it makes complete sense.

More than one founder has read this newsletter, kept reading, ended up on a call with me, and eventually hired me. That part has worked exactly the way I hoped.

But a LOT of you reading this are not the founder.

You’re the operator. The fractional. The generalist. The person someone calls when the company has somehow created four onboarding processes and no one knows which one is real.

You’ve been here the whole time.

I just haven’t been building enough specifically for you.

What stays free

The free newsletter will keep being a place where both groups can see themselves.

The founder still deep in the chaos.

The operator who can already see why the chaos keeps happening.

That is the whole point of Systems & Side Eyes. I’m not changing it.

What’s changing about the paid tier

Here’s the part I’ve been sitting on.

I have an entire Google Drive full of templates, prompts, meeting structures, scripts, and operating tools pulled from real client work.

Built for real problems.

Used inside real companies.

Currently collecting digital dust until I happen to need them again. Very efficient system I have created here.

So the paid tier is becoming The Operator’s Back Room.

This will not be a second set of essays.

It will be the actual stuff I use to do the work, along with the context that makes it useful:

The Notion homebase I set up when company information is living in seven different places.

The meeting cadence that ends the “we need another meeting to discuss this meeting” cycle.

The ownership structure I use when every decision still floats back to the founder.

The scripts, prompts, and frameworks that help turn vague frustration into a problem someone can actually solve.

One tool at a time. Plus when to use it, how to adapt it, and where it tends to fall apart.

Subscribe now

What this is NOT

This is not a course about becoming fractional.

It is not a coaching program.

I am not going to stand at the front of a virtual room and pretend I have discovered the one correct way to build a portfolio career. (The internet has enough people doing that.)

I am opening up the systems I use to do the actual work.

I know how to walk into a growing company, find the friction, get people talking to each other, and build structure that does not immediately get abandoned.

That is what belongs in the back room.

What opens first

The first resource is coming next week.

I’m deciding between:

The Notion operating homebase.

The meeting cadence structure.

The RACI-lite ownership template that helps get decisions out of the founder’s head.

If you are the operator, fractional, or generalist holding everything together for someone else, reply and tell me which one you would use first.

Paid subscribers will get the winner first, along with the walkthrough for how I actually use it.

Founders are welcome in the back room, too. You may not want to build every system yourself, but you might want to see how I approach the problems happening inside your company.

Either way, the free side is staying exactly where it belongs.

Behind the curtain. Looking at the mess. Occasionally side-eyeing the fourth Slack thread.

More soon.

KB

Subscribe now

I sat in my car after my last day and thought: cool, now I just have to convince strangers to pay me for the thing I’ve been doing inside other people’s companies for 14 years. No pressure

.

A year later, I’ve fully replaced my W2 income. This newsletter somehow has over 4,700 of you in it. Most importantly, when my daughter needs me, I’m there.

I could stop the post here and call it a nice little brag, but that’s not actually the interesting part of this year.

The interesting part is that I spent 14 years telling founders what their businesses needed. And then I built one. And it turns out knowing the playbook and living the playbook are two very different things.

So instead of a highlight reel, here’s what I actually learned. The stuff I now understand in my body, not just in a deck.

Subscribe now

The “is anyone going to pay me” panic doesn’t go away. You just get faster at moving through it.

I’ve told founders a hundred times: the fear doesn’t mean you’re wrong, it means you’re doing something that matters. I believed it. I didn’t feel it until I sent my first invoice and refreshed my banking app four times in an hour.

The panic isn’t a signal to stop. It’s just the tax on doing something real. You don’t wait for it to go away before you act. You act with it sitting right next to you.

Sometimes the fix isn’t more structure. It’s less permission for new work to exist.

A founder pulled me into what was supposed to be a quick conversation about shaping the next sprint.

By minute ten, it was obvious the sprint wasn’t the problem. Product was talking in Notion. Engineering was operating entirely out of its own head. Process was trying to stand in the middle, translating between two teams that weren’t actually talking to each other. And the founder was sitting there, acting as the human API between every function in the company.

The instinct in that room was to add more structure. More meetings. More “alignment.” I’ve watched founders do this a hundred times, and as a true ops girl, I’ve felt the pull to do it myself.

The actual call was simpler and somehow a lot harder: no new work until the existing work had an owner, a board, and a deployment plan.

The line I gave was, “If it’s not on the board, it doesn’t exist.”

Boards don’t fix anything by themselves, but the company had reached the stage where invisible work had stopped being harmless and started being dangerous. Every task living only in someone’s head was a task that could secretly die, get duplicated, or get blamed on the wrong person.

If your team can tell you what they’re working on but you can’t see it anywhere without asking them, you are dealing with invisible work. Invisible work is how founders end up back in the middle of everything, even when they swore they’d delegated it.

Boundaries aren’t the opposite of partnership. They’re what make the partnership usable.

Here’s the one I got wrong this year, and I’m not proud of it.

I underestimated how expensive unclear boundaries are when you’re the one embedded inside someone else’s chaos. Not financially, although yes, that too. Cute little bonus consequence.

I mean operationally. Emotionally. I let a few client relationships stay too vague for too long because I was trying to be helpful, flexible, easy to work with. Turns out “flexible” turns into “available for everything” faster than you’d think if you don’t define the edges early.

I know this. I build clarity for a living. I have literally told founders, in these exact words, that the fuzziest relationships in their company are the ones that eventually break. And I still let my own scope stretch because a founder needed help, I could see the path forward, and it felt easier to just do the thing.

The lesson was annoying because it was so obvious once I said it out loud: a boundary isn’t a wall you put up to protect yourself from the people you’re helping. It’s the thing that makes the help sustainable enough to keep showing up.

If you’ve got a hire, a vendor, or a fractional partner whose scope has grown past what anyone actually agreed to, that’s not a them problem. That’s an unclear-edges problem, and it’s fixable in one written conversation.

You don’t need permission to build the thing you already know how to build.

For 14 years I was already doing this work, just without the title, the ownership, or the full credit. I didn’t need a new skill to go independent. I needed to stop waiting for someone to tell me I was allowed to.

If you’re sitting on expertise you’ve been handing to someone else’s company for years, that’s not a reason to wait. That’s the business.

So. One year in. Here’s what I actually know now that I didn’t a year ago:

The fear doesn’t disqualify you. The lack of clarity isn’t a phase you outgrow. Imposter syndrome doesn’t mean you’re a fraud; it means you’re paying attention. And most of what looks broken in your company is actually just an honest conversation you haven’t had yet.

If you’ve hired me, read this newsletter, or just cheered me on this year, truly, thank you. You built this too.

Year two, let’s go!!!

A founder texted me last week: “Can you look at this? I had AI run our retro notes, and I don’t actually know what we decided anymore.”

He read that back to himself before I could even respond. “That’s weird, right?”

Yeah. That’s weird.

He’s not lazy. He’s not checked out.

He’s running a sixteen-person team, closing deals, prepping for a raise, and doing what every founder does when the to-do list eats the day whole: he found the fastest way through it. AI wrote the retro summary. AI drafted the hiring rubric. AI ran point on a comp conversation when his Head of Sales asked for a raise.

None of that is the problem on its own. I use AI for half my day too (and we all know how much I LOVE a good shortcut).

The problem showed up two weeks later, when a client complained onboarding felt disorganized, and he couldn’t tell me why. He hadn’t actually sat inside the retro where his team named the exact reason. AI folded it into a tidy paragraph, he skimmed it, and the texture, the tension, the thing someone almost said but didn’t, all of it got smoothed out before it ever reached him.

He wasn’t in the room for his own company anymore. AI was.

Here’s the part nobody out there is saying out loud

The AI backlash crowd wants you to quit using it. That’s not my advice, and it’s not happening anyway.

My advice: use it AND stay the one doing the thinking.

Those are two different jobs. Lately, founders are only doing one of them.

A recent BCG study of C-suite leaders found that half are already seeing this exact gap show up in their own teams, and most expect it to get worse over the next few years. The skill they flagged as most at risk? Judgment and decision-making. The one thing you can’t hand off and still call yourself the founder.

Judgment isn’t a task. It’s a muscle. You use AI to clear the noise around a decision. You still have to make the call, sit in the discomfort of not knowing, and watch what happens when you’re wrong. That’s the whole loop. Skip the middle two steps and the muscle goes soft, even while your calendar looks more efficient than ever.

What this actually looks like when it’s working

The founders I trust most right now use AI to get to the decision faster, then still show up FOR the decision itself. They read the raw retro notes, not just the summary. They sit in on the hard conversation even when a doc could technically stand in for them. They know the difference between delegating a task and delegating their own understanding of their company.

You didn’t get slower or dumber. You just started mistaking the summary for the thing itself.

Subscribe now

One question before you close this

Where’s the one place in your business right now where you’re reading the AI summary instead of sitting in the actual room? Be REAL, REAL honest.

...

KB

I have walked into a lotttt of team meetings.

More than I can count at this point. Across industries, company sizes, funding stages. I am going to tell you something that took me a while to say out loud, because it sounds a little harsh.

Most of them should not have happened.

I don’t say that because I believe meetings are bad. They are not. A well-run meeting is one of the most powerful tools a team has. Truly.

The problem is that what I walk into most of the time is just a weekly obligation. People go around the room, share what they worked on, nod at each other, maybe stress a little, maybe laugh a little, and then leave with exactly the same blockers they walked in with.

Nobody talked about the real stuff. Nobody decided anything.

Fifty-four percent of workers leave meetings with no idea what to do next or who owns the tasks. (Atlassian surveyed 5,000 people across four continents to get that number. So it is not just your team.)

The meeting is not the disease. It is the symptom.

When a founder tells me they have too many meetings, I do not disagree. They probably do.

What I want to ask is: why are those meetings happening in the first place?

Nine times out of ten, the answer is that nobody knows who is allowed to decide anything without the founder in the room. So everyone gets invited to everything, just in case. Updates get shared instead of decisions getting made. The meeting becomes the only place where alignment theoretically lives, so it has to happen every week, forever, whether there is anything to align on or not.

Cut the meetings all you want. The dysfunction lives in the org chart, not the calendar.

What I actually do when I walk in

The first thing I change is not the meeting cadence. It is the agenda.

A real agenda goes out before the meeting. Not the morning of. Not five minutes before. At least the day before. And it is not a list of topics. It is a list of decisions that need to be made and questions that need answers. If nothing is on that agenda by a certain point, the meeting gets postponed. (I know. I know. That sounds extreme. It is also how you get your Tuesday afternoons back.)

People can add to the agenda if something comes up. That is the point. The agenda is a living signal of whether this meeting needs to happen at all.

What I am NOT doing is letting the meeting turn into a status report. Status lives in your project management tool, your Notion, your Slack update. (Hint: Check your documentation system if you are seeing meetings turn into only status updates. )

The meeting is for blockers. Real ones. The ones where someone needs another human in the room to help them move forward. And for decisions. The ones where someone needs to say yes or no, and the team needs to hear it.

That is it. That is the whole job of a meeting.

What well-run actually looks like

Agenda sent 24 hours ahead. Decisions listed, not topics.

Everyone who is on the invite knows why they are there and what they are expected to contribute or decide. If someone is just there to listen, they probably do not need to be there.

The meeting starts on time. (I realize this sounds obvious. It is apparently not.)

Blockers get named and owned. Not vented about. Owned. Someone leaves with the action and a date.

If something comes up that is not on the agenda and is going to take more than five minutes to address, it gets a separate meeting. Not a sidebar. A real slot on the calendar with the right people in it.

And after? A short recap goes out. Decisions made, owners named, next steps with dates. Three to five lines. Not a novel.

That is cross-functional communication working. It does not require more meetings. It does require better ones.

The data, since I know some of you want the receipts

Atlassian’s research found that meetings are ineffective 72% of the time. Three in four could have been a memo.

A separate study found that organizational misalignment is the primary cause of 47% of project failures. Not tools. Not technology. Misalignment.

Those two numbers live together. Meetings that do not produce decisions produce misalignment. Misalignment produces failure. The math is not complicated.

What IS complicated is getting a team to actually change how they meet. Meetings feel productive. Everyone is there. Everyone is talking. Something is happening.

Except nothing is being decided. Nobody owns anything. The founder has to follow up on the same five things they followed up on last week.

Sound familiar?

The fix, since we are here

Keep it simple.

First: a real agenda template your team actually uses. Not a suggestion. A system. Agenda goes out by this day, at this time, with this structure. If it is not filled, the meeting does not happen.

Second: a decision log. Somewhere simple. Could be a Notion page, could be a section in your meeting notes. Every decision that gets made gets written down with a name and a date. Humans are busy and memories are unreliable and clarity is a gift.

That is it. Start there.

The meetings that need to happen will keep happening. The ones that were just filling calendar space will disappear. Your team will start to feel the difference between a meeting that mattered and one that did not.

That feeling is the goal.

If your meetings are the place where things go to stay stuck, that is something I can help with. I work with a small number of founders in an advisory capacity each month, which includes getting this exact infrastructure in place, without a big complicated engagement. If that sounds like what you need right now, hit reply.

KB | Systems & Side Eyes

In the early-stage startup ecosystem, one phrase surfaces with remarkable consistency across founder conversations, investor decks, and offsite agendas.

“Our culture is our competitive advantage.”

Fascinating... Let’s take a closer look

.

The Culture Specimen (Culturum indefinitum)

The Culture Specimen is identified most reliably not by what it does, but by what it replaces.

It replaces the org chart nobody has drawn. The decision-making framework nobody has written down. The onboarding doc that technically exists in a Notion page created in 2022 that three of the current twelve employees have opened.

The Culture Specimen thrives in environments where the founder is a genuinely good human who cares deeply about their team, and also has no idea who owns the Sales-to-CS handoff. These two things are not in conflict. They coexist beautifully in companies between $800K and $5M ARR.

You will know you are in the presence of a Culture Specimen when you ask “who decides X” and someone says “oh we’re pretty flat here, we just talk it out.”

They are not wrong. They DO just talk it out. For about 45 minutes per decision. In a meeting that was supposed to be 20 minutes. That the founder had to be in.

The Culture Specimen is warm. It is well-intentioned. It went to great effort to pick a values statement that sounds like it came from a real human being.

It has not been able to explain those values to a new hire in a way that tells them what to actually DO.

Observed Behavior in the Wild

The Culture Specimen is most active during:

Offsite season (spring and fall). You will recognize the offsite by the presence of a whiteboard covered in sticky notes organized into a framework that will not be referenced again until the next offsite.

All-hands meetings. The Culture Specimen performs beautifully here. Slides are crisp. The founder is inspiring. Someone asks a question that reveals a fundamental misalignment between two departments and the founder says “great point, let’s take that offline” and weirdly, it is never taken offline.

Hiring conversations. “Culture fit” is invoked reliably at this stage. It is doing a LOT of work in the interview process. Structural clarity is not invited to the interview. Process ownership does not get a recruiter screen.

What the Culture Specimen Is Not

The Culture Specimen is not VALUES. Values are real, and they matter, and they show up in how you treat a customer when something goes wrong, how you give feedback to someone who is struggling, what you decide NOT to do when the money is on the table.

The Culture Specimen is not COMMUNITY. The fact that your team likes each other is genuinely beautiful. I mean that, but it does not tell anyone what to do when a deal closes, and nobody knows whose job it is to kick off onboarding.

The Culture Specimen is also not ACCOUNTABILITY. Accountability is structural and involves somebody’s name next to a thing with a date. The Culture Specimen prefers collective ownership, which is another way of saying no single owner, which is another way of saying nobody owns it.

Prognosis

The Culture Specimen does not die easily. It is remarkably adaptive. It will survive two funding rounds, four new hires, and at least one painful departure that everyone describes as “not a culture fit” that was actually a structure fit.

What eventually happens: the company gets to a size where the founder cannot physically be in every room, and suddenly the culture has to DO something without them in it. And that is when everyone discovers the culture was always the founder. Which is beautiful, AND not scalable.

The fix is not complicated. It is just not glamorous enough to put on a slide.

It is: who owns what, who decides what, what happens when, and what does good look like. Written down. Given to a person. With a name on it.

That is not a threat to your culture. That IS your culture. You just haven’t built it yet.

Until next time. The wildlife persists.

KB

If any of this felt uncomfortably familiar… I work with a small number of founders in an advisory capacity. Monthly calls, async access, a second brain on the stuff that’s actually breaking. No full embed required.

If you’re not ready for that either, just hit reply. I read everything. Let’s get

7:04am.

You haven’t made coffee yet. Your phone is already face-up on the counter because you told yourself you wouldn’t check it until after breakfast.

You checked it at 6:47.

Fourteen Slack messages. Three of them are questions your team could absolutely answer themselves if anyone knew where to find the answer. Two of them are from the same person, sent four minutes apart, because they didn’t hear back fast enough.

One of them is a client who seems... off. You can’t tell if it’s fine or if it’s a thing. It’s probably fine.. You’ll circle back.

You haven’t made coffee yet.

I had a client who traveled constantly for work.

And I mean constantly. Art fairs, industry events, the kind of places where the lighting is beautiful and the wine costs more than your first car.

She was at an event once. I’m pretty sure there was a castle involved. (Yes, an actual castle.)

And there she was. In the corner. Not looking at the art. Not talking to the people she’d flown across an ocean to meet.

Hunched over her phone. Answering Slack messages.

From her team.

Who were in an office.

Without her.

I want you to sit with that image for a second. A woman in a castle (surrounded by genuinely incredible things) spending her morning being the answer key for a team that shouldn’t need one.

That wasn’t a bad team. That was a team that had never been set up to run without her.

There’s a difference.

Subscribe now

Here’s what I’ve noticed after 15 years of walking into early-stage companies:

The founder is almost never the problem.

The SYSTEM is the problem. Or more accurately: the complete and utter lack of one.

When there’s no clear place to find answers, people ask the founder.

When there’s no ownership over decisions, people wait for the founder.

When there’s no operating rhythm that works without someone at the center holding it all together — that someone is always, always the founder.

And so you wake up on Monday at 6:47am, before your coffee, already behind.

You built something that worked when it was just you, and now it’s not just you anymore, and nobody ever told you what comes next.

You didn’t break it.

You outgrew it.

Luckily, that’s actually a very fixable problem. Pinky promise.

Here’s what I’m offering this month for my wonderful newsletter readers only.

I’m opening up 2 spots for a Bottleneck Audit at $1,500 (normally $2,500).

It’s a focused engagement where I come in, talk to you and your team, identify exactly where the system is breaking down, and hand you a clear picture of what to fix first and why.

No fluff. No 40-page deck that lives in Google Drive forever. A little bit of clarity and a path forward.

This is for founders who are somewhere in the middle. Not in crisis, but not scaling the way they want to. The ones who are still in every Slack thread, every decision, every fire.

The ones who are tired of being the answer key.

If that’s you, hit reply. Tell me one thing that’s been driving you crazy lately. We’ll go from there.

Two spots. This month only.

KB

Then there are others that come from 20 years inside a broken industry, and they’ve watched the same problem happen over and over and over and over. These founders saw smart people using bad systems that just kept breaking.

They watched families, customers, employees, patients, students, or teams suffer through something that should have been easier. Then one day they stopped saying someone should fix it, and they just freaking fixed it.

This group of founders is really some of my favorites. They’re not behind, and they’re not less sophisticated because they don’t speak the jargon. They often actually understand the customer and their problem better than anyone who learned from just a market deck or Silicon Valley language. They know the weird edge cases that nobody else sees unless you’re in the dirt with them. They know the emotional stakes. They know what people say in meetings and they know what people actually do when a system fails.

THAT IS GOLD.

Now this is the part where it gets hard, because that same depth that makes them brilliant can also put them at the center of everything in the company that they’ve built. They quickly become the translator for every department.

• The sales team needs their context.

• The product very much needs their judgment and understanding of the client.

• Engineering needs their explanation to execute.

• Customers want them front and center because they trust them, and then the team all wants their approval.

Suddenly, the founder who wanted to fix a problem is spending their days answering questions, clarifying decisions, smoothing over handoffs, and trying to remember why something was promised six weeks ago.

They didn’t do anything wrong, but their knowledge never got turned into a system. They might be digging for solutions with AI or blogs from other SaaS experts, but it just isn’t clicking.

Can we just admit something?? Startup language is weird! Acronyms make normal people feel like they walked into the wrong classroom halfway through the semester.

• ICP

• PLG

• GTM

• NRR

• CAC

• LTV

Cool, but underneath most of those terms are really normal business questions, and those get lost. Really, what those terms come down to is:

• Who are we selling to?

• How do customers find value?

• What happens after someone buys?

• Are people staying?

• Are we making money in a way that makes sense?

• Do we know what’s working?

This is where I love working with founders like this.

They do not need someone to come in and make them more “startup-y.”

(Pleaseee no.)

They need someone who can sit between the founder’s hard-earned industry wisdom and the company that now has to execute around it.

Someone who can translate founder instinct into team clarity.

Customer nuance into onboarding.

Sales promises into delivery reality.

Gut feeling into a simple operating rhythm.

Cross-functional weirdness into “Here’s who owns this, here’s where it lives, and here’s what happens next.”

If this is you, I hope you know this:

You built something real.

You saw a problem other people tolerated and decided to do something about it.

That is not small.

You do not need to become a startup person to keep building it (promise), but the company does need a way to operate without everything living inside your head.

That is the next version of the work. Making what you know easier for everyone else to carry.

If part of your company still mostly lives in your head, reply and tell me what it is. That’s usually the first place the next system needs to go.

“We replaced our SDR workflow.”

“Our AI assistant handles support.”

“Ten people can now do the work of fifty!! WOOO HOO!”

Look…some of this IS real.

I use AI every single day. I LOVE it. It makes me feel like a superhuman sometimes. I use it to pressure test ideas, spot patterns, summarize information faster, draft first passes, and help structure workflows.

It’s an incredible sparring partner.

I still think we are about to see a whole lot of startups realize they never actually understood how work moved through their company in the first place.

Not sure if you’ve realized this from all my ranting, buut a shocking amount of startup infrastructure exists entirely in someone’s head.

Sam in Product has been here the longest, so he knows how onboarding works for that type of client.

Only the founder can approve pricing exceptions…after talking to Annie in Customer Success because she knows which customers are already upset.

Everyone references the same Google Sheet called FINAL_final_v2_USE_THIS_ONE.

There are seventeen Loom videos explaining the process. Nobody knows which one is current.

A new workflow gets created every time a weird client request comes in. Which means there are now 14 “temporary” processes living in Slack threads from nine months ago.

Still, somehow…through sheer force of human effort…things still mostly function.

Subscribe now

This is the part I think the AI discourse is missing.

AI isn’t the real problem.

The scary thing is that a lot of companies are trying to automate systems they never fully defined.

AI is about to expose every startup operating on tribal knowledge.

Let’s be real…operators have known this for YEARS.

A lot of founders hear “operations” and think:
unnecessary structure
bureaucracy
slowing things down
admin work

What they don’t see is the amount of translation and coordination happening underneath the surface to keep the company functioning.

The ops person manually fixing CRM data before the board meeting.

The Customer Success lead preventing a client escalation before Sales even hears about it.

The manager spending half their week translating founder chaos into actionable work for the team.

The person in the 1:1 after the meeting playing therapist, translator, and systems analyst all at once. (Oh hi. That one is me.)

So when I see posts celebrating the elimination of entire teams, especially in Customer Success and operations-heavy environments, I definitely side-eye a little.

AI can absolutely accelerate good systems, but it also totally industrializes chaos.

You cannot toss garbage into AI and expect a masterpiece back.

If ownership is unclear, AI scales confusion.

If onboarding is inconsistent, congrats, the AI makes the inconsistency faster.

If nobody knows who approves what, AI just creates more noise at a higher speed.

If your company memory currently lives inside Slack DMs and “ask Sam,” eventually something breaks.

I think some founders are underestimating how much invisible labor has been holding their companies together this whole time.

Yes, it’s task completion, but it’s also:

Context.

Judgment.

Relationship management.

Cross-functional communication.

Pattern recognition.

Knowing when a customer sounds frustrated before they churn.

Knowing which process SHOULD be followed and which one everyone ignores because it broke three months ago.

That stuff matters.

A LOT.

The companies that survive this next phase of AI adoption won’t necessarily be the leanest.

They’ll be the companies that actually understand how work flows through their business.

Who owns decisions.

How information moves.

Where handoffs break.

What deserves automation.

What still requires human judgment.

For the operators reading this feeling mildly existential right now…truly, I think your value is about to become even clearer (if you manage the moment correctly).

The people who know how to build clarity, define workflows, create alignment, and use AI WITH guardrails are going to be incredibly valuable.

The future is not AI replacing every human in the org chart.

The future is humans who understand systems working alongside AI far better than companies operating on duct tape and tribal knowledge.

Cool. Your AI agent booked the meeting.

Does anyone know what happens after the contract gets signed?

Leave a comment

You’ve been ON since 7am. Founder-led sales, or pitching the raise, or both, and you’ve finally got a minute to look at the actual work. The thing you’re supposedly running.

Ten Slack messages. All variations of the same question. Nobody’s sure where to look, nobody’s sure who decides, so everybody’s waiting on you.

And while you’re in there, you catch something in the product that feels a little off. You remember a sales call from this morning where someone said “yeah, that’s not really how we’d want it.” So now you’re trying to make a call on it. At 11pm. Without the full context, without the team in the room, just you and your gut and the slow creep of “why am I the only one who can see this.”

Here’s what you’ve decided that means: you’re the bottleneck. You’re the problem. You built a company that can’t run without you, and sooner or later someone’s going to figure that out.

I want to offer you a different read.

You’re not the bottleneck. You’re the proof it worked.

The company runs through you because you built something real. Something with enough going on that it now needs more than one brain to hold it. That’s not failure. That’s the most backhanded compliment in startups: you made a thing big enough to outgrow the way you made it.

I’ve watched this happen to a lot of founders. For a long time, I came in, saw it, helped untangle it, and still didn’t fully get how it FELT. Then I started my own business. And let me tell you, there is no lesson quite like building something from the ground up, being so proud of it, and realizing you cannot put it down. You don’t step out of the weeds because the weeds are yours. You planted them. Cute or not

.

So I’ll tell on myself. Even from the second seat, the ops chair, I have been completely convinced the place would fall apart without me. Wildly convinced. And then I’d take a real vacation and... it dragged along. Messy, sure. But it moved. Turns out companies are more like weeds than orchids. They survive a startling amount of neglect.

(I know. I know. Humbling.)

Here’s the part nobody told you, and it’s almost insultingly simple:

Your team isn’t waiting on you because they’re not smart enough. They’re waiting on you because no one ever told them they were allowed not to. You hired good people. You just never built the stupid-simple thing that lets them move without your sign-off.

Not a framework. Not a 40-page Notion fortress nobody opens.

One place that answers four questions:

Who owns this. Who gets to decide. When it’s due. What good looks like.

That’s it. That’s the whole unlock. When those four things live somewhere other than your head, the 11pm Slack pile shrinks on its own, because the answer isn’t “ask Jordan.” The answer is on the wall.

You didn’t break it. You just outgrew the way you built it.

And that, truly, is the most fixable problem you have.

If your nights look like this...

I built something for exactly this moment. It’s called the Bottleneck Audit. We find the specific places the company runs through you that it shouldn’t, and we name them, so you can stop white-knuckling every decision and start handing the right ones off.

Not a big consulting proj... no. Let me say that the right way.

It’s the fastest way I know to see, on paper, why your team keeps coming back to you, and what to do about it.

You don’t have to do this alone. You were never supposed to.

KB

Let's Chat!

Sorry to be so forward about it, buuut it’s the truth of 99% of the startups I’ve worked with. You’re paying for costs you never even thought of.

The biggest offenders:

• duplicated work

• delays due to poor communication across the team

• burnt-out employees

• meetings that lead to more confusion than clarity

Founders are busy doing ALL of the things and can easily miss these silent killers.

Let’s dive into what this actually looks like:

Read more

I ultimately arrived here by getting dropped into messy situations and figuring things out in real time.

Small teams. Big personalities. Tight budgets. Founders trying to hold 97 things together with pure force of will.

Somewhere along the way, startup work started beating a few lessons into my brain.

Some of them I learned quickly.

Some of them I apparently needed to learn over and over and over again.

So in honor of that… here are a few things I learned the hard way over 15 years working inside early-stage companies.

(You’re welcome.)

Speak up earlier than feels comfortable

Early in my career, I thought confidence and experience were the same thing.

They are not.

Some of the loudest people in the room were also the most wrong.

I can still remember sitting in meetings, feeling physically uncomfortable because I KNEW something would become a problem later.

A customer workflow that made no sense.

A launch timeline that was never going to hold.

A process everyone was nodding along to that absolutely nobody was going to follow once real life hit.

I stayed quiet sometimes because I assumed everyone else knew more than me. (If you truly know me, this is out of character. I tend to let my thoughts be known. 😂)

Older.
More technical.
More experienced.
More important.

Then I got to watch the exact problems I was worried about happen anyway.

Over time, I realized something really important:

Speaking up thoughtfully earns more respect than silently being correct.

People trust operators who are willing to say:
“Hey… I think this might break later.”

I actually think a lot of leadership teams are desperate for someone willing to say the uncomfortable thing calmly.

Subscribe now

Sometimes being right is not the most important thing

This one took me YEARSSSSS.

Especially as someone who really likes being correct. (Hi. Hello. One of my larger faults.)

Startup work taught me that you can be completely right and still make the situation worse.

I’ve built processes that founders immediately changed three days later.

I’ve watched teams resist systems that were objectively cleaner because they were exhausted and overwhelmed and couldn’t absorb one more change.

I’ve sat in meetings knowing a decision wasn’t the best possible decision… but also knowing the team needed momentum more than another week of debate.

That’s the thing nobody tells you about operations work:

You are not optimizing for intellectual victory.

You are optimizing for progress, trust, clarity, and morale.

And in small startups, especially, morale IS infrastructure.

If every conversation becomes about proving who was right, people stop collaborating and start protecting themselves.

Sometimes the best thing for the company is swallowing your pride, adjusting course, and helping the team move forward anyway.

Even when you know your original recommendation was better.

(Annoying lesson. Hate that one for us.)

Nobody is coming to fully train you

I used to think everyone else had some secret handbook I missed.

Turns out most people are figuring it out in real time, too.

Some of the most important things I learned happened in rooms where I barely said a word.

Board prep meetings.
Fundraising conversations.
Sales reviews.
Customer success escalations.
Hiring discussions.
Budget conversations.

If someone gave me the option to sit in on something, I almost always said yes.

Even when I didn’t fully understand half of what was happening yet.

That wasn’t the point.

Repetition changes your baseline.

The conversations that once intimidated you eventually become conversations you can contribute to.

The people who level up fastest are usually the people paying attention long before they “need” the information.

I also learned how rare truly generous mentors are.

There are people who gatekeep knowledge because it makes them feel valuable.

And then there are people who pull others into the room and say:
“Come listen. You’ll learn.”

I never forgot the difference.

Which is exactly why I try so hard now to help younger operators and founders coming up behind me.

Finding someone willing to explain things without making you feel stupid is a massive gift.

Simplicity scales better than brilliance

I have watched companies spend THOUSANDS of dollars building systems nobody actually uses.

Beautiful dashboards.
Overengineered workflows.
Fancy project management setups with seventeen automations and color coding and ten different views.

Meanwhile everyone is still slacking each other:
“Wait who owns this?”

Startups love building processes for their fantasy selves instead of their actual teams.

If you haven’t been listening to me blab enough about this allll over social media, lemme just say it again, the best systems are usually a little boring!

Clear owner.
Clear next step.
Clear due date.
Clear place to look.

That’s it.

The companies that scale best are not always the most sophisticated.

They’re the ones where people consistently know:
who is doing what,
where information lives,
and what happens next.

Honestly, “stupid simple” scales surprisingly far.

Final thoughts from someone who has absolutely learned many things the hard way

I still learn lessons the hard way constantly.

Startup work has a very humbling way of finding your weak spots.

Looking back, most of my career was built from:

paying attention,
staying curious,
speaking up,
asking questions,
and trying to make complicated things a little easier for the people around me.

That’s still the job.

And for anyone earlier in their career reading this:

You do not need to know everything yet.

You just need to stay curious enough to keep learning.

That part matters more than people think.

KB

PS: If your company currently runs on tribal knowledge, founder memory, and Slack archaeology… hi. You are exactly the kind of team I help.

I work with early-stage founders to simplify systems, clean up operational chaos, and build processes people ACTUALLY follow.

I currently have 2 open spots for embedded fractional COO support.

If your team is growing faster than your operations can keep up, let’s talk.

My grandma was in the ICU. As the eldest grandchild, I was so very fortunate to get to spend an enormous amount of time with this incredible woman. She has always been one of my closest confidants, my rock, my guide for how to treat others. (Not to brag or anything, but she is now beloved by her whole care team. Yes, she’s even been inviting them to her funeral.)

As I sit here and hold her hand through this brutal phase. I keep thinking about how little we actually talk about this part of life.

The end-of-life part.
The decisions.
The process.
What it actually looks and feels like when you’re in it.

Because it’s A LOT. And that doesn’t even begin to encapsulate the actual feeling.

It’s scary and stressful and dramatic and messy in a way that’s hard to explain until you’re sitting in it.

At the same time, there are these really beautiful moments.

That part has caught me off guard.

There’s something about being in a hospital room, sitting in the unknown, that strips everything down really fast.

The things that felt big a week ago don’t feel big anymore.

The grudges don’t feel as solid.

The distance between people starts to feel… unnecessary.

My mom and I haven’t spoken to my aunt in over 15 years.

Fifteen.

It had turned into this massive, awkward, unspoken thing. One of those situations where it just grows over time until it feels too big to fix.

Then this happens. The past goes out the window, and the anger or sadness that was so tied up in that doesn’t feel as heavy.

They showed up for each other.

For their mom.

And it was like something just lifted.

All of that weight, all of that history, just… loosened its grip a little.

Now, it doesn’t mean everything is magically fixed, but it means it does not matter in the same way anymore.

That’s the part I can’t stop thinking about.

How quickly we can come back to each other when something actually matters.

How easily we can choose connection when we need it. (And we really do NEED it.)

How much of what keeps us apart… is more flexible than our brain lets us believe.

The hospital itself is this strange mix of emotions.

There are moments where you’re just sitting there, completely overwhelmed by the unknown.

And then five minutes later, someone says something ridiculous, and everyone is laughing.

Like belly laughing. (Surprised they didn’t kick our big, obnoxious crew out.)

It happens because you need to.

Because it’s the only way through some of it.

I feel really lucky, honestly.

Lucky to have a family that shows up like this.

That makes each other laugh.

That sits together in the hard moments instead of trying to avoid them.

Not everyone gets that.

And I’m very aware of it.

I just keep wishing we didn’t need something like this to remember how to be with each other.

To soften.

To give each other the benefit of the doubt.

To speak a little kinder.

To meet each other where we are instead of where we think they should be.

The truth is… we’re all going through something.

All the time.

Some of it is just more visible than others.

I am sharing because my takeaway from all of this is a big fat reminder that we’re all human. We are going through things. I always push to lead with empathy, and this just makes me even more certain that it is the best path.

Life is messy and hard and beautiful in ways I don’t think we give enough space for. Next time you want to argue over a mistake or process gone awry, take a moment to remember there is a real, complicated, live person on the other side of the table.

Now go hold your loved one's hand for me.

Cool…

That could mean just about anything.

We have to dive deeper than this, my friends. I don’t believe that our main problem is that we aren’t moving fast enough. Look at Jack in sales, he is on Slack at all hours. Sarah, on the dev team, is shipping new updates and bug fixes daily. There is speed abound.

The real issue is almost always something deeper than this summary.

What I’m actually trying to figure out

I’m not trying to confirm the problem.

I’m trying to understand:

Do you actually know what your team is experiencing day to day?

If you don’t…we’re about to solve the wrong thing. Fast.

(Which I know you love. Moving fast. Breaking things. All that.)

So I start here…

Nothing fancy. Frankly, it might come off as kind of annoying to these fast-moving founders.

Read more

Different industries, different team sizes, different tools. One was running a Notion setup so elaborate it had its own table of contents. One was using a project management tool with enough views, filters, and automations to make your eyes water. One was running almost entirely out of Slack threads and luck.

All had the same problem.

Nobody knew who owned what.

Here’s the thing about systems

We’ve overcomplicated what a “system” even means. Somewhere along the way, system started meaning: sophisticated tool setup, multi-step workflow, color-coded board, documented process with a cover page.

It doesn’t mean any of that.

A system at its core is just: how does work get done reliably, without you having to chase it?

That’s it. You only need three things to make that true.

Owner

Every task, every project, every recurring thing that matters. One person’s name is on it.

Not a team. Not “marketing.” A person.

When something belongs to everyone, it belongs to no one. Let’s be real you already know this, because you’ve watched it happen. The thing that was everyone’s job didn’t get done. Again.

One name. That’s the rule

.

Deadline

A task without a due date is just a wish.

I’m not talking about arbitrary pressure for its own sake. I’m talking about the difference between “we should get to this” and “this is done by Thursday, end of day.” One of those things gets done. The other one gets discussed in four more meetings and eventually dies quietly.

Put a date on it. Even a soft one. A stake in the ground is still a stake.

Visibility

This is the one people skip.

The owner knows. The deadline exists. Yet it lives in someone’s head, or a private doc, or a thread that’s already been buried under forty other messages.

Visibility means: anyone who needs to know can find it without having to ask. It doesn’t have to be fancy. A shared Notion page works. A column in a spreadsheet works. A standing section in your weekly team update works.

The tool matters a lot less than the habit. Pick one place. Put the work there. Keep it current.

That’s the whole framework

Owner. Deadline. Visibility.

Not a new app. Not a certification in agile methodology. Not a three-day offsite to redesign your operating model.

Just those three things, applied consistently, across everything your team is working on.

I’ve watched companies spend months building elaborate systems that collapsed the second someone went on vacation. And I’ve watched scrappy early teams run remarkably clean operations out of a single Notion table because everyone knew the rules and followed them.

The difference was never the tool.

It was the clarity underneath it.

If every piece of work your team touches has a name, a date, and a place to live, you are in a genuinely good spot.

Start there...

KB

P.S. Need help getting to those stupid simple systems? I have one advisory slot available for a founder in need. My DMs are open or email me at Katie@riseandoptimize.com

I have sat in a lot of meetings. Listened to a lot of all-hands. Nodded along to a lot of phrases that sounded completely reasonable in the moment and revealed themselves (slowly) to mean something else entirely.

This is not a cynical piece. (I promise.) It’s a love letter to the gap between intention and reality. Most founders mean what they say. They’re just moving fast, under pressure, with more optimism than infrastructure. And that gap? That gap is where I live.

So. In the spirit of public service. Here is your glossary.

On Getting Hired

“We set clear expectations here.” Translation: We will set them. Eventually. Once we figure out what we’re actually building. In the meantime, please read the room.

“We’re looking for someone scrappy.” Translation: We need one person to write the strategy, execute the strategy, measure the strategy, and report back on the strategy. No, there is no budget. Yes, we expect results.

“It’s a fast-paced environment.” Translation: Everything is urgent. All the time. There is no prioritization system because prioritization would require us to admit we cannot do everything at once, and we are not ready to do that.

“We’re a family here.” Translation: We care deeply about each other. We will also, when things go sideways, discover exactly who is family and who is staff. (Hint: it becomes clear very fast.)

“We really value work-life balance.” Translation: We truly mean this. Except during crunch time. We are always in crunch time. But other than that… totally serious about the balance thing.

Subscribe now

On What the Team Actually Needs

“The team just needs to be more proactive.” Translation: They don’t know what they own. They are tired of guessing wrong. They have guessed wrong enough times that guessing now feels dangerous.

“I need them to take more ownership.” Translation: No one has defined ownership. So everything is everyone’s responsibility. Which means, practically speaking, nothing is anyone’s responsibility.

“They’re not executing.” Translation: There is no clear plan. There are no clear priorities. There is no agreed-upon definition of done. But yes, the execution is the problem.

“I don’t want to micromanage.” Translation: I have avoided defining expectations. I am now managing chaos instead of people. I do not yet see the connection between these two things.

“They should already know this.” Translation: No one taught it. It is not written down anywhere. It lives, exclusively, in the founder’s brain.

On Communication

“We’ll circle back to that.” Translation: We will not circle back to that. Ten other things have happened since this meeting started. No one has been assigned ownership of the original thing. The circle is open. It will remain open.

“We just need better communication.” Translation: We have no communication system. We have Slack and vibes. The vibes are not doing great.

“Our dashboard lives in this sheet.” Translation: It lives in a Google Sheet called TEAM KPIs FINAL_v4. One person knows how to read it. That person is currently on PTO. We will not be updating the sheet while they are gone because we do not know how.

“That’s documented in Notion.” Translation: It was documented in Notion. In February. Notion helpfully tells me it has not been touched since. New hires do not know it exists. Existing employees forgot to check it after week two. But it IS there, and that matters to us.

On the Product

“The product is strong. We just need to tell the story better.” Translation: The product is confusing, inconsistent, or not yet delivering value fast enough. Buut the story is easier to fix than the product, so we are starting there.

“This is a quick fix.” Translation: This is a systemic issue wearing a trench coat and pretending to be a feature request.

“We’re close.” Translation: We are not close. We are unclear. Close and unclear feel similar from the inside. They are not the same.

“Once we ship this, things will unlock.” Translation: We are pinning operational problems on a future feature. The feature will ship. The problems will remain. We will identify the next thing that will unlock everything.

“Engineering just needs to move faster.” Translation: Priorities are shifting constantly and no one is protecting the team’s focus. But yes. Faster. That’s the thing.

On Strategy

“We just need to tighten execution.” Translation: There is no agreed-upon strategy to execute against. But execution sounds more fixable than strategy, so we are starting there.

“We’re aligned.” Translation: Everyone in the room is using the same words. No one means the same thing. This will become apparent later, at the worst possible moment, usually in front of a client.

“We just need to tighten up our processes.” Translation: We do not have processes. We have habits, and some of the habits are bad, and we have decided to call them processes so that fixing them feels more manageable.

On Clients

“We can absolutely do that.” Translation: We cannot currently do that. We are going to figure out how to do that after this call. We believe we will figure it out. We are optimists. This is both our greatest strength and the reason our ops team is aging rapidly.

A Note From the Field

None of these phrases are malicious. I want to be really clear about that.

They come from founders and leaders who are building something that didn’t exist before, moving faster than any system can keep up with, and genuinely trying to do right by their people. The gap between what gets said and what’s actually happening isn’t dishonesty. It’s the space between intention and infrastructure.

That gap is fixable.

It just requires someone willing to stand in it, look around, and say, “Okay. Let’s talk about what’s actually going on here.”

That’s the work I do. And if any of these translations hit a little close to home today, my DMs are open.

See you in the wild.

-KB

I’m scanning.

It’s a little hard to explain unless you’ve sat in that seat, but within the first hour or two… things start to reveal themselves. Company behaviors tell all.

What I notice immediately

Who is talking.
Who is quiet.
Who defers.

Whether the founder answers every question (even the small ones. You know what, it’s especially the small ones.)

Whether people sound confident… or like they’re half-asking for permission.

You can feel pretty quickly if a team is operating
or waiting.

The three questions running in my head the whole time

I am basically trying to answer these on a loop:

Read more

“I have to be involved in everything or nothing gets done.”
“No one takes initiative.”
“It’s all in my brain.”
“I can’t step away.”

Underneath all of that is usually something simpler:

“I’m just really tired.”

I’ve been in a lot of rooms where this is happening. Meetings drift to a heated venting session where decisions are second-guessed and reversed halfway through. Tension is palpable.

Sometimes it shows up as frustration:

“If they don’t want to be here, they can go.”

Sometimes it’s less direct:

“I just don’t trust anyone to handle this.”

Either way, the whole team feels it, and things slow down massively.

What it looks like from the inside

When I step into a company at this point, the pattern is usually pretty clear within the first week.

People technically “own” things. There might be a Notion doc, a beloved Gsheet, or a Monday disintegrating somewhere.

The day-to-day reality, though? Everyone is still looking at the founder. They’ve learned that decisions don’t always stick.

Someone makes a call, and it gets changed later.
A direction gets set, and then reworked midstream.

After that happens a few times, people stop pushing forward on their own. They stop feeling empowered or valued. If your team doesn’t feel trusted, they don’t stand up and make the decisions.

Subscribe now

The subtle shift that causes all of this

At the company's start, this was the founder’s baby. They were in every decision. They made every move. The problem arises when the org starts to scale, and this is still how they operate. The founder never bothered to get out of the weeds fully. Even though they brought the bodies in to do all of the things.

Even in slightly more established companies with tools, boards, and documentation, this still happens.

You’ll see a Slack message from a client, and the founder jumps in:

“Wait, what’s going on here?”

Now everyone’s back in the thread.
Re-explaining. Re-deciding. Resetting.

It doesn’t look like a big deal in the moment.

Over time, it turns into a pattern.

Where the exhaustion really comes from

When everything flows through one person, that person never gets a break from the business. There’s no clean handoff or pause. Or room to just zoom the heck out for a second.

It becomes constant context-switching:

product
sales
support
hiring
internal questions

ALL FREAKING DAY.

Most of the founders I work with were thoughtful about the talented people they hired. They just never fully handed off the tasks the hire was brought in for.

What’s missing is true delegation and a structure that those people can actually operate within.

What changes when this gets cleaned up

You can feel the difference pretty quickly. Your meetings will go faster and be wildly more productive. You get more diverse opinions and perspectives that lead to a more successful product. Those infuriating decision loops settle down, and your people are empowered to just make the dang move.

There’s more trust on both sides.

Founders take a day off and don’t come back to a mess.
They can actually step away for a bit without everything stalling out.

The whole company just… breathes differently.

Burnout is inevitable when everything still depends on one person to keep moving. Once that weight gets distributed, things start to feel a lot more manageable. For everyone involved.

If you’re in this right now, you’re not alone.

I spend a lot of time helping founders take this from “everything runs through me” to something the team can actually carry together.

I have one advisory spot open if you are ready to dig into it. Let’s breathe!