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