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