Choosing buy side support for a small corporate development team

By Joash Boyton, founder, owner and CEO of Acquiry

Sponsored educational article by Acquiry.

A small corporate development team should choose buy-side support against the work it cannot reliably complete, not against a general desire for more acquisition opportunities. The first distinction is between capacity, specialist skill and decision authority. An external provider can add research or owner-contact capacity. It cannot substitute for the buyer deciding what it wants, who may approve a next step or how an acquired business would be run.

The practical approach is to map the work, identify the bottleneck, compare ways to fill that gap and document what remains inside the company. That produces a more useful engagement than delegating an entire acquisition programme while retaining an undefined expectation of control. It also helps the team avoid the opposite mistake: buying research support when its real problem is that nobody has time to evaluate the research.

This guide is for lean corporate development teams that need a workable division of responsibilities. It covers retained and delegated tasks, owner-contact coordination, decision queues, handovers and provider selection. The central tool is a capacity and responsibility worksheet that can be used before commissioning support and revisited when the search changes.

Diagnose where acquisition work actually stops

Start with the last several pieces of acquisition work the team handled, using only records it is authorised to review. Identify where each item waited and why. Did a target remain unresearched? Did the research sit unread? Was an owner conversation delayed because the business-unit leader was unavailable? Was the team unable to explain the strategic rationale clearly enough to proceed?

These are different constraints. Adding names does not help when the evaluation queue is already stalled. Adding an owner-contact provider does not help when nobody can approve the buyer description. Adding transaction coordination may not help when the company has not decided which capabilities it needs to acquire.

Map the flow from strategy to the next substantive buyer decision. Record the work performed, the person doing it, the recipient and the decision expected. Include the informal activities that consume time: correcting irrelevant research, finding an internal expert, reconstructing contact history and preparing an executive for a meeting. Those activities can reveal missing instructions or weak handovers rather than a simple shortage of people.

Do not diagnose capacity solely from how busy the team feels. A team can be busy because its workload is genuinely too large, because its process creates repeated rework or because decision rights are unclear. The remedy should follow the cause. Otherwise external support may increase the number of items entering the same unresolved queue.

Write the bottleneck as an observable problem. For example, relevant targets wait because product leaders receive incomplete context is more actionable than the acquisition process is slow. It points toward a better intake and handover, not necessarily a larger sourcing operation.

Separate capacity, skill and authority

Capacity concerns the amount of work the team can perform. Skill concerns whether the team can perform the work competently. Authority concerns who can make the relevant decision. The same task can contain all three issues, but they should be examined separately.

Researching a new niche may be a capacity problem if the team knows how to do it but lacks time. It may be a skill problem if the team cannot distinguish the relevant business models. It may become an authority problem if no one can decide which adjacent models are acceptable. Hiring additional researchers would address only the first of those issues unless the role is deliberately designed to cover more.

Use three questions for each workstream: can we do this well, do we have time to do it consistently, and who may decide what happens next? A missing answer should remain visible. Do not convert it into a generic request for end-to-end support and assume a provider will resolve the ambiguity.

Some decisions can be delegated within defined boundaries. An external researcher might exclude businesses that clearly fail an approved geographic criterion. The same researcher should not silently expand the geography because the initial market appears small. The distinction lies in applying an agreed rule versus changing the buyer's strategy.

Keep a named internal owner for decisions that affect the company, even when an adviser prepares the evidence or recommendation. This helps external support function as an extension of the team without creating uncertainty about who speaks for the buyer.

Compare hiring, research assistance and advisory support

Internal hiring may fit a durable, recurring need for capability that the company wants to retain. Before choosing it, define the work the new role would own and the support it would need from operating leaders. A new employee does not automatically gain access to decisions that existing team members cannot obtain.

Research assistance may fit a bounded need to identify companies, organise public information or investigate a defined market segment. Its value depends on a usable brief and an internal recipient who can evaluate the output. If the assignment stops at research, the buyer must still own owner approaches, qualification and follow-up.

Advisory origination support may fit a gap that extends from target definition into owner conversations and fit qualification. The buyer should confirm the actual scope rather than infer it from the word advisory. A proposal can include some of these activities and exclude others.

