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