A two- or three-person corporate development team cannot run a sourcing function on top of its day job, and most of the advice aimed at them assumes otherwise. The constraint is almost never judgment — corp dev leads know their market better than any outside party. It is hours, and specifically the hours that go to work with no deadline attached: researching a sector, building a list, calling forty owners, following up with the one who said "not this year" fourteen months ago.
That work always loses to whatever is urgent. So the operating model has to be built around that fact rather than around a resolution to try harder.
BizNexus covers the strategic question of how corp dev teams source middle market deal flow at best ways to source middle market deal flow in corporate development. This piece is the narrower operational one: how the program runs week to week when nobody is dedicated to it.
Separate the decisions from the volume
Almost every failed add-on program fails here. A small team tries to do both, the volume work expands to fill everything, and the decisions get made in a rush at the end of the quarter.
The split is clean once you look at it:
Decisions — is this target in scope, is this conversation worth a meeting, does this deal go to the business-unit leader, what is our number. These are judgment, they need context only you have, and they take minutes each.
Volume — building and maintaining the universe, enrichment, first approaches, second approaches, chasing an advisor who went quiet, keeping a record of every "not yet" so it can be revisited. These take hours, they are repetitive, and they have no natural deadline.
Keep the first, move the second. Whether "move" means a hire, an outside origination team, or a platform plus capacity is a separate question — but do not attempt both from the same three calendars.
Write the thesis once, and stop moving it
The single biggest cause of a stalled add-on program is a thesis that changes every quarter. Each change resets the universe, invalidates the outreach already sent, and makes you unmemorable to every intermediary you have spoken to.
A usable thesis is specific enough that someone outside your company could act on it: sectors, geography, revenue and EBITDA floors, ownership profile, structure, and the exclusions that keep coming back. Commit to it for at least four quarters. Let real conversations refine it — that is what they are for — but refine is not replace.
This is also the document that makes the rest of the model possible. A short daily review queue only works if the filter upstream of it is right, and the filter is the thesis.
Make the recurring workload a decision, not a project
The target operating state is about ten minutes a day: a short queue of matched companies with the financials in front of you, and one decision per row. In or out. An approval moves a target into outreach; a rejection teaches the filter.
If your recurring sourcing work takes materially longer than that, you are doing research rather than deciding, and the research is exactly the part that should not be on a corp dev lead's desk. The test is simple: at the end of a week, how much of your sourcing time produced a decision, and how much produced a better understanding of companies you were never going to buy?
Use operators as a channel, properly
Business-unit leaders are the most under-used origination channel in corporate development, and the one most often burned by being used badly.
What works: one structured conversation per quarter, same questions every time. Who in your market might sell in the next two years? Who has an owner approaching retirement, a partner dispute, a succession problem? Which competitor keeps coming up in lost deals? Write down the answers, put the names in the pipeline, and work them like any other target.
What burns goodwill: ad-hoc requests to opine on individual targets, meetings about the pipeline, and asking them to make introductions they have not agreed to make. Operators will give you intelligence forever. They will give you homework once.
Give them read access to the pipeline as well. An operator who can see that three targets in their sector are engaged and one is parked under someone else's LOI stops asking for updates, and starts volunteering information — which is the direction you want that relationship running.
Cover the intermediated channel, because that is where the deals are
Corp dev teams running add-on programs skew heavily toward proprietary outreach, partly because it feels more strategic and partly because the alternative feels like waiting for a banker to call.
That leaves the largest channel in the lower middle market uncovered. Most sellers below $10M of EBITDA who run a process use an intermediary, and fewer than 20% of broker-listed deals ever reach the buyers who would actually want them — the problem there is distribution, not discovery. Being on the short list an advisor already holds costs behavior rather than budget: be specific, reply the same day, say no clearly. See how brokers decide which buyers see a deal.
How to frame it to a CFO
Corp dev leads lose this argument more often than they lose the deals, and usually by framing the request as a headcount question when it is a coverage question.
The version that works: name the channel you are not covering, say what it would take to cover it, and price that against the alternative. "We see the deals our bankers send us and nothing else. Covering the intermediated market and running owner outreach across our two priority sectors is roughly a full-time job. Here is what it costs to buy that capacity, here is what it costs to hire it, and here is what a quarter of not having it looks like — which is the quarter we just had."
That framing also survives the follow-up question, which is always some version of "what do we get for it in the first year". The honest answer is conversations, not closings, and saying so up front is what stops the program being killed at month six. A CFO who has been told to expect conversations will accept conversations. One who was promised a deal will not.
Measure conversations, not closings, for the first two quarters
An add-on program measured on deals closed will be declared a failure at month six, every time, because the timeline does not work that way. A target who says "not yet" in March is a deal in the following year, and nothing about that shows up in a quarterly report.
Measure instead: targets reviewed, conversations started, conversations still live, and — the one that matters most — conversations revisited. The last of those is the number that distinguishes a pipeline from a list, and it is the first thing to collapse when nobody owns the follow-up. Most lower middle market deals fail on timing rather than fit, which means the value is almost entirely in the revisiting.
What the assembled model looks like
One documented thesis. A short daily queue that produces decisions. Outreach, follow-up and the advisor chase handled by capacity that is not your three people. Operators consulted quarterly and given read access. Intermediated, pre-market and off-market channels all running against the same thesis, landing in one pipeline rather than three inboxes.
That is what OmniSource is built to be for a team this size — the platform finds and scores, an origination team runs the outreach and the NDA and CIM chase, and the recurring commitment on your side is the review queue. The persona view is at for corporate development.
The short version
You are not short of judgment. You are short of the hours that go to work with no deadline. Build the program around that, and the ten minutes a day you can actually protect become the only part of it you have to do yourself.