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