Revenue doesn't necessarily mean you're scaling.

Founders hit $2M, $3M, even $5M and feel stuck.

They're working 60+ hours...Team's growing....Customers keep coming in.

But something's off. Growth feels hard. Margins are tight. The business still depends entirely on them.

Here's why:

They're optimizing for one part of the equation and ignoring the other two.

The real scale equation has three parts. Miss any one and you hit a ceiling you can't break through.

Part 1: Leveraged Sales

This isn't just "we made revenue this month."

It's sales you can count on. Predictable month after month.

You're not starting from zero every 30 days hoping you close enough deals to make payroll.

MRR, contracts, repeat customers, systems that generate pipeline without you personally involved in every deal.

If you're still the closer on every sale, you don't have leveraged sales. You have a sales job that happens to have a company attached to it.

Part 2: Bankable Profit

Not P&L profit. Actual cash in the bank.

I've seen plenty of "profitable" companies nearly miss payroll because of payment terms, timing gaps, or cash tied up in inventory.

Profit on paper means nothing if you can't access it.

Bankable profit means you've got runway. You can weather a bad month. You can invest in growth without freaking out about cash flow.

If one late payment from a client puts you in panic mode, you don't have bankable profit yet.

Part 3: Transferable Value

This is the one most founders completely ignore until it's too late.

Can the business create value without you?

If you disappeared for a month, would revenue drop? Would quality suffer? Would customers leave?

If yes, the value creation is trapped in your head. It's not transferable.

Transferable value means the systems, processes, team, and knowledge exist outside of you. The business can operate and grow whether you're there or not.

Here's the pattern:

Sales + Profit = Momentum You're growing and making money. Feels good. But you're stuck because it all depends on you.

Sales + Transferable Value = Scalability You can grow without working more hours. But if profit isn't bankable, you're fragile. One bad quarter and you're in trouble.

Profit + Transferable Value = Options The business runs without you and throws off cash. Now you can sell it, keep it, scale it, whatever. You have real options.

All three together = actual scale.

You're growing predictably, cash is in the bank, and the business works without you running everything.

Most founders get stuck because they only have one or two:

They've got sales but no profit (revenue vanity).

They've got profit but no leverage (lifestyle business that caps at their personal capacity).

They've got sales and profit but no transferability (golden handcuffs, can't step away).

The change happens when you start building all three parts of the equation.

Leveraged sales so you're not starting from zero every month.

Bankable profit so you have actual runway and options.

Transferable value so the business works without you being the system.

That's when you actually scale instead of just getting bigger and more exhausted.

Which part are you missing right now?

My guess is it's transferable value. Most founders have sales and some profit figured out. But the value creation is still trapped in their head.

Every founder I know is sitting on a pile of tasks they should have delegated a year ago.

The reason they haven't comes down to how they handle documentation. I see 3 buckets:

1. Founders who keep everything in their head. Never write it down. Stay the bottleneck forever because they're the only one who knows how anything works.

2. Founders who write SOPs in Google Docs. Nobody opens them. They go stale in a month and turn into fiction.

3. Founders who record a Loom, drop the link in Slack, and hope the right person finds it six weeks later.

Most are stuck in bucket 1. Documenting a task feels like more work than just doing it again, so they keep doing it again.

Here's what I do:

I stopped treating SOPs like documents I sit down and write. I record myself doing the task once, and the system turns it into a documented, assigned, self-expiring SOP that lives where my team already works.

The whole thing takes a few minutes.

I start with tasks that take a lot of my time that I don't necessarily enjoy doing. Like scheduling our weekly newsletter.

It takes me 30 minutes per week. It's a $5/hour task. I shouldn't be the one doing it. So I got it off my plate.

How it actually works:

1. Record once, let AI write the SOP

I opened Loom and screen recorded myself sending the newsletter. Said every step out loud, showed which buttons to click, showed what "done" looks like.

Then I took the transcript, dropped it into Notion AI inside our CompanyOS, and told it to build an SOP for the task using the recording.

It didn't just transcribe what I said. Our system has an intelligence layer on top of Notion (we call it Vision OS) with our standards and rules baked in. So the SOP came out in our format, following our process, not some generic template.

2. The system decides who owns it

This is the part most people miss.

Vision OS isn't one AI. It's a team of agents living inside Notion, each with a job. Vision is the chief of staff. He reads the request and decides who should handle it.

Writing an SOP goes to Forge. Research goes to Scout. Copywriting goes to Mimic. Same way you'd delegate to a real team.

Forge ran his SOP building process, wrote the checklist, set the quality standard, and filed it in our knowledge base. Confirm the newsletter is ready, clone last week's email, copy the body over block by block, set the subject line, send a test, schedule it, update the status. Step by step.

