PoC, Procurement, Strategic Investment, or M&A: What 'We're Very Interested' Actually Means in Taiwan
The same 'we're very interested' means four different things from an innovation team, a procurement office, a CVC, and a strategy executive. This guide separates PoC, procurement, strategic investment, and M&A across four axes: owner, budget, documents, and timeline.

On this page (5)
Before you read: This is general educational information and practical orientation, not investment, legal, accounting, or tax advice; it also promises no particular collaboration, procurement, or investment outcome. Internal processes, budget cycles, and decision authority at Taiwanese companies vary case by case — the timelines and departmental divisions below describe common patterns, not universal rules. For specific deal terms, confidentiality and disclosure, or corporate governance, consult a qualified professional.
Four paths that all go by the name "collaboration" are, inside a corporation, four separate and unsynchronized decision systems. The first thing a founder needs to learn is not how to negotiate, but how to recognize which path they are actually standing on.
On Monday, the innovation team at a listed company asks to set up a PoC. On Wednesday, someone from the same company's investment unit invites you for coffee. At the end of the month, procurement emails you a supplier-registration form. Three moves from one company — and it is tempting to read them as "the same thing accelerating through different doors." In reality each has its own owner, spends its own money, runs on its own timetable, and the three often do not even know the others are talking to you. The cost of blurring them is concrete: you put the wrong resources into the wrong path, prepare the wrong documents, hold the wrong timeline expectations, and end up empty-handed on both ends. Sort the paths first, and you will know what to prepare now, whom to talk to, how long to wait, and which path has not actually started at all.
What each of the four paths is really exchanging
In one line: a PoC exchanges "feasibility information," procurement exchanges "a product or service," strategic investment exchanges "equity plus an option on a deeper future relationship," and M&A exchanges "control of the whole company." Because the thing being traded differs, the decision system behind each is entirely different. To pin down the distinction, ask one question of each: with what resource, taking what risk, is the company buying what?
A PoC (Proof of Concept — a small-scale, scope-limited trial that tests whether something actually works) uses a department's small budget, or even free collaboration time, to buy the information called "feasibility." The person driving it is usually the innovation team or the operating unit that would eventually use your product. Procurement spends a line item in the annual budget to buy an actual usable product or service, and runs as a two-step dance: the operating unit raises the need, the procurement office gates the process. Strategic investment uses equity capital to buy not the cost-benefit of this one order but a strategic position — an option on whether the two of you can bind together more deeply later — and the decision-maker shifts to a CVC (Corporate Venture Capital — a corporation's strategic investment unit or fund) or corporate investment office. M&A uses corporate capital to buy "control": acquiring the whole company, team, and technology and integrating it inward, a call made by senior strategy leadership and the board.
The risk climbs with each of these four, and so does the weight of what is bought — which is why their owners, budget sources, documents, and timelines have almost no cell in common. The table below sets the four axes side by side, because when four paths are compared at once a grid shows the gaps at a glance better than prose:
| Axis | PoC | Procurement | Strategic Investment | M&A |
|---|---|---|---|---|
| Owner inside the company | Innovation team, operating unit | Operating unit + procurement office | CVC / investment unit | Senior strategy, board |
| Where the money comes from | Small department budget, often free | Annual budget line item | Investment budget or fund | Corporate capital |
| Key documents | NDA, PoC plan | Procurement spec, contract, supplier qualification | Term sheet, shareholders' agreement | Letter of intent, due-diligence checklist |
| Typical timeline | Weeks to months | Months, often across a budget cycle | Three to six months or more | Six months to over a year |
| Main risk to the startup | No next step after it ends | Long process, competitive bidding | Terms that affect the next round | Leaked secrets, long team distraction |
*The "typical timeline" column is illustrative of common cases; actual length varies by company and situation and is not a hard threshold.*
One path at a time: the lowest barrier hides the deepest trap
A PoC has the lowest barrier precisely because the company is taking the smallest risk — often no budget request is needed, and the innovation team can start it with its own people and time. That is also its biggest trap: the person willing to greenlight a PoC usually has no authority to push the result all the way to a paid contract. So whether a PoC is worth your effort turns not on how enthusiastic the other side is, but on whether two things are written down in advance — the acceptance criteria (what success looks like, by what number it is judged) and the post-success destination (who owns carrying it to the next stage, and to where). Without those two, even the smoothest PoC may finish and stop in place, because the person who said yes is not responsible for what comes after. This is also where you sign an NDA (Non-Disclosure Agreement — both sides agree the information exchanged may not be leaked or repurposed) to fence off what you hand over during the trial.
On the procurement path, what you face is not enthusiasm but process. Procurement at mid-to-large Taiwan companies typically clears supplier qualification, an information-security review, and competitive bidding or negotiation, while the annual budget is usually set in Q3-Q4 of the prior year (actual timing varies by company size and policy — SMEs and the local branches of foreign firms do not always follow this rhythm). In other words, even if the operating unit wants to buy right now, that money may not truly exist until the next budget year. So when you hear "we want to deploy," the real thing to ask is not how sincere they are but three concrete points: is the budget allocated, under which line item, and how many gates the process clears. Clear those three up and you will know whether this is "happening this quarter" or "a next-year thing." Whether you can survive until then is your own judgment call, but at least you will not be left hanging on an enthusiastic "we want to deploy."
The investment path buys your future, not your product. The decision-maker becomes a CVC or investment unit, and what they weigh is not whether this single order pencils out but strategic value and equity return — whether your company can become a piece of their ecosystem, and whether it will be worth more in a few years. The documents change accordingly: from a procurement contract to a term sheet (the document that, before formal signing, fixes the investment amount, valuation, and main terms), and the scope of review widens from product spec to finances, cap table, and team. Here, watch the terms, not the amount. Exclusivity clauses (agreeing you can work only with them and not their competitors), rights of first refusal, and the like follow the company for years; they shape your flexibility in the next round and your future exit options — far more than just how much money lands this time. One mistake to avoid is reading "the investment unit expressed interest" straight as "a big order is on the way" — whether a business unit will actually buy your product is a different department running a different logic.
The M&A path has the longest process and the highest cost, and what is on the table is control: team retention, technology integration, customer transfer — all of it. For an early-stage company, two practical risks both come down to "dragging on." The first is information: in due diligence (the buyer's full pre-close verification of the target), your core technical details and customer list pass in volume to the other side, and if the deal collapses, that information is still in their hands — a risk that is graver still if the other party is itself a potential competitor. The second is attention: M&A talks routinely run half a year or more, the founder's focus gets pulled away, core-business growth stalls, and that actually weakens your position at the table because the other side can see your numbers slipping. So once M&A exploration starts, minding the core business while you talk matters more than rushing to lay every card on the table.
Reading the path back from a single sentence
Word choice leaks the path. "Let's try a small-scale test first" is a PoC; "please complete supplier registration" is procurement; "we'd like to understand your cap table better" is investment; "we've thought about a deeper combination" is an early M&A probe. The other side rarely says it outright, but the path each sentence maps to — and what you should ask next — is nearly fixed:
| What you hear | Path | What to ask next |
|---|---|---|
| "Let's try a small-scale test first" | PoC | What are the acceptance criteria, and who owns pushing it forward after success |
| "Please complete supplier registration" | Procurement | Is the budget allocated, under which line item, how many gates the process clears |
| "We'd like to understand your cap table better" | Investment | Are they a CVC or a business unit, and roughly where the terms are heading |
| "We've thought about a deeper combination" | Early M&A probe | Hold the disclosure boundary; sign an NDA before talking |
This mapping is not meant to be applied mechanically — the same sentence can mean different things at different companies. The point is to build the habit of "when I hear collaboration interest, first ask myself which path this is." And the place things most often go wrong is misreading the path. The most common mismatch is doing PoC work on investment expectations: you hear the investment unit is interested, so you sink three months into free custom validation, only to discover that the investment decision and the PoC result sit in two different departments that do not vouch for each other — three months of engineering given away for free. The reverse happens too: treating the procurement process as a prelude to investment, assuming "if they buy, they'll invest," when at most companies procurement and investment are parallel lines — procurement signs a contract and the investment unit may not even know who you are. Every path is worth walking, provided you know which one you are on and prepare materials and timeline expectations by that path's rules; effort spent on the wrong path does not automatically convert into progress on another.
A closing principle on disclosure: how much information to give during M&A exploration follows a simple rule — sign an NDA first, then disclose in stages. Commercial information can go early; core technical detail and the customer list wait until certainty is higher, and you stay more conservative still when the other party is a potential competitor — bring in a lawyer to design the disclosure pacing where it matters.
The judgment to take away
Compress these four paths into one operating rule: at your next meeting, ask three questions outright — is the goal of this discussion to validate feasibility, to deploy on a paid basis, to make an equity investment, or to pursue a deeper combination? Which department owns it internally, and who holds the budget or investment mandate? And what document does the next step require — a PoC plan, a procurement spec, or investment-evaluation materials? Those three answers almost always locate which path you are on. What you should never do is sink heavy resources before the path is clear, especially free custom development — when the other side cannot even answer those three questions, downgrade the engagement to "exploratory conversation" and don't rush to deploy the engineering team. Collaboration is not more sincere for starting faster; recognizing which path you stand on, and only then deciding how much to invest, is the discipline a founder can actually control and most needs to hold.
Sources
- BCG — A Framework for Deep-Tech Collaboration
- McKinsey — Three Essentials of Successful Corporate Venture Capital
This article cites external material for general educational reference; different companies' internal processes, different deal terms, and individual circumstances may warrant different judgments, and formal collaboration and investment decisions should be separately verified and reviewed with a qualified professional.
Note
This is general educational information and practical orientation; it does not constitute investment, legal, accounting, or tax advice, nor a promise of fundraising success, returns, exit, or procurement outcomes.
Sources
- BCG — A Framework for Deep-Tech Collaboration— Boston Consulting Group
- McKinsey — Three Essentials of Successful Corporate Venture Capital— McKinsey & Company
