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