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