Startup Sourcing Mandate Template for M&A Teams

Most sourcing processes fail before the first company is evaluated. The mandate that kicked them off was either too vague to filter anything or too rigid to survive contact with a real market. One worked example, built for a green manufacturing search in East Asia, is faster to learn from than three pages of theory.

Quick answer: A corporate M&A sourcing mandate is a one-page brief that defines sector, geography, must-have capabilities, kill criteria, activity signals, and a success metric. A well-formed mandate lets any team member or any sourcing tool return a short list of active, relevant companies without re-litigating scope on every call. The template below includes a filled example for a green manufacturing search in East Asia.

Why sourcing mandates fail before they reach the committee

Most mandates are actually topic sentences. "Find green manufacturing targets in Asia" is a topic sentence. It tells a researcher what shelf to browse, not what to pull from the shelf. FounderNest's 2026 Scouting and Deal Sourcing Report, based on responses from more than 1,500 dealmakers, found that most corporate teams still rely on sourcing playbooks that miss 40 to 60 percent of the relevant market. Sourcing quality, not valuation creativity, has become the primary differentiator in M&A outcomes.

The gap between a topic sentence and a mandate is specificity: what capabilities the target must have, what signals tell you the company is genuinely active, and what single finding ends the conversation immediately. Without those three elements, every company on the long list looks arguable, and the committee meeting turns into a debate about whether the scope was right.

A 2026 Journal of Corporate Finance study from Warwick University found that acquisitions of private targets produce more patents and higher innovation synergies than acquisitions of public ones. The outcome correlates with acquirers' expertise in identifying innovative private targets. Identification methodology matters. A written mandate is methodology made portable.

The sourcing mandate template

A one-page mandate has six fields. Treat each as a constraint, not a description.

Sector names the technology or problem domain precisely enough that two people reading it independently would classify the same company the same way. "Green manufacturing" is still a topic sentence. "Electrochemical coating processes for steel and aluminum used in EV or industrial equipment production" is a sector.

Geography names the markets where you will look and, equally important, where you will not. East Asia is three very different sourcing environments: Japan, South Korea, and China each have distinct regulatory structures, currency risks, and integration complexities. Pick the ones that match the acquisition rationale.

Must-have capabilities is a short list of three items at most, stating technical or commercial capabilities the target must have for the deal to make sense. These are not wish-list features; they are the capabilities whose absence makes the acquisition pointless regardless of other qualities.

Kill criteria is the field most mandates omit. A kill criterion ends evaluation immediately, before a single analyst hour is spent. Common examples include total disclosed funding below a threshold that signals the company cannot survive integration due diligence, a founding team with no operating history in the target market, or IP that is licensed rather than owned.

Activity definition answers the question your committee will ask but rarely writes down: how do you know this company is active? A company incorporated five years ago with no product update, no hiring, and no customer reference in eighteen months is not active regardless of what a directory says. Define the signals (recent product releases, open engineering roles, observable customer references, or grant disbursements) that qualify a company for the short list.

Success metric is the number of qualified targets the sourcing round is expected to return, and the timeline. "Ten companies meeting all criteria within sixty days" is a success metric. "A good list" is not.

Filled example: green manufacturing, East Asia

The following mandate was built for a North American industrial equipment manufacturer evaluating strategic acquisitions in Japan and South Korea. It is an illustration of the template in use, not a client document.

Sector: Thermal process control and energy efficiency systems for metal fabrication, specifically companies whose core product reduces energy consumption in heat treatment, forging, or casting operations.

Geography: Japan (Aichi, Osaka, and Kitakyushu manufacturing corridors) and South Korea (Ulsan and Changwon industrial zones). China excluded for this round due to technology-transfer restrictions under current export-control review.

Must-have capabilities: (1) A deployed product with at least one paying industrial customer, not a pilot. (2) Sensor or controls IP that is owned, not licensed from a university or government lab. (3) Engineering team with hands-on experience in at least one of: automotive, shipbuilding, or heavy equipment manufacturing.

Kill criteria: Any of the following ends evaluation without escalation: founding team has exited or is documented as inactive, primary revenue is from government grants rather than commercial contracts, company has initiated or received an acquisition approach from a direct competitor in the past twelve months.

