Three Companies, Three Failures
The General Counsel of a B2B technology company recognised that the legal department needed a contract lifecycle management system (CLM). Contracts were difficult to locate. Approvals were slow. The team was spending time on administrative work that should have been automated. A separate budget was allocated for the project — but it sat inside the legal department's allocation, approved as a legal cost rather than a business investment.
That framing had consequences from the outset. Contracts in any organisation are not a legal department asset. They are created by sales, procurement, HR, finance, and operations. They govern supplier relationships, customer commitments, employment terms, and technology arrangements. A CLM system is not legal infrastructure — it is business infrastructure that legal helps govern. When the budget is the legal department's budget, the project is constrained to what legal can justify, the authority is limited to what legal can mandate, and every other department that depends on contracts becomes a stakeholder with no accountability for the outcome.
The lawyer assigned to lead the evaluation reasonably concluded that a CLM system was a technology system and brought in IT colleagues to assist. After two years of evaluation, the commercial systems on the market were deemed too expensive relative to the available budget. The decision was made to ask IT to build something instead — a redesigned document repository and e-approval workflow adapted from systems already in use.
The lawyer was then asked to document the legal processes the new system would need to support and work with IT to translate them into requirements. She found herself doing work she had not been trained for — process mapping, requirements documentation, system design — while her legal responsibilities continued unchanged. IT built faithfully to the specifications they were given, but had no independent understanding of why legal processes work the way they do. They could build what they were told. They could not challenge whether what they were told was right.
Two years later, the system was built. Contracts were still difficult to find. Approvals were still slow. The automation that had been the original objective was not there. The same problems remained — now with the added sunk cost of two years of a lawyer's diverted time and a custom-built system that would need to be maintained indefinitely.
The digital transformation office of a large B2C insurance group identified CLM as a priority. For an insurance company, contracts are the core business — policies are contracts, distribution agreements are contracts, reinsurance arrangements are contracts, vendor relationships are contracts. The volume is enormous, the complexity is high, and the regulatory stakes attached to contractual terms are significant. The digital transformation team brought legal and IT together and began a systematic evaluation of CLM vendors.
Three years later, they still had not selected a system. The GC, when asked to describe the obstacle, identified the same issue each time: the company had too many systems already, and contracts were spread across all of them. Policies administered in one platform. Vendor agreements in another. Distribution contracts in a third. Employment contracts in HR systems. Legacy agreements in shared drives or physical files. Every CLM vendor demo was impressive — and every demo raised the same unanswerable question: where would this system fit in a landscape this fragmented, and what would it replace?
The answer nobody had given them was that this question could not be answered by evaluating CLM vendors. It could only be answered before the vendor evaluation began — by mapping every contract type, every system, every process, and every stakeholder, and defining what a future state should look like before asking which technology could support it. Without that analysis, the vendor evaluation was a search for a solution to a problem that had not yet been properly defined. Three years of evaluation produced three years of vendor demos and no decision. The contracts remain where they were.
The GC of a B2B manufacturing company wanted a CLM system. He had seen one in operation at a previous employer and understood what it could do. Contracts were hard to find, approval cycles were slow, and the legal team had no visibility into what commitments the business had made across its supplier and customer base.
He went to the CFO with a budget request. The problem was timing: the request was submitted before the evaluation was complete — before the contract landscape had been mapped, before the requirements had been defined, before he had a clear picture of what the organisation actually needed and which systems could deliver it. The budget was sized on instinct and initial market impressions, not on evidence. It was approved.
When the evaluation proceeded, it became clear that the systems within the approved budget would not solve the problems he had identified. The systems that would were approximately three times the approved amount. He did not go back to the CFO. He had already used his one request, and returning with a number three times larger — without the analytical foundation that would have justified it — was not a conversation he felt he could have.
Two years later, there is still no CLM.
But underneath the budget problem sits a more fundamental question. Was the GC the right person to be leading this process at all? Selecting enterprise infrastructure requires contract landscape analysis, cross-functional requirements definition, vendor assessment methodology, and business case construction — capabilities that sit outside most GCs' training and experience, and that belong to legal operations as a discipline. The GC is the right person to articulate what legal needs from a CLM. Whether a particular system achieves that, what it should cost, and how to build the case for it — that is a different kind of work, requiring a different kind of expertise. Asking the GC to do it without that support is how you get a budget request submitted too early, sized incorrectly, and spent on the wrong problem.
What Those Failures Actually Cost
The three scenarios above share a surface feature: nothing was implemented. But "nothing was implemented" is not a neutral outcome. It has a cost — and in most Asian corporations, that cost has never been calculated because nobody was asked to calculate it.
Contract management is where corporate value leaks. The evidence on this point is extensive and consistent. Research by World Commerce & Contracting (WorldCC) — the global body formerly known as the International Association for Contract & Commercial Management (IACCM), drawing on data from more than 700 organisations — found that poor contract management costs companies an average of 9.2% of annual revenue. McKinsey independently confirmed this figure in a 2018 study, noting that for Fortune Global 500 companies alone, the aggregate value of that leakage would have equalled USD 2.5 trillion. Even best-in-class performers, according to the same research, still lose more than 6% of annual revenue through contract value leakage.
The cost of processing contracts without the right infrastructure compounds this. WorldCC research found that the average cost of processing a single basic contract — from drafting through negotiation to signature — is USD 6,900. Mid-complexity contracts average USD 21,300. High-complexity contracts reach USD 49,000 and above. EY research found that large organisations manage an average of 350 contracts per week. At those volumes, the cost of manual, unoptimised contracting processes is not an inconvenience. It is a significant and recurring operational expense.
And then there is the cost of contracts that cannot be found. Research published in the Journal of Contract Management found that 71% of companies could not locate at least 10% of their contracts. A contract that cannot be found cannot be enforced, cannot be renewed on terms, cannot be reviewed for compliance, and cannot inform the business decisions that depend on knowing what commitments have been made. In regulated industries — and every industry in Asia is becoming more regulated, faster — a contract that cannot be found during a regulatory investigation is not merely an administrative inconvenience. It is a liability.
Now return to the three companies. The B2C insurance group spent three years evaluating CLM vendors without making a selection. Every year of delay is a year of continued contract value leakage at the 9.2% rate — applied to the revenue base of a large insurance group, that is a very large number. The B2B technology company spent two years building a system that did not solve the problem and will now need to spend more time and money to build or procure a system that does. The B2B manufacturer submitted a budget request before the analysis existed to support it, received approval for a figure that turned out to be insufficient, and now has no path back to the CFO without the evidence that should have been built before the first request was made.
In each case, the cost of not solving the problem exceeds the cost of the right solution. The difference is that the cost of not solving it is invisible — distributed across a hundred small inefficiencies and missed opportunities — while the cost of the solution arrives as a line item that requires approval. All three companies understood that a CLM would help. What none of them had was the framework to implement one successfully. Understanding why requires looking at what CLM implementation actually demands — and what it is not.
Why CLM Is Not a Technology Decision
The three scenarios in this article are not unusual. Gartner has estimated that nearly 50% of first-time CLM implementations fail to deliver expected benefits. A 2022 survey by Onit's ContractWorks found that 77% of in-house counsel have experienced a failed legal technology implementation. These are not failures of technology — the CLM market is mature, well-funded, and offers capable systems at multiple price points. They are failures of methodology.
The methodology that makes CLM implementations succeed is legal operations — a distinct discipline that sits at the intersection of process design, technology, data management, vendor management, financial management, and organisational strategy. Legal operations asks different questions from the ones lawyers ask. A lawyer asks: what is the legal position? Legal operations asks: how does this legal work get done, how much does it cost, how long does it take, and how could it be done better? Most Asian corporations have been slow to build this capacity — not by accident, but for structural reasons: in-house teams that are lean relative to the businesses they serve, budgets sized for legal costs rather than legal investment, and a function that keeps getting deferred because there was never capacity to build it. The external environment is changing that calculus. Data privacy laws, AI governance frameworks, and trade compliance obligations have each added material workload to legal functions that were already stretched across the region. The infrastructure gap that was manageable five years ago is not manageable now.
CLM is not a technology decision. It is a legal operations project. The distinction matters enormously, because a technology decision is answered by evaluating systems and selecting one. A legal operations project is answered by a sequence of prior steps that must be completed before any system can be meaningfully evaluated:
Before a CLM can be specified, an organisation needs to know what it is managing. How many contracts exist? Of what types? Sitting in which systems, in which formats, under whose ownership? What are the typical contract volumes by type? What are the approval workflows currently in use, and are they consistent across the organisation? A company that begins a CLM evaluation without this analysis will not be able to answer the questions every vendor will ask — and the answers will differ across business units, geographies, and contract types in ways that will directly constrain the technology options available. This is the analysis the B2C insurance group had not done after three years of evaluation. Had they done it first, they would have known earlier that selecting a CLM vendor was the wrong first question.
A CLM system automates contract processes. If those processes are not mapped — if the organisation does not have a clear, agreed picture of how a contract moves from request through drafting, review, approval, execution, storage, and obligation tracking — then the system has no processes to automate. It will automate what it is given, which is typically the existing broken process in a new interface. The B2B technology company's experience is the predictable outcome of implementing a system before mapping the processes it is meant to support.
A CLM system can do many things. The question is which of those things the organisation actually needs, in which sequence, and with what priority. Requirements definition translates the contract landscape analysis and process mapping into a specific set of functional requirements that a system must satisfy. Without it, vendor evaluation becomes a comparison of feature lists against an undefined standard — which produces either selection paralysis or selection of the most impressive demo rather than the most appropriate system. This is also the step that makes a CFO budget request credible: a requirements document gives a number context, explains why a particular price point is necessary, and allows management to evaluate the trade-offs.
Contracts are not owned by legal. They are created by sales, procurement, HR, finance, and operations — reviewed by legal, approved by executives, and monitored by whoever is responsible for the underlying commercial relationship. A CLM system that serves only legal's needs will not be adopted by the rest of the organisation. Stakeholder alignment — understanding what each function needs from the system and building those requirements into the design — is a legal operations exercise, not a legal one. It requires facilitation skills, organisational authority, and cross-functional credibility that a practising lawyer assigned to a project role is unlikely to have.
EY research found that 99% of organisations lack the data and technology needed to improve their contracting processes — and that 60% are attempting sweeping transformational changes. The gap between those two statistics is change management: the capability to move an organisation from its current state to a new one in a way that sticks. CLM implementations that treat go-live as the finish line rather than the starting point of adoption consistently underdeliver. The B2C insurance group's three-year evaluation was not, at its core, a technology problem. It was the consequence of attempting a transformation without the process foundation and organisational alignment that would have made any technology selection possible.
The common thread is sequence. The organisations in the three scenarios attempted to answer a technology question — which CLM system should we buy? — before they had answered the prior questions that make that question answerable. Legal operations exists to answer those prior questions. Its absence does not make the technology question easier. It makes it impossible.
Why CLM Needs to Sit Above the GC
The B2B manufacturer's scenario is the most instructive of the three, because it surfaces two distinct failures that are easy to conflate. The first is a sequencing failure: the budget request was submitted before the analysis that would have justified it existed. The second is a role design failure: the GC was asked to do work — contract landscape analysis, requirements definition, vendor assessment, business case construction — that sits outside legal expertise and belongs to legal operations as a discipline. Neither failure reflects badly on the GC. Both reflect an organisation that had never defined what a CLM implementation requires, who should lead it, or what it should cost.
A CLM implementation cannot be led from within a legal department that is already under-resourced, working from a budget sized for legal costs rather than business investment, and lacking the cross-functional authority that implementation requires. The constraints are real. The budget is insufficient. The mandate does not extend to what the project needs. And the GC who has tried to raise these issues and been told to make do has learned, rationally, not to try again.
Breaking that cycle requires something the legal department cannot supply for itself: C-suite recognition that a CLM is a business investment — not a legal department technology project — and that it requires business-level sponsorship, budget, and governance to succeed.
The financial case for that recognition is straightforward. WorldCC's research puts contract value leakage at 9.2% of annual revenue on average. A company with USD 200 million in revenue is, on this evidence, likely losing USD 18 million annually through poor contract management. The right CLM system, properly implemented with appropriate legal operations support, will not recover all of that — but recovering even a fraction of it produces an ROI that comfortably justifies the investment.
These are not arguments that a GC can make effectively from within the legal department, because they require claims about business value in domains — finance, operations, risk — where the GC is not typically seen as the authoritative voice. They require a CFO or CEO who has been presented with the financial analysis and asked to make a decision about CLM as a business investment. In the companies where CLM has been implemented successfully, that conversation happened. It happened because someone with sufficient organisational authority decided that the question of how the business manages its contracts was a business question, not a legal one.
That is the conversation this article is an invitation to have.
What CLM Looks Like When It Works
A CLM implementation that is properly scoped, adequately resourced, and supported by the legal operations foundation it requires does not announce itself dramatically. The changes are operational and financial, and they accumulate over time rather than arriving as a single visible transformation.
Contracts are findable. Not all of them immediately — building a contract repository takes time, and legacy contracts require a migration effort that is neither fast nor cheap. But within a defined period of implementation, the legal team and the business can locate a contract, identify its key terms, check its expiry date, and understand the obligations it creates. The millions that organisations spend annually searching for and recreating lost contracts do not disappear overnight, but they begin to shrink.
The legal team is advising the business rather than processing its paperwork. When contract requests arrive through a structured intake process, are triaged according to risk and complexity, and routed to the appropriate resource — whether that is a standard template, an AI-assisted review tool, or a senior lawyer — the legal team's time is deployed against the work that actually requires legal judgment. The junior lawyer who spent two years managing a CLM evaluation she was not equipped for is doing legal work. The GC who was approving routine contracts because there was no workflow to route them elsewhere is available for the strategic work that justified hiring a GC in the first place.
That operational credibility — the ability to deliver at speed, manage costs visibly, and get ahead of problems rather than react to them — changes how the rest of the organisation perceives the legal function. And that shift in perception is what ultimately gives the GC something that no amount of legal expertise alone can provide: a seat at the table where business decisions are made.
The GC who has that seat is not there because the organisation got lucky with a particularly business-minded lawyer. The function earned it. The CFO trusts the legal spend numbers because they are tracked and explained. The CEO consults the GC on strategic decisions because legal's input arrives on time and in a form that informs rather than delays. A well-implemented CLM — treated as business infrastructure rather than a legal technology project — is what makes that possible.
Before the Vendor Demo: Three Questions
For most Asian companies reading this article, the right starting point is not selecting a CLM vendor. It is answering three questions that make vendor selection possible — and that make a budget request credible when it is submitted. Most organisations are at a stage where contracts are managed in spreadsheets and shared drives, with no structured intake process and no systematic obligation tracking. That is not a criticism — it is a description of where most organisations are before they begin. The question is not whether to start, but how.
Not what you think it looks like — what it actually looks like, across every business unit, geography, and system where contracts currently live. This analysis will take time and will produce findings that are uncomfortable. That discomfort is useful information. The B2C insurance group that could not select a CLM after three years had not done this analysis. If they had, they would have known earlier that the question they were trying to answer was the wrong question to start with.
This is the calculation the B2B manufacturer did not run — and the absence of it is what made his CFO conversation impossible the second time. It is not a complicated calculation, but it requires someone to make it. Apply the 9.2% WorldCC figure to your annual revenue. Apply the WorldCC contract processing cost to your estimated annual contract volume. The resulting number is not precise — but it is directionally correct, and it is the number that makes the business case possible.
CLM implementation requires cross-functional authority, a budget that is sized appropriately, and organisational sponsorship at a level above the GC. If the answer to "who owns this" is "the lawyer the GC assigned to it," the project will produce the same outcome as the three scenarios in this article. If the answer is "the CFO and GC jointly, with board-level awareness and a budget that reflects what the problem actually costs," the project has the foundation it needs.
These three questions are the starting point. Answering them honestly, with the right expertise in the room, is the work that comes before any CLM evaluation, any vendor demo, and any technology decision. It is the work that the three companies in this article did not do before they began.
The Conversation That Needs to Happen
Three companies, seven years of combined effort, no CLM implemented. The same contracts still hard to find, the same approvals still slow, the same costs still accumulating.
The argument this article makes is not that CLM is hard. It is that CLM is a different kind of challenge from the one most organisations prepare for. It is not a technology selection problem — the technology is available, mature, and capable at multiple price points. It is an organisational problem: a project that requires prior analysis, cross-functional alignment, a budget appropriate to a business investment, and sponsorship that sits above the GC's authority in most organisations. The three companies in this article did not fail because they chose the wrong system or because the vendors were inadequate. They failed because they attempted to answer a technology question before they had answered the organisational questions that make a technology decision possible.
Getting CLM right requires treating it as what it is: a business investment, led at a level of the organisation that can commit the resources, assign the cross-functional accountability, and mandate the sequencing that implementation requires. The companies in Asia that have deployed CLM successfully did not do so because they found a better vendor or allocated a larger budget. They did so because someone at the appropriate level of the organisation decided that the question of how the business manages its contracts was worth answering properly.
That decision is the starting point. Everything else follows from it.
This article is for informational purposes only and does not constitute legal advice. The regulatory landscape and market data described reflect publicly available information as at the date of publication and are subject to change. Readers should obtain appropriate professional advice before taking or refraining from any action in reliance on the information contained in this article. CloudVista Consulting LLC accepts no responsibility for any loss or damage arising from reliance on this material.
三個案例，三種失敗
一家B2B科技公司的法務長意識到，法務部門需要一套合約生命週期管理系統（Contract Lifecycle Management，CLM）。合約難以查找，簽核遲緩，法務人員大量時間耗在理應自動化的行政工作上。獨立的專案預算獲批——但歸在法務部門編列內，以法務費用而非企業投資的名義核准。
這個定性，從一開始就埋下了問題。組織裡的合約，從來不是法務的專屬資產。它們由業務、採購、人資、財務、營運等部門發起，規範著供應商關係、客戶承諾、僱傭條件和技術安排。CLM不是法務的基礎建設，而是由法務協助治理的企業基礎建設。預算歸屬在法務，專案的邊界就只能到法務能夠自行合理化的範圍，授權也只及於法務能夠要求執行的地方。其他一切依賴合約的部門，都成了對結果沒有承擔的局外利害關係人。
被指派主導評估的律師，合理地判斷CLM屬於資訊系統，因而邀請了IT同仁一起協助。兩年後的結論是：市場上的商業CLM系統費用超出可用預算。最終決定由IT部門改造既有系統，重新設計文件儲存庫和電子簽核流程。
接下來，這位律師被要求梳理法務流程，並配合IT撰寫需求文件。她發現自己在做沒有受訓、也不該被指派的工作——流程梳理、需求規格定義、系統設計——而她原有的法律職責一樣沒有縮減。IT同仁按照拿到的規格忠實開發，但對法務流程背後的風險控管邏輯並無獨立判斷。能做被交代的事；無法質疑被交代的事是否正確。
兩年後，系統上線了。合約還是找不到。簽核還是慢。當初期待的自動化仍不存在。原本的問題一個都沒解決——多的是兩年律師時間的沉沒成本，以及一套需要長期維護的客製化系統。
一家大型B2C保險集團的數位轉型辦公室，將CLM列為優先推動項目。對保險公司而言，合約就是核心業務本身——保單是合約，通路協議是合約，再保安排是合約，供應商關係也是合約。合約量龐大，複雜度高，監管風險直接附著在合約條款上。數位轉型辦公室召集法務與IT，展開系統性的CLM供應商評估。
三年後，仍未選定任何系統。法務長每次被問及為何遲遲無法推進，指向的都是同一個困境：公司既有系統太多，合約分散各處，不知道從何著手。保單在一個平台，供應商合約在另一個，通路合約在第三個，勞動合約在HR系統，歷史合約在共用硬碟或實體檔案。每一家供應商的展示都令人印象深刻，但每一場展示都帶出同一個無從回答的問題：這套系統要放進現有版圖的哪個位置？要取代什麼？
沒有人告訴他們，這個問題本來就不屬於CLM供應商評估階段才應去面對的問題。它只能在此之前——透過完整的合約版圖分析，釐清每種合約類型、每套系統、每條流程、每個職責歸屬，並在詢問哪種技術能支援之前，先定義未來應有的狀態——才有辦法回答。沒有那份分析，供應商評估就是在為一個尚未被清楚定義的問題尋找解答。三年的評估，換來三年的展示，零個決策。合約還在原處。
一家B2B製造商的法務長想要一套CLM系統。他在前任雇主見過CLM實際運作，知道它能做什麼。合約難以查找，簽核周期過長，法務對公司在供應商和客戶端究竟承擔了哪些義務，完全沒有能見度。
他帶著預算申請去找財務長。問題在於時機：申請在評估完成之前就送出去了——合約版圖尚未梳理，需求尚未定義，什麼系統能真正解決問題，他自己還沒有清晰的答案。預算規模依靠直覺和初步的市場印象，而非分析——但申請獲批了。
評估繼續推進，才發現核准預算範圍內的系統解決不了他想解決的問題。能夠真正對症的系統，費用大約是核准金額的三倍。他沒有回去找財務長。一次機會已經用掉；帶著一個大三倍的數字回去，卻沒有足以支撐的分析論據，不是他認為可以進行的對話。
兩年過去，仍沒有CLM。
預算問題之下，還有一個更根本的問題：法務長本來就是主導這個流程的適當人選嗎？選型企業級系統需要合約版圖分析、跨部門需求定義、供應商評估方法論，以及商業可行性論證——這些能力超出多數法務長的訓練與專業背景，屬於法務營運作為獨立學科的工作範疇。法務長是定義法務部門需要CLM哪些功能的適當人選；但特定系統是否能實現這些功能、費用應當如何、如何建立說服管理層的論證——這是性質截然不同的工作，需要不同類型的專業能力。在缺乏那種配套支援的情況下要求法務長獨力完成，正是讓預算申請過早送出、規模估算失準、資源投入錯誤問題的根本原因。
「什麼都沒做」的實際代價
三個案例的表面共同點是：什麼都沒有落地。但「什麼都沒落地」不是零成本的結果——它有代價。而在多數亞洲企業，這個代價從來沒有被計算過，因為從來沒有人被要求去計算它。
合約管理，是企業價值外溢的主要出口之一。世界商務與合約協會（World Commerce & Contracting，前身為國際合約與商業管理協會IACCM，下稱WorldCC）以超過七百家企業的資料為基礎，研究結論是：合約管理失當平均使企業每年損失年營收的9.2%。麥肯錫在2018年的獨立研究中得出接近的9%數字，並指出若以《財富》全球五百強企業當年的營收規模試算，這個流失數字高達2.5兆美元。根據同一份研究，即便是管理最完善的企業，每年透過合約流失的價值仍超過年營收的6%。
合約處理本身的成本，讓問題再疊上一層。WorldCC的研究指出，一份基本合約從起草、談判到簽署的平均處理成本為6,900美元；中等複雜度合約平均21,300美元；高複雜度合約達49,000美元以上。EY的研究則發現，大型企業平均每週處理350份合約。在這樣的業務量級下，缺乏效率的人工合約流程絕非小事，而是一筆規模可觀的持續性營運支出。
還有找不到的合約所附帶的代價。《合約管理期刊》（Journal of Contract Management）的研究顯示，71%的企業無法找到至少10%的合約。找不到的合約，無從執行、無法主動議定續約條件、無法進行合規稽核，也無法讓業務部門掌握公司究竟做出了哪些承諾。在監管環境持續收緊的今天——亞洲各產業的法規都在加速收攏——一份在主管機關調查中提不出來的合約，不是行政疏漏，而是法律責任。
回到三個案例。B2C保險集團用三年評估CLM，遲遲未能決策，而每一年的延誤都是以年均9.2%持續外溢的合約價值。B2B科技公司花兩年打造了一套解決不了問題的系統，現在仍需另投時間和資源。B2B製造商在分析完成之前就送出了預算申請，拿到後來不夠用的核准金額，現在無法在缺乏當初就應建立的論證基礎下再度叩門。
每一個案例裡，不解決問題的代價都超過了正確解決方案的成本。不解決的代價是隱形的，分散在無數細小的效率耗損與機會成本裡；而解決方案的成本，則以需要審批的預算項目形式清晰呈現。三家企業都清楚CLM能解決問題——問題不在於是否需要導入，而在於沒有一家掌握了成功導入所需的方法。要理解為何三家都走向失敗，必須先釐清CLM導入究竟是什麼性質的工作——以及它不是什麼。
為什麼CLM不是採購決策
本文的三個案例並不罕見。Gartner估計，約50%的首次CLM導入無法達到預期效益。Onit在2022年的調查發現，77%的企業內部法律顧問曾親歷失敗的法律科技導入。這些不是技術層面的失敗——CLM市場已相當成熟，各價位都有功能完整的系統可供選擇。這些是方法論層面的失敗。
讓CLM導入成功的方法論，是法務營運——一個橫跨流程設計、科技導入、資料管理、供應商管理、財務管控與組織策略的獨立專業學科。法務營運提出的問題，和律師的問題本質不同：律師問的是法律立場為何，法務營運問的是這項法律工作如何執行、成本是多少、需要多長時間、有沒有更好的方式。多數亞洲企業之所以缺乏這個職能，原因是結構性的——法務團隊規模精簡、預算以法務費用而非企業投資的標準核定、職能長期被延後，因為從來沒有資源去建立它。外部環境正在改變這個局面：個人資料保護法制、AI治理框架、貿易合規義務，在亞洲各地快速收攏，本已吃緊的法務部門，無法在沒有基礎建設支撐的情況下繼續承接新增的監管議題。五年前尚可維持的基礎建設缺口，今天已然無法為繼。
CLM不是採購決策，而是一個法務營運專案。這個區別至關重要：採購決策的答案是評估系統、選定一套；法務營運專案的答案，需要在任何系統評估啟動之前，先完成一系列前置工作：
在能夠定義CLM需求之前，企業必須先清楚掌握自己在管理什麼。現有合約有多少份？涵蓋哪些類型？分散在哪些系統、以何種格式留存、由誰負責管理？各類型合約的年度處理量為何？現行簽核流程是什麼，各業務單位和地區之間是否一致？缺乏這份分析，企業就無法回答每一家供應商都會詢問的問題——而答案將因業務單位、地區和合約類型而異，直接制約可用的技術選項。這正是B2C保險集團在三年評估後仍無法選定系統的根本原因。若他們當初先完成這份分析，便會更早發現：該採購哪一套CLM，根本不是最應優先問的問題。
CLM系統將合約流程自動化。若那些流程本身尚未被梳理清楚——若企業對於一份合約如何從需求提出、起草、審查、簽核、執行、建檔到義務追蹤的完整路徑，缺乏清晰且獲得共識的圖像——系統就沒有可以自動化的對象。它只會將現有那套已然失靈的流程，在新介面裡重演一遍。第一個案例的結局，是在系統上線前未能完成流程梳理的可預期後果。
CLM系統能做的事很多，關鍵是企業實際需要哪些功能、依什麼優先順序、分哪些階段落地。需求定義是將合約版圖分析與流程梳理的成果，轉化為系統必須滿足的具體功能規格的過程。缺乏需求定義，供應商評估就淪為在沒有判斷標準的情況下比較功能清單，結果不是陷入選擇困難，就是選了展示最精彩的系統，而非最適合組織實際需求的系統。需求定義也是讓預算申請具備說服力的關鍵：一份需求文件能為數字提供脈絡，說明特定費用水準的必要性，讓管理層有所依據地評估取捨。
合約不是法務部門的專屬資產。它們由業務、採購、人資、財務和營運等部門發起，由法務審查，由主管簽核，由負責商業關係的人監督履行。一套只服務法務需求的CLM系統，不會獲得其他部門的採用。跨部門利害關係人整合——理解各職能對系統的需求，並將其納入設計——是法務營運的工作，而非法律工作本身。它需要引導協調的能力、組織層面的授權，以及執業律師在臨時指派的專案角色中通常不具備的跨部門公信力。
EY的研究發現，99%的企業缺乏改善合約流程所需的資料與技術能力，而60%正試圖推動全面性的轉型變革。兩組數字之間的落差，就是變革管理：將組織從現狀推進至新狀態，並讓轉變真正紮根的能力。把系統上線視為終點而非導入起點的CLM專案，幾乎無一例外地表現不佳。第二個案例中，B2C保險集團長達三年的評估，根本原因不是技術問題，而是在缺乏流程基礎與跨部門共識的情況下，試圖推動轉型的必然結果。
共同的癥結在於順序。三個案例的企業，都試圖在回答那些讓技術問題得以回答的前置問題之前，就直接跳向技術問題——我們應該採購哪一套CLM？法務營運的存在，正是為了回答那些前置問題。沒有法務營運，不會讓技術問題變得更容易回答，而是讓它根本無從回答。
為什麼CLM需要由最高層推動
第三個案例是三個案例中最值得深思的，因為它揭示了兩個容易混淆、實則截然不同的失敗。第一個是順序失敗：預算申請在支撐它所需的分析完成之前就送出去了。第二個是角色設計失敗：法務長被要求執行合約版圖分析、需求定義、供應商評估、商業可行性論證——這些工作超出法律專業的範疇，屬於法務營運作為獨立學科的職責範疇。這兩個失敗，都不反映法務長個人的問題；兩個都反映了一個從未定義CLM導入需要什麼、應由誰主導、應投入多少資源的組織。
CLM導入無法在一個本已資源不足、預算按法務費用規模而非企業投資規模設定、缺乏跨部門執行授權的法務部門內部推動。這些限制是真實的。預算不足。授權不夠。曾試圖提出這些問題、卻被要求「克服困難」的法務長，已學會了不再開口。
打破這個循環，需要一件法務部門自身無法提供的東西：最高管理層的明確認定——CLM是企業層級的投資，而不是法務部門的技術採購，因此需要企業層級的主導、預算和治理架構才能成功。
支持這個認定的財務論證是直接的。WorldCC的研究，將合約價值外溢定在年營收的9.2%。一家年營收新台幣六十億元的企業，每年很可能有近新台幣五點五億元透過合約管理失當而流失。一套正確導入、有法務營運支撐的CLM系統，不可能完整回收這個數字，但即便只回收其中一部分，也足以讓投資報酬率輕鬆超越投入成本。
這些論證，法務長在法務部門內部難以有效提出——因為它們涉及在財務、營運和風險管理的領域做出主張，而這些領域通常不被視為法務長的職權範疇。它們需要一位財務長或執行長，在獲得完整的財務分析之後，被要求就CLM作為企業投資做出決策。在CLM成功落地的企業裡，這個對話曾經發生——發生，是因為某位擁有足夠組織權威的人，決定了合約管理方式是一個業務問題，而不只是一個法律問題。
這篇文章，是一個開啟那個對話的邀請。
CLM落地後，看起來是什麼樣子
一套規劃周全、資源配置適當、以正確的法務營運基礎為支撐的CLM，不會以戲劇性的方式宣告自己的存在。改變體現在營運和財務層面，隨時間積累，而非以單一可見的轉型面貌出現。
合約找得到。不是立刻就能全部找到——建立合約庫需要時間，歷史合約的資料移轉既不快也不便宜。但在導入後的特定期間內，法務團隊與業務部門能夠找到一份合約、確認關鍵條款、核查到期日，並理解它所設定的履約義務。企業每年耗在追查和重建遺失合約上的成本，不會一夕消失，但它開始收縮。
法務團隊在提供法律顧問意見，而非處理行政庶務。當法律需求透過結構化的受理機制進入、依風險程度與複雜度進行分派，並導向適當的處理資源——無論是標準範本、AI輔助審查工具，還是資深律師——法務團隊的時間才真正被投入在需要法律判斷的工作上。那位花了兩年管理自己既未受訓、也不應被指派之CLM專案的律師，現在在做法律工作。那位因為沒有分派機制可用而親自審閱例行合約的法務長，現在有餘裕去做當初聘用他時所期待的策略性工作。
這種營運公信力——能夠及時交付、讓成本清晰可見、在問題發生前就主動處理——改變了組織其他部門看待法律職能的方式。而這種觀感的轉變，最終給了法務長一件單憑法律專業無法換來的東西：在業務決策桌上的一席之地。
坐在那個位置的法務長，不是因為組織碰巧遇上了一位特別有商業眼光的律師。那個位置，是整個職能爭取來的。財務長信任法律費用的數字，因為那些數字被追蹤、被解釋。執行長在策略決策上諮詢法務長，因為法務的意見能夠及時到位，以能夠提供決策依據、而非造成延誤的形式呈現。一套被視為企業基礎建設、而非法務部門技術採購的CLM——正確導入之後——讓這一切成為可能。
在供應商展示之前：三個問題
對多數正在閱讀本文的亞洲企業而言，正確的起點不是選擇CLM供應商，而是回答三個讓供應商選擇成為可能的問題——也是讓預算申請在送出時站得住腳的問題。多數企業目前的實況是：合約靠試算表和共用硬碟管理，沒有結構化的法律需求受理機制，也沒有系統性的合約義務追蹤。這不是批評，而是多數組織在起步之前的現實狀況。問題不在於要不要開始，而在於如何開始。
不是你以為的樣子——而是它實際的樣子，涵蓋每個業務單位、每個地區、每套目前存放合約的系統。這份分析需要時間，產出的發現往往令人不自在。那種不自在，正是有用的資訊。三年評估不出結論的B2C保險集團，從未做過這份分析。若他們做了，便會更早發現：應該採購哪一套CLM，根本就不是最優先要問的問題。
這是B2B製造商從未試算的數字——而它的缺席，讓他第二次與財務長的對話從一開始就無從進行。計算本身並不複雜，但需要有人去執行。將WorldCC的9.2%套用到年營收上；將WorldCC的合約處理成本估算套用到年度合約量上。得出的數字不精確，但方向是正確的——而它，正是讓商業可行性論證成為可能的那個數字。
CLM導入需要跨部門授權、規模相稱的預算，以及法務長層級以上的組織支持。如果「由誰負責」的答案是「法務長指派的那位律師」，這個專案將得出與本文三個案例相同的結果。如果答案是「財務長與法務長共同主責、董事會知情、預算規模反映問題的實際成本」，這個專案才有可以落地的基礎。
這三個問題，是真正的起點。以適當的專業能力在場，誠實地回答它們，是在任何CLM評估、任何供應商展示、任何採購決策之前必須完成的工作。這正是本文三個案例在開始之前都沒有做的事。
必須發生的對話
三家企業，七年累計的努力，零套系統落地。合約依然難找，流程依然壅塞，代價依然持續累積。
本文的論點不是CLM難以導入，而是CLM所面臨的困難，和多數組織準備好去面對的困難不同。這不是技術選型問題——技術早已成熟，各價位都有具備實力的系統可供選擇。這是一個組織問題：一個需要前置分析、跨部門整合、規模相稱的預算，以及在多數組織架構中超出法務長職權範圍的決策授權的專案。本文三家企業的失敗，不是因為選錯了系統、也不是因為市場上沒有好的供應商，而是因為在回答組織層面的問題之前，就試圖回答技術層面的問題。
讓CLM真正落地，需要把它當成它本來的樣子：一項企業投資，由組織中有足夠授權的層級主導，能夠承諾資源、指定跨部門責任歸屬，並確保導入工作按正確的順序推進。亞洲那些成功導入CLM的企業，之所以成功，不是因為找到了更好的供應商、也不是因為編列了更多預算，而是因為組織中某個層級夠高的人，決定了合約管理方式是一個值得認真回答的業務問題。
那個決定，是起點。其他的，都從那裡展開。
本文僅供參考，不構成法律建議。文中所述監管情況及市場數據反映截至發布日期之公開資訊，相關內容可能隨時變動。讀者在依據本文資訊採取或放棄任何行動前，應尋求適當的專業意見。CloudVista Consulting LLC對因依賴本文而造成的任何損失或損害概不承擔責任。