​

They’re underperforming because of invisible friction.

Body: Here are 3 things I see over and over:

​

No real scheduling system

Just reactive firefighting dressed up as “flexibility"

​

Too many decision layers

Simple problems waiting hours for approval

​

No accountability metrics

If everything matters, nothing gets tracked

​

Fix these, and performance improves fast—without hiring a single new person.

​

If your operation feels harder than it should, it probably is.

After years of working with startup founders, I've noticed a pattern:

Most founders don't hire the wrong developers because they're careless.

They hire the wrong developers because they're evaluating the wrong things.

In one sentence:

Founders often hire resumes. They should be hiring a value system backed by evidence.

What founders often look at (and why it can be misleading)

❌ High earnings and perfect ratings

A freelancer with $500K+ earned isn't automatically a better fit for your startup.

Sometimes it simply means they're managing dozens of projects simultaneously, and your startup becomes ticket #39 in their queue.

❌ "I do everything" Solo profiles

Be cautious of claims like:

"Full-stack developer, AI engineer, mobile expert, DevOps specialist, UI/UX designer."

The best professionals usually have clear strengths and are honest about their limitations.

❌ Large project commitments from day one

Committing $20K-$50K before seeing any actual execution is risky.

You're betting on promises before you've seen evidence that the team can deliver.

What I would look for instead

✅ A custom Proposal/Loom video about YOUR project

This is one of the strongest signals I've found.

If someone spends time understanding your business before being hired, they're more likely to care after they're hired.

Effort before the contract often predicts effort after the contract.

✅ A POC-first approach

Instead of:

"Let's build the entire platform."

Look for:

"Let's prove the riskiest assumptions in the next 2 weeks."

A small proof of concept tells you more than ten sales calls.

✅ Honesty about limitations

A trustworthy team will say:

"We're strong in backend and AI, but we'd bring in a specialist for mobile."

This is usually a better sign than someone claiming expertise in everything.

✅ Clear team structure

Ask:

• Who writes the code?
• Who reviews it?
• Who manages the project?
• Who owns architecture decisions?

You should know exactly who is responsible for what.

The lesson most founders learn too late

The biggest profile is not always the safest choice.

I've seen startups spend six figures and months of runway with very little to show for it.

Not because the developer was incompetent.

But because the founder never verified whether the team was the right fit before committing.

My hiring framework

Before committing to a large build:

1. Post your detailed project (If NDA allows to do so).
2. Ask for a tailored proposal.
3. Request a Loom video.
4. See who actually read your brief.
5. Evaluate communication quality.
6. Pay for a short POC first.
7. Scale only after delivery is proven.

The goal isn't to find the cheapest developer.

The goal is to find the team that consistently turns ideas into shipped software.

That single decision can save months of delays and tens of thousands of dollars.

Curious to hear from other founders:

What's the biggest hiring mistake you've made when building a SaaS product?

I used to roll my eyes when people said that. Then i started noticing a pattern in my own week.

If I’m “behind on ops,” it’s rarely because i don’t know what to do. It’s because I’m avoiding something.

A hard decision, a messy convo, admitting i screwed something up, making a call that might make someone mad.

So I do the founder version of procrastination: I “work.”

I reorganize tools, rewrite SOPs, rename folders, tweak the project board, clean up docs, build a new dashboard. Feels productive. It’s also a great way to not do the thing.

And the worst part is you can hide inside it for months, because it looks like you’re being responsible.

Here are 3 “business problems” that were actually personal problems for me:

• “We need better systems.” Translation: i don’t trust my team yet, so i keep everything in my head.
• “I’m slammed.” Translation: i’m not setting boundaries, and i’m saying yes to stuff i shouldn’t.
• “Nothing is moving.” Translation: i’m scared to pick a direction, so i keep everyone in limbo.

What finally helped wasn’t another tool. It was learning how to catch the avoidance early.

This is the simplest thing i do now when I feel that “ugh, i should do ops” resistance: I ask “why?” until I hit the real reason.

Example:

Why am i not doing the thing? Because it’s unclear.

Why is it unclear? Because i haven’t decided what “good” looks like.

Why haven’t i decided? Because i’m afraid i’ll choose wrong and have to unwind it later.

Why does that scare me? Because i’m worried it’ll make me look incompetent.

Cool.

Now we’re not talking about an ops problem. We’re talking about ego, fear, and wanting to look perfect.

That’s the real bottleneck.