Activity definition: At least two of the following must be observable and dated within the past twelve months: a product release or version update, an open engineering or sales role posted on a public platform, a named customer reference (press release, case study, or conference presentation), or a grant disbursement from NEDO, KIAT, or a comparable national program.

Success metric: Eight to twelve companies meeting all criteria, delivered within forty-five days, each with a one-paragraph capability summary and a documented source for the activity signal.

The Japan-to-North-America green-tech corridor post on this blog covers the policy and funding environment that makes this geography worth a dedicated mandate right now. It is worth reading before you brief a sourcing team on the region.

For teams building mandates in the Osaka-Kansai manufacturing belt specifically, the Osaka-Kansai ecosystem post maps which sub-sectors have the densest concentration of acquisition-relevant companies.

How to use the template without over-engineering it

Fill all six fields before you source anything. If a field is blank, the sourcing round will produce a list you cannot defend, because the criteria that would have eliminated half of it were never written down.

The most common mistake is treating the mandate as a living document during the sourcing round. It is not. If the scope shifts mid-round because the committee changed its mind, because the geography proved thin, or because a better opportunity surfaced, close the round, revise the mandate, and restart. Sourcing against a moving target produces a list that no one trusts.

The second most common mistake is using activity signals that are easy to find rather than signals that are meaningful. A company's LinkedIn follower count is easy to find. A named paying customer is meaningful. Build the activity definition around the signals that would survive a five-minute skeptic's review in committee.

Chibit's sourcing process applies activity signals like these before a company reaches your screen, so the short list you receive is already filtered for genuine, current relevance to your mandate, not just categorical fit. If you want to test the approach against a specific mandate, Innovation Scout takes your goals as input and returns a matched set of vetted, currently active companies.

The startup due diligence checklist on this blog covers what to verify once you have a short list. The mandate gets you to the list; the checklist gets you past it.

Common pitfalls when writing a sourcing mandate

Before a team submits a mandate to a committee or a sourcing partner, four failure modes appear repeatedly.

The first is circular geography. "Asia-Pacific" is not a geography; it is a continent and a half. The mandate should name specific markets and, where relevant, specific industrial zones within them. Aichi Prefecture and Gyeonggi-do are not interchangeable sourcing environments.

The second is capability inflation. A list of ten must-haves is a wish list, not a mandate. Three capabilities, rigorously chosen, will eliminate more irrelevant targets faster than ten loosely chosen ones.

The third is undefined activity. If the mandate does not specify what qualifies as active, every company on a directory qualifies. Directories are indexes, not diligence. A company can be listed, incorporated, and effectively dormant.

The fourth is no kill criteria. Without explicit kill criteria, evaluation creep sets in. Analysts spend time building cases for companies that should have been eliminated in the first pass. The rule is simple: if finding X ends the deal, write X in the mandate before you source.

FAQ

What is a sourcing mandate in corporate M&A?

A sourcing mandate is a one-page brief that defines the sector, geography, required capabilities, disqualifying factors, activity standards, and success metric for a target search. Any person or tool running the search returns results against the same criteria, rather than re-interpreting scope at each step.

How detailed should a startup sourcing mandate be?

A mandate should be specific enough that two independent researchers, reading it separately, would classify the same company the same way. In practice, that means sector described at the technology or problem-domain level, geography named by country or region rather than continent, and capabilities stated as verifiable conditions rather than adjectives.

What counts as an activity signal for a startup sourcing brief?

An activity signal is an observable, dated event that confirms the company is operating. Useful signals include a product release or version update in the past twelve months, an open engineering role posted publicly, a named paying customer in a press release or case study, or a grant disbursement from a named government program. A company's presence in a directory is not an activity signal.

Should kill criteria be included in the mandate or handled later in diligence?

Kill criteria belong in the mandate. A criterion that ends the deal (unlicensed IP, an inactive founding team, a competing acquisition approach) is faster and cheaper to apply in the sourcing round than in diligence. Writing kill criteria into the mandate protects analyst time and keeps the short list defensible.

How is a sourcing mandate different from an investment thesis?

An investment thesis explains why a category of company is strategically interesting. A sourcing mandate translates that thesis into operational criteria. Specific enough to filter a real list of real companies, the thesis answers "why this space"; the mandate answers "which company in this space is worth a call next week."

If you have a mandate in hand and need a short list of active, relevant companies matched to it, describe your goals at https://chibit.io/scout.