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