Strategy vs. Corporate Development vs. BizOps: Who Owns What

Three hands up

Picture a board meeting at a growth-stage software company. A director asks who owns the company's move into payments. The head of strategy raises a hand: she wrote the market analysis. The head of corporate development raises a hand: he has two acquisition targets in diligence. The head of BizOps raises a hand: her team built the launch plan and tracks the pilot. All three are right. None of them can say whether the company should build, buy or partner, because each owns a different piece of a question nobody owns whole.

Corporate strategy, corporate development and BizOps are three staff functions that often sit near each other and hire similar people. Corporate strategy helps the executive team decide where the company competes and how it allocates capital. Corporate development finds, values, negotiates and closes acquisitions, divestitures and partnerships. BizOps (business operations) runs the operating rhythm, measures performance against plan and fixes cross-functional problems.

They are easy to confuse because they share skills: models, analysis, executive access. They are easy to tell apart once you ask what each one owns. Strategy owns which bets to make. Corporate development owns the deals. BizOps owns whether the operating plan is on track. The thesis of this page is that most friction between them comes not from overlap but from the handoffs, the moments when one team's output becomes another team's input.

Three teams, three clocks: the year, the deal, the week.

The three, side by side

None of these functions has a standard definition, and titles vary widely. The comparison below is practitioner judgment about the common pattern, not an industry standard.

For the full picture of what a corporate strategy team does, see what a corporate strategy team actually does. The rest of this page concentrates on the other two functions and on the seams between all three.

Corporate development: a repeatable machine, or a series of events

Corporate development is the company's dealmaking function. In a company that does one deal a decade, it may be a single executive and a banker's phone number. In a serial acquirer it is a pipeline: a list of targets kept warm for years, a valuation method, a diligence playbook, and a handoff to integration.

The case for treating it as a capability rather than an event comes from Bain's research on acquirers. In a 2022 study of 2,897 public companies, the 16% that did no deals reported a 10-year annual total shareholder return of 5.4%, while frequent acquirers doing serial bolt-on deals averaged 10.1%, and frequent acquirers who also built the capability to do larger deals led at 11.0% ¹. Bain notes it does not take many deals to count as frequent, about one per year ¹. The authors' advice is to develop a repeatable model ¹. These are associations across a large sample, not proof that deals cause returns; companies with good prospects may simply have more to buy with.

What it should not be is a function that needs deals to justify itself. Deal teams face a pressure the other two functions do not: their work is visible only when something closes. Deepak Malhotra, Gillian Ku and Keith Murnighan describe how, in the heat of competition, executives can become obsessed with beating rivals, an emotional state they call competitive arousal, which often leads to costly mistakes ³. A contested auction is that state's natural habitat.

For the concepts behind deals, see M&A strategy in the Lexicon; for pricing a run of acquisitions, serial acquisition strategy.

BizOps: the function without a definition

BizOps is the youngest and least defined of the three. The title is most common in technology companies, and what it means changes with the company. In a startup it can mean a small team of generalists who take whatever problem the CEO hands them. In a larger company it usually settles into three jobs: running the operating rhythm (the weekly and monthly business reviews, the quarterly plan), owning performance measurement, and fixing problems that cross functions and belong to none of them.

That operating rhythm is the reason BizOps exists. Robert Kaplan and David Norton describe what happens in its absence: senior executives meet at least monthly to review progress against the budget, and those discussions “invariably focus on short-term operations, fire-fighting, and tactics” ⁴. Their remedy was to shape the management meeting's agenda so that it focuses on strategy review and learning rather than just short-term financial performance and firefighting ⁴. BizOps, in most companies that have it, owns the short-term operating review, and the better it runs that review, the more room the strategy conversation has.

Its natural overlaps are with finance and with the chief of staff. FP&A owns the numbers in the plan; BizOps often owns the process and the follow-up. A chief of staff manages the CEO's time; BizOps manages the company's operating calendar. Where those lines sit matters less than writing them down. For the tools BizOps uses most, see the KPI dashboard template and the quarterly strategy review.

The three handoffs where it breaks

Overlap is visible and gets argued about. Handoffs are invisible and get dropped. Three of them matter most.

