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