[{"data":1,"prerenderedAt":2921},["ShallowReactive",2],{"blog-\u002Fblog\u002Fcost-process\u002Fbaomi-xieyi-nda":3,"blog-related-\u002Fblog\u002Fcost-process\u002Fbaomi-xieyi-nda":753},{"id":4,"title":5,"author":6,"body":7,"category":721,"cover":722,"date":723,"description":724,"draft":725,"extension":726,"faq":727,"featured":725,"image":722,"keywords":737,"meta":742,"navigation":743,"path":744,"seo":745,"sitemap":746,"stem":747,"tags":748,"updated":723,"__hash__":752},"blog\u002Fblog\u002Fcost-process\u002Fbaomi-xieyi-nda.md","保密协议（NDA）怎么签","HNREIS",{"type":8,"value":9,"toc":690},"minimark",[10,19,24,27,40,46,50,54,122,125,139,145,149,153,156,170,175,179,182,196,202,207,211,257,263,267,273,287,290,294,297,308,312,323,328,332,370,376,380,384,387,398,402,405,413,418,422,425,433,438,442,445,456,461,465,468,476,481,485,488,496,501,505,550,554,599,604,607,645,648,684],[11,12,13,14,18],"p",{},"\"我想做个软件，但担心想法被偷，要不要先签个保密协议？\"——这是很多企业主第一次外包时的顾虑。",[15,16,17],"strong",{},"NDA（保密协议）是保护商业机密和核心数据的基础工具，但很多人不知道什么时候签、签什么内容，签了等于没签。"," 这篇文章讲清 NDA 怎么签才有用。",[20,21,23],"h2",{"id":22},"nda-是什么","NDA 是什么",[11,25,26],{},"NDA（Non-Disclosure Agreement）保密协议：",[28,29,30,34,37],"ul",{},[31,32,33],"li",{},"双方约定某些信息属于保密信息。",[31,35,36],{},"接收方不能泄露、不能用于约定外用途。",[31,38,39],{},"违约要承担赔偿责任。",[11,41,42,45],{},[15,43,44],{},"作用","：约束双方行为，出事有法律依据。",[20,47,49],{"id":48},"什么时候签-nda","什么时候签 NDA",[51,52,53],"h3",{"id":53},"该签的情况",[55,56,57,70],"table",{},[58,59,60],"thead",{},[61,62,63,67],"tr",{},[64,65,66],"th",{},"场景",[64,68,69],{},"为什么签",[71,72,73,82,90,98,106,114],"tbody",{},[61,74,75,79],{},[76,77,78],"td",{},"涉及商业机密",[76,80,81],{},"业务逻辑、定价、客户数据",[61,83,84,87],{},[76,85,86],{},"未公开产品",[76,88,89],{},"还没上线的核心方案",[61,91,92,95],{},[76,93,94],{},"用户数据",[76,96,97],{},"涉及隐私和合规",[61,99,100,103],{},[76,101,102],{},"技术细节",[76,104,105],{},"算法、架构、核心代码",[61,107,108,111],{},[76,109,110],{},"招标竞标",[76,112,113],{},"多家接触方案，保护信息",[61,115,116,119],{},[76,117,118],{},"长期合作",[76,120,121],{},"持续接触内部信息",[51,123,124],{"id":124},"可不签的情况",[28,126,127,130,133,136],{},[31,128,129],{},"普通展示型网站（无敏感信息）。",[31,131,132],{},"模板建站（无定制方案）。",[31,134,135],{},"公开咨询（不涉及机密）。",[31,137,138],{},"已经公开的产品需求。",[11,140,141,144],{},[15,142,143],{},"签不签取决于信息敏感度","。",[20,146,148],{"id":147},"nda-必须包含的条款","NDA 必须包含的条款",[51,150,152],{"id":151},"_1-保密信息的定义","1. 保密信息的定义",[11,154,155],{},"写清楚什么算保密信息：",[28,157,158,161,164,167],{},[31,159,160],{},"商业：业务模式、客户、定价、营销方案。",[31,162,163],{},"技术：源码、架构、算法、数据。",[31,165,166],{},"财务：营收、成本、融资。",[31,168,169],{},"文档：原型、需求、规划。",[11,171,172,144],{},[15,173,174],{},"定义越清楚，保护越明确",[51,176,178],{"id":177},"_2-保密义务","2. 保密义务",[11,180,181],{},"接收方不能：",[28,183,184,187,190,193],{},[31,185,186],{},"向第三方披露。",[31,188,189],{},"用于约定外用途。",[31,191,192],{},"复制、传播。",[31,194,195],{},"允许员工私自留存。",[11,197,198,201],{},[15,199,200],{},"例外要列清楚","（避免事后争议）：",[28,203,204],{},[31,205,206],{},"已公开的信息。\n| 例外 | 说明 |\n| --- | --- |\n| 公开信息 | 已通过合法渠道公开 |\n| 独立开发 | 没用保密信息独立开发 |\n| 法律要求 | 法院、监管要求披露 |\n| 第三方合法获得 | 从无保密义务的第三方获得 |",[51,208,210],{"id":209},"_3-保密期限","3. 保密期限",[55,212,213,223],{},[58,214,215],{},[61,216,217,220],{},[64,218,219],{},"类型",[64,221,222],{},"期限",[71,224,225,233,241,249],{},[61,226,227,230],{},[76,228,229],{},"一般商业信息",[76,231,232],{},"2-3 年",[61,234,235,238],{},[76,236,237],{},"核心技术\u002F源码",[76,239,240],{},"5 年或长期",[61,242,243,246],{},[76,244,245],{},"客户数据",[76,247,248],{},"长期",[61,250,251,254],{},[76,252,253],{},"涉及专利",[76,255,256],{},"专利有效期内",[11,258,259,262],{},[15,260,261],{},"期限太短保护不够，太长不现实","——一般 3 年合理。",[51,264,266],{"id":265},"_4-违约责任","4. 违约责任",[11,268,269,272],{},[15,270,271],{},"光说不赔的 NDA 是废纸","：",[28,274,275,278,281,284],{},[31,276,277],{},"违约金（具体数额或计算方式）。",[31,279,280],{},"实际损失赔偿。",[31,282,283],{},"维权费用（律师费、诉讼费）。",[31,285,286],{},"禁令救济（法院禁止继续泄露）。",[11,288,289],{},"违约金要有威慑力，但不能虚高（法院会调整）。",[51,291,293],{"id":292},"_5-信息返还销毁","5. 信息返还\u002F销毁",[11,295,296],{},"合作结束或终止时：",[28,298,299,302,305],{},[31,300,301],{},"返还所有保密信息。",[31,303,304],{},"销毁副本。",[31,306,307],{},"出具销毁证明。",[51,309,311],{"id":310},"_6-争议解决","6. 争议解决",[28,313,314,317,320],{},[31,315,316],{},"协商 → 调解 → 诉讼\u002F仲裁。",[31,318,319],{},"管辖法院或仲裁机构。",[31,321,322],{},"适用法律。",[11,324,325,144],{},[15,326,327],{},"约定清楚，出事好处理",[20,329,331],{"id":330},"双向-vs-单向-nda","双向 vs 单向 NDA",[55,333,334,346],{},[58,335,336],{},[61,337,338,340,343],{},[64,339,219],{},[64,341,342],{},"谁约束谁",[64,344,345],{},"适合",[71,347,348,359],{},[61,349,350,353,356],{},[76,351,352],{},"单向 NDA",[76,354,355],{},"只约束乙方（开发方）",[76,357,358],{},"甲方提供机密",[61,360,361,364,367],{},[76,362,363],{},"双向 NDA",[76,365,366],{},"互相约束",[76,368,369],{},"双方互提供机密",[11,371,372,375],{},[15,373,374],{},"软件开发通常签双向 NDA","——甲方给需求\u002F数据，乙方给方案\u002F技术。",[20,377,379],{"id":378},"nda-常见误区","NDA 常见误区",[51,381,383],{"id":382},"_1-用网上模板不改","1. 用网上模板不改",[11,385,386],{},"通用模板不适合具体场景，关键条款要定制：",[28,388,389,392,395],{},[31,390,391],{},"保密信息定义要匹配项目。",[31,393,394],{},"违约金要合理。",[31,396,397],{},"期限要合适。",[51,399,401],{"id":400},"_2-签太早","2. 签太早",[11,403,404],{},"还没决定合作就签 NDA：",[28,406,407,410],{},[31,408,409],{},"限制自己选别家。",[31,411,412],{},"增加合规成本。",[11,414,415,144],{},[15,416,417],{},"先评估意向，确定要深度沟通再签",[51,419,421],{"id":420},"_3-签太晚","3. 签太晚",[11,423,424],{},"信息已经分享了才签：",[28,426,427,430],{},[31,428,429],{},"已经泄露的无法追溯。",[31,431,432],{},"事后签作用有限。",[11,434,435,144],{},[15,436,437],{},"敏感信息分享前必须签",[51,439,441],{"id":440},"_4-光签不落实","4. 光签不落实",[11,443,444],{},"签了 NDA 但不做：",[28,446,447,450,453],{},[31,448,449],{},"不限制信息访问（谁都能看）。",[31,451,452],{},"不做权限管理（员工随意拷贝）。",[31,454,455],{},"不留痕（出了事没证据）。",[11,457,458,144],{},[15,459,460],{},"NDA 配合管理措施才有用",[51,462,464],{"id":463},"_5-违约责任虚","5. 违约责任虚",[11,466,467],{},"只写\"违反协议承担责任\"，没具体数额：",[28,469,470,473],{},[31,471,472],{},"出事难主张。",[31,474,475],{},"威慑力不够。",[11,477,478,144],{},[15,479,480],{},"违约金要写具体或计算方式",[51,482,484],{"id":483},"_6-忽视员工约束","6. 忽视员工约束",[11,486,487],{},"开发方员工离职带走信息：",[28,489,490,493],{},[31,491,492],{},"NDA 要约束员工。",[31,494,495],{},"开发方内部要有保密制度。",[11,497,498,144],{},[15,499,500],{},"NDA 要明确开发方对员工的责任",[20,502,504],{"id":503},"怎么签-nda-才有用","怎么签 NDA 才有用",[506,507,508,514,520,526,532,538,544],"ol",{},[31,509,510,513],{},[15,511,512],{},"评估信息敏感度","：决定要不要签。",[31,515,516,519],{},[15,517,518],{},"选合适模板","：根据项目定制。",[31,521,522,525],{},[15,523,524],{},"签双向 NDA","：双方互约束。",[31,527,528,531],{},[15,529,530],{},"关键条款写清楚","：定义、义务、违约、期限。",[31,533,534,537],{},[15,535,536],{},"配合管理措施","：权限、留痕、销毁。",[31,539,540,543],{},[15,541,542],{},"争议解决约定","：管辖法院、适用法律。",[31,545,546,549],{},[15,547,548],{},"双方留原件","：签字盖章、保留证据。",[20,551,553],{"id":552},"签-nda-的成本","签 NDA 的成本",[55,555,556,566],{},[58,557,558],{},[61,559,560,563],{},[64,561,562],{},"项目",[64,564,565],{},"成本",[71,567,568,576,584,591],{},[61,569,570,573],{},[76,571,572],{},"模板获取",[76,574,575],{},"免费（网上）\u002F几百元（专业版）",[61,577,578,581],{},[76,579,580],{},"律师定制",[76,582,583],{},"几百到几千",[61,585,586,589],{},[76,587,588],{},"公证（如需）",[76,590,583],{},[61,592,593,596],{},[76,594,595],{},"管理（权限\u002F留痕）",[76,597,598],{},"内部成本",[11,600,601,144],{},[15,602,603],{},"NDA 成本不高，保护价值高",[20,605,606],{"id":606},"常见误区",[28,608,609,615,621,627,633,639],{},[31,610,611,614],{},[15,612,613],{},"\"网上下载个模板就行\"","：关键条款要定制。",[31,616,617,620],{},[15,618,619],{},"\"口头保密就行\"","：没法律效力。",[31,622,623,626],{},[15,624,625],{},"\"违约金写越高越好\"","：虚高法院不支持，反而影响效力。",[31,628,629,632],{},[15,630,631],{},"\"签了就万事大吉\"","：要配合管理措施。",[31,634,635,638],{},[15,636,637],{},"\"小公司不会泄露\"","：人员流动大，更易泄露。",[31,640,641,644],{},[15,642,643],{},"\"项目结束就不用管\"","：保密义务持续到期限结束。",[20,646,647],{"id":647},"怎么做",[506,649,650,655,661,667,673,678],{},[31,651,652,654],{},[15,653,512],{},"：决定签不签。",[31,656,657,660],{},[15,658,659],{},"准备双向 NDA","：参考模板定制。",[31,662,663,666],{},[15,664,665],{},"签在分享敏感信息前","：早签有限制，晚签没意义。",[31,668,669,672],{},[15,670,671],{},"关键条款具体","：定义、违约、期限。",[31,674,675,537],{},[15,676,677],{},"配合管理",[31,679,680,683],{},[15,681,682],{},"找规范服务商","：愿意签 NDA 的更靠谱。",[685,686,687],"blockquote",{},[11,688,689],{},"广州市汉诺雷斯（HNREIS）在涉及商业机密的项目上签双向 NDA，规范保密义务、违约责任、信息返还。把你的项目需求告诉我们，我们先签 NDA 再深度沟通。",{"title":691,"searchDepth":692,"depth":692,"links":693},"",2,[694,695,700,708,709,717,718,719,720],{"id":22,"depth":692,"text":23},{"id":48,"depth":692,"text":49,"children":696},[697,699],{"id":53,"depth":698,"text":53},3,{"id":124,"depth":698,"text":124},{"id":147,"depth":692,"text":148,"children":701},[702,703,704,705,706,707],{"id":151,"depth":698,"text":152},{"id":177,"depth":698,"text":178},{"id":209,"depth":698,"text":210},{"id":265,"depth":698,"text":266},{"id":292,"depth":698,"text":293},{"id":310,"depth":698,"text":311},{"id":330,"depth":692,"text":331},{"id":378,"depth":692,"text":379,"children":710},[711,712,713,714,715,716],{"id":382,"depth":698,"text":383},{"id":400,"depth":698,"text":401},{"id":420,"depth":698,"text":421},{"id":440,"depth":698,"text":441},{"id":463,"depth":698,"text":464},{"id":483,"depth":698,"text":484},{"id":503,"depth":692,"text":504},{"id":552,"depth":692,"text":553},{"id":606,"depth":692,"text":606},{"id":647,"depth":692,"text":647},"cost-process",null,"2024-06-29","软件外包合作前，很多企业主会被要求或主动要求签保密协议（NDA）。本文讲清 NDA 是什么、什么时候签、必须包含的条款、签 NDA 的常见误区，保护你的商业机密和核心数据。",false,"md",[728,731,734],{"q":729,"a":730},"软件外包一定要签 NDA 吗？","涉及商业机密、核心数据、未公开产品方案的项目，建议签 NDA。普通的展示型网站、模板项目可以不签。但如果你担心想法被偷、数据被泄露、方案被竞争对手拿到，NDA 是基础保护。签 NDA 不复杂，规范的开发商会主动提供模板。",{"q":732,"a":733},"NDA 要在什么阶段签？","在共享敏感信息之前签——通常是接触需求细节、商业逻辑、用户数据之前。常见节点：第一次深度沟通需求时、看到原型或源码前、参与竞标前。注意：NDA 不能太早签（你还没决定合作，签了限制自己），也不能太晚签（信息已经泄露，签了也没用）。",{"q":735,"a":736},"NDA 应该包含哪些核心条款？","至少包含：保密信息的定义（什么算机密）、保密义务（不能做什么）、保密期限（多久）、例外情况（公开信息、独立开发不违反）、违约责任（赔偿）、争议解决（管辖法院\u002F仲裁）。其中违约责任一定要写清楚——光说不赔的 NDA 是废纸。",[738,739,740,741],"保密协议 NDA","软件外包保密","商业机密保护","NDA 条款",{},true,"\u002Fblog\u002Fcost-process\u002Fbaomi-xieyi-nda",{"title":5,"description":724},{"loc":744},"blog\u002Fcost-process\u002Fbaomi-xieyi-nda",[749,750,751],"保密协议","合同","避坑","ZKr20Ca0zP6aO73Q-uwLCiKZ9_rjxPi6jH4zYBMLlHU",[754,1227,1711,2371],{"id":755,"title":756,"author":6,"body":757,"category":721,"cover":722,"date":1200,"description":1201,"draft":725,"extension":726,"faq":1202,"featured":725,"image":722,"keywords":1212,"meta":1217,"navigation":743,"path":1218,"seo":1219,"sitemap":1220,"stem":1221,"tags":1222,"updated":1200,"__hash__":1226},"blog\u002Fblog\u002Fcost-process\u002Fai-xiangmu-baojia-mingxi.md","AI项目报价为什么难统一",{"type":8,"value":758,"toc":1183},[759,766,770,773,845,851,854,858,872,882,886,900,906,910,924,930,933,936,947,953,956,964,967,971,982,985,996,1000,1003,1092,1098,1100,1138,1140,1178],[11,760,761,762,765],{},"很多企业主拿着同一个 AI 需求问一圈，报价能从几万到几十万不等，差异大到让人怀疑有人在坑钱。",[15,763,764],{},"AI 项目报价难统一，不是有人黑心，而是 AI 这件事变量太多——同样的\"智能客服\"，做法不同成本天差地别。"," 这篇文章拆解 AI 报价背后的真实构成。",[20,767,769],{"id":768},"ai-报价为什么这么乱","AI 报价为什么这么乱",[11,771,772],{},"AI 项目和传统软件不一样，变量多：",[55,774,775,788],{},[58,776,777],{},[61,778,779,782,785],{},[64,780,781],{},"维度",[64,783,784],{},"选项",[64,786,787],{},"对价格影响",[71,789,790,801,812,823,834],{},[61,791,792,795,798],{},[76,793,794],{},"模型来源",[76,796,797],{},"调 API \u002F 开源微调 \u002F 从零训练",[76,799,800],{},"几万 vs 几十万 vs 百万级",[61,802,803,806,809],{},[76,804,805],{},"数据",[76,807,808],{},"现有数据 \u002F 要清洗 \u002F 要标注",[76,810,811],{},"大幅影响工时",[61,813,814,817,820],{},[76,815,816],{},"部署",[76,818,819],{},"云端 SaaS \u002F 私有化部署",[76,821,822],{},"私有化加 30%-100%",[61,824,825,828,831],{},[76,826,827],{},"业务深度",[76,829,830],{},"套壳问答 \u002F RAG 知识库 \u002F 多 Agent 协同",[76,832,833],{},"工时几倍差异",[61,835,836,839,842],{},[76,837,838],{},"调用量",[76,840,841],{},"低频 \u002F 高并发",[76,843,844],{},"影响 token 成本",[11,846,847,850],{},[15,848,849],{},"所以\"做个 AI 客服多少钱\"这个问题没法直接答","，必须先理清楚做哪种 AI。",[20,852,853],{"id":853},"三种主流做法的成本对比",[51,855,857],{"id":856},"_1-api-套壳最便宜","1. API 套壳（最便宜）",[28,859,860,863,866,869],{},[31,861,862],{},"用 OpenAI \u002F 文心 \u002F 通义 \u002F 智谱 等大厂 API。",[31,864,865],{},"开发主要是接口对接 + 业务封装 + 前端。",[31,867,868],{},"成本：几万到十几万。",[31,870,871],{},"适合：简单问答、文案生成、轻度智能化。",[11,873,874,877,878,881],{},[15,875,876],{},"优点","：快、便宜、能力强。",[15,879,880],{},"缺点","：依赖外部 API、数据出域、token 持续付费。",[51,883,885],{"id":884},"_2-rag-知识库中等","2. RAG 知识库（中等）",[28,887,888,891,894,897],{},[31,889,890],{},"API 大模型 + 自有知识库（向量检索）。",[31,892,893],{},"模型用 API，知识用自己数据。",[31,895,896],{},"成本：十几万到几十万。",[31,898,899],{},"适合：企业智能客服、文档问答、知识助手。",[11,901,902,905],{},[15,903,904],{},"目前企业落地 AI 的主流方案","——能力强、成本可控、数据可控。",[51,907,909],{"id":908},"_3-自训微调模型最贵","3. 自训\u002F微调模型（最贵）",[28,911,912,915,918,921],{},[31,913,914],{},"开源模型（Llama、Qwen）微调，或从零训练。",[31,916,917],{},"涉及数据采集清洗、标注、算力租用、调参。",[31,919,920],{},"成本：几十万到百万级。",[31,922,923],{},"适合：有海量专有数据、对延迟\u002F成本极度敏感、不能依赖外部 API。",[11,925,926,929],{},[15,927,928],{},"绝大多数企业不需要自训","——除非你有特殊场景和充足预算。",[20,931,932],{"id":932},"影响报价的关键因素",[51,934,935],{"id":935},"数据准备",[28,937,938,941,944],{},[31,939,940],{},"数据清洗（去重、纠错、脱敏）。",[31,942,943],{},"数据标注（人工标注、规则标注）。",[31,945,946],{},"向量库构建（embed、索引、调优）。",[11,948,949,952],{},[15,950,951],{},"数据是 AI 项目的隐形大头","，常常占总成本 20%-40%。",[51,954,955],{"id":955},"私有化部署",[28,957,958,961],{},[31,959,960],{},"云端调用：开发便宜，按 token 付费。",[31,962,963],{},"私有化：要把模型部署到自己的服务器，硬件和运维成本高。",[11,965,966],{},"私有化通常加 30%-100% 成本，但数据不出域。",[51,968,970],{"id":969},"ai-评测","AI 评测",[28,972,973,976,979],{},[31,974,975],{},"AI 输出不 deterministic，需要专门的评测集。",[31,977,978],{},"评测指标：准确率、相关性、安全、延迟。",[31,980,981],{},"评测工时容易被低估。",[51,983,984],{"id":984},"持续运营成本",[28,986,987,990,993],{},[31,988,989],{},"API token 费用（按月持续）。",[31,991,992],{},"模型迭代（数据更新、Prompt 调优）。",[31,994,995],{},"监控（异常输出、成本、延迟）。",[20,997,999],{"id":998},"成本参考一个典型-ai-项目","成本参考：一个典型 AI 项目",[11,1001,1002],{},"以企业知识库智能客服为例（API + RAG 方案）：",[55,1004,1005,1018],{},[58,1006,1007],{},[61,1008,1009,1012,1015],{},[64,1010,1011],{},"模块",[64,1013,1014],{},"工作量",[64,1016,1017],{},"占比",[71,1019,1020,1031,1042,1051,1061,1072,1081],{},[61,1021,1022,1025,1028],{},[76,1023,1024],{},"需求与方案设计",[76,1026,1027],{},"1-2 周",[76,1029,1030],{},"10%-15%",[61,1032,1033,1036,1039],{},[76,1034,1035],{},"数据清洗与标注",[76,1037,1038],{},"2-4 周",[76,1040,1041],{},"20%-30%",[61,1043,1044,1047,1049],{},[76,1045,1046],{},"向量库与检索",[76,1048,1027],{},[76,1050,1030],{},[61,1052,1053,1056,1058],{},[76,1054,1055],{},"后端开发（接口、Agent）",[76,1057,1038],{},[76,1059,1060],{},"20%-25%",[61,1062,1063,1066,1069],{},[76,1064,1065],{},"前端开发",[76,1067,1068],{},"2-3 周",[76,1070,1071],{},"15%-20%",[61,1073,1074,1077,1079],{},[76,1075,1076],{},"测试与评测",[76,1078,1027],{},[76,1080,1030],{},[61,1082,1083,1086,1089],{},[76,1084,1085],{},"部署与运维",[76,1087,1088],{},"持续",[76,1090,1091],{},"5%-10%",[11,1093,1094,1095,144],{},"具体价格看团队人天单价，区间通常十几万到几十万。",[15,1096,1097],{},"报价远低于这个的，大概率是套壳省了数据\u002F评测",[20,1099,606],{"id":606},[28,1101,1102,1108,1114,1120,1126,1132],{},[31,1103,1104,1107],{},[15,1105,1106],{},"\"AI 现成的便宜\"","：调用 API 确实便宜，但要做好业务集成不便宜。",[31,1109,1110,1113],{},[15,1111,1112],{},"\"自己训模型更专业\"","：除非必要，否则 API+RAG 完全够用。",[31,1115,1116,1119],{},[15,1117,1118],{},"\"数据不用准备\"","：AI 项目数据是大头，省了数据质量一塌糊涂。",[31,1121,1122,1125],{},[15,1123,1124],{},"\"上线就完事\"","：AI 需要持续迭代，token 成本持续。",[31,1127,1128,1131],{},[15,1129,1130],{},"\"私有化简单\"","：私有化涉及硬件、运维、模型部署，成本翻倍。",[31,1133,1134,1137],{},[15,1135,1136],{},"\"AI 输出天然准\"","：需要专门评测集，不评测的 AI 上线即翻车。",[20,1139,647],{"id":647},[506,1141,1142,1148,1154,1160,1166,1172],{},[31,1143,1144,1147],{},[15,1145,1146],{},"先理清要什么 AI 能力","：问答、生成、检索、决策？不同能力做法差异大。",[31,1149,1150,1153],{},[15,1151,1152],{},"决定模型方案","：API \u002F RAG \u002F 自训，根据预算和数据敏感度。",[31,1155,1156,1159],{},[15,1157,1158],{},"盘点数据","：现有数据够不够、要不要清洗标注。",[31,1161,1162,1165],{},[15,1163,1164],{},"要明细报价","：拆到数据、模型、开发、评测、部署。",[31,1167,1168,1171],{},[15,1169,1170],{},"问清持续成本","：token、运维、迭代。",[31,1173,1174,1177],{},[15,1175,1176],{},"看 AI 经验","：做过的 AI 项目、可演示 demo。",[685,1179,1180],{},[11,1181,1182],{},"广州市汉诺雷斯（HNREIS）做 AI 项目（智能客服、知识库、文档处理、Agent 工作流）坚持明细报价：先理需求、出方案、给模块工时明细。把你的 AI 需求告诉我们，我们给方案和报价。",{"title":691,"searchDepth":692,"depth":692,"links":1184},[1185,1186,1191,1197,1198,1199],{"id":768,"depth":692,"text":769},{"id":853,"depth":692,"text":853,"children":1187},[1188,1189,1190],{"id":856,"depth":698,"text":857},{"id":884,"depth":698,"text":885},{"id":908,"depth":698,"text":909},{"id":932,"depth":692,"text":932,"children":1192},[1193,1194,1195,1196],{"id":935,"depth":698,"text":935},{"id":955,"depth":698,"text":955},{"id":969,"depth":698,"text":970},{"id":984,"depth":698,"text":984},{"id":998,"depth":692,"text":999},{"id":606,"depth":692,"text":606},{"id":647,"depth":692,"text":647},"2024-05-17","AI项目的报价常常让企业主困惑——同样一个需求，A 报 10 万，B 报 50 万，差异巨大。本文拆解 AI 项目报价背后的真实构成，讲清需求复杂度、数据、模型选型如何决定价格，让你看懂 AI 外包报价。",[1203,1206,1209],{"q":1204,"a":1205},"AI 项目报价为什么差异这么大？","AI 项目差异大，主要因为变量多：用现成 API（如 GPT、文心）调用，还是从零训练模型；数据要不要清洗、标注；要不要私有部署；调用量多大。同样一个\"智能客服\"，用 API 套壳可能几万块，做完整知识库+RAG+私有化可能几十万。报价差异反映的是做法和工作量的差异。",{"q":1207,"a":1208},"调用现成 AI API 和自己训模型，价格差多少？","差很多。调用大厂 API（OpenAI、文心、通义、智谱）是按 token 计费，开发主要是接口对接+业务封装，几万到十几万就能落地。自己训模型涉及数据采集清洗、算力租用、调参、评估，起步几十万到上百万。绝大多数企业应用用 API+RAG 就够，不必从头训模型。",{"q":1210,"a":1211},"AI 项目报价应该包含哪些明细？","至少包含：需求拆解（要做什么 AI 能力）、数据准备（清洗\u002F标注\u002F向量库）、模型方案（API 还是自训）、后端开发、前端开发、测试（含 AI 评测集）、私有化部署（如需）、运维、token 成本预估。只有总价没明细的报价，后期加项空间巨大。",[1213,1214,1215,1216],"AI项目报价","AI外包","AI开发成本","模型选型",{},"\u002Fblog\u002Fcost-process\u002Fai-xiangmu-baojia-mingxi",{"title":756,"description":1201},{"loc":1218},"blog\u002Fcost-process\u002Fai-xiangmu-baojia-mingxi",[1223,1224,1225],"AI","报价","透明","acIdRbDaJcEhnsXD4OIPN64UoHX0_rvqSA2Bx2ypIpc",{"id":1228,"title":1229,"author":6,"body":1230,"category":721,"cover":722,"date":1686,"description":1687,"draft":725,"extension":726,"faq":1688,"featured":725,"image":722,"keywords":1698,"meta":1703,"navigation":743,"path":1704,"seo":1705,"sitemap":1706,"stem":1707,"tags":1708,"updated":1686,"__hash__":1710},"blog\u002Fblog\u002Fcost-process\u002Fbaojia-buhou-xiugai.md","报价包不包含后续修改",{"type":8,"value":1231,"toc":1668},[1232,1238,1241,1244,1346,1351,1355,1358,1362,1376,1380,1397,1401,1412,1418,1422,1425,1433,1439,1442,1446,1457,1461,1475,1479,1490,1495,1499,1502,1513,1519,1523,1577,1584,1586,1624,1626,1663],[11,1233,1234,1235],{},"\"上线了，但我现在想改个按钮位置、加个字段——这是不是改一点点的事，免费的吧？\"这种话在外包项目里天天出现。",[15,1236,1237],{},"报价里的\"开发完成\"通常只指合同约定功能，不包含后续修改——把范围和边界讲清楚，才能避免上线后扯皮加价。",[20,1239,1240],{"id":1240},"报价到底包什么",[11,1242,1243],{},"软件外包报价通常包含这几部分：",[55,1245,1246,1259],{},[58,1247,1248],{},[61,1249,1250,1253,1256],{},[64,1251,1252],{},"范围",[64,1254,1255],{},"包不包",[64,1257,1258],{},"说明",[71,1260,1261,1272,1282,1292,1303,1314,1325,1336],{},[61,1262,1263,1266,1269],{},[76,1264,1265],{},"合同约定的功能开发",[76,1267,1268],{},"包",[76,1270,1271],{},"这是报价主体",[61,1273,1274,1277,1279],{},[76,1275,1276],{},"合同约定的设计稿实现",[76,1278,1268],{},[76,1280,1281],{},"按确认的 UI 稿做",[61,1283,1284,1287,1289],{},[76,1285,1286],{},"Bug 修复（质保期内）",[76,1288,1268],{},[76,1290,1291],{},"通常 1-3 个月免费",[61,1293,1294,1297,1300],{},[76,1295,1296],{},"文档与部署说明",[76,1298,1299],{},"看合同",[76,1301,1302],{},"规范公司包",[61,1304,1305,1308,1311],{},[76,1306,1307],{},"需求变更、加功能",[76,1309,1310],{},"不包",[76,1312,1313],{},"另签变更单",[61,1315,1316,1319,1322],{},[76,1317,1318],{},"设计稿调整（开发中）",[76,1320,1321],{},"看阶段",[76,1323,1324],{},"早期改包，后期改另算",[61,1326,1327,1330,1333],{},[76,1328,1329],{},"上线后改文案\u002F图片",[76,1331,1332],{},"边界模糊",[76,1334,1335],{},"看合同约定",[61,1337,1338,1341,1343],{},[76,1339,1340],{},"新增页面\u002F模块",[76,1342,1310],{},[76,1344,1345],{},"另计费",[11,1347,1348,144],{},[15,1349,1350],{},"只有合同写明的范围内才包，其他都是变更",[20,1352,1354],{"id":1353},"改一点点的边界","\"改一点点\"的边界",[11,1356,1357],{},"最容易扯皮的就是\"改一点点\"：",[51,1359,1361],{"id":1360},"算修改免费或低成本","算修改（免费或低成本）",[28,1363,1364,1367,1370,1373],{},[31,1365,1366],{},"文字错别字。",[31,1368,1369],{},"图片替换。",[31,1371,1372],{},"颜色微调。",[31,1374,1375],{},"Bug 修复（质保期内）。",[51,1377,1379],{"id":1378},"算需求变更另计费","算需求变更（另计费）",[28,1381,1382,1385,1388,1391,1394],{},[31,1383,1384],{},"加新功能、新页面。",[31,1386,1387],{},"改业务流程。",[31,1389,1390],{},"字段类型变化（如文本改下拉）。",[31,1392,1393],{},"改交互逻辑。",[31,1395,1396],{},"第三方对接新增。",[51,1398,1400],{"id":1399},"灰色地带看合同约定","灰色地带（看合同约定）",[28,1402,1403,1406,1409],{},[31,1404,1405],{},"按钮位置移动（小改？布局重排？）。",[31,1407,1408],{},"字段加几个（加 1 个？加 10 个？）。",[31,1410,1411],{},"列表加排序（小功能？还是整套筛选？）。",[11,1413,1414,1417],{},[15,1415,1416],{},"灰色地带要靠合同写清楚","，不然扯皮没完。",[20,1419,1421],{"id":1420},"为什么改一点点也要钱","为什么\"改一点点\"也要钱",[11,1423,1424],{},"很多企业主觉得\"加个字段多简单\"，但实际成本：",[28,1426,1427,1430],{},[31,1428,1429],{},"加字段：数据库改表 → 后端改接口 → 前端改表单 → 改校验 → 测试。",[31,1431,1432],{},"一个\"加字段\"涉及 4-5 处改动和测试，不是 5 分钟的事。",[11,1434,1435,1438],{},[15,1436,1437],{},"软件开发是连锁改动","，一处改处处改。所以即使看起来\"小\"，也涉及工时。",[20,1440,1441],{"id":1441},"怎么避免扯皮",[51,1443,1445],{"id":1444},"_1-需求文档写到字段级","1. 需求文档写到字段级",[28,1447,1448,1451,1454],{},[31,1449,1450],{},"每个页面有什么字段、什么交互。",[31,1452,1453],{},"字段类型、校验规则、来源。",[31,1455,1456],{},"越细越好，\"做成 XX 那样\"不算需求。",[51,1458,1460],{"id":1459},"_2-合同写清范围与变更","2. 合同写清范围与变更",[28,1462,1463,1466,1469,1472],{},[31,1464,1465],{},"开发范围（功能清单）。",[31,1467,1468],{},"质保期（修 bug 免费时长）。",[31,1470,1471],{},"变更流程（怎么提变更、怎么计费）。",[31,1473,1474],{},"设计稿确认机制（确认后改要另算）。",[51,1476,1478],{"id":1477},"_3-确认环节留痕","3. 确认环节留痕",[28,1480,1481,1484,1487],{},[31,1482,1483],{},"需求文档确认签字。",[31,1485,1486],{},"设计稿确认签字。",[31,1488,1489],{},"演示验收留记录。",[11,1491,1492,144],{},[15,1493,1494],{},"口头确认不算，必须文档留痕",[51,1496,1498],{"id":1497},"_4-变更单制度","4. 变更单制度",[11,1500,1501],{},"任何超出范围的改动走变更单：",[28,1503,1504,1507,1510],{},[31,1505,1506],{},"写明改什么。",[31,1508,1509],{},"估算工时和费用。",[31,1511,1512],{},"双方确认才执行。",[11,1514,1515,1518],{},[15,1516,1517],{},"变更单制度保护双方","——客户不会被乱加价，开发不会被无止境改。",[20,1520,1522],{"id":1521},"成本参考变更怎么计费","成本参考：变更怎么计费",[55,1524,1525,1535],{},[58,1526,1527],{},[61,1528,1529,1532],{},[64,1530,1531],{},"变更类型",[64,1533,1534],{},"计费方式",[71,1536,1537,1545,1553,1561,1569],{},[61,1538,1539,1542],{},[76,1540,1541],{},"小改动（文字、图片）",[76,1543,1544],{},"看合同，部分公司宽限",[61,1546,1547,1550],{},[76,1548,1549],{},"字段新增\u002F修改",[76,1551,1552],{},"按工时（约 0.5-2 人天）",[61,1554,1555,1558],{},[76,1556,1557],{},"新增页面",[76,1559,1560],{},"按页面工时（约 2-5 人天）",[61,1562,1563,1566],{},[76,1564,1565],{},"新增功能模块",[76,1567,1568],{},"单独签子合同",[61,1570,1571,1574],{},[76,1572,1573],{},"业务流程改动",[76,1575,1576],{},"按工时，可能涉及多端",[11,1578,1579,1580,1583],{},"人天单价参考 800-1500 元。",[15,1581,1582],{},"变更越早提，成本越低","——开发后期改成本是初期的 5-10 倍。",[20,1585,606],{"id":606},[28,1587,1588,1594,1600,1606,1612,1618],{},[31,1589,1590,1593],{},[15,1591,1592],{},"\"开发完会一直帮我改\"","：质保期外的修改要钱。",[31,1595,1596,1599],{},[15,1597,1598],{},"\"加个字段不收费吧\"","：涉及多端联动，是工时。",[31,1601,1602,1605],{},[15,1603,1604],{},"\"口头确认就行\"","：口头不算，扯皮没证据。",[31,1607,1608,1611],{},[15,1609,1610],{},"\"上线后再想需求\"","：上线后改成本高，需求前期定。",[31,1613,1614,1617],{},[15,1615,1616],{},"\"改一点点都不给改\"","：合同约定好的范围内，开发有义务做。",[31,1619,1620,1623],{},[15,1621,1622],{},"\"变更单麻烦\"","：变更单保护双方，必须走。",[20,1625,647],{"id":647},[506,1627,1628,1634,1640,1646,1652,1658],{},[31,1629,1630,1633],{},[15,1631,1632],{},"需求文档写到字段级","：每个功能描述清楚。",[31,1635,1636,1639],{},[15,1637,1638],{},"合同写范围和变更流程","：避免扯皮。",[31,1641,1642,1645],{},[15,1643,1644],{},"设计稿\u002F需求确认留痕","：签字或邮件确认。",[31,1647,1648,1651],{},[15,1649,1650],{},"建立变更单制度","：超范围改走流程。",[31,1653,1654,1657],{},[15,1655,1656],{},"变更尽早提","：越早成本越低。",[31,1659,1660,1662],{},[15,1661,682],{},"：愿意走文档流程的，靠谱。",[685,1664,1665],{},[11,1666,1667],{},"广州市汉诺雷斯（HNREIS）在合同里写清开发范围、质保期、变更流程，需求文档到字段级，变更走变更单透明计费。把你的项目需求告诉我们，我们出明细方案和报价。",{"title":691,"searchDepth":692,"depth":692,"links":1669},[1670,1671,1676,1677,1683,1684,1685],{"id":1240,"depth":692,"text":1240},{"id":1353,"depth":692,"text":1354,"children":1672},[1673,1674,1675],{"id":1360,"depth":698,"text":1361},{"id":1378,"depth":698,"text":1379},{"id":1399,"depth":698,"text":1400},{"id":1420,"depth":692,"text":1421},{"id":1441,"depth":692,"text":1441,"children":1678},[1679,1680,1681,1682],{"id":1444,"depth":698,"text":1445},{"id":1459,"depth":698,"text":1460},{"id":1477,"depth":698,"text":1478},{"id":1497,"depth":698,"text":1498},{"id":1521,"depth":692,"text":1522},{"id":606,"depth":692,"text":606},{"id":647,"depth":692,"text":647},"2024-05-29","软件外包报价单上写的\"开发完成\"，往往不包含上线后的修改和调整。本文讲清报价范围、修改边界、版本管理怎么定，避免上线后因\"改一点点\"扯皮加价。",[1689,1692,1695],{"q":1690,"a":1691},"报价里说的\"开发完成\"包含后续修改吗？","看合同怎么写。规范的报价会区分\"开发范围\"和\"质保期\"——开发范围是合同约定的功能，质保期是上线后修 bug 的免费期（通常 1-3 个月）。新增功能、改需求、调整设计都不在范围内，要另计费。签合同前必须把范围写清楚。",{"q":1693,"a":1694},"上线后改一个小功能要不要钱？","看是什么改动。修 bug 在质保期内免费；调整文字、改图标这种小改动看合同约定，有些公司宽限几小时不收费；但新增功能、改业务流程、加页面，都是需求变更要另计费。\"只是改一点点\"往往是扯皮起点，靠合同约定边界。",{"q":1696,"a":1697},"怎么避免上线后扯皮改需求？","三件事：一是需求文档足够细，每个功能描述到字段和交互；二是合同写清楚范围、修改边界、变更流程；三是确认环节要在文档上签字，不要口头确认。需求文档越细，后期扯皮越少。",[1699,1700,1701,1702],"报价包含修改","软件外包修改","需求变更","报价范围",{},"\u002Fblog\u002Fcost-process\u002Fbaojia-buhou-xiugai",{"title":1229,"description":1687},{"loc":1704},"blog\u002Fcost-process\u002Fbaojia-buhou-xiugai",[1224,1709,751],"修改","YLc1PxAo2HP1n5HdiqnTdqnVtPdj6iJeOZDu0a53MpY",{"id":1712,"title":1713,"author":6,"body":1714,"category":721,"cover":722,"date":2346,"description":2347,"draft":725,"extension":726,"faq":2348,"featured":725,"image":722,"keywords":2358,"meta":2363,"navigation":743,"path":2364,"seo":2365,"sitemap":2366,"stem":2367,"tags":2368,"updated":2346,"__hash__":2370},"blog\u002Fblog\u002Fcost-process\u002Fbaojia-chaju-zenme-pan.md","不同公司报价差很多怎么判断",{"type":8,"value":1715,"toc":2323},[1716,1723,1726,1729,1834,1839,1843,1847,1850,1989,1994,1998,2017,2023,2027,2047,2053,2057,2077,2083,2086,2090,2093,2097,2111,2115,2118,2132,2136,2150,2155,2158,2162,2173,2178,2182,2193,2198,2202,2213,2218,2222,2233,2238,2240,2278,2280,2318],[11,1717,1718,1719,1722],{},"\"做个小程序，A 报 3 万，B 报 8 万，C 报 15 万——到底谁合理？\"这是企业主最常遇到的困境。",[15,1720,1721],{},"报价差异大不一定是有人黑心，而是大家\"做多少事、做到什么程度\"完全不同——拆开明细看，才知道谁合理。"," 这篇文章讲清怎么判断报价差异。",[20,1724,1725],{"id":1725},"报价为什么会差这么多",[11,1727,1728],{},"同一个需求报价差异大，主要因为：",[55,1730,1731,1744],{},[58,1732,1733],{},[61,1734,1735,1738,1741],{},[64,1736,1737],{},"因素",[64,1739,1740],{},"低价可能",[64,1742,1743],{},"高价可能",[71,1745,1746,1757,1768,1779,1790,1801,1812,1823],{},[61,1747,1748,1751,1754],{},[76,1749,1750],{},"工时",[76,1752,1753],{},"压缩（少做\u002F省环节）",[76,1755,1756],{},"充分（细致）",[61,1758,1759,1762,1765],{},[76,1760,1761],{},"团队",[76,1763,1764],{},"初级开发",[76,1766,1767],{},"资深团队",[61,1769,1770,1773,1776],{},[76,1771,1772],{},"设计",[76,1774,1775],{},"套模板",[76,1777,1778],{},"原创设计",[61,1780,1781,1784,1787],{},[76,1782,1783],{},"测试",[76,1785,1786],{},"不测或简测",[76,1788,1789],{},"完整测试",[61,1791,1792,1795,1798],{},[76,1793,1794],{},"售后",[76,1796,1797],{},"上线失联",[76,1799,1800],{},"质保期+运维",[61,1802,1803,1806,1809],{},[76,1804,1805],{},"源码",[76,1807,1808],{},"不交或加钱",[76,1810,1811],{},"交付",[61,1813,1814,1817,1820],{},[76,1815,1816],{},"文档",[76,1818,1819],{},"无",[76,1821,1822],{},"完整文档",[61,1824,1825,1828,1831],{},[76,1826,1827],{},"技术",[76,1829,1830],{},"老旧\u002F杂牌",[76,1832,1833],{},"现代+规范",[11,1835,1836,144],{},[15,1837,1838],{},"看起来\"同一个需求\"，实际包含的工作量差几倍很正常",[20,1840,1842],{"id":1841},"_4-个维度判断报价合理性","4 个维度判断报价合理性",[51,1844,1846],{"id":1845},"维度-1报价包含什么","维度 1：报价包含什么",[11,1848,1849],{},"把每家报价的\"包含项\"列出来对比：",[55,1851,1852,1867],{},[58,1853,1854],{},[61,1855,1856,1858,1861,1864],{},[64,1857,562],{},[64,1859,1860],{},"A（3万）",[64,1862,1863],{},"B（8万）",[64,1865,1866],{},"C（15万）",[71,1868,1869,1882,1895,1907,1919,1931,1942,1953,1965,1978],{},[61,1870,1871,1874,1876,1879],{},[76,1872,1873],{},"需求文档",[76,1875,1819],{},[76,1877,1878],{},"简要",[76,1880,1881],{},"详细",[61,1883,1884,1887,1889,1892],{},[76,1885,1886],{},"原型",[76,1888,1819],{},[76,1890,1891],{},"简单线框",[76,1893,1894],{},"完整原型",[61,1896,1897,1900,1902,1905],{},[76,1898,1899],{},"UI 设计",[76,1901,1775],{},[76,1903,1904],{},"半原创",[76,1906,1778],{},[61,1908,1909,1912,1915,1917],{},[76,1910,1911],{},"前后端开发",[76,1913,1914],{},"含",[76,1916,1914],{},[76,1918,1914],{},[61,1920,1921,1923,1926,1929],{},[76,1922,1783],{},[76,1924,1925],{},"不测",[76,1927,1928],{},"简测",[76,1930,1789],{},[61,1932,1933,1936,1938,1940],{},[76,1934,1935],{},"上线部署",[76,1937,1914],{},[76,1939,1914],{},[76,1941,1914],{},[61,1943,1944,1946,1948,1950],{},[76,1945,1816],{},[76,1947,1819],{},[76,1949,1878],{},[76,1951,1952],{},"完整",[61,1954,1955,1957,1960,1963],{},[76,1956,1805],{},[76,1958,1959],{},"不交",[76,1961,1962],{},"加钱交",[76,1964,1811],{},[61,1966,1967,1970,1972,1975],{},[76,1968,1969],{},"质保期",[76,1971,1819],{},[76,1973,1974],{},"1 个月",[76,1976,1977],{},"3 个月",[61,1979,1980,1983,1985,1987],{},[76,1981,1982],{},"培训",[76,1984,1819],{},[76,1986,1819],{},[76,1988,1914],{},[11,1990,1991,144],{},[15,1992,1993],{},"包含项差很多，价格差异就有依据",[51,1995,1997],{"id":1996},"维度-2团队配置","维度 2：团队配置",[28,1999,2000,2005,2011],{},[31,2001,2002,2004],{},[15,2003,1764],{},"：单价低（500-800 元\u002F人天），但能力弱、质量差。",[31,2006,2007,2010],{},[15,2008,2009],{},"中级开发","：单价中（800-1200 元\u002F人天），主力。",[31,2012,2013,2016],{},[15,2014,2015],{},"资深开发","：单价高（1200-2000 元\u002F人天），技术好。",[11,2018,2019,2020,144],{},"同样工时，团队级别不同，单价差异 2-3 倍。",[15,2021,2022],{},"低价报价通常用初级开发或外包再外包",[51,2024,2026],{"id":2025},"维度-3技术方案","维度 3：技术方案",[28,2028,2029,2035,2041],{},[31,2030,2031,2034],{},[15,2032,2033],{},"成熟方案","：Vue\u002FReact\u002FNode，开发者多，成本可控。",[31,2036,2037,2040],{},[15,2038,2039],{},"冷门技术","：特定框架、老旧语言，人才少，单价高。",[31,2042,2043,2046],{},[15,2044,2045],{},"过度设计","：简单的需求用复杂架构（微服务、K8s），成本虚高。",[11,2048,2049,2052],{},[15,2050,2051],{},"判断技术方案是否匹配需求复杂度","——简单需求过度设计是浪费，复杂需求用简陋方案是坑。",[51,2054,2056],{"id":2055},"维度-4工时合理性","维度 4：工时合理性",[28,2058,2059,2065,2071],{},[31,2060,2061,2064],{},[15,2062,2063],{},"工时太低","：低于合理范围，省环节或赶工。",[31,2066,2067,2070],{},[15,2068,2069],{},"工时合理","：匹配功能复杂度。",[31,2072,2073,2076],{},[15,2074,2075],{},"工时太高","：可能虚报或杀熟。",[11,2078,2079,2080,144],{},"参考：一个标准登录注册（含找回密码）约 2-3 人天；一个内容列表（增删改查）约 3-5 人天；一个商品详情页约 3-5 人天。",[15,2081,2082],{},"报价工时远低于这个，警惕",[20,2084,2085],{"id":2085},"怎么对比多家报价",[51,2087,2089],{"id":2088},"_1-要求统一格式","1. 要求统一格式",[11,2091,2092],{},"让每家用同样的明细格式报价（模块工时、单价、包含项），便于对比。",[51,2094,2096],{"id":2095},"_2-关注总工时和单价","2. 关注总工时和单价",[28,2098,2099,2102,2105,2108],{},[31,2100,2101],{},"总工时 = 所有模块工时之和。",[31,2103,2104],{},"单价 = 总价 \u002F 总工时。",[31,2106,2107],{},"单价低于 600 元\u002F人天的，警惕（低于合理成本）。",[31,2109,2110],{},"单价高于 2000 元\u002F人天的，问清楚为什么。",[51,2112,2114],{"id":2113},"_3-看省了什么","3. 看\"省了什么\"",[11,2116,2117],{},"低价报价一定省了什么——",[28,2119,2120,2123,2126,2129],{},[31,2121,2122],{},"省需求文档？后期扯皮。",[31,2124,2125],{},"省测试？上线一堆 bug。",[31,2127,2128],{},"省售后？出事没人管。",[31,2130,2131],{},"省源码？被绑架。",[51,2133,2135],{"id":2134},"_4-看合同条款","4. 看合同条款",[28,2137,2138,2141,2144,2147],{},[31,2139,2140],{},"敢写源码归属？",[31,2142,2143],{},"敢写违约责任？",[31,2145,2146],{},"敢写分期付款？",[31,2148,2149],{},"敢写验收标准？",[11,2151,2152,144],{},[15,2153,2154],{},"条款含糊的，再便宜也别签",[20,2156,2157],{"id":2157},"报价差异的几种情况",[51,2159,2161],{"id":2160},"情况-a低价正常","情况 A：低价正常",[28,2163,2164,2167,2170],{},[31,2165,2166],{},"模板建站。",[31,2168,2169],{},"SaaS 套餐。",[31,2171,2172],{},"简单重复工作。",[11,2174,2175,144],{},[15,2176,2177],{},"这些低价合理，因为是\"批量\u002F标准化\"",[51,2179,2181],{"id":2180},"情况-b低价不正常","情况 B：低价不正常",[28,2183,2184,2187,2190],{},[31,2185,2186],{},"定制开发报模板价。",[31,2188,2189],{},"远低于市场平均。",[31,2191,2192],{},"拒绝出明细。",[11,2194,2195,144],{},[15,2196,2197],{},"警惕，大概率是坑",[51,2199,2201],{"id":2200},"情况-c高价正常","情况 C：高价正常",[28,2203,2204,2207,2210],{},[31,2205,2206],{},"包含完整服务。",[31,2208,2209],{},"资深团队。",[31,2211,2212],{},"复杂需求。",[11,2214,2215,144],{},[15,2216,2217],{},"这种高价有依据",[51,2219,2221],{"id":2220},"情况-d高价不正常","情况 D：高价不正常",[28,2223,2224,2227,2230],{},[31,2225,2226],{},"工时虚高。",[31,2228,2229],{},"单价虚高。",[31,2231,2232],{},"杀熟。",[11,2234,2235,144],{},[15,2236,2237],{},"这种高价也是坑",[20,2239,606],{"id":606},[28,2241,2242,2248,2254,2260,2266,2272],{},[31,2243,2244,2247],{},[15,2245,2246],{},"\"选最便宜的\"","：低价往往更贵（加项\u002F绑架\u002F重做）。",[31,2249,2250,2253],{},[15,2251,2252],{},"\"选最贵的\"","：高价不一定靠谱，可能是杀熟。",[31,2255,2256,2259],{},[15,2257,2258],{},"\"只看总价\"","：必须拆明细才能判断。",[31,2261,2262,2265],{},[15,2263,2264],{},"\"报价快就是专业\"","：不出需求文档就报价，多半是套模板或猜。",[31,2267,2268,2271],{},[15,2269,2270],{},"\"承诺多就是好\"","：敢不敢写进合同比口头承诺重要。",[31,2273,2274,2277],{},[15,2275,2276],{},"\"案例多就是大公司\"","：编造的案例经不起验证。",[20,2279,647],{"id":647},[506,2281,2282,2288,2294,2300,2306,2312],{},[31,2283,2284,2287],{},[15,2285,2286],{},"先理清需求","：把功能、目标、预期讲清楚。",[31,2289,2290,2293],{},[15,2291,2292],{},"要求统一格式报价","：便于对比。",[31,2295,2296,2299],{},[15,2297,2298],{},"拆到模块工时和单价","：不只看总价。",[31,2301,2302,2305],{},[15,2303,2304],{},"对比包含项","：看省了什么。",[31,2307,2308,2311],{},[15,2309,2310],{},"看合同条款","：源码、违约、验收。",[31,2313,2314,2317],{},[15,2315,2316],{},"验证案例","：要真实可访问的。",[685,2319,2320],{},[11,2321,2322],{},"广州市汉诺雷斯（HNREIS）坚持透明明细报价，拆到模块工时、单价、包含项，写规范合同。把你的需求告诉我们，我们出明细报价——你可以拿去对比，看清谁合理。",{"title":691,"searchDepth":692,"depth":692,"links":2324},[2325,2326,2332,2338,2344,2345],{"id":1725,"depth":692,"text":1725},{"id":1841,"depth":692,"text":1842,"children":2327},[2328,2329,2330,2331],{"id":1845,"depth":698,"text":1846},{"id":1996,"depth":698,"text":1997},{"id":2025,"depth":698,"text":2026},{"id":2055,"depth":698,"text":2056},{"id":2085,"depth":692,"text":2085,"children":2333},[2334,2335,2336,2337],{"id":2088,"depth":698,"text":2089},{"id":2095,"depth":698,"text":2096},{"id":2113,"depth":698,"text":2114},{"id":2134,"depth":698,"text":2135},{"id":2157,"depth":692,"text":2157,"children":2339},[2340,2341,2342,2343],{"id":2160,"depth":698,"text":2161},{"id":2180,"depth":698,"text":2181},{"id":2200,"depth":698,"text":2201},{"id":2220,"depth":698,"text":2221},{"id":606,"depth":692,"text":606},{"id":647,"depth":692,"text":647},"2024-06-08","同一个软件需求，A 公司报 5 万，B 公司报 15 万，差好几倍。本文从报价明细、包含范围、团队配置、技术方案 4 个维度讲清怎么判断报价合理性，识破低价陷阱、避开虚高报价。",[2349,2352,2355],{"q":2350,"a":2351},"同一个需求报价差好几倍，怎么判断谁合理？","不能只看总价，要拆明细。看四点：报价包含什么（设计\u002F测试\u002F售后\u002F源码）、团队配置（初级还是资深）、技术方案（成熟还是冷门）、工时合理性（工时是不是被人为压低）。同样的需求，包含完整服务和省环节的报价差几倍很正常，关键是拆开看钱花在哪。",{"q":2353,"a":2354},"低价报价是不是一定不靠谱？","不一定，但远低于市场平均的要警惕。判断方法：要看明细——如果只给总价不拆工时，无法判断；要看省了什么——省了设计\u002F测试\u002F售后\u002F源码的便宜有原因；要看合同——敢不敢写源码、违约、验收。低得合理的有（标准化产品、模板），低得不合理的（定制开发远低市场）基本是坑。",{"q":2356,"a":2357},"高价就一定靠谱吗？","不一定。有的高价是包含完整服务（设计、测试、资深团队、售后），值这个钱；有的高价是品牌溢价或杀熟，不值。看高价报价要看明细——如果工时和单价合理，包含的服务完整，那高价有依据；如果只有总价没明细，或工时虚高，那高价也是坑。",[2359,2360,2361,2362],"报价差异","软件外包报价","怎么判断报价","低价陷阱",{},"\u002Fblog\u002Fcost-process\u002Fbaojia-chaju-zenme-pan",{"title":1713,"description":2347},{"loc":2364},"blog\u002Fcost-process\u002Fbaojia-chaju-zenme-pan",[1224,2369,1225],"决策","mB7BRictfurYpDWbxNpo5900YhfhMP0rUGPEp8NVo2U",{"id":2372,"title":2373,"author":6,"body":2374,"category":721,"cover":722,"date":2896,"description":2897,"draft":725,"extension":726,"faq":2898,"featured":725,"image":722,"keywords":2908,"meta":2913,"navigation":743,"path":2914,"seo":2915,"sitemap":2916,"stem":2917,"tags":2918,"updated":2896,"__hash__":2920},"blog\u002Fblog\u002Fcost-process\u002Fbaojia-tanpan.md","软件外包报价怎么谈判",{"type":8,"value":2375,"toc":2872},[2376,2383,2387,2390,2394,2408,2414,2418,2430,2434,2445,2450,2453,2457,2487,2493,2497,2508,2512,2526,2530,2533,2550,2555,2559,2570,2573,2577,2580,2591,2596,2600,2611,2615,2626,2631,2634,2637,2691,2696,2699,2702,2740,2745,2749,2787,2789,2826,2828,2867],[11,2377,2378,2379,2382],{},"拿到报价单，第一反应往往是\"能不能便宜点\"。",[15,2380,2381],{},"软件外包报价当然可以谈，但要谈对地方——盲目砍价只会让开发方从质量和服务里找回来，最后吃亏的还是你。"," 这篇文章讲清怎么谈判才合理。",[20,2384,2386],{"id":2385},"谈判前先拆报价","谈判前：先拆报价",[11,2388,2389],{},"谈判前必须做的事：",[51,2391,2393],{"id":2392},"_1-要求明细报价","1. 要求明细报价",[28,2395,2396,2399,2402,2405],{},[31,2397,2398],{},"模块清单。",[31,2400,2401],{},"每模块工时（人天）。",[31,2403,2404],{},"人天单价。",[31,2406,2407],{},"设计费、测试费、管理费、售后。",[11,2409,2410,2413],{},[15,2411,2412],{},"只有总价没法谈","——你不知道哪部分虚高。",[51,2415,2417],{"id":2416},"_2-算出总工时和单价","2. 算出总工时和单价",[28,2419,2420,2422,2424,2427],{},[31,2421,2101],{},[31,2423,2104],{},[31,2425,2426],{},"单价低于 600 元\u002F人天 → 不正常（可能省环节）。",[31,2428,2429],{},"单价高于 2000 元\u002F人天 → 问清为什么。",[51,2431,2433],{"id":2432},"_3-识别虚高部分","3. 识别虚高部分",[28,2435,2436,2439,2442],{},[31,2437,2438],{},"工时虚报（一个登录说 10 人天）。",[31,2440,2441],{},"单价虚高（中级开发报资深价）。",[31,2443,2444],{},"重复收费（设计费算了两次）。",[11,2446,2447,144],{},[15,2448,2449],{},"虚高部分才是谈判空间，合理部分硬砍只会被反噬",[20,2451,2452],{"id":2452},"可以谈的几个点",[51,2454,2456],{"id":2455},"_1-付款节点","1. 付款节点",[55,2458,2459,2469],{},[58,2460,2461],{},[61,2462,2463,2466],{},[64,2464,2465],{},"原方案",[64,2467,2468],{},"可谈方案",[71,2470,2471,2479],{},[61,2472,2473,2476],{},[76,2474,2475],{},"50% 预付 + 50% 验收",[76,2477,2478],{},"30% 预付 + 30% 中期 + 40% 验收",[61,2480,2481,2484],{},[76,2482,2483],{},"验收付清",[76,2485,2486],{},"留 10% 质保金 3 个月",[11,2488,2489,2492],{},[15,2490,2491],{},"拉长分期、留质保金，降低风险","——这是合理的谈判点。",[51,2494,2496],{"id":2495},"_2-工期","2. 工期",[28,2498,2499,2502,2505],{},[31,2500,2501],{},"加急费通常上浮 20%-50%。",[31,2503,2504],{},"不急的话可以谈延长工期，换价格让步。",[31,2506,2507],{},"但工期不能无限延长，否则拖延更亏。",[51,2509,2511],{"id":2510},"_3-范围调整","3. 范围调整",[28,2513,2514,2517,2520],{},[31,2515,2516],{},"砍边缘功能，先做核心 MVP。",[31,2518,2519],{},"把\"锦上添花\"放到二期。",[31,2521,2522,2525],{},[15,2523,2524],{},"核心功能不能砍","，否则失去项目价值。",[51,2527,2529],{"id":2528},"_4-增值服务","4. 增值服务",[11,2531,2532],{},"谈判时可以争取的\"白送\"：",[28,2534,2535,2538,2541,2544,2547],{},[31,2536,2537],{},"完整文档（部署、API、用户手册）。",[31,2539,2540],{},"培训（运维培训、用户培训）。",[31,2542,2543],{},"延长质保期（1 个月 → 3 个月）。",[31,2545,2546],{},"一段时间免费运维（3-6 个月）。",[31,2548,2549],{},"备份和监控方案。",[11,2551,2552,144],{},[15,2553,2554],{},"这些是开发方能给但客户容易忽略的",[51,2556,2558],{"id":2557},"_5-单价让步","5. 单价让步",[28,2560,2561,2564,2567],{},[31,2562,2563],{},"多家对比，单价高的可以让。",[31,2565,2566],{},"但让步空间有限（5%-15%），不能再低。",[31,2568,2569],{},"让步后看是不是改了团队配置（资深降中级）。",[20,2571,2572],{"id":2572},"不该谈的点",[51,2574,2576],{"id":2575},"_1-质量","1. 质量",[11,2578,2579],{},"砍价导致：",[28,2581,2582,2585,2588],{},[31,2583,2584],{},"省测试 → 上线一堆 bug。",[31,2586,2587],{},"用初级开发 → 工期长、质量差。",[31,2589,2590],{},"压缩工时 → 赶工粗糙。",[11,2592,2593,144],{},[15,2594,2595],{},"质量是底线，压价会从质量找回来",[51,2597,2599],{"id":2598},"_2-源码归属","2. 源码归属",[28,2601,2602,2605,2608],{},[31,2603,2604],{},"必须给客户。",[31,2606,2607],{},"不交源码 = 被绑架。",[31,2609,2610],{},"这个不能让步。",[51,2612,2614],{"id":2613},"_3-合同保障","3. 合同保障",[28,2616,2617,2620,2623],{},[31,2618,2619],{},"违约责任。",[31,2621,2622],{},"验收标准。",[31,2624,2625],{},"知识产权。",[11,2627,2628,144],{},[15,2629,2630],{},"保障条款弱化等于放弃保护",[20,2632,2633],{"id":2633},"谈判的合理目标",[11,2635,2636],{},"不是砍到底，而是：",[55,2638,2639,2649],{},[58,2640,2641],{},[61,2642,2643,2646],{},[64,2644,2645],{},"目标",[64,2647,2648],{},"做法",[71,2650,2651,2659,2667,2675,2683],{},[61,2652,2653,2656],{},[76,2654,2655],{},"价格合理",[76,2657,2658],{},"拆虚高部分，砍虚高不砍合理",[61,2660,2661,2664],{},[76,2662,2663],{},"风险可控",[76,2665,2666],{},"分期付款、留质保金",[61,2668,2669,2672],{},[76,2670,2671],{},"范围清晰",[76,2673,2674],{},"边缘功能砍到二期",[61,2676,2677,2680],{},[76,2678,2679],{},"增值多",[76,2681,2682],{},"文档、培训、运维",[61,2684,2685,2688],{},[76,2686,2687],{},"保障足",[76,2689,2690],{},"合同条款完整",[11,2692,2693,144],{},[15,2694,2695],{},"好的谈判是双赢——你拿到合理价和保障，开发方拿到合理利润",[20,2697,2698],{"id":2698},"谈判中的红旗信号",[11,2700,2701],{},"如果开发方在谈判中出现这些，要警惕：",[28,2703,2704,2710,2716,2722,2728,2734],{},[31,2705,2706,2709],{},[15,2707,2708],{},"轻易接受大幅砍价","：说明报价虚高太多，或者准备从别处找回来。",[31,2711,2712,2715],{},[15,2713,2714],{},"口头承诺多","：不写进合同的承诺不算数。",[31,2717,2718,2721],{},[15,2719,2720],{},"急着成交","：可能准备拿钱走人。",[31,2723,2724,2727],{},[15,2725,2726],{},"拒绝明细报价","：只给总价，无法判断合理性。",[31,2729,2730,2733],{},[15,2731,2732],{},"要求全款\u002F大头预付","：风险转嫁给客户。",[31,2735,2736,2739],{},[15,2737,2738],{},"不愿写违约\u002F源码条款","：心虚。",[11,2741,2742,144],{},[15,2743,2744],{},"靠谱的服务商谈判时会守住底线（源码、质量），让步在合理范围（付款、增值）",[20,2746,2748],{"id":2747},"谈判策略分阶段谈","谈判策略：分阶段谈",[506,2750,2751,2757,2763,2769,2775,2781],{},[31,2752,2753,2756],{},[15,2754,2755],{},"先要求明细报价","：拿到明细才能谈。",[31,2758,2759,2762],{},[15,2760,2761],{},"指出虚高部分","：具体到哪个模块工时高、单价高。",[31,2764,2765,2768],{},[15,2766,2767],{},"谈付款和范围","：拉长分期、砍边缘功能。",[31,2770,2771,2774],{},[15,2772,2773],{},"争取增值","：文档、培训、运维。",[31,2776,2777,2780],{},[15,2778,2779],{},"锁定合同保障","：源码、违约、验收写死。",[31,2782,2783,2786],{},[15,2784,2785],{},"不急拍板","：多对比、多沟通。",[20,2788,606],{"id":606},[28,2790,2791,2797,2803,2809,2815,2820],{},[31,2792,2793,2796],{},[15,2794,2795],{},"\"砍得越狠越赚\"","：开发方从质量找回，吃亏的是你。",[31,2798,2799,2802],{},[15,2800,2801],{},"\"口头承诺就行\"","：不写合同的承诺无效。",[31,2804,2805,2808],{},[15,2806,2807],{},"\"急着成交\"","：被对方看穿，谈判被动。",[31,2810,2811,2814],{},[15,2812,2813],{},"\"全款换低价\"","：风险全转嫁，出事没人管。",[31,2816,2817,2819],{},[15,2818,2258],{},"：必须拆明细才能谈。",[31,2821,2822,2825],{},[15,2823,2824],{},"\"敢让步就是好公司\"","：轻易让步的反而要警惕。",[20,2827,647],{"id":647},[506,2829,2830,2836,2842,2848,2853,2857,2861],{},[31,2831,2832,2835],{},[15,2833,2834],{},"要求明细报价","：拆到模块工时。",[31,2837,2838,2841],{},[15,2839,2840],{},"算总工时和单价","：判断合理性。",[31,2843,2844,2847],{},[15,2845,2846],{},"识别虚高部分","：针对性谈。",[31,2849,2850,2852],{},[15,2851,2767],{},"：风险和成本平衡。",[31,2854,2855,2774],{},[15,2856,2773],{},[31,2858,2859,2311],{},[15,2860,2779],{},[31,2862,2863,2866],{},[15,2864,2865],{},"多对比不急拍板","：合理谈判。",[685,2868,2869],{},[11,2870,2871],{},"广州市汉诺雷斯（HNREIS）坚持透明明细报价，欢迎客户拆工时、对比、谈判——我们守源码和质量底线，在付款和增值上合理让步。把需求告诉我们，我们出明细报价，你看着谈。",{"title":691,"searchDepth":692,"depth":692,"links":2873},[2874,2879,2886,2891,2892,2893,2894,2895],{"id":2385,"depth":692,"text":2386,"children":2875},[2876,2877,2878],{"id":2392,"depth":698,"text":2393},{"id":2416,"depth":698,"text":2417},{"id":2432,"depth":698,"text":2433},{"id":2452,"depth":692,"text":2452,"children":2880},[2881,2882,2883,2884,2885],{"id":2455,"depth":698,"text":2456},{"id":2495,"depth":698,"text":2496},{"id":2510,"depth":698,"text":2511},{"id":2528,"depth":698,"text":2529},{"id":2557,"depth":698,"text":2558},{"id":2572,"depth":692,"text":2572,"children":2887},[2888,2889,2890],{"id":2575,"depth":698,"text":2576},{"id":2598,"depth":698,"text":2599},{"id":2613,"depth":698,"text":2614},{"id":2633,"depth":692,"text":2633},{"id":2698,"depth":692,"text":2698},{"id":2747,"depth":692,"text":2748},{"id":606,"depth":692,"text":606},{"id":647,"depth":692,"text":647},"2024-06-19","拿到软件外包报价后，怎么谈才不吃亏？本文讲清谈判前的准备、可谈的几个点（付款、范围、工期、增值）、不该谈的点（质量、源码），帮你谈出合理价又不踩坑。",[2899,2902,2905],{"q":2900,"a":2901},"软件外包报价能砍多少合理？","取决于报价是否虚高。如果报价是按规范工时和单价算出来的，砍价空间有限（5%-10% 是常见的让利空间，用于建立合作）。如果报价虚高（工时虚报、单价虚高），可以拆出不合理部分谈。盲目砍价的副作用是开发方会从别处找回来——省工时、降质量、加项。",{"q":2903,"a":2904},"谈判时哪些点能谈，哪些不能？","能谈的：付款节点（拉长分期降低风险）、工期（延长减少加急费）、范围（先做核心砍边缘功能）、增值（要文档、培训、延长质保）、运维（含一段时间免费运维）。不该谈的：质量（压价会导致省测试\u002F降质量）、源码归属（必须给客户）、合同保障条款（违约、验收不能弱化）。",{"q":2906,"a":2907},"报价砍太狠会有什么后果？","开发方接受低价后，必然从别处找回来：省测试（bug 多）、用初级开发（质量差）、压缩工时（赶工粗糙）、后期加项（\"这个不在范围\"）、不交源码（绑架交付）、上线失联（无售后）。砍价的本质是把成本转移，最后客户付出的是质量、维护、扯皮的代价。砍价要合理，不能盲目压低。",[2909,2910,2911,2912],"外包报价谈判","软件外包谈价","报价谈判技巧","外包合同",{},"\u002Fblog\u002Fcost-process\u002Fbaojia-tanpan",{"title":2373,"description":2897},{"loc":2914},"blog\u002Fcost-process\u002Fbaojia-tanpan",[2919,1224,2369],"谈判","SqN9trtZWP93iZRrrOY6ULCCPIfmZ2ZCmxLAL40jDEo",1781688910064]