A combination may be sensible. The internal team can own strategy and operating judgement, a research resource can expand coverage, and an origination adviser can handle specified owner conversations. The combination becomes unhelpful when nobody owns the handovers or multiple parties approach the same people with inconsistent messages.

Compare the routes on the work each would remove from the internal queue, the new management work it would create and the decisions it would still require. A service that appears comprehensive may demand substantial buyer input. A narrow service may be highly effective if it addresses the exact constraint.

Identify the decisions the buyer should retain

The buyer should retain ownership of its acquisition objective and the reasons a target would fit. An adviser can challenge or refine those ideas, but the company must be able to explain them in its own words. If the rationale exists only in the provider's presentation, it may not survive internal review or an owner discussion.

Retain clear responsibility for approving target criteria, material changes to the search, authorised external messages and the decision to commit operating attention. Also identify who owns any decision to stop. Without that responsibility, unsuitable targets can remain active simply because nobody wants to close the record.

Operating leaders should own the assumptions that depend on their teams. If a proposed acquisition requires the product function to absorb a new codebase or customer support to serve another customer group, those leaders need to assess the assumption. Corporate development can coordinate the assessment; it should not silently accept resources on their behalf.

Specialist judgements require the appropriate specialists. A sourcing provider can flag a question about a contract, technology dependency or financial definition. It should not be treated as a substitute for the qualified advisers or internal experts needed to resolve that question. The retained-work map should identify how those people will enter the process.

Retaining a decision does not mean doing every preparatory task. The internal owner can ask an external team to organise evidence and state options. The handover should make the judgement easier while leaving accountability clear.

Define delegated work as outputs with acceptance tests

Delegation works better when the recipient knows what a useful output looks like. Research companies in this sector is incomplete instruction. Identify companies serving a specified workflow, explain the evidence of relevance and flag unanswered criteria is more usable.

For each delegated task, define an output and an acceptance test. A research record might require a source date, a clear fit rationale and a distinction between observed and inferred information. An owner-conversation record might require the owner's actual response, any restrictions on further contact and the next step agreed.

Avoid specifying so much process that the buyer must supervise every action. The objective is to define the decision boundary and quality requirement, while allowing the provider to perform the agreed work. Where the task involves judgement, use examples of acceptable and unacceptable reasoning to establish the standard.

Name the reviewer. A deliverable without a recipient becomes another unattended item. Agree how feedback will be returned and incorporated into future work. If the same correction appears repeatedly, update the instructions rather than treating each occurrence as an isolated error.

Also define what the provider should do when the acceptance test cannot be met. It may need to mark a question unresolved, request clarification or recommend pausing a target. That is preferable to filling gaps with assumptions merely to complete a template.

Build a capacity and responsibility worksheet

Use one row per workstream rather than one row per person. This reveals whether an activity is unowned or duplicated. The worksheet should show the existing constraint, the proposed allocation and the buyer input required for the arrangement to work.

Add four fields to every completed row: named person, required evidence, review point and escalation route. Do not put the provider in the named-person field for a decision that the company has not authorised it to make. If the right internal person is unknown, resolve that before the task reaches them.

Review the worksheet with the provider and the operating stakeholders. Each should be able to explain where their work begins and what a successful handover looks like. Differences in interpretation are a reason to clarify the plan, not a reason to proceed and hope the process becomes obvious.

Prevent duplicate and contradictory owner contact

A lean team may rely on executives, business-unit leaders, advisers and existing industry contacts. Before any new outreach, establish a shared view of who already knows or has contacted the relevant company. Record only the information the team is authorised to hold and use.

Designate one coordination owner for external contact. That person does not need to conduct every conversation, but should know which conversations are active and what each participant is authorised to say. Without coordination, two well-intentioned people may offer different explanations of the buyer's interest or ask the owner to repeat the same information.

Create a simple contact rule: check the current record before a new approach, record the approach after it occurs and escalate uncertainty rather than guessing. Include restrictions such as no further contact, contact only through a named representative or discuss only a specified topic. These are operational instructions that should be visible to anyone working on the target.

