How to Hire an Integrator (in the Age of AI)

The right-hand hire that changes everything, and how to make it without losing control

By Scott Oldford

I made myself obsolete on purpose

Two years ago I decided to make myself obsolete inside my own business. I built the AI stack. I hired the person I should've hired five years earlier. I handed over the day-to-day. I stopped being the bottleneck.

Today my team is three humans. Five years ago the same output would've taken a team of thirty. My AI writes better first drafts than I do. My ad manager is an agent. My operator runs the business.

And I'm free to do the work only I can do.

This is a guide about the hire that made that possible. The right-hand hire. The integrator. The operator. Whatever you want to call the person who takes your ideas and turns them into shipped reality without needing you to hold their hand.

Most founders wait too long to make this hire. I did. I've watched hundreds of founders do it. And in nearly every case, the delay is not a strategy problem. It is a story problem. A story we tell ourselves about what happens if someone else touches the thing.

This guide breaks that story.

If you are doing $500K to $3M and you still touch every launch, every client, every ad, every product decision... this is for you.

If you are earlier than that, you are welcome to read it. Some of it will apply now, some of it will apply later. Bookmark it and come back when the readiness audit in Chapter 8 says yes.

Take what applies. Skip what doesn't.

– Scott

Chapter 1: The four blocks that keep you from hiring an integrator

If you haven't hired this person yet, it's not because you couldn't find them. It's because one of these four things is running the show.

Block 1: Control

The story: "No one will do it as well as me."

This is the most common one. It sounds like a standards problem. It's a scorecard problem.

You've never written down what "as well as me" actually means. So no one can meet it. Which means you'll always be the only person qualified... by definition.

The fix is not lowering your standards. The fix is externalizing them. Writing them down. Making them teachable. If you can't explain what winning looks like in one page, you don't have standards. You have moods.

Block 2: Trust

The story: "I've been burned before."

You hired someone who didn't own it. They took a paycheck and left you doing all the thinking. Now every résumé looks like the last betrayal.

Scar tissue is data. It's also just data. You hired the wrong altitude last time. You hired a doer when you needed an owner. That's a hiring mistake, not a species problem. Different fish, same lake.

The next hire won't be like the last one because you're not going to hire like you did before. Read the rest of this guide and you won't.

Block 3: Identity

The story: "If I'm not the one doing it... who am I?"

This is the one nobody talks about. And it's the one that kills more businesses than markets, competitors, or cash.

You built this thing. You are the person who does. Delivery, marketing, sales, product, ops. You are the founder-as-hero. And somewhere in the back of your head, if someone else can do it, you're afraid you become... optional.

You don't. Your job just changes. You go from being the person who does the work to being the person who decides what work matters. That's a bigger job. A harder job. And it's the one your business needs you in.

Block 4: Money

The story: "I can't afford them yet."

Every operator hire costs money before it makes money. That is how the math works.

But here's the actual math. You're the highest-paid person in your business. If you're doing $30-an-hour work as the founder, your business will always cap out at $30-an-hour output. An operator who takes 20 hours of that work off your plate every week has paid for themselves before you've adjusted to their name.

You can't afford NOT to. And in the age of AI, the number is smaller than you think. We'll get to that in Chapter 3.

Which one is yours?

Name it. Say it out loud. If you can't tell which one it is, it's probably identity. That's the one that hides best.

Then keep reading.

Chapter 2: Integrator, chief of staff, or operator. What to call this person and what they actually own

Language matters here. There are three names for this role floating around online, and they mean different things.

Integrator is the EOS term. It comes from Traction and the "visionary/integrator" pairing. Best-known name, most search volume, most baggage. If you've read Traction, this is the mental model you have.

Chief of Staff is the higher-altitude version. It comes from politics and enterprise, and it usually means a strategic thought-partner who runs the founder's calendar, priorities, and team on their behalf. Higher status. Usually smaller portfolio of direct ownership.

Entrepreneurial Operator is the term I use. It means someone who owns outcomes end-to-end in your business. Not managing your calendar. Not just tracking projects. Actually running the work.

For the rest of this guide I'm going to use "integrator" and "operator" more or less interchangeably. The role I'm describing is closer to what the online business world calls an integrator than a chief of staff. The COO title is for later, when they've got a team of five or more reporting to them.

What this person is NOT

Not a VA. A VA takes tasks off your list. An operator takes outcomes.

