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