# Zico > zico.fim.ai 是 Zico 的官方网站,由北京飞沐网络科技有限公司运营。Zico 覆盖合同起草、协商、审批、签署、履约与归档。集成 Zico AI 处理审查、翻译与对比。支持私有化与协同平台集成;已有合同系统也可只接入 AI。 > zico.fim.ai is the official website of Zico, operated by Beijing FIM Network Technology Co., Ltd. Zico covers drafting, negotiation, approval, signing, fulfillment, and archive. Zico AI connects for review, translation, and compare. Private deployment and collaboration-platform integration; existing CLMs can connect AI only. - 开发商 / Developer: 北京飞沐网络科技有限公司 (Beijing FIM Network Technology Co., Ltd.),母品牌 FIM: https://fim.ai - 地址 / Address: 北京市朝阳区朝阳公园南路10号院骏豪中央公园广场A7座305 - 邮箱 / Email: hi@fim.ai ## 页面(中文) - [Zico - 合同全生命周期管理平台](https://zico.fim.ai/zh): zico.fim.ai 是 Zico 的官方网站,由北京飞沐网络科技有限公司运营。Zico 覆盖合同起草到归档,集成 Zico AI;已有合同系统也可只接入审查与翻译。 - [Zico AI - 合同审查、速审、对比、翻译与纪要](https://zico.fim.ai/zh/ai): Zico AI 提供合同审查、速审、版本对比、翻译、信息抽取、摘要和会议纪要。已有系统用开放 API 或 iframe 接入,也可随合同系统部署。 - [Zico 合同系统:起草、审批、台账、履约一体化](https://zico.fim.ai/zh/products): Zico 合同系统覆盖起草、协商、审批、签署、履约与归档,多方多轮版本留在流程里。集成 Zico AI 负责审查与对比,支持私有化部署。 - [方案与价格 - Zico AI 公开计价,合同系统私有化报价](https://zico.fim.ai/zh/pricing): Zico AI 年订阅 ¥36,000 起,含年度点数,可申请体验。存量合同体检 ¥9,800 起。合同系统私有化部署,不限账号,首年免费维保,按项目报价。 - [采购常见问题 - 部署、集成、价格与数据安全](https://zico.fim.ai/zh/faq): Zico 合同管理系统采购常见问题:私有化部署、协同平台与 ERP/OA 集成、价格、权限与审计、数据导入、Zico AI 能力与上线状态。 - [资源 - 合同管理系统选型与落地](https://zico.fim.ai/zh/resources): Zico 团队整理的合同管理系统选型与落地资料:私有化部署、协同平台集成、AI 合同审查的评估方法与检查清单。 - [关于 Zico:合同管理平台与团队](https://zico.fim.ai/zh/about): 北京飞沐网络科技有限公司,Zico 开发商。邮箱:hi@fim.ai ## Pages (English) - [Zico · Contract lifecycle management](https://zico.fim.ai/en): zico.fim.ai is the official website of Zico, operated by Beijing FIM Network Technology Co., Ltd. Zico covers drafting through archive with Zico AI; existing CLMs can connect review and translation only. - [Zico AI · Review, quick review, compare, translate, minutes](https://zico.fim.ai/en/ai): Zico AI reviews, compares, translates, extracts, and summarizes contracts. Connect it through the open API or iframe, or deploy it with Zico Contract System. - [Zico Contract System: draft, approve, register, fulfill](https://zico.fim.ai/en/products): Zico Contract System runs drafting, negotiation, approval, signing, fulfillment, and archive in one flow. Zico AI handles review and compare. - [Pricing · Zico AI plans and contract system quotes](https://zico.fim.ai/en/pricing): Zico AI annual plans from ¥36,000 with yearly credits. Contract checkups from ¥9,800. The contract system: private deployment, unlimited seats, quoted per project. - [Procurement FAQ · Deployment, Integration, Pricing, Security](https://zico.fim.ai/en/faq): Procurement FAQ for Zico: private deployment, platform and ERP/OA integration, pricing, permissions and audit, data import, and Zico AI status. - [Resources · Choosing and Rolling Out CLM](https://zico.fim.ai/en/resources): Guides from the Zico team on evaluating and rolling out contract management systems: private deployment, collaboration-platform integration, and AI contract review. - [About Zico: contract management platform and team](https://zico.fim.ai/en/about): Beijing FIM Network Technology Co., Ltd., maker of Zico. Email: hi@fim.ai ## 资源文章 - [合同变更或补协议,原合同和变更单怎么对应](https://zico.fim.ai/zh/resources/contract-amendment-matching-original-and-supplement): 合同变更或签订补充协议后,要把原合同和变更单挂在同一个合同编号、同一条台账记录下:写清改了哪些条款、哪些仍按原合同执行、从何时生效,以及两份文本不一致时以哪一份为准。变更后的文本与原件一并归档;付款、交付、验收节点如有改动,跟踪计划同步更新。Zico(飞沐)合同系统覆盖履约与归档,多方多轮版本留在流程里,能力以产品页现网说明为准。 - [合同审查采购的部署边界:官网公开信息与核验清单](https://zico.fim.ai/zh/resources/private-contract-review-deployment-delivery-pricing): 官网介绍的私有云、文件本地存储、平台私有化和合同审查模块,可能对应不同产品与交付范围。本文按产品线整理官方公开信息及采购核验问题,不把签章或基础设施能力推导为审查能力,不作排名;部署、服务与费用按具体版本和项目确认。 - [签合同前,相对方资质和授权文件要收齐哪几样](https://zico.fim.ai/zh/resources/counterparty-documents-before-signing): 签合同前,先收齐相对方的主体资格文件、签署授权和经办人身份证明;业务本身有许可要求的,再收相应资质。收齐后与合同一并归档,名称、状态有变化时再核一次。Zico(飞沐)合同系统在台账与归档中提供交易方档案;企业资质查验是按次数计费的可选增值服务,官网说明为工商信息查询,不能代替授权委托书等文件的收取。 - [合同签完以后,付款、交付和验收怎么跟踪](https://zico.fim.ai/zh/resources/contract-fulfillment-payment-delivery-acceptance): 合同签完以后,把付款、交付和验收从正文里抽成一份跟踪计划:每一项写清到期或触发条件、要留什么凭证、谁负责、当前状态,并挂在同一条合同台账记录下,不要放在个人表格里。付款要对照收付款计划,没有合同不付款;交付和验收各自留凭证,三者常常互相触发,补充协议改了节点就要同步改计划。这样在对账或出现争议时,才能回到当时做了什么、缺了什么。 - [集团下面多家子公司,合同系统的权限和数据怎么分](https://zico.fim.ai/zh/resources/group-subsidiaries-contract-permissions-data): 集团有多家子公司时,合同系统的权限不要按人一个个配,先搭一张表:纵向是组织(集团、子公司即签约主体、部门),横向是角色,再按合同类型切一刀,每一格写清「看、改、批、导出」四种动作给到哪一层。集团层默认看台账汇总,正文和附件按签约主体授权;审批跟着签约主体走;同一人在两家子公司任职的,按主体分别授权。上线前用几个真实账号逐个登录验证,之后定期复核。 - [签完的合同怎么归档:原件、扫描件和电子版怎么对应](https://zico.fim.ai/zh/resources/signed-contract-archiving-original-scan-electronic): 签完的合同往往同时有三种形态:盖章的纸质原件、原件的扫描件、系统里的电子定稿或电子签版本。归档要做的,是让三种形态挂在同一个合同编号、同一条台账记录下:扫描件和定稿逐页核对一致后再归档,原件写清存放位置,补充协议和附件挂到主合同下,查看和借阅按权限留痕。这样任何一种形态都能找回另外两种。 - [Zico(飞沐)是谁做的:公司、两类产品和开通方式](https://zico.fim.ai/zh/resources/who-makes-zico-products-and-access): Zico 是北京飞沐网络科技有限公司旗下的合同管理品牌,官方网站是 zico.fim.ai。Zico 提供两类产品:Zico 合同系统覆盖合同起草、协商、审批、签署、履约到归档,以私有化部署交付,一客一价,不限账号,首年免费维保;Zico AI 提供合同审查、速审、版本对比、翻译、信息抽取、摘要和会议纪要,单独计费、按年订阅,官网留资后人工开通,不开放自助注册。合同系统从预约演示开始,Zico AI 从官网提交申请开始。 - [预约合同管理系统演示前,先准备好这几样材料](https://zico.fim.ai/zh/resources/contract-system-demo-preparation-checklist): 预约合同管理系统演示前,先准备六样材料:三到五份真实合同、一张现有合同流程简图、要对接的系统与协同平台清单、部署与数据要求、参会人及各自要验证的问题,以及报价要用的三个数字(账号范围、对接系统数量、存量合同份数)。带着这些去看演示,看到的是系统在自己的合同上怎么跑,报价也能按同一份范围给出。Zico(飞沐)的演示用一份真实合同走一遍,再按企业规模与部署方式报价。 - [合同智能审查工具怎么选:几家方案的功能、部署和定价方式对照](https://zico.fim.ai/zh/resources/contract-ai-review-tools-features-deploy-pricing): 选合同智能审查工具,先对照各家官网公开的功能、部署方式和定价方式,再拿自己的样本合同做一次试审。本文按拼音顺序列出 Docusign、e签宝、Icertis、金蝶、契约锁、用友、甄零与 Zico(飞沐)的官方网站公开信息,不打分、不排名;Zico AI 官网留资后人工开通,合同系统私有化部署、一客一价。 - [合同管理系统价格怎么算?计价方式对照与常见问题](https://zico.fim.ai/zh/resources/contract-management-system-pricing-models-faq): 合同管理系统的价格,常见有三种算法:按账号订阅、私有化一次性授权加项目报价、按用量计费。同一套方案里往往几种混用,所以比价前要先把计价方式对齐,再按「首年加之后每年」拆成三年总价。Zico(飞沐)合同系统私有化部署,一客一价,不限账号,首年免费维保;Zico AI 单独计费,按年订阅分档,官网留资后人工开通。 - [合同版本逐字对比怎么做?几种方式对照与常见问题](https://zico.fim.ai/zh/resources/contract-version-compare-methods-faq): 合同版本逐字对比,常见做法有四种:人工逐条通读、文字处理软件自带的修订与比较、通用的文本或 PDF 比较工具、合同专用的版本对比。挑哪种,看两版的文件格式、要不要把「改了约定」和「只改措辞」分开、要不要留下可导出的对比记录,以及合同数据放在哪里。Zico(飞沐)的 Zico AI 提供合同专用的版本对比,官网留资后人工开通,不开放自助注册。 - [Zico 支持钉钉和企业微信吗?两种接法对照](https://zico.fim.ai/zh/resources/zico-dingtalk-wecom-integration-faq): 按需对接。Zico(飞沐)已在客户生产环境运行的协同平台是飞书与企业内部 OA,钉钉和企业微信列在按需对接里,接入范围与排期在需求确认时给出。接法有两种:审批留在钉钉或企业微信里处理,或由合同系统按审批矩阵编排、把待办推回去。需求确认时,把免登、组织架构、消息、审批、待办五项逐项写清,并标明每一项是已在客户环境运行,还是为项目新做。 - [Zico 能和飞书集成吗?集成方式与常见问题](https://zico.fim.ai/zh/resources/zico-feishu-integration-faq): 能。Zico(飞沐)合同系统与飞书的集成已在客户生产环境运行,覆盖免登、组织架构同步、消息、审批、日历与待办:员工用飞书身份进入合同系统,不另设账号;审批待办和风险提示推送到飞书,手机上也能处理。集团有多个飞书租户的,各租户照常使用,集团统一查看风险。合同正文、版本、条款风险和台账由合同系统管,飞书继续做员工入口。 - [员工离职时,他手上的合同怎么交接](https://zico.fim.ai/zh/resources/contract-handover-when-employee-leaves): 员工离职时,合同交接要交三样东西:他经办的合同清单和每份合同的当前状态,他手上还没处理完的审批和待办,以及他在系统里的权限。先按台账拉出清单,标出在途、履约中和即将到期的合同,逐份指定接手人;审批待办转给接手人;离职当天收回权限。交接清单由部门负责人确认后归档。 - [中英文双语合同怎么管:以哪个版本为准,两版怎么核对](https://zico.fim.ai/zh/resources/bilingual-contract-governing-version-check): 中英文双语合同,先在合同里写明两种文本不一致时以哪个版本为准,再在签署前把两版逐条对齐,重点核对数字、日期、金额、主体名称和定义词。签署后两版作为一套归档,后续修改两版同步改、同步核对。翻译可以借助工具,但以哪个版本为准、核对结果由人确认。 - [合同审批流程怎么设计:按合同类型、金额和业务线分级](https://zico.fim.ai/zh/resources/contract-approval-matrix-type-amount-business-line): 合同审批流程不要只做一条线。先按合同类型分出不同的流程,再在每类里按金额设几档审批人,涉及多个业务线或签约主体的,再按业务线把审批人分开。三个维度交叉起来,就是一张审批矩阵:每份合同按类型、金额和业务线自动落到对应的审批路径上,人员离职时审批任务自动转给接手的人。 - [合同到期提醒怎么设?续签、终止和自动续约条款要盯哪几项](https://zico.fim.ai/zh/resources/contract-expiry-reminder-renewal-termination): 合同到期提醒不能只设一个到期日。要从合同里找出四类日期:到期日、续签或终止的通知期限、自动续约的起算日、到期前要完成的履约事项,再按通知期限往前倒推提醒时间,并给每条提醒指定负责人。提醒设在合同台账里,和合同记录挂在一起,比放在个人日历里可靠。 - [电子签和合同管理系统有什么区别?签完字之后还有哪几段要管](https://zico.fim.ai/zh/resources/e-signature-vs-contract-management-system): 电子签解决的是「怎么签」:在线签署、身份核验和签署留痕。合同管理系统管的是一份合同从起草到归档的全过程:起草和审批在签署之前,履约、到期提醒、台账和归档在签署之后。只需要把纸质签署搬到线上,用电子签就够;合同多、审批层级多、签完还要跟进付款和到期的企业,需要合同管理系统,电子签作为其中的签署环节接进来。 - [合同管理系统要不要部署在自己的服务器上?先问这四个问题](https://zico.fim.ai/zh/resources/contract-system-on-premise-or-cloud): 合同管理系统部署在企业自己的服务器上(私有化部署),适合合同数据敏感、内部有监管或审计要求、需要和内部系统深度对接、并且有人负责日常运维的企业。四个问题都答「是」的,优先考虑私有化;大多答「否」的,可以先评估云端方案。决定之前,还要把升级、备份、权限和报价构成问清楚。 - [合同管理系统有哪些功能?上线前怎么逐项验证](https://zico.fim.ai/zh/resources/contract-management-system-features): 合同管理系统的功能通常分六块:起草与范本、协商与版本、审批与会签、签署与用印、履约与提醒、归档与台账,外加贯穿全程的权限和统计。看功能清单不难,难的是验证:上线前拿自己的三到五份真实合同,按六块逐项走一遍,每一步看系统里能不能做、做完数据在哪。 - [集团合同管理办法怎么定:选系统之前,先把这几章写清楚](https://zico.fim.ai/zh/resources/group-contract-management-policy): 集团合同管理办法通常要写清八件事:适用范围和签约主体、分级授权表、范本管理、审查与会签、签署与用印、履行与变更、归档与保管、统计与责任。先把办法写定,再选合同系统;选型时逐章问一句「这一章在系统里落在哪个配置上」,能落下来的才是合用的系统。 - [钉钉合同审批怎么设置?什么时候需要单独的合同系统](https://zico.fim.ai/zh/resources/dingtalk-contract-approval): 在钉钉里做合同审批,用 OA 审批新建一个「合同审批」表单、按金额设好条件分支,就能跑起来。判断要不要上单独的合同系统,看五个信号:同一份合同改了好几稿、审批人要对着正文看条款、签完以后没人跟付款和到期、查一份旧合同要翻聊天记录、合同分属几个签约主体。出现两三个,就该让合同系统管合同,钉钉继续收待办。 - [企业微信里的合同审批怎么做?哪些环节要单独管](https://zico.fim.ai/zh/resources/wecom-contract-approval): 合同量不大、审批规则简单时,用企业微信自带的审批应用建一个「合同审批」模板就能跑起来。合同多起来以后,审批之外的几件事企业微信管不到:正文版本、条款审查、签署后的履约和到期、台账查询。这些环节要放进合同系统,审批待办再推回企业微信处理。 - [合同台账模板:哪些字段必须有,怎么从正文里抽出来](https://zico.fim.ai/zh/resources/contract-ledger-template-fields): 一张能用的合同台账,至少要有五组字段:身份(编号、名称、类型)、主体(我方签约主体、交易方)、金额与付款、期限与履约节点、状态与归档。字段宜少不宜多,每个字段写清口径和谁来填。存量合同可以先用信息抽取从正文里提出候选值,再由人核对后写入台账。 - [两份合同怎么找不同:修订稿对比要盯哪些改动](https://zico.fim.ai/zh/resources/contract-redline-compare-what-to-check): 对方退回修订稿,先按条款把两版对齐,再把改了约定的「实质性改动」和只改措辞的改动分开看。重点盯金额与付款、期限与交付、违约与赔偿、管辖与争议、主体与签约方、知识产权与保密六类;对方没开修订模式、直接改了 PDF 的,更要逐条比。 - [AI 合同审查工具免费吗?审完以后法务还要复核哪几步](https://zico.fim.ai/zh/resources/ai-contract-review-free-and-human-check): 能免费试的 AI 审合同方式不少,比如把条款贴进通用聊天助手;但企业正式用,要看数据放在哪、结论能不能对回原文、能不能按自己的审查清单来。无论用哪种工具,AI 出完结果后,法务至少还要做五步复核:核对立场、逐条回原文、补齐缺失条款、确认金额日期、把口头约定落成文本。 - [合同管理系统多少钱?报价通常包含哪几块](https://zico.fim.ai/zh/resources/contract-management-system-cost): 合同管理系统没有统一的「一口价」:报价由软件许可、实施与对接、历史合同迁移、维保,以及 AI 用量和电子签几块拼成。想拿到一个能比的数字,先把账号范围、要对接的系统和存量合同数量整理好,再请厂商按三年拆开报。 - [AI 合同管理系统和普通合同系统差在哪:按日常五个环节看](https://zico.fim.ai/zh/resources/ai-clm-vs-traditional-clm): 普通合同系统管的是「流程和记录」:谁起草、谁审批、签没签、存在哪。 - [公司已经有飞书审批,为什么还需要合同系统](https://zico.fim.ai/zh/resources/lark-approval-vs-contract-system): 飞书、企业微信、钉钉的审批流已经把合同流程跑起来的企业,什么情况下够用,什么情况下不够,以及合同系统与协同平台并存而不是替代的做法。 - [合同系统和 ERP、CRM、电子签应该怎么分工](https://zico.fim.ai/zh/resources/contract-system-vs-erp-crm-esign): 合同数据同时散在 ERP、CRM、电子签和邮件里时,哪个系统该管哪一段、字段往哪个方向流、重复录入从哪里来,以及判断主系统归属的一条原则。 - [标准 CLM 不适合哪些企业](https://zico.fim.ai/zh/resources/when-standard-clm-does-not-fit): 标准化合同管理产品建立在三个假设之上:单一入口、以自有模板为主、流程可以按产品形状重排。哪些企业不满足这些假设,以及不满足时的可选路径。 - [Zico、幂律、甄零分别适合什么类型的企业](https://zico.fim.ai/zh/resources/clm-vendor-fit): 三家合同管理产品按各自官网公开定位的适配场景对照:企业规模、是否更换主系统、合同以自有模板还是外部来稿为主、部署形态。由 Zico 团队整理,立场已声明。 - [一次合同流程诊断到底诊断什么](https://zico.fim.ai/zh/resources/what-a-contract-diagnosis-covers): 合同流程诊断不是需求调研,目的是定位最值得先解决的那一段。会前要回答的八个问题、六十分钟怎么用、产出包含什么,以及什么情况下不必做。 - [从邮件和 Word 迁移到合同系统,应该先动哪一步](https://zico.fim.ai/zh/resources/migrating-from-email-and-word): 合同一直靠邮件和 Word 跑的企业上系统时,第一步不该是导历史合同。先接哪一段、历史合同迁多少、双轨期怎么控制,以及怎么判断迁成功了。 - [多子公司合同权限最容易踩的七个坑](https://zico.fim.ai/zh/resources/multi-entity-contract-permissions): 集团型企业做合同权限设计时特有的七类问题:集团可见性与主体隔离的优先级、多协同租户的身份对齐、授权阈值、关联交易、数据驻留、台账口径与人员调动后的权限残留。 - [既有流程不能改时,合同系统怎么适配:字段前置与外部审批链](https://zico.fim.ai/zh/resources/adapting-to-existing-processes): 企业既有的填表习惯和审批系统往往动不了,合同系统要去适配。两个常见做法:把台账字段前置成抽取加确认,以及把审批编排交回外部费控或 OA 系统,以及各自的边界和风险。 - [不替换现有 OA,如何接入 AI 合同审查](https://zico.fim.ai/zh/resources/ai-review-without-replacing-oa): 已有 OA 或合同系统时,接入 AI 合同审查的三种方式、审查结果如何回到原流程、人工确认该放在哪一步,以及当前能做与做不了的边界。 - [私有化合同管理系统选型:部署、集成、AI 审查怎么验](https://zico.fim.ai/zh/resources/private-deployment-checklist): 已经定了私有化部署、要比较合同管理系统供应商时,建议逐项核对部署、集成、AI 审查三个检查点:每一项该问供应商什么、怎么验证,以及飞沐旗下合同管理品牌 Zico 的做法。 ## Resources (English) - [How to Keep a Contract and Its Amendments Aligned](https://zico.fim.ai/en/resources/contract-amendment-matching-original-and-supplement): After a contract is amended or a supplement is signed, keep the original and the amendment under the same contract number and the same register record. State which clauses have changed, which still follow the original, when the change takes effect, and which text prevails if the two disagree. File the new text with the original; if payment, delivery or acceptance dates change, update the fulfillment plan as well. Zico (FIM) covers fulfillment and archive, and keeps successive versions in the same flow; capabilities are those stated on the live product page. - [Before Signing: Which Counterparty Documents to Collect](https://zico.fim.ai/en/resources/counterparty-documents-before-signing): Before signing, collect the counterparty's registration documents, signing authority, and the signatory's ID; if the work requires a permit, collect that too. File them with the contract and re-check after a name or status change. Zico's contract system includes a counterparty record in its register and archive. Enterprise qualification checks are an optional, per-query add-on described on the pricing page as a business-registration lookup; they do not replace letters of authorization. - [After Signing, Track Payment, Delivery and Acceptance](https://zico.fim.ai/en/resources/contract-fulfillment-payment-delivery-acceptance): After a contract is signed, pull payment, delivery and acceptance out of the text into a tracking plan: for each item, write the due date or trigger, the evidence to keep, who is responsible, and the current status, and hang the plan on the same ledger record, not in a personal spreadsheet. Payments should follow a receipt-and-payment plan, and there should be no payment without a contract; delivery and acceptance each need their own evidence, the three often trigger one another, and a supplemental agreement that changes a milestone should change the same plan. That is what you can go back to when reconciling accounts or when a dispute arises. - [Group Subsidiaries: Splitting Contract Permissions and Data](https://zico.fim.ai/en/resources/group-subsidiaries-contract-permissions-data): When a group has several subsidiaries, don't configure contract permissions person by person. Build one table first: organization down the side (group, subsidiary as the contracting entity, department), roles across the top, then a cut by contract type, and for each cell decide who gets to view, edit, approve and export. By default the group level sees ledger summaries, while full text and attachments are granted per contracting entity; approvals follow the contracting entity; people who hold roles in two subsidiaries get separate grants for each. Before launch, log in with a few real accounts to verify, then review grants regularly. - [Archiving Signed Contracts: Originals, Scans and E-Copies](https://zico.fim.ai/en/resources/signed-contract-archiving-original-scan-electronic): A signed contract usually exists in three forms at once: the stamped paper original, a scan of that original, and the final electronic version (or e-signed version) in a system. Archiving means tying all three to one contract number and one ledger record: check the scan against the final version page by page before filing, record where the original is kept, attach supplements and appendices to the main contract, and control and log who views or borrows it. Then any one form leads you to the other two. - [Who Makes Zico: Company, Two Products and How to Start](https://zico.fim.ai/en/resources/who-makes-zico-products-and-access): Zico is the contract management brand of Beijing FIM Network Technology Co., Ltd., and its official website is zico.fim.ai. Zico offers two products. Zico Contract System covers drafting, negotiation, approval, signing, fulfillment and archive; it is delivered as a private deployment, quoted per client, with unlimited seats and free maintenance in year one. Zico AI provides contract review, quick review, version compare, translation, extraction, summaries and meeting minutes; it is billed separately as an annual subscription and opened manually after you leave your details on the website, with no self-service sign-up. The contract system starts with a demo; Zico AI starts with a request on the website. - [Before a Contract System Demo: What to Prepare](https://zico.fim.ai/en/resources/contract-system-demo-preparation-checklist): Before booking a contract management system demo, prepare six things: three to five real contracts, a one-page sketch of your current contract process, a list of the systems and collaboration platforms to connect, your deployment and data requirements, the attendees and the questions each wants answered, and three numbers for the quote (seat scope, number of systems to connect, number of existing contracts). Then the demo shows the system running on your own contracts, and the quote follows one shared scope. A Zico demo walks through one real contract, then quotes by company size and deployment. - [Contract System Pricing: Billing Models Compared and FAQ](https://zico.fim.ai/en/resources/contract-management-system-pricing-models-faq): Contract management systems are usually priced in one of three ways: per-seat subscription, a one-time license plus project-based quote, or usage-based billing. Many quotes mix them, so align the billing model first, then split each quote into year one plus each later year and add up three years. Zico contract system is deployed privately, quoted per client, with unlimited seats and free maintenance in year one. Zico AI is billed separately as an annual subscription and is opened manually after you leave your details on the website. - [Handing over contracts when an employee leaves](https://zico.fim.ai/en/resources/contract-handover-when-employee-leaves): When an employee leaves, a contract handover covers three things: the list of contracts they handled and where each one stands, the approvals and tasks still open in their name, and their access rights in the system. Pull the list from the contract register, flag contracts that are in progress, being performed or about to expire, and name a new owner for each. Move open approvals to the new owner and revoke access on the last day. The department head signs off the handover list, which is then filed. - [Designing a contract approval workflow by contract type, amount and business line](https://zico.fim.ai/en/resources/contract-approval-matrix-type-amount-business-line): Do not run every contract through one approval line. Split workflows by contract type, set a few amount tiers within each type, and, where several business lines or signing entities are involved, route approvers by business line. Crossing the three gives you an approval matrix: each contract is routed automatically by type, amount and business line, and pending approvals move to a successor when someone leaves. - [Contract expiry reminders: what to track for renewals, terminations and auto-renewal clauses](https://zico.fim.ai/en/resources/contract-expiry-reminder-renewal-termination): A contract expiry reminder needs more than an end date. Pull four kinds of dates from each contract: the expiry date, the notice period for renewal or termination, any auto-renewal terms, and obligations due before expiry. Work back from the notice deadline to set reminder dates, and give each reminder an owner. Reminders kept in the contract register, attached to the contract record, are more reliable than ones in a personal calendar. - [E-signature vs. contract management system: what still needs managing after the signature](https://zico.fim.ai/en/resources/e-signature-vs-contract-management-system): E-signature handles how a contract gets signed: online signing, signer identity and an audit trail. A contract management system covers the whole life of a contract: drafting and approval before signing, and performance tracking, renewal reminders, the contract register and archiving after it. If you only need to move paper signing online, e-signature is enough. If you have many contracts, layered approvals and obligations to follow up after signing, you need a contract management system, with e-signature plugged in as its signing step. - [Should your contract management system run on your own servers? Four questions to ask first](https://zico.fim.ai/en/resources/contract-system-on-premise-or-cloud): Running a contract management system on your own servers (private deployment) suits companies whose contract data is sensitive, who face regulatory, audit or group-policy requirements to keep data in-house, who need deep integration with internal systems, and who have someone to run the system day to day. If most answers are yes, start with private deployment; if most are no, evaluate cloud options first. Either way, settle upgrades, backups, admin handover and pricing before you sign. - [What features does a contract management system need, and how do you test them before go-live?](https://zico.fim.ai/en/resources/contract-management-system-features): Contract management system features usually fall into six groups: drafting and templates, negotiation and versions, approval and sign-off, signing and sealing, performance and reminders, and archiving and the contract register, plus permissions and reporting across all of them. Reading a feature list is easy; testing is what matters. Before go-live, take three to five of your own real contracts and walk each one through all six groups. - [Writing a group contract management policy before you choose a system](https://zico.fim.ai/en/resources/group-contract-management-policy): A group-wide contract management policy usually needs eight sections: scope and contracting entities, an approval authority matrix, template control, review and sign-off, execution and sealing, performance and amendments, archiving, and reporting and accountability. Write the policy first, then choose a contract system by asking, section by section, where each rule lives in the system's configuration. - [Contract ledger template: which fields you need and how to pull them from the contract text](https://zico.fim.ai/en/resources/contract-ledger-template-fields): A workable contract ledger needs five groups of fields - identity (number, name, type), parties (your signing entity, the counterparty), amount and payment, term and obligations, and status and filing. Keep the field list short and define each field and who fills it. For existing contracts, extract candidate values from the text first, then have a person confirm them before they go into the ledger. - [How much does a contract management system cost? What a quote usually includes](https://zico.fim.ai/en/resources/contract-management-system-cost): There is no single list price for a contract management system. A quote is built from software licensing, implementation and integration, legacy contract migration, maintenance, AI usage and e-signature. To get numbers you can compare, prepare your user count, the systems to integrate and your contract backlog, then ask each vendor for a three-year breakdown. - [How an AI contract management system differs from a regular one: five everyday steps](https://zico.fim.ai/en/resources/ai-clm-vs-traditional-clm): A regular contract system manages process and records: who drafted, who approved, whether it is signed, where it is stored. - [You already run approvals in your chat suite. Why add a contract system?](https://zico.fim.ai/en/resources/lark-approval-vs-contract-system): For teams already running contract approvals in Lark, Teams, WeCom or DingTalk: when that is enough, when it stops being enough, and how a contract system sits alongside rather than replacing it. - [How a contract system divides work with ERP, CRM and e-signature](https://zico.fim.ai/en/resources/contract-system-vs-erp-crm-esign): When contract data is scattered across ERP, CRM, e-signature and email, which system owns which stretch, which direction fields should flow, where duplicate entry comes from, and one rule for deciding the system of record. - [Which companies a standard CLM does not fit](https://zico.fim.ai/en/resources/when-standard-clm-does-not-fit): Standard contract management products rest on three assumptions: one entry point, mostly first-party templates, and a process that can be rearranged to suit the product. Which companies break those assumptions, and what the options are when they do. - [Which contract management products fit which companies](https://zico.fim.ai/en/resources/clm-vendor-fit): A scenario-based comparison of contract management products by their publicly stated positioning: company size, whether the system of record is being replaced, first-party templates versus inbound paper, and deployment shape. Written by the Zico team, with that interest declared. - [What a contract process diagnosis actually covers](https://zico.fim.ai/en/resources/what-a-contract-diagnosis-covers): A contract process diagnosis is not requirements gathering. Its purpose is to locate the one stretch worth fixing first. The eight questions to answer beforehand, how the hour is spent, what it produces, and when to skip it. - [Moving off email and Word: which step comes first](https://zico.fim.ai/en/resources/migrating-from-email-and-word): For teams still running contracts through email and Word, importing history is the wrong first step. Which loop to connect first, how much history to migrate, how to run the dual-track period, and how to tell it worked. - [Seven traps in contract permissions across group subsidiaries](https://zico.fim.ai/en/resources/multi-entity-contract-permissions): Seven problems specific to group structures: group visibility versus entity isolation, identity across collaboration tenants, authority thresholds, related-party transactions, data residency, register consistency, and permissions left behind after transfers. - [When existing processes cannot change: upfront fields and external approval chains](https://zico.fim.ai/en/resources/adapting-to-existing-processes): Form habits and approval systems a company cannot change are usually fixed points, so the contract system adapts. Two patterns from real rollouts: moving register fields to extraction plus confirmation at upload, and handing approval orchestration back to the existing spend-control or OA system. - [Adding AI contract review without replacing your existing system](https://zico.fim.ai/en/resources/ai-review-without-replacing-oa): If contracts already run through your workflow or contract system, AI review can be added alongside it. The three integration paths, where results land, who signs off, and what is out of scope today. - [Vetting a Privately Deployed Contract Management System: Deployment, Integration, AI Review](https://zico.fim.ai/en/resources/private-deployment-checklist): Once you have decided on private deployment and are comparing contract management vendors, check three things: deployment, integration, and AI review. For each: what to ask vendors, how to verify, and how Zico (by FIM) does it. ## Zico 合同系统:起草、审批、台账、履约一体化 - 覆盖:起草、协商、审批、签署、履约、归档 - 协商:多方多轮版本、在线协同编辑、协商评论与附件 - 审批:灵活审批流、按类型、金额、业务线分级审批、离职自动转办、审批流版本管理 - 台账与归档:合同台账与搜索、合同模板管理、交易方档案、签署扫描件与定稿一致性比对 - 履约与内控:收付款计划、无合同不付款、倒签合规治理、操作审计日志 - 组织与生态:飞书多租户、OA 账号联动、ERP / 财务 API、电子签章集成 - 系统与合同数据:可部署在企业自有环境内流转,飞沐提供软件授权与技术支持。 - 协同入口:已在客户生产环境运行:飞书(消息、审批、日历、待办)与企业内部 OA。钉钉、企业微信、泛微、致远、蓝凌等按需对接,范围在需求确认时给出。 - 外部系统:通过开放 API / Webhook 对接 ERP、财务费控、OA 与电子签章。 - Zico AI:单独计费,按年订阅(含点数),公开价见方案页;可随合同系统一并采购,也可单独接入已有系统(开放 API、Webhook 或白标 iframe)。 ## 采购事实(摘自 /zh/faq) - Zico 支持哪些部署方式?区别是什么? Zico 合同系统以私有化部署交付:系统部署在企业自己的服务器上,数据由企业掌控。Zico AI 可在飞沐提供的环境中使用(申请后人工开通),也可随合同系统部署到企业环境。 - 私有化部署需要什么服务器配置? 按企业规模配置,从标准配置(8 核 16G × 2 台)到企业级配置(32 核 64G × 5 台及以上)不等。具体配置可联系销售,按用户规模与使用场景给出建议。 - 私有化标准版和进阶版有什么区别? 私有化标准版覆盖起草到归档的合同流程模块,不限账号数,协同平台深度集成,完整系统集成,以及首年免费维保;Zico AI 单独计费,可一并采购。进阶版增加可选的私有化 LLM 部署(按项目确认)与定制化开发支持。 - Zico AI 怎么收费? 按年订阅:Silver ¥36,000、Gold ¥60,000、Platinum ¥96,000,分别含 10 万、20 万、40 万点的年度额度,用尽后按 1 元 = 10 点增购。审查每页 10 点,速审每份 1 点,其余能力的扣点见方案页。可申请 2,000 点、30 天的产品体验,提交后人工开通。 - 私有化部署怎么收费? 按企业规模、集成范围与迁移量报价。私有化方案为一次性付费,不限账号数,首年免费维保。 - AI 功能需要额外付费吗? 需要。合同系统与 Zico AI 分开计价:合同系统私有化按项目报价,Zico AI 按年订阅计费,可随合同系统一并采购,也可单独接入已有系统。 - 哪些项目需要另外计费? 以下增值服务按需选购:电子签章(e签宝 / 章管家)按签署次数计费,OCR 识别按页数计费,企业资质查验按次数计费,定制开发按人天计费,AI 能力定制价格请联系销售。 - 合同数据存储在哪里? 私有化部署时,系统与数据部署在企业自己的服务器上,数据驻留在企业环境内,由企业掌控。在飞沐环境中使用 Zico AI 时,上传的文档存放在飞沐的服务器上。 - 使用 AI 时,合同内容能否不出企业网络? 私有化部署时,系统与合同数据存放在企业环境内。OCR、ASR 与 Zev 速审在企业有 GPU 时于企业内运行,没有 GPU 时使用飞沐算力,不经第三方模型服务;要求全部 AI 能力在企业网络内运行的,可选私有化进阶版的私有化 LLM 部署(按项目确认)。各项 AI 能力的运行位置与数据边界,在部署前按企业网络环境书面确认。 - 权限和操作审计怎么管理? 系统提供角色管理与权限配置,数据权限可按组织与合同类型精细授权;关键操作记录操作日志,可追踪、可导出。合同分享支持有效期与密码保护,打印件带防伪水印和二维码。 ## Zico AI:合同场景的能力中枢 - 合同审查(按立场,回到原文,可用):按甲乙方立场扫描主体、付款、违约、管辖与知识产权等条款,输出分级清单。存在型与缺失型分开;法条核对在风险出完之后补上。 - 合同速审(自研 Zev 模型,几秒标出利弊,可用):Zico AI 自研的 Zev 模型按一套固定核对清单,逐条提取合同条款写了什么,例如付款是否以发票为前提、违约后果写到什么程度,并标出每条约定利于哪一方。一份一两百条条款的合同几秒出结果。需要逐条出意见与改法时,转到合同审查。 - 版本对比(实质性分开,可用):两份合同做条款级 diff。实质性与非实质性变更分开,Word 与电子版 PDF 可对读。还可对两版各做一次合同速审,标出哪些改动改变了核对结论。 - 合同翻译(数字对得上,可用):按条款结构翻译,术语表锁定译法。数字、日期、金额与原文不一致会标出;模型没返回的段落计为未译出,不编一段填空。 - 信息抽取(回流下游台账,可用):当事人、标的、金额、期限、付款节点等写成结构化结果。台账、到期提醒留在合同系统或你现有的系统里。 - 合同摘要(一页看完这一份,可用):主合同要点加附件对照。挂了谈判录音时,转写稿一并读入,不一致处单独标出。 - 会议纪要(录音可回听,可用):谈判录音转写后按侧重点生成纪要。说话人可由人指认成真名;时间戳可回到原声。 ## 相关站点 / Related - FIM(飞沐)公司站: https://fim.ai - FIM One 企业 Agent 平台: https://one.fim.ai