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