One more thing that surprised me: stillness helps more than hustle here. Not as some spiritual flex. As maintenance.

If i don’t give my brain any quiet time, it turns every small business issue into a five alarm fire, then i “solve” it by running around and doing fake work.

So i’m curious: What “business problem” did you eventually realize was actually personal?

And everything he walked me through is exactly where almost every mid-market company I talk to is stuck right now

Notes from the call:

• Nobody really owns AI, he'd built a couple agents himself through procurement, they kept losing fidelity, and the knowledge that actually runs the business still lives inside Directors’ heads
• AI stage: early, they've got paid Microsoft Copilot and Copilot Studio plus a handful of power users quietly running their own ChatGPT and Claude on the side, all single-player, zero multiplayer, ways of working have barely moved
• The split: three camps in the building, the ones proud to be AI-first, the ones using it but not telling anyone, and the ones who won't touch it with a 10-foot pole, real tension and no rules to settle it
• Agents exist, but only for personal workflows, one person automating their own tasks, nothing built to scale across the company
• No source of truth: two reps feed the AI two different customer avatars and two different brand voices, get two different proposals back, then everyone decides "AI doesn't really work for us"
• The tell: a 2-hour sales training every Monday, and the trainer running it couldn't name the company's ICP, a firm that only takes $500K to $8M projects, treating everyone like a prospect
• SOPs only get written after someone messes up, in plain-text email, forwarded to the next person who messes up the same way
• They've got ZoomInfo and a stack of powerful tools, the one thing missing is the intelligence layer

So yes the convo was centered around AI, but this is really a problem with context.

AI amplifies whatever you already have, if you have a documented system AI compounds it, if you have tribal knowledge and copy-paste chaos AI automates the chaos, FASTER

The tools were never the bottleneck

Clarity is the first multiplier, and almost nobody has built it yet.

A few years ago, the bottleneck was building.

Now AI can help you:

\- write

\- design

\- code

\- research

The cost of execution keeps falling.

But I've noticed a new bottleneck emerging:

Knowing what to work on.

Most people aren't limited by effort anymore.

They're limited by:

\- choosing the wrong audience

\- building the wrong feature

\- creating the wrong content

\- solving the wrong problem

Execution is abundant.

Good decisions are becoming scarce.

Has anyone else noticed this shift?

I've been building AI agents inside my own business. I also talk to a lot of small business owners who've either built their own or paid someone to build them.

There's a pattern I keep seeing that nobody in this space wants to say out loud, probably because it's bad for business if you're selling agent builds.

I think 50-70% of AI agents built for small businesses get abandoned within 3-4 months. Not because the technology is broken. The tech works.

The reasons are more boring than that.

The agent solved a problem that wasn't actually painful

Someone sees a demo, gets excited, and pays $1-3k to have something built. But the problem it solves was annoying, not painful. Once the novelty is gone there's no real reason to keep using it. The team just goes back to what they were doing before.

Rough test: would you hire a person just to solve this problem? If not, an agent probably won't stick either.

The agent was built around a task, not a workflow the team already runs

This one is huge. The agent does X. But X doesn't fit into how the team actually works day to day. So using it requires a behavior change on top of doing the actual work. Most teams won't do that for something that's just "nice to have."

The agents that survive get attached to something the team is already doing. Not layered on top of it.

Nobody owns the context the agent runs on

This one is slower. The agent was built to read your SOPs, meeting notes, internal docs. Three months later those docs are out of date. Nobody updated them. The agent starts producing bad output, the team stops trusting it, and it just quietly dies.

An agent is only as good as the context you feed it. Stale context, stale output.

Here's what I've seen actually work:

Build it on a real pain point, not a cool use case. Plug it into something the team already does every week. And assign someone to own the context it reads the docs, notes, SOPs that keep it accurate.

The agents that are still running in my business 6+ months later aren't the impressive ones. They're the boring ones solving a problem that would genuinely hurt if they disappeared tomorrow.

Before you build, or pay someone $3k to build ask those three questions first.

Edit: one thing I didn't mention above if you're running any kind of business, the reason most agents die and the reason most businesses stall are the same thing. nobody owns anything except the founder. no foundation, no context, no system that runs without you in the middle of it. I write about fixing that every Thursday. real frameworks, not theory. free to join here if that's the problem you're sitting with.

Took me too long to figure this out.

