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