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