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