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