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!

“We built the product. Why is getting customers so hard??”

Over the past month, I went down a bit of a rabbit hole reading founder threads on Reddit. r/SaaS, r/indiehackers, r/startups. Hundreds of comments. (I know. I know. I have a fun life.)

The pattern was surprisingly consistent.

Founders are not struggling to build products. (Thanks to tools like Lovable, Emergent, and Bolt…everyone can be a builder now!)

Where the struggle happens is getting the right people to use them.

Finding actual users who care enough to try the product and tell them what’s working is not easy.

The conversation always sounds roughly like this:

“We launched, but nobody’s using it.”
“We’re getting traffic but no conversions.”
“How do you find your first 10 real users?”
“People say it’s cool, but they don’t pay.”

A lot of the time, this is diagnosed internally as a distribution problem.

They assume they need better marketing, more reach, or a growth hack they haven’t discovered yet.

Sometimes that’s true, but a lot of the time, the real issue shows up much earlier.

They don’t have a shared operational definition of the customer.

Subscribe now

When “our customer” means “basically anyone”

One of the fastest ways to make customer acquisition feel impossible is to build a product for too many people at once.

When founders describe their target user, it often sounds something like:

“Anyone who manages projects.”
“Small businesses.”
“People who want to be more productive.”
“Startups.”

These sound reasonable on the surface, but they are too broad to guide anything useful.

Marketing and messaging become vague, and outreach feels like throwing darts in the dark.

If you don’t know exactly who the product is for, every channel feels inefficient. Because it IS.

The difference between a market and a customer

A market is not the same thing as a customer.

“Startups” is a market.

A customer looks more like this:

A seed-stage SaaS founder with 20–50 employees who just hired their first customer success manager and is realizing onboarding is messy.

That founder has a very specific problem.

They are feeling it every day.

They will recognize themselves immediately when they see the right message.

That’s when acquisition starts to feel less like shouting into the void and more like starting conversations with the right people.

Why the first users matter so much

A lot of founders say they want their “first 10 users.”

I would argue that what they actually need are the right first 10 users.

The early adopters who:

• have the exact problem the product solves
• are motivated enough to try something new
• are willing to give honest feedback
• will tell you where the product is confusing or weak

Those users teach you how to talk about the product.

They help refine the messaging.

They expose which features actually matter.

Without them, marketing stays theoretical.

You end up optimizing channels before you understand the problem you’re selling.

When distribution finally starts working

Once the customer definition gets clearer, everything downstream improves.

Messaging becomes sharper.

Outreach feels more natural.

Channels start performing differently.

Instead of trying to reach everyone, you start seeing patterns in where your people actually spend time.

And most importantly, conversations get easier.

Because the person you’re talking to recognizes their problem in what you’re describing.

The pattern I see inside startups

After 14+ years inside early-stage companies, this shows up constantly.

Founders think they have a marketing problem.

The reality is that it’s a company alignment problem.

There is no shared operational definition of the customer.

What this looks like

Sales is talking to one type of customer.
Marketing is targeting a different one.
The product was built for a third.

So the founder says:

“We need more leads.”

The real issue is that no one can clearly describe what a good customer actually is. So what would these leads do?

The clarity that’s missing

• who the product is for
• what problem is painful enough that they will pay to solve it
• where those people already spend time

If your team can’t answer those the same way, acquisition will feel (and BE) inconsistent.

Why this is an ops problem

It doesn’t stay in marketing.

• Sales closes the wrong deals
• Onboarding struggles
• Customers churn

What looks like a top-of-funnel problem is a completely broken customer lifecycle.

What changes when this gets fixed

Clarity sharpens messaging.
Outreach gets easier.
Channels start working.

Customer acquisition stops feeling like guesswork.

It starts behaving like a system. And we all know how much I LOVE a system.

Sara shared a lot of thoughtful perspectives from the investor side. What they look for in founders, how the AI moment is changing the landscape, and why so much still comes down to people and conviction.

One thing she said stuck with me:

“Make them love you. Make them want to support you.”