Not an assistant. An assistant manages your calendar, your inbox, your reminders. An operator manages your business.

Not a project manager. A project manager tracks deadlines and pings people. An operator owns the outcome of the project, which means they'll blow up the deadline if the deadline is wrong.

Not a COO. A COO runs operations at scale, with a team under them, and typically comes in later. If you don't have the revenue for a COO, don't call this person one.

What they ARE is an owner. Of outcomes. Someone who takes your ideas... and turns them into shipped reality.

The four zones they own

Product and project delivery, end-to-end. Whatever you're currently doing at the "make the thing happen" layer. Client builds. Course launches. Product releases. Books. Funnels. The stuff that's on your plate today, that shouldn't be.

Team, ops, and the weekly rhythm. The contractors, the VAs, the freelancers. The meetings that need to happen. The dashboards. The scorecards. The Friday review. The Monday plan. The stuff that keeps the machine running.

Hiring, onboarding, and firing the rest of the team. The person you hire to own this becomes the person who hires everyone else. That's the compound-interest hire. One good operator hires two more good people. Two more good people become five. That's how a business gets built.

Customer experience, retention, and financial ops. The relationship layer and the money layer. Who's happy. Who's leaving. What we're collecting. What we're spending. Not doing the books, but knowing the numbers and calling out what's breaking.

They don't do all four in week one. They own all four by month six.

Chapter 3: The AI multiplier. Why one integrator can now do the work of four

Here's the part nobody wants to say out loud.

One integrator with AI, right now, can do the work of four hires from three years ago.

This is not a hype line. This is the new baseline. I run a team of three humans that would've required thirty five years ago. I lost my ad manager and replaced them with an AI agent that runs my Facebook ads. I built the entire suite of AI products I sell during nine months where I was too sick to look at a screen for more than a few hours a day. My AI writes better first drafts than I do, and I don't have to edit them heavily.

I made myself obsolete on purpose. That was the goal.

The math

The old math: hire a project manager. Hire a marketing coordinator. Hire a client success person. Hire a bookkeeper. That's four salaries, four sets of benefits, four onboardings, four sets of quarterly reviews, and coordination cost between all four. Plus you're still the bottleneck for every decision that spans two of their roles.

The new math: hire one integrator. Give them the AI stack. They cover all four zones. Total cost is lower. Coordination cost is zero. Output is higher, because there's no game of telephone between four people who each own a slice.

Ad copy? Their AI writes it. They review it. It ships.

Client onboarding email? Their AI drafts it. They approve it. It goes out.

Weekly financial report? Their AI pulls it from Stripe, formats it, flags what's off. They read it. They tell you what needs your attention.

Project plan for the next launch? Their AI generates a first draft based on your last three launches. They edit it. They run it.

The pattern is the same across every zone. AI drafts. Operator decides. Human ships.

The reframe

This is the part that changes the whole hiring conversation.

The operator's real job is no longer doing the work. The operator's real job is orchestrating the agents that do the work. And using judgment where AI can't yet.

Which means the skill you're hiring for is not "can they do project management" or "can they write copy" or "can they run ads." AI can do all of that now. It'll do it better in six months. Better again in a year.

The skill you're hiring for is: can they run an AI-native operating system inside your business, and can they use judgment on top of it. Can they read what the AI produces and know when it's wrong. Can they know when to override the machine. Can they see the pattern the machine can't see yet.

That's a different hire than the one you were making three years ago.

Which brings us to the line you need to read twice.

You don't hire someone with an impressive skill stack. You hire the human you actually want, with a deep-learning mindset. Everything else is teachable in 90 days.

The résumé matters less than it ever has. What matters is: can they think, can they learn fast, can they own the outcome, and do you actually want to be around them for the next three years.

That's the hire.

Before you keep reading

If what you're reading is landing, and you want the book that goes deeper on how to actually build the business this hire enables... grab a copy of Read This If You're Scaling. It's the fastest way to see the full picture of what changes on the other side of the bottleneck.

Get the book →

