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