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