You have a platform, a thesis, and a mandate to grow through add-ons. What you probably lack is a consistent filter. Most operating partners I work with inherit a pipeline of 40 to 60 “potential targets” from bankers, brokers, and board members. Half are strategic noise. A quarter have integration costs that would consume the first two years of EBITDA. And the rest sit in limbo because nobody has a shared scoring language to say “yes,” “no,” or “park it.”
This is the live problem: add-on acquisition strategy without a disciplined screen burns diligence dollars, exhausts management bandwidth, and creates a pattern of near-misses that erode board confidence. According to Bain’s 2023 M&A report, acquirers who use systematic screening criteria close deals 30% faster and report higher satisfaction with post-close performance. The screen is the strategy.
Below is the framework I use with portfolio companies running buy-and-build programs. It is not a sourcing playbook or a valuation model. It is a qualification gate that sits between “interesting name” and “spend money on diligence.” By the end, you will have a working scorecard you can apply to your next pipeline review.
Why most add-on pipelines fail before diligence even starts
The failure mode is not finding targets. The failure mode is filtering them. Deal teams often operate with implicit criteria: “we want something in the Midwest,” “it should be $3M to $8M EBITDA,” “ideally a competitor.” These are preferences, not a screen.
A screen requires explicit dimensions, weighted importance, and a decision rule. Without it, you get three problems:
- Inconsistent pipeline reviews. Different partners evaluate targets against different mental models. A target rejected last quarter gets reintroduced because someone new saw it.
- Sunk-cost bias. Once you spend $50K on a QofE, you are emotionally invested. The screen must kill deals before that spend.
- Management distraction. Platform CEOs get pulled into early conversations on targets that never had strategic merit. That time does not come back.
The goal of a disciplined add-on acquisition strategy is to compress the “maybe” pile into a short list of “proceed to diligence” and a longer list of “declined with documented rationale.” If you want to understand how this connects to the broader operating model, review the buy-and-build integration and operating model framework.
Strategic fit to the platform thesis
Strategic fit is the first gate, and it is binary. A target either advances your thesis or it does not. This is not about revenue or margin. It is about whether the acquisition makes the platform more valuable to your eventual buyer.
Questions That Define Strategic Fit
- Does the target serve the same end customer segment, or an adjacent segment you have explicitly decided to enter?
- Does it add a capability (product, geography, channel) that your thesis calls for?
- Would combining the two businesses create a story a strategic buyer or larger PE firm would pay a premium for?
If the answer to all three is “no,” stop. It does not matter how cheap the target is or how eager the seller is. A platform add-on must fit the thesis, or it dilutes the narrative you are building toward exit.
Common Traps
Beware “strategic fit by adjacency.” A target in a related industry is not automatically strategic. I have seen platforms acquire businesses that share a customer type but operate in fundamentally different buying cycles. The cross-sell thesis collapses on contact with reality. Be precise about what “fit” means for your thesis, and write it down.
Commercial fit: overlap, cross-sell, concentration
Once strategic fit clears, commercial fit determines whether the deal creates value or just adds complexity. This is where most add-on acquisition screens fall apart because teams conflate “revenue” with “value.”
Customer Overlap Analysis
How many of the target’s customers already buy from the platform? Overlap above 30% signals cannibalization risk. Overlap below 5% signals minimal cross-sell opportunity. The sweet spot, typically 10% to 25%, suggests complementary but not redundant customer bases. You want enough overlap to validate market fit, not so much that you are buying revenue you could have won organically.
Cross-Sell and Wallet Share
Can the platform’s sales team sell the target’s product to existing customers? This is a GTM capacity question, not a hope. Ask: does the platform’s sales motion match the target’s? If your platform sells enterprise contracts through a 6-month cycle and the target sells transactional products through inside sales, cross-sell is a fantasy.
Revenue Concentration
McKinsey’s research on deal value drivers consistently shows that customer concentration is one of the top predictors of post-close underperformance. A target with 40% of revenue from one customer is a risk, not an opportunity. Build concentration into your screen as a hard gate: if the top 3 customers exceed 50% of revenue, require explicit risk mitigation before proceeding.
For a deeper dive into commercial diligence dimensions, the commercial due diligence checklist for B2B acquisitions covers the full scope.
Integration cost and system compatibility signals
Integration cost is where add-on deals quietly destroy value. A target with $2M EBITDA looks attractive until you realize the system migration will cost $1.5M and consume 18 months of management attention. The screen must surface these costs before diligence, not after.
System Architecture Signals
At the screening stage, you cannot run a full technical audit. But you can ask directional questions:
- What ERP does the target run? If it is the same as the platform, integration cost drops significantly. If it is a legacy system the vendor no longer supports, budget for a full migration.
- How is customer data stored? Targets with customer data in spreadsheets or fragmented databases will require significant data engineering before you can report a consolidated view.
- What is the tech stack age? BCG’s 2022 research on technology integration found that targets running systems more than 10 years old cost 2x to 3x more to integrate than those on modern architectures.
Operational Dependency Mapping
Beyond systems, look for operational dependencies that create integration drag:
- Does the target rely on the founder for key vendor relationships?
- Are there manual processes that the platform has already automated?
- Is the target’s billing cycle compatible with the platform’s revenue recognition policies?
These are not diligence questions. They are screening signals you can gather from an initial management conversation or CIM review.
Cultural and management continuity signals
Culture is often dismissed as soft. It is not. Cultural misalignment is a leading cause of post-close attrition, and attrition in key roles can collapse the deal thesis. According to Harvard Business Review’s analysis of M&A failures, cultural integration challenges rank among the top three reasons acquisitions underperform expectations.
Management Continuity Assessment
At the screen stage, you need to answer one question: what happens if the founder leaves on Day 91? If the answer is “the business continues with minor disruption,” you have a real asset. If the answer is “key customer relationships and operational knowledge walk out the door,” you have a different deal entirely.
Signals to capture early:
- Is there a defined second-in-command? Can they articulate the business model independently?
- What is the tenure of the top 5 employees? High tenure with shallow depth is a risk. Low tenure with deep bench is a signal of instability.
- Has the founder already begun transitioning out of day-to-day operations?
Cultural Compatibility Indicators
Cultural compatibility is not about whether people will get along. It is about whether operating norms align. Ask:
- How does the target make decisions? Consensus-driven cultures integrate poorly into command-driven platforms, and vice versa.
- What is the communication cadence? A target that runs on weekly all-hands and daily standups will struggle in a platform that communicates quarterly.
- How is performance managed? If the platform uses rigorous KPIs and the target has never tracked metrics, expect friction.
Scoring and stage-gating the pipeline
A screen without a score is just a checklist. To move from “we reviewed it” to “we have a decision,” you need weighted scoring and explicit gates.
The Scoring Framework
I recommend a 5-dimension model, each scored 1 to 5, with weights that reflect your platform’s priorities:
- Strategic Fit (25%): Does the target advance the thesis?
- Commercial Overlap (20%): Is there real cross-sell opportunity without cannibalization?
- Integration Cost (20%): Can we integrate within budget and timeline?
- Management Continuity (20%): Will the business survive the transition?
- Revenue Quality (15%): Is the revenue durable, diversified, and growing?
Weighted scores above 3.5 proceed to diligence. Scores between 2.5 and 3.5 require explicit risk mitigation plans before proceeding. Scores below 2.5 are declined with documented rationale.
Stage-Gate Logic
Not every dimension deserves equal gating power. I recommend hard gates on two dimensions:
- Strategic Fit: If the score is below 3, stop. No amount of commercial attractiveness compensates for thesis dilution.
- Management Continuity: If the score is below 2 and no mitigation plan exists, stop. You are buying a shell, not a business.
All other dimensions are weighted into the composite score. This creates a system where clear failures are rejected quickly, and borderline cases get structured evaluation.
The sourcing screen scorecard
Below is the working scorecard. This is not a conceptual model. It is the tool you can use in your next pipeline review. Score each target, calculate the weighted total, and apply the gate logic.
| Dimension | Weight | Scoring Criteria | Score (1-5) | Weighted Score | Gate Rule |
|---|---|---|---|---|---|
| Strategic Fit | 25% | 5 = Directly advances thesis, adds required capability, creates exit premium 3 = Tangentially related, unclear capability add 1 = No thesis alignment | Hard gate: Must score 3+ to proceed | ||
| Commercial Overlap | 20% | 5 = 10-25% customer overlap, clear cross-sell, no cannibalization 3 = Overlap outside optimal range, cross-sell requires GTM change 1 = High cannibalization or no synergy | Weighted | ||
| Integration Cost | 20% | 5 = Same ERP, clean data, documented processes 3 = Different but modern systems, some manual work 1 = Legacy systems, fragmented data, founder-dependent ops | Weighted | ||
| Management Continuity | 20% | 5 = Strong second-in-command, founder already transitioning 3 = Bench exists but untested, founder still central 1 = No succession depth, key relationships founder-held | Hard gate: Must score 2+ with mitigation plan | ||
| Revenue Quality | 15% | 5 = Growing, diversified, recurring, low concentration 3 = Flat growth, moderate concentration, some recurring 1 = Declining, project-based, top 3 customers >50% | Weighted | ||
| TOTAL WEIGHTED SCORE | Sum of weighted scores | ||||
| Decision Rule: Score ≥3.5 = Proceed to diligence | Score 2.5-3.49 = Proceed with explicit risk mitigation | Score <2.5 = Decline with documented rationale | |||||
Use this scorecard at the first pipeline review after initial target identification. Before you commission a QofE, before you engage outside counsel, before management spends a day on site visits. The screen saves money by killing bad deals early.
Applying the framework to a real pipeline
To illustrate how this works in practice, consider an illustrative scenario. A platform in the B2B services space has three targets in the pipeline:
Target A: Regional competitor with $4M EBITDA, same ERP as platform, founder planning to retire, 15% customer overlap, top customer is 12% of revenue. Scores: Strategic Fit 5, Commercial Overlap 5, Integration Cost 5, Management Continuity 3, Revenue Quality 4. Weighted total: 4.45. Decision: Proceed to diligence.
Target B: Adjacent service provider with $2M EBITDA, different ERP on legacy system, strong founder with no succession plan, 3% customer overlap, top 3 customers are 55% of revenue. Scores: Strategic Fit 3, Commercial Overlap 2, Integration Cost 2, Management Continuity 1, Revenue Quality 2. Weighted total: 2.05. Decision: Decline. Management continuity fails hard gate with no viable mitigation path.
Target C: Smaller competitor with $1.5M EBITDA, modern tech stack different from platform, experienced GM in place, 22% customer overlap, diversified customer base. Scores: Strategic Fit 4, Commercial Overlap 4, Integration Cost 3, Management Continuity 4, Revenue Quality 4. Weighted total: 3.80. Decision: Proceed to diligence.
This is how the scorecard compresses a 90-minute pipeline debate into a 15-minute decision. The framework does not replace judgment. It structures it.
Connecting the screen to post-close execution
A good screen does more than filter deals. It creates the risk register for integration. Every score below 4 is a workstream that needs a plan.
If Integration Cost scored 3, you know Day 1 planning must include system migration scope and budget. If Management Continuity scored 3, you know the first 100 days after an acquisition must include succession development. The screen is not separate from integration planning. It is the first layer of it.
For the full integration framework, review the post-merger integration checklist for revenue, data, and customer systems. For deeper commercial diligence, see the revenue model due diligence guide. On managing acquisition integration cycles, the post-acquisition product roadmap covers the operational handoff.
The screen is the strategy
An add-on acquisition strategy without a disciplined screen is just a wish list. The framework above gives you a shared language for pipeline reviews, explicit gates that kill bad deals early, and a risk register that feeds directly into integration planning.
The scorecard is designed to be used, not admired. Print it. Fill it out for your next three targets. Watch how quickly the “maybe” pile shrinks and the decision velocity increases.
To turn the screen into a repeatable add-on machine with real diligence behind each pass, DevriX can operate it.