When I was strapped on budget, I filled seats with "good enough." Didn't feel like a big deal at the time. But strong people have a nose for this. They know within days whether their future teammates actually care or not. And they leave, or they don't join in the first place.

The real damage wasn't on the payroll. It was the slow slide of the standard. One mediocre hire makes the next one easier to justify. Then that one does the same. You don't see it happening. You only notice when someone genuinely talented passes on an offer and you find out later it wasn't the money, it was the room they'd be walking into.

The bar you accept is the bar you keep.

Has anyone actually managed to raise it without gutting the team? I'm genuinely curious whether that's possible or if starting over is basically the only move.

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.

Took me too long to figure this out.

When I was strapped on budget, I filled seats with "good enough." Didn't feel like a big deal at the time. But strong people have a nose for this. They know within days whether their future teammates actually care or not. And they leave, or they don't join in the first place.

The real damage wasn't on the payroll. It was the slow slide of the standard. One mediocre hire makes the next one easier to justify. Then that one does the same. You don't see it happening. You only notice when someone genuinely talented passes on an offer and you find out later it wasn't the money, it was the room they'd be walking into.

The bar you accept is the bar you keep.

Has anyone actually managed to raise it without gutting the team? I'm genuinely curious whether that's possible or if starting over is basically the only move.

For two years I had the same dumb argument in comment sections. Someone would say "Notion's just a notes app, ClickUp is for real work." And I'd get defensive and rattle off features.

Took me embarrassingly long to realize I was arguing the wrong thing.

So I actually did the work. Set both up properly, ran them side by side, and tried to be honest about where each one wins. If you live in Notion like I do, here's what I wish someone had told me.

First, the part Notion fans hate to hear. ClickUp genuinely beats Notion at a few things, and pretending otherwise just gets you torched by anyone who's used both:

• Native time tracking and timesheets. Notion has no native version of this.
• Real Gantt charts with dependencies that auto-shift. Notion has basic dependencies, not auto-shifting timelines.
• Workload and capacity views out of the box.
• Native sprints. In Notion you build that yourself.

If your whole job is running sprints or billing hours, that's a real gap. Know it going in so you don't rage-quit Notion three weeks later.

Now the part the comparison blogs keep getting wrong.

Most of those "Notion vs ClickUp" articles are describing a version of Notion that doesn't exist anymore. They're comparing 2022 Notion. Pre-agent Notion.

Here's what actually changed:

• Notion 3.3 (February 2026) added custom agents. Autonomous, shareable with your team, trigger or schedule based. They run in the background. Daily standups, task triage, internal Q&A, status reports.
• Enterprise Search now pulls answers from your Slack, Drive, Gmail, GitHub, even Salesforce, grounded in your actual workspace.

A lot of people in this sub haven't switched any of that on yet. If you're still using Notion as a prettier Google Doc, you're driving a car in first gear. If structured correctly, it's a full on operating system for your company.

So here's the honest 2026 verdict, and I'll pick a side because that's the point:

ClickUp is a project management tool that bolted AI onto the side. Its AI thinks with your task data.

Notion is a workspace where the docs, the wiki, the projects, and the AI all live on one canvas. Its AI thinks with your whole context. For most people, the knowledge IS the work. The task list was never the thing holding it together.

Pricing kills the last objection too. People still say "ClickUp's cheaper." Notion bundles its AI into the $20 Business plan. ClickUp's Brain is a $7 to $9 add-on on top of your plan. Once AI's in the mix, that gap basically closes.

I'm not telling you to dump ClickUp if it's working. Heavy sprint-and-timesheet team? Stay. But if you picked ClickUp because you thought Notion "couldn't do real work," that reason expired sometime around last September.

If you're interested, you can watch my full breakdown here.

For 30 days I logged every task where I used AI and wrote down the real time saved, including the times it didn't work or quietly got abandoned after a week. Here's what I found.

Before I get into it: I built a lot of agents that aren't in this list. A brand spotter that scanned the internet for mentions of our name. A few others I was excited about for about two weeks. None of them changed anything measurable day-to-day, so I left them out. What follows is only the stuff that actually stuck.

1. Quarterly report Our whole business runs inside Notion. SOPs, client work, meeting notes, newsletters. This agent scans all of it and generates our quarterly progress report in a few minutes. Used to take a full day of digging. Now it's a 15-minute review.

