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