The first handoff is the one most companies already know about. The corporate strategy team page makes the point directly: if the strategic case for a deal is written after the price is agreed, nobody is testing it. The third is the most neglected. Operating data is where a wrong strategy shows up first, and BizOps is usually the first to see it. If its only channel is a red cell on a dashboard, the evidence is read as an execution problem, and the strategy is never asked.

Overlap gets argued about. Handoffs get dropped.

A worked example: one question, three teams

Nothing in the example required new people. It required a thesis that corporate development could test deals against, and a channel for BizOps to send evidence back to strategy instead of into a dashboard.

Which teams do you need?

Not every company needs all three as separate teams. The answer depends mostly on two things: how often you do deals and how complex the portfolio is. Menz and Scheef's study of S&P 500 firms found that diversification and acquisition activity were both associated with having a chief strategy officer in the top team ⁵, which fits the intuition that dedicated strategy roles appear as the portfolio and the deal flow grow.

The strongest objection is that the split itself is the problem. Three teams mean three agendas, three sets of executives to brief and handoffs that would not exist in a single “strategy and operations” group. Many companies merge them for exactly this reason, and some do it well.

The merger works when the team is small and its leader has the authority to hold all three clocks. It tends to fail as the company grows, for a predictable reason: the week always beats the year. A combined team that runs the monthly business review will spend its best people on the monthly business review, because the deadline is real and the executives are watching. The portfolio question gets the leftover time, and deal theses get written by whoever is free. Splitting the teams is a way of protecting the slow clock from the fast one. If you merge them, protect it some other way: named people whose only job is the year.

Moving between them

Because the three functions share skills, people move between them, and each move teaches something the others do not. Strategy people who spend time in corporate development learn what a thesis costs when someone must put a price on it. Corporate development people who move to strategy learn that most of the important decisions are not deals. BizOps people who move to strategy bring the most underrated skill of all: knowing how the company actually runs, which is where most strategies fail.

If you lead one of the three teams, the most useful thing you can do this quarter is write down the three handoffs for your company: what passes, who sends it, who receives it, and what happens if it does not arrive. The chief strategy officer page covers how the senior strategy role defines its own boundaries with the CFO and corporate development.

Draw the seams

Monday morning: take one live strategic question at your company, the kind that crosses all three teams. Write down who owns the bet, who owns the deal and who owns the operating evidence. Then write down the two moments when one hands to another. If any of the five blanks is empty, that is where the question will stall.

Org charts draw boxes. The work happens on the lines between them. Strategy, corporate development and BizOps each do their own job well enough in most companies. What decides whether the company gets the payments move right is whether the thesis reaches the deal team and the evidence reaches the strategy team. Draw the seams, and give each one an owner.

Questions

What is the difference between corporate strategy and corporate development?

Corporate strategy helps the executive team decide where the company competes and how capital is allocated, including where to grow through acquisitions and why. Corporate development finds, values, negotiates and closes the deals that serve that direction. The key handoff is the investment thesis: strategy should define what the company wants to own before corporate development negotiates a price.

What does a BizOps team do?

BizOps (business operations) usually runs the company's operating rhythm, such as weekly and monthly business reviews and quarterly planning, owns performance measurement against plan, and fixes problems that cross functions. The role has no standard definition and varies by company size: in startups it is often a team of generalists, while larger companies tend to formalize it around the operating cadence.

Is corporate development the same as M&A?

Mostly, but not entirely. Corporate development's core work is acquisitions and divestitures, and often partnerships, joint ventures and minority investments too. In some companies it also owns post-deal integration or reviews. What it should not own alone is the strategic reason for a deal; that belongs with strategy and the executive team.

Does a company need separate strategy, corporate development and BizOps teams?

Not always. Early-stage companies often have one combined team. Separate teams become more useful as the portfolio grows more complex and deals become frequent. If the functions are combined, protect time for long-horizon questions, because the operating rhythm's deadlines tend to crowd out portfolio and strategy work.

Where to go next

• What a Corporate Strategy Team Actually Does
• The Chief Strategy Officer Role
• Build, Buy or Partner