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