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