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