Which sounds simple, but when you think about the mechanics of fundraising, it actually means something deeper.

Investors have to walk into a partner meeting and advocate for you. They have to answer hard questions from the rest of the partnership. They have to explain why THIS company, THIS team, THIS moment.

The clearer and more prepared you are, the easier it is for someone on the inside to do that.

Listening to the conversation, I kept thinking about something I see over and over again when founders start preparing to raise.

Raising a round ends up being a bit of an operations test.

Not in a scary “gotcha” way. The process simply surfaces whatever is still fuzzy inside the company.

Investors start asking questions like:

How clearly can you explain what you’re building?
Is the team aligned on where the company is going?
Can you quickly pull together the numbers or materials someone asks for?

Those questions sound like fundraising questions, but at the core, they’re really operations questions.

They reveal how clearly the company thinks, how organized things are behind the scenes, and how easily the team can move when someone asks for something.

So when I help a founder get ready to raise, these are usually the first things I tighten.

1. Get your narrative straight before you get your deck pretty

This one is painfully relatable.

A lot of founders start by polishing slides. Or tweaking the design of the deck. Or refreshing the website.

Meanwhile, the core story is still a little wobbly.

Before worrying about fonts or layout, I want founders to be able to clearly answer a few things:

• What problem are you solving?

• Why does it matter right now?

• Why are you the team to do this?

• What have you already learned from customers?

• What will this round allow you to prove next?

Investors don’t need a perfect story.

They do need to understand it quickly.

And if you’re finding yourself rewriting the same slide ten times, that’s usually a sign the thinking underneath it needs a little more work. Once you get that clear, then take the time to make the slide deck. And BTW, there are some killer AI tools out there now to help you draft that beautiful deck. Claude + Gamma is my favorite deck-building setup right now.

2. Know what the round is actually for

“We’re raising” is not the strategy.

The round should connect to a specific set of milestones.

Maybe the goal is shipping a key product milestone.
Maybe it’s proving early customer traction.
Maybe it’s building the first repeatable sales motion.

Whatever the case, the money should have a clear job.

I LOVE it when founders can connect this back to a lightweight financial model or operating plan, even if it’s early.

Not everyone has the resources to build a beautiful full-scale model at this stage. That’s okay. (Hint: This is another good opportunity to work with your AI tools to put together even a lightweight model.)

What matters more is showing that the capital connects to real progress and thoughtful decisions about what comes next.

3. Make sure the story lives beyond the founder

Another pattern I see a lot: the founder understands the story in their head.

Then an investor asks to meet the cofounder.
Or the head of product.
Or the person leading engineering.

Suddenly, the story starts to drift a little.

If multiple people on your team are going to interact with investors, they should all understand the core narrative.

Why this problem matters.
What the company is building.
What this round is supposed to unlock.

It doesn’t need to sound rehearsed.

But alignment here goes a long way toward building confidence.

4. Treat the raise like a live operating process

One of the fastest ways for fundraising to become overwhelming is when it lives only in your inbox and your memory.

A simple pipeline tracker helps a lot.

I’ve seen founders run this in Airtable, Notion, or a basic Google Sheet. The tool matters less than the habit of keeping it updated.

Track things like:

• target investors

• stage and fit

• meetings scheduled

• notes and objections

• follow-ups

• diligence requests

• next steps

If you have someone helping you with the process, even better. Run it like a mini pipeline review each week. (Shocker…this is another space you could use AI to help you run a process. Claude would do nicely.)

Fundraising involves A LOT of conversations moving in parallel. Having a clear view of what’s happening keeps the whole thing from turning into a wild mess.

5. Know what kind of investor you actually want

This one can be tricky.

When you’re raising, it’s easy to feel like the goal is simply to get a “yes”, but investors become part of the company’s story for a long time.

So while you’re evaluating check size and stage fit, it’s also worth paying attention to a few other signals:

• Do you trust this person?

• Can you imagine being honest with them when things get hard?

• Do they seem curious about your business?

• Are they someone who can actually support you in the ways you’ll need?

Chemistry matters more than people sometimes admit.