A previous relationship does not automatically confer permission to disclose a private acquisition search. Where identities or identifying details require approval, obtain it before they enter an external message or draft. A useful anonymous overview can preserve momentum without bypassing that decision.

If duplicate contact does occur, reconcile the facts promptly. Decide who will own the relationship, agree a consistent explanation and avoid asking the owner to resolve the buyer's internal coordination problem. The incident should also trigger a process correction, not merely an apology followed by the same workflow.

Design an intake that saves executive time

An introductory pack should answer the questions the internal recipient needs for the next decision. It should explain why the target is relevant, what evidence supports that view, what the owner has actually agreed to discuss and what decision the buyer is being asked to make.

Keep the distinction between background and action clear. A long company description may be useful reference material, but it should not obscure the one unresolved question that determines whether a meeting is worthwhile. Put the decision request first and attach supporting detail in an organised form.

A practical intake record can use these fields: acquisition rationale, current evidence, owner-contact status, important unknowns, internal expert needed, proposed next step and decision owner. Add a date so the recipient understands when the information was checked. Do not label a target qualified without explaining the basis of that label.

Ask internal recipients what they need to assess a target efficiently. A product leader may need a workflow demonstration, while an operating executive may first need to understand management dependence. Standardise the common fields while allowing the key question to vary with the acquisition thesis.

The intake should reduce unnecessary meetings. If the evidence already shows that a hard constraint fails, the team can close the target with a reason. If a question can be resolved through limited research, do that before scheduling a broad executive discussion.

Set handover and escalation responsibilities

A handover should transfer context, not just a calendar invitation. The receiving person needs to know what the owner believes the conversation is about, what has already been shared and what should not be assumed. Otherwise the buyer risks restarting the discussion or making commitments inconsistent with the earlier approach.

Define the trigger for involving internal leadership. It might be credible product relevance combined with permission for a substantive discussion. The trigger should reflect the buyer's needs and the owner's willingness, not an arbitrary desire to show that a meeting has been arranged.

Escalation is necessary when the provider encounters a question outside its authority. Examples include a request to identify the buyer, a proposal to change the search scope or an owner asking for a commitment the representative cannot make. Specify who receives the question and what the provider may say while awaiting an answer.

Also identify what can be handled without escalation. Requiring senior approval for every routine research correction defeats the purpose of adding capacity. The division should permit execution within agreed boundaries while reserving decisions that change risk, representation or strategy.

At the end of a handover, record the next owner of the action. Shared responsibility can be useful, but it should not mean both parties assume the other is following up.

Protect the team from an unmanageable decision queue

More sourcing can make a small team less effective if it creates more active items than the team can assess. Before expanding the search, ask how many substantive target discussions the relevant operating leaders can support alongside their existing responsibilities. This is a capacity discussion, not a universal benchmark.

Separate active decisions from background research. The team may continue mapping a market while limiting the number of owner conversations requiring immediate executive attention. Make the distinction transparent so neither the provider nor the owner mistakes research activity for readiness to progress.

Use explicit queue states such as awaiting research, awaiting buyer decision and paused with owner permission. Assign a reason and an owner to each wait. An item should not remain active indefinitely because nobody has examined whether its original rationale still holds.

When the queue grows, diagnose before asking the provider to accelerate. The buyer may need narrower criteria, better intake information or a scheduled decision forum. It may also need to tell an owner honestly that the company cannot move at the desired pace.

A pause should preserve relationship context and permissions. It should not mean the target disappears from view until someone rediscovers it and starts the same conversation again.

A hypothetical allocation for a lean team

Consider a hypothetical company with a small corporate development function supporting several operating units. The team wants to add an adjacent product capability. It can assess strategic fit but lacks consistent time for company research and owner follow-up. No real buyer, target or engagement is represented.

Initially, the team considers asking an external provider to deliver more introductions. A workflow review reveals that several earlier introductions waited because operating leaders did not understand why the target mattered. The bottleneck therefore has two parts: research capacity and the quality of internal decision preparation.

The company retains approval of the acquisition objective, target constraints and external buyer description. It assigns a product leader to assess workflow fit and an operating executive to assess integration dependence. Corporate development remains responsible for deciding which conversations move to those leaders.

