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