Chapter 4: Where to find your integrator (they're probably already in your audience)

Most founders make this hire harder than it needs to be by looking outside their business first. Job boards. LinkedIn. Recruiters. Cold outreach. Chief-of-staff communities. That's where you think this person lives.

They don't. A lot of the time, they're already in your world.

The best integrator I've watched anyone hire in the last five years came from that founder's own paid program. She'd been in his community for two years. She'd bought his stuff. She'd used his frameworks in her own business. She knew his voice, his methods, his customers, his product before she ever sent a résumé.

I've seen this happen over and over. The operator who ends up transforming a business is often:

A customer of your low-ticket offer who's between things
A member of your mastermind who's ready to work IN a business instead of on their own
A past client who did the work and knows why your stuff wins
Someone who's been in your Facebook group for eighteen months and hasn't missed a post
A former coach or consultant who's tired of managing their own funnel and wants to help someone else scale theirs

Look at your customer list. Look at the people who reply to your emails. Look at who's showing up on your live calls with real questions. Look at your top 20 buyers, the ones who've bought everything you've made.

There's a candidate in that list. Probably more than one.

Why hiring from your audience works

They know the voice. They know the customer. They know the offer stack. They know the values. They know what you actually stand for, because they bought in with real money.

You skip the six months of "learning the business." You skip the interpretation risk on your brand. You skip the "will they get it" question. They already got it, back when they swiped their card.

The onboarding curve is a third of what it would be for an outside hire. Maybe less.

How to open the door

If you have a program, post inside it. "Looking for someone who wants to help me build the next version of this. Reply if that's you."

If you have a mailing list, ask them. "I'm hiring my right-hand person. If you've been around a while and this feels like your next move, tell me."

If you have a community, watch who steps up when there's a question no one else can answer. Watch who solves other members' problems for free. Watch who ships their own stuff using your frameworks. Those are your candidates.

You don't need to run a full search. You need to open the door.

Then run them through the scorecard and the interviews later in this guide. Same bar. Same rigor. Just a much shorter runway.

One example from a client

A course creator I work with in the seven-figure range spent six months searching LinkedIn for the right integrator. Interviewed nine people from outside. Nothing landed. The tenth interview was a customer who'd been in her program for eighteen months and had DM'd her the week before saying "I'd love to help you if you ever need it." Two years later, that hire runs her entire operation.

That's not a rare story. That's the story.

Chapter 5: How to onboard your integrator using AI

The single biggest reason founders don't let go is because they've never externalized what's in their head. It's all trapped in there. Every context. Every relationship. Every decision. Every "we don't do it that way" that they've never written down.

That used to take a year of shadowing to transfer. Now it takes about six weeks. Because AI can do most of the extraction for you.

Here's the exact workflow I use, and the workflow I teach every founder I work with.

Step 1: Record everything for two weeks

Turn on Fathom or Otter or Fireflies on every meeting. Client calls. Internal calls. Sales calls. Team check-ins. Every conversation.

Voice-memo your decisions as you make them. Open your phone, hit record, talk for two minutes: "I just decided to push the launch. Here's why. Here's what I told the team. Here's what I'm worried about." Every day. Multiple times.

Screen-record yourself doing the recurring stuff. Uploading videos. Reviewing dashboards. Doing your Monday plan. Doing your Friday review. Ten to fifteen minute Looms, no editing.

Two weeks of this generates hundreds of hours of raw context. That's the input.

Step 2: Extract with AI

Take all of that raw material and drop it into ChatGPT or Claude. Not one file at a time. In batches, by category.

Then prompt it:

"Here are twenty of my recent client calls. Extract every recurring pattern in how I handle clients. What do I always say? What do I never say? What are my non-negotiables? What are my tells for when something is going wrong? Write it as a playbook for someone new."

"Here are three weeks of my daily voice memos. Extract my decision-making framework. When do I say yes to opportunities? When do I say no? What are my values in practice, not in theory? Write it as a decision guide for my new operator."

"Here are the Looms of me doing my weekly review. Extract the exact steps, the questions I ask, the metrics I look at, and the pattern of how I make the week's plan. Write it as an SOP."

You do this once per zone. Client work, marketing, sales, operations, finance, team management, product.

What comes out is a playbook of you. In your voice. With your logic. Ready to hand to your operator.

I did this for my own business over about a month. The output was a hundred-plus-page document that captures how I think, how I decide, how I run the business, and what I care about. My AI knows me better than my own team does. And now I can hand that document to any operator I hire and they can be running at 70% of my judgment inside 30 days.

Step 3: Give them the same AI as their onboarding buddy

This is the part people miss.

Your new operator's first tool is your AI, not a Notion doc. The AI you've fed everything to. The one that knows how you think.

Set them up with access. Tell them "when in doubt, ask this. It knows what I'd do. If it doesn't give you a clear answer, THEN come to me."

Week one, they're asking the AI. Week four, they're getting most answers from the AI. Week eight, they're only coming to you on genuinely new decisions.

You're not their bottleneck anymore. The AI is their first-pass mentor. You're the escalation.

Step 4: The stack that actually works

Not gospel. Just what I've seen work over and over.

Meeting capture: Fathom or Otter. Fathom for internal-friendly, Otter for cheap and universal. Fireflies if you're already in Slack.
Voice memos: iPhone Voice Memos, then Whisper to transcribe. Or Otter directly.
Screen recording: Loom. Full stop.
AI extraction and playbook building: ChatGPT Projects or Claude Projects. Feed each zone as a project. Ask questions inside the project.
Knowledge base and SOP home: Notion. Nothing beats it for this. Your operator's home base.
Ongoing memory: custom GPT or Claude project, per zone. So the AI keeps learning as you go, not just from the initial dump.

The point is not the tools. The point is that you have to externalize the business from your head before you can hand any of it to a human.

Do this before you hire, or in the first two weeks after they start. Not month six.

Chapter 6: The four mistakes almost everyone makes when hiring an integrator

I've watched hundreds of founders try to hire this person. Here are the four mistakes that show up over and over. All four apply, in different combinations. Read them all.

Mistake 1: Hiring a doer when you need an owner

You write a job description that lists tasks. "Manage the calendar." "Coordinate launches." "Handle client onboarding."

Then you're surprised when the person you hire... does the tasks. And nothing else.

You needed someone who would look at the launch and say "the offer is wrong, we should push it." You got someone who ran the checklist.

The fix: hire on outcomes, not tasks. The job description says "own the launch," not "coordinate the launch." Say "own the client experience," not "handle onboarding." Words are the tell. Watch yours.

Mistake 2: Hiring too junior to save money

You paid for a junior person for a senior job. You saved on paper. You cost yourself five times that in the business.

Junior operators are still learning what a business is. They don't have the pattern-recognition to spot what's breaking. They need you to tell them what to do, which means you're still doing the job... just with more meetings.

The fix: pay for judgment, not seniority. An operator with three to seven years of running things in a small business is often the right hire. Not fifteen years at a Fortune 500. Not two years out of school. The middle ground, where they've seen enough to have opinions but not so much that they're bringing corporate baggage.

Mistake 3: Hiring on vibes with no scorecard

You met someone on a podcast. You loved them. You hired them. You didn't write down what winning looked like.

Three months in, you resent them for not doing things you never actually asked them to do. They resent you for changing your mind about what mattered every week. Both of you feel unseen. Nobody's wrong. The scorecard was missing.

The fix: write the scorecard BEFORE you post the job. What does month 3 look like? Month 6? Month 12? What are the three things that would make you say "this hire was the best money I've ever spent"? Write those down. Then you're hiring against something real.

Mistake 4: Shadow-managing after they start

This one kills more integrator hires than the other three combined.

You hire them. They start. They begin owning things. And every time they do it a way that's different from how you'd do it... you step in.

You edit their emails before they go out. You rework their project plan. You take back the client call. You approve the ad copy. Every week, you take back a little more of the job you hired them to own.

Six months in, you're doing the job again. They're a very expensive assistant. You blame them for not stepping up. They blame you for not letting them.

The fix: 90-day handoff protocol, later in this guide. And a rule. After day 30, if you're still in the doing seat on their zones, you failed the hire. Not them.

Chapter 7: The trap of hiring someone too much like you

This is the trap I've watched founders fall into more than once. And it's the one nobody warns you about.

You feel the chemistry in the interview. You "vibe." They think like you. They talk like you. They finish your sentences.

You hire them.

And six months later, nothing has changed. Because they are you. They have the same strengths you have. Which means they have the same weaknesses. They avoid the same conversations you avoid. They procrastinate on the same things you procrastinate on. They love the parts of the business you love, and they hate the parts you hate.

The parts you hate are the parts you needed to hand off.

Which means the parts that were broken before... are still broken.

The best integrator hire is a complement, not a mirror.

What to look for instead

If you're a visionary who lives in ideas, hire someone who lives in systems. Someone who gets bored by big-picture strategy and comes alive making things run. If ideas are your zone, execution should be theirs.

If you're a builder who loves the zero-to-one, hire someone who loves the one-to-ten. Someone who wants to take what exists and make it more, and better, and more reliable, and doesn't need the dopamine of building something new from scratch every quarter.

If you're a public-facing founder who runs the marketing and the sales and the content, hire someone who wants to work in the background. Who has no interest in being on camera. Who wants to run the machine, not be the face.

If you're the emotional one who gets excited and crashes, hire the even one. The one whose baseline never moves. Whose Tuesday looks like their Friday looks like their Monday.

The rule: if your integrator's greatest strength is your greatest strength, you hired wrong.

How to test for this in the interview

Ask two questions.

"What are the parts of running a business you love that most founders hate?"

Listen. If they say the same things you love, that's a flag. If they say things you hate... celebrate.

"What are the parts of running a business you hate that most people love?"

If they hate what you hate, walk away. If they say "honestly, I don't hate any of it, I just like different parts," that's a green light. They're wired for the ops seat.

You want someone who wakes up excited about the things that drain you. That's the sign.

Chapter 8: The readiness audit. Are you actually ready to hire an integrator?

Not everyone reading this is ready to hire yet. That's fine. Better to know now than to burn money finding out.

Answer these ten questions. Yes or no. No maybes.

Do I have twelve months of this person's compensation set aside, whether they perform or not?
Can I write down what "winning" looks like for this role in one page, before I post the job?
Am I willing to let them make decisions I disagree with, and honor those decisions in front of the team?
Are there at least three projects, products, or systems in my business right now that need an owner who is not me?
Will my business survive if this hire takes six months to fully ramp?
Am I willing to change the way I run my week, the way I run my meetings, and the way I make decisions, to accommodate this person's ownership?
Do I have a clear picture of what I'll do with the time this person frees up... and is that picture bigger than "rest"?
Have I let go of any hire in the last twelve months for a reason other than "they weren't a fit"? Meaning, have I built the emotional muscle of the hard conversation?
Am I willing to pay this person more than anyone else in my business... possibly more than I've ever paid anyone... because their leverage is that high?
Can I say out loud, without flinching, "I want to hire someone who is better than me at running the day-to-day of my business"?

Scoring

8 to 10 yesses: you're ready. Keep reading.

5 to 7 yesses: you're close. Name the specific nos. Fix those first. Might take 90 days. Might take a year. Come back when they flip.

Under 5 yesses: you're not ready yet. That doesn't mean you never will be. It means the block from Chapter 1 is still winning. Don't hire under 5. You'll burn the money and, worse, you'll burn a good person.

If you scored 8 or higher

This is the exact work I do inside The Online Business Accelerator. Every month, my team and I help founders at your stage build the scorecard, run the search, do the interviews, and make the hire that changes everything.

If you want help getting this hire right the first time, come see what OBA looks like.

Learn more about OBA →

Chapter 9: The scorecard, the compensation, and the four interview questions

Three things in this chapter. The artifact you post the job with, the deal you offer, and the four questions that actually reveal who this person is.

The integrator scorecard

Write it before you post. Not after.

Section 1: What this role owns. The four zones. In your own words, with your specific business named.

Section 2: Outcomes at 90 days. Three to five specific outcomes. "By day 90, they have taken over full ownership of our client onboarding, including running the kickoff calls." "By day 90, they have documented every recurring workflow in the business."

Section 3: Outcomes at 180 days. Bigger. "By day 180, they have hired at least one additional team member and onboarded them." "By day 180, our client retention has moved from X to Y."

Section 4: Outcomes at 365 days. Bigger still. "By day 365, they run the weekly leadership meeting, own the P&L conversation, and manage a team of three." "By day 365, the business runs for two full weeks without me touching it."

Section 5: Behavioral non-negotiables. Six to eight traits. Not "team player." Real ones. "Makes decisions with incomplete information and updates when better information arrives." "Uses AI daily and can show me how." "Says the hard thing in the room, on the record, respectfully." "Reads a P&L without being scared of it."

This is what you post. This is what you interview against. This is what you review against.

How to think about compensation

I'm not going to give you specific numbers. Different businesses, different markets, different candidates. But here's how to think about the structure.

Base plus bonus is the default. A reasonable base that pays the mortgage, plus a bonus tied to the scorecard outcomes. Not tied to revenue directly, unless you want them managing to revenue over everything else. Tied to the outcomes you actually care about.

Profit share is often better than equity. Equity in a small online business is usually worth less than the paper it's written on. There's no exit event coming. Profit share pays them out of actual cash generated, quarterly or annually. It aligns them with the health of the business without the legal complexity of equity.

Equity is for the operator who's replacing themselves out of their own business to come build yours. That's a rare hire, and worth it when you find them, and it requires equity to attract them. Real equity, vested over three to four years, with real language.

Compensation should feel slightly uncomfortable to you. If the number feels easy, you didn't hire high enough for the role. Great operators are aware of their leverage. They know what they're worth. Pay to the top of the market for what you can afford, and let the scorecard hold them to it.

Reset the deal at day 180. Whatever you offer at hire, tell them: "At day 180, if you're crushing the scorecard, we redo the deal upward." That's what a great operator wants to hear. It says you're playing the long game with them.

The four interview questions

Skip the standard interview. Ask these four questions and shut up.

Question 1: Tell me about the last thing you shipped that nobody asked you to ship.

You're listening for ownership. Doers wait to be told. Owners see something broken and fix it, without permission, and then explain why later. If they can't name something, they're a doer.

Question 2: Walk me through a time you were wrong about something important. What changed?

You're listening for learning speed. If they can't remember being wrong, they're either lying or they've never been in the arena. Both are disqualifiers. Owners are wrong constantly, and they metabolize it fast. Doers get defensive.

Question 3: Show me, right now on this call, how you'd use AI to do one of the tasks in this role.

You're listening for AI-nativity. Not skill... nativity. Do they open ChatGPT while you're talking? Do they know how to prompt? Do they know what agents are? A candidate who doesn't reach for AI within thirty seconds of hearing this question is not going to survive the next three years in your business.

Question 4: What would you fire yourself for in year one?

You're listening for self-awareness. The best operators have a sharp read on their own failure modes. They'll tell you "I'd fire myself if I stopped saying the hard thing" or "I'd fire myself if I got too comfortable and stopped raising the bar." Candidates who can't answer this... or who say something evasive like "I'd never let it get to that"... are hiding. Don't hire them.

Four questions. Fifteen minutes each. You'll know.

Chapter 10: The 90-day handoff protocol

This is the part where most founders lose the hire they just made.

You did the work. You found the person. You wrote the scorecard. You posted the role. You interviewed. You hired. And now, if you don't do this next part correctly, you undo all of it in the first ninety days.

The 90-day map

Weeks 1 and 2: shadow and absorb. They shadow you. Every meeting, every decision, every send. They take notes. They Loom what you do. They spend hours inside the AI playbook you built in Chapter 5. They don't do the work. They watch and document. You keep doing everything.

Weeks 3 and 4: draft. They draft. Everything. Emails, project plans, decisions, briefs. You approve or edit. They ship. You're still the final approver, but you're not the drafter anymore.

Weeks 5 through 8: ship. They ship without your approval on the day-to-day. Weekly review. You're looking at outputs, not inputs. If they made a call you wouldn't have made, and it worked... say so. If it didn't work, ask what they learned.

Weeks 9 through 12: own. They own the outcomes. Monthly review, not weekly. You're looking at whether the scorecard numbers are moving. You're not in the doing seat anymore. You're the strategic partner and the escalation point.

Day 90: scorecard review. Sit down. Look at every outcome you wrote. Are they hitting them? Trending toward them? Or missing them?

The first 30 days management rhythm

The rhythm is what makes this work. Not the meetings. The rhythm.

Daily, first 14 days: 15-minute end-of-day sync. They tell you what they saw, what they did, what they don't understand yet. You clarify one thing. You don't add three new things.

Weeks 3 and 4: shift to three touchpoints a week. Monday plan, Wednesday check, Friday review. Each one is 30 minutes max. The Wednesday check is where things surface. Don't skip it.

Weeks 5 through 8: weekly Monday plan and Friday review. That's it. If they want an ad-hoc conversation, they book it. If you want one, you book it. Otherwise, one touchpoint on each end of the week.

Weeks 9 through 12: weekly review, plus a monthly deep-dive on the scorecard. The daily and midweek check-ins are gone. If you're still doing them at week 10, you're shadow-managing. Stop.

Format of every review: three questions.

What did we say would happen this week, and did it?
What did you learn?
What do you need from me?

That's it. Not a status update. Not a task list. A pattern-and-learning conversation.

Day 90 decision

Three options at day 90:

Hitting or exceeding: double down. Give them more scope. Raise the compensation. Lock them in.
Trending toward: confirm the plan. Extend the review to day 180. No changes.
Missing badly: have the hard conversation. Not a firing conversation yet. A "here's what I'm seeing, here's what needs to change, here's what happens in thirty days if it doesn't" conversation.

At day 180 you either have your integrator or you don't. Don't drag it past that.

The rule

Print this line and put it on your wall.

After day 30, if I am still in the doing seat on their zones, I failed the hire, not them.

Read it every Friday.

Chapter 11: How to know when it's working, and when to cut

Somewhere in months two through five, you'll ask yourself the question. "Is this working?"

Here's how to answer it honestly.

The metrics

Look at the scorecard first. Cold. What did you say would happen by day 90? By day 180? By day 365?

If the 90-day outcomes are hitting, it's working. If they're 80% there and trending upward, it's working. If they're at 40% and stalled, it's not.

Don't rewrite the scorecard in your head to make them look better. The scorecard is the scorecard. That's why you wrote it before you hired.

The gut checks

Metrics alone don't tell you. Also check these.

Are the fires getting smaller? Not disappearing. Getting smaller. If the same fires you had before them are still yours to put out, they're not owning. If new, different, smaller fires are emerging that they're handling on their own, that's working.

Do you dread the Monday plan meeting? If yes, something's off. Either they're not prepared and you're carrying it, or you're not letting them lead it. Either is fixable, but you have to name it.

Are they surprising you? Great operators surprise you regularly. They ship things you didn't ask for. They flag things you didn't see. They save money you didn't know was being wasted. If nothing they do surprises you, they're a checklist executor, not an owner.

Are they saying "no" to you? This is the big one. Great operators push back. They tell you when your idea is bad. They tell you when your timing is wrong. They tell you when the team is at capacity. If they've never said no to you, they're managing you, not the business.

Are they hiring, firing, or restructuring under them? By month four or five, they should be making people decisions. Not everyone. But at least one meaningful call. If they haven't, they're still in shadow-mode.

Does the business look different than it did four months ago? Not the strategy. The operations. The way work moves. The rhythm. If it looks identical, they haven't put their fingerprint on anything. Which means they're not owning.

The signs it's not working

Any three of these together is a serious flag.

Scorecard outcomes are missing at day 90 with no clear reason
You're still doing the work you thought you handed off
They keep asking you to make decisions they should be making
The team is not clearer, not stronger, not more coordinated than before
You feel more tired, not less
They haven't disagreed with you on anything of consequence
You catch yourself thinking "I could just do this myself" more than once a week

If three or more of these are true at day 90, have the conversation. If they're still true at day 120 after the conversation, cut.

The cut

Cutting an integrator is harder than cutting a VA. They know more. They see more. They're plugged into the team.

Do it fast when you know. Not fast in impulse. Fast in execution once you've decided.

Two-week transition. Clear severance. Genuine warmth. No dragging out the "maybe it'll get better" story past the point where you know.

The best founders I know have cut at least one integrator. Sometimes two. It's not a failure. It's a data point. It teaches you what you actually need in the seat. The next hire is always better because of it.

The worst mistake is not the cut. The worst mistake is holding on for another six months because you don't want to have the conversation.

Chapter 12: The founder you become on the other side

There's a version of you that exists on the other side of this hire that you cannot access from where you're sitting right now.

The version who plans instead of executes. Who thinks in years instead of weeks. Who calls the shots on what the business becomes, instead of running the treadmill of what the business is.

The version who wakes up and doesn't have twelve fires. Who has one big question. And who spends the day on that question, because the fires are being handled by someone whose entire job is handling fires.

That version of you gets to build the things that only you can build. The category-defining stuff. The books. The frameworks. The high-stakes bets. The founder-led moves that no operator, no matter how good, can make on your behalf.

Your job stops being to do the work. Your job becomes to see the future, and to point at it, and to say "we're going there."

That's the trade. You give up the seat that makes you feel useful. You gain the seat that makes you actually valuable.

And the business you build from that seat is a different business than the one you're building right now.

I promise you that.

What to do this week

Three steps. Sequenced. In order.

Today: do the readiness audit. Ten questions. Fifteen minutes. Score yourself honestly. If you're under 5, the rest of this guide is not for you yet. Fix the nos.

This week: fill out the scorecard, and start the AI extraction. Post inside your own audience first. Turn on Fathom or Otter on every meeting starting Monday. If you're at 8 or above on the readiness audit, and you've written the scorecard, there's no reason to wait another week. The best operators are looking right now, this month, this quarter. Not next year.

By Friday: post the role. Inside your own list first. Then outside if you need to. Use the scorecard as the post. Watch who replies.

Want help getting this hire right?

This whole guide is a preview of the work we do inside The Online Business Accelerator. Every week, my team and I help founders build the scorecard, run the search, do the interviews, and make the hire that changes everything. If you want to build the right team the right way, this is where we do it.

See what OBA looks like →

If you're earlier in the journey and want the full picture of what changes on the other side of the bottleneck, grab a copy of Read This If You're Scaling.

Get the book →

Either way, do the audit today.

Your business does not need more of you. It needs someone who can turn your ideas into reality while you go build the next one.

Go find them.

– Scott :)

