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