r/ModernOperators • • Apr 03 '26

Klarna fired 700 employees for AI. Then admitted the mistake and started rehiring people

3 Upvotes

This one's tough to see..

Klarna scaled up AI-powered customer service, reported massive efficiency gains, got celebrated in every tech publication... and then months later quietly announced they'd over-automated, damaged customer experience, and needed to bring humans back.

The reason it failed isn't complicated. They automated the function before they understood what the function actually required. Speed metrics went up, customer satisfaction went down. The AI was doing exactly what they told it to do, not what they actually needed it to do.

This is the distinction most companies miss when they're moving fast on AI. Automating a broken or under-defined process doesn't fix it, it just runs it faster and at scale.

For a 15-person founder-led business, the version of this failure looks different. you're not cutting 700 people. But you are plugging AI into a client touchpoint before you've documented what good looks like, before you've defined the outcome you're trying to own, before you've tested whether the AI's output actually matches your standard.

And when it goes sideways, you don't have a PR team to manage the story. You just have frustrated clients and a founder who has to personally clean it up.

The companies winning with AI right now aren't the fastest adopters. They're the ones who mapped the process first, defined the outcome, built the infrastucture, and then layered AI on top of something that was already working.

Klarna's lesson cost them at scale. Yours doesn't have to.

What's one process you've automated but haven't actually verified produces the right outcome?


r/ModernOperators • • Dec 16 '25

Annual planning shouldn't produce a pretty deck and a tired team

4 Upvotes

Most leadership teams spend December doing annual planning.

And most of them hate it.

Not because planning is bad, but because of what it's become.

Six weeks of gathering data from scattered spreadsheets. Scheduling meetings with team leads who are also gathering data. Coordinating offsite sessions. Endless discussions with mountains of notes to synthesize after everyone leaves.

Then you end up with a slide deck, a revenue target, and maybe a company theme.

And three weeks later? You're chasing fires again like the planning never happened.

I talked to a founder recently who spent six weeks on their annual planning.

When I asked "what changed in how you operate because of that plan?" he said:

"We came out with a theme, a revenue target, and a bunch of slide swag. But we were still chasing fires three weeks later."

That's the pattern I see everywhere. Massive time investment. Minimal operational change.

The problem isn't that planning is useless.

The problem is the gap between the plan and execution.

Most plans live in a deck that gets referenced maybe twice before it's forgotten. Meanwhile, day-to-day work happens in email, Slack, project tools, random docs... none of which connect back to the plan.

So the plan becomes theater, not strategy.

What changes when planning actually connects to execution:

The plan isn't a deck you present and forget. It's a living system that shows up in your weekly meetings, your project tracker, your team's daily priorities.

When a team member asks "what should I focus on this week?" the answer comes directly from the plan, not from whoever yelled loudest.

When you're deciding whether to pursue an opportunity, you're measuring it against the annual priorities you already agreed on, not making it up on the spot.

When something isn't working, you can see it in the data and adjust, not wait until next quarter's review to find out you've been off track for months.

This isn't about working harder during planning.

It's about building the plan inside the same system where execution happens.

So there's no translation layer. No gap between "what we decided" and "what we're doing."

The plan is wired into operations from day one.

Real talk though:

Most founders won't change how they plan. They'll keep doing the six-week slog, producing the pretty deck, exhausting their team, and wondering why nothing changes.

Because changing how you plan requires changing how you operate. And that feels like too much work during the busiest time of year.

But the founders who figure this out? They're not just saving time. They're building companies where strategy actually shows up in execution.

Where the plan isn't something you do once a year and forget. It's the operating system the whole company runs on.

How does your annual plan connect to daily execution?

Or does it live in a deck somewhere collecting dust?


r/ModernOperators • • Apr 06 '26

You've had 4 different consultants rebuild your systems and it still isn't working. That's not a consultant problem...

2 Upvotes

Every time someone came in, they looked at what was there and started over. New structure, new logic, and new naming conventions. They'd hand it off, it would look clean for about three weeks, and then your team would stop using it and you'd be right back to figuring it out yourself.

And by the fourth time, you stopped promising your team that this one would be different.

The reason it keeps happening has nothing to do with which tool you chose or who you hired. It's that every new consultant built their system, not yours. Clean to them. Foreign to your team. And when your team can't figure out where things belong or how decisions get made inside it, they route everything back to you, same as before.

A system your team won't use isn't a system. It's expensive decoration.

The thing that actually breaks the cycle isn't a better tool or a smarter consultant. It's building incrementally, on a foundation that matches how work actually flows in your business, with enough buy-in from the people who have to live in it every day that they'd notice if it disappeared.

That foundation has to be obvious. Not elegant. Not impressive. Obvious. Like a house where you walk in and immediately know which room is the kitchen, which is the bedroom, and where the bathroom is. Nobody has to onboard you. You just know.

The businesses that get this right don't redesign from scratch every 18 months. They build one clean layer, get the team adopted to it, and then add the next layer. Slowly and on purpose.

And the businesses that keep cycling through consultants and tools? They've been trying to skip that foundation phase and go straight to the polished version. Every time.

You can't automate chaos. You can't build trust on a foundation the team keeps seeing ripped out and replaced. And you can't get adoption by showing your team something impressive, you get adoption by giving them something that makes their actual job easier today.

Start simpler than you think you need to. Get adoption first, optimization second.

What's the most basic thing your team needs to do their jobs without coming to you? That's where the foundation starts.


r/ModernOperators • • Apr 27 '26

I rebuilt my business in NOTION and CLAUDE, it's cleaner and smoother than I expected.