Finding investors who are aligned with how you want to build can make a big difference over the long run.

A quick note after my last article

In my last piece, I wrote about the funding numbers for women founders and how much work there still is to do. (You can read it here if you missed it.)

The advice in this post applies to every founder raising capital, but I know many female founders are navigating additional dynamics inside the venture ecosystem. Annoyingly, preparation alone doesn’t fix those structural challenges. (More to come in future posts about how we can start tackling those additional dynamics.)

What preparation CAN do is make sure the fundamentals of the business and the story are clear when those conversations happen.

Clear messaging and process go a long way.

Fundraising always involves some storytelling, but the process also highlights how the company actually operates.

How clearly the team thinks.
How aligned people are.
How quickly the business can respond.

You don’t need everything perfectly figured out before you raise, but the more clarity and structure you bring into the process, the easier it becomes for someone on the investor side to understand what you’re building and advocate for it internally.

That is really the goal. Make it easy for the person across the table to walk into their partner meeting and say,

“I know exactly why this company matters.”

If you’re in the middle of fundraising prep and want a calm second brain on things, I still have a small number of founding member office hours spots for readers of this newsletter. ($99 for access to my paid articles and two 60-minute 1:1 sessions)

These are short working sessions where we can look at things like:

• Sharpening your fundraising narrative

• preparing your data room

• mapping out hiring after the round

• spotting operational gaps investors might notice

It’s intentionally lightweight and affordable because I know founders often just need a quick clarity pass, not a big consulting project. Choose founding member in the link below.

Subscribe now

Female-founded startups raised a record $73.6 billion in 2025.

Sounds great, right? Buuut there’s a catch.