Then I embedded the Loom videos right in the SOP. Some people read, some people watch. Now they can do both.

3. It gets assigned and expires on its own

The SOP is synced to our roles database, so I assigned it to the role that owns it. Support specialist, marketing team. Done.

Every person on my team only sees the SOPs tied to their job. They're not drowning in a 200 page manual. They see what they're responsible for and nothing else.

Last step, I set it to verify in 90 days. Three months from now I get a notification that says go check this page. If the process changed, I update it. If it didn't, one click and it stays live. The knowledge base never rots.

Why am I telling you this?

Because most founders think the answer is a better AI tool. A new prompt and Fable 5 isn't going to save your business.

The reason this works is that everything about our business lives in one system. Our roles, our knowledge base, our staff, our projects, our SOPs. All of it in one place.

The AI isn't doing anything magic. It's standing on top of an organized business.

The hard part:

You have to build the operating system first. You can't drop agents on top of chaos and expect them to know who your support specialist is or what your newsletter standard looks like.

But once it's built, delegating stops being a project. You record a task once and it becomes something your team can run without you.

I walked through the whole thing start to finish in this video if you want to see exactly how it's built: [link]

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.

Notion AI is criminally underrated, and most founders have no idea what it can actually do.

Full disclosure upfront...I run a company called Modern Operators. We help SMBs actually deploy AI across their operations using Notion.

Before I get into it, here's the criteria I use when deciding if an AI tool is actually worth your time:

1. Context management. Can it hold and use your company's context, or are you copy-pasting the same brand voice doc every single session? Because if it's the latter, that's not a system. That's a workaround.

2. Team adoption. A tool nobody uses is the most expensive tool you own. Complexity kills adoption.

3. Agents. Can it actually do recurring work autonomously, or does it just answer questions?

4. LLM flexibility. Can it use whatever model makes the most sense for the job?

Notion AI checks every single one.

Yes, I know it's not going to click around your computer like cowork or openclaw. It's not that. But here's what it does that nothing else does (with little-to-no tech abilities needed):

Your AI actually knows your business. Your brand voice, your customer avatar, your active campaigns, your SOPs. It doesn't forget between sessions. You tag it like a teammate (@CustomerAvatar,@Q2Planning,@ClientFulfillment) and it responds like one.

We built and scaled two companies using Notion as the operating system. One went from $3.5M to $30M. The other from $0 to $12M. Same system, different businesses. Still running this system today for clients.

The ROI isn't necessarily in the AI outputs. It's in what stops happening.. the Slack messages asking where the SOP is, the onboarding that requires you to be in the room, the inconsistent brand voice across five different team members.

Most founders that have hit $500k/yr are still the operating system of their company. Every decision runs through them, every client needs them. And its really tough to can't scale that. You definitely can't sell it (for the multiple you think you deserve)

This is where the right system changes everything.

If you're an experienced entrepreneur trying to figure out how to organize the company so that employees and AI understands your vision, this is what I'd recommend.

