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