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