[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article:contract-one-vision":3},{"meta":4,"markdown":151},{"type":5,"articleId":6,"slug":6,"title":7,"titleEn":8,"category":9,"summary":10,"publishedAt":11,"image":12,"vocabulary":13,"source":148},"article","contract-one-vision","契約書を\"意思決定のインフラ\"に──Contract Oneで挑む、新たな価値創造","Turning contracts into \"decision-making infrastructure\" — Creating new value with Contract One","software\u002Fcompanies\u002Fsansan","The new head of Contract One Engineering Unit explains his vision: transforming contracts from static documents into decision-making infrastructure through data structuring, AI-driven utilization, and 10x developer productivity.","2026-04-26T00:00:00Z","https:\u002F\u002Fimages.yamiyomi.com\u002Fcontract-one-vision.png",[14,19,24,28,32,36,40,44,48,52,56,60,64,68,72,76,80,84,88,92,96,100,104,108,112,116,120,124,128,132,136,140,144],{"word":15,"reading":16,"meaning":17,"level":18},"立ち上げ","たちあげ","launch, establishment","N2",{"word":20,"reading":21,"meaning":22,"level":23},"非構造化","ひこうぞうか","unstructured","N1",{"word":25,"reading":26,"meaning":27,"level":23},"構造化","こうぞうか","structuring, structured",{"word":29,"reading":30,"meaning":31,"level":18},"活用","かつよう","utilization, practical use",{"word":33,"reading":34,"meaning":35,"level":18},"異動","いどう","transfer (job)",{"word":37,"reading":38,"meaning":39,"level":23},"本質的","ほんしつてき","essential, fundamental",{"word":41,"reading":42,"meaning":43,"level":18},"方向性","ほうこうせい","direction, orientation",{"word":45,"reading":46,"meaning":47,"level":18},"意思決定","いしけってい","decision-making",{"word":49,"reading":50,"meaning":51,"level":23},"締結","ていけつ","conclusion (of a contract)",{"word":53,"reading":54,"meaning":55,"level":23},"軌跡","きせき","trajectory, track record",{"word":57,"reading":58,"meaning":59,"level":18},"手段","しゅだん","means, measure",{"word":61,"reading":62,"meaning":63,"level":18},"提供","ていきょう","provision, offering",{"word":65,"reading":66,"meaning":67,"level":23},"慣習","かんしゅう","custom, convention",{"word":69,"reading":70,"meaning":71,"level":18},"特有","とくゆう","unique, peculiar to",{"word":73,"reading":74,"meaning":75,"level":18},"関係性","かんけいせい","relationship, relatedness",{"word":77,"reading":78,"meaning":79,"level":23},"文脈","ぶんみゃく","context",{"word":81,"reading":82,"meaning":83,"level":18},"領域","りょういき","domain, area",{"word":85,"reading":86,"meaning":87,"level":23},"高精度","こうせいど","high precision",{"word":89,"reading":90,"meaning":91,"level":23},"自然言語処理","しぜんげんごしょり","natural language processing",{"word":93,"reading":94,"meaning":95,"level":18},"視覚","しかく","visual, vision",{"word":97,"reading":98,"meaning":99,"level":23},"活路","かつろ","way out, breakthrough",{"word":101,"reading":102,"meaning":103,"level":18},"拡張","かくちょう","extension, expansion",{"word":105,"reading":106,"meaning":107,"level":23},"都度","つど","each time, whenever",{"word":109,"reading":110,"meaning":111,"level":18},"記載","きさい","entry, description",{"word":113,"reading":114,"meaning":115,"level":18},"類似","るいじ","similarity, resemblance",{"word":117,"reading":118,"meaning":119,"level":18},"横断","おうだん","cross-cutting, spanning",{"word":121,"reading":122,"meaning":123,"level":18},"生産性","せいさんせい","productivity",{"word":125,"reading":126,"meaning":127,"level":18},"本格的","ほんかくてき","full-scale, genuine",{"word":129,"reading":130,"meaning":131,"level":18},"主体","しゅたい","initiative, lead",{"word":133,"reading":134,"meaning":135,"level":18},"企画","きかく","planning, project",{"word":137,"reading":138,"meaning":139,"level":23},"圧倒的","あっとうてき","overwhelming, dominant",{"word":141,"reading":142,"meaning":143,"level":18},"体制","たいせい","structure, system, regime",{"word":145,"reading":146,"meaning":147,"level":18},"構築","こうちく","construction, building (a system)",{"name":149,"url":150},"Sansan Builders Box","https:\u002F\u002Fbuildersbox.corp-sansan.com\u002Fentry\u002F2025\u002F09\u002F01\u002F120000","\n::para\nこんにちは、Contract One Engineering Unitの[大島]{おおしま:Oshima (surname):N2}です。このたび、Contract One Engineering Unitの[立ち上げ]{たちあげ:launch, establishment:N4}に[伴い]{ともない:accompanying:N1}、[部長]{ぶちょう:department head:N3}としてジョインしました。これまで[私]{わたし:I:N4}は[研究]{けんきゅう:research:N4}[開発]{かいはつ:development:N4}[部]{ぶ:department:N3}の[部長]{ぶちょう:department head:N3}として、また[時]{とき:time:N5}にはSansan Engineering Unitの[副]{ふく:vice-:N2}[部長]{ぶちょう:department head:N3}として[非]{ひ:non-:N3}[構造化]{こうぞうか:structuring:N2}データを[構造化]{こうぞうか:structuring:N2}し、[意味]{いみ:meaning:N4}のあるデータとして[活用]{かつよう:utilization:N3}するための[技術]{ぎじゅつ:technology:N2}[開発]{かいはつ:development:N4}に[取り組んで]{とりくんで:to work on:N3}きました。\n\n#en\nHello, I'm Oshima from the Contract One Engineering Unit. I've joined as department head alongside the launch of the Contract One Engineering Unit. Until now, I served as head of the R&D department, and at times as vice-head of the Sansan Engineering Unit, working on technology development to structure unstructured data and utilize it as meaningful data.\n::\n\n::heading\nなぜ[私]{わたし:I:N4}がContract Oneに「[行こう]{いこう:let's go:N5}」と[思った]{おもった:thought:N4}のか\n\n#en\nWhy I decided to \"go\" to Contract One\n::\n\n::para\n[私]{わたし:I:N4}がContract Oneへの[異動]{いどう:transfer:N1}の[話]{はなし:discussion:N5}をもらったとき、[真っ先]{まっさき:first of all:N4}に[思った]{おもった:thought:N4}のは「このプロダクトには、[自分]{じぶん:oneself:N4}のこれまでの[経験]{けいけん:experience:N3}が[生かせる]{いかせる:can put to use:N5}」ということでした。Contract Oneの[成長]{せいちょう:growth:N3}を[支える]{ささえる:to support:N3}[鍵]{かぎ:key:N1}は[以下]{いか:the following:N4}の2つだと[考えて]{かんがえて:thinking:N4}います。[契約]{けいやく:contract:N1}データのSSoT[化]{か:-ification:N3}、そのデータをあらゆる[方法]{ほうほう:method:N3}で[活用]{かつよう:utilization:N3}[可能]{かのう:possible:N3}にすること。[本質的]{ほんしつてき:essentially:N4}には[同じ]{おなじ:same:N4}ことです。[詳細]{しょうさい:details:N1}を[理解]{りかい:understanding:N3}するにつれ、[目指す]{めざす:to aim for:N3}[方向性]{ほうこうせい:direction:N3}がクリアにイメージできたことを[覚えて]{おぼえて:to remember:N3}います。\n\n#en\nWhen I received the offer to transfer to Contract One, the first thing I thought was \"I can put my experience to use in this product.\" I believe the two keys to Contract One's growth are: making contract data the Single Source of Truth (SSoT), and making that data usable through every possible method. Essentially, this is the same thing I've always done. As I understood the details, I remember clearly envisioning the direction we were aiming for.\n::\n\n::heading\n[目指す]{めざす:to aim for:N3}ものは「[意思]{いし:will:N4}[決定]{けってい:decision:N3}のインフラ」\n\n#en\nWhat we aim for: \"decision-making infrastructure\"\n::\n\n::para\nContract Oneは、[契約書]{けいやくしょ:contract document:N1}を[単に]{たんに:simply, merely:N3}[管理]{かんり:management:N2}するためのツールではありません。[私]{わたし:we:N4}たちが[目指して]{めざして:aiming for:N3}いるのは、[契約書]{けいやくしょ:contract document:N1}という\"[意思]{いし:will, intention:N4}[決定]{けってい:decision:N3}の[集まり]{あつまり:collection:N4}\"をSingle Source of Truth（SSoT）として[整理]{せいり:organize:N1}し、それをあらゆる[手段]{しゅだん:means:N3}で[再]{さい:re-:N2}[活用]{かつよう:utilization:N3}できるようにするということです。[企業]{きぎょう:enterprise:N1}が[何]{なに:something:N5}かを[決める]{きめる:to decide:N3}とき、[背景]{はいけい:background:N3}には[必ず]{かならず:always:N3}[契約]{けいやく:contract:N1}があります。その[契約]{けいやく:contract:N1}が、どういった[文脈]{ぶんみゃく:context:N1}で、どんな[条件]{じょうけん:conditions:N1}のもとに[締結]{ていけつ:conclusion (of a contract):N1}されたのか──その[意思]{いし:will:N4}[決定]{けってい:decision:N3}の[軌跡]{きせき:trajectory, track record:N1}をしっかりデータとして[残し]{のこし:to leave behind:N3}、そのデータを[活用]{かつよう:utilization:N3}する[手段]{しゅだん:means:N3}を[提供]{ていきょう:provide:N1}する。\n\n#en\nContract One is not simply a tool for managing contracts. What we are aiming for is to organize contracts — which are a \"collection of decisions\" — as a Single Source of Truth (SSoT), and make them reusable through every possible means. Behind every decision a company makes, there is always a contract. Under what context and conditions was that contract concluded? We aim to firmly preserve that trajectory of decision-making as data, and provide the means to utilize it.\n::\n\n::heading\n[契約書]{けいやくしょ:contract document:N1}を「[意思]{いし:will:N4}[決定]{けってい:decision:N3}のSSoT」に[変える]{かえる:to change:N3}\n\n#en\nTurning contracts into the \"SSoT of decision-making\"\n::\n\n::para\n[契約書]{けいやくしょ:contract document:N1}は、PDFや[紙]{かみ:paper:N4}、[電子]{でんし:electronic:N5}[契約]{けいやく:contract:N1}など、さまざまな[形式]{けいしき:format:N3}で[存在]{そんざい:to exist:N3}し、[内容]{ないよう:content:N3}も[非常に]{ひじょうに:extremely:N3}[多様]{たよう:diverse:N3}です。[中]{なか:among:N5}には、[業界]{ぎょうかい:industry:N4}ごとの[慣習]{かんしゅう:custom, convention:N3}や[会社]{かいしゃ:company:N4}[特有]{とくゆう:unique, peculiar:N4}の[表現]{ひょうげん:expression:N3}も[多く]{おおく:many:N4}[含まれて]{ふくまれて:to be included:N2}います。[契約書]{けいやくしょ:contract document:N1}を[使える]{つかえる:usable:N4}データにするには[構造]{こうぞう:structure:N2}・[関係性]{かんけいせい:relationships:N3}・[文脈]{ぶんみゃく:context:N1}をしっかり[理解]{りかい:understand:N3}した[上]{うえ:upon:N5}でデータ[化]{か:-ification:N3}するということが[重要]{じゅうよう:important:N3}です。\n\n#en\nContracts exist in various formats — PDF, paper, electronic contracts, and more — and their content is extremely diverse. They often include industry-specific conventions and company-specific expressions. To turn contracts into usable data, it is crucial to digitize them only after thoroughly understanding their structure, relationships, and context.\n::\n\n::para\n[非]{ひ:non-:N3}[構造化]{こうぞうか:structuring:N2}データを[構造化]{こうぞうか:structuring:N2}されたデータにすることは、Sansanが[長年]{ながねん:many years:N5}[取り組んで]{とりくんで:to work on:N3}きた[領域]{りょういき:domain, area:N2}であり、Sansanの[強み]{つよみ:strength:N4}となる[部分]{ぶぶん:part:N3}です。[私]{わたし:I:N4}は[研究]{けんきゅう:research:N4}[開発]{かいはつ:development:N4}[部]{ぶ:department:N3}[時代]{じだい:era, period:N4}、その[強み]{つよみ:strength:N4}をさらに[高める]{たかめる:to enhance:N5}べく、[高]{こう:high:N5}[精度]{せいど:precision:N3}のOCR[技術]{ぎじゅつ:technology:N2}や[自然]{しぜん:natural:N3}[言語]{げんご:language:N4}[処理]{しょり:processing:N3}の[技術]{ぎじゅつ:technology:N2}の[開発]{かいはつ:development:N4}に[取り組んで]{とりくんで:to work on:N3}きました。[研究]{けんきゅう:research:N4}[開発]{かいはつ:development:N4}[部]{ぶ:department:N3}で[開発]{かいはつ:development:N4}した[視覚]{しかく:visual:N1}[言語]{げんご:language:N4}モデル「Viola」はその[一例]{いちれい:one example:N3}です。\n\n#en\nTurning unstructured data into structured data is a domain Sansan has worked on for many years, and it is one of Sansan's core strengths. During my time in the R&D department, I worked on developing high-precision OCR technology and natural language processing technology to further enhance that strength. The visual-language model \"Viola,\" developed in the R&D department, is one such example.\n::\n\n::heading\n[意思]{いし:will:N4}[決定]{けってい:decision:N3}データの[利]{り:use:N3}[活用]{かつよう:utilization:N3}を[推進]{すいしん:promote:N1}する\n\n#en\nPromoting the utilization of decision-making data\n::\n\n::para\nデータベースがどれだけ[優れて]{すぐれて:excellent:N3}いても、そのデータを[使い]{つかい:use:N4}やすい[形]{かたち:form:N3}で[提供]{ていきょう:provide:N1}できなければ[意味]{いみ:meaning:N4}がありません。Contract OneはAI[活用]{かつよう:utilization:N3}にデータ[利]{り:use:N3}[活用]{かつよう:utilization:N3}の[活路]{かつろ:way out, breakthrough:N3}を[見出しました]{みいだしました:discovered:N5}。[例えば]{たとえば:for example:N3}「[拡張]{かくちょう:extension:N1}[項目]{こうもく:item, field:N1}のAI[自動]{じどう:automatic:N4}[入力]{にゅうりょく:input:N4}」をリリースしたことで、[契約書]{けいやくしょ:contract document:N1}から[都度]{つど:each time:N3}[記載]{きさい:description, entry:N1}[箇所]{かしょ:section, location:N1}を[探す]{さがす:to search for:N3}といった[手間]{てま:effort, trouble:N4}が[必要]{ひつよう:necessary:N3}なくなりました。[今後]{こんご:from now on:N5}も[自然]{しぜん:natural:N3}[言語]{げんご:language:N4}で[契約]{けいやく:contract:N1}[内容]{ないよう:content:N3}を[検索]{けんさく:search:N1}したり、[企業]{きぎょう:enterprise:N1}[横断]{おうだん:cross-cutting:N3}での[類似]{るいじ:similar:N3}[契約]{けいやく:contract:N1}の[発見]{はっけん:discovery:N4}を[支援]{しえん:support:N1}したりと、[生成]{せいせい:generative:N3}AIの[力]{ちから:power:N4}が[大きく]{おおきく:greatly:N5}[生きる]{いきる:to be useful:N5}[場面]{ばめん:scene, situation:N3}が[多数]{たすう:many:N3}[出て]{でて:to appear:N5}きます。\n\n#en\nNo matter how excellent a database is, it's meaningless if the data cannot be provided in an easy-to-use form. Contract One found a breakthrough in data utilization through AI. For example, by releasing \"AI auto-fill for extended fields,\" users no longer need to manually search for specific entries in contract documents each time. Going forward, there will be many situations where generative AI proves its value — such as searching contract content in natural language or supporting the discovery of similar contracts across companies.\n::\n\n::heading\nAI-Driven[開発]{かいはつ:development:N4}で[生産性]{せいさんせい:productivity:N3}を10[倍]{ばい:times:N2}にする\n\n#en\nAchieving 10x productivity with AI-driven development\n::\n\n::para\nContract Oneには[意思]{いし:will:N4}[決定]{けってい:decision:N3}のインフラになるためのピースが[揃って]{そろって:to be in order:N1}います。しかし、スピードなくして[事業]{じぎょう:business:N4}[成長]{せいちょう:growth:N3}を[支える]{ささえる:to support:N3}ことはできません。Contract Oneの[事業]{じぎょう:business:N4}[成長]{せいちょう:growth:N3}を[支える]{ささえる:to support:N3}には2[倍]{ばい:times:N2}、いや[近い]{ちかい:near:N4}[将来]{しょうらい:future:N2}10[倍]{ばい:times:N2}の[生産性]{せいさんせい:productivity:N3}が[必要]{ひつよう:necessary:N3}になります。[現在]{げんざい:currently:N3}、[私]{わたし:we:N4}たちはAI[主体]{しゅたい:initiative, lead:N4}の[開発]{かいはつ:development:N4}プロセス[構築]{こうちく:building:N2}に[本格的]{ほんかくてき:full-scale:N3}に[取り組んで]{とりくんで:to work on:N3}います。これはコーディング[部分]{ぶぶん:part:N3}を[単に]{たんに:simply:N3}AI[化]{か:-ification:N3}するだけではなく、[企画]{きかく:planning:N1}、デザインなどすべてのフェーズをAI[主体]{しゅたい:lead:N4}にしていくという、チャレンジングな[取り組み]{とりくみ:initiative:N3}です。\n\n#en\nContract One has all the pieces needed to become decision-making infrastructure. However, without speed, we cannot support business growth. Supporting Contract One's business growth requires 2x — no, in the near future 10x — productivity. Currently, we are earnestly building AI-driven development processes. This is not simply about automating the coding portion with AI, but a challenging initiative to make AI the lead across all phases including planning and design.\n::\n\n::para\n[目指して]{めざして:aiming for:N3}いるのは、10[倍]{ばい:times:N2}の[生産性]{せいさんせい:productivity:N3}です。AIの[力]{ちから:power:N4}を[最大限]{さいだいげん:maximum:N3}に[活用]{かつよう:utilization:N3}しながら、[圧倒的]{あっとうてき:overwhelming:N2}なスピードで[価値]{かち:value:N1}を[届ける]{とどける:to deliver:N2}[体制]{たいせい:structure, system:N3}を[築いて]{きずいて:to build:N2}いきます。\n\n#en\nWhat we are aiming for is 10x productivity. While leveraging AI to the fullest, we will build a structure that delivers value at overwhelming speed.\n::\n"]