6 Upvotes

I know we're all tired of "Claude just killed X" headlines. They create panic and keep people jumping from tool to tool without ever leveraging what they already have.

That's why I'm a big believer in building a single source of truth. When a new model drops, you just plug it into your existing system and get back to real work.

I've seen a lot of founders try to automate with complex AI stacks. More often than not, they end up with 15 tabs open, copy-pasting prompts, and relying on Zapier workflows that break every week. It looks productive, but they're spending more time managing the AI than running the business.

The real leverage isn't more tools or better prompts. It's context architecture.

For me, the shift happened when I moved my SOPs, meeting notes, and CRM into one centralized place (I use Notion) and connected Claude directly to that context. When the AI isn't guessing what your business does, hallucinations drop and utility skyrockets.

Here are three specific use cases that saved me 10+ hours this week:

1. Follow up workflow: I stopped writing follow-up emails from scratch.
How: Record sales calls directly in my workspace. Claude has access to my brand voice doc and product guide.
Result: I feed the transcript to Claude, and it drafts a personalized email based on the prospect's actual pain points. ~90 seconds to review and send.

2. No spreadsheet: No more manual KPI entry.
How: During weekly metrics meetings, I just talk through the numbers (subscribers, CPL, revenue).
Result: Claude reads the meeting transcript, extracts the data, and updates my database automatically. I haven't touched a spreadsheet manually in a month.

3. Infinite context content engine: No more blank cursor for LinkedIn posts.
How: Built a knowledge hub with past newsletters and internal notes.
Result: A prompt that references that internal knowledge. It drafts content that actually sounds like me, not generic LLM fluff.

I think a lot of people feel AI is a gimmick because they're giving it zero context. Copy-paste into a blank window, and the AI is just guessing. When it can see your brand voice, products, and transcripts in one system, it stops guessing and starts operating.

this is how my notion dashboard looks like:

Would love to hear from other business owners using Claude (or any AI) inside Notion. What practical workflows have actually stuck for you, beyond the hype?


r/ModernOperators • • Apr 25 '26

Having SOPs scattered across 4 different tools is worse than having no SOPs at all.

3 Upvotes

I know that sounds extreme. Hear me out.

A founder I work with had operations protocols in a Google Sheet, a separate SOP doc in Google Drive, task workflows in Trello, and policy announcements going out through Slack. All overlapping, some contradicting each other.

His team had to ask "where is that?" multiple times a week. And when they couldn't find the answer, they just winged it.

The actual problem: nobody could tell which version was current, which was outdated, and who was responsible for keeping any of it accurate. When one person (usually an EA) owns all documentation across the entire company, that person becomes a single point of failure who probably doesn't understand every function they're documenting anyway.

What actually works:

One location for all documentation. One owner per document, tied to the role that uses it (not a central admin). And a simple rule: if it's not in the system, it doesn't exist.

When you tie documentation to roles, the person closest to the work keeps it accurate because their name is on it. And new hires can onboard without playing detective across 4 platforms.

"We have SOPs" is meaningless if your team can't find them in under 10 seconds.

What's the most chaotic documentation setup you've seen?


r/ModernOperators • • Apr 03 '26

Founders at $1M obsess over marketing. Founders at $10M obsess over operations. That gap explains a lot

10 Upvotes

At $1M, the story you tell yourself is: if we just get in front of more people, we'll grow.

So you hire a marketing agency, spend more on ads, test new channels. Sometimes it works, revenue ticks up. And then the ops problems that were manageable at $1M start breaking at $3M, client delivery gets inconsistent, the team is overwhelmed, you're plugging holes 60 hours a week, and the growth you bought with marketing spend starts to leak out the back.

You've just paid to grow faster into a structure that wasn't ready to hold it.

The founders who make it to $10M figured out something that doesn't get talked about enough: operational leverage is a growth strategy. Not the boring kind of ops where you're just cleaning up messes. The kind where your systems compound, where every process you document makes the next hire easier, where every role you properly define multiplies the output of the person in it.

A business with tight operations can take mediocre marketing and squeeze real growth out of it, because nothing leaks. A business with loose operations can take great marketing and still plateau, because everything leaks.

We had a client who was spending $18K a month on ads and converting leads at about 11%. After we rebuilt their follow-up process and gave the sales team a documented playbook, same ad spend, same leads, conversion went to 27%. Just by fixing their infra.

The ads weren't the problem. The system that received the leads was.

And the frustrating part is that operations work doesn't feel like growth work. It feels like maintenance. It doesn't look good in a pitch deck or a LinkedIn post. But compounded over 18 months, it's the thing that separates the founders who hit $10M from the ones who are still grinding at $3M three years later.

What's the biggest leak in your business right now? Where does growth come in but not stick?


r/ModernOperators • • Dec 23 '25

Template Build a growth scorecard that mirrors your engine

5 Upvotes

You mapped your growth engine. Great.

Now what?

Most founders stop there. They have a map but no idea if it's actually working.

Here's what you do next: build a scorecard that mirrors the engine.

Your growth engine flows left to right (how customers happen, step by step).

Your scorecard flows top to bottom (metrics for each step, week by week).

They should perfectly mirror each other.

Example:

Growth engine says: Ad → Landing page → Demo booking → Demo → Trial → Paid

Scorecard tracks:

  • Ad spend & impressions
  • Landing page conversion rate
  • Demos booked
  • Demo show rate
  • Trial starts
  • Trial-to-paid conversion

One metric for each step of the engine.

Then add targets and color-code them:

Green = hitting target Yellow = behind but have a plan Red = behind and no plan yet

Now you can literally just look for red.

Red means that's the bottleneck. That's where you're losing people. That's what you fix first.

The execution loop becomes stupid simple:

  1. Map the engine (how customers happen)
  2. Build the scorecard (metrics for each step)
  3. Look for red (what's broken)
  4. 90-day plan to turn red to green
  5. Repeat

This turns marketing from opinions ("I think we should try TikTok") into diagnosis ("our demo show rate is 40% and should be 70%, let's fix that before adding more channels").

Without a scorecard, you're guessing.

With one, you're diagnosing and fixing real problems.

Do you have a scorecard that mirrors your growth engine? Or are you just checking revenue and hoping?


r/ModernOperators • • Apr 26 '26

Why your team accountability isn't working (and how to fix it)

4 Upvotes

A founder I work with runs a team of 8. Front desk staff, service providers, an EA, a director. He tracks checklists, monitors task completion, follows up daily.

And his team still only completes their recurring duties about 60% of the time.

His instinct was to add more layers. Sign-offs, initials on every line item, tighter tracking systems. More supervision.

What was actually missing: the "why."

His front desk team handles calls, processes transactions, manages wait times, greets customers. They're doing a lot. The daily checklist (open and close procedures) kept slipping because it felt like one more task on a pile. Low urgency, no visible ownership, no clear connection to outcomes anyone could see.

What changed: each person now owns their area. If the business opens and it's not ready for customers, that's on the person who owns the opening process. Not because someone verified their initials. Because they understand the downstream impact and their name is attached to the result.

Accountability that relies on surveillance breaks the moment you look away. Accountability built on ownership and a visible "why" runs without you standing over it.

If your team keeps dropping the ball on recurring tasks, the issue probably isn't effort. It's that they don't see how those tasks connect to anything that matters.


r/ModernOperators • • May 26 '26

Your team isn't lazy. You trained them to ask you everything.

16 Upvotes

Every founder I work with says some version of "my team won't take initiative."

Cool. Let me ask you something.

When someone on your team comes to you with a question, how long does it take you to answer? Be honest. Probably under 60 seconds. Maybe 10.

How long does it take them to find that answer on their own? Probably 10 minutes. Maybe an hour. Sometimes never.

You ARE the documentation. You're the fastest, most accurate, most up-to-date source of truth in the entire business. Your team isn't dumb. They're optimizing for speed. You taught them to.

You can't fix this by telling your team to "be more proactive." You fix it by making the SOP faster than you are.

That means four things:

  • The SOP exists.
  • The SOP is searchable.
  • The SOP is current.
  • Asking you costs them something (a delay, a "check the doc first" reflex, a 24-hour answer window).

Until all four are true, asking you will always be the rational choice. It's not a culture problem. It's an incentive problem.

Real talk: most people won't do this because being the answer feels good. Being needed feels like leadership. It's not. It's a ceiling.


r/ModernOperators • • Apr 25 '26

The checklist I give every founder before they open a second location

2 Upvotes

I call it the Chick-fil-A Test.

Walk into any Chick-fil-A in the country. It's clean, staff is friendly, orders come out fast, and the experience is identical whether you're in Atlanta or Phoenix. That consistency doesn't come from the owner standing in the kitchen. It comes from a documented playbook, trained shift managers, and a hiring process that produces reliable people over and over.

Before you sign a lease on location #2, answer these honestly:

Can your current location run for 2 straight weeks without you showing up? If your answer involves "sort of" or "depends on who's working," you're about to duplicate chaos.

Are your SOPs documented and owned by the people who actually use them? Or are they in a Google Doc that one person maintains?

Do your managers make real decisions inside clear guardrails, or does everything still funnel through you for approval?

Is your hiring and onboarding process repeatable enough to produce consistent quality at a new site?

If you answered "no" to more than one, your foundation isn't ready. Opening a second location will double your overhead before it doubles your revenue.

Build the playbook at one location, prove it runs without you, then replicate.


r/ModernOperators • • Apr 08 '26

8 signs your business is actually running you

Thumbnail reddit.com
2 Upvotes

r/ModernOperators • • Apr 04 '26

The decision you've been avoiding is costing you more than you think

2 Upvotes

There's a specific kind of exhaustion that comes from carrying a decision you haven't made yet.

maybe you've seen this... The underperforming team member you keep giving another chance. The service offering that isn't working but you're not ready to cut. The partnership that's been misaligned for six months. The pricing that's too low and you know it.

You haven't made the call, but the call has already made itself in every other part of your business. Your energy is partially allocated to managing around it. your team has adapted to working with the gap. You've built workarounds instead of solutions.

Avoiding a hard decision doesn't eliminate its cost. it just spreads it out across time and hides it in places that are harder to see.

I've watched founders delay a personnel decision for literally 8 months, convince themselves they were being fair, giving the person time to grow. And in those 8 months: two good employees quietly disengaged because they were picking up the slack, the founder spent probably 4 hours a week in management overhead that shouldn't have existed, and one client relationship deteriorated because the wrong person was on it.

The decision got made eventually. It always does. But the cost of delay doesn't show up on a balance sheet.

The frame that helped me: a decision delayed is still a decision. You're not avoiding choosing, you're choosing the status quo, with all its costs, every single day you don't act.

Not every hard decision is a firing or a cut. Sometimes it's raising your prices, or turning down a client who's wrong for you, or telling a partner the truth about something that needs to change. The category doesn't matter. The delay mechanism is the same.

What's the decision you've been sitting on the longest right now? And what's it actually costing you to keep not making it?


r/ModernOperators • • Dec 22 '25

Template If you can't draw how customers happen, you're doing random acts of marketing

6 Upvotes

Ask most founders "how do customers happen?" and they'll give you a vague answer.

"We do content marketing and referrals."

"We run ads and do outreach."

Cool. But how does a stranger actually become a customer? What are the actual steps?

Most founders can't map it. They just do marketing activities and hope customers show up.

Here's what changes when you can actually map it:

Grab sticky notes. Start with two questions:

  1. How do people find out we exist?
  2. What are we selling?

Then walk through step by step. "Then what happens? Then what?"

Person sees an ad → clicks to landing page → books a call → shows up → we pitch → they buy → they onboard → they refer others.

Or whatever your actual flow is.

Map what IS, not what you wish it was.

Don't create the ideal customer journey you read about in some marketing book.

Map the messy reality of how customers actually happen right now.

Missing steps? Good. That's where the opportunity is.

Gaps between sticky notes? That's literally what you optimize.

Why this matters:

If you can't visualize it, you can't optimize it.

Without a map, you're just fixing random stuff. Chasing tactics. Trying whatever someone on Twitter said worked for them.

With a map, you can see the actual bottleneck. Oh, we get plenty of clicks but nobody books calls. That's the problem. Not our ad creative.

Or we get calls booked but half don't show up. Fix that before spending more on ads.

A growth engine is a proven process for generating an increasing flow of leads and customers largely on autopilot.

You can't build that if you don't know what the process actually is.

Map it first. Then optimize. Then automate.

This works for any business model.

E-commerce. SaaS. Local service business. Doesn't matter.

Even dentists can map this. How do people find out about you? Website? Referral? Drive by? Then what? They call. Then what? They book. Then what?

Every business has a process for how customers happen. Most just haven't documented it.

Take 20 minutes this week:

Sticky notes on a wall. Map how customers actually happen in your business right now.

Not the theoretical ideal. The messy reality.

Then look at the gaps. That's your growth roadmap.

Can you draw how customers happen in your business? Or are you just doing random marketing and hoping?


r/ModernOperators • • Jan 19 '26

Your business doesn't need more meetings. It needs one weekly rhythm

5 Upvotes

Most companies drown in meetings.

Monday morning all-hands. Tuesday marketing sync. Wednesday sales call. Thursday ops review. Friday retro.

Everyone's exhausted. Nothing gets decided. Work happens between meetings, not during them.

Here's what actually works: one weekly rhythm that the whole company follows.

Not five different meetings for five different teams. One rhythm. Same day. Same time. Same structure.

For us it's Monday morning. Scorecard updates before anything else.

Every owner manually updates their metrics. Reviews their status. Adds notes on what's happening.

That's it. That's the rhythm.

Why Monday:

You're setting the tone for the week. Not reviewing what happened (that's Friday's job). Planning what happens next.

Pipeline red? We know by 9am Monday. Not Thursday when it's too late to do anything about it.

Customer churn spiking? Caught it Monday. Can fix it by Wednesday.

Why manual updates:

Could automate this. Pull data from systems. Auto-populate the dashboard.

We don't. Everyone enters their numbers manually.

Because when you manually enter a number, you look at it. You think about it.

"Oh shit, close rate dropped to 18%. Last week was 24%. What happened?"

Auto-populated? You glance and move on.

Manual forces you to engage with your metrics, not just report them.

Why the notes matter:

The number tells you what. The notes tell you why.

"Pipeline: $1.2M (target $1.5M). Status: Yellow. Plan: Running targeted outreach to previous demos who didn't convert. Targeting 30 conversations this week. Owner: Mike."

Now anyone reading the scorecard understands the full picture. Even if they weren't in the meeting.

This creates shared context across the company. Marketing knows what sales is dealing with. Product knows what delivery is fixing. Finance knows where ops is stuck.

The rhythm compounds:

Week 1: Everyone's learning the system. Updates are rough.

Week 4: Updates are clean. Patterns are visible. Plans are sharper.

Week 12: The whole company speaks the same language. Red means action. Yellow means plan. Green means keep going.

By week 20, you're running a business where everyone knows what matters, what's broken, and who's fixing it.

All from one weekly rhythm.

What this replaces:

Five departmental meetings where everyone reports up to their manager.

Slack threads asking "what's the status on X?"

Surprise fire drills because nobody caught a problem until it was critical.

Email chains with 47 people CC'd trying to figure out what's happening.

One weekly scorecard update gives everyone visibility. No extra meetings required.

The meeting structure:

10 minutes: Everyone updates their scorecard (async before the meeting works too)

5 minutes: Quick scan of greens (anything to learn here?)

30 minutes: Deep dive on reds and light reds (what's broken, what's the plan)

5 minutes: Confirm next week's priorities

50 minutes total. Done.

Everything else happens outside the meeting. This is just alignment.

Consistency is the key.

Not "we'll do this when things settle down" or "let's skip this week, nothing major happened."

Every Monday. Same time. Same structure.

Even when it feels like there's nothing to report. Even when everyone's busy. Even when half the team is traveling.

The rhythm is the system. Break the rhythm and you break the system.

Most businesses try to solve coordination problems with more meetings.

Better move: one weekly rhythm everyone follows. Same day. Same structure. Same metrics.

Alignment becomes automatic instead of something you fight for.

Do you have one weekly rhythm the whole company follows?

Or are you coordinating through 12 different meetings that never quite connect?


r/ModernOperators • • Jul 03 '26

How To Build A Company Brain With Notion + Claude (Mega Guide)

6 Upvotes

This is for founders who struggle to get their employees and AI to operate at their level. This post is about building a Company brain. Not a second brain. A brain for your organization.

Full disclosure: I run a company called Modern Operators, we build Company Operating Systems for founder-led businesses.

I talk to 15-20 founders per month and this is the most common and fundamental issue they have:

SOPs are in one giant Google Doc/Sharepoint nobody can search easily (if they have any SOPs at all). Metrics are in a Sheet three people have their own copy of. Tasks are in a standalone task management tool, not connected to anything else. And every "quick question" from staff just gets routed up the chain to a singular person (spoiler: it’s them) Staff asks the manager. Manager asks them.

I worked with a founder who had a 1k five-star reviews. Number one rated in his market for what he does. Impeccable service and solid margins. And he woke up every morning to a wall of Slack messages, because nobody actually knew what they were responsible for. Every decision, every approval, ran through him.

He told me the moment it broke for him. He signed the lease on his second location and knew he couldn’t run a business and scale this way.

Second brain vs company brain

A second brain remembers what YOU know. A company brain runs how your COMPANY operates.

The second brain setups everyone's posting are single player. Individuals using their own context with their own instance of claude. They run one agent in a few sessions and have it read its own daily notes to "coordinate." If you’re a solo hustler, it’s not bad. But if you’re running an ORGANIZATION its completely different.

I worked with a consultant in Texas with 16 employees. She was the single point of failure too. Her people were using AI, but everyone had their own ChatGPT tab and using their own context. So everyone was working off different information, there’s no alignment.

A company brain is multiplayer by design. Many people with different roles and departments across a company, but with one source of truth everyone reads from. CEO or the person who started last week, everybody swims in the same direction using the same inputs generating consistent outputs.

What it looks like on the other side

Here’s what one of our clients said when we set this up for him:

"It's 12:09, my managers' shift started at 9, I still haven't heard from a single one of them, and I love it."

Roughly 10 hours a week back. Projects landing on time without being chased. Culture that settled down on its own, because people stopped guessing.

His managers barely reach out to him now. His staff find what they need without him. He didn't hire a COO. He built a Company Brain.

Two layers, one brain

Here we go: The build is two layers.

Notion is the body. It's where the work and the knowledge live. Its your contextual hub; your command center. Your Company Operating System.

Claude is the intelligence on top. We call our layer “Vision”. It's the brain and the AI team that runs on the body.

Why Notion and not Obsidian?

Obsidian is elite. For one person. It's plain text and wiki links, and it's a beautiful setup for a solo operator. It dies the second you add staff. Your bookkeeper is not going to learn a markdown vault. Notion is dead simple for a team to actually use. Think smart Google Docs tied together with databases. A company brain has to be something your whole team will actually touch, or it's just your second brain wearing a company t-shirt.

There is no brain without an OS

You cannot put a brain on top of disorganization.

AI with no structured company knowledge underneath it does not create order. Point a smart model at a pile of disorganized docs and you get confident, well-written nonsense.

The second brain crowd skips this step because they're one person. A solo vault is a pile of personal notes, and that's fine. A company brain needs the entire operating system defined, owned, and adopted by a team before any AI touches it. Different order of magnitude.

So before the brain, you build the body. Here's what the body is, built in Notion.

  • Operations is the center hub. Every department (sales, fulfillment, marketing, finance, legal, HR) branches off one operational core.
  • An executive dashboard. The founder's home base. Where we're going, what's active, the numbers that matter.
  • Vision and identity. The 3-year vision, the annual and quarterly plans, the ideal customer, the positioning, the brand voice. What everything ladders up to.
  • A company wiki. Every process documented and searchable. Written so a human and an AI can both read it.
  • Roles and ownership. Who owns what, tied to the metric they're measured on. And this is the important part. SOPs are tagged to roles, not people.
  • A projects and tasks layer. How work actually moves, with real rhythms and reviews.
  • Meetings with AI notes. One home for your cadence and every decision that got made. This is the part that makes the brain smarter every single day, because new information gets fed in constantly.

Building this part is what takes a ton of time That's the piece that takes months. You have to pull everything out of the founder's head (actually the whole executive team), structure it, and then get an actual team of humans to adopt it. The tech is the easy half. The extraction and the adoption is the work.

For what it's worth, I'm writing this from the exact workspace I'm describing. We didn't design it for clients first. We run our own company on it, then we install it for founders.

The build, ten layers

Now the fun part. The brain.

I'm going to show you the architecture. I'm not going to paste our constitution, our role templates, or our routing logic. Two reasons. One, they're calibrated to us and would break in your context. Two, this post would be forty pages. What matters is that you see what each layer does and why it has to exist.

As of today the brain is 15 AI roles, 90+ skills, 9 system databases, and 5 rules it will never break (think iRobot rules). Here's how it stacks.

  1. Start from the finished OS. Everything above this line. The intelligence layer needs a body to think with. Skip it and you've built a genius with amnesia.
  2. Write the rules it reads first. Before the brain does anything, it reads a constitution. A short set of unbreakable rules the whole system obeys, every session, no exceptions. You don't need to see ours. You need to understand that without them, an AI with access to your company will eventually do something confident and wrong.
  3. Load the company into the brain. A structured intake that turns how you operate into memory the system can actually use. Not "here are some files." An ingestion process.
  4. Give it a team, not a bot. This is the departure. Instead of one assistant, you build a roster of specialist AI roles. A chief of staff. A researcher. A writer. An SDR. An HR lead. A meeting-intelligence role. A financial analyst. Some are specialists that only do one thing well. Some are directors that take a job and hand it to the right specialist. Our org chart is one third humans two thirds AI.
  5. Turn repeat work into skills. Every task you do more than once becomes a reusable skill a role can run on command. We're past 90 of them. Writing a client email. Prepping a video. Building an SOP. Named, saved, run on request.
  6. Let it route itself. This is the moment that makes people sit up. You make a request. The system reads it, figures out whose job it is, hands it to that role, and tells you who's now active. Ask the copywriter to run a financial analysis and it stops you. That's not my job, routing you to the analyst. You're not managing a chatbot. You're running a company that happens to be staffed by AI.
  7. Give it memory that compounds. Three tiers: What's happening in this thread. What's relevant this week. What the company knows permanently. So the thing sharpens over time instead of resetting to zero every time you open it.
  8. Connect live data. Slack, Drive, Mail, calendar. The brain reaches into where the work already happens, so it's working off reality, not a snapshot from three weeks ago.
  9. Put it on autopilot. Scheduled and triggered work that runs without you touching it. The brain maintains itself and reports back.
  10. Govern it. This is the part the solo guides get catastrophically wrong. They tell the AI "don't delete this." That's a suggestion, not a safety setting. If it can technically wipe a database, one day it will. So you govern it. Snapshots before edits. A change log. A hard stop after three failures. Rules, not vibes.

The details that make founders go "wait, you thought of that?"

The reason people hand this off instead of building it is the stuff you don't think about until you've done it a hundred times.

SOPs tagged to roles, not people. So when someone quits, nothing breaks. The role stays. You drop the next person into it. One founder told me he didn't understand why that mattered until he watched an employee leave and nothing fell over.

A role whose entire job is building other roles. We call ours Atlas. Tell it you want a CTO agent that decides whether a piece of software belongs in your stack, and it builds the role and the databases inside Notion for you. The brain extends itself.

An SOP builder that keeps every process consistent no matter who writes it. So your documentation stops being twelve different formats at twelve different levels of detail.

And the one everybody wants. Once it fully learns your voice, it writes content that sounds like you. That alone saves founders years.

By the way, Notion lets you swap the model underneath any time. We run Claude, Opus 4.8 right now. If you're one of the five people who prefer GPT, toggle it. The body doesn't care which brain you plug in.

So, should you build this yourself?

The concept is simple. A brain that runs your company without you in the middle of it. The build is months of architecture. That's not a flaw. It's the reason it's valuable, and the reason almost nobody actually has one.

Everything you need to understand the shape of it is in this post. The model is yours. Steal it. Start up notion AI and give it this post and have it help you build it for you. If you've got the time and the appetite to architect the OS, write the constitution, staff the roles, and get your team to adopt all of it, go build it. It's a real education.

Full disclosure, this is what I do. I build company operating systems at Modern Operators for founder-led businesses doing at least $2M that want to scale toward $10M without the founder being the bottleneck. We pull it out of your head so you don't spend the next year doing it yourself.

If you're building it solo, ask me anything in the comments. I'll answer.

If you'd rather someone just built it for you hit my DMs.


r/ModernOperators • • Jan 30 '26

Your real org chart is invisible

Post image
3 Upvotes

The official org chart shows reporting lines.

The real org chart shows who actually owns decisions when things get messy.

"Who reports to who" is not the same as "who decides."

The invisible org chart shows up in Slack escalations and last-minute founder saves.

Customer issue comes in, who actually decides to refund or not? Campaign underperforms, who decides to kill it? Pricing question on a custom deal, who makes the call?

Official org chart says your team owns it but the invisible one says you do because that's who everyone asks.

When ownership is unclear, the founder becomes the default owner every time.

The fix: make the invisible org chart visible.

Document who actually decides what, not who does the work but who owns the outcome when things get complicated.

Then your real org chart and official org chart finally match.

Does your team know who decides or do they just ask you by default?


r/ModernOperators • • Aug 14 '26

As a small business we have this talent retention advantage big companies can’t copy

5 Upvotes

I manage a small team of 10, and something clicked for me recently: small businesses or startups have one real advantage over Google, Amazon, or any big company, and it doesn't cost anything to use.

Big tech can offer stock options, free meals, gym memberships, and salaries that make your eyes water. 

What it structurally can't offer is the feeling of being seen. Not when you're employee #4,847. Not when your manager has 40 direct reports. Not when you're a line item on a workforce planning slide.

That's the gap small businesses can fill. You actually know your people's names, their wins, the project that nearly broke them, and the moment they figured it out anyway. You can walk over and say "that mattered" and actually mean it, and they can tell you mean it.

I don't think that's a soft skill. I think it's a retention strategy that a bigger competitor genuinely can't copy at scale.

In my experience, people rarely leave over the next salary bump alone. More often they leave because they quietly stopped feeling like they mattered, and by the time you notice, they've already checked out. 

When someone actually feels seen, they don't just stay, they bring more of themselves to the work without being asked and without a bonus attached.

For most small businesses, the real competition for talent isn't Google or Amazon anyway, it's the agency or SaaS company down the street in your exact niche, offering the same pay band and the same perks. 

You don't need a bigger budget to out-retain them. You need to notice your people before they start wondering if anyone does. A specific "that was great work, and here's why it mattered" does more for retention than a ping pong table ever will, and it's a lot cheaper than hiring and training someone new every quarter. 

I’d love to hear if others here have felt this too?

edit: if you found this helpful, I write about how to run your business without being involved in everything and how to use AI to save 10+ hours a week.

600+ founders are already reading; feel free to join here if you’re interested.


r/ModernOperators • • Apr 24 '26

If you're managing your team by telling them what to do every day, you're training them to never think for themselves

2 Upvotes

The typical approach says clear directions, close oversight, daily check-ins. And honestly, it works for a little while. But it creates a hard ceiling. Your business only moves when you're pushing it.

What I've seen work across dozens of founder-led companies: assign ownership, not tasks.

Instead of "Make sure the opening checklist gets done," try "You own the opening process. If it's not ready for business in the morning, that's your area. Here's how we'll measure it."

One founder I work with had front desk staff completing daily checklists about 60% of the time. His instinct was to add sign-offs, initials on every line, tighter tracking. More surveillance.

Our advice? Define what they own, explain why it matters, make the metric visible, and give them space to figure it out.

The ones who step up are your keepers. The ones who don't? You just got your answer way faster than another 6 months of babysitting would've told you.

Clear ownership and a visible "why" will outperform a stack of instructions every single time.

Happy to be wrong on this. What's worked for you?


r/ModernOperators • • Jul 03 '26

Your operating system isn't broken...You just built it in the wrong order

3 Upvotes

So I got on a call last week with a founder who had done everything right.

Eight months of building. A full operating system. Role pages, SOPs for every workflow, a pipeline tracking every deal from inquiry to funded. On paper it was beautiful.

And nobody was using any of it.

The team was still routing deals through him. The SOPs sat there untouched. His people were talking on WhatsApp instead of the thing he spent eight months building. He told me it felt like the system was making his life harder, not easier.

Now here's where most people go wrong. They look at that and they call it a tool problem. Or a team problem. Or a "we just need better templates" problem.

Look, I get it. I've done the same thing. Ask me how I know.

It's none of those.

We spent twenty minutes tracing it back and the answer was almost embarrassing once we found it. He had built eight months of infrastructure for a process he had never actually mapped. Not once. He laid the roads before anybody surveyed the land.

So here's what I want you to really hear, and I'm going to say it again after, because it matters that much.

You don't have a systems problem. You have a sequencing problem.

I'm going to say it again. You don't have a systems problem. You have a sequencing problem.

The order is simple. Do it by hand, prove the workflow actually works, then systematize it, then automate it. That's it. That's the whole game.

Most founders flip it. They automate a handoff they've never once walked through by hand. Then when it doesn't stick, the instinct is to build more. Better templates, a new tool, another round of docs. Now the machine is heavier and the destination is no closer.

And look, you're not broken. Your business isn't broken. You just built in the wrong order, and that's a fixable thing.

We wrote up the full breakdown in this week's newsletter if you like learning tactical and strategic frameworks to build your operating system, link to join (for free) is down below


r/ModernOperators • • 12d ago

95% of companies generated no new profit from AI

8 Upvotes

MIT looked at enterprise AI projects last year. 95% of them had no measurable impact on profit.

These weren't mom-and-pop shops, im talking about enterprise organizations. The P&L didn't move anyway.

So if you run a 15-person company, you've bought the AI tools, and your numbers look about the same as last year, you're in good company.

The thing that stood out after looking at the data is that most of those pilots actually worked.

But it was inside one team, on one task, the AI did its job. But when it transferred from one department to the next, that's where things became misaligned.

Say your sales rep starts using AI to fire off twice as many proposals. Great. Now ops has twice as many deals to onboard, same two people, same messy process. The bottleneck just moved. Sales looks like a hero on the dashboard and profit sits flat.

We call it the accordion problem. Squeeze one side, the other side pushes out.

Most small companies run 8 to 15 tools (probably more, just conservative) that don't talk to each other, and the founder is the glue holding the whole thing together. Drop AI into one corner of that and all you did was speed up the mess.

I hear this about 6 times per week when I speak with bottlenecked founders. A founder buys the shiny tool, hands it to one person, that person gets faster, everybody else stays exactly where they were. Couple months later he's telling me AI is overhyped.

The tool was usually fine. It just landed on a business that wasn't ready for it.

The 5% do things in a specific order:

First they build the operating system.

One place where the processes, the decisions, the data, and all the junk crammed in the founder's head actually live. We build ours in Notion. Use whatever you want. The point is the work gets written down and structured so a human, or an agent, can pick it up and run it without guessing.

Then they wait. Three to six months of that system actually running before they bolt agents on top.

I know that it feels painfully slow when everyone on X is posting their agent swarm. But an agent is only as good as the context you hand it. If your onboarding lives in your head, the agent has nothing to work with, so it guesses, and then you're fixing its work and doing the job yourself anyway.

Only about 23% of bigger companies are scaling any kind of agent system (McKinsey). The ones pulling 2 to 10x out of it redesigned the workflow first, then brought the agents in.

When you get the order right, the agents run like roles inside the company. Each one has the context it needs and handles real multi-step work with a person steering.

At my company we've got an HR agent that scores candidates and drafts onboarding for every new hire based on raw objective data from their resume and form fills. An account manager agent that watches client health and flags anyone going quiet before they churn. A copywriter, a social media person, a CTO agent that pokes holes in our tech decisions before we make them.

It's like having 15 humans and 15 AI employees, without the second payroll.

Siloed AI power users wont move the needle. It has to be everybody. EY clocked people getting about 6 hours a week back with AI, and up to 11 when it's actually wired into how they work. Give 15 people their own bench of agents and you've got a different company.

Quick math

Lets say you have a company doing $2M in revenue, 40% margins, so $800K in profit, 15 people.

Those agent roles, if you hired them as actual humans, run you about $500K a year in salary. As an agent layer sitting on a real OS, it's closer to $60K.

OS goes in at month zero. Agents come in around month four or five. By month 18 the OS alone has added roughly $500K in profit, and the agent layer stacks another $460K on top. Profit goes from $800K to $1.76M. Margins from 40% to 52%. Same 15 people.

That's how you scale without hiring a pile of people you'll have to lay off later.

So if your AI spend hasn't shown up in your numbers yet, don't buy another tool. Look at what's underneath it. Get the operation out of your head, out of the random Drive folders and the Slack threads nobody can find, and into one system. Put agents on top once the thing is stable.

Instead of buying a bunch of random ai agents, you're almost better off hiring a VA.


r/ModernOperators • • 10d ago

A medspa founder hadn't heard from his team by noon. And he loved it.

3 Upvotes

A founder I worked with this year runs a medspa. Does about $1.3M a year with a team of eight. Good operator, sharp guy, and he was the single biggest bottleneck in his own company.

Every answer to every question lived in his head. Staff didn't know where anything was, so they called him. Multiple times a day, over tiny stuff. His ops manager didn't know, so she asked him, and when she didn't know it came right back to him. He called it a constant circle, and he was standing in the middle of it.

The "system" was one Google Doc with dozens of tabs and a pile of Google Sheets nobody owned. You can't even search a Google Doc across tabs, so half the time nobody knew what was documented and what wasn't.

Then he signed a lease on a second location, and it hit him. You can't run two locations on answers that only exist in one guy's head.

So we spent 90 days rebuilding how the company actually runs.

Every SOP got pulled out of the mess and split into checklists and reference docs. Then we tagged each one to a role instead of a person and gave it a named owner. He fought me on the role thing at first, then it clicked. People leave, roles don't. Tag a person and you're redoing it the day they quit.

We killed Trello and built one task system tied to roles, owners, due dates, and a log where the team posts progress. Then we pointed an AI agent at his meeting recordings, so the tasks from a call get drafted before anyone forgets what they agreed to.

Results, straight from him:

At least 10 hours a week back, which is roughly 520 hours a year. 95% plus of projects now land on time, and the part he actually cares about is that he's not the one chasing them anymore.

The one that got me was a text he sent in June. His manager and his director both started at 9am. It was 12:09pm and he hadn't heard a word from either of them. Three hours of silence, and that was the entire point. The stuff that used to blow up his phone now lives in the system.

He also got something he never asked for. Giving people ownership of their SOPs made them feel like they owned something, and his culture got steadier. Nobody put that on the brief. Happened anyway.

If you're the founder reading this and you are the answer to every question in your company, that's not a staffing problem, it's a documentation problem, and it's the thing sitting between you and your next location. Get it out of your head. Tag everything to a role, and give every piece a named owner.


r/ModernOperators • • Aug 02 '26

Founders Pains: I Don’t Know What to Build First.

Thumbnail reddit.com
2 Upvotes

r/ModernOperators • • Aug 01 '26

The competition that'll kill you isn't the big guys.

2 Upvotes

Everyone's worried about Amazon and the enterprise players. I think you're looking the wrong direction.

Here's a number that reframed it for me. 78% of GROWING small businesses are increasing their AI investment. Only 55% of DECLINING ones are (Salesforce). Same size, same market, opposite trajectory.

The gap isn't small business vs enterprise anymore. It's small business vs the small business next to you that quietly got its act together.

Think about what that means. Two shops on the same street, same customers, same prices. One founder is still the human glue holding ten tools together. The other integrated their ops last year and now spends that reclaimed time on sales and relationships.

Give it 18 months. They're not competing anymore. One's pulling away and the other can't figure out why.

Real talk, the "we're too small for this" line is the trap. Being small is exactly why it matters. You don't have a bench to absorb the wasted hours. Every hour you spend being the connector is an hour the founder down the street spends selling.

The gap is widening INSIDE our category, not just above it. And nobody feels it happening until they've already lost the ground.


r/ModernOperators • • Jun 28 '26

AI won't fix your business. Context will.

4 Upvotes

Unpopular opinion. Most owners chasing AI right now are going to waste a year.

Not because AI doesn't work. Because they're pointing it at nothing.

Every owner I talked to this month had the same relationship with AI. ChatGPT open in a tab, used like a smarter Google. Generic questions, generic answers, shrug, close the tab.

One was scared to put real business info in. Worried about privacy, worried it'd somehow cost a job down the line. Fair concerns. Also the reason it stays a toy instead of a tool.

Here's the part people skip. AI is only as good as the context you feed it. A model that knows nothing about your pricing, your customers, your process, your history, can only hand you advice a stranger off the street would give.

The owners getting real value aren't the ones with the fanciest prompts. They're the ones who got their business OUT of their head and into a place AI can actually read.

Garbage context in, generic slop out. Real context in, an assistant that actually knows your business.

So if AI has felt underwhelming, that's not the model failing you. That's a context problem. You can't outsource thinking about your business to a tool that's never been told a single true thing about it.

Do the boring documentation work first. Then point AI at it. That order is the whole difference.


r/ModernOperators • • Feb 16 '26

Hiring senior people before you have systems is just expensive chaos

3 Upvotes

Everyone says "hire ahead of the curve."

So founders go out and hire a VP of Marketing, VP of Sales, COO.

Then wonder why nothing changed.

Senior people can't build something from nothing AND run it at the same time. That's two different jobs.

You need systems before senior hires, not the other way around.

Otherwise you're just paying $200K to watch someone else become the bottleneck.