The proposed external scope covers market research, evidence-backed target records, authorised owner approaches and initial qualification. Before a target reaches the internal review, the record must explain the specific product connection and the owner's actual interest. Questions requiring technical assessment are flagged rather than answered by inference.

The team also introduces a short decision session. Each target receives one of four actions: obtain a specified fact, arrange a relevant internal discussion, pause for a stated reason or stop. The session is not a general pipeline presentation. It exists to clear decisions that would otherwise wait in individual inboxes.

During the hypothetical search, one owner requests an immediate discussion with the chief executive. The provider does not promise that meeting. It records the request and escalates it to corporate development, which decides whether the strategic relevance and preparation justify executive involvement. Another company clearly fails the approved product criterion and is excluded without senior escalation.

The arrangement succeeds as a design if each participant knows what to do and the buyer receives usable decisions rather than an expanding queue. Whether any transaction follows remains a separate question that the scenario does not assume.

Test a provider against the specific capacity gap

Ask the provider to restate the work it would remove from the internal team's day. Then ask what new work its service would require from the buyer. This second question is important. Research review, disclosure approval and owner meetings still require attention even when an external partner coordinates them.

Walk through one hypothetical target together. Observe whether the provider asks about strategic purpose, existing contacts, decision authority and the information needed at handover. A provider that cannot explain its dependencies may create more management work than the team expects.

Request a sample output relevant to the proposed task, using hypothetical or appropriately anonymised information. A research assignment should demonstrate research quality. An owner-dialogue assignment should demonstrate how responses and permissions are recorded. A full transaction presentation is not necessarily evidence that a narrow origination task will be performed well.

Ask who will do the work and how feedback reaches them. A lean team needs a relationship that can absorb corrections into a repeatable process. It should not need to re-explain the target criteria every time a new researcher or relationship manager becomes involved.

Finally, ask how the provider would handle a buyer-caused delay. The answer should include a clear escalation and owner communication process, not an assumption that the provider can keep every conversation active indefinitely without an internal response.

Where Acquiry can fit a lean corporate development model

Acquiry's published buy-side service includes shaping target criteria, researching companies, approaching owners and qualifying fit. Its company information also describes support for advisers needing origination capacity. For a small corporate development team, the relevant question is whether the proposed scope covers the research and owner-conversation work the team needs help with.

The buyer should retain the strategic and operating decisions that belong to the company. If the gap is specialist technical review, legal advice or integration delivery, commission the appropriate capability rather than assuming an origination engagement includes it. If the gap is simply an unresolved internal mandate, clarify the mandate first.

A useful discussion with Acquiry would therefore start with the capacity worksheet: what the team can do, what it cannot sustain, what it wants delegated and what evidence should arrive at handover. That is more informative than asking for a general promise of additional deal flow.

Run a review meeting around decisions and exceptions

A lean team benefits from a short, consistent review structure. Begin with changes to the brief or buyer availability. Then consider targets requiring a decision, owner conversations with a new development and exceptions that need escalation. Review general research coverage after the immediate decisions are clear.

For every item, ask what changed since the last review and what action follows. An unchanged target may still matter, but the report should explain why it remains active. Do not create a discussion simply because the item appears on the list.

Keep a decision log that records the action, reason, owner and next review point. When a criterion changes, the log helps the provider understand whether earlier exclusions should be revisited. When an owner has declined, it helps prevent later activity from contradicting the recorded response.

End by checking the buyer's own commitments. A provider can be blocked by missing information or decisions just as an internal team can. The review should expose those dependencies rather than make external activity the only subject of scrutiny.

Commissioning questions for the internal team and provider

Use the following questions to test whether the arrangement is ready to begin. Answer them jointly where responsibilities cross organisational boundaries. Any material unanswered question should become an explicit action rather than disappear into a broad description of collaboration.

• What specific work is currently waiting, and what evidence shows why it is waiting?
• Is the problem a shortage of time, missing expertise or unclear decision authority?
• Which decisions remain with the buyer, and who has accepted responsibility for each?
• What output will the provider deliver, and how will the buyer judge whether it is useful?
• Which internal experts need to be available when a target reaches the next stage?
• How will existing relationships and contact restrictions be checked before outreach?
• Who approves identifying disclosures and changes to the buyer's message?
• What happens when the buyer cannot respond within the pace an owner requests?
• How will the working record be transferred if the assignment changes or pauses?