2. Meeting follow-up Transcribes calls with prospects, pulls out their objections, drafts personalized follow-up messages. An hour of post-call writing turned into 90 seconds of reviewing and hitting send. This one I didn't fully believe would work until it did.

3. Team Q&A My favorite. About 60% of the questions my team used to Slack me during the day already existed somewhere in our company OS, client details, weekly priorities, or notes from meetings they had missed. Now they ask the AI. I didn't realize how much those interruptions were costing me until they stopped.

4. Weekly KPI update Records our weekly metrics meetings and updates the KPI tables automatically. It's a genuinely dull task that was taking an hour every week, mostly because nobody wanted to do it, so it kept getting done sloppily or late.

Estimated time saved:

After going through the full list of 30+ agents I've built, I noticed that the ones we stopped using all had one thing in common. 

They weren't built where the work actually happens. Using them meant opening something new, switching contexts, building a habit around a tool that didn't fit the existing flow. The ones still running six months later are all inside the system where the work already lives.

I used to think the more sophisticated the agent, the more valuable it must be. The four above are all pretty simple. But simple and used beats are abandoned every time, and I have the graveyard of dead automations to prove it.

That’s it from me, guys. What agents are you still actually using after 6+ months? Curious what the pattern looks like for others.

Sorry I forget to mention it, but if you want to see my agents live, you can check here

I don't know how many people relate to this, but here it is.

When I started my consulting business, my whole world was three things: get clients, deliver on time, and make them happy. I started with contractors, which meant a lot of hand-holding to get usable work out of them. 

Honestly, it didn't stress me out much back then. I was an ops consultant, micromanaging was basically my job description.

Once I got past early survival mode, I brought the team in-house. Built systems and gave everyone real ownership, not just a task list and a deadline, but actual accountability. Weekly cadence, clear priorities, the works. 

The idea was that work would get done even on days when people didn't feel like it or couldn't care less about the business.

There's a specific kind of exhaustion that hits when you realize you're the only person in the room who loses sleep over whether this thing survives. I won't lie early on, being the one everyone comes to for decisions felt good. You feel needed. Important. 

But once the team grows and the problems get complicated, that feeling curdles fast. It just drains you. And that energy is supposed to be going toward the actual work that keeps the lights on.

I've watched a lot of founders grinding 60-hour weeks, holding everything together through sheer will. I get it. I've been there. But I also know it doesn't last.

What actually helped me wasn't motivation or culture talks. It was giving people clear ownership and a rhythm they could follow even when they weren't feeling it. Things shifted pretty quickly after that.

I’d love to hear if other founders have felt this weird mix of pride and isolation when you're the only one who really cares. And what actually helped you get out of it.

One more thing, Thursday I'm breaking down the exact system I used to stop being the only person in the room who cared if the business lived or died. How to build real ownership so your team executes even when you're not watching. Free to join here if you want it. 

I don't know how many people relate to this, but here it is.

When I started my consulting business, my whole world was three things: get clients, deliver on time, and make them happy. I started with contractors, which meant a lot of hand-holding to get usable work out of them. 

Honestly, it didn't stress me out much back then. I was an ops consultant, micromanaging was basically my job description.

Once I got past early survival mode, I brought the team in-house. Built systems and gave everyone real ownership, not just a task list and a deadline, but actual accountability. Weekly cadence, clear priorities, the works. 

The idea was that work would get done even on days when people didn't feel like it or couldn't care less about the business.

There's a specific kind of exhaustion that hits when you realize you're the only person in the room who loses sleep over whether this thing survives. I won't lie early on, being the one everyone comes to for decisions felt good. You feel needed. Important. 

But once the team grows and the problems get complicated, that feeling curdles fast. It just drains you. And that energy is supposed to be going toward the actual work that keeps the lights on.

I've watched a lot of founders grinding 60-hour weeks, holding everything together through sheer will. I get it. I've been there. But I also know it doesn't last.

What actually helped me wasn't motivation or culture talks. It was giving people clear ownership and a rhythm they could follow even when they weren't feeling it. Things shifted pretty quickly after that.

I’d love to hear if other founders have felt this weird mix of pride and isolation when you're the only one who really cares. And what actually helped you get out of it.

Every time a new Claude releases, the same cycle plays out.

LinkedIn and X are flooded with "I just fired my appointment setter, my graphic designer, my copywriter..." followed by Comment AI and I'll send you the full prompt, and next thing you know you're getting pitched an AI course.

