What the role actually is
The integrator is the person who turns a visionary into a company. The term is most associated with EOS — the Entrepreneurial Operating System from Gino Wickman's Traction — where Visionary and Integrator are the core pairing. But the shape predates the label and exists in plenty of businesses that have never read the book. Every founder-led company that made it past the founder had someone playing this part, whatever the title on their email signature said.
The premise is a real observation about founders. The person who starts a company is usually strong at ideas, relationships, direction, and starting things — and structurally bad at the part where twelve ideas have to become three priorities and then get finished by other people. That's not a character flaw; it's the same trait that made the business exist. The integrator is the counterweight: the one who takes the ideas, decides which three survive, gives them owners, and makes the organization actually deliver them.
Day to day, that means owning the profit and loss, running the leadership team, holding the meeting rhythm, resolving the cross-functional arguments that nobody else is positioned to resolve, and removing obstacles so people can execute. They're the filter that stands between the founder's enthusiasm and the team's week — which is, honestly, most of the value. A team that receives every idea the founder has is a team that finishes none of them.
The deliverable is a company that runs. Not a document, not a decision — a functioning organization where the leadership team is aligned, priorities are stable for a quarter at a time, and things that get started get finished by people who aren't you.
What it costs
There isn't a clean market rate, because integrator is a function rather than a standardized title. The comp lands wherever the seniority lands. Hired full-time at genuine COO altitude, you're in executive territory. Hired as a strong operations lead wearing the integrator hat, a full-time US operations manager typically runs somewhere around $70-110k in salary plus benefits, payroll tax, and a real ramp — more in expensive markets and for strong candidates. Fractionally, integrator-shaped engagements often price like a fractional COO, commonly in the $5-15k/mo range. Treat all of that as general market context, not a quote.
The more useful number is the one nobody puts on the offer letter: the ramp. An integrator's value is almost entirely in context — knowing what actually matters, who's reliable, which promise in the sales process is aspirational, where the business really makes money. That context takes months to acquire and it acquires faster or slower depending entirely on whether it's written down anywhere. In a business where it's documented, an integrator is productive in weeks. In a business where it lives exclusively in the founder's head, the first six months are an extraction project, and you're paying full freight for it.
Which means the honest cost of the hire is the salary plus however many months of your own time you'll spend being interviewed by your own employee. That second number varies from near-zero to enormous, and it's determined before you post the job.
When you genuinely need an integrator
You need one when there are actual functions to integrate. If you have a sales motion and a delivery motion and they are distinct things run by distinct people, and the handoff between them is where work goes to die — that's an integration problem, and integration is a person-shaped job. Someone has to stand in the middle, arbitrate, and hold both sides to the seam. Hire them.
You need one when the leadership team exists but doesn't function as one. Three senior people with three different pictures of the quarter is not a systems problem. No dashboard resolves it. People resolve it, in a room, and an integrator's whole job is being the person in that room who makes it conclude.
You need one when your ideas are outrunning your organization. This is the classic case and it's real. If you generate more direction in a month than the company can absorb in a year, and the team has quietly learned to wait out your enthusiasm because half of it evaporates — you need a filter with authority. Not a system. A person who can tell you no and make it stick.
You need one when you have grown past the point where you can personally hold the whole thing in your head, and you know it, and the evidence is that things you care about are now failing without you noticing until later. That's a capacity ceiling on a human, and there is no elegant answer to it other than another human at sufficient altitude.
And you need one when you genuinely don't want the operator job. Some founders are excellent at it and choose to hand it off. Some are bad at it and shouldn't be doing it at all. Both are legitimate reasons and neither requires justification. If you hate running the company and you'd rather be in the market, hire the integrator and go.
When the hire is a mistake
The mistake is hiring an integrator when there's nothing to integrate. It's the most common failure in this role and it's not obvious from inside, because a founder holding four functions together by hand feels exactly like a founder with four functions that need integrating. The difference is whether the functions have any independent existence.
If they don't — if sales is you, and delivery is you deciding what happens per client, and the handoff is a thing that occurs inside your own head between Tuesday and Wednesday — then the integrator arrives to find that the only interface between the parts of your business is a person. So they can't integrate. They can only replace the interface, which means becoming you: holding four functions together by hand, from memory, with less context than you had. That's not a hire. That's a transplant, and the organ was the problem.
Then one of two things happens. Either they're strong enough to build the architecture themselves — in which case you got lucky, you hired an operations designer at operations-lead rates, and they will leave inside two years for what that skill is actually worth. Or, far more commonly, they become a second single point of failure. The business feels lighter for a quarter and then settles back at a slightly higher cost base, because you didn't remove the dependency. You split it across two people, and two people being the system is just a bigger, more expensive system with the same ceiling.
The specific tell: eight months in, your integrator is excellent, and the honest reason you still can't disappear for two weeks is that half of what they do is also undocumented. You've moved the cage. You haven't opened it.
What has to exist for the integrator to succeed
Three things, and they're the same three the book calls the forces behind enablement. Empowerment: the authority to decide. An integrator without the real power to overrule someone is a very expensive suggestion box, and founders hand out the title far more readily than the authority. Education: the knowledge to act, which in practice means a written record of how the business works that isn't a conversation with you. Environment: the system that supports action — tools that connect, numbers that compute themselves, ownership that's defined.
That third one is where most integrator hires quietly fail, because it's the one nobody checks for before the hire. Enablement isn't about trusting people first; it's about trusting your systems enough that people can succeed inside them. An integrator dropped into a business with no environment doesn't get to integrate. They get to be the environment, personally, forever.
The test, and it takes ten minutes. List your functions. For each seam between them, ask whether anything crosses it today without you carrying it. If most seams have a shape — a defined handoff, a place the work lives, a way to tell whether it went well — hire the integrator now. You have a company and you need someone to run it, and you'll be glad you did it a year ago. If almost no seam has a shape, the hire is premature. Not wrong. Premature.
That's where Ops+AI sits, and we're not an integrator — we're an operations studio that builds the machinery and doesn't take a seat on your org chart. The sequencing that works: build the seams, then hire the person to run them. Done in that order, the integrator you hire is cheaper to find, faster to onboard, and dramatically more likely to stay, because they're stepping into a system rather than into a fog. The OPERATE Report ($1,997) maps which of your seams exist before you commit to a salary. The business stops depending on your instructions and starts depending on your infrastructure — and only then can somebody else run it.
An integrator turns a visionary's ideas into a company that delivers them — and they can only integrate things that independently exist. If your functions have real seams that just need running, hire now and stop deliberating. If every seam is you, personally, between Tuesday and Wednesday, the first hire into that job doesn't integrate the business. They inherit you.