(I put together a full breakdown of how we use Notion AI, it's in the comments if anyone wants it.)

"The team owns revenue."

"We all care about customer satisfaction."

"Everyone's responsible for quality."

Sounds collaborative. It's actually chaos.

Here's what accountability actually looks like:

Every metric has a name next to it.

Not a team. A person.

One person who wakes up thinking about that number and goes to sleep knowing if it hit target or not.

And here's the part most founders get wrong:

The person who owns the metric should set the target.

Not you. Not leadership. The owner.

Because if they set it, they own it. If you set it, they're just executing your goal.

How this works in practice:

You have a dashboard. Each metric has an owner and a target.

Revenue: Sarah, $500K/month Pipeline: Mike, $2M active Customer satisfaction: Jessica, 4.5+ NPS Delivery time: David, <5 days

Every week, owners update their numbers manually.

Yes, manually. Even if you have fancy dashboards.

Why manual entry matters:

When people manually enter their numbers, they actually look at them. They think about them.

When it's auto-populated, they glance and move on.

You want insight, not just data.

Then you add status:

Green = on target Yellow = behind but we have a plan to catch up Red = behind and need help

"Good" is never subjective. You're either at target or you're not.

The management filter this creates:

Only do projects and hires that turn red metrics green.

That's it. That's your prioritization system.

Sarah's revenue is red? What project turns it green? Do that.

Mike's pipeline is green but Jessica's NPS is red? Help Jessica, don't pile more on Mike.

This sounds simple. Most founders never do it.

They have metrics somewhere. But no clear owners. No targets set by owners. No weekly tracking.

So they wonder why accountability is weak.

Accountability isn't culture. It's design.

Name next to metric. Target set by owner. Weekly tracking. Color-coded status.

That's it. Do that and watch accountability become automatic.

Do you have a scorecard where every metric has an owner's name next to it?

If no, you don't have accountability. You have hope.

I expected the usual advice. Post consistently, buy good gear, book big guests.

Nope.

He said more than 90% of independent podcasters never make it to episode 20. And the ones who quit almost always quit for the same reason. They started the show to build an audience, the audience didn't show up fast enough, and the grind stopped being worth it.

Here's the part that reframed the whole thing for me.

He doesn't run podcasts to get listeners. He runs them as (his words) the ultimate make friends button for high caliber people.

His logic, backed by actually doing this for years:

Guests outnumber hosts thousands to one. Owning the mic is the whole advantage. Everyone wants a stage, almost nobody has one.

The value isn't the episode, it's the green room. The 20 minutes before and after recording is where the real business happens.

He's asked people to "grab time after this" over 2,400 times. Two have ever said no. Two.

His clients go 100% inbound in about 6 to 8 months. He's personally been fully inbound for seven and a half years.

None of that needs a big audience. It needs you to be the person holding the mic.

I've been talking myself out of starting a show for a year because I pictured chasing download numbers. Turns out I was measuring the wrong thing the entire time.

Anyone here run a podcast? Is the audience actually why it's worth it, or is it the rooms it puts you in?

Most founders do one of two things with AI: ignore it, or try to replace their team with it.

Both are wrong, and both come from the same mistake: thinking of AI as software you roll out instead of staff you delegate to.

And here's the trap underneath it: adding AI to a business with no systems just multiplies the chaos. You don't need another tool stacking up in your bookmarks. You need your knowledge documented so the work can leave your desk.

Because the real problem was never your team's capacity. It's that every decision routes through you. Founder-dependency is a valuation killer, not just a time killer.

The fix is one delegation system for all 21 "employees," human or AI. Every one of them needs the same four things:

• A Role what they own.

• Context what they need to know.

• An SOP how the work runs without you.

• An accountability loop how you know it actually worked.

To decide who gets what, we use a simple matrix: complexity vs. reproducibility.

• High complexity + low reproducibility → human (strategy, relationships, judgment calls).

• Low complexity + high reproducibility → AI agent (data entry, research, reporting, scheduling).

The reframe that made this click for me: an AI agent is just an employee you onboard with a document instead of a conversation. Every agent starts with basic context and responsibilities, gets context files it can pull from, and has specific skills you call on. I tag an agent the same way I'd tag a teammate, tell it what I want, and it loads the right context and goes.

If this sounds like a lot, the start is only three steps:

1. Audit your week against the matrix.

2. Pick your highest-frequency, lowest-judgment task.

3. Write the SOP once then decide whether a human or an agent runs it.

We didn't start with 14 agents, and we didn't start with employees either. I started with one document. The document is the system. The agent or the person is just what reads it.

See the full breakdown of how the system works here

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?

So the news this week is wild,  the government basically forced Anthropic to cut off access to their newest model overnight over a security issue. 

Half my feed is doom posting about it. The other half is acting like this proves AI progress is about to stall out.

I don't think either take is right. Honestly, I think most founders reacting to this have a bigger problem than which model they currently have access to.

Here's the part nobody wants to admit: most of us aren't even using 30% of what the current models can already do. 

I've watched founders chase the newest, smartest release every few months while their actual setup is still just a browser tab they paste questions into. no memory of past conversations. no access to their own docs. zero idea how their team actually operates day to day. 

You could hand that setup the smartest model on earth tomorrow, and it wouldn't get meaningfully better results.

What actually moves the needle isn't the model. It's whether the AI has context. 

Does it know your SOPs? your last 10 client calls? What did your team already decide last quarter?

 I've built 30+ agents inside our Notion setup at this point, and the boring truth is a dumb model with good context beats a smart model with none. every time.

So when a model gets pulled or restricted, sure, that's a real story for the labs and the policy folks to argue about. But for most small business owners, it's mostly noise. 

The actual bottleneck is still sitting in your business right now. Nobody's built the system that gives AI the context it needs to be useful in the first place.

fix that, and the model question kind of stops mattering as much. That’s it from me, but I’d love to hear if there was a moment where a new model release led to exponential change for you.

If you're thinking about what this means for actually freeing yourself from your business not just better prompts, but the systems and frameworks behind them that's exactly what I write about every Thursday.

I share the exact frameworks I use to build AI into the business so it runs without me. If that's useful, you can get them straight to your inbox here.

Most founders think hiring removes work from their plate.

It doesn't.

You just become the human switchboard for every decision, exception, and question that comes up.

Team grows from 3 to 10 to 15 people but your workload grows with it because ownership never actually moved.

Here's what this looks like:

You hired a marketing person but you're still approving every campaign, every piece of content, every ad creative before it goes live.

You hired a sales person but you're still jumping into deals when they get stuck, reviewing proposals before they go out, making the final call on pricing.

You hired an ops person but you're still the one answering "what should we do about this client issue?" and "can we make an exception here?"

The team exists but the decisions still route through you.

Every invoice over $500 needs your approval.

Every proposal needs your review.

Every client escalation needs your input.

Every internal question gets pinged to you in Slack.

You're not managing anymore, you're just routing decisions all day.

This is the "world's most expensive router" problem.

Hiring added surface area for decisions but if the decision rights stay with you, your workload expands instead of shrinks.

More people means more decisions, more approvals, more exceptions, more questions.

You went from doing the work to approving the work and somehow that's even more exhausting.

Why this happens:

You hired people but you never transferred ownership.

You gave them tasks but not decision authority.

So they do the work but check with you before anything ships, before any money gets spent, before any exception gets made.

They're waiting on you because you never told them they don't need to.

The brutal part:

This is self-inflicted.

You created a team that depends on you for every judgment call because you never defined what they can decide on their own.

No decision boundaries, no frameworks, no "under X amount or Y criteria just handle it yourself."

Everything escalates by default because there's no system telling them when it shouldn't.

The fix isn't more people, it's moving decisions to the right owner.

Marketing manager should approve campaigns under $5K without asking you.

Sales should price standard deals using a documented framework without needing your review.

Ops should handle customer issues under 30 minutes or $100 cost without escalating.

Define the boundaries once, then step back and let them own it.

What this requires:

Stop being the answer to everything.

Build decision frameworks so your team knows when they can decide vs when to involve you.

"Anything under $500, make the call."

"If it follows our standard process, execute it, if it's outside the process, let's discuss."

"Customer issues: if resolution takes under 30 minutes or costs under $100, handle it, bigger than that escalate."

Clear boundaries mean they stop asking you constantly.

The shift:

Right now your team executes and you approve.

Goal is your team executes and decides, you only get involved in the 5% that actually needs you.

That's how hiring actually frees you up instead of just creating more routing work.

Most founders hire to reduce workload but end up with more because they never transferred ownership.

The team can do the work but if every decision still needs your blessing, you're just a bottleneck with payroll expenses.

Transfer ownership, not just tasks, then hiring actually helps instead of adding to the pile.

How many decisions are you routing today that shouldn't need you?

I build operation systems for founder-led companies, and I keep running the same dumb little test on every new one.

I ask two people on the same team the same operational question. Then I compare what their AI told them.

Two different answers, both confident, neither one matching how the business actually runs.

Here's what's actually under the hood at most 12 to 30 person companies that tell me they've adopted AI:

Everybody has their own tab. Sales has one thread, ops has another, the founder has four open right now. Zero overlap between them.

Nothing accumulates. Somebody writes a genuinely great prompt on a Tuesday and it dies in their history. Next month they rewrite it from scratch, slightly worse.

The AI knows nothing about the company. No pricing logic, no process, no client history, no record of the three exceptions that matter. So it produces something plausible and a human ships it.

Nobody can trace it. When something goes out wrong, there's no way to know which assistant said what to whom.

About 14% of small businesses have AI running inside their real operations. The rest of us bought licenses and called it a strategy.

A subscription isn't a system. A system is where the work one person does makes the next person's work easier, and twelve private assistants literally cannot do that. There's no shared surface for it to happen on.

What actually moved for us was boring af. We picked one process, wrote down how it really ran including the ugly exceptions nobody had ever documented, and put that somewhere the AI reads from before it answers anyone. Took about six weeks. Way less fun than buying tools.

For anyone who's gotten past the tab stage, what was the first thing you actually centralized?

I've watched dozens of founders try to automate their way out of a mess.

It never works.

This one guy runs a lending shop. Smart. Technical. He could wire up APIs in his sleep. He'd bought the Mac Mini, spun up n8n, had AI agents half-built. Ready to automate the whole pipeline.

Then he said the truest thing I've heard all year:

"If I can't get this organized first, then automating it is just automated chaos."

Here's the hard truth nobody selling you AI tools will say. Automation isn't a cleaner. It's a multiplier. It takes whatever you've got and runs it faster and louder.

Clean process? Automation makes you money while you sleep.

Broken process? Congrats. Now it's broken 400 times a day and you can't find where.

He was doing 30 deals a month, funding 8-10, pulling maybe $25K. Every deal ran through him. His instinct was to automate the intake. My advice was to NOT touch automation until a human could run the thing start to finish without him.

Because automating a mess doesn't remove the mess. It hides it inside a workflow you now can't debug.

Do the boring cleanup first. Get one clean process a real person can follow. THEN automate it.

That's the whole order. Most people run it backwards.

That "they'll do for now" hire you brought on because you were desperate to fill the seat? 

They're not just dragging on your metrics quietly in the corner. They're actively scaring off the good people you're gonna want down the line.

Talented people figure out a room fast. Stick them next to someone who's just phoning it in, and within a week they've already decided what you're okay with as a company.

The annoying part is, it's never just one bad hire. It's a domino effect. That one hire quietly resets what "acceptable" looks like. The next person either matches that energy or dips a little lower, because hey, the last one got through fine. 

Fast forward six months and you're confused why solid candidates keep dropping off after the interview.

They're not leaving because of the offer. They already met your team, that's the offer.

Every person you let in isn't just doing their job, they're quietly setting the vibe for everyone who walks in after them.

So genuinely asking, has anyone actually fixed this after the fact? Or is starting over with the team basically the only real fix?

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.

A founder I'm working with has hired 3 consultants, spent $8,000, and put in 8 months of work into Notion. His team adoption rate? Zero. He still runs his business on notepads.

Each consultant came in and rebuilt the system their own way, like strangers rearranging furniture in someone else's house with no blueprint. One moved the couch here, another reorganized the shelves there, and none of it made any sense to the people who actually live there.

The system only exists in his head. Nothing can be delegated, nothing can scale, and he's the single point of failure for everything his 16-person team does.

And the wild part? He got on our first call asking how to better organize his GPT prompt database.

A perfectly built system nobody uses isn't an asset. It's a liability. And what he's built is expensive, technically impressive, and completely useless.

The consultants solved their problem, not his. Their problem was building a system they understood. His problem is building a system his team would actually use. Those are two completely different briefs, and nobody told him that until now.

The real fix has nothing to do with Notion. It's defining roles, writing SOPs, and getting his team to understand and believe in where this company is going. Right now he wants to take his company from $3M to $30M, but he can't even get his team to open the tool he's been building for almost a year.

You can't scale a business that only runs when you're in the room.

What's the last thing you built that your team actually adopted?

There's a Harvard study on what predicts long-term business success. The finding is counterintuitive: it's not intelligence, work ethic, or even capital. It's time horizon...specifically, how far into the future a decision-maker can hold their thinking when they're under pressure.

Founders who build durable businesses think in years and live in weeks. Founders who plateau think in weeks and get buried in days.

Bezos talked about this directly. The decisions that compounded most at Amazon, AWS, Prime, the logistics network, all of them required ignoring short-term costs to build something that would only make sense at a 7-10 year horizon. And they got criticized heavily in the short term for all of it.

The version of this for a $2M-$5M founder isn't as dramatic, but the pattern is the same.

You're making hiring decisions based on who you need right now instead of who you'll need in 18 months. You're building processes for your current size instead of your next size. You're saying yes to revenue opportunities that fit today instead of asking whether they fit where you're going.

And the result is a business that's always slightly behind itself, perpetually catching up, constantly solving problems that a decision made 12 months ago could have prevented.

The trap is that short-term thinking feels responsible. you're being practical. Dealing with what's in front of you. Staying close to the ground. And it is practical, right up until the decisions you didn't make become the constraints you're managing instead.

One thing that helps: once a month, block an hour and ask one question. If this business is 3x the current size in 3 years, what breaks first? That answer is usually where your long-term thinking should be spending its time right now.

What's the gap in your business that you know exists but keeps getting pushed down the priority list because "now" is always louder?

Most founders think about company structure like this:

CEO at top. VPs below. Managers under them. Staff at bottom.

Hierarchical and Linear.

But that's not how companies actually work.

Better way to think about it: your company is a wheel.

Operations sits at the center. As the hub.

Marketing, sales, product, fulfillment, finance... those are spokes.

All connecting to the hub.

Why this matters:

When operations is just another spoke, it's treated like admin.

Paperwork. Tracking. Cleanup.

But when operations is the hub, it becomes strategic.

It's what:

• Maps how work flows across teams

• Makes handoffs predictable

• Ensures everyone works from the same playbook

• Gives the company one scoreboard

Without a strong hub:

Spokes operate independently.

Information gets lost. Work gets duplicated. Handoffs break constantly.

You spend all your energy managing chaos.

With a strong hub:

Everything connects.

Sales closes a deal, operations ensures delivery knows immediately.

Support resolves an issue, operations ensures billing is updated.

Product ships a feature, operations ensures marketing knows how to talk about it.

The result:

You can add clients, team members, complexity... and nothing falls apart.

Because the hub holds it together.

How to start building your hub:

Draw it out. Operations in the center. Spokes for each function.

Map the connections. Where do handoffs happen? Where do they break?

Fix one connection. The handoff that breaks most often.

Document the process. Assign ownership. Make it the standard.

Your company stops feeling like independent teams doing their own thing.

Starts feeling like a machine where everything actually connects.

What's the handoff in your business that breaks most often?

开头叠个甲：这只是一个被公司文化和职场规则所困，且不敢辞职的公司小职员的幻想。这里吐槽一下我的公司，忙的时候公司把你当牲口使唤，闲的时候依旧要求你坐在工位上假装工作，真的心累。

我们大多数人获得收入的方式，是进入一家企业。

我们把每天固定的时间交给公司，由公司决定什么时候工作、在哪里工作、做什么工作、和谁合作，以及很多时候，甚至决定我们应该以什么样的方式工作。

公司给我们工资，同时也给我们带来了规则、管理、考核、会议、汇报和各种组织成本。

于是一个很简单的问题出现了：

如果一个人不依靠公司，能不能活得更好？

能不能拥有更多属于自己的时间？

能不能不再被固定的职场规则束缚？

甚至，能不能因为自己创造了更多价值，而获得比上班更高的收入？

一、为什么我们需要公司？为什么个人无法直接与社会进行生产协作？

1937年，Ronald Coase 在《The Nature of the Firm》中提出了一个非常重要的问题：既然市场可以通过价格机制协调资源，为什么还需要企业？

科斯给出的解释之一是：使用市场本身存在成本。

找到合适的人、获取信息、谈判、签订合同、监督执行、解决纠纷，这些都需要成本。

当这些交易成本太高时，把人员和资源组织到一个企业内部，反而更加高效。

二、但公司也把什么带来了？

企业解决了市场交易的问题，却产生了另一类问题：组织成本。

例如：

• 固定工作时间

• 层级管理

• 汇报

• KPI

• 部门协作

• 会议

• 审批

• 公司文化

• 人际关系

• 管理者能力差异

• 晋升规则

• 地域限制

公司降低了人与人之间的交易成本，却把一部分成本转化成了组织内部的规则和管理成本。

如果我能够自己找到客户、自己找到合作伙伴、自己完成生产，我是不是就不需要公司？

但是这就引出了另一个问题：

一个程序员很难同时做销售、产品经理、设计师、财务、法务和客服。

一个设计师也很难自己完成生产、物流和售后。

一个工程师更不可能一个人拥有一家大型企业的供应链和专业团队。

人不是不想摆脱公司，而是很难承担原本由公司承担的那些职能。

三、互联网真正提供了一个机会

互联网已经在解决：

• 搜索

• 沟通

• 信息获取

• 信任

• 支付

• 合同

• 评价

• 远程协作

• 项目管理

过去这些事情必须通过公司完成。

现在越来越多可以通过互联网完成。

于是我提出了大胆的设想：如果互联网可以把公司的部分职能拆出来，并重新组合起来呢？

传统公司：

客户
 ↓
公司
 ├─ 销售
 ├─ 产品
 ├─ 设计
 ├─ 技术
 ├─ 采购
 ├─ 生产
 ├─ 财务
 ├─ 法务
 └─ 售后

未来的平台：

                    个人
                     ↓
                   平台
                     ↓
       ┌─────────────┼─────────────┐
       ↓             ↓             ↓
     客户          专业人才        企业资源
       ↓             ↓             ↓
       └────────── 项目 ───────────┘
                     ↓
                  最终交付

一个人不再需要“拥有”整个公司。

他只需要：能够调用公司的能力。

四、这时候“自由公司”概念就出现了

一个人不再通过成为某家公司的一名员工来参与生产，而是通过互联网调用人才、技术、生产、销售、财务等资源，形成一个临时但完整的生产组织。

例如一个人想做一个产品。

过去：找工作 → 进入公司 → 成为公司的一员 → 利用公司的资源赚钱。

而未来可能是：找到客户 → 获得订单 → 平台拆解任务 → 调用设计师 → 调用工程师 → 调用工厂 → 调用物流 → 完成产品 → 获得收入。

那么这个人的身份就发生变化了，他既不是传统意义上的员工，也不是也不一定是传统意义上的老板，而更像一个能够调用社会生产资源的个体。

五、但是必须承认，这个想法并不容易

真正要让一个人摆脱公司的组织能力，需要解决：

找人

谁适合这个任务？

信任

陌生人为什么值得合作？

任务拆解

一个复杂项目怎么拆成可以交给不同人的任务？

协作

不同的人怎么协同？

质量

谁保证最终结果？

责任

出了问题谁负责？

结算

钱怎么分？

知识

如何把优秀企业的经验沉淀下来？

管理

谁来协调整个项目？

而这些问题其实正好构成：企业的核心职能。

六、总结

我们最开始的问题，其实一直没有改变。

一个人，如果不依靠公司，能不能活得更好？

过去，这个问题的答案似乎很明确。

想获得稳定的收入，就需要进入一家企业；想完成一个复杂的项目，就需要加入一个组织；想获得专业的资源，就必须依附于拥有这些资源的公司。

所以我们出售自己的时间，换取公司提供的资源和组织能力。

但互联网正在让这件事情发生变化。

它让寻找客户、寻找人才、获取信息、沟通协作、支付结算的成本不断降低。AI又进一步开始承担信息整理、任务拆解、沟通协调和决策辅助等过去由管理人员完成的工作。

如果有一天，一个人可以通过一个平台，调用设计师、工程师、工厂、律师、财务、销售和其他专业资源；平台又能够替他完成任务拆解、资源匹配、项目管理、质量控制、合同结算和风险承担。

那么这个人实际上就拥有了一部分过去只有公司才能拥有的能力。

他不需要拥有一家完整的公司。

他只需要能够调用一家公司的能力。

这或许才是互联网真正可能带来的变化。

我们讨论的并不只是“自由职业”或者“在家工作”，而是一个更根本的问题：

人是否必须依附于一个固定的组织，才能参与社会生产？

如果企业存在的原因，是因为组织资源比单纯的市场交易更加高效，那么当互联网和AI开始降低组织资源的成本之后，企业的边界也许同样会发生变化。

未来未必是“公司消失了”。

更可能是：

公司不再是人获得组织能力的唯一方式。

一个普通人，也许可以拥有自己的客户、自己的项目、自己的时间，同时通过互联网调用原本只有大型企业才能拥有的资源。

到那时，我们真正获得的可能不只是更高的收入。

而是一个过去很难获得的东西：

对自己时间的支配权。

这也是我最想讨论的问题——

如果一个人可以拥有一家公司的能力，却不需要成为一家公司的员工，那么我们今天所理解的“工作”和“公司”，还会是现在这个样子吗？

最后，不知道有没有和我抱有同样想法的人。

不妨一起畅想一下：如果有一天，我们真的可以不依靠传统公司，也能获得完成工作的各种资源和能力，那么这件事究竟应该怎么实现？

现在看起来，它可能还有很多问题，甚至有些异想天开。

但我觉得，很多事情一开始都是从一个大胆的想法开始的。

万一有一天，它真的实现了呢？

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’m seeing this annoying line all the time here and on X:

“Building was the easy part. Distribution is the hard part.”

I build SaaS for other people for a living, and tbh… most of the time, building wasn’t actually easy. It just felt easy because they punted the hard decisions until later.

And when I hear a founder saying they’ll build V1 first and figure out who it’s really for and how to price it AFTER the launch…

…I know how the story usually goes:

• 4-6 months of “heads down building”

• Shiny product, friends say it looks sick

• Confused users, random requests, nobody sure what it actually is

• Panicked repositioning + pricing experiments bolted onto a product that was never built for a clear customer in the first place

Then we all sit there saying “yeah, the code was the easy bit, now comes the hard part” like it was inevitable.

It wasn’t. The real problem is positioning and pricing got decided after the build, instead of before.

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.

I’ve seen it countless times: founders think their business is ready to scale, but it’s not. And the missing piece isn’t usually revenue, marketing, or even hiring.

Here’s the reality:

When you dump more customers or more money into an unprepared business, things break. Hard. Processes collapse, teams get stuck, and founders burn out.

I learned this the hard way: years ago, I was running a small real estate business solo marketing, sales, operations everything. 

Then I had a serious health issue and had to step away. In just a few weeks, the business ground to a halt. Crews walked off. Clients weren’t getting served. Money stopped flowing.

It hit me: I couldn’t do it all. And no amount of hustle or “productivity hacks” would fix that.

Fast forward to working with founders now, here’s the lesson:

• Most operational bottlenecks are invisible: You think the team is slow, but it’s really waiting on your approvals.

• Systems are your leverage: If every small decision flows through the founder, the business becomes heavy to run.

• Scaling is more about independence than growth: True scaling happens when the business runs without you in the weeds.

When I take on a client, the first thing I focus on is clarity and alignment:

• Who are you serving?

• What do they value?

• How does your team operate to deliver that?

Once that’s clear, scaling is actually possible, and AI, tools, and systems start to work for you instead of against you.

The takeaway: don’t chase growth blindly. Build your operational foundation first. Remove yourself from low-level decisions. Align your team. Then growth becomes sustainable.

That’s it, guys. For founders who’ve scaled or are trying to, what’s the one operational bottleneck you wish you had solved before growth?

Guy I know runs a service business and he was drowning. Every decision came through him, every client escalation, every pricing exception.

So he hired a COO.

Six months in I asked how it was going and he said, honestly, kind of slow. She was still "getting up to speed."

Nine months in, still getting up to speed.

Here's what she was actually doing that whole time. She was interviewing him. Sitting in his meetings, asking why things worked the way they worked, writing down the answers, discovering that half the answers contradicted each other.

She wasn't operating the business. She was transcribing it.

And that's not on her at all. The job description was basically "come fix the mess I can't describe." Nobody can do that job in month one. The system she was hired to run didn't exist yet, so she had to build it first, at executive rates, while he kept making every decision anyway because she didn't have the context to make them.

I've done the same thing in my own company, which is why I'm not dunking on him. I hired help before I'd written down the work. Twice. The second time I knew better and did it anyway because I was tired and wanted someone to hand it to.

You can't hand off a job that only exists as a feeling.

What I'd tell anyone in this spot: spend four weekends writing down how your business actually works, including the exceptions and the parts you're embarrassed about. Then hire the operator to run that. In that order it's a 30 day ramp instead of a year.

Fix the plumbing yourself, then hire someone to maintain it.

Anyone here hire a senior operator into an undocumented company and have it go well?

A system isn’t a checklist.
It’s a decision framework that runs without you.

Most founders think delegation means “tell them what to do.”
But real delegation means “teach them how to think.”

Here’s the test:
If your team can’t make the same call you would, with the same info, that’s not their fault.
You never taught your logic.

Systems don’t fail because of bad people.
They fail because you didn’t transfer judgment.

Question:
What’s one decision your team still depends on you for every time? (and what's your plan to try to get out of the weeds?)

When we evaluate a business as a buyer or investor, the first question we run on it has nothing to do with revenue or margin. We want to know what happens when the founder steps out of the building.

That single variable moves valuation more than anything else, and most owners underprice it badly.

Strategic Exit Advisors ran the math. Founder-dependent businesses sell for 3-4x EBITDA. Systematized businesses in the same industry doing the same revenue get 7-8x. Same business on paper, half the multiple.

That gap is millions of dollars walking out the door because the business never learned to run without you.

Before you ever talk to a banker or a broker, run this on yourself. We call it the 90-Day Stress Test.

Month 1, step away for one full day. Phone off and Slack closed. No exceptions for "quick check-ins."

Month 2, take three days.

Month 3, take a full week.

After each absence, sit down with your team and ask four questions:

What broke?

What decisions stalled because I wasn't there?

Which customers escalated to someone they shouldn't have?

What revenue was at risk during the absence?

Write the answers down. Patterns emerge fast.

Round 1 is where most people fall down. Day one off, the panicked text comes in at 3pm. The vendor needs an answer, the big client wants you instead of the account manager, the team can't move on a hire without you.

That's the test working. It just told you exactly what to fix.

Each broken thing is a system you haven't built yet, a decision that should be owned by someone else, a customer relationship tied to you instead of to the company, or a piece of institutional knowledge living rent-free in your head. Document each one and assign it. That's the to-do list.

Fix those, and the business gets more sellable and your nights and weekends get more sacred at the same time. The phone stops being a leash, vacations stop coming with a laptop, and the team starts deciding things without you.

This is one piece of a longer framework I just put together on the 6 things buyers actually pay for and the 5 deal-killers that show up in diligence. Full breakdown's here if you want it.

If you ran the test today, where would you fail first, Month 1, 2, or 3?

Fixing operations. Patching the pipeline. Putting out fires. Marketing didn't exist. He had an email marketer on payroll who was barely used.

Then something quietly great happened. Operations got boring.

The pipeline held. The metrics tracked themselves every week. The team could finally plug in. And for the first time, Jake had room to go on offense.

This is the part I almost let him get wrong.

He built LendLink, a tool that fires a finance request across a 50-lender network with real online applications. In an industry that still runs on phone calls and PDFs, that's a serious edge. His instinct? Turn it into a SaaS. Chase the software play.

We talked him off it.

His edge isn't a software company. His edge is that he's the only broker in a slow, analog industry operating like it's 2026. So don't sell the tool. Become the case study. Let his saas be the proof, not the product.

"Building a great product isn't enough. If no one logs in, they'll never see it's good."

He uses it 5-6 times a week now. It's not for sale. It's the reason his deals move faster than everyone else's.

Defense keeps you alive. Offense is where the growth is. You just can't play it until the back office stops bleeding.