Frequently Asked Questions

What is an integrator?

An integrator is the operational right-hand to a founder or visionary. In the online business world, this person owns outcomes end-to-end. Product and project delivery, team and ops, hiring and firing, customer experience and financial ops. The term comes from EOS (Traction), where it names the counterpart to the "visionary." Whether you call them an integrator, a chief of staff, or an entrepreneurial operator, the job is the same: they take your ideas and turn them into shipped reality.

What's the difference between an integrator and a chief of staff?

A chief of staff is generally a strategic thought-partner who runs the founder's calendar, priorities, and cross-functional projects on their behalf. Higher status, sometimes lower direct ownership. An integrator owns actual outcomes in the business, not just the founder's schedule. In a small online business, the role you probably want is closer to an integrator than a chief of staff. In a larger company, chief of staff makes more sense.

When should I hire my first integrator?

The readiness audit in Chapter 8 answers this better than any revenue threshold. Most founders in the $500K to $3M range are ready if they can score 8 or higher on the ten questions. Revenue alone is not the signal. The signal is: do you have the money set aside, the scorecard written, the willingness to let go, and three or more zones that need an owner who isn't you.

How much should I pay an integrator?

Compensation depends on your business, your market, and the candidate. Structure matters more than the specific number. Use base plus bonus (bonus tied to scorecard outcomes, not raw revenue). Consider profit share instead of equity, since most online businesses don't have an exit event. Pay to the top of what you can afford, and reset the deal at day 180 if they're crushing it.

