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