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