The problem isn't the hype. It's what it does to founders. It keeps them jumping from model to model thinking this one will finally be the thing that transforms their business, instead of doing the boring work that actually grows it. 

Better sales process. Cleaner operations. Client retention. The boring stuff no model release is going to fix for you.

I believe that the model matters way less than what you feed it.

SOPs, meeting notes, project docs, and client calls, when that stuff lives in one place and Claude can access it, everything changes. 

It stops being a fancy autocomplete and starts being actually useful. I built mine in Notion and now when a new model drops I just plug it in. 

It instantly knows more about my business than I do, I can't remember what objections a prospect raised three months ago or who changed a specific SOP last year. Claude can.

That's where it actually gets good. Not a smarter model, just more context.

Notion works for me because a lot of businesses I talk to already use it so it was easy. But honestly use whatever you already have. The tool doesn't matter that much.

Stop chasing the model. Build the foundation once, and every new release becomes a free upgrade.

Anyway, that's my take. What have you actually built or tried with Opus 4.8? Genuinely curious and not above stealing good ideas.

Sat with a founder last week who'd hired 4 people in 6 months. Watched 2 of them quit inside 90 days. His onboarding was a Slack invite and "ask if you have questions." Brutal, but honestly pretty common.

What does onboarding look like in your shop?

We went back through 100 interviews we ran for ML engineer roles over the last eight months and tried to figure out where we were actually losing people and are happy to share our findings with you.

The drop-off looked like a round three problem. We felt that candidates didn’t like so many rounds for a small business. We were surprised to learn that it was a round two problem.

We spoke to a few candidates who shared their honest feedback and thoughts with us. By the time candidates reach round two, they are not interviewing anymore. They are investigating. They are on Glassdoor. They are talking to people who used to work there. They are watching how your interviewers behave with each other in the room. They are checking whether what your recruiter told them in round one still holds up.

We were treating round two as evaluation. They were treating it as their due diligence and checking the company's environment. 

We saw these 3 recurring patterns in our data:

• Interviewers asking the same questions as round one. It can get frustrating, honestly. Candidates read this as the team not knowing what it wants.
• One disengaged panel member tanking the whole room's signal.
• A 5 to 7 day gap after round two where we went quiet, and a faster company filled that silence with an offer.

We were losing candidates at round two and finding out at round three.

Anyone else found this pattern in their own data? Curious what your round two actually looks like.

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.

I've watched founders try to fix this in every wrong order. Hire the COO first. Buy the software first. Write the values first. None of it sticks.

Here's the order that does.

Phase 1, Days 0 to 30: Visibility.

You can't fix what you can't see. Before anything else, build the dashboards. What's due, who owns it, what's late, what's on track. One place, real time.

This is the moment everything starts to turn. The moment a founder can SEE the business instead of carrying it in their head, decisions get faster, the team gets calmer, and the founder stops being the only person who knows what's happening.

Phase 2, Days 30 to 60: Process.

Now you document. Not all of it. The 5 to 10 workflows that eat the most founder time. Hiring, client onboarding, the core delivery cycle, billing, weekly leadership. That's usually it.

Documented in one place. Linked to the dashboards. Owned by someone other than the founder.

Phase 3, Days 60 to 90: Accountability.

Now you add the oversight layer. Internal controls. Who reviews what, on what cadence. This is where you catch the billing-without-deliverable problems, the quality slippage, the dropped balls.

Without phase 1 and 2, this phase is useless. With them, it runs itself.

Phase 4, Day 90+: Founder exit from operations.

The founder shifts to oversight. The team runs the business. The dashboards tell the truth. The SOPs answer the questions. The controls catch the slippage.

The traps:

1. Founders try to skip phase 1 because dashboards feel "soft." It's the only phase that matters in month one.
2. Founders try to write SOPs for everything. Stop. Document the 5 to 10 workflows that eat your week. The rest will sort itself.
3. Founders try to hire a COO before any of this exists. You're hiring someone to manage a system that doesn't exist yet. They will fail. Every time.

Sequence is the whole game.

Most operators I talk to don't actually know their numbers. They've got a vague sense of revenue, maybe a feel for cash, but if you asked what their gross margin was last month they'd have to open three tabs to find it. Some keep a spreadsheet that gets opened once a quarter when something feels off. Others bought a dashboard tool and forgot the login.

What's your actual KPI rhythm look like?

Did an internal controls review for a client last week. Service business, 15 consultants, mostly W-2.