Can AI replace an integrator?

Not yet. AI can replace many of the tasks an integrator used to do (writing, project planning, reporting, drafting comms), but it can't own outcomes, use judgment across ambiguous situations, or manage humans. What has changed is that one integrator with AI can now cover the ground four hires used to cover. The role is more valuable now, not less.

Where do I find integrators to hire?

Inside your own audience first. Customers, community members, past clients, and mailing list subscribers who have been around a while are the strongest candidates because they already know your voice, offer, and values. Outside your audience: LinkedIn (search adjacent industries and pivots), Chief of Staff Network, EOS communities, and referrals from other founders. Job boards are the weakest source.

What should I look for in an integrator interview?

Four questions reveal the most. What's the last thing they shipped that nobody asked them to ship (ownership). A time they were wrong about something important (learning speed). How they'd use AI to do a task in the role, live on the call (AI nativity). What they'd fire themselves for in year one (self-awareness). If a candidate can't answer these four with clarity, they're not the hire.

How long should the integrator onboarding process be?

Ninety days to real ownership. Two weeks of shadowing, two weeks of drafting with your approval, four weeks of shipping with weekly review, four weeks of owning with monthly review. Day 90 is the scorecard review. If AI has been used to extract your playbook before they start, this timeline holds. Without that, add 60 days.

What if my first integrator hire doesn't work out?

The best founders I know have cut at least one integrator. The signals are in Chapter 11. If three or more of the "not working" signs are true at day 90, have the conversation. If they're still true at day 120, cut. Two-week transition, clear severance, genuine warmth. It teaches you what you actually need in the seat. The next hire is always better.

Written by Scott Oldford. If this guide helped you, share it with a founder who needs to hire their right-hand.