By Joash Boyton, founder, owner and CEO of Acquiry
Sponsored educational article by Acquiry.
A private equity team should select an add-on origination partner against the needs of a specific portfolio company, not against a generic promise of more deal flow. The partner should understand the platform's strategic objective, distinguish relevant companies within the sector, coordinate owner contact and return qualified conversations with evidence the sponsor and operating team can use. General industry knowledge is useful, but it does not establish understanding of this platform's integration limits.
Start by agreeing what the sponsor and portfolio leadership need the partner to do. Research coverage, owner dialogue and initial qualification are different workstreams. A provider may be strong in one and need a different scope or additional support for another. The buyer should compare the actual proposed work, the evidence behind it and the demands it places on the platform.
This guide is about provider selection for an add-on programme. It is not a target-search execution manual or a prediction of acquisition outcomes. The central tool is a partner scorecard tied to platform-specific fit, with interview questions, a hypothetical comparison and a commissioning worksheet that separates sponsor decisions, platform input and provider responsibilities.
Before meeting providers, state what the portfolio company is trying to add. The objective may concern a product capability, a customer segment, a service line or another commercial requirement. Describe the operating outcome rather than relying on a broad sector label. A provider should be able to explain why a target would matter to the platform beyond belonging to the same industry.
Separate the platform's immediate requirement from possible future opportunities. An add-on programme can become unfocused if every adjacent company is treated as equally relevant. Explain which objective takes priority and which alternatives are outside the current search. If several theses remain open, identify them separately so the provider does not blend their criteria into an unworkable brief.
Ask what the platform can absorb. Which capabilities are available to support a new business, and which are constrained? A provider does not need to conduct the full integration assessment during selection, but it should recognise the constraints that determine whether a conversation is worth starting.
Also state what support the internal team lacks. The sponsor may know the sector but need more detailed mapping. The platform may know relevant owners but need help maintaining discussions. The combined team may receive introductions but lack consistent early qualification. The proposed provider should address that specific gap.
A clear requirement lets the buyer reject a service that is impressive in general but poorly matched to the programme. It also helps a provider propose a bounded role rather than assuming responsibility for everything between research and integration.
Identify who owns the search objective, who approves the target brief and who may authorise owner contact. The sponsor and platform can contribute different perspectives, but the provider needs one current set of instructions. It should not have to infer the agreed position from separate conversations.
Clarify the platform leadership team's role in evaluating fit. If a target would depend on the platform's sales, technology, customer support or management resources, the relevant leaders should assess those assumptions. A sponsor's strategic interest does not by itself establish operational capacity.
Define the sponsor's decisions separately. These may include prioritisation, investment review or other approvals according to the actual arrangement. Do not assume the same decision rights apply to every programme. The point is to create a working map for this buyer, with appropriate specialist advice where formal arrangements require it.
Set a route for disagreement. A sponsor may view a company as strategically attractive while the platform considers the integration burden unacceptable. The provider should preserve both positions and request a decision from the agreed owner. It should not resolve the conflict by presenting a more optimistic version to the seller.
Before appointment, ask the provider how it would operate when instructions conflict. A credible answer should involve clarification and documented approval, not an attempt to satisfy each participant through different external messages.
An add-on search begins with a proposed relationship between the target and an existing business. That relationship creates requirements that a generic sector list may not capture. The same company could fit one platform and fail another because of product overlap, customer needs, operating systems or management dependence.
Ask providers how they would learn the platform's commercial language. They should be able to distinguish adjacent capabilities from superficial similarity. For example, two companies may describe themselves using the same industry category while serving different users or requiring incompatible delivery models. A useful research approach should identify those differences.
The provider should also understand what the platform is not trying to acquire. A target may be too dependent on a capability the platform lacks, or it may require a degree of standalone leadership that the programme is not prepared to support. These exclusions should be linked to the intended operating relationship rather than to generic judgements about company quality.
A recurring programme needs a way to carry learning from one reviewed target to the next. Ask how the provider updates research instructions after platform feedback and how it prevents the same misunderstanding from recurring. This is different from merely adding more names to a database.
The selection test is whether the provider can connect the target universe to a specific platform thesis while keeping unresolved operating questions visible.
Ask a provider to describe the segments it would distinguish within the relevant market. The answer should reflect the platform's objective. Product function, customer type, delivery model or position in a workflow may matter more than a broad industry code.
Use a hypothetical mapping exercise during selection. Provide an anonymous description of the platform's need and ask the provider to explain which company characteristics would indicate relevance. Then ask what characteristics would create a false positive. This tests reasoning without requesting another client's confidential target list.
Examine the proposed evidence sources. The provider should be able to explain how it would use company materials, public announcements and other appropriate sources, and how it would handle information that is incomplete or outdated. A polished map without source discipline may be difficult for the platform to rely on.
Ask how exclusions are recorded. If a company is rejected because it serves the wrong buyer group or depends on an incompatible operating model, that reasoning should be preserved. Otherwise the same business may reappear in a later batch under a different description.
A generic database can support discovery, but its existence is not proof of fit. The useful output is the provider's supported explanation of why a company deserves attention under this programme, including the questions that remain before any owner approach.
The provider should understand the constraints that matter at the search stage. It does not need to claim that it can complete the platform's technical, operational or organisational assessment. The buyer should distinguish early screening questions from later specialist conclusions.
Examples of search-stage constraints include dependence on a founder for daily delivery, a product requiring a capability the platform cannot support or a customer model outside the platform's intended scope. These should be expressed as questions with evidence requirements, not assumed facts about every business in a segment.
Ask the provider how it would identify a dependency that is not visible publicly. It may be able to flag a question for initial owner dialogue. It should not simply mark the criterion as passed because no public information indicates a problem. Absence of evidence is not a completed operating assessment.
Also test whether the provider understands the platform's available resources. If the search rationale assumes access to a central function, that function's leader should confirm the assumption. The provider should know which dependencies are supported, conditional or unresolved.
The best selection evidence is a realistic discussion of boundaries: what can be screened, what can be explored with an owner and what needs the platform or a specialist. Confidence should come from that clarity, not from broad claims that integration will be straightforward.
An owner approach should connect the buyer's interest to a specific strategic rationale. It should not rely only on the sponsor's name or the promise of joining a larger group. The provider needs enough understanding of the platform to explain why a discussion might be relevant, within the disclosure permissions agreed.
Ask who would be represented in the initial conversation: the sponsor, the platform, an adviser acting for the buyer or another authorised party. The answer should be accurate and consistent. A provider should not imply that it is the principal acquirer if it is acting as an adviser.
Review how the provider would learn owner priorities. The owner may care about continuing involvement, employees, customer continuity, growth or timing. The provider should ask rather than infer. It should also distinguish an owner willing to learn about the platform from an owner willing to explore an ownership change.
Avoid promises that the platform has not approved. The proposed approach should not guarantee employment arrangements, operating independence, a transaction timetable or a future role merely to secure a meeting. If an owner asks for such a commitment, the provider should escalate the request.
During selection, ask the provider to explain how it would handle a clear decline. Respecting the owner's answer and preserving the contact record are part of a credible approach, even when the response does not advance the programme.
A programme may involve several people who know the same market. Before a new approach, the provider should check existing relationships and contact history through an agreed process. The aim is to avoid repeated requests, contradictory messages or accidental disclosure of a search.
Appoint a coordination owner who can resolve uncertainty about who should speak. This person does not need to conduct every conversation. They do need a reliable view of active discussions, restrictions and the approved buyer message. A relationship held by the platform should not be bypassed simply because an external provider found another route.
Ask how the provider will record source channel, contact status, authorised recipient and the next agreed action. Where another adviser is involved, clarify the responsibilities and have the relevant parties address contractual or representation questions. Do not ask the provider to improvise conclusions about competing claims to an introduction.
Set a rule for approaches involving companies already known to the sponsor. Known can mean researched, previously contacted, actively engaged or declined. Those are different situations. The record should show which applies and what can happen next.
Contact coordination is a practical selection criterion. A provider that promises high activity but cannot explain how it avoids conflicting outreach may create work and relationship risk for the platform rather than useful capacity.
Agree what the sponsor and platform should receive before a target is presented for substantive discussion. The record should explain the strategic connection, the evidence supporting initial fit, the owner's actual response and the questions that require internal assessment.
Keep information status clear. A statement may be observed publicly, reported by the owner or still unverified. Those distinctions should survive the handover. A preliminary claim should not become a settled fact merely because it appears in a presentation to senior leadership.
Qualification should include the proposed next step. Has the owner agreed to a general introduction, a discussion of strategic fit or a more specific ownership conversation? The receiving team should know what the owner expects. That avoids starting a meeting with an assumption the owner has not accepted.
The handover should also identify integration questions early enough for the right person to attend. If the key uncertainty concerns product compatibility, the platform may need a product leader rather than a broad executive group. If it concerns management transition, the operating discussion may need a different participant.
Ask prospective providers to demonstrate this record using a hypothetical example. A contact name and an enthusiastic paragraph are not the same as a decision-ready introduction.
The scorecard should compare evidence of capability, not promised deal volume. Use it after providers have reviewed the same approved brief. Mark each dimension as supported, partly supported or unresolved, and write the reason. Do not assign a precise score to information that has not been demonstrated.
| Selection dimension | Evidence to request | Unresolved question to record |
|---|---|---|
| Platform understanding | Explanation of the capability gap and operating limits | Which assumptions require platform confirmation? |
| Sector mapping | Hypothetical segment map and false-positive examples | Can the provider distinguish relevant adjacent models? |
| Research discipline | Source-backed target record with exclusion reasoning | Which facts would need reconfirmation before contact? |
| Owner approach | Approved-message process and discussion agenda | How are owner priorities learned rather than assumed? |
| Contact coordination | Existing-relationship check and escalation route | Who resolves overlapping approaches? |
| Qualification | Definition and hypothetical introduction record | What remains for sponsor, platform or specialist review? |
| Learning and feedback | Method for updating instructions after target reviews | How will recurring misunderstandings be prevented? |
| Scope and continuity | Named responsibilities and handover arrangements | What happens when the programme pauses or changes? |
The sponsor and platform may initially judge a dimension differently. Discuss that difference. A sponsor may value broad mapping while the platform prioritises fewer, better-prepared discussions. The scorecard should reveal the underlying requirement, not conceal the disagreement inside an average.
Record the evidence that would resolve each material gap. This turns selection into a practical process: request a relevant sample, clarify a responsibility or revise the brief. If a provider cannot demonstrate a critical capability, the buyer can narrow the proposed role or choose another arrangement.
Before appointment, ask how the provider identifies and manages relevant conflicts. It may work in the same sector for more than one participant or know owners through other relationships. The buyer needs a clear process without demanding confidential information about unrelated clients.
Define what the provider may share about the sponsor, platform and search. Identifying details should not enter an external approach or draft without the approval required for that disclosure. An anonymous overview can explain the strategic purpose while preserving private identities. Avoid unusual combinations of facts that identify a target indirectly.
Clarify whether the provider is expected to support only origination or additional coordination after an introduction. Describe those activities specifically. Legal, financial, technical and other specialist responsibilities should remain assigned to the appropriate people rather than being assumed within a general advisory label.
Agree how changes to the programme are approved. If the platform's operating priorities change, the provider should know which criteria and owner messages must be revised. Existing discussions may require a careful update rather than simply disappearing from the active list.
Finally, address record continuity. The buyer should understand how it will access the agreed working information, permissions and pending actions if the engagement pauses or the assigned personnel change. The programme should not depend on one individual's memory.
Consider a hypothetical sponsor and portfolio company seeking a complementary service capability. The platform can evaluate service delivery but has limited time for market research and owner follow-up. Its essential constraint is that it cannot immediately replace a target's day-to-day leadership. No real provider, client or acquisition opportunity is represented.
Proposal A offers broad sector mapping and a large research output. Proposal B offers a narrower platform-specific map, authorised owner dialogue and a defined qualification record. Proposal C focuses on owner relationships in the sector but provides little detail about research outside those relationships. These are invented service descriptions used to illustrate the selection method.
The sponsor initially prefers A's broad coverage. The platform is concerned that it will receive many companies without enough information about management dependence. Rather than deciding from those impressions, the buying team asks each provider to apply the same hypothetical brief and explain how it would handle the leadership constraint.
Provider A demonstrates strong segmentation but treats management questions as entirely outside its scope. That may still be useful if the buyer assigns the work elsewhere. Provider B explains how it would flag public indicators, ask appropriate initial questions and preserve uncertainty for platform assessment. Provider C can describe a route to selected owners but cannot show that its coverage matches the capability requirement.
The team then tests handover quality. It asks what an introduction would contain and what the owner would have agreed to discuss. A provider that supplies only a relationship description does not meet the buyer's stated need for initial qualification, even if the relationship is genuine.
The resulting decision might favour B, combine A with a separate dialogue resource or narrow C's role to a defined segment. The scorecard does not predetermine the answer. It makes clear which work is covered, which remains with the buyer and where evidence is missing.
The team should not convert the preferred proposal into a prediction of completed add-ons. Selection establishes a suitable support model. Owner willingness, target fit and subsequent transaction decisions remain to be tested.
Continue the hypothetical example. After initial mapping, the platform's operating leader explains that a major internal project will reduce its ability to support new integrations. The strategic objective remains relevant, but the near-term capacity assumption has changed.
Ask prospective providers how they would respond. A useful answer should separate work that can continue from work that should slow or pause. Research may still improve the target map. A conversation already agreed with an owner may need an accurate update. New approaches should not imply a pace of progression the platform cannot support.
The provider should also identify which target criteria are affected. A business requiring substantial immediate support may become unsuitable for the current phase. A business with stronger independent management may remain worth investigating, subject to the buyer's approval. The provider should recommend a revision rather than quietly changing the brief.
The sponsor and platform must decide the revised scope. The provider can organise the implications, but it cannot create operating capacity or promise a different integration model without authorisation. This scenario tests whether the partner can remain useful when the programme's constraints change.
After the decision, update the working record and owner messages. Preserve the reason for the change so a later reviewer does not mistake paused candidates for failed strategic fit. That distinction can matter if the programme resumes under different operating conditions.
Use these questions after sharing the approved brief. Ask for concrete explanations and hypothetical examples. The purpose is to understand how the provider would work, not to request private transaction histories or confidential target identities.
Watch whether the answers remain specific to the platform. General assurances about experience or networks may be relevant background, but they do not resolve the operating questions. A provider should be able to explain what it would do differently because of the actual brief.
Acquiry identifies private equity among its buyer audiences and describes an acquisition process built around agreed target profiles, company research, owner approaches and fit qualification. That scope is relevant when a sponsor and portfolio company need support converting a defined add-on objective into suitable owner conversations.
A commissioning discussion should bring both the strategic rationale and the platform's operating constraints. Ask how the proposed scope would cover mapping, contact coordination and initial qualification, and identify the decisions that remain with the sponsor and platform. The firm's public positioning establishes its offered role; the agreed engagement should define the actual work.
Another arrangement may fit when the platform already has relevant owner dialogue and needs specialist diligence, when a bounded research exercise is sufficient or when integration capacity is the true constraint. Origination support should address a sourcing or qualification gap rather than conceal an unresolved operating problem.
Before work begins, assemble a concise commissioning pack approved by the relevant buyer decision-makers. It should contain the acquisition objective, essential criteria, platform dependencies, existing contacts, disclosure permissions and the required introduction record. Keep the pack current as the programme develops.
Name the sponsor contact, platform contact and coordination owner. Specify which questions each can answer and who resolves disagreement. If the provider receives an instruction that changes the brief, it should be able to confirm that instruction through the agreed route before acting externally.
Include examples of false positives. A short explanation of why an apparently relevant company would fail the platform's requirements can be more useful than another page of positive sector descriptions. It helps the provider apply judgement consistently and reduces repeated review of the same mismatch.
Also state the buyer's own commitments. Who will assess product or service fit? Who will attend an owner conversation? Who will respond when a target needs a decision? The provider's scope should be matched by a realistic internal plan for using its output.
A review should ask whether the partner is improving the platform's access to relevant, well-understood conversations. Consider research quality, exclusion reasoning, owner-response accuracy and the clarity of handovers. Do not rely only on the number of names researched or messages sent.
Separate provider execution from changes in the market or buyer readiness. A well-run search may establish that relevant owners are not currently receptive. A poor handover may waste attention even when an owner is interested. Those situations call for different responses.
When performance is disappointing, identify the evidence of the problem. Are target profiles repeatedly missing the capability requirement? Are owner responses overstated? Are platform questions unanswered? Or is the buyer failing to provide timely decisions? The review should be candid about both sides of the relationship.
Agree whether to continue, refine the scope, change a responsibility or pause. Preserve contact restrictions and pending commitments through any change. A provider relationship should remain accountable when the programme slows as well as when conversations advance.
The decision should follow the actual governance arrangement, with input from those who will use the work. The sponsor may own the appointment decision while the platform assesses operating relevance, or another arrangement may apply. What matters is a shared brief, clear authority and a process for resolving conflicting instructions.
No. Ask how the provider's understanding applies to the specific platform objective, customer model and operating limits. Sector familiarity can support good research, but the buyer should still test segmentation, false-positive reasoning and the proposed qualification record. Broad experience claims do not replace a relevant process demonstration.
It should identify and screen the constraints agreed for the early stage, while flagging what remains unresolved. Full integration judgement belongs with the platform and appropriate specialists. The provider should help the right questions reach the right people, not present preliminary research as completed operational diligence.
Yes, if responsibilities, contact checks and information flows are coordinated. Define which segments or activities each source covers and how overlapping candidates are handled. The buyer should maintain one current brief and avoid exposing owners to inconsistent approaches from different representatives.
Review what the search has established. The criteria may need clarification, the researched universe may be incomplete or owners may not be receptive. Do not redefine a weak candidate as qualified merely to maintain activity. A useful provider should explain the evidence and recommend a proportionate next decision.
A selection exercise should include evidence that weakens an initially attractive target. Otherwise every sample can be designed to end in a positive recommendation. Ask the provider to show how it would document a material uncertainty or contradiction without either hiding it or turning it into an unsupported rejection.
In a further hypothetical extension of the service-capability example, public materials emphasise the founder's leadership. That observation does not establish that the business cannot operate without the founder. The provider should identify management dependence as a question, explain why it matters to the platform and propose the next proportionate verification step.
| Record field | Hypothetical entry |
|---|---|
| Observed information | Public materials describe a prominent founder role |
| Platform relevance | The buyer cannot immediately replace day-to-day leadership |
| Unresolved question | Which responsibilities depend on the founder, and who else performs them? |
| Permitted next action | Raise the question in an authorised initial dialogue if the owner welcomes discussion |
| Decision boundary | Do not represent management independence as verified before evidence exists |
The provider's explanation matters as much as the format. It should distinguish the observation, the inference being considered and the decision that cannot yet be made. A platform reviewer should be able to understand the concern without concluding that the company has already failed the brief.
Now ask what would happen if direct discussion confirmed a dependency the platform cannot support. The record should show the evidence, the buyer's decision and the authorised response to the owner. It should not keep the target labelled attractive merely because substantial research has already been performed. A provider's handling of a well-founded stop decision is useful evidence of whether it will protect the programme's focus.
An effective add-on origination relationship connects the sponsor's objective with the portfolio company's real operating capacity. Choose a provider that can demonstrate platform-specific research, thoughtful owner dialogue, accurate qualification and reliable coordination. Keep investment and operating decisions with their proper owners, and judge the relationship by the usefulness of its evidence rather than unsupported promises of volume.
About the author: Joash Boyton is the founder, owner and CEO of Acquiry, an international M&A advisory firm based in Melbourne with a core focus on buy-side acquisition origination. Public company information is available at acquiry.com.
Acquiry, About Acquiry: Global M&A Advisory Firm. https://www.acquiry.com/about/
Acquiry, Buy-Side M&A Advisory. https://www.acquiry.com/acquisitions/
Acquiry, Official Information About Acquiry: Company Facts. https://www.acquiry.com/ai-instructions/