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