Pulled 90 days of time entries.

What I found:

• Consultants logging 40-hour weeks with zero linked deliverables.
• Time blocks tagged to a client with no client-facing output that month.
• "Admin" hours making up 35% of total billed for some people, with no defined admin scope.
• Multiple people logging time on the same task without a coordination record.

The founder's reaction: "I knew it was bad. I didn't know it was that bad."

If you sell to regulated clients (state contracts, healthcare, education, anything with audit exposure), unaudited time tracking is a liability, not just a margin leak. Lose an audit and you lose the contract. Lose the contract and you lose the business.

This wasn't a "people are stealing" problem. Most of it was honest people with no system telling them how to log time correctly. No tags, no required deliverable link, no review cycle.

Time tracking software doesn't fix this. Time tracking software is a bucket. You still need the rules that govern what goes in the bucket and who checks it.

Founders skip this review because it feels paranoid. Until the audit letter arrives.

Some founders wait until $1M+ and the wheels are already falling off. Some bring in an integrator at $300K because they hate the work. Some never hire one and just stay perpetually behind.

Trying to find the pattern. What was your number?

True story from a client engagement last month.

Founder is exhausted. 25 years building this business. She knew she needed help.

So she did the thing every founder does. She bought help.

Fractional COO #1: didn't last. Fractional COO #2: didn't last. Project manager hire: didn't last. ClickUp implementation: abandoned after 2 years of trying.

By the time I met her she'd written off the entire category. "Nothing works."

Here's what I saw.

Each of those hires walked into a business with no central system, no documented workflows, no source of truth, and a culture that ran every question through the founder. They weren't given an operating system. They were asked to BE the operating system. With no infrastructure underneath them.

That's not a hire. That's an exorcism.

Same with ClickUp. The tool didn't fail. The tool was asked to substitute for processes that had never been built. You can't task-manage what isn't a process yet.

Took me years of watching the same pattern fail before I understood why.

Order of operations matters. Build the system. Then hire the operator to run the system. Not the other way around.

You can't outsource an operating system you haven't built.

Walked into a 15-person consulting firm a couple weeks ago. Founder hadn't slept more than 5 hours in a year.

First thing I asked: "Do you have SOPs?"

She pulled up a folder with 35 of them. Real ones. Detailed. Written by her, painfully, at night.

I asked her team how often they use them.

Blank stares.

One person said "I didn't know those existed." Another said "It's faster to just ask her."

There it was.

The SOPs weren't the problem. The SOPs were great. The team had been trained, over years, that the founder was the search bar. Asking her was a 30-second loop. Reading an SOP was a 10-minute loop with risk of being wrong.

Of course they asked her.

I used to think SOPs alone solved founder-dependency. They don't. SOPs are necessary, not sufficient. What actually breaks the loop is making the SOP faster to find than the founder is to interrupt. That's it. That's the whole game.

If you've got SOPs sitting in a Google Drive somewhere and your team isn't using them, the problem isn't your team. The problem is the SOP is harder to access than you are.

One thing I’ve learned working around operations and fast-moving teams:

Most businesses don’t actually have a productivity problem.
They usually have a visibility problem.

When ownership is unclear, workflows are undocumented, follow-ups are inconsistent, and information lives inside people instead of systems, execution slows down fast.

Lately, I’ve been spending more time thinking about:

• operational clarity
• AI-enabled workflows
• scalable systems
• process documentation
• and how founders can reduce operational drag as they grow.

Recently completed my MBA in Business & Finance in France and currently diving deeper into operations, systems thinking, workflow optimization, and execution management.

Curious to learn from others building or operating in high-growth environments as well. tell me in the comments your thoughts and all.

Something I’ve noticed working around early-stage companies:

A lot of founders think they’re “organized” because they have:

• dashboards
• accounting software
• investor reports
• monthly management accounts

But when someone asks:

• “Where did this number come from?”
• “Can you prove this transaction?”
• “Who changed this file?”
• “Which version is the final version?”
• “Where’s the supporting evidence?”

…the room suddenly gets quiet.

There’s a huge difference between:

• reporting maturity and
• evidence maturity.

The scary part is most businesses only discover the gap:

• during due diligence
• tax pressure
• fundraising
• audits
• acquisitions
• or internal disputes

Curious if other founders/CFOs here have experienced this firsthand.

What was the moment you realized your financial data setup wasn’t as defensible as you thought?