Remove two companies (Anthropic and Scale AI) and that “record year” essentially disappears. :(

TWO companies are holding up the entire headline.

Meanwhile, all-female founding teams raised just 1.1% of venture capital in 2025. That number actually went down from 2.1% the year before. (I wrote about that, also sad, number in this article last year.)

So depending on how you write the headline, the story is either:

• Women founders are thriving

Or, you know…

• Women founders are still almost entirely shut out of venture capital

Both statements technically come from the same dataset. One just makes the system look better.

I’ve been thinking about this a lot lately because of the founders I work with.

One in particular.

She’s building a company in one of the most complicated data environments in healthcare.

Her days look like most founders’ days:

finance convos
product decisions
team leadership
regulatory hurdles

But there’s a second layer of work she does constantly.

She listens.

She notices when a process breaks.

She catches the moment when something that “should work” in theory clearly doesn’t in reality.

She pushes back on systems that have failed patients for years.

None of that shows up in venture funding statistics, but it’s the kind of work that actually builds companies worth funding.

The venture industry and publishers love to celebrate outliers. A massive round here. A unicorn there.

A headline that suggests the system is working, but most founders don’t live in those headlines.

They’re doing the slower, messier work of actually building something.

For women founders in particular, the bar is still very different.

You have to be exceptional just to be considered normal.

You have to prove the market twice.

You have to explain risks male founders are rarely asked about.

Sometimes you have to keep a company alive long enough for the system to even notice it exists.

I love seeing women founders succeed. Truly. It’s the best.

But if we’re going to celebrate progress, we should at least be honest about the numbers. A record year built on two companies isn’t a solved problem. It’s a reminder of how far we still have to go.

Still, I hope you had a great International Women’s Day. We deserve a celebration for all of the hard work!

“Can you fix our CRM?”
“We need better onboarding.”
“Our teams just need to communicate better.”

Sometimes that’s true, but most of the time the real issue shows up long before we open a dashboard or a tool.

Within the first hour, a few signals tell me how a company actually runs.

Not how someone tells me it runs.

How it runs when no one is looking.

Here are the first five things I check.

1. Is anything documented anywhere?

I usually start with a very simple question:

“Where do you keep documentation?”

Sometimes the answer is Notion.
Sometimes Google Docs.
Sometimes a messy internal wiki.

Other times, the answer is silence and a shy smile.

Early-stage companies often run on tribal knowledge.

Everyone “just knows” how things work.

Until someone leaves, a new hire shows up. or a customer asks a question that only one person can answer.

I’m not a monster; I am not looking for perfect SOPs, but I am looking for any signal that the company believes systems matter.

Even a rough manual, a messy playbook, or a half-built RACI framework tells me something important:

Someone has started turning knowledge into infrastructure.

If nothing is documented anywhere, the company isn’t scaling yet. They are a team of improvisers.

2. How does the team actually talk to each other?

Next, I look at the team’s actual communication. Not what one leader tells me.

• Do they have recurring leadership meetings?

• Is there a weekly cadence where teams align?

• Or does everything happen in Slack at random times of day?

I’ve said this many times, but Slack is one of the fastest ways to understand a company.

Sometimes it’s organized:

• clear channels
• decisions summarized
• threads used well

Other times it’s a stream of chaos with questions flying everywhere. decisions buried in threads, and the founder answering everything.

If a company doesn’t have clear communication rhythms, the founder becomes the router for every decision.

Which leads us to the next signal.

3. What tools are you using?

I always ask founders to walk me through their stack.

It usually sounds something like this:

HubSpot.
A support tool.
Stripe or billing software.
Product analytics.
A project management tool.
A knowledge base.

And then a few more tools snuggled their way in over time.

The tools themselves aren’t the problem.

What I’m really looking for is this:

Do these tools reflect a system… or a series of reactions?

Many early-stage companies accumulate software the way people accumulate kitchen gadgets. (And I am not judging, I LOVE a good kitchen gadget. Hello Ninja blender.)

Something broken? They add a tool that promises to fix it all fast.

Six months later you have:

• automations firing everywhere
• fields missing data
• marketing capturing information sales never uses
• customer success rebuilding context manually

At that point, the company doesn’t have a tech stack.

You’re looking at tool soup. (More on that here.)

4. Who is the glue person?

This question reveals almost everything. Every company has someone who holds things together.

The question is who. Sometimes it is the founder themselves. Other times it’s the stable operator. (Hi, hello, this was me.)

Whoever it is, it creates a hidden operating model where every question, need, and decision flows through one person.

The glue becomes the connective tissue for:

• sales questions
• customer escalations
• internal alignment
• product context

Which feels efficient.

Until growth makes it impossible.

The goal isn’t to eliminate that glue.

It’s to turn it into structure the company can use without the founder (or that person).

5. What metrics does the company actually run on?

This is the last thing I check.

No, not what metrics appear in decks. The ones that drive team behavior.

• Does the company have a clear North Star?

• Do teams know how their work contributes to it?

• Are there OKRs or operating goals connected to that number?

  • Or are people just busy all the time.

This is where many early-stage companies struggle.

Teams are working hard, but they’re not always moving in the same direction.

When metrics are unclear, progress becomes subjective. Which means decisions start happening based on instinct instead of shared targets.

The mistake I see founders make most often

When companies notice these problems, the instinct is usually the same.

Hire someone.

A new head of marketing.
A sales leader.
A RevOps person.

If the structure isn’t there yet, those hires inherit confusion instead of momentum.

Now instead of one overwhelmed founder…

You have multiple capable people trying to operate inside a system that hasn’t been defined.

Hiring doesn’t fix that, but a clear stable system? Now THAT can fix a lot.

What founders usually want when they bring me in

Most founders really don’t want a big operational overhaul.

They want the company to move faster, but what they’re really asking for is something simpler.

They want to stop being the bottleneck.

They want their teams to operate without needing them in every conversation.

They want the company to feel less fragile.

That’s what good operations does.

It turns founder knowledge into company capability.

A quick question to ask yourself

If you stepped away from your company for a week…

What would stall?

That answer usually reveals exactly where the structure is missing.

I have two advisory slots open if you want a friend to share a little of that mental load.

They handed off the task. They assigned the owner. They moved on.

Except… they’re checking in on it three times a day. Jumping into threads their team started. Making decisions their Head of CS should be making by now. Leading a zone they’re not even the best perso…

Read more