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