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