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