The answers should be concise enough to use in practice. A lengthy responsibility document is not useful if participants cannot identify the next action during a live conversation. Keep the detailed scope available, but make the operating rules easy to find.

Questions small corporate development teams often ask

Can we delegate target screening without losing control?

Yes, if screening means applying approved criteria and recording evidence. Define which exclusions can be made without escalation and which questions require buyer judgement. Retain approval of material criterion changes. Ask for reasons behind both inclusions and exclusions so the team can verify that the delegated work reflects the brief.

Should the external provider attend every internal meeting?

Not necessarily. Include the provider where its information or participation helps the decision. Internal operating discussions may remain internal, with relevant conclusions passed back through the coordination owner. The objective is clear information flow, not universal attendance. Agree what feedback the provider needs to avoid continuing work against outdated assumptions.

What if the team only needs research for a limited period?

A bounded assignment may fit better than a broad ongoing role. Specify the market segment, required evidence, output format and handover. Confirm who will perform owner contact and qualification afterwards. The usefulness of research depends partly on the team's ability to act on it while the information remains relevant.

Can external support compensate for limited executive availability?

It can improve preparation and reduce unnecessary demands, but it cannot create executive attention where a decision genuinely requires it. Identify those decision points early. If the buyer cannot support them, narrow or pause the search rather than creating owner expectations that the company cannot meet.

How should we know whether the arrangement is working?

Return to the original bottleneck. Is relevant work moving with less rework? Are operating leaders receiving the context they need? Are owner conversations accurately recorded and coordinated? Is the buyer making clearer decisions? These questions assess the support model without treating transaction completion as the only evidence of useful work.

Reallocate work when the search changes

A capacity plan should not remain fixed after the underlying search changes. If the buyer narrows its focus, enters a new segment or pauses one operating unit's acquisition activity, review the allocation of research, contact and decision work. Otherwise the external team may continue producing material that no longer has an internal recipient.

Use a short change record. State what changed, why it changed, which workstreams are affected and who approved the revision. Identify active owner conversations that need a different message. Do not assume a change to the internal target profile has automatically reached everyone authorised to speak externally.

Consider a second hypothetical situation within the lean-team example. The product leader becomes unavailable while a major internal project is underway. The buyer could keep mapping the market, but it should not continue promising rapid technical discussions. It might assign another qualified reviewer, narrow the active queue or pause new approaches until the necessary capacity returns. The choice depends on the actual operating situation, not on maintaining an appearance of uninterrupted activity.

In that scenario, the researcher can continue checking public product descriptions and recording exclusions. The coordination owner can answer existing owners using an approved explanation of the pause. New technical meetings should wait unless another qualified reviewer accepts them. A target needing only a simple strategic exclusion decision can still be closed. This allocation preserves useful work without pretending the missing review capacity has been replaced.

Preserve the knowledge gained. A paused search should leave the buyer with a usable record of the brief, evaluated companies, contact permissions and unresolved questions. When work restarts, the team can check what remains current instead of rebuilding the history from scattered messages.

Review the support model itself when the same bottleneck persists. If research repeatedly arrives before anyone can review it, the company may need a smaller research scope rather than additional output. If internal experts repeatedly ask for the same missing information, adjust the intake standard. If every decision escalates to one unavailable executive, clarify what authority can responsibly be assigned elsewhere. These changes improve the division of work without assuming the provider can solve an internal governance problem alone.

Build a sustainable division of work

The best capacity allocation is one the buyer can maintain when the search becomes busy. Keep strategic choices and operating accountability clear, delegate defined work with acceptance tests and coordinate every owner conversation through a reliable record. External support should make the internal team more effective at its decisions, not simply give it more material to process.

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.

Sources and further reading

Acquiry, Buy-Side M&A Advisory. https://www.acquiry.com/acquisitions/

Acquiry, Official Information About Acquiry: Company Facts. https://www.acquiry.com/ai-instructions/