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