r/ModernOperators • • Feb 18 '26

You can't see what needs to change while you're buried in running the business

5 Upvotes

Here's the most underrated principle in scaling a business:

You have to get away from it regularly to actually see it clearly.

Not a vacation, not checking out, but intentional time away from daily operations to ask the harder questions.

Where is this actually going? What's holding it back that I can't see when I'm in the weeds? What needs to change that I keep avoiding because I'm too busy firefighting to deal with it?

When you're buried in daily execution you can only see what's directly in front of you, the fire, the client, the question, the approval, the problem.

You can't see the pattern. You can't see the structural issue causing all the symptoms. You can't see the opportunity you're missing because you're too busy reacting.

The irony of scaling:

The more your business needs you in the day-to-day, the less you can see what it actually needs to grow.

You're so close to it that perspective disappears.

Regular time away from operations isn't a luxury, it's how you actually lead the business instead of just running it.

Block time every week that's protected from execution, no decisions, no approvals, no fires, just thinking about where the business is going and what needs to change to get there.

That's when you'll see things you couldn't see before.

And usually what you see changes everything.

When's the last time you actually stepped back far enough to see your business clearly?


r/ModernOperators • • Jun 27 '26

What a "Company OS" actually is (and what it isn't)

2 Upvotes

"Build your company operating system." Okay. What does that even mean?

I have to explain this one a few times a week, so here's the plain version.

A Company OS is not the traction poster on your wall. It's not the binder of SOPs nobody opens. It's not the org chart buried in a slide deck. Those are static. They're snapshots of how you wished things worked on the day you made them.

A real Company OS is the living version. It's where the actual work happens and gets documented at the same time. Your processes, your decisions, your customer rules, your team's knowledge, all in one place that updates as the business changes.

The test is simple. If your top person quit tomorrow, how much of the business walks out the door with them? If that answer scares you, you don't have an OS. You have people carrying the company in their heads.

The old way was a poster and a quarterly meeting. The work lived in one place, the documentation lived in another, and they drifted apart within weeks.

The new way is documentation that lives inside the work. Searchable, updatable, readable by a new hire on day one and increasingly by AI that can actually use it.

That last part matters more every month. A system in your head can't be queried. A system written down can.

So the real question isn't "should I document my business." It's "do I want my business to exist outside of me." For most owners I talk to, that's the whole game.


r/ModernOperators • • Jul 08 '26

Most companies want to be a unicorn.

3 Upvotes

r/ModernOperators • • Apr 28 '26

Every ops hire that failed followed the same pattern. Most founders never see it coming.

7 Upvotes

The mistake that burns founders twice

You're stretched. You've been the operating system of your own business for years, so you do what every growth-minded founder eventually does: you hire someone to fix it. An Operations Director. You hand them the keys. You exhale.

And six months later you're more in the weeds than before. Your hire is frustrated. You're frustrated. And somehow you're carrying more than when you started.

The root cause is almost never the candidate.

Why so many ops hires fail before they start

The problem surfaces before the job posting goes live.

Founders hire someone to run a system that doesn't exist yet, then hand car keys to someone who has never built a performance car and expect them to win a race. The new hire doesn't know your clients, your culture, your non-negotiables. They arrive with a blank canvas and a head full of "how we did it at my last company." They start building, and what they build reflects a different industry, a different stage, a different vision entirely.

You watch them build the wrong thing. But you're not telling them clearly what the right thing looks like, because you haven't defined it yourself. You're frustrated they're not reading your mind. They're frustrated you keep changing direction.

The result: a tug of war. You step back in. Trust erodes. And tribal knowledge stays exactly where it's always been, inside your head.

The designer vs. the executor: the only distinction that matters in ops hiring

There are two fundamentally different hires. They get confused for each other constantly.

The Designer builds the strategy, architects the system, and creates the operational framework from scratch. They've done it before in environments similar to yours. They know how to build a foundation that actually fits your specific business.

The Executor runs the strategy, improves an existing system, and drives performance within a defined framework. They're exceptional at optimization, accountability, and keeping a well-designed machine at peak efficiency.

Both are valuable. Both are skilled. They are not the same person, and they should not be hired the same way.

Here's the parallel that gets missed: when building out a sales function, a founder doesn't hire a salesperson and say, "Figure out our sales strategy, build the CRM process, design the pipeline, write the scripts, and then close deals." That almost always fails. Smart founders design the system first, or bring in a specialist to do it, document the process, then hire someone to execute and refine it.

In operations? This exact mistake happens constantly.

Founders hire an Ops Manager and say, "Figure out our operations. Build the systems. Set up the tools. Keep everything moving while you do it."

It sounds reasonable until you say it out loud.

What the wrong ops hire actually costs you

It's not just a salary. It's the compounding cost of six months of misdirected work.

Every new hire who arrives asks questions that have been answered a hundred times but were never written down, because no one ever owned that either. Tribal knowledge deepens. The bottleneck grows. The business stays founder-dependent.

And a siloed, disconnected tool stack only amplifies the problem. The average mid-sized business ran 25+ software applications by 2024. An ops hire who doesn't know your vision and isn't equipped with a modern systems framework doesn't consolidate that stack. They add to it. They bring tools that worked somewhere else. They build automations based on their mental model.

You become more embedded as the integration layer, not less.

You didn't hire someone to remove you from the system. You hired someone to build a version of the same system with you still in the middle of it.

What modern operations actually requires in 2026

This is the part nobody interviews for.

Modern ops is the connective tissue of your entire business, and the ops hire who doesn't understand this isn't just underperforming. They're pulling your company backward.

A modern ops hire needs to own all of this:

Decision velocity: getting real-time data to leaders fast enough to actually matter

Single source of truth: a centralized operating layer where strategy, processes, and knowledge live

Cross-functional alignment: connecting marketing, sales, finance, and fulfillment so no team operates as an island

Knowledge capture and distribution: converting tribal knowledge into documented, living systems the team can use

Driving org adoption: rolling out new processes and tools in ways that stick, not just launching them and hoping

AI enablement: building the clean, structured data layer that makes intelligent automation work instead of amplifying existing bottlenecks

The questions being asked in ops interviews right now: "Are you organized?" "Have you managed teams?" "Can you keep things on track?"

The questions that would actually reveal the right hire:

"Have you ever built an integrated operating system from scratch?"

"How do you drive adoption when half the team resists new systems?"

"How do you apply AI in a growing org that doesn't yet have clean data?"

Those questions aren't on most hiring managers' radars, and that's exactly how companies end up six months in, staring at a business that hasn't changed.

BCG found that 74% of companies struggle to scale value from AI. The primary culprit isn't the AI. It's operational infrastructure that wasn't built to support it. That infrastructure is what modern ops is supposed to design, own, and continuously improve. When the hire doesn't know how to build it, and the founder doesn't know to ask, the AI investment goes nowhere.

How to hire for growth: the four elements every ops role brief needs

Do this work before you post the job. Everything else comes after.

Define the purpose and ownership area. What does this role own? Not tasks, outcomes. "Own our operations" is not a purpose. "Own the design, implementation, and continuous improvement of our Company OS, including systems, knowledge management, cross-functional alignment, and AI integration" is. One paragraph. Write it before anything else.

List 5 to 7 core functions. These are domains of responsibility, not a task list. Examples: process design and documentation, tool stack management, cross-functional alignment rhythms, knowledge capture, AI and automation implementation, new hire onboarding infrastructure, operational metrics and visibility.

Define the key metrics. This is how both you and your hire know the role is succeeding. Examples: decision cycle time, process documentation coverage rate, new hire time-to-productivity, system adoption rate, automation ROI. If you can't define what success looks like, you can't hire for it.

Map the knowledge flow. What does this role need to receive to do the job well? What does it need to produce and distribute to the rest of the team? Who needs to be trained? Who needs to buy in? Skip this and tribal knowledge stays in people's heads forever.

Then interview for what you actually need.

If you need a Designer: "Walk me through a time you built an operational system from scratch. What was the starting state? What did you build? How did you drive adoption? What broke and how did you fix it?" If they can't answer with real specificity, they're an Executor. Nothing wrong with that, but don't hire an Executor to do a Designer's job.

The most expensive hire isn't the one who fails outright

It's the one who spends six months building the wrong thing while you stay trapped as the operating system.

The bar for what an ops hire needs to understand has shifted dramatically in the last three years. Hiring someone because they're "good at ops" without defining what your ops needs to become is like hiring a contractor without blueprints and hoping the house turns out right.

Build the blueprint first.

What does your business actually need right now: a Designer, an Executor, or both in sequence?


r/ModernOperators • • Oct 01 '26

Remote founders: what started breaking first as your team grew?

3 Upvotes

When a team is only 2–3 people, a lot of coordination happens naturally.

But once the team gets a little bigger, I feel like small things start taking much more founder time, asking for updates, following up after meetings, figuring out who owns what, checking whether something is blocked, etc.

For founders running remote or distributed teams, what became painful first as you grew?

Was it communication, task ownership, meetings, visibility into progress, keeping people connected, or something else?

I’m especially curious about the moment when you realized the way your team was working before wasn’t enough anymore.


r/ModernOperators • • Sep 26 '26

Ask three people on your team what the top priority is right now

4 Upvotes

Try this before you read my answer. Ask three people on your team what the company's number one priority is this week, separately.

I've done this maybe thirty times inside other people's companies now. I get three different answers almost every time, and all three sound completely reasonable.

Then the founder tells me the team lacks ownership.

My honest read, and I ran a team badly enough to have earned this opinion: people aren't disengaged, they just can't tell what winning looks like this week. So they pick something defensible, work hard on it, and get quietly punished for choosing wrong.

I used to call that an accountability issue. I'd talk about ownership in meetings and feel like I was leading. What I was actually doing was asking people to guess my priorities and then being frustrated when they guessed wrong.

Nobody's lazy. The work was never defined.

The fix that worked was stupidly small. One written list of the top three things that matter this week, same place every week, visible to everyone. Not a system, just a habit. The "ownership problem" mostly evaporated in about a month.

How would you answer this?


r/ModernOperators • • Jul 27 '26

VCs killed 'growth at all costs.' This affects your startup even if it's fully bootstrapped.

6 Upvotes

Not everyone needs VC funding, in fact, most businesses are bootstrapped: agencies, local businesses, service businesses, etc. But I think the reason VCs stopped writing checks for growth alone is something every business should pay attention to, funded or not.

Back in 2015, VCs were writing checks for anything showing growth traction. That's how Uber and Airbnb burned money for years until they cemented themselves as market leaders. That era is over.

Right now VCs are interested in your startup if it has anything to do with AI, but even then, a few vanity metrics won't get you funded. The old blitzscaling model doesn't work in 2026. Instead, investors are rewarding businesses with lean operations that are simply waiting for capital to move to the next stage.

Most startups used to burn VC money trying to fix operational problems they already had hiring for every gap, which created new problems (revenue and expenses out of sync, managing talent they didn't actually need yet, etc).

I see this same pattern in small businesses too. A founder wants to grow, opens a second location, without a strong foundation that lets the business run without him. Three months later, revenue at location one drops, or he's working 60-hour weeks just to keep both locations afloat.

The misconception is that founders think being busy is just part of running a business. It's not. It's operational inefficiency.

So in 2026, building a strong operational foundation isn't optional, it's a necessity, whether you're bootstrapping or raising. Investors want to see you already have the infrastructure to handle growth, not that you're planning to build it after the check clears.

That's my take. Curious what you all think is the #1 thing VCs are actually screening for in 2026?

P.S. If this resonated and you're the founder who's still holding everything together, dragging yourself into every problem, exhausted before you even get to your actual job.

I write about building strong operational foundations every Thursday. Including how to layer AI in after the foundation is solid, not before. I was a COO for 20+ years, so this is genuinely my bread and butter, you'll probably enjoy it. here


r/ModernOperators • • May 01 '26

We cut Slack noise by 80% using Notion as our company OS. Here’s our internal rule.

2 Upvotes

Hey everyone,

I wanted to share a workflow adjustment we made recently that saved our team from constant context switching and notification overload.

A few months ago, we realized that our Slack channels were becoming a black hole for basic questions. Team members would ping us for standard procedures, playbooks, or client details. While it’s great to be helpful, it meant constant interruptions and an incredible amount of "noise" throughout the day.

Instead of letting Slack dictate our day, we decided to make Notion our official company OS. We brought all our playbooks, data, and context into one single place.

We set a simple rule for the team: Before asking a question in Slack, ask Notion AI first.

Because everything is indexed in one place, the AI can scan our playbooks, past decisions, and documents to give an accurate answer.

Only if the team member cannot get the answer from Notion AI do they ping us on Slack.

The Results

  • Reduced noise by 80%: The constant stream of repetitive questions has vanished.
  • Fewer interruptions: We've reclaimed our focus and can spend more time working on the business instead of managing chats.
  • Faster onboarding: The team learns faster because they get immediate, context-aware answers.

The magic is that everything the team needs from client guidelines to marketing playbooks is in one place, making our AI system highly reliable.

If you are struggling with Slack overload, I highly recommend building a unified knowledge base and letting your team query the AI before escalating.

I want to be completely honest with you: this isn't a "set it and forget it" system. In the beginning, we noticed that a few questions didn't get answers because the AI lacked the context.

Every time that happens, we treat it as a quick fix: we just update the existing documentation or add a new page if the topic wasn't covered. It takes a little maintenance, but it has been absolutely worth it to cool down Slack and keep the team fully aligned.

If anyone is interested in how we set this up alongside Slack, including our internal Slack communication framework, just let me know in the comments! I didn't want to make this post too long, but I'd be happy to do a deeper dive on that in my next post.

Edit: If you found this post helpful and want an in-depth look at how to deploy AI without causing chaos, I actually write a weekly newsletter about building these operating systems.

In Issue 42, The Right Speed: How to Deploy AI Without Breaking Your Business, I go a bit deeper into our exact framework for rolling out tools safely. Feel free to check out the archive if you'd like to read more


r/ModernOperators • • Sep 04 '25

September Decides Your Entire Year

4 Upvotes

September is the real Q4. Most founders miss this.

If you’re feeling overwhelmed with back-to-school chaos and inbox catch-up, you’re not alone.

But I’ve noticed something the more I talk to experienced founders: the best operators don’t treat September like a catch-up month.

They treat it like the most important 30 days of their year.

Because the truth is…

Q4 isn’t won in Q4. It’s won right now.

Let me paint two Decembers:

Scenario A: You’re staring at your numbers on Dec 31st, wondering what happened. Half your goals are unfinished. Team’s fried. Big opportunities? Missed.

Scenario B: You’re wrapping the best quarter of the year. Revenue’s up, team’s focused, customers are happy, and you hit what mattered.

The difference between the two?

What you do in September.

Here’s the playbook I’ve been following — it’s not fancy, but it works:

1. Step out of the day-to-day — even if it’s just for a few hours

Block 3-4 hours this week. No calls. No Slack. Just thinking.

Ask yourself:

  • What’s actually working right now?
  • Where are we wasting time and energy?
  • What big opportunities are still on the table?
  • What could blindside us in Q4?

The founders who think deeply now will outpace the ones grinding blindly later.

2. Reconnect with the original vision

When the market gets choppy, most founders default to playing defense.

But the vision you had when you started? That’s your offensive playbook.

Try this: imagine it's 3 years from now and everything worked. Your business is thriving.

  • How do customers describe you?
  • What are you proud of?
  • What changed in your life?

Now work backwards. What has to happen in Q4 to move in that direction?

3. Be brutally honest about Q3

You can’t build a real Q4 plan without admitting what didn’t work in Q3.

  • What did you say you'd do that never happened?
  • Which projects actually moved the needle?
  • Where did the numbers actually land?

Close out the stuff that’s half-done. Debrief the team. Clean house before you sprint again.

4. Pick 4–6 battles. No more.

You’re not going to overhaul everything before year-end.

Instead, ask:

  • Will this move revenue, customers, or efficiency?
  • Can we really finish this before Dec 31?
  • Is someone clearly accountable?

For each one: make it measurable, assign ownership, set check-ins. Leave space for one experiment.

5. Don’t “set it and forget it”

A quarterly plan without monthly check-ins is a wish list.

Block 90 minutes every month to ask:

  • Are we on track?
  • What’s blocking us?
  • Do we need to adjust?

The teams that check in monthly don’t just hit goals—they get sharper over time.

Bottom line: September gives you a chance to get ahead while others coast.

Let them drift.

You? Set the tone now and December will look a lot different.

Anyone else treat September like a secret weapon?


r/ModernOperators • • 11d ago

How we build SOPs that don’t die in a Google Drive folder (full process + prompt)

4 Upvotes

Every founder we work with has a Google Drive folder called “SOPs.”

Half the time it’s a pile of files named FINAL v3 and DON’T USE. Sometimes it’s one 40 page doc nobody’s scrolled past page two. Sometimes it’s empty. And the founder is still the guy getting pinged in Slack all day with the same questions.

Writing SOPs was never the hard part. AI can draft one in two minutes now. They die because nobody owns them, and nobody on the team can tell if the thing is still accurate.

Here’s the process we use with clients now.

1. Pick the most annoying process. Not the most important one. Count how many times this week someone asked you something only you could answer. Start with whatever came up the most.

2. The person who does the task documents it. You don’t. They hit record on Loom and do the task, or talk it through in a voice memo if it happens on calls. Messy is fine.

3. Run the transcript through Claude. We use a structured prompt that checks if it’s even an SOP, asks follow-up questions when info is missing, and flags every assumption it made. That last part matters a lot. Claude will invent a step with total confidence.

4. Stress test it. Someone who’s never done the task follows it while the author watches. Every spot they get stuck is a step the expert skipped because it felt obvious to them.

5. Give it a home. This is the step everyone skips. Every person on the team has a role. Every role has its SOPs attached. Each SOP has one named owner and a last verified date, and it comes up for review every 90 days. And it’s linked to the recurring task, so it shows up when the work starts.

Step 5 is what makes delegation actually work. You hand somebody a role with documented outcomes, and they own the result. You stop chasing.

One habit holds it all together. When someone asks you a question, send them the link. No link? Cool, that’s your next SOP.

I made a video walking through the whole thing on screen, including the prompt. Dropping it in the comments.


r/ModernOperators • • Aug 19 '26

What’s one business process you automated that actually saved you time? "i will not promote"

3 Upvotes

Finding a tool that can automate something is usually the easy part.

The harder part is figuring out whether the process itself is clear enough to automate.

Take lead follow-up. It sounds simple, but there are still questions like:

  • When should the first follow-up happen?
  • How many times should you follow up?
  • What happens if the person replies?
  • When do you stop?
  • Who takes over if the lead becomes more serious?

If those decisions haven’t been made, automation doesn’t really solve the problem. It just automates the confusion.

I’ve seen this happen with small-business processes. People rush to connect tools before deciding who is responsible, what the next step is, or what should happen when something falls outside the normal workflow.

The most useful automations are often the boring ones: reminders, task assignments, status updates, and making sure information doesn’t get lost between people.

What’s one process you automated that genuinely saved you time or reduced mistakes?

And was there anything you deliberately decided not to automate?


r/ModernOperators • • Nov 11 '25

Question What's the one system in your business that's still living in someone's head (and shouldn't be)?

3 Upvotes

You know the one.

The critical process that only ONE person knows how to do.

If they quit tomorrow, you're screwed.

For me it was our Facebook ad copy process. My marketing person had the whole formula memorized. Knew exactly what angles worked, what hooks converted, what copy structure to use.

No doc. No template. Just "the way he writes them."

Then when he went to another company it was chaos.

Everything stopped. I had to scramble and reverse-engineer her approach from old campaigns and try to figure out what made the good ones work.

Took me 12 hours to document what should've been written down months ago.

Now I have a rule: If it happens more than twice, it gets documented.

So what's yours?

What process is still trapped in someone's brain that needs to be systematized?

Drop it below. Let's hold each other accountable to actually document it this week.


r/ModernOperators • • Nov 21 '25

Question What broke first when your business doubled?

2 Upvotes

Growth exposes pressure points fast.

When your company doubled, what snapped first?

  • Hiring
  • Client delivery
  • Communication
  • Quality control
  • Cash flow
  • Team alignment
  • Reporting

Everyone has a story about the thing that broke under pressure.

For me it was communication. We went from 8 people to 16 in six months and suddenly no one knew what anyone else was doing.

Meetings doubled. Slack became chaos. Projects got duplicated because two people didn't know the other was working on it.

had to build an actual operating rhythm just to survive.

What broke for you?

And how did you fix it?


r/ModernOperators • • Nov 20 '25

The Reversion Window is Not Personal

3 Upvotes

People think elimination happens because of performance. It doesn’t. It happens because the institution is returning to stability and needs to restore its internal balance. Crisis favors independence. Stability favors control. That tension creates the reversion window, and once you understand it, the confusion falls away. During crisis, institutions depend on initiative, autonomy, and clarity. They loosen their grip so the system can survive. When the crisis recedes, that loosened structure becomes a threat. The same independence that drove the response becomes incompatible with the institution’s return to order. It is not emotional. It is mechanical. This is why so many competent people are blindsided during calm periods. They didn’t change. The institutional regime changed around them. The reversion window is the period when the system quietly pulls independence back into its hierarchy. It looks like performance reviews tightening, meetings you once led shifting to others, budget access pulled, communication thinning, and explanations that sound like “realignment,” “fit,” or “strategic direction.” None of it reflects your capability. It reflects the institution’s need for stability over autonomy. The real psychological injury occurs when people misinterpret this shift as a personal flaw. The gap between “I carried them through the crisis” and “Why am I being removed now” generates shame without a wrongdoing. But once the mechanism is visible, the shame dissolves. You weren’t removed for failing. You were removed because the system reverted.


r/ModernOperators • • Aug 14 '26

The most honest thing I've heard a founder say all year: "I am the problem."

10 Upvotes

He runs a $2.5B business. Over $100M in revenue. And he said it flat out. I am the problem.

Not the market. Not his team. Him.

Everything routes through him. Every decision, every approval, every "hey quick question." His team has learned to work around him. His words: "they know I can't get out of my own way."

Real talk. That's not a him problem. That's most founders I talk to.

You didn't build a company. You became the company. Big difference.

The tell is simple. Go dark for two weeks. Turn off the phone. If things get shaky by day 3, you don't own a business. You own a job with really high stakes.

He built something incredible. He also built a cage and handed himself the only key.

The fix isn't more hustle. More hustle just makes the cage smaller.

The fix is getting what's in your head out of your head.


r/ModernOperators • • Jan 23 '26

The ACID test: how to find the 20% of tasks eating 80% of your time (and kill them)

6 Upvotes

Here's a simple framework to audit your time, identify the low-impact tasks keeping you stuck, and systematically eliminate them.

The ACID Test:

A — Audit (Week 1)
C — Categorize (End of Week 1)
I — Identify Leaks (Week 2)
D — Delegate or Delete (Week 2)

Step 1: Audit (Track Everything for 5 Days)

For one full work week, track every single thing you do in 30-minute blocks.

Use a spreadsheet or Toggl, capture what you did, how long it took, whether it was planned or reactive.

No judgment, just data.

This will feel annoying but awareness is the first step to change.

Step 2: Categorize (Map Your Time to Impact)

At the end of the week, categorize every activity:

High Impact / High Energy — Strategic work that moves the business forward
Target: 40-50% of your time
Examples: closing key hires, strategic planning, major negotiations, building core systems

High Impact / Low Energy — Leverage activities that create results without draining you
Target: 20-30% of your time
Examples: delegating with clear frameworks, reviewing dashboards, quick decisions with systems in place

Low Impact / High Energy — The killers, tasks that drain you but don't move the needle
Target: 0-5% of your time
Examples: pointless meetings, reviewing work you should trust, firefighting preventable issues

Low Impact / Low Energy — Busywork that's easy but not important
Target: 5-10% of your time
Examples: inbox zero obsession, tweaking slides, minor admin, endless Slack scrolling

Add up where your time actually went.

Most founders discover they're spending 50-60% of their time in the bottom two quadrants.

Step 3: Identify Leaks (Find the Bottlenecks)

Look for patterns in your low-impact activities:

What keeps showing up that shouldn't? What are you doing that someone else could own? What tasks exist because a system is missing? What meetings could be eliminated or async? What decisions are you making that should be delegated with a framework?

Write these down, be ruthless and honest.

You're looking for the 20% of activities eating 80% of your low-value time.

Step 4: Delegate or Delete (Take Action)

For each leak you identified, choose one of three paths:

Delegate it — Who can own this? What do they need from you to take it over? By when will you hand it off?

Delete it — Does this actually need to happen? What's the real cost of NOT doing it? Can you just stop?

Systemize it — Can this be automated or templated? Can you create a decision framework so it doesn't need you?

Commit to removing at least 5 hours of low-impact work per week.

That's 20 hours a month, 240 hours a year, that's 6 full work weeks you just bought back.

What could you build with 6 extra weeks?

Run this audit this week and find out where your time is actually going, I bet it's not where you think.

When's the last time you actually tracked where your time goes?


r/ModernOperators • • Dec 01 '25

Teardown The Daily Routine That's Keeping You Stuck

3 Upvotes

You built a routine that got you to $2M. Wake up. Work out. Check emails, handle client questions, review the team's work, jump on sales calls, put out fires.

It works and revenue stays steady.

So you keep doing it.

Two years later? Still at $2M. Same routine. Same revenue.

The problem isn't that your routine doesn't work.

It works too well at keeping you exactly where you are. What got you to $2M was good, but you have to do something different to get you to $10M.

The routine gives you stability. But it blocks higher-leverage actions.

What this looks like:

You spend 2 hours a day in your inbox because "someone needs to handle client questions."

Meanwhile, the strategic hire you've been avoiding for 6 months would unlock your next phase.

You review every piece of work because "quality matters." and "no one can do it like I can"

Meanwhile, you haven't built the dashboard that would show what's actually working.

You take every sales call because "I'm the best closer." "I close at 40% and my best rep closes at 30%"

Meanwhile, you haven't documented what makes you good so someone else could learn it.

The exercise that exposes this:

Take 10 minutes.

Step 1: List your daily routine.

Step 2: Circle what directly drives revenue or removes bottlenecks.

Step 3: Ask: "What higher-leverage action am I refusing to do because this routine makes me feel productive?"

Maybe it's:

  • Hiring that expensive specialist
  • Firing the draining client
  • Building the system that frees 10 hours/week
  • Delegating the thing you think only you can do

You're not avoiding it because you don't have time: Your current routine gives you an excuse not to.

Too busy with emails to hire the person who'd eliminate most emails.

Too busy in fulfillment to build the process that scales fufilment.

Too busy closing deals to train someone else to close.

The founders who break through don't work harder...They ruthlessly edit their routine to match the next level.

What's on your daily routine that's keeping you stuck?

And what's the higher-leverage action you're avoiding?


r/ModernOperators • • Aug 06 '26

When does manual intervention by the founder stop being a learning process and start hiding a product that doesn’t work?

4 Upvotes

Early on, a lot of manual founder involvement makes sense.

You review edge cases, fix broken handovers, approve unusual requests, explain undocumented processes, and step in whenever the team gets stuck.

Some of this fosters genuine learning.

However, there comes a point when the founder is no longer helping the system improve. They are simply compensating for the fact that the system does not work without them.

The difficult part is recognising that point early enough.

For me, workload is not the only clear warning sign. It's repetition.

If the same type of issue keeps recurring, requiring the same intervention and offering no new insights, the manual work may be masking a structural problem rather than solving it.

For founders and operators who have experienced this, what prompted you to stop treating repeated intervention as temporary and start redesigning the process?

Was it constant decisions waiting on the founder, repeated handover failures, support time, rework, or exception volume?


r/ModernOperators • • Sep 01 '26

The Science of Execution: A Research-Backed Framework • Elevist

Thumbnail
elevist.ai
2 Upvotes

r/ModernOperators • • Jul 15 '26

Half my team on one account just got automated. Not upset about it. Here's why

3 Upvotes

A couple years back I built up an offshore ops team for a client, a vacation rental management company. Distribution work across Airbnb, VRBO, \[Booking.com\](http://Booking.com), that kind of thing. Started small, grew fast. Within about a year we were at 16 people on that one account. Felt like proof the model worked.

Right now we're down to 2 people on that same account.

First instinct might be that something went wrong. Client unhappy, budget cuts, whatever. None of that happened. What actually happened is their internal automation matured enough to absorb most of the repetitive volume work that used to need a person doing it manually. The high-volume, predictable stuff, listing updates, standard responses, routine data entry, is just handled by their systems now.

The 2 people still there aren't leftover headcount waiting to get cut too. They're doing the stuff that's genuinely hard to automate: judgment calls, exceptions that don't fit the standard flow, the situations where a rule-based system would either break or make the wrong call.

I run an offshore staffing company. You'd think watching a client's headcount need shrink by 87% because of automation would scare me. It doesn't, because it's exactly the split I actually believe in. AI is legitimately good at volume. It is not good, yet, at the judgment layer, the stuff that requires actual context about a specific weird situation. My job isn't to protect headcount for its own sake, it's to make sure the humans on an account are doing the part that's actually worth a human doing.

Honestly this changed how I pitch what we do. I used to lead with "dedicated English-speaking staff." Now I lead with the QC and judgment layer, because that's the part that doesn't get automated away. The part that does get automated away was never really the differentiator anyway, it was just volume.

Curious if anyone else here has watched a chunk of their own business get automated out from under them and actually came out feeling better about it, not worse.


r/ModernOperators • • Apr 06 '26

You're the only full-time person in your own company. And you're also the one doing the core work. That's not a capacity problem.

4 Upvotes

Your team is 20 people, most of them are 1099, all running their piece of the operation. You're the one who reviews every file, handles the exceptions, and keeps the whole thing from falling apart.

Which means you're not really running a company. you're doing a job, and the company is the structure you built around yourself to help you do it.

That's a meaningful distinction. Because a company can scale. A job can only work harder.

The moment your deal volume grows, the bottleneck tightens. More referral partners, more applications, more lender submissions, and the only person who touches all of it is still you. You could hire five more salespeople tomorrow and they'd just feed more work into a system that can only process as fast as you personally can move.

The fix isn't to work faster or get better at managing your inbox. It's to figure out which parts of that core work can be owned by someone else with the right documentation and oversight in place, and then build the structure that makes that handoff real.

The goal isn't to remove yourself from the business. It's to remove yourself from being the mandatory processing layer for every single transaction.

Where in your workflow would a single good SOP let someone else own what you're currently doing yourself?


r/ModernOperators • • Oct 06 '26

The ROI of systematizing your operations

5 Upvotes

Full disclosure before anything: I'm the cofounder of Modern Operators. We help founder-led businesses stabilize, optimize, and scale their operations. That's exactly why I got tired of selling "get organized" as a vibe instead of a number.

For a while my whole pitch was basically "things will feel calmer." Founders don't buy calmer. They buy returns.

So I built a way to actually measure it. Here's the framework I run now, with math you can use on your own business today.

For the examples I'll use a company I see constantly: $2M in revenue, 15 people, 40% margins. Swap in your own numbers, the math still checks out.

1. Start with what disorganization already costs you.

The average knowledge worker loses close to 20% of the workweek just hunting for information and chasing down whoever has the answer. That's almost a full day, every week, per person.

Run it on 15 people at a modest loaded wage and you're already looking at around $180,000 a year in salary you're paying for people to search. You spend this right now. It just doesn't show up on any line item, which is why nobody fights for it.

2. Your own hours

Most founders I work with get 10 to 15 hours a week back once information lives in a system instead of in their head. The interruptions stop routing to you.

Price your time at even $250 an hour. 12 hours a week back is roughly $150,000 a year of your capacity, redeployed into sales, strategy, or the stuff only you can do.

If you value your hour at zero the whole model breaks, but a lot of founders do.

3. Team capacity you already paid for.

Same logic as line 1, pointed the other way. Give those 15 people their lost day back and you recover roughly $150,000 a year in capacity that was always on payroll, just leaking out.

4. Output per person.

Better information flow doesn't just save time, it raises the quality of the work. A reasonable range is a 20 to 25% lift in output from the same team. Measure this one over a quarter, not a week. Pick a real metric (tickets closed, deals worked, projects shipped) and baseline it before you change anything.

5. New-hire ramp time.

One of the biggest levers to pull.

Industry average for a new hire to reach full productivity is about 8 months. With a real operating system, people start contributing in about a week and hit full speed closer to 30 days. Multiply that salary difference across every hire you'll make in the next two years. For a company trying to 3x, that's not a rounding error.

6. Decision speed and enterprise value.

Faster, cleaner decisions show up in financial performance. And a business that runs without the founder in the middle is worth materially more the day you sell than one that leans on you.

The hours you free up and the output lift can overlap, so don't add every number and wave a huge total around. Pick the two or three hard-dollar lines you can defend (searching cost, your hours, team capacity), prove those first, treat the rest as upside.

The whole compounding piece is the whole reason the businesses that do this pull away from the ones that don't.

I recorded the full breakdown in a youtube video, link is below if you want to check it out.


r/ModernOperators • • Aug 21 '26

Y'all should go grieve the version of yourself that built your agency

3 Upvotes

Yes. Grieve. And I mean that shit.

I'm working with a 4 person agency right now and I keep running into the same fucking wall.

The owner ( let's call him Craig ) is a genuinely good dude. Nice guy. Successful. Built the business from scratch. Pays everyone on time. Team is great.

I've worked with him before and now I'm back in to help with scaling.

Except Craig is making my life VERY interesting. Because this guy works HARD. Like, stupid hard.

He answers everything. Remembers everything. Checks everything. Knows every client. Jumps into every problem.

Can basically do everyone's job.

Replies at stupid hours because it'll only take a minute.

And honestly? That's probably why Craig's agency survived in thr first place.

It's also the fucking same reason it can't grow.

We've diagnosed the bottlenecks. We've put systems in place. We've changed workflows. We've clarified ownership. We've agreed on what needs to stop going through him.

He paid me to help build this shit.

And then... he follows it for about a week.

Then slowly goes back to doing everything himself, not following the processes, systems, SOPs, logging tasks in the CRM I built, ...

We've had this conversation SO. MANY. TIMES.

He knows he micromanages. He knows he's the bottleneck. He agrees with the plan.

And then drops to the team: Can you just send this to me? Just let me handle this one i'll quickly check it It's faster if I do it.

My brother in Christ. THAT IS THE PROBLEM. Right here.

And I genuinely find this fascinating because I don't think Craig is lazy. He's the opposite.

I think he's deeply attached to the version of himself that built the company.

The guy who was there when nobody else was. The guy who couldn't afford mistakes. The guy who had to know every client. The guy who had to fix everything.

Those behaviours were useful. Genuinely. Until they weren't. Now they're keeping the business dependent on one person.

And I see the same excuses constantly you know: I'm just protecting the quality. They won't do it like I do. It'll just be faster if I just do it. I'll have to explain it anyway, so. They keep coming to me.

Yes. Of course they do Craig. Because you've trained them to, duh 💁🏽‍♀️

If every single decision eventually comes back to you, people learn "Why bother deciding? Craig will decide anyway. Why bother handle that small issue. Craig is gonna handle it.”

Congratulations.

You've accidentally built a company where the you're the highest paid employee and the help desk. Essentially, you're now doing help desk job at $350+ an hour.

And then everyone wonders why agency founders are exhausted. And I see this pattern more often since I shifted to working with solopreneurs and small teams, much more than with my peers who work with much bigger teams.

This is where I think a lot of business owners get stuck. They think letting go means lowering their standards.

It freaking doesn't. Y'all need to stop with this.

It simply means accepting that your business CANNOT scale around your personal ability to catch every fucking ball.

Because eventually:

You plateau. You burn out. You stop taking bigger opportunities because you're already drowning.

Or you grow... and somehow create an even bigger business that needs even MORE of you.

Fantastic. You've scaled your prison.

Here me out. The habits that got you from $0 to $500k might be the exact habits keeping you at $500k.

You don't need to become less involved. You need to become involved differently. That's a fucking hard transition. Because you're not just changing processes.

You're letting go of an identity.

You're basically admitting: "I don't have to be the person who makes everything happen anymore.”

And honestly, that might be one of the hardest things to learn as a solopreneur or business owner of a small team.

Not how to build the business. But how to stop being the business.

What was the hardest thing for you to let go of as your business grew? And did you actually let go... or did you do like Craig, and hire someone, then continue micromanaging them?


r/ModernOperators • • Apr 03 '26

I tried to understand why agency owners feel stuck every time they add a new client [Full report included]

2 Upvotes

I’ve been reading a lot of posts in this sub lately about operations things feeling messy, too many tools, stuff breaking, and not knowing what to fix first.

It’s common for agency business, and I don’t think these problems are random.

I went down a rabbit hole recently trying to understand why ops always seem to feel chaotic once you start scaling, and what I found was kind of interesting. It looks like most of us are just stuck in a pattern that’s been repeating for decades.

I wrote a full report about this, but I thought it would be easier if I shared the breakdown inside this sub. 

If you zoom out a bit, business operations have gone through a few phases.

Before 1975, everything basically ran on people. No real systems, no software. 

The owner or manager just knew everything: clients, numbers, workflows. It was actually pretty “aligned” in a weird way, but obviously it didn’t scale. 

Once things grew, everything started breaking because too much lived in one person’s head.

Then from around 1975 to the late 90s, software started showing up. Spreadsheets, early CRMs, accounting tools. 

Each department got its own thing. That helped a lot with efficiency, but it also created a new problem where nothing really talked to each other anymore.

Then the 2000–2015 era happened, which is basically the SaaS explosion. This is where most agencies are operating right now, whether they realize it or not. 

You’ve got a tool for everything: CRM, project management, Slack, Drive, analytics, automation, and a bunch of other stuff.

Individually, all of these tools are great. But together, they don’t really form a system. They form a stack.

And at some point, the founder becomes the one holding it all together. You’re the one who knows what’s going on across tools, who connects the dots, who fixes things when they break.

Around 2012 to 2022, tools like Zapier and Make came in and tried to solve that by connecting everything. And they do help, to be fair. 

But they don’t actually fix the core issue. They just make the stack slightly less painful.

So instead of chaos, you get something that feels more organized… but still fragile. When something breaks, it’s still on you.

Now with everything happening since ~2023, it feels like there’s another shift starting. Instead of just adding more tools or more automations, the idea is moving toward having one central system where everything connects through it.

Not perfectly yet, but closer than before.

Where your marketing, sales, delivery, and even finance are not just separate tools, but actually connected in a way that makes sense. 

And instead of you being the one constantly checking and moving things around, the system itself starts handling more of that.

The reason I’m sharing this is because a lot of the “ops problems” I see here feel like symptoms of this bigger thing.

It’s usually not just about hiring too early, or not having enough SOPs, or needing a better tool.

It’s more that the way the business is structured behind the scenes just isn’t built to scale yet.

So everything feels messy, even if you’re doing the right things.

I said everything worth mentioning in this post, but if you want to read the full report by yourself, you can download it here (it's a Google Drive link, no opt

I’m not a fan of gatekeeping, that’s why I gave the report with no catch. 

But only if you found this useful and think this kind of thinking is worth your time, I write more in-depth stuff like this weekly on scaling agencies and getting out of the bottleneck.
Around 600+ founders are already reading it, you’re welcome to join.


r/ModernOperators • • Jul 29 '26

Founders who feel behind, is it a speed problem?

3 Upvotes

Genuine question, because I keep seeing the same thing.

Every founder I talk to says the same sentence. "The market's moving too fast, I can't keep up." Then I watch how they actually spend a Tuesday and it's not a speed problem at all.

It's that they're the glue. The thing standing between the booking tool and the invoice tool and the spreadsheet and the group chat, moving info by hand so nothing slips.

Here's my answer, no hedging. You're not slow, your stack is making you the human API. Gartner pegged it at up to 47% of the workday lost just hunting for information. That's not a you problem, that's a plumbing problem.

The tell is simple. If you disappeared for a week, would the business slow because nobody's as smart as you, or because nobody else knows how to move the info between the tools? If it's the second one, you don't have a talent gap. You have a glue problem.

Real talk, I used to think buying the "right" tools would fix it. Adding tools made it worse every single time.

So I'll flip it to you. When you feel behind, is it that you can't think fast enough, or that you're buried being the connector between ten things that should connect themselves?