A stronger add-on acquisition strategy starts with the portfolio company’s actual operating constraint. The target list is an output. The investment case begins with the capability, market, or capacity gap the acquisition is meant to address.
That distinction changes how a buyer defines fit. A company can match the sector, size, and geography on paper while doing little to advance the platform’s plan. A useful add-on thesis explains what the combined business is expected to do better, what evidence supports that view, and who will own the work after close.
Start with the platform’s next constraint
Begin with the portfolio company as it operates today. Where does demand exceed capacity? Which customers or geographies are difficult to serve? What capability would allow the company to win or retain work it can serve profitably? Which operating process limits the team’s ability to grow?
These questions make the acquisition purpose concrete. The answer might point to added production capacity, a service line the platform cannot currently deliver, broader access to a defined customer group, or stronger coverage in a nearby market. Each possibility creates a different target profile and a different diligence path.
Use evidence from the platform to establish the constraint. Review customer demand, backlog, service mix, capacity, margins, customer retention, delivery times, and management bandwidth where those records exist. If the evidence is thin, the gap itself becomes a diligence question. It does not become a fact through repetition.
The point is to define the problem before a sourcing list starts to shape the answer. A target that looks attractive can pull the team toward a new rationale. A clear operating constraint gives the team a stable reason to advance, request more information, or pass.
Give the acquisition one primary job
An add-on can have several attractive features. It may bring new customers, a broader service range, a second location, experienced employees, or a stronger supplier position. The thesis still needs one primary job.
Name the job in language the platform’s leadership team can test. For example, the acquisition may add a service capability that current customers already request. It may extend a route into a market where the platform has demand but limited coverage. It may add trained capacity that can absorb work the company currently turns away.
A precise job makes the target screen more useful. The buyer can distinguish a company that solves the stated constraint from one that simply shares the same industry label. It also helps the team describe why an opportunity fits without stretching the rationale to cover every positive attribute.
Secondary benefits can remain in the analysis. Keep them separate from the central thesis until the evidence shows how they contribute. This keeps the first decision legible and gives diligence a clear question to answer.
Translate the job into testable criteria
The target criteria should follow from the acquisition’s purpose. If the job is to expand a service capability, identify the licenses, equipment, talent, customer relationships, or delivery process the capability requires. If the job is geographic coverage, define the territory, travel pattern, customer density, and service model that make the expansion workable.
The same logic applies to platform and add-on financial criteria. A platform search and an add-on search can use different thresholds because each has a different role in the acquisition plan. Keep gross revenue, annual EBITDA, SDE, cash flow, and asking price as separate measures. Use source-stated financial information and label what has not been verified.
A useful criteria sheet answers four questions. What must be true for the target to perform its stand-alone role? What must be true for the combined company to realize the strategic case? Which facts can be confirmed before a first call? Which unknowns require owner conversation or diligence?
Those answers help the sourcing team prioritize the next step. A target can fit the sector and size range while leaving a critical integration question open. Showing that gap gives the deal team a decision to make instead of a vague sense of fit.
Keep stand-alone economics separate from the combination case
The target’s stand-alone performance and the expected benefit of combining it with the platform are different parts of the investment case. Keep them visible as separate lines of reasoning.
The stand-alone view uses the target’s own revenue, annual EBITDA, cash flow, customer profile, operating needs, and capital requirements. Each measure keeps its source and period. If a number is disclosed in a listing or seller material, label it as source-stated until it has been verified through the appropriate review.
The combination case describes what may change after the transaction. It could include access to additional customers, use of existing capacity, broader geographic coverage, a new service offering, or changes to shared systems. For every expected benefit, state the mechanism. Identify the owner who can execute it, the resources it requires, and the evidence that would confirm progress.
This separation matters when the combined case carries much of the expected value. A promising rationale deserves disciplined testing. The buyer can then see whether the acquisition works on its own, depends on the platform’s capabilities, or needs a specific operating change to meet the investment thesis.
Name the integration owner before the LOI
A target can fit the acquisition criteria and still create work the platform is not prepared to absorb. Integration affects leadership time, customer communication, employee decisions, reporting, systems, and day-to-day operations. The buyer does not need a finished integration plan before an LOI. The team does need an early view of the decisions and dependencies that could change its interest in the deal.
Name the person who would own the first phase after close. Then identify the work that person would need to coordinate. Which customers need continuity? Which operating practices should remain local? What information must move between the companies? Where would duplicate work appear? What has to be ready on Day 1, and what can wait?
The integration owner helps the deal team test capacity as well as intent. If a key executive already carries a full operating agenda, the integration plan needs to reflect that. If the expected benefit relies on a system change, diligence can establish what the change would involve and who can lead it.
This is where an add-on thesis connects acquisition work to portfolio operations. The target profile describes what to buy. The integration view describes how the platform can make the acquisition useful.
Build a screen the team can use
Before outreach or broker review, put the thesis into a short scorecard. Each item should help the team decide what to advance and what to learn next.
- State the single operating constraint or growth opportunity the acquisition is meant to address.
- List the source information that shows the target can perform that job, along with any important gaps.
- Record the target’s disclosed financial profile and the questions needed to verify it.
- Describe the expected change after close, the mechanism behind it, and what could prevent it.
- Name the likely integration owner and the management, systems, or capital requirements that need review.
- Specify the missing fact that would move the opportunity forward, keep it on hold, or end review.
The scorecard should fit the decision stage. An early screen can use public information and direct questions. A deeper diligence pass can test customer overlap, retention, employee needs, operating performance, technology, and capital requirements. The team should know which questions belong to the current decision and which belong to a later stage.
This creates a cleaner handoff from market mapping to first review. The sourcing team knows what a qualified target looks like. The investment team can see why it may fit. The operating team can identify the commitments that need further work.
An illustrative example
Consider a regional field-services platform with customer demand in an adjacent territory. A broad search for service companies in that region may return many plausible names. An add-on thesis gives the screen more direction.
The buyer can first ask whether the platform has enough demand to support the expansion. The team can then define the service radius, staffing needs, customer profile, and response-time expectations a target would need to meet. The stand-alone review can assess the target’s financial performance, customer concentration, workforce, and equipment requirements. The combination case can test whether the platform’s dispatch, sales, or management capacity can support the expanded territory.
That example does not establish that buying is the right answer. It shows how the operating question produces a better first screen and clearer diligence questions. If the buyer cannot support the demand case or name a responsible operating owner, the team has a specific reason to pause before investing more time.
Make the target list earn its place
An add-on acquisition strategy becomes actionable when the platform’s operating need, target criteria, evidence standard, and integration owner point in the same direction. The target list then helps the team investigate a defined thesis instead of generating one after an opportunity appears.
Before the next target review, record what the acquisition should let the platform do and how it will do it. Then name the evidence needed to support the thesis, the facts that remain open, and the person who will own the first operating decisions after close.
For private equity teams building an add-on lane, SilverShore’s investor services start with the mandate and organize thesis-aligned market coverage, opportunity fit, and source context for the next decision. Explore SilverShore’s investor services.