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