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